draft-ietf-dhc-dhcpv6-reconfigure-rebind-07.txt   draft-ietf-dhc-dhcpv6-reconfigure-rebind-08.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: Standards Track R. Droms
Expires: May 12, 2010 Cisco Systems, Inc. Updates: 3315 Cisco Systems, Inc.
November 8, 2009 Expires: February 23, 2012 S. Jiang
Huawei Technologies Co., Ltd
August 22, 2011
Rebind Capability in DHCPv6 Reconfigure Messages Rebind Capability in DHCPv6 Reconfigure Messages
draft-ietf-dhc-dhcpv6-reconfigure-rebind-07.txt draft-ietf-dhc-dhcpv6-reconfigure-rebind-08.txt
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 extends the Reconfigure message to allow a DHCPv6 server to which extends the Reconfigure message to allow a DHCPv6 server to
cause a DHCPv6 client to send a Rebind message. The document also cause a DHCPv6 client to send a Rebind message. The document also
clarifies how a DHCPv6 client responds to a received Reconfigure clarifies how a DHCPv6 client responds to a received Reconfigure
message. message.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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 This Internet-Draft will expire on February 23, 2012.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 12, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. The Reconfigure Message option of the DHCPv6 Reconfigure
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Clarification of section 19.4.2, RFC 3315 . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
9. Change log [RFC Editor please remove] . . . . . . . . . . . . . 7
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
10.1. Normative References . . . . . . . . . . . . . . . . . . . 7
10.2. Informative References . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
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 section 19 of RFC 3315 is either a Renew or an according to section 19 of RFC 3315 is either a Renew or an
Information-Request message, depending on the contents of the msg- Information-Request message, depending on the contents of the msg-
type field in the Reconfigure Message option of the Reconfigure type field in the Reconfigure Message option of the Reconfigure
message. message. If the client sends a Renew message, it includes a Server
Identifier option in the Renew message to specify the server that
should respond to the Renew message. The RFC 3315 specification is
only suitable for the scenarios that client would communicate with
the same DHCPv6 servers.
If the client sends a Renew message, it includes a Server Identifier There are also scenarios that the client may desire to communicate
option in the Renew message to specify the server that should respond with a different server: for example, a network administrator may
to the Renew message. Under some circumstances, it may be desirable initiatively want to shut down a DHCPv6 server and move these clients
for the client to communicate with a different server; for example, who most recently communicated with to another different server.
if the server that the client most recently communicated with is no Hence, this document expands the allowed values of the msg-type field
longer available, the network administrator may want the client to with in reconfiguration message to allow the server to indicate the
communicate with a different server. This document expands the client to send a Rebind message, which does not include a Server
allowed values of the msg-type field to allow the server to indicate Identifier option and allows any server to respond to the client.
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.
RFC 3315 does not specify that a Reconfigure message must be sent RFC 3315 does not specify that a Reconfigure message must be sent
from the server with which the client most recently communicated, and from the server with which the client most recently communicated, and
it does not specify which server the client should identify with a it does not specify which server the client should identify with a
Server Identifier option when the client responds to the Reconfigure Server Identifier option when the client responds to the Reconfigure
message. This document clarifies that the client should send a Renew message. This document clarifies that the client should send a Renew
message in response to a Reconfigure message with a Server Identifier message in response to a Reconfigure message with a Server Identifier
option identifying the same server that the client would have option identifying the same server that the client would have
identified if the client had sent the Renew message after expiration identified if the client had sent the Renew message after expiration
of T1. 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 NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
This document uses IPv6 and DHCPv6 terms as defined in section 4 of This document uses IPv6 and DHCPv6 terms as defined in section 4 of
RFC 3315. [RFC3315].
3. The Reconfigure Message option of the DHCPv6 Reconfigure 3. The Reconfigure Message option of the DHCPv6 Reconfigure Message
Message
This section modifies section 22.19 of RFC 3315 to allow the This section modifies section 22.19 of RFC 3315 to allow the
specification of the Rebind message in a Reconfigure message. 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:
skipping to change at page 4, line 14 skipping to change at page 6, line 5
In response to a Rebind message, the server generates and sends a 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 Reply message to the client as described in sections 18.2.4 and
18.2.8, including options for configuration parameters. 18.2.8, including options for configuration parameters.
The server MAY include options containing the IAs and new values for The server MAY include options containing the IAs and new values for
other configuration parameters in the Reply message, even if those other configuration parameters in the Reply message, even if those
IAs and parameters were not requested in the Renew message from the IAs and parameters were not requested in the Renew message from the
client. client.
4.1. Client Behavior 5. Client Behavior
This section updates specific text in section 19.4 of RFC 3315. This section updates specific text in section 19.4 of RFC 3315.
Upon receipt of a valid Reconfigure message, the client responds with Upon receipt of a valid Reconfigure message, the client responds with
a Renew message, a Rebind message or an Information-request message a Renew message, a Rebind message or an Information-request message
as indicated by the Reconfigure Message option (as defined in as indicated by the Reconfigure Message option (as defined in
Section 3). The client ignores the transaction-id field in the Section 3). The client ignores the transaction-id field in the
received Reconfigure message. While the transaction is in progress, received Reconfigure message. While the transaction is in progress,
the client silently discards any Reconfigure messages it receives. the client silently discards any Reconfigure messages it receives.
skipping to change at page 4, line 43 skipping to change at page 6, line 34
Reconfigure messages. Reconfigure messages.
The client uses the same variables and retransmission algorithm as it The client uses the same variables and retransmission algorithm as it
does with Renew, Rebind or Information-request messages generated as does with Renew, Rebind or Information-request messages generated as
part of a client-initiated configuration exchange. See sections part of a client-initiated configuration exchange. See sections
18.1.3, 18.1.4 and 18.1.5 of RFC 3315 for details. If the client 18.1.3, 18.1.4 and 18.1.5 of RFC 3315 for details. If the client
does not receive a response from the server by the end of the does not receive a response from the server by the end of the
retransmission process, the client ignores and discards the retransmission process, the client ignores and discards the
Reconfigure message. Reconfigure message.
5. Clarification of section 19.4.2, RFC 3315 6. Clarification of section 19.4.2, RFC 3315
When sending a Renew message in response to the receipt of a When sending a Renew message in response to the receipt of a
Reconfigure message, the client MUST include a Server Identifier Reconfigure message, the client MUST include a Server Identifier
option identifying the server the client most recently communicated option identifying the server the client most recently communicated
with. with.
6. Security Considerations 7. Security Considerations
This document adds no new security considerations beyond those This document allows the Rebind message type to appear in the
present in RFC 3315. Reconfigure Message option of a Reconfigure message so that the
client rebinds to a different DHCPv6 server. A malicious attacker
may use a faked Reconfigure message to force the client to disconnect
from the current server and relink to a faked server by quickly
responding to the client's Rebind message. These attacks may be
prevented by using the AUTH option [RFC3315] or Secure DHCPv6
[I-D.ietf-dhc-secure-dhcpv6].
7. IANA Considerations 8. IANA Considerations
There are no actions for IANA associated with this document. There are no actions for IANA associated with this document.
8. Change log 9. Change log [RFC Editor please remove]
This section MUST be removed before publication.
8.1. Revision -05 Revision -05
Clarified description of this feature in introduction. Clarified description of this feature in introduction.
Clarified action of client if it receives a Reconfigure while sending Clarified action of client if it receives a Reconfigure while sending
Rebind messages. Rebind messages.
8.2. Revision -06 Revision -08
Corrected a minor typo, changing "RFC3315" to "RFC 3315" in section
1.
8.3. Revision -07 Add a new co-author. Refreshed expired draft. Refine the motivation
and suitable scenarios, also add some new security considerations.
Correct the intended status to standard track
Refreshed expired draft, no material changes. 10. References
9. Normative References 10.1. 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.
10.2. Informative References
[I-D.ietf-dhc-secure-dhcpv6]
Jiang, S. and S. Shen, "Secure DHCPv6 Using CGAs",
draft-ietf-dhc-secure-dhcpv6-03 (work in progress),
June 2011.
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
Email: N7DR@arrisi.com Email: N7DR@arrisi.com
Ralph Droms Ralph Droms
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
Sheng Jiang
Huawei Technologies Co., Ltd
Huawei Building, No.3 Xinxi Rd.,
Shang-Di Information Industry Base, Hai-Dian District, Beijing
P.R. China
Email: jiangsheng@huawei.com
 End of changes. 25 change blocks. 
52 lines changed or deleted 87 lines changed or added

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