Requirements for IPv6 Prefix Delegation (RFC3769)
Original Publication Date: 2004-Jun-01
Included in the Prior Art Database: 2004-Jun-17
Internet Society Requests For Comment (RFCs)
S. Miyakawa: AUTHOR [+2]
This document describes requirements for how IPv6 address prefixes should be delegated to an IPv6 subscriber's network (or "site").
Network Working Group S. Miyakawa
Request for Comments: 3769 NTT Communications Corporation
Category: Informational R. Droms
Requirements for IPv6 Prefix Delegation
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright (C) The Internet Society (2004).
This document describes requirements for how IPv6 address prefixes
should be delegated to an IPv6 subscriber's network (or "site").
With the deployment of IPv6 , several Internet Service Providers
are ready to offer IPv6 access to the public. In conjunction with
widely deployed "always on" media such as ADSL and the expectation
that customers will be assigned a /48 IPv6 unicast address prefix
(see RFC 3513  and section 3 of RFC 3177 ), an efficient
mechanism for delegating address prefixes to the customer's sites is
needed. The delegation mechanism will be intended to automate the
process of informing the customer's networking equipment of the
prefixes to be used at the customer's site.
This document clarifies the requirements for IPv6 address prefix
delegation from the ISP to the site.
Miyakawa & Droms Informational [Page 1]
RFC 3769 Requirements IPv6 Prefix Delegation June 2004
2. Scenario and terminology
The following figure illustrates a likely example for the
organization of a network providing subscription IPv6 service:
/ \ /
+---------------+ +--------+/ \------/
|ISP Edge Router|Point-to-point|Customer+
| +--------------+ Router | Customer networks
| (PE) | link | (CPE) +