draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-01.txt   draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-02.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: February 15, 2013 Cisco Systems Expires: March 25, 2013 Cisco Systems
August 14, 2012 September 21, 2012
Client Link-layer Address Option in DHCPv6 Client Link-layer Address Option in DHCPv6
draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-01 draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-02
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 February 15, 2013. This Internet-Draft will expire on March 25, 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 3, line 41 skipping to change at page 3, line 41
operator such as the client hardware address. operator such as the client hardware address.
Currently, the DHCPv6 protocol specification [RFC3315] does not Currently, the DHCPv6 protocol specification [RFC3315] does not
define a way for DHCP clients to specify client link-layer address in define a way for DHCP clients to specify client link-layer address in
the DHCPv6 message sent towards DHCPv6 Server. Similarly DHCPv6 the DHCPv6 message sent towards DHCPv6 Server. Similarly DHCPv6
Relay or Server cannot glean client link-layer address from the Relay or Server cannot glean client link-layer address from the
contents of DHCPv6 message received. DHCPv6 protocol specification contents of DHCPv6 message received. DHCPv6 protocol specification
mandates all clients to prepare and send DUID as the client mandates all clients to prepare and send DUID as the client
identifier option in all the DHCPv6 message exchange. However none identifier option in all the DHCPv6 message exchange. However none
of these methods provide a simple way to extract client's link-layer of these methods provide a simple way to extract client's link-layer
address.This presents a problem to an operator who is using an address. This presents a problem to an operator who is using an
existing DHCPv4 system with the client hardware address as the existing DHCPv4 system with the client hardware address as the
customer identifier, and desires to correlate DHCPv6 assignments customer identifier, and desires to correlate DHCPv6 assignments
using the same identifier. Modifying the system to use DUID based using the same identifier. Modifying the system to use DUID based
correlation across DHCPv4 and DHCPv6 is possible, but it requires a correlation across DHCPv4 and DHCPv6 is possible, but it requires a
modification of the DHCPv4 system and associated back-ends. modification of the DHCPv4 system and associated back-ends.
Providing an option in DHCPv6 relay forward messages to carry client Providing an option in DHCPv6 relay forward messages to carry client
link-layer address explicitly will help above mentioned scenarios. link-layer address explicitly will help above mentioned scenarios.
For e.g. it can be used along with other identifiers to associate For e.g. it can be used along with other identifiers to associate
DHCPv4 and DHCPv6 messages from a dual stack client. Further, having DHCPv4 and DHCPv6 messages from a dual stack client. Further, having
skipping to change at page 4, line 34 skipping to change at page 4, line 34
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: OPTION_CLIENT_LINKLAYER_ADDR (TBD) option-code: OPTION_CLIENT_LINKLAYER_ADDR (TBD)
option-length: 2 + length of link-layer address option-length: 2 + length of link-layer address
hardware type: Client Link-layer address type. The hardware type MUST be a hardware type: Client Link-layer address type. The hardware type MUST be a
valid hardware type assigned by the IANA, as described in [RFC0826] valid hardware type assigned by the IANA, as described in [RFC0826]
link-layer address: Client Link-layer address. link-layer address: Client Link-layer address.
4. DHCPv6 Relay Agent Behavior 4. DHCPv6 Relay Agent Behavior
DHCPv6 Relay agents which are directly connected to clients/hosts MAY DHCPv6 Relay agents which receive messages originating from clients
include client link-layer address option in relayed DHCPv6 (RELAY- (for example Solicit and Request, but not, for example, Relay Forward
FORW) message. The DHCPv6 Relay agent behaviour can depend on or Advertise) MAY include the link-layer source address of the
configuration that decides whether Client Link-layer Address option received DHCPv6 message in Client Link-layer Address option in
needs to be processed and included. relayed DHCPv6 Relay Forward messages. The DHCPv6 Relay agent
behavior can depend on configuration that decides whether Client
In Relay chaining scenarios, any other relay agent other than first Link-layer Address option needs to be processed and included.
hop DHCPv6 Relay agent or DHCPv6 LDRA [RFC6221] MUST not add this
option.
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. client. This specification does not specify the mechanism for DHCPv6
Server to find out link-layer address of the directly connected
clients as a DHCP option as it can obtain it directly from the
received 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).
7. Security Considerations 7. Security Considerations
Security issues related DHCPv6 are described in section 23 of Security issues related DHCPv6 are described in section 23 of
[RFC3315]. [RFC3315].
8. Acknowledgements 8. Acknowledgements
Many thanks to Bernie Volz, Hemant Singh, Simon Hobson, Tina TSOU, Many thanks to Ted Lemon, Bernie Volz, Hemant Singh, Simon Hobson,
Andre Kostur, Chuck Anderson, Steinar Haug, Niall O'Reilly, Jarrod Tina TSOU, Andre Kostur, Chuck Anderson, Steinar Haug, Niall
Johnson, Tomek Mrugalski and Vincent Zimmer for their input and O'Reilly, Jarrod Johnson, Tomek Mrugalski and Vincent Zimmer for
review. their input and review.
9. Normative References 9. Normative References
[RFC0826] Plummer, D., "Ethernet Address Resolution Protocol: Or [RFC0826] Plummer, D., "Ethernet Address Resolution Protocol: Or
converting network protocol addresses to 48.bit Ethernet converting network protocol addresses to 48.bit Ethernet
address for transmission on Ethernet hardware", STD 37, address for transmission on Ethernet hardware", STD 37,
RFC 826, November 1982. RFC 826, November 1982.
[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.
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", [RFC2131] Droms, R., "Dynamic Host Configuration Protocol",
RFC 2131, March 1997. RFC 2131, 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.
[RFC6221] Miles, D., Ooghe, S., Dec, W., Krishnan, S., and A.
Kavanagh, "Lightweight DHCPv6 Relay Agent", RFC 6221,
May 2011.
Authors' Addresses Authors' Addresses
Gaurav Halwasia Gaurav Halwasia
Cisco Systems Cisco Systems
Cessna Business Park, Sarjapura Marathalli Outer Ring Road Cessna Business Park, Sarjapura Marathalli Outer Ring Road
Bangalore, KARNATAKA 560 087 Bangalore, KARNATAKA 560 087
India India
Phone: +91 80 4426 1321 Phone: +91 80 4426 1321
Email: ghalwasi@cisco.com Email: ghalwasi@cisco.com
 End of changes. 8 change blocks. 
24 lines changed or deleted 20 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/