draft-ietf-dhc-dhcpv6-reconfigure-rebind-08.txt   draft-ietf-dhc-dhcpv6-reconfigure-rebind-09.txt 
Network Working Group D. Evans Network Working Group D. Evans
Internet-Draft ARRIS International, Inc. Internet-Draft ARRIS International, Inc.
Intended status: Standards Track R. Droms Intended status: Standards Track R. Droms
Updates: 3315 Cisco Systems, Inc. Updates: 3315 Cisco Systems, Inc.
Expires: February 23, 2012 S. Jiang Expires: June 18, 2012 S. Jiang
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
August 22, 2011 December 16, 2011
Rebind Capability in DHCPv6 Reconfigure Messages Rebind Capability in DHCPv6 Reconfigure Messages
draft-ietf-dhc-dhcpv6-reconfigure-rebind-08.txt draft-ietf-dhc-dhcpv6-reconfigure-rebind-09.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.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. 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."
This Internet-Draft will expire on February 23, 2012. This Internet-Draft will expire on June 18, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 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
skipping to change at page 4, line 18 skipping to change at page 4, line 18
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. If the client sends a Renew message, it includes a Server message. If the client sends a Renew message, it includes a Server
Identifier option in the Renew message to specify the server that Identifier option in the Renew message to specify the server that
should respond to the Renew message. The RFC 3315 specification is should respond to the Renew message. The RFC 3315 specification is
only suitable for the scenarios that client would communicate with only suitable for the scenarios that client would communicate with
the same DHCPv6 servers. the same DHCPv6 servers.
There are also scenarios that the client may desire to communicate There are also scenarios that the client must communicate with a
with a different server: for example, a network administrator may different server: for example, a network administrator may choose to
initiatively want to shut down a DHCPv6 server and move these clients shut down a DHCPv6 server and move these clients who most recently
who most recently communicated with to another different server. communicated with it to another different server. Hence, this
Hence, this document expands the allowed values of the msg-type field document expands the allowed values of the msg-type field with in
with in reconfiguration message to allow the server to indicate the reconfiguration message to allow the server to indicate the client to
client to send a Rebind message, which does not include a Server send a Rebind message, which does not include a Server Identifier
Identifier option and allows any server to respond to the client. 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.
skipping to change at page 8, line 9 skipping to change at page 8, line 9
[I-D.ietf-dhc-secure-dhcpv6] [I-D.ietf-dhc-secure-dhcpv6]
Jiang, S. and S. Shen, "Secure DHCPv6 Using CGAs", Jiang, S. and S. Shen, "Secure DHCPv6 Using CGAs",
draft-ietf-dhc-secure-dhcpv6-03 (work in progress), draft-ietf-dhc-secure-dhcpv6-03 (work in progress),
June 2011. June 2011.
Authors' Addresses Authors' Addresses
D. R. Evans D. R. Evans
ARRIS International, Inc. ARRIS International, Inc.
7912 Fairview Road IPfonix, Inc., 330 WCR 16 1/2
Boulder, CO 80303 Longmont, CO 80504-9467
USA USA
Phone: +1 303.494.0394 Phone: +1 303.682.2412
Email: N7DR@arrisi.com Email: N7DR@ipfonix.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
 End of changes. 7 change blocks. 
16 lines changed or deleted 16 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/