Network Working Group B. Liu
Internet Draft Huawei Technologies Co., Ltd
Intended status: Proposed Standard W. Wang
Expires: July 18, 2013 X. Gong
University of BUPT
January 15, 2013
DHCPv6/SLAAC Address Configuration Switching for Host Renumbering
draft-liu-6renum-dhcpv6-slaac-switching-02.txt
Status of this Memo
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 http://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 July 18, 2013.
Copyright Notice
Copyright (c) 2011 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
(http://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 Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Abstract
Bing Liu Expires July 18 2013 [Page 1]
Internet-Draft draft-liu-6renum-dhcpv6-slaac-switching January 2013
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.
Table of Contents
1. Introduction ................................................. 3
2. DHCPv6/SLAAC interaction ..................................... 3
2.1. Host behavior defined in standards ...................... 3
2.2. Test of desktop operating systems' behavior ............. 4
2.2.1. Test environment ................................... 4
2.2.2. Test scenarios and results ......................... 5
2.2.3. Conclusion ......................................... 6
3. Requirement of Address Configuration Switching in Renumbering. 6
4. Proposed Standard Update ..................................... 7
4.1. Adding a "DHCPv6Required" Flag .......................... 8
4.2. Adding a "ReleaseDHCPv6" Flag ........................... 8
4.3. Host Behavior of Interpreting D/R Flag .................. 8
5. Security Considerations ...................................... 9
6. IANA Considerations .......................................... 9
7. References ................................................... 9
7.1. Normative References .................................... 9
7.2. Informative References .................................. 9
8. Acknowledgments .............................................. 9
Authors' Addresses ............................................. 10
Bing Liu Expires July 18 2013 [Page 2]
Internet-Draft draft-liu-6renum-dhcpv6-slaac-switching January 2013
1. Introduction
In IPv6, both of the DHCPv6 [RFC3315] and Neighbor Discovery [RFC4861]
protocols can provide automatic IP address configuration for the
hosts. They are known as stateful address auto-configuration and
SLAAC (stateless address auto-configuration)[RFC4862], and are
suitable for different scenarios respectively.
Sometimes the two address configuration modes may be both available
in one network. This would add more or less additional complexity for
both the hosts and the network management. In ND protocol, there is a
datatracker.ietf.org