RFC 7969: Customizing DHCP Configuration on the Basis of Network Topology
In plain English — editorial summary, not part of the RFC
DHCP servers have evolved over the years to provide significant functionality beyond that described in the DHCP base specifications. One aspect of this functionality is support for context-specific configuration information. This memo describes some such features and explains their operation.
Document record
- Document ID
- RFC7969
- Published
- October 2016
- Authors
- T. Lemon; T. Mrugalski
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
- RFC 7839Access-Network-Identifier Option in DHCPCurrent
June 2016
- RFC 8156DHCPv6 Failover ProtocolCurrent
June 2017
- RFC 8168DHCPv6 Prefix-Length Hint IssuesCurrent
May 2017
- RFC 7653DHCPv6 Active LeasequeryCurrent
October 2015
- RFC 7598DHCPv6 Options for Configuration of Softwire Address and Port-Mapped ClientsUpdated
July 2015
- RFC 8415Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Obsoleted
November 2018
- RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent
August 2014
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?