wdiff draft-ietf-dime-pmip6-02.txt draft-ietf-dime-pmip6-03.txt

Diameter Maintenance and J. Korhonen, Ed.
Extensions (DIME) Nokia Siemens Network
Internet-Draft J. Bournelle
Intended status: Standards Track Orange Labs
Expires: October 18, 2009 February 25, 2010 K. Chowdhury
Starent Networks
A. Muhanna
Nortel
U. Meyer
RWTH Aachen
April 16,
August 24, 2009

Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility
Anchor Interaction with Diameter Server
draft-ietf-dime-pmip6-02.txt
draft-ietf-dime-pmip6-03.txt

Status of this Memo

This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."

The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.

This Internet-Draft will expire on October 18, 2009. February 25, 2010.

This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).

Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.

Abstract

This specification defines the Diameter support for the Proxy Mobile
IPv6 Authentication, Authorization, and the corresponding mobility service session setup. The
policy information needed by the
Accounting interactions between Proxy Mobile IPv6 is defined in
mobile node's policy profile, which could be downloaded from the
Diameter server to the entities (both
Mobile Access Gateway once the mobile node
attaches to and Local Mobility Anchor) and an
Authentication, Authorization, and Accounting server within a Proxy
Mobile IPv6 Domain Domain. These Authentication, Authorization, and
Accounting interactions are primarily used to download and performs access
authentication. During the binding update exchange
mobile node specific policy profile information between the Proxy Mobile Access Gateway
IPv6 entities and the Local Mobility Anchor, the Local
Mobility Anchor can interact with the Diameter server in order to
update the a remote policy store with the mobility session related
information. store.

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 4
3. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 5
4. Attribute Value Pair Definitions . Generic Application Support and Command Codes . . . . . . . . 7
4.1. MAG-to-HAAA Interface . . . . . . 7
4.1. MIP6-Agent-Info AVP . . . . . . . . . . . . 7
4.2. LMA-to-HAAA Interface . . . . . . . 7
4.2. PMIP6-IPv4-Home-Address AVP . . . . . . . . . . . 7
5. Attribute Value Pair Definitions . . . . 7
4.3. MIP6-Home-Link-Prefix AVP . . . . . . . . . . . 8
5.1. MIP6-Agent-Info AVP . . . . . 8
4.4. PMIP6-DHCP-Server-Address AVP . . . . . . . . . . . . . . 8
4.5. MIP6-Feature-Vector
5.2. PMIP6-IPv4-Home-Address AVP . . . . . . . . . . . . . . . . . 8
4.6. Mobile-Node-Identifier 9
5.3. MIP6-Home-Link-Prefix AVP . . . . . . . . . . . . . . . . 9
4.7. Calling-Station-Id
5.4. PMIP6-DHCP-Server-Address AVP . . . . . . . . . . . . . . . . . . 9
4.8. Service-Selection 10
5.5. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . . . . 10
4.9. Service-Configuration
5.6. Mobile-Node-Identifier AVP . . . . . . . . . . . . . . . . 10
5. Application Support and Command Codes . . 11
5.7. Calling-Station-Id AVP . . . . . . . . . . 11
5.1. MAG-to-HAAA Interface . . . . . . . . 11
5.8. Service-Selection AVP . . . . . . . . . . 11
5.2. LMA-to-HAAA Interface . . . . . . . . 11
5.9. Service-Configuration AVP . . . . . . . . . . 11
5.2.1. Authorization of the Proxy Binding Update . . . . . . 12
6. Proxy Mobile IPv6 Session Management . . . . . . . . . . . . . 12
6.1. Session-Termination-Request . . . . . . . . . . . . . . . 13
6.2. Session-Termination-Answer . . . . . . . . . . . . . . . . 13
6.3. Abort-Session-Request . . . . . . . . . . . . . . . . . . 13
6.4. Abort-Session-Answer . . . . . . . . . . . . . . . . . . . 13
7. Attribute Value Pair Occurrence Tables . . . . . . . . . . . . 13
7.1. MAG-to-HAAA Interface . . . . . . . . . . . . . . . . . . 14
7.2. LMA-to-HAAA Interface . . . . . . . . . . . . . . . . . . 14
8. Example Signaling Flows . . . . . . . . . . . . . . . . . . . 14
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
9.1. Attribute Value Pair Codes . . . . . . . . . . . . . . . . 16
9.2. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 16 17
9.3. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 16 17
10. Security Considerations . . . . . . . . . . . . . . . . . . . 16 17
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
12.1. Normative References . . . . . . . . . . . . . . . . . . . 17
12.2. Informative References . . . . . . . . . . . . . . . . . . 17 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 19

1. Introduction

In the Proxy Mobile IPv6 (PMIPv6) protocol [RFC5213]

This specification defines Authentication, Authorization, and IPv4 support
for Proxy Mobile IPv6 [I-D.ietf-netlmm-pmip6-ipv4-support]
Accounting (AAA) interactions between a Mobile Access Gateway (MAG) performs a proxy registration with
and an AAA server, and between a Local Mobility Anchor (LMA) on behalf of the mobile node (MN). In order to
perform the proxy registration the MAG needs the IP address of the
LMA, possibly MN's Home Network Prefix(es) (MN-HNP), MN's IPv4 home
address (IPv4-MN-HoA), DHCP server address and other PMIPv6 specific
information such as the allowed address configuration modes and
roaming related policies. All this information is defined in MN's
policy profile that gets downloaded from the Diameter an
AAA server to the
MAG once the MN attaches to the MAG's within a Proxy Mobile IPv6 (PMIPv6) Domain
(PMIPv6 Domain) [RFC5213].
These AAA interactions are primarily used to download and performs the access authentication. update
mobile node (MN) specific policy profile information between PMIPv6
entities (a MAG and a LMA) and a remote policy store.

Dynamic assignment and downloading of PMIPv6 MN's policy profile information
to a MAG from a remote policy store is a desirable feature to ease
the deployment and network maintenance of larger PMIPv6 deployments. domains. For
this purpose, the
Authentication, Authorization, and Accounting (AAA) infrastructure,
which same AAA infrastructure that is used for access authentication,
authenticating and authorizing the MN for a network access, can be
leveraged to assign download some or all of the necessary parameters. The Diameter server in the
Mobility Service authorizer's (MSA) network may return these
parameters policy profile
information to the Network Access Server (NAS). MAG.

Once the MN authenticates to the network has authenticated the MN, the MAG sends a Proxy
Binding Update (PBU) towards to the LMA in order to setup a mobility session
on behalf of the MN. When the LMA receives the PBU, the LMA may need
to authorize the received PBU against the AAA infrastructure. The
same AAA infrastructure that can be used for the authorization of the
PBU, is also used to update the remote policy store located in the MSA with the MN's LMA
provided MN specific mobility session related information.

This specification defines the Diameter support for PMIPv6.

In the context of this specification the location of the subscriber policy
profile equals to the home Diameter server, which is also referred as
the home AAA server (HAAA). (HAAA)
functionality is co-located with the remote policy store. The NAS
functionality of the MAG may be co-located or an integral part of with the MAG. MAG function in the network
access router. Diameter [RFC3588] is the used AAA protocol.

2. Terminology and Abbreviations

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119 [RFC2119].

The general terminology used in this document can be found in
[RFC5213] and [I-D.ietf-netlmm-pmip6-ipv4-support]. The following
additional or clarified terms are also used in this document:

Network Access Server (NAS):

A device that provides an access service for a user to a network.
In the context of this document the NAS may be integrated into or
co-located to a MAG. The NAS contains a Diameter client function.

Home AAA (HAAA):

An Authentication, Authorization, and Accounting (AAA) server
located in user's home network. A HAAA is essentially a Diameter
server.

3. Solution Overview

This document addresses the AAA interactions and AAA-based session
management functionality needed in the PMIPv6 Domain. This document
defines Diameter based AAA interactions between the MAG and the HAAA,
and between the LMA and the HAAA.

The policy profile is downloaded from the HAAA to the MAG during the
MN attachment to the PMIPv6 Domain. Figure 1 shows the participating
network entities. This document, however, concentrates on the MAG,
LMA, and the HAAA (the home Diameter server. server).

+--------+
| HAAA & | Diameter +-----+
| Policy |<---(2)-->| LMA |
| Profile| Store | +-----+
+--------+ | <--- LMA-Address
^ |
| // \\
+---|------------- //---\\----------------+
( | IPv4/IPv6 // \\ )
( | Network // \\ )
+---|-----------//---------\\-------------+
| // \\
Diameter // <- Tunnel1 \\ <- Tunnel2
(1) // \\
| |- MAG1-Address |- MAG2-Address
| +----+ +----+
+---->|MAG1| |MAG2|
+----+ +----+
| |
| |
[MN1] [MN2]

Legend:

(1): MAG-to-HAAA interaction is described
in Section 5.1
(2): LMA-to-HAAA interaction is described
in Section 5.2

Figure 1: Proxy Mobile IPv6 Domain Interaction with Diameter HAAA
Server

When a MN attaches to a PMIPv6 Domain, a network access
authentication procedure is usually started. The choice of the
authentication mechanism is specific to the access network
deployment, but could be based on the Extensible Authentication
Protocol (EAP) [RFC3748]. During the network access authentication
procedure, the MAG acting as a NAS queries the HAAA through the AAA
infrastructure using the Diameter protocol. If the HAAA detects that
the subscriber is also authorized for the PMIPv6 service, PMIPv6
specific information is returned along with the successful network
access authentication answer to the MAG.

After the MN has been successfully authenticated, the MAG sends a PBU
to the LMA based on the MN's policy profile information. Upon
receiving the PBU the LMA interacts with the HAAA and fetches the
relevant parts of the subscriber policy profile and authorization
information related to the mobility service session. In this
specification, the HAAA has the role of the PMIPv6 remote policy
store.

4. Attribute Value Pair Definitions

This section describes Attribute Value Pairs (AVPs) defined by this Generic Application Support and Command Codes

This specification does not define new Application-IDs or re-used from existing specifications in Command
Codes for the MAG-to-HAAA or for the LMA-to-HAAA Diameter
connections. Rather, this specification is generic to any Diameter
application (and their commands) that is suitable for a PMIPv6
specific way. network
access authentication and authorization. Example applications
include NASREQ [RFC4005] and EAP [RFC4072].

4.1. MIP6-Agent-Info AVP

The MIP6-Agent-Info grouped AVP (AVP Code 486) is defined in
[RFC5447]. MAG-to-HAAA Interface

The AVP is MAG-to-HAAA interactions are primarily used to carry LMA addressing related
information for bootstrapping
PMIPv6 mobility service session when a MN attaches and authenticates
to a MN-HNP. PMIPv6 Domain. This specification extends the MIP6-Agent-
Info with the PMIP6-IPv4-Home-Address AVP using includes the Diameter
extensibility rules defined in [RFC3588]. bootstrapping of PMIPv6
session related information. The PMIP6-IPv4-Home-
Address AVP contains the IPv4-MN-HoA. same interface may also be used for
accounting. The extended MIP6-Agent-Info AVP results MAG acts as a Diameter client.

Whenever the MAG sends a Diameter request message to the following grouped
AVP:

MIP6-Agent-Info ::= < AVP-Header: 486 >
*2[ MIP-Home-Agent-Address ]
[ MIP-Home-Agent-Host ]
[ MIP6-Home-Link-Prefix ]
[ PMIP6-IPv4-Home-Address ]
* [ AVP ]

4.2. PMIP6-IPv4-Home-Address AVP

The PMIP6-IPv4-Home-Address HAAA, the
User-Name AVP (AVP Code TBD2) SHOULD contain the MN's identity unless the identity is of type Address
and contains an IPv4 address. This AVP
being suppressed for policy reasons - for example, when identity
hiding is used to carry the IPv4-MN-
HoA, in effect. The MN identity, if available, from MUST be in
Network Access Identifier (NAI) [RFC4282] format. At minimum the HAAA to
home realm of the MAG. This AVP SHOULD only MN MUST be
present when available at the MN is statically provisioned with MAG when the IPv4-MN-HoA.
Note that proactive dynamic assignment of network
access authentication takes place. Otherwise the IPv4-MN-HoA by MAG is not able to
route the HAAA
may result in unnecessary reservation of IPv4 address resources,
because Diameter request messages towards the MN may considerably delay or completely bypass its IPv4
address configuration. correct HAAA. The PMIP6-IPv4-Home-Address AVP is also MN
identity used on the LMA-to-HAAA
interface. The MAG-to-HAAA interface and in the User-Name AVP contains
MAY entirely be related to the IPv4-MN-HoA assigned network access authentication, and
therefore not suitable to be used as the MN. If MN-ID mobility option value
in the LMA delegates subsequent PBU/PBA messages. See the assignment of related discussion on
MN's identities in Section 5.6 and in Section 4.2.

For the IPv4-MN-HoA to session management and service authorization purposes,
session state SHOULD be maintained on the HAAA, MAG-to-HAAA interface. See
the
AVP MUST contain all zeroes IPv4 address (i.e., 0.0.0.0) discussion in Section 5.8.

4.2. LMA-to-HAAA Interface

The-LMA-to HAAA interface may be used for multiple purposes. These
include the
request message. If authorization of the LMA delegated incoming PBU, updating the IPv4-MN-HoA assignment LMA
address to the HAAA, then delegating the AVP contains assignment of the HAAA assigned IPv4-MN-HoA in HNP or the
response message.

4.3. MIP6-Home-Link-Prefix AVP

The MIP6-Home-Link-Prefix AVP (AVP Code 125) is defined in [RFC5447].
This AVP is used
IPv4-HoA to carry the MN-HNP, if available, from HAAA, and for accounting and PMIPv6 session
management.

Whenever the HAAA LMA sends a Diameter request message to the MAG. The low 64 bits of HAAA, the prefix MUST be all zeroes.

The MIP6-Home-Link-Prefix
User-Name AVP is also used on SHOULD contain the LMA-to-HAAA
interface. MN's identity. The AVP contains the prefix assigned to LMA MAY retrieve
the MN. If MN's identity information from the
LMA delegates PBU MN-ID [RFC4283][RFC5213]
mobility option. The identity SHOULD be the assignment same as used on the MAG-
to-HAAA interface, but in the case those identities differ the HAAA
MUST have a mechanism of mapping the MN-HNP MN identity used on the MAG-to-
HAAA interface to the HAAA, identity used on the LMA-to-HAAA interface.

If the PBU contains the MN Link-Layer Identifier option, the Calling-
Station-Id AVP MUST
contain all zeroes address (i.e., 0::0) SHOULD be included in the request message. If message containing
the LMA delegated received Link-Layer Identifier. Furthermore, if the MN-HNP assignment to PBU contains
the HAAA, then Service Selection mobility option [RFC5149], the Service-
Selection AVP
contains the HAAA assigned MNM-HNP SHOULD be included in the response message.

4.4. PMIP6-DHCP-Server-Address AVP request message containing
the received service identifier.

The PMIP6-DHCP-Server-Address AVP (AVP Code TBD1) is of type Address LMA and contains the IP address of HAAA use the DHCPv4 and/or DHCPv6 server
assigned MIP6-Home-Link-Prefix AVP to exchange
the MAG serving MN-HNP when appropriate. Similarly, the newly attached MN. If LMA and the HAAA use the
PMIP6-IPv4-Home-Address AVP
contains a DHCPv4 server address, then to exchange the Address type MUST be IPv4.
If IPv4-MN-HoA when
appropriate. Note that these AVPs are encapsulated inside the AVP contains MIP6-
Agent-Info AVP. Which entity is actually responsible for the address
management is a DHCPv6 server address, then deployment specific within the Address type PMIPv6 Domain and MUST
be IPv6. pre-agreed on per deployment basis.

The HAAA MAY assign a DHCP server Auth-Request-Type AVP MUST be set to the MAG in
deployments where value AUTHORIZE_ONLY.
If the MAG acts as a DHCP Relay
[I-D.ietf-netlmm-pmip6-ipv4-support].

4.5. MIP6-Feature-Vector AVP

The MIP6-Feature-Vector AVP HAAA is originally defined in [RFC5447]. This
document defines new capability flag bits according not able to authorize the rules in
[RFC5447].

PMIP6_SUPPORTED (0x0000010000000000)

When the MAG/NAS sets this bit in subscriber's mobility
service session, then the MIP6-Feature-Vector AVP, it
is an indication reply message to the HAAA that the NAS supports PMIPv6. When
the HAAA sets this bit in the response MIP6-Feature-Vector AVP, it
indicates that LMA MUST have the HAAA also has PMIPv6 support. This capability
bit
Result-Code AVP set to value DIAMETER_PMIP6_AUTHORIZATION_FAILED
(TBD5) indicating a permanent failure.

The LMA-to-HAAA interface can also be used to allow PMIPv6 mobility support in a
subscription granularity.

IP4_HOA_SUPPORTED (0x0000020000000000)

Assignment of the IPv4-MN-HoA is supported. When the MAG sets
this bit in the MIP6-Feature-Vector AVP, it indicates that update the MAG
implements a minimal functionality of a DHCP server (and a relay)
and is able to deliver IPv4-MN-HoA selected LMA
address to the MN. When the HAAA sets
this bit in and the response MIP6-Feature-Vector AVP, it indicates
that remote policy store during the HAAA has authorized
authorization step. This applies to the use of IPv4-MN-HoA case where the MAG, for
example, discovered the MN.
If LMA address using the DNS.

5. Attribute Value Pair Definitions

This section describes Attribute Value Pairs (AVPs) defined by this bit is unset
specification or re-used from existing specifications in the returned MIP6-Feature-Vector AVP, the
HAAA does not authorize the configuration a PMIPv6
specific way. Derived Diameter AVP Data Formats such as Address and
UTF8String are defined in Section 4.3 of IPv4 address.

LOCAL_MAG_ROUTING_SUPPORTED (0x0000040000000000)

Direct routing RFC 3588. Grouped AVP
values are defined in Section 4.4 of IP packets between MNs anchored to the same MAG RFC 3588.

5.1. MIP6-Agent-Info AVP

The MIP6-Agent-Info grouped AVP (AVP Code 486) is supported. When a MAG sets this bit defined in the MIP6-Feature-
Vector, it indicates that routing IP packets between MNs anchored
to the same MAG
[RFC5447]. The AVP is supported, without reverse tunneling packets
via the used to carry LMA or requiring any Route Optimization addressing related signaling
(e.g.
information and a MN-HNP. This specification extends the Return Routability Procedure MIP6-Agent-
Info with the PMIP6-IPv4-Home-Address AVP using the Diameter
extensibility rules defined in [RFC3775]) prior direct
routing. If this bit [RFC3588]. The PMIP6-IPv4-Home-
Address AVP contains the IPv4-MN-HoA.

The extended MIP6-Agent-Info AVP results to the following grouped
AVP:

MIP6-Agent-Info ::= < AVP-Header: 486 >
*2[ MIP-Home-Agent-Address ]
[ MIP-Home-Agent-Host ]
[ MIP6-Home-Link-Prefix ]
[ PMIP6-IPv4-Home-Address ]
* [ AVP ]

5.2. PMIP6-IPv4-Home-Address AVP

The PMIP6-IPv4-Home-Address AVP (AVP Code TBD2) is unset in of type Address
and contains an IPv4 address. This AVP is used to carry the returned MIP6-Feature-Vector
AVP, IPv4-MN-
HoA, if available, from the HAAA does not authorize direct routing of packets between
MNs anchored to the same MAG. This policy feature AVP SHOULD only be
supported per
present when the MN and subscription basis. is statically provisioned with the IPv4-MN-HoA.
Note that proactive dynamic assignment of the IPv4-MN-HoA by the HAAA
may result in unnecessary reservation of IPv4 address resources,
because the MN may considerably delay or completely bypass its IPv4
address configuration.

The MIP6-Feature-Vector PMIP6-IPv4-Home-Address AVP is also used on the LMA to HAAA LMA-to-HAAA
interface. Using the capability announcement The AVP it is possible contains the IPv4-MN-HoA assigned to
perform a simple capability negotiation between the MN. If
the LMA and delegates the HAAA.
Those capabilities that are announced by both parties are also known assignment of the IPv4-MN-HoA to be mutually supported. The capabilities listed in earlier are
also supported the HAAA, the
AVP MUST contain all zeroes IPv4 address (i.e., 0.0.0.0) in the
request message. If the LMA delegated the IPv4-MN-HoA assignment to
the HAAA, then the AVP contains the HAAA interface. The LMA to HAAA
interface does not define any new capability values.

4.6. Mobile-Node-Identifier assigned IPv4-MN-HoA in the
response message.

5.3. MIP6-Home-Link-Prefix AVP

The Mobile-Node-Identifier MIP6-Home-Link-Prefix AVP (AVP Code TBD3) 125) is of type UTF8String
and contains the mobile node identifier (MN-Identifier, see
[RFC5213]) defined in the NAI [RFC4282] format. [RFC5447].
This AVP is used on the MAG-
to-HAAA interface. The Mobile-Node-Identifier AV is designed for
deployments where the MAG does not have a way to find out such MN
identity that could be used in subsequent PBU/PBA exchanges (e.g.,
due to identity hiding during carry the network access authentication) or MN-HNP, if available, from the HAAA wants to assign periodically changing identities to
the MN. MAG. The Mobile-Node-Identifier low 64 bits of the prefix MUST be all zeroes.

The MIP6-Home-Link-Prefix AVP is returned in also used on the answer message that
ends a successful authentication (and possibly an authorization)
exchange between LMA-to-HAAA
interface. The AVP contains the MAG and prefix assigned to the HAAA, assuming MN. If the HAAA is also able
LMA delegates the assignment of the MN-HNP to provide the MAG with HAAA, the MN-Identifier AVP MUST
contain all zeroes address (i.e., 0::0) in the first place. The
MAG MUST use request message. If
the received MN-Identifier, if it has not been able to
get LMA delegated the mobile node identifier through other means. If MN-HNP assignment to the MAG
already has a valid mobile node identifier, HAAA, then the MAG MUST
silently discard the received MN-identifier.

4.7. Calling-Station-Id AVP

The Calling-Station-Id AVP (AVP Code 31) is of type UTF8String and
contains a Link-Layer Identifier of the MN. This identifier
corresponds to the Link-Layer Identifier as defined HAAA assigned MNM-HNP in RFC 5213
Section 2.2. and 8.6.

4.8. Service-Selection the response message.

5.4. PMIP6-DHCP-Server-Address AVP

The Service-Selection PMIP6-DHCP-Server-Address AVP (AVP Code TBD) TBD1) is of type UTF8String Address
and contains a LMA provided service identifier on the LMA-to-HAAA
interface. This AVP is re-used from [I-D.ietf-dime-mip6-split]. The
service identifier may be used IP address of the Dynamic Host Configuration
Protocol (DHCP) server assigned to assist the PBU authorization and MAG serving the assignment of newly attached
MN. If the MN-HNP and AVP contains a DHCPv4 [RFC2131] server address, then the IPv4-MN-HoA as described in RFC
5149 [RFC5149]. The identifier
Address type MUST be unique within the PMIPv6
Domain. In the absence of IPv4. If the Service-Selection AVP in the request
message, contains a DHCPv6 [RFC3315]
server address, then the Address type MUST be IPv6. The HAAA may want MAY
assign a DHCP server to inform the LMA of MAG in deployments where the default service
provisioned MAG acts as
a DHCP Relay [I-D.ietf-netlmm-pmip6-ipv4-support].

5.5. MIP6-Feature-Vector AVP

The MIP6-Feature-Vector AVP is originally defined in [RFC5447]. This
document defines new capability flag bits according to the MN and include IANA rules
in RFC 5447.

PMIP6_SUPPORTED (0x0000010000000000)

When the Service-Selection AVP MAG/NAS sets this bit in the
response message.

It MIP6-Feature-Vector AVP, it
is also possible that an indication to the MAG receives HAAA that the service selection
information from NAS supports PMIPv6. When
the MN, for example, via some lower layer mechanism.
In HAAA sets this case bit in the MAG SHOULD include response MIP6-Feature-Vector AVP, it
indicates that the Service-Selection AVP HAAA also has PMIPv6 support. This capability
bit can also be used to allow PMIPv6 mobility support in a
subscription granularity.

IP4_HOA_SUPPORTED (0x0000020000000000)

Assignment of the MAG-to-HAAA request messages. In absence of IPv4-MN-HoA is supported. When the Service-
Selection AVP MAG sets
this bit in the MAG-to-HAAA request messages, the HAAA may want
to inform MIP6-Feature-Vector AVP, it indicates that the MAG
implements a minimal functionality of the default service provisioned a DHCP server (and a relay)
and is able to deliver IPv4-MN-HoA to the MN and
include MN. When the Service-Selection AVP HAAA sets
this bit in the response message.

Whenever the Service-Selection AVP is included either in a request
message or in a response message, and the AAA interaction with HAAA
completes successfully, MIP6-Feature-Vector AVP, it is an indication indicates
that the HAAA also has authorized the MN to some service. This should be taken into account
when considering what to include in the Auth-Request-Type AVP.

The service selection concept supports signaling one service at time.
However, use of IPv4-MN-HoA for the MN policy profile MAY support multiple services being
used simultaneously. For MN.
If this purpose, bit is unset in the returned MIP6-Feature-Vector AVP, the
HAAA MAY return multiple
LMA and service pairs (see Section 4.9) does not authorize the configuration of IPv4 address.

LOCAL_MAG_ROUTING_SUPPORTED (0x0000040000000000)

Direct routing of IP packets between MNs anchored to the same MAG in
is supported. When a response
message MAG sets this bit in the MIP6-Feature-
Vector, it indicates that ends a successful authentication (and possibly an
authorization) exchange routing IP packets between MNs anchored
to the same MAG and the HAAA. Whenever is supported, without reverse tunneling packets
via the
MN initiates additional mobility session to another service (using a
link layer LMA or deployment specific method), requiring any Route Optimization related signaling
(e.g. the provisioned service
information is already contained Return Routability Procedure in the MAG. Therefore, there [RFC3775]) prior direct
routing. If this bit is no
need for additional AAA signaling between cleared in the MAG and returned MIP6-Feature-
Vector AVP, the HAAA.

4.9. Service-Configuration AVP

The Service-Configuration AVP (AVP Code TBD4) is of type Grouped and
contains a service and a LMA pair. The HAAA can use this AVP to
inform the MAG of MN's subscribed services and LMAs where those
services are hosted in.

Service-Configuration ::= < AVP-Header: TBD4 >
[ MIP6-Agent-Info ]
[ Service-Selection ]
* [ AVP ]

5. Application Support and Command Codes

5.1. MAG-to-HAAA Interface

This specification does not define a new Application-ID for the MAG-
to-HAAA Diameter connection. Rather, this specification re-uses any
Diameter application and their commands that are used to authenticate
and authorize the MN for the network access. Example applications
include NASREQ [RFC4005] and EAP [RFC4072]. The MAG acts as a
Diameter client.

The MAG-to-HAAA interactions are primarily used for bootstrapping
PMIPv6 mobility service session when a MN attaches and authenticates direct routing of packets
between MNs anchored to a PMIPv6 Domain. This includes the bootstrapping of PMIPv6
session related information. The same interface may MAG. The MAG SHOULD support this
policy feature per-MN and per-subscription basis.

The MIP6-Feature-Vector AVP is also be used for
accounting.

Whenever on the MAG sends a Diameter request message LMA to the HAAA
interface. Using the
User-Name capability announcement AVP SHOULD contain it is possible to
perform a simple capability negotiation between the MN's identity. The MN identity, if
available, MUST LMA and the HAAA.
Those capabilities that are announced by both parties are also known
to be mutually supported. The capabilities listed in earlier are
also supported in Network Access Identifier (NAI) [RFC4282]
format. At minimum the home realm LMA to HAAA interface. The LMA to HAAA
interface does not define any new capability values.

5.6. Mobile-Node-Identifier AVP

The Mobile-Node-Identifier AVP (AVP Code TBD3) is of type UTF8String
and contains the MN MUST be available at mobile node identifier (MN-Identifier, see
[RFC5213]) in the
MAG when NAI [RFC4282] format. This AVP is used on the network access authentication takes place. Otherwise MAG-
to-HAAA interface. The Mobile-Node-Identifier AV is designed for
deployments where the MAG is does not able have a way to route the Diameter request messages towards
the correct HAAA. The find out such MN
identity that could be used on the MAG-to-HAAA interface
and in the User-Name AVP MAY entirely be related subsequent PBU/PBA exchanges (e.g.,
due to identity hiding during the network access authentication, and therefore not suitable authentication) or
the HAAA wants to assign periodically changing identities to be used as the
MN-ID mobility option value MN.

The Mobile-Node-Identifier AVP is returned in the subsequent PBU/PBA messages. See
the related discussion on MN's identities in Section 4.6 and in
Section 5.2.1

For answer message that
ends a successful authentication (and possibly an authorization)
exchange between the session management MAG and service authorization purposes,
session state SHOULD be maintained on the MAG-to-HAAA interface. See HAAA, assuming the discussion in Section 4.8.

5.2. LMA-to-HAAA Interface

The-LMA-to HAAA interface may be used for multiple purposes. These
include is also able
to provide the authorization of MAG with the incoming PBU, updating MN-Identifier in the LMA
address to first place. The
MAG MUST use the HAAA, accounting and PMIPv6 session management.

This specification does received MN-Identifier, if it has not define been able to
get the mobile node identifier through other means. If the MAG
already has a new Application-ID for valid mobile node identifier, then the LMA-
to-HAAA Diameter connection. Rather, this specification re-uses any
Diameter application and their commands. An example application
could be NASREQ [RFC4005]. MAG MUST
silently discard the received MN-identifier.

5.7. Calling-Station-Id AVP

The LMA acts as Calling-Station-Id AVP (AVP Code 31) is of type UTF8String and
contains a Diameter client.

5.2.1. Authorization Link-Layer Identifier of the Proxy Binding Update

Whenever the LMA sends a Diameter request message MN. This identifier
corresponds to the HAAA, the
User-Name Link-Layer Identifier as defined in RFC 5213
Section 2.2. and 8.6.

5.8. Service-Selection AVP SHOULD contain the MN's identity.

The Service-Selection AVP (AVP Code 493) is of type UTF8String and
contains a LMA MAY retrieve provided service identifier on the MN's identity information LMA-to-HAAA
interface. This AVP is re-used from the PBU MN-ID [RFC4283][RFC5213]
mobility option. [I-D.ietf-dime-mip6-split]. The identity SHOULD
service identifier may be the same as used on to assist the MAG-
to-HAAA interface, but in PBU authorization and
the case those identities differ assignment of the HAAA MN-HNP and the IPv4-MN-HoA as described in RFC
5149 [RFC5149]. The identifier MUST have a mechanism be unique within the PMIPv6
Domain. In the absence of mapping the MN identity used on Service-Selection AVP in the request
message, the MAG-to- HAAA interface may want to inform the identity used on the LMA-to-HAAA interface.

If LMA of the PBU contains default service
provisioned to the MN Link-Layer Identifier option, and include the Calling-
Station-Id Service-Selection AVP SHOULD be included in the request message containing
response message.

It is also possible that the received Link-Layer Identifier. Furthermore, if MAG receives the PBU contains service selection
information from the Service Selection mobility option [RFC5149], MN, for example, via some lower layer mechanism.
In this case the MAG MUST include the Service-Selection AVP also in
the MAG-to-HAAA request messages. In absence of the Service-
Selection AVP SHOULD be included in the MAG-to-HAAA request message containing messages, the received HAAA may want
to inform the MAG of the default service identifier.

The LMA and provisioned to the HAAA use MN and
include the MIP6-Home-Link-Prefix Service-Selection AVP to exchange in the MN-HNP when appropriate. Similarly, response message.

Whenever the LMA Service-Selection AVP is included either in a request
message or in a response message, and the AAA interaction with HAAA use
completes successfully, it is an indication that the
PMIP6-IPv4-Home-Address AVP to exchange HAAA also
authorized the IPv4-MN-HoA MN to some service. This should be taken into account
when
appropriate. Note that these AVPs are encapsulated inside considering what to include in the MIP6-
Agent-Info Auth-Request-Type AVP. Which entity is actually responsible for

The service selection concept supports signaling one service at time.
However, the address
management is MN policy profile MAY support multiple services being
used simultaneously. For this purpose, the HAAA MAY return multiple
LMA and service pairs (see Section 5.9) to the MAG in a deployment specific within response
message that ends a successful authentication (and possibly an
authorization) exchange between the PMIPv6 Domain MAG and MUST
be pre-agreed on per deployment basis.

The Auth-Request-Type AVP MUST be set to the value AUTHORIZE_ONLY.
If HAAA. Whenever the HAAA is not able
MN initiates additional mobility session to authorize another service (using a
link layer or deployment specific method), the subscriber's mobility provisioned service session, then
information is already contained in the reply message to MAG. Therefore, there is no
need for additional AAA signaling between the LMA MUST have MAG and the
Result-Code HAAA.

5.9. Service-Configuration AVP set to value DIAMETER_PMIP6_AUTHORIZATION_FAILED
(TBD5) indicating

The Service-Configuration AVP (AVP Code TBD4) is of type Grouped and
contains a permanent failure. service and a LMA pair. The LMA-to-HAAA interface HAAA can also be used to update the selected LMA
address use this AVP to
inform the HAAA MAG of MN's subscribed services and the remote policy store during the
authorization step. This applies to the case LMAs where the MAG, for
example, discovered the LMA address using the DNS. those
services are hosted in.

Service-Configuration ::= < AVP-Header: TBD4 >
[ MIP6-Agent-Info ]
[ Service-Selection ]
* [ AVP ]

6. Proxy Mobile IPv6 Session Management

Concerning a PMIPv6 mobility session, the HAAA, the MAG and the LMA
Diameter entities SHOULD be stateful and maintain the corresponding
Authorization Session State Machine defined in [RFC3588]. If a state
is maintained, then a PMIPv6 mobility session that can be identified
by any of the Binding Cache (BCE) Lookup Keys described in RFC 5213
(see Sections 5.4.1.1., 5.4.1.2. and 5.4.1.3.) MUST map to a single
Diameter Session-Id. If the PMIPv6 Domain allows further separation
of sessions, for example, identified by the RFC 5213 BCE Lookup Keys
and the service selection combination (see Section 4.8 5.8 and
[RFC5149]), then a single Diameter Session-Id MUST map to a PMIPv6
mobility session identified by the RFC 5213 BCE Lookup Keys and the
selected service.

If both the MAG-to-HAAA and the LMA-to-HAAA interfaces are deployed
in a PMIPv6 Domain, and a state is maintained on both interfaces,
then one PMIPv6 mobility session would have two distinct Diameter
sessions on the HAAA. The HAAA needs to be aware of this deployment
possibility and SHOULD allow multiple Diameter sessions for the same
PMIPv6 mobility session.

Diameter session termination related commands described in the
following sections may be exchanged between the LMA and the HAAA, or
between the MAG and the HAAA. The actual PMIPv6 session termination
procedures take place at PMIPv6 protocol level and are described in
more detail in RFC 5213 and [I-D.ietf-mext-binding-revocation].

6.1. Session-Termination-Request

The LMA or the MAG MAY send the Session-Termination-Request (STR)
command [RFC3588] to inform the HAAA and inform that the termination of an
ongoing PMIPv6 session is in progress.

6.2. Session-Termination-Answer

The Session-Termination-Answer (STA) [RFC3588] is sent by the HAAA to
acknowledge the termination of a PMIPv6 session.

6.3. Abort-Session-Request

The HAAA MAY send the Abort-Session-Request (ASR) command [RFC3588]
to the LMA or to the MAG and request termination of a PMIPv6 session.

6.4. Abort-Session-Answer

The Abort-Session-Answer (ASA) command [RFC3588]is sent by the LMA or
the MAG to acknowledge that the termination of a PMIPv6 session.

7. Attribute Value Pair Occurrence Tables

The following tables list the PMIPv6 MAG-to-HAAA interface and LMA-
to-HAAA interface AVPs including those that are defined in [RFC5447].

The Figure 2 contains the AVPs and their occurrences on the MAG-to-
HAAA interface. The AVPs that are part of grouped AVP are not listed
in the table, rather only the grouped AVP is listed.

7.1. MAG-to-HAAA Interface

+---------------+
| Command-Code |
|-------+-------+
Attribute Name | REQ | ANS |
-------------------------------+-------+-------+
PMIP6-DHCP-Server-Address | 0 | 0+ |
MIP6-Agent-Info | 0+ | 0+ |
MIP6-Feature-Vector | 0-1 | 0-1 |
Mobile-Node-Identifier | 0-1 | 0-1 |
Calling-Station-Id | 0-1 | 0 |
Service-Selection | 0-1 | 0 |
Service-Configuration | 0 | 0+ |
+-------+-------+

Figure 2: MAG-to-HAAA Interface Generic Diameter Request and Answer
Commands AVPs

7.2. LMA-to-HAAA Interface

+---------------+
| Command-Code |
|-------+-------+
Attribute Name | REQ | ANS |
-------------------------------+-------+-------+
MIP6-Agent-Info | 0-1 | 0-1 |
MIP6-Feature-Vector | 0-1 | 0-1 |
Calling-Station-Id | 0-1 | 0 |
Service-Selection | 0-1 | 0-1 |
User-Name | 0-1 | 0-1 |
+-------+-------+

Figure 3: LMA-to-HAAA Interface Generic Diameter Request and Answer
Commands AVPs

8. Example Signaling Flows

Figure 4 shows a signaling flow example during PMIPv6 bootstrapping
using the AAA interactions defined in this specification. In step
(1) of this example, the MN is authenticated to PMIPv6 domain Domain using
EAP-based authentication. The MAG to the HAAA signaling uses the
Diameter EAP Application. During step (2), the LMA uses Diameter
NASREQ application to authorize the MN with the HAAA server.

The MAG-to-HAAA AVPs, as listed in Section 7.1 are used during step
(1). These AVPs are included only in the DER message which starts
the EAP exchange and in the corresponding DEA message which
successfully completes this EAP exchange. The LMA-to-HAAA AVPs, as
listed in Section 7.2, are used during step (2). Step (2) is used to
authorize the MN request for the mobility service and update the HAAA
server with the assigned LMA information. In addition, this step may
be used to dynamically assist in the assignment of the MN-HNP.

MN MAG/NAS LMA HAAA
| | | |
| L2 attach | | |
|-------------------->| | |
| EAP/req-identity | | |
|<--------------------| | |
| EAP/res-identity | DER + MAG-to-HAAA AVPs | s
|-------------------->|---------------------------------------->| t
| EAP/req #1 | DEA (EAP request #1) | e
|<--------------------|<----------------------------------------| p
| EAP/res #2 | DER (EAP response #2) |
|-------------------->|---------------------------------------->| 1
: : : :
: : : :
| EAP/res #N | DER (EAP response #N) |
|-------------------->|---------------------------------------->|
| EAP/success | DEA (EAP success) + MAG-to-HAAA AVPs |
|<--------------------|<----------------------------------------|
: : : :
: : : :
| | PMIPv6 PBU | AAR + | s
| |------------------->| LMA-to-HAAA AVPs | t
| | |------------------->| e
| | | AAA + | p
| | | LMA-to-HAAA AVPs |
| | PMIPv6 PBA |<-------------------| 2
| RA |<-------------------| |
|<--------------------| | |
: : : :
: : : :
| IP connectivity | PMIPv6 tunnel up | |
|---------------------|====================| |
| | | |

Figure 4: MAG and LMA Signaling Interaction with AAA server during
PMIPv6 bootstrapping

9. IANA Considerations

9.1. Attribute Value Pair Codes

This specification defines the following new AVPs:

PMIP6-DHCP-Server-Address is set to TBD1
PMIP6-IPv4-Home-Address is set to TBD2
Mobile-Node-Identifier is set to TBD3
Service-Configuration is set to TBD4

9.2. Namespaces

This specification defines new values to the Mobility Capability
registry (see [RFC5447]) for use with the MIP6-Feature-Vector AVP:

9.3. Result-Code AVP Values

This specification requests IANA to allocate a new value to the
Result-Code AVP (AVP Code 268) address space within the Permanent
Failures category (5xxx) defined in [RFC3588]:

DIAMETER_PMIP6_AUTHORIZATION_FAILED is set to TBD5

10. Security Considerations

The security considerations of the Diameter Base protocol [RFC3588],
Diameter EAP application [RFC4072], Diameter NASREQ application
[RFC4005] and Diameter Mobile IPv6 integrated scenario bootstrapping
[RFC5447] are applicable to this document.

In general, the Diameter messages may be transported between the HA
and the Diameter server via one or more AAA brokers or Diameter
agents. In this case the HA to the Diameter server AAA communication
rely on the security properties of the intermediate AAA brokers and
Diameter agents (such as proxies).

11. Acknowledgements

Jouni Korhonen would like to thank the TEKES GIGA program MERCoNe-
project for providing funding to work on this document while he was
with TeliaSonera.

12. References

12.1. Normative References

[I-D.ietf-dime-mip6-split]
Korhonen, J., Tschofenig, H., Bournelle, J., Giaretta, G.,
and M. Nakhjiri, "Diameter Mobile IPv6: Support for Home
Agent to Diameter Server Interaction",
draft-ietf-dime-mip6-split-17 (work in progress),
April 2009.

[I-D.ietf-netlmm-pmip6-ipv4-support]
Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy
Mobile IPv6", draft-ietf-netlmm-pmip6-ipv4-support-11 draft-ietf-netlmm-pmip6-ipv4-support-15
(work in progress), April August 2009.

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.

[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Arkko, "Diameter Base Protocol", RFC 3588, September 2003.

[RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton,
"Diameter Network Access Server Application", RFC 4005,
August 2005.

[RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
Authentication Protocol (EAP) Application", RFC 4072,
August 2005.

[RFC4282] Aboba, B., Beadles, M., Arkko, J., and P. Eronen, "The
Network Access Identifier", RFC 4282, December 2005.

[RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K.,
and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008.

[RFC5447] Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C.,
and K. Chowdhury, "Diameter Mobile IPv6: Support for
Network Access Server to Diameter Server Interaction",
RFC 5447, February 2009.

12.2. Informative References

[I-D.ietf-mext-binding-revocation]
Muhanna, A., Khalil, M., Gundavelli, S., Chowdhury, K.,
and P. Yegani, "Binding Revocation for IPv6 Mobility",
draft-ietf-mext-binding-revocation-05
draft-ietf-mext-binding-revocation-10 (work in progress),
March
August 2009.

[RFC2131] Droms, R., "Dynamic Host Configuration Protocol",
RFC 2131, March 1997.

[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003.

[RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H.
Levkowetz, "Extensible Authentication Protocol (EAP)",
RFC 3748, June 2004.

[RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
in IPv6", RFC 3775, June 2004.

[RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K.
Chowdhury, "Mobile Node Identifier Option for Mobile IPv6
(MIPv6)", RFC 4283, November 2005.

[RFC5149] Korhonen, J., Nilsson, U., and V. Devarapalli, "Service
Selection for Mobile IPv6", RFC 5149, February 2008.

Authors' Addresses

Jouni Korhonen (editor)
Nokia Siemens Network
Linnoitustie 6
Espoo FI-02600
Finland

Email: jouni.nospam@gmail.com

Julien Bournelle
Orange Labs
38-4O rue du general Leclerc
Issy-Les-Moulineaux 92794
France

Email: julien.bournelle@orange-ftgroup.com

Kuntal Chowdhury
Starent Networks
30 International Place
Tewksbury MA 01876
USA

Email: kchowdhury@starentnetworks.com
Ahmad Muhanna
Nortel
2221 Lakeside Blvd.
Richardson, TX 75082
USA

Email: amuhanna@nortel.com

Ulrike Meyer
RWTH Aachen

Email: meyer@umic.rwth-aachen.de