Mobile networks and IPv6
Explain 3GPP PDN/PDU connection types and the one-/64-per-UE model (RFC 6459). Describe IPv6-only mobile access with 464XLAT (RFC 6877). Apply the IPv6 profile for 3GPP mobile devices (RFC 7849).
Take the quiz · pass mark 70% · 9 questions
Explanation
Mobile networks are the largest IPv6 deployments in the world. Understanding them explains why the mobile industry went IPv6-only years before most fixed networks.
3GPP connectivity and the /64 per UE (RFC 6459)
RFC 6459 describes how IPv6 works in 3GPP. A mobile device (the UE) establishes a bearer (a PDP context in older terminology, a PDN/PDU session in LTE/5G) with a PDN type: IPv4, IPv6, or IPv4v6 (dual stack). For IPv6, the network assigns a whole /64 to each UE — not a single address — via the Router Advertisement on that bearer. The UE forms its address with SLAAC inside that /64; the /64 is dedicated to that one device, which simplifies accounting and isolates subscribers.
IPv6-only mobile with 464XLAT (RFC 6877)
Because each UE is its own /64 and the operator has huge subscriber counts, running dual stack doubles the control-plane and still needs IPv4 per session. Mobile operators therefore run the bearer IPv6-only and provide IPv4 reachability with 464XLAT (L6.05): a CLAT on the handset translates the apps' IPv4 (and IPv4 literals) to IPv6, and a PLAT (stateful NAT64) in the core reaches the IPv4 Internet. This is why an IPv6-only PDU session still runs legacy IPv4 apps.
The device profile (RFC 7849)
RFC 7849 is an IPv6 profile for 3GPP mobile devices: the set of features a handset should support to work well on modern mobile networks — IPv6 and IPv4v6 PDN types, correct RA/SLAAC handling, a working CLAT for 464XLAT, DNS over IPv6, privacy addresses, and so on. Operators use it as a procurement and certification checklist, much as RFC 7084 is used for CPE.
ictNetworks scenario
ictNetworks' mobile arm runs IPv6-only PDU sessions, assigning a /64 per UE from its documentation space, with a PLAT (NAT64) in the core and CLAT on certified handsets (checked against RFC 7849) so IPv4-only apps and literals keep working via 464XLAT. Dual-stack (IPv4v6) bearers are offered only to devices that need them, and the network reports the share of traffic staying native IPv6 versus translated.
Drawing diagram…
Worked examples
Example 1: What one UE receives
A UE on an IPv6 bearer is assigned a full /64, giving it 2^64 = 18446744073709551616 addresses of its own. The UE uses SLAAC within that /64; no other subscriber shares it.
Example 2: Subscribers per operator block
Assigning a /64 per UE from a /32 operator block supports 2^(64-32) = 4294967296 UEs — ample for any carrier, which is why the per-UE /64 model is affordable.
Example 3: The IPv4 floor still applies
Even on an IPv6-only bearer, the path must carry the IPv6 minimum link MTU of 1280 bytes end to end, so the CLAT and PLAT must preserve PMTUD for the translated IPv4 traffic.
Lab
Goal: Emulate an IPv6-only mobile client with a CLAT behind a NAT64 PLAT and test common apps.
You need: a containerlab topology emulating an IPv6-only "bearer" (a /64 per client), a PLAT (Jool NAT64), a CLAT on the client (Jool SIIT or clatd), a DNS64 resolver, and IPv4-only and dual-stack test services. (Jool/clatd/resolver syntax varies by version — check the docs.)
- Bring up the IPv6-only "bearer" and confirm the client gets a /64 and native IPv6 works.
- Deploy the PLAT (NAT64) and DNS64; confirm the client reaches an IPv4-only service by name.
- Start the CLAT on the client and reach an IPv4 literal (the 464XLAT case apps rely on).
- Test a representative set of "apps" (DNS-based and literal-based) and record which rely on the CLAT.
- Check the client against RFC 7849 profile points you can emulate (IPv6 PDN type, SLAAC, CLAT, DNS over IPv6) and note any gaps.
What to submit: the PLAT/CLAT/DNS64 configuration, evidence of native IPv6 and 464XLAT working, the per-app table, and the RFC 7849 profile check.
Summary
- 3GPP assigns a whole /64 per UE on an IPv6 bearer; PDN types are IPv4, IPv6 or IPv4v6 (RFC 6459).
- Mobile networks run IPv6-only with 464XLAT (CLAT on the handset, PLAT/NAT64 in the core) to carry IPv4 apps (RFC 6877).
- RFC 7849 is the IPv6 device profile operators use to certify handsets.
- The 1280-byte IPv6 MTU floor must hold end to end for translated traffic.
- Next lesson (L7.03): enterprise deployment planning.
Quiz imported · 9 questions · pass mark 70%. Lab questions are not auto-marked.