RFC 7563: Extensions to the Proxy Mobile IPv6 (PMIPv6) Access Network Identifier Option
In plain English — editorial summary, not part of the RFC
The Access Network Identifier (ANI) mobility option was introduced in RFC 6757, "Access Network Identifier (ANI) Option for Proxy Mobile IPv6". This enables a Mobile Access Gateway (MAG) to convey identifiers like the network identifier, geolocation, and operator identifier. This specification extends the Access Network Identifier mobility option with sub-options to carry the civic location and the MAG group identifier. This specification also defines an ANI Update-Timer sub-option that determines when and how often the ANI option will be updated.
Document record
- Document ID
- RFC7563
- Published
- June 2015
- Authors
- R. Pazhyannur; S. Speicher; S. Gundavelli; J. Korhonen; J. Kaippallimalil
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 12
- Also known as
- —
- Updates:
- RFC 6757
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7561Mapping Quality of Service (QoS) Procedures of Proxy Mobile IPv6 (PMIPv6) and WLANCurrent
June 2015
- RFC 7559Packet-Loss Resiliency for Router SolicitationsCurrent
May 2015
- RFC 7558Requirements for Scalable DNS-Based Service Discovery (DNS-SD) / Multicast DNS (mDNS) ExtensionsCurrent
July 2015
- RFC 7556Multiple Provisioning Domain ArchitectureCurrent
June 2015
- RFC 7554Using IEEE 802.15.4e Time-Slotted Channel Hopping (TSCH) in the Internet of Things (IoT): Problem StatementCurrent
May 2015
- RFC 7550Issues and Recommendations with Multiple Stateful DHCPv6 OptionsObsoleted
May 2015
- RFC 7588A Widely Deployed Solution to the Generic Routing Encapsulation (GRE) Fragmentation ProblemCurrent
July 2015
- RFC 7596Lightweight 4over6: An Extension to the Dual-Stack Lite ArchitectureCurrent
July 2015
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?