draft-ietf-dhc-dhcpv6-reconfigure-rebind-01.txt   draft-ietf-dhc-dhcpv6-reconfigure-rebind-02.txt 
Network Working Group D. Evans Network Working Group D. Evans
Internet-Draft ARRIS International, Inc. Internet-Draft ARRIS International, Inc.
Intended status: Informational R. Droms Intended status: Informational R. Droms
Expires: May 20, 2007 Cisco Systems, Inc. Expires: May 16, 2008 Cisco Systems, Inc.
November 16, 2006 November 13, 2007
Rebind Capability in DHCPv6 Reconfigure Messages Rebind Capability in DHCPv6 Reconfigure Messages
draft-ietf-dhc-dhcpv6-reconfigure-rebind-01.txt draft-ietf-dhc-dhcpv6-reconfigure-rebind-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 35
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 20, 2007. This Internet-Draft will expire on May 16, 2008.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document updtaes RFC 3315 to allow the Rebind message type to This document updates RFC 3315 to allow the Rebind message type to
appear in the Reconfigure Message option of a Reconfigure message, appear in the Reconfigure Message option of a Reconfigure message,
which allows DHCPv6 servers to instruct clients to perform a Rebind which allows DHCPv6 servers to instruct clients to perform a Rebind
operation as well as a Renew operation. operation as well as a Renew operation.
1. Introduction 1. Introduction
DHCPv6 [2] allows a server to send an unsolicited Reconfigure message DHCPv6 [RFC3315] allows a server to send an unsolicited Reconfigure
to a client. The client's response to a Reconfigure message, message to a client. The client's response to a Reconfigure message,
according to [2] is either a Renew or an Information-Request message, according to [RFC3315] is either a Renew or an Information-Request
depending on the contents of the msg-type field in the Reconfigure message, depending on the contents of the msg-type field in the
Message option of the Reconfigure message. Reconfigure Message option of the Reconfigure message.
In a network with multiple DHCPv6 servers, the Reconfigure message In a network with multiple DHCPv6 servers, the Reconfigure message
may not be sent by the same server as the one from which the client may not be sent by the same server as the one from which the client
last obtained configuration and/or addressing information. If the last obtained configuration and/or addressing information. If the
Reconfigure message commands the client to perform a Renew, [2] does Reconfigure message commands the client to perform a Renew, [RFC3315]
not specify to which server the client should send the Renew. This does not specify to which server the client should send the Renew.
difficulty is avoided if the server commands the client to perform an This difficulty is avoided if the server commands the client to
Information-Request, since such messages are multicast. However, perform an Information-Request, since such messages are multicast.
Information-Request messages do not cause addressing configuration to However, Information-Request messages do not cause addressing
be returned. configuration to be returned.
This document expands the allowed values of the msg-type field to This document expands the allowed values of the msg-type field to
allow the server to indicate that the client is to attempt to perform allow the server to indicate that the client is to attempt to perform
a Rebind; since Rebind messages are multicast, this avoids the a Rebind; since Rebind messages are multicast, this avoids the
necessity of the client contacting a particular server. Rebind necessity of the client contacting a particular server. Rebind
messaegs also cause all configuration information, including messages also cause all configuration information, including
addresses, to be returned from a server. addresses, to be returned from a server.
This document updates section 19 of RFC 3315. This document updates section 19 of RFC 3315.
2. Terminology 2. Terminology
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be
interpreted as described in [1]. interpreted as described in [RFC2119].
3. The Reconfigure Message option of the DHCPv6 Reconfigure Message 3. The Reconfigure Message option of the DHCPv6 Reconfigure Message
A server includes a Reconfigure Message option in a Reconfigure A server includes a Reconfigure Message option in a Reconfigure
message to indicate to the client whether the client responds with a message to indicate to the client whether the client responds with a
Renew, an Information-request, or a Rebind message. Renew, an Information-request, or a Rebind message.
The format of this option is: The format of this option is:
0 1 2 3 0 1 2 3
skipping to change at page 3, line 23 skipping to change at page 3, line 23
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
option-code OPTION_RECONF_MSG (19). option-code OPTION_RECONF_MSG (19).
option-len 1. option-len 1.
msg-type 5 for Renew message, 6 for Rebind, 11 for msg-type 5 for Renew message, 6 for Rebind, 11 for
Information-request message. Information-request message.
4. Security Considerations 4. Security Considerations
This document adds no new security considerations beyond those This document adds no new security considerations beyond those
present in [2]. present in [RFC3315].
5. IANA Considerations 5. IANA Considerations
There are no actions for IANA associated with this document. There are no actions for IANA associated with this document.
6. Normative References 6. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[2] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", and M. Carney, "Dynamic Host Configuration Protocol for
RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
Authors' Addresses Authors' Addresses
D. R. Evans D. R. Evans
ARRIS International, Inc. ARRIS International, Inc.
7912 Fairview Road 7912 Fairview Road
Boulder, CO 80303 Boulder, CO 80303
USA USA
Phone: +1 303.494.0394 Phone: +1 303.494.0394
skipping to change at page 5, line 7 skipping to change at page 5, line 7
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Avenue 1414 Massachusetts Avenue
Boxborough, MA 01719 Boxborough, MA 01719
USA USA
Phone: +1 978.936.1674 Phone: +1 978.936.1674
Email: rdroms@cisco.com Email: rdroms@cisco.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
 End of changes. 14 change blocks. 
30 lines changed or deleted 30 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/