--- 1/draft-ietf-dime-pmip6-00.txt 2009-03-06 19:12:08.000000000 +0100 +++ 2/draft-ietf-dime-pmip6-01.txt 2009-03-06 19:12:08.000000000 +0100 @@ -1,26 +1,26 @@ Diameter Maintenance and J. Korhonen, Ed. Extensions (DIME) Nokia Siemens Network Internet-Draft J. Bournelle Intended status: Standards Track Orange Labs -Expires: July 18, 2009 A. Muhanna - Nortel - K. Chowdhury +Expires: September 7, 2009 K. Chowdhury Starent Networks + A. Muhanna + Nortel U. Meyer RWTH Aachen - January 14, 2009 + March 6, 2009 -Diameter Proxy Mobile IPv6: Support For Mobile Access Gateway and Local - Mobility Anchor to Diameter Server Interaction - draft-ietf-dime-pmip6-00.txt + Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility + Anchor Interaction with Diameter Server + draft-ietf-dime-pmip6-01.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. @@ -29,751 +29,630 @@ 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 July 18, 2009. + This Internet-Draft will expire on September 7, 2009. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal - Provisions Relating to IETF Documents - (http://trustee.ietf.org/license-info) in effect on the date of - publication of this document. Please review these documents - carefully, as they describe your rights and restrictions with respect - to this document. + 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 and the corresponding mobility service session setup. The policy information needed by the Proxy Mobile IPv6 is defined in mobile node's policy profile, which could be downloaded from the Diameter server to the Mobile Access Gateway once the mobile node - roams into a Proxy Mobile IPv6 Domain and performs access - authentication. + attaches to a Proxy Mobile IPv6 Domain and performs access + authentication. During the binding update exchange between the + Mobile Access Gateway and the Local Mobility Anchor, the Local + Mobility Anchor can interact with the Diameter server in order to + update the remote policy store with the mobility session related + information. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 4 3. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 5 4. Attribute Value Pair Definitions . . . . . . . . . . . . . . . 7 4.1. MIP6-Agent-Info AVP . . . . . . . . . . . . . . . . . . . 7 4.2. PMIP6-IPv4-Home-Address AVP . . . . . . . . . . . . . . . 7 - 4.3. PMIP6-DHCP-Address AVP . . . . . . . . . . . . . . . . . . 8 - 4.4. PMIP6-Home-Prefix AVP . . . . . . . . . . . . . . . . . . 8 + 4.3. MIP6-Home-Link-Prefix AVP . . . . . . . . . . . . . . . . 8 + 4.4. PMIP6-DHCP-Server-Address AVP . . . . . . . . . . . . . . 8 4.5. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . . . 8 4.6. Mobile-Node-Identifier AVP . . . . . . . . . . . . . . . . 9 - 4.7. Calling-Station-Id AVP . . . . . . . . . . . . . . . . . . 10 + 4.7. Calling-Station-Id AVP . . . . . . . . . . . . . . . . . . 9 4.8. Service-Selection AVP . . . . . . . . . . . . . . . . . . 10 - 4.9. Session-Timeout AVP . . . . . . . . . . . . . . . . . . . 10 - 5. MAG to HAAA Interface Application Support . . . . . . . . . . 10 - 5.1. Application Support and Command Codes . . . . . . . . . . 10 - 5.2. Accounting at MAG . . . . . . . . . . . . . . . . . . . . 11 - 6. LMA to HAAA Interface Application Support . . . . . . . . . . 11 - 6.1. Application Support and Command Codes . . . . . . . . . . 11 - 6.2. Authorization of the Proxy Binding Update . . . . . . . . 11 - 6.2.1. LHA-Request . . . . . . . . . . . . . . . . . . . . . 12 - 6.2.2. LHA-Answer . . . . . . . . . . . . . . . . . . . . . . 13 - 6.3. Accounting at LMA . . . . . . . . . . . . . . . . . . . . 14 - 7. Proxy Mobile IPv6 Session Management . . . . . . . . . . . . . 14 - 7.1. Session-Termination-Request . . . . . . . . . . . . . . . 15 - 7.2. Session-Termination-Answer . . . . . . . . . . . . . . . . 15 - 7.3. Abort-Session-Request . . . . . . . . . . . . . . . . . . 15 - 7.4. Abort-Session-Answer . . . . . . . . . . . . . . . . . . . 15 - 8. Attribute Value Pair Occurrence Tables . . . . . . . . . . . . 15 - 8.1. MAG to HAAA Interface . . . . . . . . . . . . . . . . . . 15 - 8.2. LMA to HAAA Interface . . . . . . . . . . . . . . . . . . 17 - 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 - 9.1. Attribute Value Pair Codes . . . . . . . . . . . . . . . . 17 - 9.2. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 17 - 9.3. Application Identifiers . . . . . . . . . . . . . . . . . 18 - 9.4. Command Codes . . . . . . . . . . . . . . . . . . . . . . 18 - 9.5. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 18 - 10. Security Considerations . . . . . . . . . . . . . . . . . . . 18 - 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19 - 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 - 12.1. Normative References . . . . . . . . . . . . . . . . . . . 19 - 12.2. Informative References . . . . . . . . . . . . . . . . . . 19 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20 + 4.9. Service-Configuration AVP . . . . . . . . . . . . . . . . 10 + 5. Application Support and Command Codes . . . . . . . . . . . . 11 + 5.1. MAG-to-HAAA Interface . . . . . . . . . . . . . . . . . . 11 + 5.2. LMA-to-HAAA Interface . . . . . . . . . . . . . . . . . . 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. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 + 8.1. Attribute Value Pair Codes . . . . . . . . . . . . . . . . 14 + 8.2. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 15 + 8.3. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 15 + 9. Security Considerations . . . . . . . . . . . . . . . . . . . 15 + 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 + 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 + 11.1. Normative References . . . . . . . . . . . . . . . . . . . 16 + 11.2. Informative References . . . . . . . . . . . . . . . . . . 16 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17 1. Introduction - In the Proxy Mobile IPv6 (PMIPv6) protocol [RFC5213] and its IPv4 - support [I-D.ietf-netlmm-pmip6-ipv4-support] a Mobile Access Gateway - (MAG) performs a proxy registration with a Local Mobility Anchor - (LMA) on behalf of the mobile node (MN). In order to perform the - proxy registration the PMIPv6 MAG needs the address of the LMA, - possibly MN's home network prefix (MN-HNP), possibly MN's IPv4 home - address (IPv4-HoA), DHCP server address and other PMIPv6 specific - information such as allowed address configuration modes and possible + In the Proxy Mobile IPv6 (PMIPv6) protocol [RFC5213] and IPv4 support + for Proxy Mobile IPv6 [I-D.ietf-netlmm-pmip6-ipv4-support] a Mobile + Access Gateway (MAG) performs a proxy registration with 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 server to the - MAG once the MN roams into a Proxy Mobile IPv6 Domain (PMIPv6-Domain) - and performs the access authentication. + MAG once the MN attaches to the MAG's Proxy Mobile IPv6 Domain + (PMIPv6 Domain) and performs the access authentication. Dynamic assignment and downloading of PMIPv6 policy profile information is a desirable feature to ease the deployment and network - maintenance of larger PMIPv6 deployments. For this purpose, the AAA - infrastructure, which is used for access authentication, can be - leveraged to assign some or all of the necessary parameters. The - Diameter server in the Mobility Service authorizer's (MSA) or in the - Mobility Service Provider's (MSP) network may return these parameters - to the Network Access Server (NAS). + maintenance of larger PMIPv6 deployments. For this purpose, the + Authentication, Authorization, and Accounting (AAA) infrastructure, + which is used for access authentication, can be leveraged to assign + some or all of the necessary parameters. The Diameter server in the + Mobility Service authorizer's (MSA) network may return these + parameters to the Network Access Server (NAS). Once the MN authenticates to the network the MAG sends a Proxy - Binding Update (PBU) towards the LMA on behalf of the MN. Upon - arrival of the PBU the LMA needs to interact with the Diameter server - and fetch the MN's policy related information that was already - partially downloaded to the MAG. + Binding Update (PBU) towards the LMA on behalf of the MN. When the + LMA receives the PBU, the LMA may need to update the remote policy + store located in the MSA with the MN's mobility session related + information. - This specification defines the Diameter support for the PMIPv6 and - the corresponding mobility service session setup. 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). The NAS functionality of the MAG may be co- - located or an integral part of the MAG. The access authentication - procedure into a PMIPv6-Domain resembles the Mobile IPv6 integrated - scenario bootstrapping [I-D.ietf-dime-mip6-integrated]. The - assumption is that the Access Service Authenticator (ASA) is the same - entity as the MSA/MSP. This specification leverages the work already - done for the Mobile IPv6 integrated scenario bootstrapping - [I-D.ietf-dime-mip6-integrated]. + 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). The NAS functionality of the MAG may be + co-located or an integral part of the MAG. 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]. - General mobility terminology can be found in [RFC3753]. The - following additional or clarified terms are used in this document: + 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 server located in - user's home network. A HAAA is essentially a Diameter server. + 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 authentication, authorization, accounting - and session management functionality needed by the PMIPv6 protocol. - This document defines Diameter based interfaces between the PMIPv6 - two entities, MAG and HAAA, to the HAAA. The intention of this - document is only to extend existing Diameter Mobile IPv6 - specifications such as [I-D.ietf-dime-mip6-integrated] and define the - needed additional AVPs and functionality to fully support PMIPv6 - deployment. + 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 download from the HAAA to the MAG is part of the - network access authentication procedure when a MN roams into or - within a PMIPv6 Domain. Figure 1 shows the participating network - entities. This document, however, only concentrates on the MAG, LMA, - possible local Diameter proxies and the home Diameter server. When - aligned with [I-D.ietf-dime-mip6-integrated] the MAG acts as the NAS - located in ASP, the HAAA acts as the Diameter server located in ASA/ - MSA/MSP and the LMA acts as the HA in ASP/MSP. + 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 home Diameter server. +--------+ | HAAA & | Diameter +-----+ - | Policy |<---(1)-->| LMA | + | Policy |<---(2)-->| LMA | | Profile| +-----+ +--------+ | <--- LMA-Address ^ | | // \\ +---|------------- //---\\----------------+ ( | IPv4/IPv6 // \\ ) ( | Network // \\ ) +---|-----------//---------\\-------------+ | // \\ Diameter // <- Tunnel1 \\ <- Tunnel2 - (2) // \\ - | |- MAG-Address1 |- MAG-Address2 + (1) // \\ + | |- MAG1-Address |- MAG2-Address | +----+ +----+ +---->|MAG1| |MAG2| +----+ +----+ | | | | [MN1] [MN2] Legend: - (1): LMA <-> HAAA interaction is described - in Section 6 - (2): MAG <-> HAAA interaction is described - in Section 5 + (1): MAG-to-HAAA interaction is described + in Section 5.1 + (2): LMA-to-HAAA interaction is described + in Section 5.2 - Figure 1: Diameter Proxy Mobile IPv6 Support with MAG to HAAA and LMA - to HAAA Interfaces + Figure 1: Proxy Mobile IPv6 Domain Interaction with Diameter HAAA + Server - In a PMIPv6 access scenario a MN attaches to a PMIPv6-Domain and - starts a network access authentication procedure. The choice of the + 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, the - subscriber policy is returned along with the successful network + 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 access is successfully authenticated, the MAG sends a - PBU to the LMA. Upon receiving the PBU the LMA interacts with the - HAAA and fetches the relevant subscriber policy, authorization and - security information related to the PMIPv6 session. This - specification assumes that the HAAA is the central node for managing - everything related to PMIPv6 subscription and session, possibly even - including the allocation of prefixes. - - Prior to sending the PBU there might be a need to dynamically setup - the MAG to LMA Security Association (SA), for example using IKEv2/ - IPSec [RFC4306]. The dynamic SA setup procedure may be triggered by - the MN attaching to the MAG that does not have an existing SA with - the correspondent LMA. The details of the dynamic SA setup procedure - is out of scope of this specification. However, the SA is between - the MAG and the corresponding LMA, thus it can be created using any - security mechanism that is applicable for PMIPv6 security such as - IKEv2 IPSec with an EAP-based authentication. It should be noted - that the identity used by the MAG during the SA creation is the MAG's - own identity and the credentials are for authenticating the MAG - toward the LMA and possibly for authorizing the MAG to offer Proxy - Mobile IPv6 service with the same LMA. + 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 both new AVPs defined in this specification - and re-used AVPs that are used in a PMIPv6 specific way. The AVPs - described here are applicable for both MAG to HAAA and LMA to HAAA - interfaces. + This section describes Attribute Value Pairs (AVPs) defined by this + specification or re-used from existing specifications in a PMIPv6 + specific way. 4.1. MIP6-Agent-Info AVP - The MIP6-Agent-Info grouped AVP is defined in - [I-D.ietf-dime-mip6-integrated]. This specification reuses the said - AVP and its sub-AVPs to carry the LMA IP address and/or FQDN. + The MIP6-Agent-Info grouped AVP (AVP Code 486) is defined in + [RFC5447]. The AVP is used to carry LMA addressing related + information and a MN-HNP. This specification extends the MIP6-Agent- + Info with the PMIP6-IPv4-Home-Address AVP using the Diameter + extensibility rules defined in [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 ] 4.2. PMIP6-IPv4-Home-Address AVP - The PMIP6-IPv4-Home-Address AVP (AVP Code TBD) is of type Address and - contains the IPv4-HoA of the MN. The primary use of this AVP is to - carry the IPv4 Home Address, if available, from the HAAA to the MAG. + The PMIP6-IPv4-Home-Address AVP (AVP Code TBD2) is of type Address + and contains an IPv4 address. This AVP is used to carry the IPv4-MN- + HoA, if available, from the HAAA to the MAG. This AVP SHOULD only be + present when the MN 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 PMIP6-IPv4-Home-Address AVP may also be used on the LMA to HAAA - interface. In this scenario the AVP contains the IPv4 Home Address - the LMA has assigned to the MN. If the LMA delegates assignment of - the Home Address to the HAAA, the AVP MUST contain all zeroes address - (i.e., 0.0.0.0) in the request message. The answer message SHOULD in - all cases contain the assigned IPv4 Home Address value. + The PMIP6-IPv4-Home-Address AVP is also used on the LMA-to-HAAA + interface. The AVP contains the IPv4-MN-HoA assigned to the MN. If + the LMA delegates the assignment of the IPv4-MN-HoA to 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 assigned IPv4-MN-HoA in the + response message. -4.3. PMIP6-DHCP-Address AVP +4.3. MIP6-Home-Link-Prefix AVP - The PMIP6-DHCP-Address AVP (AVP Code TBD) is of type Address and - contains the IP address of the DHCPv4 and/or DHCPv6 server assigned - to the MAG serving the newly attached MN. If the AVP contains a - DHCPv4 server address, then the Address type MUST be IPv4. If the - AVP contains a DHCPv6 server address, then the Address type MUST be - IPv6. The HAAA MAY assign a DHCP server to the MAG in deployments - where the MAG acts as a DHCP Relay and the DHCP Server is not co- - located with the LMA [I-D.ietf-netlmm-pmip6-ipv4-support]. + The MIP6-Home-Link-Prefix AVP (AVP Code 125) is defined in [RFC5447]. + This AVP is used to carry the MN-HNP, if available, from the HAAA to + the MAG. The low 64 bits of the prefix MUST be all zeroes. -4.4. PMIP6-Home-Prefix AVP + The MIP6-Home-Link-Prefix AVP is also used on the LMA-to-HAAA + interface. The AVP contains the prefix assigned to the MN. If the + LMA delegates the assignment of the MN-HNP to the HAAA, the AVP MUST + contain all zeroes address (i.e., 0::0) in the request message. If + the LMA delegated the MN-HNP assignment to the HAAA, then the AVP + contains the HAAA assigned MNM-HNP in the response message. - The PMIP6-Home-Prefix AVP (AVP Code TBD) is of type Address and - contains the MN-NHP. The low 64 bits of the IPv6 address MUST be all - zeroes. The high 64 bits of the IPv6 address are used as the MN-HNP. - The primary use of this AVP is to carry the IPv6 Home Network Prefix, - if available, from the HAAA to the MAG. +4.4. PMIP6-DHCP-Server-Address AVP - The PMIP6-Home-Prefix AVP may also be used on the LMA to HAAA - interface. In this scenario the AVP contains the prefix the LMA has - assigned to the MN. If the LMA delegates assignment of the home - network prefix to the HAAA, the AVP MUST contain all zeroes address - (i.e., 0::0) in the request message. The answer message SHOULD in - all cases contain the assigned home prefix value. + The PMIP6-DHCP-Server-Address AVP (AVP Code TBD1) is of type Address + and contains the IP address of the DHCPv4 and/or DHCPv6 server + assigned to the MAG serving the newly attached MN. If the AVP + contains a DHCPv4 server address, then the Address type MUST be IPv4. + If the AVP contains a DHCPv6 server address, then the Address type + MUST be IPv6. The HAAA MAY assign a DHCP server to the MAG in + deployments where 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 is originally defined in - [I-D.ietf-dime-mip6-integrated]. This document only reserves new - capability bits according to the rules in - [I-D.ietf-dime-mip6-integrated]. The new reserved bits contain - PMIPv6 capability announcement of the MAG and the HAAA(/LMA)). Using - the capability announcement it is possible to perform a simple - capability negotiation between the MAG and the HAAA. Those - capabilities that are announced by both parties are also known to be - mutually supported. The following capability bits are defined in - this document: + The MIP6-Feature-Vector AVP is originally defined in [RFC5447]. This + document defines new capability flag bits according to the rules in + [RFC5447]. PMIP6_SUPPORTED (0x0000010000000000) When the MAG/NAS sets this bit in the MIP6-Feature-Vector AVP, it is an indication to the HAAA that the NAS supports PMIPv6. When the HAAA sets this bit in the response MIP6-Feature-Vector AVP, it indicates that the 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 IPv4-HoA is supported. When the MAG sets this - bit in the MIP6-Feature-Vector AVP, it indicates that the MAG + Assignment of the IPv4-MN-HoA is supported. When the MAG sets + this bit in the MIP6-Feature-Vector AVP, it indicates that the MAG implements a minimal functionality of a DHCP server (and a relay) - and is able to deliver IPv4-HoA to the MN. When the HAAA sets + and is able to deliver IPv4-MN-HoA to the MN. When the HAAA sets this bit in the response MIP6-Feature-Vector AVP, it indicates - that the HAAA has authorized the use of IPv4-HoA for the MN. If - this bit is unset in the returned MIP6-Feature-Vector AVP, the + that the HAAA has authorized the use of IPv4-MN-HoA for the MN. + If this bit is unset in the returned MIP6-Feature-Vector AVP, the HAAA 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 is supported. When a MAG sets this bit in the MIP6-Feature- Vector, it indicates that routing IP packets between MNs anchored to the same MAG is supported, without reverse tunneling packets via the LMA or requiring any Route Optimization related signaling (e.g. the Return Routability Procedure in [RFC3775]) prior direct routing. If this bit is unset in the returned MIP6-Feature-Vector AVP, the HAAA does not authorize direct routing of packets between - MNs anchored to the same MAG. This policy feature MUST be + MNs anchored to the same MAG. This policy feature SHOULD be supported per MN and subscription basis. The MIP6-Feature-Vector AVP is also used on the LMA to HAAA interface. Using the capability announcement AVP it is possible to perform a simple capability negotiation between the 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 the LMA to HAAA interface. The LMA to HAAA interface does not define any new capability values. 4.6. Mobile-Node-Identifier AVP - The Mobile-Node-Identifier AVP (AVP Code TBD) is of type UTF8String + The Mobile-Node-Identifier AVP (AVP Code TBD3) is of type UTF8String and contains the mobile node identifier (MN-Identifier, see - [RFC5213]) in a NAI [RFC4282] format. This AVP is used on the MAG to - HAAA interface. + [RFC5213]) in the NAI [RFC4282] format. 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 the network access authentication) or + the HAAA wants to assign periodically changing identities to the MN. The Mobile-Node-Identifier AVP is returned in the answer message that ends a successful authentication (and possibly an authorization) exchange between the MAG and the HAAA, assuming the HAAA is also able to provide the MAG with the MN-Identifier in the first place. The MAG MUST use the received MN-Identifier, if it has not been able to get the mobile node identifier through other means. If the MAG - already has a valid mobile node identifier, then the MAG MAY silently - discard the received MN-identifier. + already has a valid mobile node identifier, 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 may - correspond to a real physical interface or something that the MAG has - generated. + contains a Link-Layer Identifier of the MN. This identifier + corresponds to the Link-Layer Identifier as defined in RFC 5213 + Section 2.2. and 8.6. 4.8. Service-Selection AVP The Service-Selection AVP (AVP Code TBD) is of type UTF8String and - contains a LMA provided service identifier on the LMA to HAAA - interface. The service identifier may be used to assist the PBU - authorization. The identifier MUST be unique within the PMIPv6 - domain. This AVP is re-used from [I-D.ietf-dime-mip6-split]. + 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 to assist the PBU authorization and + the assignment of the MN-HNP and the IPv4-MN-HoA as described in RFC + 5149 [RFC5149]. The identifier MUST be unique within the PMIPv6 + Domain. In the absence of the Service-Selection AVP in the request + message, the HAAA may want to inform the LMA of the default service + provisioned to the MN and include the Service-Selection AVP in the + response message. -4.9. Session-Timeout AVP + It is also possible that the MAG receives the service selection + information from the MN, for example, via some lower layer mechanism. + In this case the MAG SHOULD include the Service-Selection AVP also in + the MAG-to-HAAA request messages. In absence of the Service- + Selection AVP in the MAG-to-HAAA request messages, the HAAA may want + to inform the MAG of the default service provisioned to the MN and + include the Service-Selection AVP in the response message. - The Session-Timeout AVP (AVP Code 27) is of type Unsigned32 and - contains lifetime of the Binding Cache Entry in a unit of seconds. + 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, it is an indication that the HAAA also + authorized the MN to some service. This should be taken into account + when considering what to include in the Auth-Request-Type AVP. -5. MAG to HAAA Interface Application Support + The service selection concept supports signaling one service at time. + However, the MN policy profile MAY support multiple services being + used simultaneously. For this purpose, the HAAA MAY return multiple + LMA and service pairs (see Section 4.9) to the MAG in a response + message that ends a successful authentication (and possibly an + authorization) exchange between the MAG and the HAAA. Whenever the + MN initiates additional mobility session to another service (using a + link layer or deployment specific method), the provisioned service + information is already contained in the MAG. Therefore, there is no + need for additional AAA signaling between the MAG and the HAAA. -5.1. Application Support and Command Codes +4.9. Service-Configuration AVP - This specification does not define a new Application-ID for the MAG - to HAAA interface. Rather, this specification re-uses any Diameter - application and its commands that are used to authenticate and - authorize the MN for the network access and mobility service. - Example applications include NASREQ [RFC4005] and EAP [RFC4072]. The - MAG acts as a Diameter client. + 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. - The MAG to HAAA interface is primarily used for bootstrapping PMIPv6 - mobility service session when a MN attaches and authenticates to a - PMIPv6 domain. This includes the bootstrapping of PMIPv6 session - related information and possibly PMIPv6 security related information - retrieval. The same interface may also be used for accounting. + Service-Configuration ::= < AVP-Header: TBD4 > + [ MIP6-Agent-Info ] + [ Service-Selection ] + * [ AVP ] - Whenever the MAG sends a Diameter request message to the HAAA the - User-Name AVP MUST contain the MN identity. At minimum the home - realm of the MN MUST be available at the MAG when the network access - authentication takes place. Otherwise the MAG is not able to route - the Diameter request messages towards the correct HAAA. The MN - identity MUST be in Network Access Identifier (NAI) [RFC4282] format. +5. Application Support and Command Codes - The Diameter response messages MAY contain Framed-IPv6-Prefix and/or - Framed-IPv4-Address AVPs. For example a local Diameter proxy MAY add - those in order to advertise locally available prefixes and addresses - as well [I-D.damic-netlmm-pmip6-ind-discover]. It is also possible - that PMIPv6 mobility support is not allowed for a subscription. In - this case, a MAG may still provide normal IP connectivity to the MN - using, for example, local address pools. +5.1. MAG-to-HAAA Interface -5.2. Accounting at MAG + 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 accounting at the MAG to HAAA interface is based on the - [RFC4005]. The application identifier used for accounting is the - Diameter Base Accounting (3) [RFC3588]. + The MAG-to-HAAA interactions are primarily used for bootstrapping + PMIPv6 mobility service session when a MN attaches and authenticates + to a PMIPv6 Domain. This includes the bootstrapping of PMIPv6 + session related information. The same interface may also be used for + accounting. - TBD. + Whenever the MAG sends a Diameter request message to the HAAA the + User-Name AVP SHOULD contain the MN's identity. The MN identity, if + available, MUST be in Network Access Identifier (NAI) [RFC4282] + format. At minimum the home realm of the MN MUST be available at the + MAG when the network access authentication takes place. Otherwise + the MAG is not able to route the Diameter request messages towards + the correct HAAA. The MN identity used on the MAG-to-HAAA interface + and in the User-Name AVP MAY entirely be related to the network + access authentication, and therefore not suitable to be used as the + MN-ID mobility option value in the subsequent PBU/PBA messages. See + the related discussion on MN's identities in Section 4.6 and in + Section 5.2.1 -6. LMA to HAAA Interface Application Support + For the session management and service authorization purposes, + session state SHOULD be maintained on the MAG-to-HAAA interface. See + the discussion in Section 4.8. -6.1. Application Support and Command Codes +5.2. LMA-to-HAAA Interface - The LMA to HAAA interface may be used for multiple purposes. These - include the authorization of the incoming PBU, possible PMIPv6 - security related information retrieval, accounting and PMIPv6 session - management. + The-LMA-to HAAA interface may be used for multiple purposes. These + include the authorization of the incoming PBU, updating the LMA + address to the HAAA, accounting and PMIPv6 session management. - This specification defines a new Application-ID for the LMA to HAAA - interface and specifically for the authorization of the Proxy Binding - Updates. The new application identifier is TBD BY IANA. The new - application also defines two new commands and respective Command - Codes: LHA-Request (value of TBD) and LHA-Answer (value of TBD). The - LMA acts as a Diameter client. + This specification does not define a new Application-ID for the LMA- + to-HAAA Diameter connection. Rather, this specification re-uses any + Diameter application and their commands. An example application + could be NASREQ [RFC4005]. The LMA acts as a Diameter client. -6.2. Authorization of the Proxy Binding Update +5.2.1. Authorization of the Proxy Binding Update Whenever the LMA sends a Diameter request message to the HAAA, the - User-Name AVP MUST contain the MN identity. The identity MUST be in - a NAI format. The LMA MAY retrieve the MN identity information from - the PBU MN-ID [RFC4283][RFC5213] mobility option. The identity - SHOULD be the same as used on the MAG to HAAA interface, but in a - case those identities differ the HAAA MUST have a mechanism of - mapping the MN identity used on the MAG to HAAA interface to the - identity used on the LMA to HAAA interface. + User-Name AVP SHOULD contain the MN's identity. The LMA MAY retrieve + the MN's identity information from the PBU MN-ID [RFC4283][RFC5213] + mobility option. The identity SHOULD be the 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 identity used on the MAG-to- + HAAA interface to the identity used on the LMA-to-HAAA interface. If the PBU contains the MN Link-Layer Identifier option, the Calling- Station-Id AVP SHOULD be included in the request message containing the received Link-Layer Identifier. Furthermore, if the PBU contains the Service Selection mobility option [RFC5149], the Service- Selection AVP SHOULD be included in the request message containing the received service identifier. - The LMA and the HAAA use the PMIP6-Home-Prefix AVP to exchange the - MN-HNP when appropriate. The low 64 bits of the prefix must be all - zeroes. Similarly, the LMA and the HAAA use the PMIP6-IPv4-Home- - Address AVP to exchange the MN IPv4-HoA when appropriate. If the - PMIP6-Home-Prefix is set to an all zeroes address (i.e., 0::0) in the - request message, it is an indication that the HAAA needs to assign - the MN-HNP and return it to the LMA in the response message. If the - PMIP6-IPv4-Home-Address is set to all zeroes (i.e., 0.0.0.0) in the - request message, it is an indication that the HAAA needs to assign - the MN IPv4-HoA and return it to the LMA in the response message. + The LMA and the HAAA use the MIP6-Home-Link-Prefix AVP to exchange + the MN-HNP when appropriate. Similarly, the LMA and the HAAA use the + PMIP6-IPv4-Home-Address AVP to exchange the IPv4-MN-HoA when + appropriate. Note that these AVPs are encapsulated inside the MIP6- + Agent-Info AVP. Which entity is actually responsible for the address + management is a deployment specific within the PMIPv6 Domain and MUST + be pre-agreed on per deployment basis. The Auth-Request-Type AVP MUST be set to the value AUTHORIZE_ONLY. If the HAAA is not able to authorize the subscriber's mobility service session, then the reply message to the LMA MUST have the - Result-Code AVP set to value DIAMETER_PMIP6_AUTHORIZATION_FAILED (TBD - BY IANA) indicating a permanent failure. - - The LMA to HAAA interface can also be used to update the selected LMA - address to the HAAA. This applies to the case where the MAG, for - example, discovers the LMA address using the DNS. - -6.2.1. LHA-Request - - The LHA-Request (LHAR, value of TBD) message is sent by the LMA to - the Diameter server to initiate a mobility service session - authorization procedure. The LHAR message format is defined below: - - ::= < Diameter Header: TBD, REQ, PXY > - < Session-ID > - { Auth-Application-Id } - { User-Name } - { Destination-Realm } - { Origin-Host } - { Origin-Realm } - { Auth-Request-Type } - [ Destination-Host ] - [ Origin-State-Id ] - [ NAS-Identifier ] - [ NAS-IP-Address ] - [ NAS-IPv6-Address ] - [ NAS-Port-Type ] - [ Called-Station-Id ] - [ Calling-Station-Id ] - { MIP6-Feature-Vector } - { MIP6-Agent-Info } - * [ PMIP6-Home-Prefix ] - [ PMIP6-IPv4-Home-Address ] - [ Service-Selection ] - [ Authorization-Lifetime ] - [ Auth-Session-State ] - * [ Proxy-Info ] - * [ Route-Record ] - * [ AVP ] - -6.2.2. LHA-Answer - - The LHA-Answer (LHAA, value of TBD) message is sent in response to - the LHA-Request (LHAR) message. If the mobility service session - authorization procedure was successful then the response MAY include - PMIPv6 LMA to HAAA interface AVPs. The PMIP6-Home-Prefix AVP - contains MN-HNP and the PMIP6-IPv4-Home-Address AVP contains IPv4- - HoA, if such information are needed. The LHAA message format is - defined below: - - ::= < Diameter Header: TBD, PXY > - < Session-Id > - { Auth-Application-Id } - { Result-Code } - { Origin-Host } - { Origin-Realm } - { Auth-Request-Type } - [ User-Name ] - [ Authorization-Lifetime ] - [ Auth-Session-State ] - [ Error-Message ] - [ Error-Reporting-Host ] - [ Re-Auth-Request-Type ] - [ MIP6-Feature-Vector ] - * [ PMIP6-Home-Prefix ] - [ PMIP6-IPv4-Home-Address ] - [ Session-Timeout ] - [ Chargeable-User-Identity ] - [ Origin-State-Id ] - * [ Proxy-Info ] - * [ Redirect-Host ] - [ Redirect-Host-Usage ] - [ Redirect-Max-Cache-Time ] - * [ Failed-AVP ] - * [ AVP ] - -6.3. Accounting at LMA + Result-Code AVP set to value DIAMETER_PMIP6_AUTHORIZATION_FAILED + (TBD5) indicating a permanent failure. - The accounting at the LMA to HAAA interface is based on the - [RFC4005]. The application identifier used for accounting is the - Diameter Base Accounting (3) [RFC3588]. + The LMA-to-HAAA interface can also be used to update the selected LMA + address to the HAAA and the remote policy store during the + authorization step. This applies to the case where the MAG, for + example, discovered the LMA address using the DNS. - TBD. +6. Proxy Mobile IPv6 Session Management -7. 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 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. - Concerning a PMIPv6 session, the HAAA MAY maintain a state. The LMA - and the MAG MUST support the Authorization Session State Machine - defined in [RFC3588]. Diameter session termination related commands - described in the following sections may be exchanged between the LMA - and the HAAA. + 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. - The actual PMIPv6 session termination procedures take place at PMIPv6 - protocol level and are out of scope of this document. + 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]. -7.1. Session-Termination-Request +6.1. Session-Termination-Request The LMA or the MAG MAY send the Session-Termination-Request (STR) command [RFC3588] to the HAAA and inform the termination of an ongoing PMIPv6 session is in progress. -7.2. Session-Termination-Answer +6.2. Session-Termination-Answer The Session-Termination-Answer (STA) [RFC3588] is sent by the HAAA to acknowledge the termination of a PMIPv6 session. -7.3. Abort-Session-Request +6.3. Abort-Session-Request - The HAAA MAY send the Abort-Session-Request (ACR) command [RFC3588] + 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. -7.4. Abort-Session-Answer +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. -8. Attribute Value Pair Occurrence Tables +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 - [I-D.ietf-dime-mip6-integrated]. + 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 + 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. -8.1. MAG to HAAA Interface +7.1. MAG-to-HAAA Interface + +---------------+ | Command-Code | |-------+-------+ Attribute Name | REQ | ANS | -------------------------------+-------+-------+ - PMIP6-DHCP-Address | 0 | 0+ | - MIP6-Agent-Info | 0 | 0+ | + PMIP6-DHCP-Server-Address | 0 | 0+ | + MIP6-Agent-Info | 0+ | 0+ | MIP6-Feature-Vector | 0-1 | 0-1 | - PMIP6-IPv4-Home-Address | 0 | 0-1 | - PMIP6-Home-Prefix | 0 | 0+ | 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 + Figure 2: MAG-to-HAAA Interface Generic Diameter Request and Answer Commands AVPs - The following table describes the Diameter AVPs code values, types, - possible flag values, and whether the AVP MAY be encrypted. The - Diameter base protocol specification [RFC3588] specifies the AVP - Flags rules for AVPs in section 4.5. Due to space constraints, the - short form DiamIdent is used to represent DiameterIdentity and - OctetStr is used to represent OctetString. - - +--------------------+ - | AVP Flag rules | - +----+----+----+-----+----+ - AVP Section | | |SHLD|MUST | | - Attribute Name Code Defined Data Type |MUST| MAY|NOT |NOT |Encr| - ------------------------------------------+----+----+----+-----+----+ - MIP6-Agent-Info TBD 4.1 Grouped | | P | | M,V | Y | - PMIP6-IPv4-Home- | | | | | | - Address TBD 4.2 Address | | P | | M,V | Y | - PMIP6-DHCP-Address TBD 4.3 Address | | P | | M,V | Y | - PMIP6-Home-Prefix TBD 4.4 Address | | P | | M,V | Y | - MIP6-Feature- | | | | | | - Vector TBD 4.5 Unsigned64| | P | | M,V | Y | - Calling-Station-Id 31 4.7 UTF8String| | P | | M,V | Y | - Mobile-Node- | | | | | | - Identifier TBD 4.6 UTF8String| | P | | M,V | Y | - ------------------------------------------+----+----+----+-----+----+ - - Figure 3: AVP Flag Rules Table - -8.2. LMA to HAAA Interface - - The AVP occurrences are defined in the ABNFs for the LHA-Request (see - Section 6.2.1) and LHA-Answer (see Section 6.2.2) commands. - - The following table describes the Diameter AVPs code values, types, - possible flag values, and whether the AVP MAY be encrypted. The - Diameter base protocol specification [RFC3588] specifies the AVP - Flags rules for AVPs in section 4.5. Due to space constraints, the - short form DiamIdent is used to represent DiameterIdentity and - OctetStr is used to represent OctetString. +7.2. LMA-to-HAAA Interface - +--------------------+ - | AVP Flag rules | - +----+----+----+-----+----+ - AVP Section | | |SHLD|MUST | | - Attribute Name Code Defined Data Type |MUST| MAY|NOT |NOT |Encr| - ------------------------------------------+----+----+----+-----+----+ - MIP6-Agent-Info TBD 4.1 Grouped | M | P | | V | Y | - PMIP6-IPv4-Home- | | | | | | - Address TBD 4.2 Address | M | P | | V | Y | - PMIP6-Home-Prefix TBD 4.4 Address | M | P | | V | Y | - MIP6-Feature- | | | | | | - Vector TBD 4.5 Unsigned64| M | P | | V | Y | - Calling-Station-Id 31 4.7 UTF8String| M | P | | V | Y | - Service-Selection TBD 4.8 UTF8String| M | P | | V | Y | - Session-Timeout 27 4.9 Unsigned32| M | P | | V | Y | - ------------------------------------------+----+----+----+-----+----+ + +---------------+ + | 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 4: AVP Flag Rules Table + Figure 3: LMA-to-HAAA Interface Generic Diameter Request and Answer + Commands AVPs -9. IANA Considerations +8. IANA Considerations -9.1. Attribute Value Pair Codes +8.1. Attribute Value Pair Codes This specification defines the following new AVPs: - PMIP6-DHCP-Address is set to TBD - PMIP6-Home-Prefix is set to TBD - PMIP6-IPv4-Home-Address is set to TBD - Mobile-Node-Identifier is set to TBD + 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 +8.2. Namespaces This specification defines new values to the Mobility Capability - registry (see [I-D.ietf-dime-mip6-integrated]) for use with the MIP6- - Feature-Vector AVP: + registry (see [RFC5447]) for use with the MIP6-Feature-Vector AVP: Token | Value | Description ---------------------------------+----------------------+------------ PMIP6_SUPPORTED | 0x0000010000000000 | [RFC TBD] IP4_HOA_SUPPORTED | 0x0000020000000000 | [RFC TBD] LOCAL_MAG_ROUTING_SUPPORTED | 0x0000040000000000 | [RFC TBD] -9.3. Application Identifiers - - This specification requires IANA to allocate a new value for - "Diameter Proxy Mobile IPv6" (PMIP6) from the Application Identifier - namespace defined in [RFC3588]. - -9.4. Command Codes - - IANA is requested to allocate new command code values for the - following new commands from the Command Code namespace defined in - [RFC3588]. - - Command Code | Value - -----------------------------------+------ - LHA-Request (LHAR) | TBD - LHA-Answer (LHAA) | TBD - -9.5. Result-Code AVP Values +8.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 TBD + DIAMETER_PMIP6_AUTHORIZATION_FAILED is set to TBD5 -10. Security Considerations +9. 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 - [I-D.ietf-dime-mip6-integrated] are applicable to this document. + [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 TEKES MERCoNe project for - providing funding to work on this document while he was with - TeliaSonera. +10. Acknowledgements -12. References + 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.1. Normative References +11. References - [I-D.ietf-dime-mip6-integrated] - Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C., - and K. Chowdhury, "Diameter Mobile IPv6: Support for - Network Access Server to Diameter Server Interaction", - draft-ietf-dime-mip6-integrated-12 (work in progress), - January 2009. +11.1. Normative References [I-D.ietf-netlmm-pmip6-ipv4-support] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy - Mobile IPv6", draft-ietf-netlmm-pmip6-ipv4-support-07 - (work in progress), December 2008. + Mobile IPv6", draft-ietf-netlmm-pmip6-ipv4-support-09 + (work in progress), January 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. @@ -781,82 +660,82 @@ [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. -12.2. Informative References + [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. - [I-D.damic-netlmm-pmip6-ind-discover] - Damic, D., Premec, D., Patil, B., Sahasrabudhe, M., and S. - Krishnan, "Proxy Mobile IPv6 indication and discovery", - draft-damic-netlmm-pmip6-ind-discover-03 (work in - progress), February 2008. +11.2. Informative 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-16 (work in progress), December 2008. + [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-03 (work in progress), + January 2009. + [RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H. + Levkowetz, "Extensible Authentication Protocol (EAP)", RFC 3748, June 2004. - [RFC3753] Manner, J. and M. Kojo, "Mobility Related Terminology", - RFC 3753, 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. - [RFC4306] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol", - RFC 4306, December 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 FIN-02600 + 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 - Ahmad Muhanna - Nortel - 2221 Lakeside Blvd. - Richardson, TX 75082 - USA - - Email: amuhanna@nortel.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