draft-ietf-dhc-dhcpv6-relay-supplied-options-07.txt   draft-ietf-dhc-dhcpv6-relay-supplied-options-08.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 12, 2012 July 11, 2011 Expires: January 13, 2012 July 12, 2011
Relay-Supplied DHCP Options Relay-Supplied DHCP Options
draft-ietf-dhc-dhcpv6-relay-supplied-options-07 draft-ietf-dhc-dhcpv6-relay-supplied-options-08
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 12, 2012. This Internet-Draft will expire on January 13, 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 5, line 17 skipping to change at page 5, line 17
5. DHCP Relay Agent Behavior 5. DHCP Relay Agent Behavior
Relay agents MAY include a Relay-Supplied Options option in the Relay agents MAY include a Relay-Supplied Options option in the
option payload of a Relay-Forward message being sent toward a DHCP option payload of a Relay-Forward message being sent toward a DHCP
server. When relaying the payload of Relay-Reply messages toward server. When relaying the payload of Relay-Reply messages toward
clients, Relay agents MUST NOT modify the payload. clients, Relay agents MUST NOT modify the payload.
Relay agents MUST NOT send non-RSOO-enabled options in the Relay- Relay agents MUST NOT send non-RSOO-enabled options in the Relay-
Supplied Options option. Supplied Options option.
Implementors of relay agents that support Relay-Supplied DHCP Options In order to allow network administrators to control the flow of RSOO
are strongly urged to implement a configuration parameter that options onto the network, relay agents that implement the Relay
determines whether or not they will relay a Relay-Forward message Supplied Options Option need to have a configuration parameter that
toward the DHCP server if it contains a Relay-Supplied Options determines to whether or not they will relay RSOO-containing Relay-
option. Forward messages.
Relay agents that have this configuration parameter and that are Relay agents that have this configuration parameter and that are
configured to disable forwarding of Relay-Forward messages that configured to disable forwarding of Relay-Forward messages that
contain a Relay-Supplied Options option MUST silently discard any contain a Relay-Supplied Options option MUST silently discard any
such message. such message.
Implementations that can be configured in this way MUST examine all Implementations that can be configured in this way MUST examine all
Relay-Forward encapsulations, not just the outer encapsulation. Relay-Forward encapsulations, not just the outer encapsulation.
6. DHCP Server Behavior 6. DHCP Server Behavior
 End of changes. 4 change blocks. 
8 lines changed or deleted 8 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/