Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four
RFC 4361, “Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four”, is a Proposed Standard document published in February 2006 by T. Lemon, B. Sommerfeld. It updates RFC 2131, RFC 2132, RFC 3315. It has since been updated by RFC 5494. The canonical text is published by the RFC Editor.
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 4361 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4360 BGP Extended Communities Attribute
- RFC 4362 RObust Header Compression : A Link-Layer Assisted Profile for IP/UDP/RTP
- RFC 4359 The Use of RSA/SHA-1 Signatures within Encapsulating Security Payload and Authentication Header
- RFC 4363 Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN Extensions
- RFC 4358 A Uniform Resource Name Namespace for the Open Mobile Alliance
- RFC 4364 BGP/MPLS IP Virtual Private Networks
- RFC 4357 Additional Cryptographic Algorithms for Use with GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 Algorithms
- RFC 4365 Applicability Statement for BGP/MPLS IP Virtual Private Networks