draft-ietf-dhc-dhcpv6-ero-00.txt   draft-ietf-dhc-dhcpv6-ero-01.txt 
DHC S. Zeng DHC S. Zeng
Internet-Draft B. Volz Internet-Draft B. Volz
Intended status: Standards Track K. Kinnear Intended status: Standards Track K. Kinnear
Expires: April 5, 2007 Cisco Systems, Inc. Expires: September 16, 2007 Cisco Systems, Inc.
J. Brzozowski J. Brzozowski
Comcast Cable Comcast Cable
October 02, 2006 March 15, 2007
DHCPv6 Relay Agent Echo Request Option DHCPv6 Relay Agent Echo Request Option
draft-ietf-dhc-dhcpv6-ero-00.txt draft-ietf-dhc-dhcpv6-ero-01
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 37 skipping to change at page 1, line 37
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 April 5, 2007. This Internet-Draft will expire on September 16, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This memo defines a Relay Agent Echo Request option for the Dynamic This memo defines a Relay Agent Echo Request option for the Dynamic
Host Configuration Protocol for IPv6 (DHCPv6). The option allows a Host Configuration Protocol for IPv6 (DHCPv6). The option allows a
DHCPv6 relay agent to request a list of relay agent options that the DHCPv6 relay agent to request a list of relay agent options that the
server echoes back to the relay agent. server echoes back to the relay agent.
Table of Contents Table of Contents
skipping to change at page 2, line 19 skipping to change at page 2, line 19
3. The Relay Agent Echo Request Option . . . . . . . . . . . . . . 3 3. The Relay Agent Echo Request Option . . . . . . . . . . . . . . 3
4. DHCPv6 Relay Agent Behavior . . . . . . . . . . . . . . . . . . 4 4. DHCPv6 Relay Agent Behavior . . . . . . . . . . . . . . . . . . 4
5. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . . . . 4 5. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
9.1. Normative References . . . . . . . . . . . . . . . . . . . 5 9.1. Normative References . . . . . . . . . . . . . . . . . . . 5
9.2. Informative References . . . . . . . . . . . . . . . . . . 5 9.2. Informative References . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
Intellectual Property and Copyright Statements . . . . . . . . . . 8 Intellectual Property and Copyright Statements . . . . . . . . . . 7
1. Introduction 1. Introduction
DHCPv6 [2] provides a framework for configuring IPv6 clients with DHCPv6 [2] provides a framework for configuring IPv6 clients with
addresses and other network parameters. It includes a relay agent addresses and other network parameters. It includes a relay agent
capability. A relay agent is an intermediary node that delivers DHCP capability. A relay agent is an intermediary node that delivers DHCP
messages between clients and servers. The relay agent and the server messages between clients and servers. The relay agent and the server
exchange information using options in relay agent messages. The exchange information using options in relay agent messages. The
relay agent may add relay agent options to the client DHCP message relay agent may add relay agent options to the client DHCP message
before forwarding it. before forwarding it.
The information that relay agents supply can be used in the server's The information that relay agents supply can be used in the server's
decision making about the addresses, delegated prefixes, and decision making about the addresses, delegated prefixes, and
configuration parameters that the client is to receive. Likewise, configuration parameters that the client is to receive. Likewise,
the relay may need some of the information to efficiently return the relay may need some of the information to efficiently return
replies to clients. replies to clients.
In DHCPv4, the server generally echoes the relay agent option back In DHCPv4, the server generally echoes the relay agent option back
verbatim to the relay agent in server-to-client replies [3]. verbatim to the relay agent in server-to-client replies [3].
However, DHCPv6 [2] does not require the server to do so. As matter However, DHCPv6 [2] does not require the server to do so. As a
of fact, for certain relay agent options, the server is required to matter of fact, for certain relay agent options, the server is
echo back the options only if it recognizes them (e.g., [5], [6]). required to echo back the options only if it recognizes them (e.g.,
This could be problematic, as the relay agent may need to use some [4], [5]). This could be problematic, as the relay agent may need to
relay options even if the server does not recognize them. use some relay options even if the server does not recognize them.
This memo defines a relay agent echo request option that the relay This memo defines a relay agent echo request option that the relay
agent uses to explicitly request a list of options that the server agent uses to explicitly request a list of options that the server
echoes back to the relay agent. echoes back to the relay agent.
2. Requirements Terminology 2. Requirements 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 [1]. document are to be interpreted as described in [1].
skipping to change at page 4, line 31 skipping to change at page 4, line 31
the relay agent. the relay agent.
4. DHCPv6 Relay Agent Behavior 4. DHCPv6 Relay Agent Behavior
A relay agent MAY include an Echo Request option in a Relay Forward A relay agent MAY include an Echo Request option in a Relay Forward
message to inform the server about options the relay agent wants the message to inform the server about options the relay agent wants the
server to echo back to the relay agent. If the relay agent takes server to echo back to the relay agent. If the relay agent takes
different actions based on whether an option is echoed back or not, different actions based on whether an option is echoed back or not,
then the relay agent SHOULD NOT include such an option in the Echo then the relay agent SHOULD NOT include such an option in the Echo
Request option. Note that the relay uses the OPTION_ORO [2] to Request option. Note that the relay uses the OPTION_ORO [2] to
request the server to return options (e.g., [7]) other than relay request the server to return options (e.g., [6]) other than relay
agent options in the Relay Forward message. agent options in the Relay Forward message.
5. DHCPv6 Server Behavior 5. DHCPv6 Server Behavior
When a server creates a Relay-Reply, it SHOULD perform ERO processing When a server creates a Relay-Reply, it SHOULD perform ERO processing
after processing the ORO and other options processing. For each after processing the ORO and other options processing. For each
option in the ERO: option in the ERO:
a. If the option is already in the Relay-Reply, the server MUST a. If the option is already in the Relay-Reply, the server MUST
ignore that option and continue to process any remaining options ignore that option and continue to process any remaining options
in the ERO. in the ERO.
skipping to change at page 5, line 43 skipping to change at page 5, line 43
[2] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. [2] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M.
Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",
RFC 3315, July 2003. RFC 3315, July 2003.
[3] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046, [3] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046,
January 2001. January 2001.
9.2. Informative References 9.2. Informative References
[4] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host [4] Volz, B., "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
Configuration Protocol (DHCP) version 6", RFC 3633, Relay Agent Subscriber-ID Option", RFC 4580, June 2006.
December 2003.
[5] Volz, B., "DHCPv6 Relay Agent Subscriber-ID Option",
draft-ietf-dhc-dhcpv6-subid-01 (work in progress), March 2006.
[6] Volz, B., "DHCPv6 Relay Agent Remote ID Option", [5] Volz, B., "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
draft-ietf-dhc-dhcpv6-remoteid-01 (work in progress), Relay Agent Remote-ID Option", RFC 4649, August 2006.
March 2006.
[7] Droms, R., "DHCPv6 Relay Agent Assignment Notification (RAAN) [6] Droms, R., "DHCPv6 Relay Agent Assignment Notification (RAAN)
Option", draft-ietf-dhc-dhcpv6-agentopt-delegate-01 (work in Option", draft-ietf-dhc-dhcpv6-agentopt-delegate-02 (work in
progress), August 2006. progress), November 2006.
Authors' Addresses Authors' Addresses
Shengyou Zeng Shengyou Zeng
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Ave. 1414 Massachusetts Ave.
Boxborough, MA 01719 Boxborough, MA 01719
USA USA
Phone: +1 978 936 0000 Phone: +1 978 936 0000
skipping to change at page 8, line 7 skipping to change at page 7, line 7
Comcast Cable Comcast Cable
1800 Bishops Gate Boulevard 1800 Bishops Gate Boulevard
Mt. Laurel, NJ 08054 Mt. Laurel, NJ 08054
USA USA
Phone: +1 856 324 2671 Phone: +1 856 324 2671
Email: john_brzozowski@cable.comcast.com Email: john_brzozowski@cable.comcast.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. 13 change blocks. 
29 lines changed or deleted 24 lines changed or added

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