Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4
RFC 3925, “Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4”, is a Proposed Standard document published in October 2004 by J. Littlefield. The canonical text is published by the RFC Editor.
Abstract
The Dynamic Host Configuration Protocol (DHCP) options for Vendor Class and Vendor-Specific Information can be limiting or ambiguous when a DHCP client represents multiple vendors. This document defines two new options, modeled on the IPv6 options for vendor class and vendor-specific information, that contain Enterprise Numbers to remove ambiguity. [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 3925 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3924 Cisco Architecture for Lawful Intercept in IP Networks
- RFC 3926 FLUTE - File Delivery over Unidirectional Transport
- RFC 3923 End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol
- RFC 3922 Mapping the Extensible Messaging and Presence Protocol to Common Presence and Instant Messaging
- RFC 3928 Lightweight Directory Access Protocol Client Update Protocol
- RFC 3921 Extensible Messaging and Presence Protocol : Instant Messaging and Presence
- RFC 3929 Alternative Decision Making Processes for Consensus-Blocked Decisions in the IETF
- RFC 3920 Extensible Messaging and Presence Protocol : Core