IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6
RFC 3633
| Document | Type |
RFC - Proposed Standard
(December 2003; Errata)
Obsoleted by RFC 8415
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text pdf htmlized with errata bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 3633 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Thomas Narten | ||
| IESG note | 2003-12-18: RFC 3633 published. | ||
| Send notices to | (None) | ||
Network Working Group O. Troan
Request for Comments: 3633 R. Droms
Category: Standards Track Cisco Systems
December 2003
IPv6 Prefix Options for
Dynamic Host Configuration Protocol (DHCP) version 6
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
The Prefix Delegation options provide a mechanism for automated
delegation of IPv6 prefixes using the Dynamic Host Configuration
Protocol (DHCP). This mechanism is intended for delegating a long-
lived prefix from a delegating router to a requesting router, across
an administrative boundary, where the delegating router does not
require knowledge about the topology of the links in the network to
which the prefixes will be assigned.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. DHCPv6 specification dependency . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Model and Applicability . . . . . . . . . . . . . . . . . . 3
5.1. Example network architecture . . . . . . . . . . . . . 4
6. Identity Association for Prefix Delegation . . . . . . . . . 5
7. Overview of DHCP with Prefix Delegation . . . . . . . . . . 6
8. Interface Selection . . . . . . . . . . . . . . . . . . . . 7
9. Identity Association for Prefix Delegation Option . . . . . 7
10. IA_PD Prefix option . . . . . . . . . . . . . . . . . . . . 9
11. Delegating Router Solicitation . . . . . . . . . . . . . . . 11
11.1. Requesting router behavior . . . . . . . . . . . . . . 11
11.2. Delegating router behavior . . . . . . . . . . . . . . 11
12. Requesting router initiated prefix delegation . . . . . . . 12
Troan & Droms Standards Track [Page 1]
RFC 3633 IPv6 Prefix Options for DHCPv6 December 2003
12.1. Requesting router behavior . . . . . . . . . . . . . . 12
12.2. Delegating Router behavior . . . . . . . . . . . . . . 14
13. Prefix Delegation reconfiguration . . . . . . . . . . . . . 15
13.1. Delegating Router behavior . . . . . . . . . . . . . . 15
13.2. Requesting Router behavior . . . . . . . . . . . . . . 15
14. Relay agent behavior . . . . . . . . . . . . . . . . . . . . 15
15. Security Considerations . . . . . . . . . . . . . . . . . . 16
16. IANA Considerations . . . . . . . . . . . . . . . . . . . . 16
17. Intellectual Property Statement. . . . . . . . . . . . . . . 17
18. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
18.1. Normative References . . . . . . . . . . . . . . . . . 17
18.2. Informative References . . . . . . . . . . . . . . . . 17
19. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18
20. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 18
21. Full Copyright Statement . . . . . . . . . . . . . . . . . . 19
1. Introduction
This document describes new options for Dynamic Host Configuration
Protocol (DHCP) that provide a mechanism for the delegation of IPv6
prefixes [1]. Through these options, a delegating router can
delegate prefixes to authorized requesting routers.
The prefix delegation mechanism described in this document is
intended for simple delegation of prefixes from a delegating router
to requesting routers. It is appropriate for situations in which the
delegating router does not have knowledge about the topology of the
networks to which the requesting router is attached, and the
delegating router does not require other information aside from the
identity of the requesting router to choose a prefix for delegation.
For example, these options would be used by a service provider to
assign a prefix to a Customer Premise Equipment (CPE) device acting
as a router between the subscriber's internal network and the service
provider's core network.
Many applications expect stable addresses. Even though this
mechanism makes automatic renumbering easier, it is expected that
prefixes have a long lifespan. During renumbering it is expected
that the old and the new prefix co-exist for some time.
The design of this prefix delegation mechanism meets the requirements
Show full document text