Browse Prior Art Database

Client Identifier Option in DHCP Server Replies (RFC6842)

IP.com Disclosure Number: IPCOM000224833D
Original Publication Date: 2013-Jan-01
Included in the Prior Art Database: 2013-Jan-08
Document File: 10 page(s) / 10K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

N. Swamy: AUTHOR [+3]

Abstract

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

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 27% of the total text.

Internet Engineering Task Force (IETF)                          N. Swamy Request for Comments: 6842                                 Samsung India Updates: 2131                                                G. Halwasia Category: Standards Track                                    P. Jhingran ISSN: 2070-1721                                            Cisco Systems                                                             January 2013

             Client Identifier Option in DHCP Server Replies

Abstract

   This document updates RFC 2131 "Dynamic Host Configuration Protocol"    by addressing the issues arising from that document's specification    that the server MUST NOT return the 'client identifier' option to the    client.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc6842.

Copyright Notice

   Copyright (c) 2013 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    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.

 Swamy, et al.                Standards Track                    [Page 1]
 RFC 6842                Client Identifier Option            January 2013

 Table of Contents

   1. Introduction ....................................................2       1.1. Requirements Language ......................................2    2. Problem Statement ...............................................2    3. Modification to RFC 2131 ........................................3    4. Security Considerations .........................................4    5. Acknowledgments ..............................