draft-ietf-dhc-dhcpv6-reconfigure-rebind-10.txt   rfc6644.txt 
Network Working Group D. Evans Internet Engineering Task Force (IETF) D. Evans
Internet-Draft ARRIS International, Inc. Request for Comments: 6644 IPfonix, Inc.
Intended status: Standards Track R. Droms Updates: 3315 R. Droms
Updates: 3315 Cisco Systems, Inc. Category: Standards Track Cisco Systems, Inc.
Expires: October 18, 2012 S. Jiang ISSN: 2070-1721 S. Jiang
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
April 16, 2012 July 2012
Rebind Capability in DHCPv6 Reconfigure Messages Rebind Capability in DHCPv6 Reconfigure Messages
draft-ietf-dhc-dhcpv6-reconfigure-rebind-10.txt
Abstract Abstract
This document updates RFC 3315 (DHCPv6) to allow the Rebind message This document updates RFC 3315 (DHCPv6) to allow the Rebind message
type to appear in the Reconfigure Message option of a Reconfigure type to appear in the Reconfigure Message option of a Reconfigure
message. It extends the Reconfigure message to allow a DHCPv6 server message. It extends the Reconfigure message to allow a DHCPv6 server
to cause a DHCPv6 client to send a Rebind message. The document also to 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 in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This is an Internet Standards Track document.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by
material or to cite them other than as "work in progress." the Internet Engineering Steering Group (IESG). Further
information on Internet Standards is available in Section 2 of
RFC 5741.
This Internet-Draft will expire on October 18, 2012. Information about the current status of this document, any
errata, and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6644.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 3, line 7 skipping to change at page 2, line 34
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction ....................................................3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology .....................................................3
3. The Reconfigure Message option of the DHCPv6 Reconfigure 3. The Reconfigure Message Option of the DHCPv6 Reconfigure
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Message .........................................................3
4. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . 5 4. Server Behavior .................................................4
5. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . 8 5. Client Behavior .................................................7
6. Clarification of section 19.4.2, RFC 3315 . . . . . . . . . . 9 6. Clarification of Section 19.4.2, RFC 3315 .......................8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 7. Security Considerations .........................................8
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 8. Acknowledgements ................................................9
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 9. References ......................................................9
10. Change log [RFC Editor please remove] . . . . . . . . . . . . 10 9.1. Normative References .......................................9
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 9.2. Informative References.....................................9
11.1. Normative References . . . . . . . . . . . . . . . . . . 10
11.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
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
type field in the Reconfigure Message option of the Reconfigure msg-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 specification defined in
only suitable for the scenarios that client would communicate with RFC 3315 is suitable only for scenarios in which the client would
the same DHCPv6 servers. communicate with the same DHCPv6 servers.
There are also scenarios that the client must communicate with a There are also scenarios where the client must communicate with a
different server: for example, a network administrator may choose to different server; for example, a network administrator may choose to
shut down a DHCPv6 server and move these clients who most recently shut down a DHCPv6 server and move the clients who most recently
communicated with it to another different server. Hence, this communicated with it to a different server. Hence, this document
document expands the allowed values of the message type field with in expands the allowed values of the message type field within the
reconfiguration message to allow the server to indicate the client to reconfiguration message to allow the server to indicate to the client
send a Rebind message, which does not include a Server Identifier to send a Rebind message, which does not include a Server 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 the timer T1. of the timer T1.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be 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
[RFC3315]. [RFC3315].
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 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:
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. Server Behavior 4. Server Behavior
This section updates specific text in sections 19.1, and 19.2 of RFC This section updates specific text in Sections 19.1 and 19.2 of RFC
3315. 3315.
Section 19.1.1: Section 19.1.1:
OLD: OLD:
The server MUST include a Reconfigure Message option (defined in The server MUST include a Reconfigure Message option (defined in
section 22.19) to select whether the client responds with a Renew section 22.19) to select whether the client responds with a Renew
message or an Information-Request message. message or an Information-Request message.
skipping to change at page 6, line 20 skipping to change at page 5, line 20
The Reconfigure message causes the client to initiate a Renew/Reply The Reconfigure message causes the client to initiate a Renew/Reply
or Information-request/Reply message exchange with the server. The or Information-request/Reply message exchange with the server. The
server interprets the receipt of a Renew or Information-request server interprets the receipt of a Renew or Information-request
message (whichever was specified in the original Reconfigure message) message (whichever was specified in the original Reconfigure message)
from the client as satisfying the Reconfigure message request. from the client as satisfying the Reconfigure message request.
NEW: NEW:
The server MUST include a Reconfigure Message option (as defined in The server MUST include a Reconfigure Message option (as defined in
Section 3) to select whether the client responds with a Renew Section 3 of RFC 6644) to select whether the client responds with a
message, a Rebind message or an Information-Request message. Renew message, a Rebind message, or an Information-request message.
The server MUST NOT include any other options in the Reconfigure,
The server MUST NOT include any other options in the Reconfigure
except as specifically allowed in the definition of individual except as specifically allowed in the definition of individual
options. options.
A server sends each Reconfigure message to a single DHCP client, A server sends each Reconfigure message to a single DHCP client,
using an IPv6 unicast address of sufficient scope belonging to the using an IPv6 unicast address of sufficient scope belonging to the
DHCP client. If the server does not have an address to which it can DHCP client. If the server does not have an address to which it can
send the Reconfigure message directly to the client, the server uses send the Reconfigure message directly to the client, the server uses
a Relay-reply message (as described in section 20.3) to send the a Relay-reply message (as described in Section 20.3) to send the
Reconfigure message to a relay agent that will relay the message to Reconfigure message to a relay agent that will relay the message to
the client. The server may obtain the address of the client (and the the client. The server may obtain the address of the client (and the
appropriate relay agent, if required) through the information the appropriate relay agent, if required) through the information the
server has about clients that have been in contact with the server, server has about clients that have been in contact with the server,
or through some external agent. or through some external agent.
To reconfigure more than one client, the server unicasts a separate To reconfigure more than one client, the server unicasts a separate
message to each client. The server may initiate the reconfiguration message to each client. The server may initiate the reconfiguration
of multiple clients concurrently; for example, a server may send a of multiple clients concurrently; for example, a server may send a
Reconfigure message to additional clients while previous Reconfigure message to additional clients while previous
reconfiguration message exchanges are still in progress. reconfiguration message exchanges are still in progress.
The Reconfigure message causes the client to initiate a Renew/Reply, The Reconfigure message causes the client to initiate a Renew/Reply,
a Rebind/Reply message exchange or an Information-request/Reply a Rebind/Reply message exchange, or an Information-request/Reply
message exchange. The server interprets the receipt of a Renew, a message exchange. The server interprets the receipt of a Renew, a
Rebind or an Information-request message (whichever was specified in Rebind, or an Information-request message (whichever was specified in
the original Reconfigure message) from the client as satisfying the the original Reconfigure message) from the client as satisfying the
Reconfigure message request. Reconfigure message request.
Section 19.1.2: Section 19.1.2:
OLD: OLD:
If the server does not receive a Renew or Information-request message If the server does not receive a Renew or Information-request message
from the client in REC_TIMEOUT milliseconds, the server retransmits from the client in REC_TIMEOUT milliseconds, the server retransmits
the Reconfigure message, doubles the REC_TIMEOUT value and waits the Reconfigure message, doubles the REC_TIMEOUT value and waits
again. The server continues this process until REC_MAX_RC again. The server continues this process until REC_MAX_RC
unsuccessful attempts have been made, at which point the server unsuccessful attempts have been made, at which point the server
SHOULD abort the reconfigure process for that client. SHOULD abort the reconfigure process for that client.
NEW: NEW:
If the server does not receive a Renew, Rebind or Information-request If the server does not receive a Renew, Rebind, or Information-
message from the client in REC_TIMEOUT milliseconds, the server request message from the client in REC_TIMEOUT milliseconds, the
retransmits the Reconfigure message, doubles the REC_TIMEOUT value server retransmits the Reconfigure message, doubles the REC_TIMEOUT
and waits again. The server continues this process until REC_MAX_RC value, and waits again. The server continues this process until
unsuccessful attempts have been made, at which point the server REC_MAX_RC unsuccessful attempts have been made, at which point the
SHOULD abort the reconfigure process for that client. server SHOULD abort the reconfigure process for that client.
Section 19.2: Section 19.2:
OLD: OLD:
19.2. Receipt of Renew or Rebind Messages 19.2. Receipt of Renew or Rebind Messages
The server generates and sends a Reply message to the client as The server generates and sends a Reply message to the client as
described in sections 18.2.3 and 18.2.8, including options for described in sections 18.2.3 and 18.2.8, including options for
configuration parameters. configuration parameters.
skipping to change at page 7, line 43 skipping to change at page 6, line 45
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.
NEW: NEW:
19.2. Receipt of Renew Messages 19.2. Receipt of Renew Messages
In response to a Renew message, the server generates and sends a In response to a Renew message, the server generates and sends a
Reply message to the client as described in sections 18.2.3 and Reply message to the client as described in Sections 18.2.3 and
18.2.8, including options for configuration parameters. 18.2.8, including options for configuration parameters.
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 identity associations
other configuration parameters in the Reply message, even if those (IAs) and new values for other configuration parameters in the Reply
IAs and parameters were not requested in the Renew or Rebind message message, even if those IAs and parameters were not requested in the
from the client. Renew or Rebind message from the client.
5. 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.
Section 19.4.1: Section 19.4.1:
OLD: OLD:
Upon receipt of a valid Reconfigure message, the client responds with Upon receipt of a valid Reconfigure message, the client responds with
either a Renew message or an Information-request message as indicated either a Renew message or an Information-request message as indicated
by the Reconfigure Message option (as defined in section 22.19). The by the Reconfigure Message option (as defined in section 22.19). The
client ignores the transaction-id field in the received Reconfigure client ignores the transaction-id field in the received Reconfigure
message. While the transaction is in progress, the client silently message. While the transaction is in progress, the client silently
discards any Reconfigure messages it receives. discards any Reconfigure messages it receives.
NEW: NEW:
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 Section as indicated by the Reconfigure Message option (as defined in Section
3). The client ignores the transaction-id field in the received 3 of RFC 6644). The client ignores the transaction-id field in the
Reconfigure message. While the transaction is in progress, the received Reconfigure message. While the transaction is in progress,
client silently discards any Reconfigure messages it receives. the client silently discards any Reconfigure messages it receives.
Section 19.4.2: Section 19.4.2:
ADD new second and third paragraphs: ADD new second and third paragraphs:
When responding to a Reconfigure, the client creates and sends the When responding to a Reconfigure, the client creates and sends the
Rebind message in exactly the same manner as outlined in section 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 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 Option Request option and any IA options from the Reconfigure message
into the Rebind message. into the Rebind message.
If a client is currently sending Rebind messages, as described in If a client is currently sending Rebind messages, as described in
section 18.1.4 of RFC 3315, the client ignores any received Section 18.1.4 of RFC 3315, the client ignores any received
Reconfigure messages. Reconfigure messages.
Section 19.4.4: Section 19.4.4:
OLD: OLD:
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 or Information-request messages generated as part of does with Renew or Information-request messages generated as part of
a client-initiated configuration exchange. See sections 18.1.3 and a client-initiated configuration exchange. See sections 18.1.3 and
18.1.5 for details. If the client does not receive a response from 18.1.5 for details. If the client does not receive a response from
the server by the end of the retransmission process, the client the server by the end of the retransmission process, the client
ignores and discards the Reconfigure message. ignores and discards the Reconfigure message.
NEW: NEW:
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.
6. 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 with which the client most recently
with. communicated.
7. Security Considerations 7. Security Considerations
This document allows the Rebind message type to appear in the This document allows the Rebind message type to appear in the
Reconfigure Message option of a Reconfigure message so that the Reconfigure Message option of a Reconfigure message so that the
client rebinds to a different DHCPv6 server. A malicious attacker client rebinds to a different DHCPv6 server. A malicious attacker
may use a faked Reconfigure message to force the client to disconnect may use a faked Reconfigure message to force the client to disconnect
from the current server and relink to a faked server by quickly from the current server and relink to a faked server by quickly
responding to the client's Rebind message. A similar attack is responding to the client's Rebind message. A similar attack is
available in DHCPv6 by an attacker spoofing itself as a valid DHCPv6 available in DHCPv6 by an attacker spoofing itself as a valid DHCPv6
server in response to a Solicit or Request message. These attacks server in response to a Solicit or Request message. These attacks
can be prevented by using the AUTH option [RFC3315]. DHCPv6 clients can be prevented by using the AUTH option [RFC3315]. DHCPv6 clients
that support Reconfigure-Rebind MUST implement the Reconfigure Key that support Reconfigure-Rebind MUST implement the Reconfigure Key
authentication protocol as described in [RFC3315] section 21.5. authentication protocol as described in [RFC3315], Section 21.5.
Other authentication mechanisms may optionally be implemented. For Other authentication mechanisms may optionally be implemented. For
example, the Secure DHCPv6 [I-D.ietf-dhc-secure-dhcpv6], based on example, the Secure DHCPv6 [SEC-DHCPv6], based on Cryptographically
Cryptographically Generated Addresses (CGA) [RFC3972], can provide Generated Addresses (CGA) [RFC3972], can provide source address (for
source address ownership validation, message origin authentication the DHCP server/relay) ownership validation, message origin
and message integrity without requesting symmetric key pairs or authentication, and message integrity without requiring symmetric key
supporting from any key management system. pairs or support from a key management system.
8. Acknowledgements 8. Acknowledgements
Valuable comments were made by Jari Arkko, Sean Turner, Ted Lemon and Valuable comments were made by Jari Arkko, Sean Turner, Ted Lemon,
Stephen Farrell. and Stephen Farrell.
9. IANA Considerations
There are no actions for IANA associated with this document.
10. Change log [RFC Editor please remove]
Revision -05
Clarified description of this feature in introduction.
Clarified action of client if it receives a Reconfigure while sending
Rebind messages.
Revision -08
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.
Revision-10
Adopt OLD-NEW style according to IESG comment and address other IESG
comments.
11. References 9. References
11.1. Normative References 9.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., Ed., Bound, J., Volz, B., Lemon, T., Perkins,
and M. Carney, "Dynamic Host Configuration Protocol for C., and M. Carney, "Dynamic Host Configuration Protocol
IPv6 (DHCPv6)", RFC 3315, July 2003. for IPv6 (DHCPv6)", RFC 3315, July 2003.
[RFC3972] Aura, T., "Cryptographically Generated Addresses (CGA)", [RFC3972] Aura, T., "Cryptographically Generated Addresses (CGA)",
RFC 3972, March 2005. RFC 3972, March 2005.
11.2. Informative References 9.2. Informative References
[I-D.ietf-dhc-secure-dhcpv6] [SEC-DHCPv6]
Jiang, S. and S. Shen, "Secure DHCPv6 Using CGAs", Jiang, S. and S. Shen, "Secure DHCPv6 Using CGAs", Work in
draft-ietf-dhc-secure-dhcpv6-06 (work in progress), Progress, March 2012.
March 2012.
Authors' Addresses Authors' Addresses
D. R. Evans D. R. Evans
ARRIS International, Inc. IPfonix, Inc.
IPfonix, Inc., 330 WCR 16 1/2 330 WCR 16 1/2
Longmont, CO 80504-9467 Longmont, CO 80504-9467
USA USA
Phone: +1 303.682.2412 Phone: +1 303.682.2412
Email: N7DR@ipfonix.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
Sheng Jiang Sheng Jiang
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
Q14, Huawei Campus, No.156 Beiqing Road Q14, Huawei Campus, No.156 Beiqing Road
Hai-Dian District, Beijing, 100095 Hai-Dian District, Beijing, 100095
P.R. China P.R. China
Email: jiangsheng@huawei.com EMail: jiangsheng@huawei.com
 End of changes. 46 change blocks. 
141 lines changed or deleted 109 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/