RFC 6842: Client Identifier Option in DHCP Server Replies
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6842
- Published
- January 2013
- Authors
- N. Swamy; G. Halwasia; P. Jhingran
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 5
- Also known as
- —
- Updates:
- RFC 2131
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6840Clarifications and Implementation Notes for DNS Security (DNSSEC)Updated
February 2013
- RFC 6853DHCPv6 Redundancy Deployment ConsiderationsCurrent
February 2013
- RFC 6864Updated Specification of the IPv4 ID FieldCurrent
February 2013
- RFC 6874Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource IdentifiersObsoleted
February 2013
- RFC 6887Port Control Protocol (PCP)Updated
April 2013
- RFC 6891Extension Mechanisms for DNS (EDNS(0))Current
April 2013
- RFC 6895Domain Name System (DNS) IANA ConsiderationsCurrent
April 2013
- RFC 6788The Line-Identification OptionCurrent
November 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?