draft-ietf-dhc-dhcpv6-relay-supplied-options-08.txt   draft-ietf-dhc-dhcpv6-relay-supplied-options-09.txt 
dhc T. Lemon dhc T. Lemon
Internet-Draft Nominum Internet-Draft Nominum
Updates: 3315 (if approved) Q. Wu Updates: 3315 (if approved) Q. Wu
Intended status: Standards Track Huawei Intended status: Standards Track Huawei
Expires: January 13, 2012 July 12, 2011 Expires: March 9, 2012 September 6, 2011
Relay-Supplied DHCP Options Relay-Supplied DHCP Options
draft-ietf-dhc-dhcpv6-relay-supplied-options-08 draft-ietf-dhc-dhcpv6-relay-supplied-options-09
Abstract Abstract
DHCPv6 relay agents can not communicate with DHCPv6 clients directly. DHCPv6 relay agents can not communicate with DHCPv6 clients directly.
However, in some cases, the relay agent possesses some information However, in some cases, the relay agent possesses some information
that would be useful to the DHCPv6 client. This document describes a that would be useful to the DHCPv6 client. This document describes a
mechanism whereby the DHCPv6 relay agent can provide such information mechanism whereby the DHCPv6 relay agent can provide such information
to the DHCPv6 server, which can, in turn, pass this information on to to the DHCPv6 server, which can, in turn, pass this information on to
the DHCP client. the DHCP client.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 January 13, 2012. This Internet-Draft will expire on March 9, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 7, line 20 skipping to change at page 7, line 20
Note, however, that this will only be effective if the message from Note, however, that this will only be effective if the message from
the DHCP server to the DHCP client is authenticated as specified in the DHCP server to the DHCP client is authenticated as specified in
Section 21 of DHCP Version 6 [RFC3315], or using some similar Section 21 of DHCP Version 6 [RFC3315], or using some similar
mechanism. Without this authentication, the malicious node on the mechanism. Without this authentication, the malicious node on the
untrusted portion of the network can simply modify the DHCP server's untrusted portion of the network can simply modify the DHCP server's
response in transit back to the DHCP client, and there is no way for response in transit back to the DHCP client, and there is no way for
the client to detect that this has happened. the client to detect that this has happened.
8. IANA Considerations 8. IANA Considerations
We request that IANA assign one new registry code from the registry IANA is requested to assign one new DHCPv6 option code from the
of DHCP Option Codes maintained at registry of DHCP Option Codes maintained at
http://www.iana.org/assignments/dhcpv6-parameters. This registry http://www.iana.org/assignments/dhcpv6-parameters. The option code
code will be assigned to the Relay-Supplied Options option. OPTION_RSOO will be assigned to the Relay-Supplied Options option.
We request that the IANA create a new registry on the same IANA is also requested to create a new registry on the same
assignments page, titled "Options Permitted in the Relay-Supplied assignments page, titled "Options Permitted in the Relay-Supplied
Options Option". This option will contain a list of names of options Options Option". This registry will contain a list of DHCPv6 option
from the DHCP Option Codes list. Currently, the list is empty. codes from the DHCP Option Codes list at
http://www.iana.org/assignments/dhcpv6-parameters as suboptions of
the Relay-Supplied Options option. Currently, the list is empty.
Options may be added to this list after IETF Review[RFC5226]. Options may be added to this list after IETF Review[RFC5226].
IETF Review should include careful consideration of the security IETF Review should include careful consideration of the security
implications of allowing a relay agent to provide a value for the implications of allowing a relay agent to provide a value for the
option being considered for addition to this registry. In the case option being considered for addition to this registry. In the case
where an IETF working group chartered to review DHCP protocol where an IETF working group chartered to review DHCP protocol
extensions exists, it is not sufficient for some other working group extensions exists, it is not sufficient for some other working group
to review the registry addition. to review the registry addition.
9. References 9. References
 End of changes. 6 change blocks. 
10 lines changed or deleted 12 lines changed or added

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