DHCPv6/SLAAC Address Configuration Switching for Host Renumbering
draft-liu-6renum-dhcpv6-slaac-switching-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Bing Liu , Wendong Wang , Xiangyang Gong | ||
| Last updated | 2013-07-29 (Latest revision 2013-01-14) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Sometimes stateful DHCPv6 address configuration and SLAAC may be both available in one network. In ND protocol, there is a "M" (ManagedFlag) flag defined in RA message, which indicates the hosts the DHCPv6 service is available. But for some reason, the ND protocol didn't define the flag as prescriptive but only advisory. This draft proposes to use two reserved bits in RA message to let the network control the hosts that which address configuration mode should be used. This feature is useful for management, especially in a renumbering event.
Authors
Bing Liu
Wendong Wang
Xiangyang Gong
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)