draft-ietf-dhc-dhcpv6-reconfigure-rebind-02.txt   draft-ietf-dhc-dhcpv6-reconfigure-rebind-03.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 16, 2008 Cisco Systems, Inc. Expires: June 6, 2008 Cisco Systems, Inc.
November 13, 2007 December 4, 2007
Rebind Capability in DHCPv6 Reconfigure Messages Rebind Capability in DHCPv6 Reconfigure Messages
draft-ietf-dhc-dhcpv6-reconfigure-rebind-02.txt draft-ietf-dhc-dhcpv6-reconfigure-rebind-03.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 16, 2008. This Internet-Draft will expire on June 6, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document updates 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. The document also clarifies
how a DHCPv6 client responds to a received Reconfigure message.
1. Introduction 1. Introduction
DHCPv6 [RFC3315] allows a server to send an unsolicited Reconfigure DHCPv6 [RFC3315] allows a server to send an unsolicited Reconfigure
message 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 [RFC3315] is either a Renew or an Information-Request according to section 19 of RFC3315 is either a Renew or an
message, depending on the contents of the msg-type field in the Information-Request message, depending on the contents of the msg-
Reconfigure Message option of the Reconfigure message. type field in the Reconfigure Message option of 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
last obtained configuration and/or addressing information. If the
Reconfigure message commands the client to perform a Renew, [RFC3315]
does not specify to which server the client should send the Renew.
This difficulty is avoided if the server commands the client to
perform an Information-Request, since such messages are multicast.
However, Information-Request messages do not cause addressing
configuration to be returned.
This document expands the allowed values of the msg-type field to If the client sends a Renew message, it includes a Server Identifier
allow the server to indicate that the client is to attempt to perform option in the Renew message to specify the server that should respond
a Rebind; since Rebind messages are multicast, this avoids the to the Renew message. Under some circumstances, it may be desirable
necessity of the client contacting a particular server. Rebind for the client to communicate with a different server; for example,
messages also cause all configuration information, including if the server that the client most recently communicated with is no
addresses, to be returned from a server. longer available, the network administrator may want the client to
communicate with a different server. This document expands the
allowed values of the msg-type field to allow the server to indicate
that the client is to send a Rebind message, which does not include a
Server Identifier option and allows any server to respond to the
client.
This document updates section 19 of RFC 3315. RFC 3315 does not specify that a Reconfigure message must be sent
from the server with which the client most recently communicated, and
it does not specify which server the client should identify with a
Server Identifier option when the client responds to the Reconfigure
message. This document clarifies that the client should send a Renew
message in response to a Reconfigure message with a Server Identifier
option identifying the same server that the client would have
identified if the client had sent the Renew message after expiration
of T1.
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 [RFC2119]. interpreted as described in [RFC2119].
This document uses IPv6 and DHCPv6 terms as defined in section 4 of
RFC 3315.
3. The Reconfigure Message option of the DHCPv6 Reconfigure Message 3. The Reconfigure Message option of the DHCPv6 Reconfigure Message
This section modifies section 22.19 of RFC 3315 to allow the
specification of the Rebind message in a 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
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_RECONF_MSG | option-len | | OPTION_RECONF_MSG | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| msg-type | | msg-type |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
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. Server Behavior
This section updates specific text in sections 19.1, 19.2 and 19.3 of
RFC 3315.
The server MUST include a Reconfigure Message option (as defined in
Section 3 to select whether the client responds with a Renew message,
a Rebind message or an Information-Request message.
The Reconfigure message causes the client to initiate a Renew/Reply,
a Rebind/Reply message exchange or an Information-request/Reply
message exchange. The server interprets the receipt of a Renew, a
Rebind or an Information-request message (whichever was specified in
the original Reconfigure message) from the client as satisfying the
Reconfigure message request.
The server retransmits a Reconfigure message specifying a Rebind
message in the same way as described in section 19.1.2 of RFC 3315.
In response to a Rebind message, the server generates and sends a
Reply message to the client as described in sections 18.2.4 and
18.2.8, including options for configuration parameters.
The server MAY include options containing the IAs and new values for
other configuration parameters in the Reply message, even if those
IAs and parameters were not requested in the Renew message from the
client.
4.1. Client Behavior
This section updates specific text in section 19.4 of RFC 3315.
Upon receipt of a valid Reconfigure message, the client responds with
a Renew message, a Rebind message or an Information-request message
as indicated by the Reconfigure Message option (as defined in
Section 3). The client ignores the transaction-id field in the
received Reconfigure message. While the transaction is in progress,
the client silently discards any Reconfigure messages it receives.
When responding to a Reconfigure, the client creates and sends the
Rebind message in exactly the same manner as outlined in section
18.1.4 of RFC 3315, with the exception that the client copies the
Option Request option and any IA options from the Reconfigure message
into the Renew message.
The client uses the same variables and retransmission algorithm as it
does with Renew, Rebind or Information-request messages generated as
part of a client-initiated configuration exchange. See sections
18.1.3, 18.1.4 and 18.1.5 of RFC 3315for details. If the client does
not receive a response from the server by the end of the
retransmission process, the client ignores and discards the
Reconfigure message.
5. Clarification of section 19.4.2, RFC 3315
When sending a Renew message in response to the receipt of a
Reconfigure message, the client MUST include a Server Identifier
option identifying the server the client most recently communicated
with.
6. Security Considerations
This document adds no new security considerations beyond those This document adds no new security considerations beyond those
present in [RFC3315]. present in RFC 3315.
5. IANA Considerations 7. 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 8. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
Authors' Addresses Authors' Addresses
 End of changes. 13 change blocks. 
29 lines changed or deleted 100 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/