What is an IPv6-Mostly Network?

IPv6

An IPv6-mostly network allows IPv6-only, dual-stack, and IPv4-only devices to coexist on the same network segment. Devices capable of operating without native IPv4 connectivity use IPv6, while devices that still require IPv4 continue to receive an IPv4 address. This approach allows organizations to move toward IPv6-only operation incrementally while maintaining compatibility with existing devices and applications.

Last updated: November 8, 2026

Why IPv6-Mostly?

Many organizations deploy IPv6 alongside IPv4, a configuration known as dual stack. However, assigning both protocols to every device keeps demand for IPv4 addresses and requires administrators to manage both protocols across the network. Moving directly to IPv6-only is often impractical, because some devices and applications still depend on IPv4, and building separate network segments for each type of device adds complexity. IPv6-mostly provides a practical next step by letting capable devices operate without native IPv4 connectivity on the same segment, while retaining IPv4 for devices that need it.

Dual-Stack, IPv6-Mostly, and IPv6-Only Compared

 Dual-stackIPv6-mostlyIPv6-only
IPv4 addresses for clientsAll clientsOnly clients that require IPv4None
NAT64 requiredNoYes, for IPv6-only clientsYes
CLAT required for IPv4-only applicationsNoOn IPv6-only clientsYes
DHCP option 108Not usedRequiredNot used
Supports IPv4-only devicesYesYesNo

DHCP Option 108

DHCPv4 option 108, called IPv6-Only Preferred and defined in RFC 8925, provides a way for the network and client to agree that native IPv4 configuration is unnecessary. A client capable of operating without IPv4 requests the option from the DHCP server. When the DHCP scope is configured for IPv6-mostly operation, the server includes the option in its response, along with a wait time. The client then stops DHCPv4 configuration for that period, or until it reconnects to a network. If the server sends a value below 300 seconds (or no value at all), the client waits 300 seconds. Devices that do not request this option continue obtaining IPv4 addresses normally.

Only hosts that can operate without native IPv4 request option 108, usually because they include a CLAT or because all of their applications work over IPv6. Hosts that require IPv4 must not request it. On Windows 11, the client honors option 108 when Windows CLAT (WinCLAT) is permitted on the interface. For configuration guidance, see Configure DHCP Option 108 on Windows DHCP Server for IPv6-Mostly.

Access to IPv4 Resources

Operating without native IPv4 connectivity does not eliminate the need to access IPv4 resources. NAT64 provides translation between IPv6 clients and IPv4 destinations, while DNS64 synthesizes IPv6 DNS records for IPv4-only resources. Applications that generate IPv4 traffic require a customer-side translator (CLAT) working with NAT64, an architecture known as 464XLAT. On Windows, Windows CLAT (WinCLAT) provides this functionality.

NAT64 Prefix Discovery

Option 108 tells a client that it can operate without IPv4, but it does not tell the client how to reach IPv4 destinations. IPv6-only clients learn the network’s NAT64 prefix separately, either from the PREF64 option in IPv6 router advertisements (RFC 8781) or by querying a DNS64 server for ipv4only.arpa (RFC 7050). PREF64 is generally preferred because it does not depend on DNS. For more information, see How Windows CLAT Discovers the NAT64 Prefix and Configure Windows Server DNS64 for IPv6-Mostly and IPv6-Only.

Deployment Considerations

IPv6-mostly requires working IPv6 connectivity, NAT64, a discoverable NAT64 prefix, and validation of device and application compatibility. Enabling DHCP option 108 alone does not provide these capabilities. Enabling option 108 without NAT64 does not break IPv6 connectivity, but clients that forgo IPv4 lose access to IPv4-only destinations, and WinCLAT cannot activate without a NAT64 prefix. Administrators should test with a limited group of devices before expanding deployment. The IETF describes this approach in IPv6-mostly Networks: Deployment and Operations Considerations. As of November 2026, the document is in IETF Last Call and nearing publication as an Informational RFC.

Frequently Asked Questions

What is the difference between IPv6-mostly and IPv6-only?

An IPv6-only network provides no native IPv4 to any device. An IPv6-mostly network still offers IPv4 through DHCP, but capable devices decline it using option 108, so IPv4-only devices continue to work on the same segment.

Does IPv6-mostly require a separate network segment?

No. IPv6-only, dual-stack, and IPv4-only devices share the same segment, VLAN, or SSID. Each device configures itself based on its capabilities.

What happens to devices that do not support option 108?

They obtain an IPv4 address through DHCP as usual and are unaffected by the IPv6-mostly configuration.

Is NAT64 required for IPv6-mostly?

Yes. NAT64 is part of the definition of an IPv6-mostly network in RFC 8925. Without it, devices that decline IPv4 cannot reach IPv4-only destinations, whether through DNS64 or a CLAT.

Does Windows support IPv6-mostly?

Yes. Windows 11 honors DHCP option 108 when WinCLAT is permitted, and WinCLAT provides IPv4 support for applications that require it. See the WinCLAT FAQ for details.

Summary

IPv6-mostly networks allow capable devices to operate using IPv6 while retaining native IPv4 connectivity for devices that need it. DHCP option 108, NAT64, and 464XLAT work together to support this gradual transition toward IPv6-only networking.

Additional Information