rfc-7563

Extensions to the Proxy Mobile IPv6 (PMIPv6) Access Network Identifier Option

R. Pazhyannur, S. Speicher, S. Gundavelli, J. Korhonen, J. Kaippallimalil
date2015-06 streamIETF areaint wgnetext statusPROPOSED STANDARD pages12 canonicalhttps://www.rfc-editor.org/rfc/rfc7563 doi10.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.

updates

Extracted elements (24)

design-rationale §1

Civic location is introduced because in indoor WLAN (AP) deployments it is difficult to determine geospatial coordinates, yet many location-based applications only require a civic address (street address or room number). The existing Geo-Location sub-option from RFC 6757 is insufficient for these deployments.

mobility, ip

design-rationale §1

The ANI Update-Timer sub-option is introduced to handle WLC (Wireless LAN Controller) deployments where the MAG is co-located with the WLC rather than individual APs. In such cases, intra-WLC AP roaming is invisible to the LMA, causing ANI information to go stale. The timer lets the LMA control how frequently it receives ANI refreshes without requiring a PBU per AP transition.

mobility, ip

design-rationale §1

The MAG-Group-Identifier is introduced to allow operators to express AP group affiliation (e.g., floor or small building), which serves as a proxy for coarse location and enables group-level policy (QoS, charging, DPI) to be applied by the LMA for all APs in the group.

mobility, ip

interoperability-note §4.1

If the MAG included ANI sub-options in its PBU but receives a successful PBA without an ANI option, the MAG may log the event and, based on local policy, terminate the mobility session, indicating the LMA does not understand the ANI option.

mobility, ip

interoperability-note §3.2

The MAG-Group-Identifier should be unique within an operator network but is not assumed globally unique. In multi-operator domains, it SHOULD be combined with the Operator-Identifier sub-option (RFC 6757) to ensure uniqueness.

mobility, ip

normative-requirement §4.2 MUST

If a received PBU does not include the Access Network Information option, the LMA updates the mobility session to remove any previously stored access network information elements.

mobility, ip

normative-requirement §4.1 MUST

If the MAG is configured to support the ANI sub-options defined in this specification, it includes the ANI option with those sub-options in all PBU messages (including lifetime-extension and deregistration PBUs) sent to the LMA.

mobility, ip

normative-requirement §4.2 MUST

On receiving a PBU with the ANI option, the LMA MUST process the option and update the corresponding fields in the Binding Cache entry. If the option is not understood, the LMA skips it and processes the PBU without those options.

mobility, ip

normative-requirement §3.1 SHOULD NOT

The civic location field in the Civic-Location sub-option SHALL NOT exceed 253 bytes.

mobility, ip

normative-requirement §4.2 SHOULD NOT

The LMA echoes back accepted ANI sub-options in the PBA. The Civic-Location and MAG-Group-Identifier sub-options SHOULD NOT be altered by the LMA; the LMA MAY change the ANI Update-Timer value.

mobility, ip

normative-requirement §3.1 MUST

The Reserved field in the Civic-Location sub-option MUST be set to zero when sending and ignored when received.

mobility, ip

normative-requirement §4.1 SHOULD

When the LMA-provided Update-Timer value in the PBA differs from the value the MAG sent in the PBU, the MAG SHOULD use the LMA-provided value.

mobility, ip

normative-requirement §4.1 MUST

When the MAG sends a PBU for any reason before the Update-Timer expires (e.g., for a QoS service request), the MAG MUST reset the Update-Timer.

mobility, ip

privacy-consideration §6

The Civic-Location sub-option is considered very sensitive as it reveals the physical location of the network to which a mobile node is attached. Care must be taken to secure PMIPv6 signaling carrying this sub-option, and provisioning location at the coarsest acceptable granularity is recommended.

privacy, mobility

protocol-element §3.3

The ANI Update-Timer sub-option allows the LMA to control how frequently the MAG sends ANI updates. The MAG proposes a value in the PBU; the LMA may echo, increase, or decrease it in the PBA. A value of 0 means the MAG sends updates immediately upon detecting ANI changes.

mobility, ip

protocol-element §3.1

The Civic-Location sub-option carries the civic address (street address or building location) of the mobile node as known to the MAG. Binary Encoding (Format=0) follows RFC 4776 Section 3.1 encoding with the first 3 DHCP-specific octets omitted, starting with a two-letter ISO 3166 country code.

mobility, ip

protocol-element §3.2

The MAG-Group-Identifier sub-option identifies the group affiliation of the MAG within its PMIPv6 domain. The group identifier is not assumed to be globally unique; operators spanning multiple domains SHOULD use it together with the Operator-Identifier sub-option from RFC 6757.

mobility, ip

registry §5

Three new type values are allocated in the IANA registry 'Access Network Information (ANI) Sub-Option Type Values': Civic-Location (type 4), MAG-Group-Identifier (type 5), and ANI Update-Timer (type 6).

registry, mobility

security-consideration §6

Access-network information elements the MAG sends may be dynamically learned over DHCP or other protocols. Without proper security (IPsec, TLS, or equivalent) on the MAG-to-access-point path, exchanged information can be compromised, leading to incorrect policy enforcement at the LMA.

security, mobility

security-consideration §6

The Civic-Location sub-option exposes sensitive civic location of the mobile node's attachment point. IPsec ESP with confidentiality and integrity protection SHOULD be used to protect this information in PMIPv6 signaling, as specified in RFC 5213. Operators may also choose to provision location only to coarse granularity (e.g., city or province level).

security, privacy, mobility

state-machine §4.1

MAG Update-Timer state machine: when ANI parameters change, if the timer has expired the MAG sends a PBU; if not expired, no PBU is sent. When the timer expires, the MAG checks for changes — if changed since last report it sends a PBU; otherwise it does not and the timer remains expired.

mobility, ip

wire-format §3.3

ANI Update-Timer Sub-Option (ANI Type=6): 1-byte ANI Type, 1-byte ANI Length (always 2), and a 16-bit unsigned integer Update-Timer in units of 4 seconds; value 0 means immediate updates on ANI change.

mobility, ip

wire-format §3.1

Civic-Location Sub-Option (ANI Type=4): 1-byte ANI Type, 1-byte ANI Length, 1-byte Format (0=Binary Encoding per RFC 4776 Section 3.1, omitting first 3 DHCP octets), 1-byte Reserved, followed by civic location data not exceeding 253 bytes.

mobility, ip

wire-format §3.2

MAG-Group-Identifier Sub-Option (ANI Type=5): 1-byte ANI Type, 1-byte ANI Length (always 2), and a 3-octet unsigned integer group identifier assigned to a group of MAGs.

mobility, ip