draft-ietf-dhc-dhcpv6-relay-supplied-options-00.txt   draft-ietf-dhc-dhcpv6-relay-supplied-options-01.txt 
dhc T. Lemon dhc T. Lemon
Internet-Draft Nominum Internet-Draft Nominum
Intended status: Standards Track Q. Wu Intended status: Standards Track Q. Wu
Expires: March 18, 2011 Huawei Expires: March 22, 2011 Huawei
September 14, 2010 September 18, 2010
Relay-Supplied DHCP Options Relay-Supplied DHCP Options
draft-ietf-dhc-dhcpv6-relay-supplied-options-00 draft-ietf-dhc-dhcpv6-relay-supplied-options-01
Abstract Abstract
This document describes a general mechanism whereby a DHCPv6 relay This document describes a general mechanism whereby a DHCPv6 relay
agent can provide options to a DHCPv6 server that the DHCPv6 server agent can provide options to a DHCPv6 server that the DHCPv6 server
can then provide to the DHCPv6 client. can then provide to the DHCPv6 client.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 33 skipping to change at page 1, line 33
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on March 18, 2011. This Internet-Draft will expire on March 22, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 2, line 16 skipping to change at page 2, line 16
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Protocol Summary . . . . . . . . . . . . . . . . . . . . . . . 3 2. Protocol Summary . . . . . . . . . . . . . . . . . . . . . . . 3
3. Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. DHCP Relay Agent Behavior . . . . . . . . . . . . . . . . . . . 4 4. DHCP Relay Agent Behavior . . . . . . . . . . . . . . . . . . . 4
5. DHCP Server Behavior . . . . . . . . . . . . . . . . . . . . . 4 5. DHCP Server Behavior . . . . . . . . . . . . . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
8. Normative References . . . . . . . . . . . . . . . . . . . . . 5 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 8.1. Normative References . . . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
There are some cases where a DHCP relay agent has information that The DHCPv6 specification [RFC3315] allows DHCP relay agents to
would be useful to provide to a DHCP client, and the DHCP server does forward DHCPv6 messages between clients and servers that are not on
not have that information. The DHCPv6 specification [RFC3315] does the same IPv6 link. In some cases the DHCP relay agent has
not provide a mechanism whereby the DHCP relay can provide options to information the DHCP server does not have that would be useful to
the DHCP client. This document defines an extension to DHCP that provide to a DHCP client. For example, the DHCP client may need to
allows DHCP relay agents to propose options to be sent to DHCP 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
agent but not the server. The DHCPv6 protocol specification does not
provide a mechanism whereby the relay agent can provide options to
the client. This document extends DHCP with a mechanism that allows
DHCP relay agents to propose options for the server to send to DHCP
clients. clients.
The initial motivation for this draft came from a proposal from the
Mobile IPv6 working group that proposed a single-use mechanism
whereby a particular relay option would be forwarded to the client.
Subsequent independent effort in another working group has confirmed
the need for a general mechanism to do this.
1.1. Requirements Language 1.1. Requirements Language
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 RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
1.2. Terminology 1.2. Terminology
The following terms and acronyms are used in this document: The following terms and acronyms are used in this document:
skipping to change at page 5, line 37 skipping to change at page 5, line 37
the client, rather than using this mechanism to cause the server to the client, rather than using this mechanism to cause the server to
produce a message containing forged information. produce a message containing forged information.
7. IANA Considerations 7. IANA Considerations
We request that IANA assign one new option code from the registry of We request that IANA assign one new option code from the registry of
DHCP Option Codes maintained at DHCP Option Codes maintained at
http://www.iana.org/assignments/dhcpv6-parameters. This option code http://www.iana.org/assignments/dhcpv6-parameters. This option code
will be assigned to the Relay-Supplied Options option. will be assigned to the Relay-Supplied Options option.
8. Normative References 8. References
8.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., 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.
8.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.
[RFC5296] Narayanan, V. and L. Dondeti, "EAP Extensions for EAP Re-
authentication Protocol (ERP)", RFC 5296, August 2008.
Authors' Addresses Authors' Addresses
Ted Lemon Ted Lemon
Nominum Nominum
2000 Seaport Blvd 2000 Seaport Blvd
Redwood City, CA 94063 Redwood City, CA 94063
USA USA
Phone: +1 650 381 6000 Phone: +1 650 381 6000
Email: mellon@nominum.com Email: mellon@nominum.com
 End of changes. 8 change blocks. 
19 lines changed or deleted 32 lines changed or added

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