Version

Diameter Proxy Mobile IPv6 [RFC5779] AVPs

Diameter Proxy Mobile IPv6 (RFC5779)

This interface defines the AAA interactions required in a Proxy Mobile IPv6 (PMIPv6) domain, detailing how a Mobile Access Gateway (MAG) and a Local Mobility Anchor (LMA) interact with a AAA server—referred to as the home AAA (HAAA) server—to download and update mobile node (MN) specific policy profile information. Leveraging the Diameter protocol [RFC3588], this specification supports dynamic assignment of policy profiles, thus simplifying deployment and maintenance in large PMIPv6 networks.

Purpose of the Diameter Proxy Mobile IPv6 Interface

  • Dynamic Policy Profile Management: The interface enables the MAG to download MN-specific policy profile information from a remote policy store co-located with the HAAA server. This functionality is crucial for ensuring that the MAG receives the necessary parameters to manage the mobility session of an authenticated MN.
  • AAA-Based Session Management: Once the network authenticates an MN using an access authentication procedure (potentially based on EAP [RFC3748]), the MAG initiates a mobility session by sending a Proxy Binding Update (PBU) to the LMA. The LMA, in turn, utilizes Diameter-based AAA interactions to authorize the PBU and update the subscriber’s mobility session details in the remote policy store.
  • Integrated Network Access and Mobility Support: By using the same AAA infrastructure for both network access authentication and mobility session management, the solution streamlines operations and reduces administrative overhead within the PMIPv6 domain.

Key Elements and Operational Workflow

MAG-to-HAAA Interaction:

  • During the MN’s network attachment, the MAG (acting as a NAS) queries the HAAA using the Diameter protocol. If the subscriber is authorized for PMIPv6 service, the HAAA returns PMIPv6-specific policy profile information along with the network access authentication answer. This dynamic download of policy profiles eases the operational management of PMIPv6 domains.

LMA-to-HAAA Interaction:

  • After a successful authentication, the MAG sends a Proxy Binding Update (PBU) to the LMA. The LMA then interacts with the HAAA to fetch the relevant parts of the subscriber’s policy profile and additional authorization information required for establishing and managing the MN’s mobility session. In this context, the HAAA serves as the remote policy store.

Network Entities:

  • Home AAA (HAAA) & Policy Store: Co-located to provide centralized policy management and AAA functionality.
  • Local Mobility Anchor (LMA): Receives PBUs from MAGs, fetches policy profiles from the HAAA, and authorizes mobility sessions.
  • Mobile Access Gateway (MAG): Acts as the NAS at the network access router, initiating AAA requests and conveying MN-specific policy information.
  • Mobile Node (MN): Attaches to the PMIPv6 domain, triggering the AAA-based procedures for authentication and mobility session establishment.

For complete technical specification of Diameter Proxy Mobile IPv6 please refer to: [RFC5779]

package com.mobius.software.telco.protocols.diameter.primitives.rfc5779

Name

AVP Code

Data Type

Vendor

Mobile-Node-Identifier

506

UTF8String

IETF

Contains the identifier of a mobile node in Network Access Identifier (NAI) format as defined in [RFC4282]. This AVP is primarily used in Proxy Binding Update (PBU) and Proxy Binding Acknowledgment (PBA) exchanges on the MAG-to-HAAA interface.

The HAAA includes this AVP in the response of a successful authentication or authorization exchange, providing the MAG with the MN-Identifier.

If the MAG has not obtained the MN-Identifier by other means, it must use the identifier provided in this AVP.

If the MAG already has a valid MN-Identifier, it must silently discard the received MN-Identifier from this AVP.

PMIP6-DHCP-Server-Address

504

Address

IETF

Contains the IP address of a Dynamic Host Configuration Protocol (DHCP) server assigned to the Mobile Access Gateway (MAG) serving the newly attached Mobile Node (MN). This AVP supports deployments where the MAG acts as a DHCP Relay, enabling interaction between the MN and the DHCP server.

If the AVP specifies a DHCPv4 server address, the Address type must be IPv4 as per [RFC2131].

If the AVP specifies a DHCPv6 server address, the Address type must be IPv6 as per [RFC3315].

The Home AAA (HAAA) may assign the DHCP server to the MAG as part of the provisioning process, ensuring the MAG has the necessary network configuration details for the MN.

PMIP6-IPv4-Home-Address

505

Address (IPv4)

IETF

Used in Proxy Mobile IPv6 (PMIPv6) to carry the IPv4 Mobile Node Home Address (IPv4-MN-HoA) between the Home AAA (HAAA) and the Mobile Access Gateway (MAG). This AVP should be present only when the Mobile Node (MN) is statically provisioned with an IPv4-MN-HoA.

If the HAAA proactively assigns the IPv4-MN-HoA, the assignment might result in unnecessary reservation of resources, as the MN might delay or bypass its IPv4 configuration process.

This AVP is used on the LMA-to-HAAA interface when the Local Mobility Anchor (LMA) delegates the assignment of the IPv4-MN-HoA to the HAAA.

If the LMA delegates the address assignment, the AVP will contain an all-zero IPv4 address (0.0.0.0) in the request, and the HAAA will return the assigned IPv4-MN-HoA in the response.

Service-Configuration

507

Grouped

IETF

Used in the Diameter protocol to communicate service configurations between the Home AAA (HAAA) and the Mobile Access Gateway (MAG). It is typically used in Proxy Mobile IPv6 (PMIPv6) scenarios to convey the Mobile Node's (MN) subscribed services and the Local Mobility Anchor (LMA) where those services are hosted.

The AVP structure is defined as follows:

MIP6-Agent-Info: Carries information about the MIP6 agent.

Service-Selection: Contains a string identifying the service selected for the MN.

 

 

Start innovating with Mobius

What's next? Let's talk!

Mobius Software

As a company you'll get:

  • Get started quickly

  • Support any business model

  • Join millions of businesses

Questions? websupport@mobius.com