ISP access networks: residential and business broadband
Design prefix delegation (/48 or /56) and a stable-prefix policy for broadband customers. Apply CPE requirements and renumbering behaviour (RFC 7084, RFC 9096). Plan reverse DNS and logging for delegated customer prefixes (RFC 8501).
Take the quiz · pass mark 70% · 9 questions
Explanation
An ISP's job in IPv6 is to delegate each customer a prefix, not a single address, so every home or business can number many subnets. The design choices are the delegation size, prefix stability, the CPE behaviour, and reverse DNS/logging.
Delegation size and stability
RFC 6177 (BCP 157) killed the old "one /48 for everyone or nothing" debate: give end sites enough space, typically a /48 for business and a /56 (or /48) for residential, never a single /64 — a single /64 cannot be subnetted and breaks DHCPv6-PD downstream. A /56 still yields 256 /64s, enough for any home.
Stability matters. A prefix that changes on every reconnect ("dynamic prefix") breaks internal addressing, firewall rules, DNS and PD to downstream routers. Prefer a stable prefix per customer, released only on explicit change. RFC 9096 gives current recommendations for how CE routers should react to prefix changes and renumbering events so a flapping or withdrawn prefix does not leave stale addresses in use.
CPE requirements (RFC 7084)
RFC 7084 is the baseline for an IPv6 customer edge router: it must do stateless address autoconfiguration on the WAN, request a prefix via DHCPv6 prefix delegation (DHCPv6-PD, RFC 9915), sub-delegate /64s to its LANs, run a stateful firewall (default-deny inbound, L5.05), and handle the WAN/LAN correctly. RFC 9096 updates the expected behaviour on renumbering. An ISP should test candidate CPE against these requirements before shipping it.
Reverse DNS and logging
Customers and mail servers expect PTR records. For delegated prefixes an ISP either auto-generates PTRs, delegates the ip6.arpa zone to the customer, or provides a wildcard/dynamic scheme — RFC 8501 describes the options for reverse DNS in IPv6 for ISPs. For abuse handling and lawful traceability the ISP must log which customer held which prefix and when (prefix, not just address), because a customer's addresses within their /56 are their own business.
ictNetworks scenario
ictNetworks (as ISP-A, AS64496, numbering customers from its documentation allocation 3fff:a00::/32) delegates a stable /56 per residential line and a /48 per business, via DHCPv6-PD from Kea, with CPE validated against RFC 7084/9096. It auto-generates reverse DNS for delegated /56s per RFC 8501 and logs the prefix-to-customer binding with timestamps for abuse response, never forcing a renumber except on explicit account change.
Drawing diagram…
Worked examples
Example 1: Subnets in a residential /56
A home delegated a /56 can create 2^(64-56) = 256 /64 subnets — far more than a household needs, and the reason a /56 (not a /64) is the residential minimum.
Example 2: How many customers fit in the allocation
From a /32 ISP allocation, giving each customer a /56 yields 2^(56-32) = 16777216 customer delegations — so address space is never the constraint on subscriber growth.
Example 3: Reverse-DNS boundary for a /56
A /56 is nibble-aligned: 56 / 4 = 14 hex nibbles of prefix are fixed in the ip6.arpa name, and the remaining 18 nibbles identify the host within the customer's space. The ISP delegates or generates PTRs at that 14-nibble boundary.
Lab
Goal: ISP-A delivers a stable /56 to a home CPE, and the CPE numbers two LANs from it.
You need: a containerlab topology with an ISP BNG running Kea (DHCPv6-PD), a CE router (RouterOS/ROS or Linux acting as CPE) and two LAN segments behind it; dhcp6c/Kea logs, tcpdump, and the ability to disconnect/reconnect. (Kea and ROS syntax vary by version — check the docs.)
- Configure Kea to delegate a stable /56 to the CPE (keyed on DUID/identifier) from 3fff:a00::/32.
- On the CPE, obtain the /56 by DHCPv6-PD and sub-delegate a /64 to each LAN; confirm hosts on both LANs autoconfigure.
- Reconnect the CPE and confirm it receives the same /56 (stable prefix); observe RFC 9096-style behaviour.
- Simulate a prefix change and confirm the CPE withdraws the old /64s and renumbers the LANs without leaving stale addresses.
- Generate/delegate reverse DNS for the /56 (RFC 8501) and verify a PTR; show the prefix-to-customer log entry with a timestamp.
What to submit: the Kea and CPE configuration, evidence of the two numbered LANs, the stable-prefix reconnect test, the renumbering behaviour, and the reverse-DNS + log evidence.
Summary
- Delegate a prefix, not an address: /48 for business, /56 (or /48) for residential, never a single /64 (RFC 6177).
- Prefer stable prefixes; CPE must meet RFC 7084 and react correctly to renumbering (RFC 9096) using DHCPv6-PD (RFC 9915).
- Provide reverse DNS for delegated prefixes (RFC 8501) and log the prefix-to-customer binding with time for abuse handling.
- A /56 gives 256 /64s and is nibble-aligned at 14 ip6.arpa nibbles.
- Next lesson (L7.02): mobile networks and IPv6.
Quiz imported · 9 questions · pass mark 70%. Lab questions are not auto-marked.