| Internet-Draft | IPv6 CE Routers LAN Prefix Delegation | August 2024 |
| Winters | Expires 8 February 2025 | [Page] |
This document defines requirements for IPv6 CE Routers to support DHCPv6 Prefix Delegation for redistributing any unused prefix(es) that were delegated to the IPv6 CE Router. This document updates RFC 7084.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 8 February 2025.¶
Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
This document defines DHCPv6 Prefix Delegation in IPv6 CE Routers ([RFC7084]) in order to properly utilize the IPv6 prefixes assigned by service providers. Many ISPs will assign a prefix larger then /64 to the CE Router, as recommended in [RFC6177]. If an IPv6 CE Router does not support IA_PD on the LAN it will not be able to assign any prefixes beyond its local interfaces, limiting the usefulness of assigning prefixes larger than /64 by the operator. Supporting IA_PD on the LAN interfaces will allow those unused prefixes to be distributed into a network. Work is being done in the areas such as Stub Networking Auto Configuration (SNAC) working group that depends on IPv6 prefixes being properly distibuted.¶
Two models, hierarchical prefix and flat, have been proposed in the past for prefix sub-delegation beyond the IPv6 CE Router. Hierarchical prefix delegation requires an IPv6 CE Router to sub delegate IPv6 prefixes based on set of rules. If more then one router uses hierarchical prefix delegation, a IPv6 prefix tree is created. When no routing protocol is present to discover the network topology, it's possible to have unbalanced prefix delegation tree which leads to running out of prefixes. For more information on heirachical prefix delegation is contained in Section 8.5 of CableLabs IPv6 eRouter Specifiction [eRouter]. A flat prefix delegation requires the router to be provisioned with the initial prefix and to assign /64 prefixes to all other prefix requests from routers downstream. As the default configuration is designed to be the flat model to support zero configuration networking.¶
The Home Networking working group producted solutions for prefix delegation for home networks, including [RFC7695]. The Home Networking solutions haven't been deployed by ISPs or IPv6 CE Routers since the publication partially due to their complexity.¶
This document does not cover dealing with multi-provisioned networks with more than one provider. Due to complexity of a solution that would require routing, provisioning and policy, this is out of scope of this document.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
This document also makes use of internal conceptual variables to describe protocol behavior and external variables that an implementation must allow system administrators to change. The specific variable names, how their values change, and how their settings influence protocol behavior are provided to demonstrate protocol behavior. An implementation is not required to have them in the exact form described here, as long as its external behavior is consistent with that described in this document.¶
The following terminology is defined for this document.¶
IPv6 CE Router: A router intended for home or small-office use that forwards packets not explicitly addressed to itself as defined in [RFC7084].¶
Internet Service Provider (ISP): An entity that provides access to the Internet. In this document, a service provider specifically offers Internet access using IPv6, and may also offer IPv4 Internet access. The service provider can provide such access over a variety of different transport methods such as DSL, cable, wireless, and others.¶
The end-user network that has IPv6 Customer Edge Routers with routers and hosts downstream. Figure 1 illustrates the model topology.¶
+-----------+
| Service |
| Provider |
| Router |
+-----+-----+
|
|
| Customer
| Internet Connection
|
+-----v-----+
| IPv6 |
| CE |
| Router |
+-----+-----+
|
+----+-+-------+
| |
| |
+---+----+ +-----+------+
| IPv6 | | |
| Host | | Router |
| | | |
+--------+ +------------+
The IPv6 CE Router distributes configuration information obtained during WAN interface provisioning to IPv6 hosts and routers. Previously, a router based on [RFC7084] would only provide IPv6 hosts with individual addresses; this update allows for addressing and routing of IPv6 prefixes to both hosts and routers.¶
The IPv6 CE Router MUST support a DHCPv6 server capable of IPv6 prefix assignment according to [RFC8415] (Identity Association for Prefix Delegation (IA_PD) option).¶
The IPv6 CE Router MUST assign a prefix from the delegated prefix as specified by L-2 [RFC7084]. If not enough addresses are available the IPv6 CE Router SHOULD log a system management error.¶
The prefix assigned to a link MUST NOT change in the absence of topology or configuration changes.¶
After LAN link prefix assignment the IPv6 CE Router MUST make the remaining IPv6 prefixes available to other routers via Prefix Delegation.¶
The IPv6 CE Router MUST install a route to the assigned IA_PD with a next-hop of the IPv6 node that was assigned the prefix. The IPv6 CE Router MUST remove the route when IA_PD lease expires.¶
By default, the IPv6 CE Router firewall MUST allow forwarding of packets with an outer IPv6 header containing a source address belonging to Delegated Prefixes, along with reciprocal packets from the same flow, following the recommendations of [RFC6092]¶
The IPv6 CE Router SHOULD by default provision IA_PD IA prefixes with a prefix-length of 64.¶
If the CE Router is configured to generate a ULA prefix as defined in ULA-1 of [RFC7084] after LAN link prefix assignment of the ULA prefixes the IPv6 CE Router MUST make the remaining IPv6 prefixes available to other routers via Prefix Delegation.¶
This document does not add any new security considerations beyond those mentioned in Section 4 of [RFC8213] and Section 22 of [RFC8415].¶
This document makes no request of IANA.¶
Thanks to the following people for their guidance and feedback: Marion Dillon, Erik Auerswald, Esko Dijk, Tim Carlin, Richard Patterson, Ted Lemon, Michael Richardson, Martin Huneki, Gabor Lencse, Ole Troan, Brian Carpenter, David Farmer, Tim Chown.¶