A new Request for Comments is now available in online RFC libraries.
RFC 7563
Title: Extensions to the Proxy Mobile IPv6 (PMIPv6)
Access Network Identifier Option
Author: R. Pazhyannur, S. Speicher,
S. Gundavelli, J. Korhonen,
J. Kaippallimalil
Status: Standards Track
Stream: IETF
Date: June 2015
Mailbox: [email protected],
[email protected],
[email protected],
[email protected],
[email protected]
Pages: 12
Characters: 27982
Updates: RFC 6757
I-D Tag: draft-ietf-netext-ani-location-09.txt
URL: https://www.rfc-editor.org/info/rfc7563
DOI: http://dx.doi.org/10.17487/RFC7563
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.
This document is a product of the Network-Based Mobility Extensions Working
Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
