metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 4361: Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)

Still current, but amended. Parts of this document are changed or extended by RFC 5494. Read both.

In plain English — editorial summary, not part of the RFC

This document specifies the format that is to be used for encoding Dynamic Host Configuration Protocol Version Four (DHCPv4) client identifiers, so that those identifiers will be interchangeable with identifiers used in the DHCPv6 protocol. This document also addresses and corrects some problems in RFC 2131 and RFC 2132 with respect to the handling of DHCP client identifiers. [STANDARDS-TRACK]

Document record

Document ID
RFC4361
Published
February 2006
Authors
T. Lemon; B. Sommerfeld
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
12
Also known as
—
Updates:
RFC 2131, RFC 2132, RFC 3315
Updated by:
RFC 5494

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/4361-node-specific-client-identifiers-for-dynamic-host-configuration-protocol-version