draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-02.txt   draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-03.txt 
Network Working Group G. Halwasia Network Working Group G. Halwasia
Internet-Draft S. Bhandari Internet-Draft S. Bhandari
Intended status: Standards Track W. Dec Intended status: Standards Track W. Dec
Expires: March 25, 2013 Cisco Systems Expires: April 21, 2013 Cisco Systems
September 21, 2012 October 18, 2012
Client Link-layer Address Option in DHCPv6 Client Link-layer Address Option in DHCPv6
draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-02 draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-03
Abstract Abstract
This document specifies the format and mechanism that is to be used This document specifies the format and mechanism that is to be used
for encoding client link-layer address in DHCPv6 relay forward for encoding client link-layer address in DHCPv6 relay forward
messages by defining a new DHCPv6 Client Link-layer Address option. messages by defining a new DHCPv6 Client Link-layer Address option.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 25, 2013. This Internet-Draft will expire on April 21, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 6 skipping to change at page 5, line 6
behavior can depend on configuration that decides whether Client behavior can depend on configuration that decides whether Client
Link-layer Address option needs to be processed and included. Link-layer Address option needs to be processed and included.
5. DHCPv6 Server Behavior 5. DHCPv6 Server Behavior
If DHCPv6 Server is configured to store or use client link-layer If DHCPv6 Server is configured to store or use client link-layer
address, it SHOULD look for the client link-layer address option in address, it SHOULD look for the client link-layer address option in
the RELAY-FORW DHCP message of the DHCPv6 Relay agent closest to the the RELAY-FORW DHCP message of the DHCPv6 Relay agent closest to the
client. This specification does not specify the mechanism for DHCPv6 client. This specification does not specify the mechanism for DHCPv6
Server to find out link-layer address of the directly connected Server to find out link-layer address of the directly connected
clients as a DHCP option as it can obtain it directly from the clients as a DHCP option as it can obtain it directly from the link-
received message. layer source address of the received DHCPv6 message.
There is no requirement that a server return this option and its data There is no requirement that a server return this option and its data
in a downstream DHCP message. in a downstream DHCP message.
6. IANA Considerations 6. IANA Considerations
IANA is requested to assign an option code to IANA is requested to assign an option code to
OPTION_CLIENT_LINKLAYER_ADDR from the "DHCPv6 and DHCPv6 options" OPTION_CLIENT_LINKLAYER_ADDR from the "DHCPv6 and DHCPv6 options"
registry (http://www.iana.org/assignments/dhcpv6-parameters/dhcpv6- registry (http://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-
parameters.xml). parameters.xml).
 End of changes. 4 change blocks. 
6 lines changed or deleted 6 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/