draft-ietf-dhc-dhcpv6-agentopt-delegate-00.txt   draft-ietf-dhc-dhcpv6-agentopt-delegate-01.txt 
dhc Group R. Droms dhc Group R. Droms
Internet-Draft B. Volz Internet-Draft B. Volz
Expires: July 28, 2006 O. Troan Intended status: Informational O. Troan
Cisco Systems, Inc. Expires: February 11, 2007 Cisco Systems, Inc.
January 24, 2006 August 10, 2006
DHCP Relay Agent Assignment Notification Option DHCPv6 Relay Agent Assignment Notification (RAAN) Option
draft-ietf-dhc-dhcpv6-agentopt-delegate-00.txt draft-ietf-dhc-dhcpv6-agentopt-delegate-01.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 July 28, 2006. This Internet-Draft will expire on February 11, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
The DHCP Relay Agent Assignment Notification option is sent from a The DHCP Relay Agent Assignment Notification (RAAN) option is sent
DHCP server to a DHCP relay agent to inform the relay agent of IPv6 from a DHCP server to a DHCP relay agent to inform the relay agent of
addresses that have been assigned or IPv6 prefixes that have been IPv6 addresses that have been assigned or IPv6 prefixes that have
delegated to DHCP clients. been delegated to DHCP clients.
1. Introduction 1. Introduction
The DHCP Relay Agent Assignment Notification option encapsulates The DHCP Relay Agent Assignment Notification (RAAN) option
address and prefix options to indicate that an address or prefix has encapsulates address and prefix options to indicate that an address
been assigned. The option may also carry other information required or prefix has been assigned. The option may also carry other
by the network element for configuration related to the assigned information required by the network element for configuration related
address or prefix. to the assigned address or prefix.
For example, a network administrator uses the DHCP Relay Agent For example, a network administrator uses the RAAN option to inform a
Assignment Notification option to inform a relay agent of a prefix relay agent of a prefix that has been delegated through DHCP PD to a
that has been delegated through DHCP PD to a DHCP client. The relay DHCP client. The relay agent notifies the network element on which
agent notifies the network element on which the it is implemented of it is implemented of the delegation information so the network
the delegation information so the network element can add routing element can add routing information about the delegated prefix into
information about the delegated prefix into the appropriate routing the appropriate routing protocols.
protocols.
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 RFC 2119 [1]. interpreted as described in RFC 2119 [1].
The term "DHCP" in this document refers to DHCP for IPv6, as defined The term "DHCP" in this document refers to DHCP for IPv6, as defined
in RFC 3315 [2]. The terms "DHCP prefix delegation" and "DHCP PD" in RFC 3315 [2]. The terms "DHCP prefix delegation" and "DHCP PD"
refer DHCP for IPv6 prefix delegation, as defined in RFC 3633 [3] refer DHCP for IPv6 prefix delegation, as defined in RFC 3633 [3]
Additional terms used in the description of DHCP and DHCP prefix Additional terms used in the description of DHCP and DHCP prefix
delegation are defined in RFC 3315 and RFC 3633. In this document delegation are defined in RFC 3315 and RFC 3633. In this document
"assigning" an IPv6 prefix is equivalent to "delegating" a prefix. "assigning" an IPv6 prefix is equivalent to "delegating" a prefix.
3. Option semantics 3. Option semantics
The DHCP Relay Agent Assignment Notification option carries The RAANn option carries information about assigned IPv6 addresses
information about assigned IPv6 addresses and prefixes. It and prefixes. It encapsulates an IA Address option (RFC 3315) or an
encapsulates an IA Address option (RFC 3315) or an IA Prefix option IA Prefix option (RFC 3633), and possibly other options that carry
(RFC 3633), and possibly other options that carry other information other information related to the assigned IPv6 address or prefix.
related to the assigned IPv6 address or prefix.
The DHCP server MAY include this option in a Reply message sent to a The DHCP server MAY include this option in a Reply message sent to a
client that includes assigned addresses and/or prefixes. If the DHCP client that includes assigned addresses and/or prefixes. If the DHCP
server does include this option in a Reply message, it MUST include server does include this option in a Reply message, it MUST include
it in the option area of the Relay-reply message sent to the relay it in the option area of the Relay-reply message sent to the relay
agent intended as the recipient of the option. agent intended as the recipient of the option.
The DHCP server is responsible for synchronizing any state created by The DHCP server is responsible for synchronizing any state created by
a node through the use of the Assignment Notification option. For a node through the use of the RAAN option. For example, if a DHCP
example, if a DHCP server receives a Release message for a delegated server receives a Release message for a delegated prefix, it causes
prefix, it causes the node to delete any state associated with that the node to delete any state associated with that prefix by sending
prefix by sending an Assignment Notification option containing an IA an RAAN option containing an IA Prefix option with the released
Prefix option with the released prefix and a valid lifetime of zero. prefix and a valid lifetime of zero.
A relay agent that receives this option SHOULD pass the information A relay agent that receives this option SHOULD pass the information
to the node in which the relay agent is instantiated. The node MAY to the node in which the relay agent is instantiated. The node MAY
make use of the information received from the relay agent. make use of the information received from the relay agent.
If a node creates state based on the information included in this If a node creates state based on the information included in this
option, it MUST remove that state when the lifetime as specified in option, it MUST remove that state when the lifetime as specified in
the option expires. the option expires.
Examples of use: Examples of use:
o Populate an ACL with an assigned IPv6 address if the network o Populate an ACL with an assigned IPv6 address if the network
device in which the relay agent is instantiated implements a device in which the relay agent is instantiated implements a
security policy limiting IPv6 forwarding to devices that have security policy limiting IPv6 forwarding to devices that have
obtained an address through DHCP obtained an address through DHCP
o Inject routing information into a routing infrastructure about a o Inject routing information into a routing infrastructure about a
delegated prefix on behalf of a requesting router delegated prefix on behalf of a requesting router
4. Option format 4. Option format
The DHCP Relay Agent Assignment Notification Option has the following The RAAN option has the following format:
format:
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-code | length | | option-code | length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| encapsulated-options | | encapsulated-options |
. . . .
. . . .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code OPTION_AGENT_NOTIFY (TBD) option-code OPTION_AGENT_NOTIFY (TBD)
length length of encapsulated options, in octets length length of encapsulated options, in octets
encapsulated-options DHCP options to be delivered by the Relay Agent encapsulated-options DHCP options to be delivered by the Relay Agent
Assignment Notification option Assignment Notification option
5. Encapsulating DHCP options in the DHCP Relay Agent Assignment 5. Encapsulating DHCP options in the RAAN Option
Notification Option
The contents of options encapsulated in the DHCP Relay Agent The contents of options encapsulated in the RAAN option are
Assignment Notification option are interpreted according to the use interpreted according to the use of those options in the node on
of those options in the node on which the relay agent is implemented. which the relay agent is implemented. For the purposes of address
For the purposes of address and prefix assignment, the uses of the and prefix assignment, the uses of the DHCP IA Address and IA Prefix
DHCP IA Address and IA Prefix options are defined in this document. options are defined in this document.
Note that the contents of these options are not necessarily the same Note that the contents of these options are not necessarily the same
as in the corresponding options sent to the DHCP client. For as in the corresponding options sent to the DHCP client. For
example, the node that receives the information from these options example, the node that receives the information from these options
may be instructed to use the information for a shorter period of time may be instructed to use the information for a shorter period of time
than the client by setting a shorter valid-lifetime in the this than the client by setting a shorter valid-lifetime in the this
option. option.
5.1. IA Address option 5.1. IA Address option
skipping to change at page 5, line 18 skipping to change at page 5, line 15
IAprefix-options Not used at the time this document was published IAprefix-options Not used at the time this document was published
6. Requesting assignment information from the DHCP server 6. Requesting assignment information from the DHCP server
If a relay agent requires the DHCP server to provide information If a relay agent requires the DHCP server to provide information
about assigned addresses and prefixes, it MUST include an Option about assigned addresses and prefixes, it MUST include an Option
Request option, requesting the Assignment Notification option, as Request option, requesting the Assignment Notification option, as
described in section 22.7 of RFC 3315. described in section 22.7 of RFC 3315.
7. IANA considerations 7. Reordering received DHCP messages
The relay agent MUST use the Server Reply Sequence Number (SRSN)
option [4] to detect and discard RAAN options contained in DHCP
messages that are received out of order.
8. IANA considerations
IANA is requested to assign an option code from the "DHCPv6 and IANA is requested to assign an option code from the "DHCPv6 and
DHCPv6 options registry DHCPv6 options" registry
http://www.iana.org/assignments/dhcpv6-parameters to http://www.iana.org/assignments/dhcpv6-parameters to
OPTION_AGENT_NOTIFY. OPTION_AGENT_NOTIFY.
8. Security considerations 9. Security considerations
Security issues related to DHCP are described in RFC 3315 and RFC Security issues related to DHCP are described in RFC 3315 and RFC
3633. 3633.
The DHCP Relay Agent Assignment Notification Option may be used to The RAAN option may be used to mount a denial of service attack by
mount a denial of service attack by causing a node to incorrectly causing a node to incorrectly populate an ACL or incorrectly
populate an ACL or incorrectly configure routing protocol information configure routing protocol information for a delegated prefix. This
for a delegated prefix. This option may also be used to insert option may also be used to insert invalid prefixes into the routing
invalid prefixes into the routing infrastruture or add invalid IP infrastruture or add invalid IP addresses to ACLs in nodes.
addresses to ACLs in nodes. Communication between a server and a Communication between a server and a relay agent, and communication
relay agent, and communication between relay agents, can be secured between relay agents, can be secured through the use of IPSec, as
through the use of IPSec, as described in section 21.1 of RFC 3315. described in section 21.1 of RFC 3315.
9. Normative References 10. Changes in this revision
If this section is included in the document when it is submitted for
publication, the RFC Editor is requested to remove it.
Changes in rev -01:
o Added section describing use of "Server Reply Sequence Number"
option to allow resequencing of out-of-order messages
11. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[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] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host [3] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host
Configuration Protocol (DHCP) version 6", RFC 3633, Configuration Protocol (DHCP) version 6", RFC 3633,
December 2003. December 2003.
[4] Volz, B. and R. Droms, "DHCPv6 Server Reply Sequence Number
Option", draft-volz-dhc-dhcpv6-srsn-option-00 (work in
progress), August 2006.
Authors' Addresses Authors' Addresses
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
skipping to change at page 7, line 24 skipping to change at page 7, line 4
Email: rdroms@cisco.com Email: rdroms@cisco.com
Bernie Volz Bernie Volz
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Avenue 1414 Massachusetts Avenue
Boxborough, MA 01719 Boxborough, MA 01719
USA USA
Phone: +1 978.936.0382 Phone: +1 978.936.0382
Email: volz@cisco.com Email: volz@cisco.com
Ole Troan Ole Troan
Cisco Systems, Inc. Cisco Systems, Inc.
Shinjuku Mitsui Building, 2-1-1, Nishi-Shinjuku, Shinjuku-Ku Shinjuku Mitsui Building, 2-1-1, Nishi-Shinjuku, Shinjuku-Ku
Tokyo, Kanto 163-0409 Tokyo, Kanto 163-0409
Japan Japan
Phone: +81 3 5324.4027 Phone: +81 3 5324.4027
Email: otroan@cisco.com Email: otroan@cisco.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
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
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 8, line 29 skipping to change at page 8, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 21 change blocks. 
71 lines changed or deleted 85 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/