RFC 3396: Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4)
In plain English — editorial summary, not part of the RFC
This document specifies the processing rules for DHCPv4 options that appear multiple times in the same message. Multiple instances of the same option are generated when an option exceeds 255 octets in size (the maximum size of a single option) or when an option needs to be split apart in order to take advantage of DHCP option overloading. When multiple instances of the same option appear in the options, file and/or sname fields in a DHCP packet, the contents of these options are concatenated together to form a single option prior to processing.
Document record
- Document ID
- RFC3396
- Published
- November 2002
- Authors
- T. Lemon; S. Cheshire
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 9
- Also known as
- —
- Updates:
- RFC 2131
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3527Link Selection sub-option for the Relay Agent Information Option for DHCPv4Current
April 2003
- RFC 3456Dynamic Host Configuration Protocol (DHCPv4) Configuration of IPsec Tunnel ModeCurrent
January 2003
- RFC 3442The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4Current
December 2002
- RFC 3495Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client ConfigurationCurrent
March 2003
- RFC 3256The DOCSIS (Data-Over-Cable Service Interface Specifications) Device Class DHCP (Dynamic Host Configuration Protocol) Relay Agent Information Sub-optionCurrent
April 2002
- RFC 3594PacketCable Security Ticket Control Sub-Option for the DHCP CableLabs Client Configuration (CCC) OptionCurrent
September 2003
- RFC 3633IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6Obsoleted
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
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?