RFC 4361
Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4), February 2006
- File formats:
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 2131, RFC 2132, RFC 3315
- Updated by:
- RFC 5494
- Authors:
- T. Lemon
B. Sommerfeld - Stream:
- IETF
- Source:
- dhc (int)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC4361
Discuss this RFC: Send questions or comments to the mailing list dhcwg@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 4361
Abstract
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]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.