Client Identifier Option in DHCP Server Replies
draft-ietf-dhc-client-id-05

The information below is for an old version of the document
Document Type Active Internet-Draft (dhc WG)
Last updated 2012-09-24 (latest revision 2012-09-10)
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state AD Evaluation
Consensus Boilerplate Unknown
Telechat date
Responsible AD Ralph Droms
IESG note Ted Lemon (Ted.Lemon@nominum.com) is the Document Shepherd.
Send notices to dhc-chairs@tools.ietf.org, draft-ietf-dhc-client-id@tools.ietf.org
DHC Working Group                                               N. Swamy
Internet-Draft                                             Samsung India
Updates: 2131 (if approved)                                  G. Halwasia
Intended status: Standards Track                             P. Jhingran
Expires: March 15, 2013                                    Cisco Systems
                                                      September 11, 2012

            Client Identifier Option in DHCP Server Replies
                      draft-ietf-dhc-client-id-05

Abstract

   This document updates RFC2131 [RFC2131].  The changes to [RFC2131]
   defined in this draft clarifies the use of 'client identifier' option
   by the DHCP servers.  The clarification addresses the issues arising
   out of the point specified by [RFC2131] that the server 'MUST NOT'
   return client identifier' option to the client.

Requirements

   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 [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 March 15, 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

Swamy, et al.            Expires March 15, 2013                 [Page 1]
Internet-Draft          Client Identifier Option          September 2012

   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
   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 Statement . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Proposed Modification To [RFC2131]  . . . . . . . . . . . . . . 4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 5
   7.  Normative References  . . . . . . . . . . . . . . . . . . . . . 5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 5

Swamy, et al.            Expires March 15, 2013                 [Page 2]
Internet-Draft          Client Identifier Option          September 2012

1.  Introduction

   The Dynamic Host Configuration Protocol (DHCP) defined in [RFC2131]
   provides configuration parameters to hosts on a TCP/IP based network.
   DHCP is built on a client-server model, where designated DHCP server
   allocate network addresses and deliver configuration parameters to
   dynamically configured hosts.

   The changes to [RFC2131] defined in this document clarifies the use
   of 'client identifier' option by the DHCP servers.  The clarification
   addresses the issues (as mentioned in Problem Statement) arising out
   of the point specified by [RFC2131] that the server 'MUST NOT' return
   client identifier' option to the client.

2.  Problem Statement

   [RFC2131] specifies that a combination of 'client identifier' or
   'chaddr' and assigned network address constitute a unique identifier
   for the client's lease and are used by both the client and server to
   identify a lease referred in any DHCP messages.  [RFC2131] also
   specifies that the server "MUST NOT" return 'client identifier' in
   DHCPOFFER and DHCPACK messages.  DHCP relay agents and servers,
   following these recommendations MAY drop the DHCP packets in the
   absence of both 'client identifier' and 'chaddr'.

   In some cases, client may not be having valid hardware address value
   to be filled in 'chaddr' field of the packet and hence may set this
   field as zero.  One such example is when DHCP is used to assign IP
   address to a mobile phone or a tablet and where the 'chaddr' field is
   set to zero in DHCP request packets.  In such cases, client usually
Show full document text