--- 1/draft-ietf-dhc-dhcpv6-relay-supplied-options-04.txt 2011-05-09 04:15:39.000000000 +0200 +++ 2/draft-ietf-dhc-dhcpv6-relay-supplied-options-05.txt 2011-05-09 04:15:39.000000000 +0200 @@ -1,19 +1,19 @@ dhc T. Lemon Internet-Draft Nominum Intended status: Standards Track Q. Wu -Expires: April 18, 2011 Huawei - October 15, 2010 +Expires: November 10, 2011 Huawei + May 9, 2011 Relay-Supplied DHCP Options - draft-ietf-dhc-dhcpv6-relay-supplied-options-04 + draft-ietf-dhc-dhcpv6-relay-supplied-options-05 Abstract This document describes a mechanism whereby a DHCPv6 relay agent can provide options to a DHCPv6 server that the DHCPv6 server can then provide to the DHCPv6 client in certain restricted cases where this is necessary. Status of this Memo @@ -23,25 +23,25 @@ Internet-Drafts are working documents of the Internet Engineering 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 and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on April 18, 2011. + This Internet-Draft will expire on November 10, 2011. Copyright Notice - Copyright (c) 2010 IETF Trust and the persons identified as the + Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -55,21 +55,21 @@ 2. Protocol Summary . . . . . . . . . . . . . . . . . . . . . . . 3 3. Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. RSOO-enabled options . . . . . . . . . . . . . . . . . . . . . 4 5. DHCP Relay Agent Behavior . . . . . . . . . . . . . . . . . . . 5 6. DHCP Server Behavior . . . . . . . . . . . . . . . . . . . . . 5 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 9.1. Normative References . . . . . . . . . . . . . . . . . . . 7 9.2. Informative References . . . . . . . . . . . . . . . . . . 7 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 1. Introduction The DHCPv6 specification [RFC3315] allows DHCP relay agents to forward DHCPv6 messages between clients and servers that are not on the same IPv6 link. In some cases the DHCP relay agent has information not available to the DHCP server that would be useful to provide to a DHCP client. For example, the DHCP client may need to learn the EAP local domain name [I.D-ietf-hokey-ldn-discovery] for use in EAP re-authentication [RFC5296], which is known to the relay @@ -119,25 +119,31 @@ agent wishes to provide to the DHCPv6 server. 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | OPTION_RSOO | option-length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | options... +-+-+-+-+-+-+-+-+-+-+-+ - OPTION_RSOO Relay-Supplied Options code (TBD). + OPTION_RSOO - option-length Length of Relay-Supplied Options option. + Relay-Supplied Options code (TBD). - options One or more DHCPv6 options. + option-length + + Length of Relay-Supplied Options option. + + options + + One or more DHCPv6 options. 4. RSOO-enabled options Unless specifically called out as an RSOO-enabled option, no DHCP option should appear in an RSOO. Specifications that describe RSOO- enabled options MUST reference this specification, and MUST state that the option they define is RSOO-enabled. No DHCP option specified prior to the issuance of this specification is RSOO- enabled. @@ -278,23 +284,23 @@ [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, July 2003. 9.2. Informative References [I.D-ietf-hokey-ldn-discovery] - Zorn, G., Wu, Q., and Y. Wang, "The Local Domain Name - DHCPv6 Option", draft-ietf-hokey-ldn-discovery-05 (work in - progress), September 2010. + Zorn, G., Wu, Q., and Y. Wang, "The ERP Local Domain Name + DHCPv6 Option", draft-ietf-hokey-ldn-discovery-10 (work in + progress), April 2011. [RFC5296] Narayanan, V. and L. Dondeti, "EAP Extensions for EAP Re- authentication Protocol (ERP)", RFC 5296, August 2008. Authors' Addresses Ted Lemon Nominum 2000 Seaport Blvd Redwood City, CA 94063