RFC 7839: Access-Network-Identifier Option in DHCP
In plain English — editorial summary, not part of the RFC
This document specifies the format and mechanism that is to be used for encoding Access-Network Identifiers in DHCPv4 and DHCPv6 messages by defining new Access-Network-Identifier options and sub-options.
Document record
- Document ID
- RFC7839
- Published
- June 2016
- Authors
- S. Bhandari; S. Gundavelli; M. Grayson; B. Volz; J. Korhonen
- Status
- PROPOSED STANDARD
- 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 7969Customizing DHCP Configuration on the Basis of Network TopologyCurrent
October 2016
- RFC 7653DHCPv6 Active LeasequeryCurrent
October 2015
- RFC 7598DHCPv6 Options for Configuration of Softwire Address and Port-Mapped ClientsUpdated
July 2015
- RFC 8156DHCPv6 Failover ProtocolCurrent
June 2017
- RFC 8168DHCPv6 Prefix-Length Hint IssuesCurrent
May 2017
- RFC 8278Mobile Access Gateway (MAG) Multipath OptionsCurrent
January 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?