Skip to content
AdminKit

DS-Lite (Dual-Stack Lite)

What is DS-Lite (Dual-Stack Lite)?

Dual-Stack Lite (DS-Lite), defined in RFC 6333, lets an ISP run an IPv6-only access network while customers still reach the IPv4 internet, tunneling their traffic to a shared carrier-side NAT (AFTR) over IPv6. AdminKit's CGNAT guide compares this with ordinary carrier-grade NAT, which shares addresses without removing IPv4 from the access network.

By AdminKit team, Netbase JSC · Updated

Dual-Stack Lite (DS-Lite), defined in RFC 6333 (tracked on the IETF Datatracker alongside its working-group history), lets an ISP deploy an IPv6-only access network while its customers still reach the IPv4 internet, without needing to hand out a public IPv4 address to every household at all — one of the transition mechanisms NIST’s own IPv6 deployment guidelines cover. Each customer’s router (the B4 element) tunnels its IPv4 traffic inside IPv6 packets across the ISP’s IPv6-only network to a carrier-operated AFTR (Address Family Transition Router) — discovered via the DHCPv6 option RFC 6334 defines — which performs the actual NAT, translating that tunneled IPv4 traffic to a shared pool of public IPv4 addresses before it reaches the IPv4 internet. F5’s BIG-IP documentation on using DS-Lite with CGNAT describes the same split from an equipment vendor’s side: the B4 device at the customer premises encapsulates IPv4 packets inside IPv6 and sends them to the AFTR, which decapsulates the traffic and performs address translation before sending it to the external IPv4 network. This is a different approach from CGNAT, which keeps the access network itself running IPv4 and shares addresses with ordinary NAT at the carrier edge; DS-Lite instead removes IPv4 from the access network entirely and tunnels it only where needed, over an IPv6-only path. It also solves a different problem than 464XLAT, which translates between address families for a client that itself only has IPv6 available; DS-Lite’s B4 and AFTR exchange IPv4 packets over an IPv6 tunnel rather than translating the packets between protocols at all. Because every DS-Lite customer shares AFTR addresses the same way CGNAT customers share a NAT pool, it carries the same tradeoffs: shared blacklist exposure and no inbound reachability without an explicit port-mapping protocol.

DS-Lite (Dual-Stack Lite) is part of AdminKit’s IP & network cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

Does DS-Lite require handing out a public IPv4 address to every household?

No -- the whole point of DS-Lite is letting an ISP run an IPv6-only access network while customers still reach the IPv4 internet without one.

What tunnels the customer's IPv4 traffic to the AFTR?

The customer's router, the B4 element, tunnels its IPv4 traffic inside IPv6 packets across the ISP's IPv6-only network to the AFTR, which performs the actual NAT.

How is DS-Lite different from CGNAT?

CGNAT keeps the access network running IPv4 and shares addresses with ordinary NAT at the carrier edge, while DS-Lite removes IPv4 from the access network entirely and tunnels it only where needed, over an IPv6-only path.

Does DS-Lite support inbound connections to a customer's device?

Not without an explicit port-mapping protocol -- DS-Lite customers share AFTR addresses the same way CGNAT customers share a NAT pool, carrying the same no-inbound-reachability-by-default tradeoff.