draft-ietf-dhc-dhcpv6-agentopt-delegate-03.txt   draft-ietf-dhc-dhcpv6-agentopt-delegate-04.txt 
dhc Group R. Droms dhc Group R. Droms
Internet-Draft B. Volz Internet-Draft B. Volz
Intended status: Standards Track Cisco Systems, Inc. Intended status: Standards Track O. Troan
Expires: August 10, 2009 O. Troan Expires: January 14, 2010 Cisco Systems, Inc.
No Affiliation July 13, 2009
February 6, 2009
DHCPv6 Relay Agent Assignment Notification (RAAN) Option DHCPv6 Relay Agent Assignment Notification (RAAN) Option
draft-ietf-dhc-dhcpv6-agentopt-delegate-03.txt draft-ietf-dhc-dhcpv6-agentopt-delegate-04.txt
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 to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79. 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.
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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 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 August 10, 2009. This Internet-Draft will expire on January 14, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of
(http://trustee.ietf.org/license-info) in effect on the date of publication of this document (http://trustee.ietf.org/license-info).
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document.
to this document.
Abstract Abstract
The DHCP Relay Agent Assignment Notification (RAAN) option is sent The DHCP Relay Agent Assignment Notification (RAAN) option is sent
from a DHCP server to a DHCP relay agent to inform the relay agent of from a DHCP server to a DHCP relay agent to inform the relay agent of
IPv6 addresses that have been assigned or IPv6 prefixes that have IPv6 addresses that have been assigned or IPv6 prefixes that have
been delegated to DHCP clients. been delegated to DHCP clients.
1. Introduction 1. Introduction
skipping to change at page 6, line 5 skipping to change at page 6, line 16
corresponding IA Prefix option in the message to corresponding IA Prefix option in the message to
be forwarded to the client be forwarded to the client
8. Requesting assignment information from the DHCP server 8. 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.
9. Reordering received DHCP messages 9. IANA considerations
The relay agent MUST use the Server Reply Sequence Number (SRSN)
option [I-D.ietf-dhc-dhcpv6-srsn-option] to detect and discard RAAN
options contained in DHCP messages that are received out of order.
10. 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.
11. Security considerations 10. 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 RAAN option may be used to mount a denial of service attack by The RAAN option may be used to mount a denial of service attack by
causing a node to incorrectly populate an ACL or incorrectly causing a node to incorrectly populate an ACL or incorrectly
configure routing information for a delegated prefix. This option configure routing information for a delegated prefix. This option
may also be used to insert invalid prefixes into the routing may also be used to insert invalid prefixes into the routing
infrastructure or add invalid IP addresses to ACLs in nodes. infrastructure or add invalid IP addresses to ACLs in nodes.
Communication between a server and a relay agent, and communication Communication between a server and a relay agent, and communication
between relay agents, can be secured through the use of IPSec, as between relay agents, can be secured through the use of IPSec, as
described in section 21.1 of RFC 3315. described in section 21.1 of RFC 3315.
12. Changes log 11. Changes log
If this section is included in the document when it is submitted for If this section is included in the document when it is submitted for
publication, the RFC Editor is requested to remove it. publication, the RFC Editor is requested to remove it.
Changes in rev -01: Changes in rev -01:
o Added section describing use of "Server Reply Sequence Number" o Added section describing use of "Server Reply Sequence Number"
option to allow resequencing of out-of-order messages option to allow resequencing of out-of-order messages
Changes in rev -02: Changes in rev -02:
o Made editorial change in section 1: s/the appropriate routing o Made editorial change in section 1: s/the appropriate routing
protocols/the routing infrastructure/ protocols/the routing infrastructure/
o Updated first paragraph in Section 3 to allow multiple IA Address o Updated first paragraph in Section 3 to allow multiple IA Address
options and/or IA Prefix options options and/or IA Prefix options
o Renamed section 3 to "Options Semantics and Usage" o Renamed section 3 to "Options Semantics and Usage"
o Added paragraph to section "Option Semantics and Usage" requiring o Added paragraph to section "Option Semantics and Usage" requiring
that the DHCP server must include all addresses/prefixes for the that the DHCP server must include all addresses/prefixes for the
client (on that link) in the RAAN option client (on that link) in the RAAN option
o Added list of use cases to section "Option Semantics and Usage" o Added list of use cases to section "Option Semantics and Usage"
o Added section "Relay Agent Behavior" o Added section "Relay Agent Behavior"
skipping to change at page 7, line 14 skipping to change at page 7, line 23
o Added list of use cases to section "Option Semantics and Usage" o Added list of use cases to section "Option Semantics and Usage"
o Added section "Relay Agent Behavior" o Added section "Relay Agent Behavior"
o Added section "Server Behavior"; moved second paragraph of section o Added section "Server Behavior"; moved second paragraph of section
"Option Semantics and Usage" to "Server Behavior" "Option Semantics and Usage" to "Server Behavior"
o Updated reference to draft-ietf-dhc-dhcpv6-srsn-option-00 o Updated reference to draft-ietf-dhc-dhcpv6-srsn-option-00
o Clarified descriptions of various option fields in section o Clarified descriptions of various option fields in section
"Encapsulating DHCP options in the RAAN Option" "Encapsulating DHCP options in the RAAN Option"
Changes in rev -03: refreshed after expiration. Changes in rev -03: refreshed after expiration.
13. Normative References Changes in rev -04: all references to the "Server Reply Sequence
Number" option were removed from the draft.
12. 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.
[RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic
Host Configuration Protocol (DHCP) version 6", RFC 3633, Host Configuration Protocol (DHCP) version 6", RFC 3633,
December 2003. December 2003.
[I-D.ietf-dhc-dhcpv6-srsn-option]
Volz, B. and R. Droms, "DHCPv6 Server Reply Sequence
Number Option", draft-ietf-dhc-dhcpv6-srsn-option-02 (work
in progress), February 2009.
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
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
No Affiliation Cisco Systems, Inc.
Phone: TBD Phone: +47 23 27 3664
Email: TBD Email: otroan@cisco.com
 End of changes. 13 change blocks. 
28 lines changed or deleted 29 lines changed or added

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