draft-ietf-dhc-dhcpv6-relay-supplied-options-03.txt   draft-ietf-dhc-dhcpv6-relay-supplied-options-04.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: April 14, 2011 Huawei Expires: April 18, 2011 Huawei
October 11, 2010 October 15, 2010
Relay-Supplied DHCP Options Relay-Supplied DHCP Options
draft-ietf-dhc-dhcpv6-relay-supplied-options-03 draft-ietf-dhc-dhcpv6-relay-supplied-options-04
Abstract Abstract
This document describes a mechanism whereby a DHCPv6 relay agent can This document describes a mechanism whereby a DHCPv6 relay agent can
provide options to a DHCPv6 server that the DHCPv6 server can then provide options to a DHCPv6 server that the DHCPv6 server can then
provide to the DHCPv6 client in certain restricted cases where this provide to the DHCPv6 client in certain restricted cases where this
is necessary. is necessary.
Status of this Memo Status of this Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 April 14, 2011. This Internet-Draft will expire on April 18, 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 4, line 17 skipping to change at page 4, line 17
In order to supply options for the DHCP server to send to the client, In order to supply options for the DHCP server to send to the client,
the relay agent sends a Relay-Supplied Options option in the Relay- the relay agent sends a Relay-Supplied Options option in the Relay-
Forward message. This option encapsulates whatever options the relay Forward message. This option encapsulates whatever options the relay
agent wishes to provide to the DHCPv6 server. agent wishes to provide to the DHCPv6 server.
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_RSOO | option-length | | OPTION_RSOO | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| suboptions... | options...
+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+
OPTION_RSOO Relay-Supplied Options code (TBD). OPTION_RSOO Relay-Supplied Options code (TBD).
option-length Length of Relay-Supplied Options option. option-length Length of Relay-Supplied Options option.
suboptions One or more DHCPv6 options. options One or more DHCPv6 options.
4. RSOO-enabled options 4. RSOO-enabled options
Unless specifically called out as an RSOO-enabled option, no DHCP Unless specifically called out as an RSOO-enabled option, no DHCP
option should appear in an RSOO. Specifications that describe RSOO- option should appear in an RSOO. Specifications that describe RSOO-
enabled options MUST reference this specification, and MUST state enabled options MUST reference this specification, and MUST state
that the option they define is RSOO-enabled. No DHCP option that the option they define is RSOO-enabled. No DHCP option
specified prior to the issuance of this specification is RSOO- specified prior to the issuance of this specification is RSOO-
enabled. enabled.
skipping to change at page 6, line 11 skipping to change at page 6, line 11
Aside from the addition of options from the RSOO, the DHCP server Aside from the addition of options from the RSOO, the DHCP server
should then construct a DHCP packet as it normally would, and should then construct a DHCP packet as it normally would, and
transmit it to the DHCP client as described in DHCPv6 [RFC3315]. transmit it to the DHCP client as described in DHCPv6 [RFC3315].
DHCP servers may receive multiply-nested Relay-Forward messages DHCP servers may receive multiply-nested Relay-Forward messages
containing conflicting values for options contained in Relay Supplied containing conflicting values for options contained in Relay Supplied
Options options in these messages. Options options in these messages.
When such a conflict exists, the DHCP server MUST choose no more than When such a conflict exists, the DHCP server MUST choose no more than
one of these options to forward to the client. The DHCP server MUST one of these options to forward to the client. The DHCP server MUST
not forward more than one of these options to the client. NOT forward more than one of these options to the client.
By default, the DHCP server MUST choose the innermost value--the By default, the DHCP server MUST choose the innermost value--the
value supplied by the relay agent closest to the DHCP client, to value supplied by the relay agent closest to the DHCP client, to
forward to the DHCP client. forward to the DHCP client.
DHCP server implementations MAY provide other heuristics for choosing DHCP server implementations MAY provide other heuristics for choosing
which one of a set of such conflicting options to forward to the which one of a set of such conflicting options to forward to the
client, as long as the specified behavior is the default behavior. client, as long as the specified behavior is the default behavior.
7. Security Considerations 7. Security Considerations
 End of changes. 6 change blocks. 
7 lines changed or deleted 7 lines changed or added

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