Client Link-layer Address Option in DHCPv6
draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-03

The information below is for an old version of the document
Document Type Active Internet-Draft (dhc WG)
Last updated 2012-10-18
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        G. Halwasia
Internet-Draft                                               S. Bhandari
Intended status: Standards Track                                  W. Dec
Expires: April 21, 2013                                    Cisco Systems
                                                        October 18, 2012

               Client Link-layer Address Option in DHCPv6
          draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-03

Abstract

   This document specifies the format and mechanism that is to be used
   for encoding client link-layer address in DHCPv6 relay forward
   messages by defining a new DHCPv6 Client Link-layer Address option.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 21, 2013.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Halwasia, et al.         Expires April 21, 2013                 [Page 1]
Internet-Draft   DHCPv6 client link-layer address option    October 2012

   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Problem Background and Scenario . . . . . . . . . . . . . . . . 3
   3.  DHCPv6 Client Link-layer Address Option . . . . . . . . . . . . 4
   4.  DHCPv6 Relay Agent Behavior . . . . . . . . . . . . . . . . . . 4
   5.  DHCPv6 Server Behavior  . . . . . . . . . . . . . . . . . . . . 4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 5
   9.  Normative References  . . . . . . . . . . . . . . . . . . . . . 5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 6

Halwasia, et al.         Expires April 21, 2013                 [Page 2]
Internet-Draft   DHCPv6 client link-layer address option    October 2012

1.  Introduction

   This specification defines an optional mechanism and the related
   DHCPv6 option to allow first hop DHCPv6 relay agent directly
   connected to the client to populate client link-layer address in the
   DHCPv6 messages being sent towards the server.

2.  Problem Background and Scenario

   DHCPv4 protocol specification [RFC2131] provides a way to specify the
   client hardware address in the DHCPv4 message header.  DHCPv4 message
   header has 'htype' and 'chaddr' fields to specify client hardware
   address type and hardware address respectively.  The client hardware
   address thus learnt can be used by DHCPv4 server and relay in
   different ways.  In some of the deployments DHCPv4 servers use
   'chaddr' as a customer identifier and a key for lookup in the client
   lease database.

   With the incremental deployment of IPv6 to existing IPv4 networks,
   effectively an enablement of dual-stack, there will be devices that
   act as both DHCPv4 and DHCPv6 clients.  In service provider
   deployments, a typical DHCPv4 implementation will use the client
   hardware address as one of the keys to build DHCP client lease
   database.  In dual stack scenarios it is desirable for the operator
Show full document text