464XLAT, CLAT and IPv6-mostly networks
Explain the CLAT and PLAT roles in 464XLAT and how they fix the DNS64 IPv4-literal gap (RFC 6877, RFC 8683). Signal IPv6-only to capable hosts with DHCPv4 option 108 and advertise PREF64 in RAs (RFC 8925, RFC 8781). Apply current guidance on discovering the NAT64 prefix (RFC 7050, RFC 9872).
Take the quiz · pass mark 70% · 9 questions
Explanation
NAT64/DNS64 (L6.04) breaks on two things: IPv4 literals (no DNS lookup to synthesise) and some IPv4-only socket apps. 464XLAT (RFC 6877) fixes this by adding a stateless translator on the client side.
CLAT and PLAT
464XLAT has two translators:
- The PLAT (Provider-side translator) is the stateful NAT64 in the network (L6.04).
- The CLAT (Customer-side translator) is a stateless SIIT (L6.03) on the client or CPE. It takes IPv4 packets the host still produces (including those to literals) and translates them to IPv6 addressed into the NAT64 prefix, so they reach the PLAT and then the IPv4 Internet.
The host keeps a working (often private) IPv4 interface for legacy apps, but no IPv4 runs on the link — only IPv6. RFC 8683 gives additional deployment guidance for NAT64/464XLAT, including when you need a CLAT versus plain NAT64/DNS64.
IPv6-mostly: option 108 and PREF64
On a shared LAN you do not want to force every host IPv6-only at once. DHCPv4 option 108 ("IPv6-Only Preferred", RFC 8925) lets a capable host tell the DHCPv4 server it is willing to run without IPv4; the server then withholds an IPv4 lease and the host goes IPv6-only (running a CLAT), while legacy hosts that do not understand option 108 still get IPv4 on the same segment. That is an IPv6-mostly network, and it drains toward IPv6-only without a flag day. Option 108 also carries a timer, V6ONLY_WAIT, whose minimum is 300 seconds (a host must treat smaller values as 300).
A CLAT needs to know the NAT64 prefix. The modern way is the PREF64 Router Advertisement option (RFC 8781), ND option type 38, which advertises the NAT64 prefix on the link so hosts learn it directly from RAs.
Discovering the NAT64 prefix
Before PREF64 in RAs, hosts discovered the prefix with RFC 7050, which resolves the special name ipv4only.arpa through the DNS64 resolver and infers the prefix from the synthesised AAAA. RFC 7050 still works, but RFC 9872 is the current guidance on prefix discovery and recommends preferring the RA PREF64 option where available and treating ipv4only.arpa as a fallback. Use PREF64 first, RFC 7050 as backup.
ictNetworks scenario
ictNetworks runs its corporate Wi-Fi as IPv6-mostly: the Kea DHCPv4 server honours option 108 so managed laptops go IPv6-only and run a CLAT, while a handful of legacy devices still receive IPv4. radvd advertises the PREF64 option so CLATs learn the NAT64 prefix from RAs (RFC 8781), with ipv4only.arpa (RFC 7050) as a fallback per RFC 9872. IPv4-literal apps keep working because the CLAT translates them to the PLAT.
Drawing diagram…
Worked examples
Example 1: The option that signals IPv6-only
A capable host includes DHCPv4 option 108 in its request; the server then withholds an IPv4 address and the host runs IPv6-only with a CLAT. Legacy hosts that omit option 108 still get IPv4. Option 108 is option number 108.
Example 2: The minimum wait timer
If a DHCPv4 server returns a V6ONLY_WAIT below the minimum, the host must clamp it to 300 seconds (RFC 8925), the minimum time before it retries IPv4.
Example 3: Learning the prefix from RAs
A CLAT reads the NAT64 prefix from the PREF64 Router Advertisement option, ND option type 38 (RFC 8781), rather than resolving ipv4only.arpa; RFC 9872 recommends preferring this RA method.
Lab
Goal: Build an IPv6-mostly LAN where IPv4-only applications still work through a CLAT.
You need: a topology with an IPv6-only uplink and a PLAT/NAT64 (Jool), a Kea DHCPv4 server configured for option 108, radvd advertising RAs with the PREF64 option, a CLAT (Jool SIIT or clatd) on a client, and an IPv4-only test app/literal. (All of Jool, Kea, radvd and clatd syntax vary by version — check the docs.)
- Bring up NAT64/DNS64 as the PLAT and confirm native IPv6 and NAT64 both work.
- Enable option 108 in Kea; show a capable client goes IPv6-only (no IPv4 lease) while a legacy client still gets IPv4 (IPv6-mostly).
- Advertise PREF64 in RAs with radvd; confirm the CLAT learns the NAT64 prefix from the RA (RFC 8781).
- Start the CLAT on the IPv6-only client; connect to an IPv4 literal and confirm it now works (the gap DNS64 could not fill).
- Disable PREF64 and show the CLAT falling back to
ipv4only.arpa(RFC 7050), per RFC 9872 guidance.
What to submit: the Kea/radvd/Jool/CLAT configuration, evidence of the IPv6-only vs legacy clients, the working IPv4-literal connection through the CLAT, and the prefix-discovery fallback demonstration.
Summary
- 464XLAT (RFC 6877) adds a stateless CLAT on the client to a stateful NAT64 PLAT, fixing IPv4 literals and IPv4-only apps.
- DHCPv4 option 108 (RFC 8925) makes capable hosts IPv6-only on a shared LAN (IPv6-mostly); its V6ONLY_WAIT minimum is 300 s.
- PREF64 in RAs (RFC 8781, ND option 38) advertises the NAT64 prefix to CLATs.
- Discover the prefix via PREF64 first, with
ipv4only.arpa(RFC 7050) as fallback, per RFC 9872; RFC 8683 gives deployment guidance. - Next lesson (L6.06): carrier transition — DS-Lite, MAP-E, MAP-T and CGNAT.
Quiz imported · 9 questions · pass mark 70%. Lab questions are not auto-marked.