RFC 3925: Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4)
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC3925
- Published
- October 2004
- Authors
- J. Littlefield
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3736Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6Obsoleted
April 2004
- RFC 3646DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
December 2003
- RFC 3634Key Distribution Center (KDC) Server Address Sub-option for the Dynamic Host Configuration Protocol (DHCP) CableLabs Client Configuration (CCC) OptionCurrent
December 2003
- RFC 3633IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6Obsoleted
December 2003
- RFC 3594PacketCable Security Ticket Control Sub-Option for the DHCP CableLabs Client Configuration (CCC) OptionCurrent
September 2003
- RFC 3495Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client ConfigurationCurrent
March 2003
- RFC 3442The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4Current
December 2002
- RFC 3256The DOCSIS (Data-Over-Cable Service Interface Specifications) Device Class DHCP (Dynamic Host Configuration Protocol) Relay Agent Information Sub-optionCurrent
April 2002
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?