draft-ietf-dime-mip6-split-17.txt   rfc5778.txt 
Diameter Maintenance and J. Korhonen, Ed. Internet Engineering Task Force (IETF) J. Korhonen, Ed.
Extensions (DIME) H. Tschofenig Request for Comments: 5778 H. Tschofenig
Internet-Draft Nokia Siemens Networks Category: Standards Track Nokia Siemens Networks
Intended status: Standards Track J. Bournelle ISSN: 2070-1721 J. Bournelle
Expires: October 30, 2009 Orange Labs Orange Labs
G. Giaretta G. Giaretta
Qualcomm Qualcomm
M. Nakhjiri M. Nakhjiri
Motorola Motorola
April 28, 2009 February 2010
Diameter Mobile IPv6: Support for Home Agent to Diameter Server Diameter Mobile IPv6:
Interaction Support for Home Agent to Diameter Server Interaction
draft-ietf-dime-mip6-split-17.txt
Status of this Memo Abstract
This Internet-Draft is submitted to IETF in full conformance with the Mobile IPv6 deployments may want to bootstrap their operations
provisions of BCP 78 and BCP 79. dynamically based on an interaction between the home agent and the
Diameter server of the Mobile Service Provider. This document
specifies the interaction between a Mobile IP home agent and a
Diameter server.
Internet-Drafts are working documents of the Internet Engineering This document defines the home agent to the Diameter server
Task Force (IETF), its areas, and its working groups. Note that communication when the mobile node authenticates using the Internet
other groups may also distribute working documents as Internet- Key Exchange v2 protocol with the Extensible Authentication Protocol
Drafts. or using the Mobile IPv6 Authentication Protocol. In addition to
authentication and authorization, the configuration of Mobile IPv6-
specific parameters and accounting is specified in this document.
Internet-Drafts are draft documents valid for a maximum of six months Status of This Memo
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 This is an Internet Standards Track document.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at This document is a product of the Internet Engineering Task Force
http://www.ietf.org/shadow.html. (IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on October 30, 2009. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc5778.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
Mobile IPv6 deployments may want to bootstrap their operations described in the Simplified BSD License.
dynamically based on an interaction between the Home Agent and the
Diameter server of the Mobile Service Provider. This document
specifies the interaction between a Mobile IP Home Agent and a
Diameter server.
This document defines the Home Agent to the Diameter server
communication when the mobile node authenticates using the Internet
Key Exchange v2 protocol with the Extensible Authentication Protocol
or using the Mobile IPv6 Authentication Protocol. In addition to
authentication and authorization, the configuration of Mobile IPv6
specific parameters and accounting is specified in this document.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction ....................................................4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 8 2. Terminology .....................................................6
3. Application Identifiers . . . . . . . . . . . . . . . . . . . 9 3. Application Identifiers .........................................6
4. Protocol Description . . . . . . . . . . . . . . . . . . . . . 10 4. Protocol Description ............................................7
4.1. Support for Mobile IPv6 with IKEv2 and EAP . . . . . . . . 10 4.1. Support for Mobile IPv6 with IKEv2 and EAP .................7
4.2. Support for the Mobile IPv6 Authentication Protocol . . . 13 4.2. Support for the Mobile IPv6 Authentication Protocol .......10
4.3. Mobile IPv6 Session Management . . . . . . . . . . . . . . 14 4.3. Mobile IPv6 Session Management ............................11
4.3.1. Session-Termination-Request . . . . . . . . . . . . . 14 4.3.1. Session-Termination-Request ........................11
4.3.2. Session-Termination-Answer . . . . . . . . . . . . . . 14 4.3.2. Session-Termination-Answer .........................11
4.3.3. Abort-Session-Request . . . . . . . . . . . . . . . . 15 4.3.3. Abort-Session-Request ..............................12
4.3.4. Abort-Session-Answer . . . . . . . . . . . . . . . . . 15 4.3.4. Abort-Session-Answer ...............................12
4.4. Accounting for Mobile IPv6 services . . . . . . . . . . . 15 4.4. Accounting for Mobile IPv6 Services .......................12
4.4.1. Accounting-Request . . . . . . . . . . . . . . . . . . 16 4.4.1. Accounting-Request .................................13
4.4.2. Accounting-Answer . . . . . . . . . . . . . . . . . . 16 4.4.2. Accounting-Answer ..................................13
5. Command Codes . . . . . . . . . . . . . . . . . . . . . . . . 17 5. Command Codes ..................................................13
5.1. Command Code for Mobile IPv6 with IKEv2 and EAP . . . . . 17 5.1. Command Code for Mobile IPv6 with IKEv2 and EAP ...........13
5.1.1. Diameter-EAP-Request . . . . . . . . . . . . . . . . . 17 5.1.1. Diameter-EAP-Request ...............................13
5.1.2. Diameter-EAP-Answer . . . . . . . . . . . . . . . . . 18 5.1.2. Diameter-EAP-Answer ................................14
5.2. Command Codes for Mobile IPv6 Authentication Protocol 5.2. Command Codes for Mobile IPv6 Authentication
Support . . . . . . . . . . . . . . . . . . . . . . . . . 19 Protocol Support ..........................................15
5.2.1. MIP6-Request . . . . . . . . . . . . . . . . . . . . . 20 5.2.1. MIP6-Request .......................................16
5.2.2. MIP6-Answer . . . . . . . . . . . . . . . . . . . . . 21 5.2.2. MIP6-Answer ........................................17
6. AVPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 6. AVPs ...........................................................18
6.1. User-Name AVP . . . . . . . . . . . . . . . . . . . . . . 25 6.1. User-Name AVP .............................................21
6.2. Service-Selection AVP . . . . . . . . . . . . . . . . . . 25 6.2. Service-Selection AVP .....................................21
6.3. MIP-MN-AAA-SPI AVP . . . . . . . . . . . . . . . . . . . . 25 6.3. MIP-MN-AAA-SPI AVP ........................................21
6.4. MIP-MN-HA-SPI AVP . . . . . . . . . . . . . . . . . . . . 26 6.4. MIP-MN-HA-SPI AVP .........................................22
6.5. MIP-Mobile-Node-Address AVP . . . . . . . . . . . . . . . 26 6.5. MIP-Mobile-Node-Address AVP ...............................22
6.6. MIP6-Agent-Info AVP . . . . . . . . . . . . . . . . . . . 26 6.6. MIP6-Agent-Info AVP .......................................22
6.7. MIP-Careof-Address AVP . . . . . . . . . . . . . . . . . . 27 6.7. MIP-Careof-Address AVP ....................................23
6.8. MIP-Authenticator AVP . . . . . . . . . . . . . . . . . . 27 6.8. MIP-Authenticator AVP .....................................23
6.9. MIP-MAC-Mobility-Data AVP . . . . . . . . . . . . . . . . 27 6.9. MIP-MAC-Mobility-Data AVP .................................23
6.10. MIP-Session-Key AVP . . . . . . . . . . . . . . . . . . . 27 6.10. MIP-Session-Key AVP ......................................23
6.11. MIP-MSA-Lifetime AVP . . . . . . . . . . . . . . . . . . . 27 6.11. MIP-MSA-Lifetime AVP .....................................23
6.12. MIP-MN-HA-MSA AVP . . . . . . . . . . . . . . . . . . . . 28 6.12. MIP-MN-HA-MSA AVP ........................................24
6.13. MIP-Algorithm-Type AVP . . . . . . . . . . . . . . . . . . 28 6.13. MIP-Algorithm-Type AVP ...................................24
6.14. MIP-Replay-Mode AVP . . . . . . . . . . . . . . . . . . . 28 6.14. MIP-Replay-Mode AVP ......................................24
6.15. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . . . 29 6.15. MIP6-Feature-Vector AVP ..................................25
6.16. MIP-Timestamp AVP . . . . . . . . . . . . . . . . . . . . 29 6.16. MIP-Timestamp AVP ........................................25
6.17. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 29 6.17. QoS-Capability AVP .......................................25
6.18. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 29 6.18. QoS-Resources AVP ........................................25
6.19. Chargeable-User-Identity AVP . . . . . . . . . . . . . . . 29 6.19. Chargeable-User-Identity AVP .............................25
6.20. MIP6-Auth-Mode AVP . . . . . . . . . . . . . . . . . . . . 29 6.20. MIP6-Auth-Mode AVP .......................................25
6.21. Accounting AVPs . . . . . . . . . . . . . . . . . . . . . 30 6.21. Accounting AVPs ..........................................26
7. Result-Code AVP Values . . . . . . . . . . . . . . . . . . . . 32 7. Result-Code AVP Values .........................................27
7.1. Success . . . . . . . . . . . . . . . . . . . . . . . . . 32 7.1. Success ...................................................27
7.2. Permanent Failures . . . . . . . . . . . . . . . . . . . . 32 7.2. Permanent Failures ........................................27
8. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 33 8. AVP Occurrence Tables ..........................................27
8.1. DER, DEA, MIR and MIA AVP/Command-Code Table . . . . . . . 33 8.1. DER, DEA, MIR, and MIA AVP/Command-Code Table .............28
8.2. Coupled Accounting Model AVP Table . . . . . . . . . . . . 34 8.2. Coupled Accounting Model AVP Table ........................28
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 9. IANA Considerations ............................................29
9.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 36 9.1. Command Codes .............................................29
9.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . 36 9.2. AVP Codes .................................................29
9.3. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 36 9.3. Result-Code AVP Values ....................................30
9.4. Application Identifier . . . . . . . . . . . . . . . . . . 37 9.4. Application Identifier ....................................30
9.5. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 37 9.5. Namespaces ................................................30
10. Security Considerations . . . . . . . . . . . . . . . . . . . 38 10. Security Considerations .......................................31
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 39 11. Acknowledgements ..............................................31
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 40 12. References ....................................................32
12.1. Normative References . . . . . . . . . . . . . . . . . . . 40 12.1. Normative References .....................................32
12.2. Informative References . . . . . . . . . . . . . . . . . . 41 12.2. Informative References ...................................33
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 42
1. Introduction 1. Introduction
Performing the Mobile IPv6 protocol [RFC3775], requires the Mobile Performing the Mobile IPv6 protocol [RFC3775] requires the mobile
Node (MN) to own a Home Address (HoA) and to have an assigned Home node (MN) to own a home address and to have an assigned home agent
Agent (HA) to the MN. The MN needs to register with the HA in order (HA) to the MN. The MN needs to register with the HA in order to
to enable its reachability and mobility, when away from its home enable its reachability and mobility, when away from its home link.
link. The registration process itself may require an establishment The registration process itself may require an establishment of IPsec
of IPsec security associations (SA) and cryptographic material security associations (SAs) and cryptographic material between the MN
between the MN and the HA. Alternatively, the registration process and the HA. Alternatively, the registration process may be secured
may be secured using a mobility message authentication option, which using a mobility message authentication option, which enables IPv6
enables IPv6 mobility in a MN without having to establish an IPsec SA mobility in an MN without having to establish an IPsec SA with its
with its HA. Providing the collection of home address, HA address HA. Providing the collection of home address, HA address, and keying
and keying material is generally referred to as the Mobile IPv6 material is generally referred to as the Mobile IPv6 bootstrapping
bootstrapping problem [RFC4640]. The purpose of this specification problem [RFC4640]. The purpose of this specification is to provide
is to provide Diameter support for the interaction between the HA and Diameter support for the interaction between the HA and the
the Authentication, Authorization, and Accounting (AAA) server. This Authentication, Authorization, and Accounting (AAA) server. This
specification satisfies the requirements defined in specification satisfies the requirements defined in [RFC5637] for the
[I-D.ietf-mext-aaa-ha-goals] for the bootstrapping problem in the bootstrapping problem in the split scenario [RFC5026] and also
split scenario [RFC5026] and also specifies Diameter support for the specifies Diameter support for the Authentication Protocol for Mobile
Authentication Protocol for Mobile IPv6 [RFC4285]. The Diameter IPv6 [RFC4285]. The Diameter support defined in this specification
support defined in this specification also applies to Dual Stack also applies to Dual Stack Mobile IPv6 [RFC5555].
Mobile IPv6 [I-D.ietf-mext-nemo-v4traversal].
From a Mobility Service Provider (MSP) perspective, it is important From a Mobility Service Provider (MSP) perspective, it is important
to verify that the MN is authenticated and authorized to utilize to verify that the MN is authenticated and authorized to utilize
Mobile IPv6 service, and is accounted for those. Only when the MN is Mobile IPv6 service, and is accounted for those. Only when the MN is
authenticated and authorized, the MSP allows the bootstrapping of authenticated and authorized does the MSP allow the bootstrapping of
Mobile IPv6 parameters. Thus, prior to processing the Mobile IPv6 Mobile IPv6 parameters. Thus, prior to processing the Mobile IPv6
registrations, the HA participates in the authentication of the MN to registrations, the HA participates in the authentication of the MN to
verify the MN's identity. The HA also participates in the Mobile verify the MN's identity. The HA also participates in the Mobile
IPv6 authorization process involving the Diameter infrastructure. IPv6 authorization process involving the Diameter infrastructure.
The HA, due to its role in traffic forwarding, may also perform The HA, due to its role in traffic forwarding, may also perform
accounting for the Mobile IPv6 service provided to the MN. accounting for the Mobile IPv6 service provided to the MN.
This document enables the following functionality: This document enables the following functionality:
Authentication: Verifying the MN's identity. As a Diameter client Authentication: The MN's identity needs to be verified. As a
supporting the new Diameter Mobile IPv6 application, the HA may Diameter client supporting the new Diameter Mobile IPv6
need to support more than one authentication type depending on the application, the HA may need to support more than one
environment. Although the authentication is performed by the AAA authentication type depending on the environment. Although the
server there is an impact for the HA as different set of command authentication is performed by the AAA server, there is an impact
codes are needed for the respective authentication procedures. for the HA as different sets of command codes are needed for the
respective authentication procedures.
Authorization: The HA must verify that the user is authorized to the Authorization: The HA must verify that the user is authorized to the
Mobile IPv6 service using the assistance of the MSP Diameter Mobile IPv6 service using the assistance of the MSP Diameter
servers. This is accomplished through the use of new Diameter servers. This is accomplished through the use of new Diameter
applications specifically designed for performing Mobile IPv6 applications specifically designed for performing Mobile IPv6
authorization decisions. This document defines required AAA authorization decisions. This document defines required AAA
procedures and requires the HA to support them and to participate procedures and requires the HA to support them and to participate
in this authorization signaling. in this authorization signaling.
Accounting: For accounting purposes and capacity planning, it is Accounting: For accounting purposes and capacity planning, it is
required that the HA provides accounting reports to the Diameter required that the HA provides accounting reports to the Diameter
infrastructure and thus to support the related Diameter accounting infrastructure and thus supports the related Diameter accounting
procedures. procedures.
Session Management: The management of the mobility services may Session Management: The management of the mobility services may
require the Diameter server or the HA to terminate the Mobile IPv6 require the Diameter server or the HA to terminate the Mobile IPv6
service before the binding expires. This document defines service before the binding expires. This document defines
procedures for the AAA based session management. procedures for the AAA-based session management.
Figure 1 depicts the reference architecture for this document. Figure 1 depicts the reference architecture for this document.
+--------+ +--------+
|Diameter| |Diameter|
|Server | |Server |
+--------+ +--------+
^ ^
Back-End | Diameter Mobile IPv6 Back-End | Diameter Mobile IPv6
Protocol | HA<->AAA Server Protocol | HA<->AAA Server
skipping to change at page 6, line 38 skipping to change at page 5, line 38
| (this document) | (this document)
v v
+---------+ +---------------+ +---------+ +---------------+
| Mobile | Front-End Protocol |Home Agent / | | Mobile | Front-End Protocol |Home Agent / |
| Node |<-------------------->|Diameter Client| | Node |<-------------------->|Diameter Client|
+---------+ IKEv2 or RFC 4285 +---------------+ +---------+ IKEv2 or RFC 4285 +---------------+
Figure 1: Architecture Overview Figure 1: Architecture Overview
Mobile IPv6 signaling between the MN and the HA can be protected Mobile IPv6 signaling between the MN and the HA can be protected
using two different mechanisms, namely using IPsec or the using two different mechanisms, namely, using IPsec or the
Authentication Protocol for Mobile IPv6 [RFC4285]. For these two Authentication Protocol for Mobile IPv6 [RFC4285]. For these two
approaches several different authentication and key exchange approaches, several different authentication and key exchange
solutions are available. When IPsec is used to protect Mobile IPv6 solutions are available. When IPsec is used to protect Mobile IPv6
signaling messages, Internet Key Exchange v2 (IKEv2) is used signaling messages, Internet Key Exchange v2 (IKEv2) is used
[RFC4877] for the setup of the IPsec SAs. IKEv2 supports Extensible [RFC4877] for the setup of the IPsec SAs. IKEv2 supports EAP-based
Authentication Protocol (EAP) based initiator authentication, (Extensible Authentication Protocol) initiator authentication,
certificates and pre-shared secrets. Alternatively, the certificates, and pre-shared secrets. Alternatively, the
Authentication Protocol for Mobile IPv6 uses a mechanism that is very Authentication Protocol for Mobile IPv6 uses a mechanism that is very
similar to the one used for protecting Mobile IPv4 signaling similar to the one used for protecting Mobile IPv4 signaling
messages. messages.
The ability to use different credentials and methods to authenticate The ability to use different credentials and methods to authenticate
the MN has an impact on the AAA interactions between the HA (acting the MN has an impact on the AAA interactions between the HA (acting
as a Diameter client) and the Diameter Server. This specification is as a Diameter client) and the Diameter server. This specification is
only limited to the following MN authentication methods: only limited to the following MN authentication methods:
o IKEv2 usage with EAP o IKEv2 usage with EAP
o Mobile IPv6 Authentication Protocol o Mobile IPv6 Authentication Protocol
New authentication mechanisms may be added later by separate New authentication mechanisms may be added later by separate
specifications. specifications.
For accounting of Mobile IPv6 services provided to the MN, this For accounting of Mobile IPv6 services provided to the MN, this
specification uses the Diameter Base Protocol accounting defined in specification uses the Diameter base protocol accounting defined in
[RFC3588]. [RFC3588].
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
The Mobile IPv6 bootstrapping terminology is taken from [RFC4640]. The Mobile IPv6 bootstrapping terminology is taken from [RFC4640].
Additional terminology is defined below: Additional terminology is defined below:
Authentication, Authorization, and Accounting (AAA): Authentication, Authorization, and Accounting (AAA):
AAA protocol based on Diameter [RFC3588] with required EAP support AAA protocol based on Diameter [RFC3588] with required EAP support
[RFC4072]. [RFC4072].
Home AAA (AAAH): Home AAA (AAAH):
An authentication, authorization and accounting server located in An authentication, authorization, and accounting server located in
user's home network i.e., in the home realm. the user's home network, i.e., in the home realm.
3. Application Identifiers 3. Application Identifiers
This specification defines two new Diameter applications and their This specification defines two new Diameter applications and their
respective Application Identifiers: respective Application Identifiers:
Diameter Mobile IPv6 IKE (MIP6I) TBD by IANA Diameter Mobile IPv6 IKE (MIP6I) 7
Diameter Mobile IPv6 Auth (MIP6A) TBD by IANA Diameter Mobile IPv6 Auth (MIP6A) 8
The MIP6I Application Identifier is used when the MN is authenticated The MIP6I Application Identifier is used when the MN is authenticated
and authorized using IKEv2. The MIP6A Application Identifier is used and authorized using IKEv2. The MIP6A Application Identifier is used
when the MN is authenticated and authorized using the Mobile IPv6 when the MN is authenticated and authorized using the Mobile IPv6
Authentication Protocol. Authentication Protocol.
Mobile IPv6 related accounting information generated by the HA uses Mobile IPv6-related accounting information generated by the HA uses
either the MIP6I or the MIP6A Application Identifier in the case of either the MIP6I or the MIP6A Application Identifier in the case of
coupled accounting model. The Diameter Base Accounting Application the coupled accounting model. The Diameter Base Accounting
Identifier (value of 3) is used in case of the split accounting Application Identifier (value of 3) is used in the case of the split
model. Refer to Section 4.4 for more information regarding the accounting model. Refer to Section 4.4 for more information
accounting models. regarding the accounting models.
4. Protocol Description 4. Protocol Description
4.1. Support for Mobile IPv6 with IKEv2 and EAP 4.1. Support for Mobile IPv6 with IKEv2 and EAP
The use of IKEv2 with EAP between the MN and the HA allows the AAA to The use of IKEv2 with EAP between the MN and the HA allows the AAA to
authenticate the MN. When EAP is used with IKEv2, the Diameter EAP authenticate the MN. When EAP is used with IKEv2, the Diameter EAP
application logic and procedures, as defined in [RFC4072], are re- application logic and procedures, as defined in [RFC4072], are re-
used. EAP methods that do not establish a shared key SHOULD NOT be used. EAP methods that do not establish a shared key SHOULD NOT be
used, as they are subject to a number of man-in-the-middle attacks as used, as they are subject to a number of man-in-the-middle attacks as
stated in Section 2.16 and Section 5 of [RFC4306]. AVPs specific to stated in Section 2.16 and Section 5 of [RFC4306]. Attribute-value
Mobile IPv6 bootstrapping are added to the EAP application commands. pairs (AVPs) specific to Mobile IPv6 bootstrapping are added to the
EAP application commands.
Figure 2 shows the message flow involved during the authentication Figure 2 shows the message flow involved during the authentication
phase when EAP is used. The communication between the mobile node phase when EAP is used. The communication between the mobile node
and the home agent use the conventions defined in [RFC4306]. and the home agent uses the conventions defined in [RFC4306].
Similarly, the communication between the home agent and the Diameter Similarly, the communication between the home agent and the Diameter
server use the conventions defined in [RFC4072]. server uses the conventions defined in [RFC4072].
Mobile Home Diameter Mobile Home Diameter
Node Agent Server Node Agent Server
| | | | | |
| HDR, SAi1, KEi, Ni (1) | | | HDR, SAi1, KEi, Ni (1) | |
|-------------------------------->| | |-------------------------------->| |
| | | | | |
| HDR, SAr1, KEr, Nr, [CERTREQ](2)| | | HDR, SAr1, KEr, Nr, [CERTREQ](2)| |
|<--------------------------------| | |<--------------------------------| |
| | | | | |
skipping to change at page 11, line 50 skipping to change at page 8, line 50
|<--------------------------------| | |<--------------------------------| |
| | | | | |
| HDR, SK{AUTH} | | | HDR, SK{AUTH} | |
|-------------------------------->| | |-------------------------------->| |
| | | | | |
| HDR, SK{AUTH, [CP(CFG_REPLY,] | | | HDR, SK{AUTH, [CP(CFG_REPLY,] | |
| SAr2, TSi, TSr} | | | SAr2, TSi, TSr} | |
|<--------------------------------| | |<--------------------------------| |
| | | | | |
Figure 2: Mobile IPv6 bootstrapping using IKEv2 and EAP Figure 2: Mobile IPv6 Bootstrapping Using IKEv2 and EAP
The MN and the HA start the interaction with an IKE_SA_INIT exchange. The MN and the HA start the interaction with an IKE_SA_INIT exchange.
In this phase cryptographic algorithms are negotiated, nonces and In this phase, cryptographic algorithms are negotiated, and nonces
Diffie-Hellman parameters are exchanged. Message (3) starts the and Diffie-Hellman parameters are exchanged. Message (3) starts the
IKE_AUTH phase. This second phase authenticates the previous IKE_AUTH phase. This second phase authenticates the previous
messages, exchanges identities and certificates and establishes the messages, exchanges identities and certificates, and establishes the
first CHILD_SA. It is used to mutually authenticate the MN (acting first CHILD_SA. It is used to mutually authenticate the MN (acting
as an IKEv2 Initiator) and the HA (acting as an IKEv2 Responder). as an IKEv2 initiator) and the HA (acting as an IKEv2 responder).
The identity of the user/MN is provided in the IDi field. The MN The identity of the user/MN is provided in the IDi field. The MN
indicates its willingness to be authenticated via EAP by omitting the indicates its willingness to be authenticated via EAP by omitting the
AUTH field in message (3) (see Section 2.16 of [RFC4306]). AUTH field in message (3) (see Section 2.16 of [RFC4306]).
As part of the authentication process, the MN MAY request a Home- As part of the authentication process, the MN MAY request a home
Address, a Home Prefix or suggests one, see [RFC4877], using a address or a home prefix or suggest one (see [RFC4877]), using a
CFG_REQUEST payload in the message (3). CFG_REQUEST payload in the message (3).
The HA extracts the IDi field from the message (3) and sends a The HA extracts the IDi field from the message (3) and sends a
Diameter-EAP-Request (DER) message (4) towards the authenticating Diameter-EAP-Request (DER) message (4) towards the authenticating
Diameter server. The EAP-Payload AVP contains a EAP-Response/ Diameter server. The EAP-Payload AVP contains a EAP-Response/
Identity with the identity extracted from the IDi field. Identity with the identity extracted from the IDi field.
This message is routed to the MN's Diameter server/EAP server. The This message is routed to the MN's Diameter server/EAP server. The
Diameter server selects the EAP method and replies with the Diameter- Diameter server selects the EAP method and replies with the Diameter-
EAP-Answer (DEA) Message. Depending on the type of EAP method EAP-Answer (DEA) message. Depending on the type of EAP method
chosen, a number of DER and DEA messages carry the method specific chosen, a number of DER and DEA messages carry the method-specific
exchanges between the MN and the Diameter server/EAP server. exchanges between the MN and the Diameter server/EAP server.
At the end of the EAP authentication phase, the Diameter server At the end of the EAP authentication phase, the Diameter server
indicates the result of the authentication in the Result-Code AVP and indicates the result of the authentication in the Result-Code AVP and
provides the corresponding EAP packet (EAP Success or EAP Failure). provides the corresponding EAP packet (EAP Success or EAP Failure).
The last IKEv2 message sent by the HA contains the Home Address or The last IKEv2 message sent by the HA contains the home address or
the Home Prefix. In the latter case, a CREATE_CHILD_SA exchange is the home prefix. In the latter case, a CREATE_CHILD_SA exchange is
necessary to setup IPsec SAs for Mobile IPv6 signaling. necessary to set up IPsec SAs for Mobile IPv6 signaling.
In some deployment scenarios, the HA may also act as an IKEv2 In some deployment scenarios, the HA may also act as an IKEv2
Responder for a conventional IPsec VPN access. The challenge in this responder for a conventional IPsec VPN access. The challenge in this
case is that the IKEv2 responder may not know if IKEv2 is used for case is that the IKEv2 responder may not know if IKEv2 is used for
Mobile IPv6 service or for IPsec VPN access service. A network Mobile IPv6 service or for IPsec VPN access service. A network
operator needs to be aware of this limitation. One solution already operator needs to be aware of this limitation. One solution already
supported by IKEv2 is to use different responder identities when supported by IKEv2 is to use different responder identities when
operating as a conventional IPsec VPN gateway or as a HA. The MN can operating as a conventional IPsec VPN gateway or as an HA. The MN
then indicate the preferred responder type using the appropriate IDr can then indicate the preferred responder type using the appropriate
payload in the IKE_AUTH message. IDr payload in the IKE_AUTH message.
Eventually, when the HA receives a Binding Update (BU), the HA Eventually, when the HA receives a Binding Update (BU), the HA
authenticates and authorizes the MN. It is RECOMMENDED that the HA authenticates and authorizes the MN. It is RECOMMENDED that the HA
sends an accounting request message every time it receives a BU. sends an accounting request message every time it receives a BU.
4.2. Support for the Mobile IPv6 Authentication Protocol 4.2. Support for the Mobile IPv6 Authentication Protocol
Figure 3 shows the message sequence between the MN, the HA and the Figure 3 shows the message sequence between the MN, the HA, and the
Diameter server during the registration when Mobile IPv6 Diameter server during the registration when Mobile IPv6
Authentication Protocol is used. A BU and a Binding Acknowledgement Authentication Protocol is used. A BU and a Binding Acknowledgement
(BA) messages are used in the binding registration process. (BA) messages are used in the binding registration process.
Receiving a BU at the HA initiates a MIP6-Request to be sent to the Receiving a BU at the HA initiates a MIP6-Request to be sent to the
Diameter server. The Diameter server in turn responds with a MIP6- Diameter server. The Diameter server in turn responds with a MIP6-
Answer. The HA may assign a Home Address to the MN and provide it to Answer. The HA may assign a home address to the MN and provide it to
the Diameter server in the MIP-Mobile-Node-Address AVP. the Diameter server in the MIP-Mobile-Node-Address AVP.
According to [RFC4285] the MN uses the Mobile Node Identifier Option, According to [RFC4285], the MN uses the Mobile Node Identifier
specifically the MN-NAI mobility option (as defined in [RFC4283]) to Option, specifically the MN-NAI mobility option (as defined in
identify itself. The HA MUST copy the MN-NAI mobility option value [RFC4283]) to identify itself. The HA MUST copy the MN-NAI mobility
to the User-Name AVP in the subsequent request messages. option value to the User-Name AVP in the subsequent request messages.
The procedure described in this specification for the Mobile IPv6 The procedure described in this specification for the Mobile IPv6
Authentication Protocol is only needed for the initially received BU Authentication Protocol is only needed for the initially received BU
for which the HA does not have an existing security association. for which the HA does not have an existing security association.
When the HA receives subsequent BUs, they are processed locally in When the HA receives subsequent BUs, they are processed locally in
the HA. It is RECOMMENDED that the HA sends an accounting request the HA. It is RECOMMENDED that the HA sends an accounting request
message every time it receives a Binding Update. However, the HA MAY message every time it receives a Binding Update. However, the HA MAY
re-authorize the MN with the Diameter server at any time depending on re-authorize the MN with the Diameter server at any time depending on
the deployment and the local policy. the deployment and the local policy.
This specification assumes that in the case Mobile IPv6 This specification assumes that in the case where Mobile IPv6
Authentication Protocol is used, the MN-AAA option is included in the Authentication Protocol is used, the MN-AAA option is included in the
BU as defined in [RFC4285] and the Diameter server computes required BU as defined in [RFC4285] and the Diameter server computes required
session keys after having successfully authenticated the MN. The session keys after having successfully authenticated the MN. The
computation of the session keys is out of scope of this computation of the session keys is out of scope of this
specification. Other possible ways of using Mobile IPv6 specification. Other possible ways of using the Mobile IPv6
Authentication Protocol are also out of scope of this specification Authentication Protocol are also out of scope of this specification
and would require a new specification to describe the detailed and would require a new specification to describe the detailed
behavior of the HA-AAAH interface and corresponding session key behavior of the HA-AAAH interface and corresponding session key
derivation. derivation.
Mobile Home Diameter Mobile Home Diameter
Node Agent Server Node Agent Server
| | | | | |
| | MIP6-Request + MIP6 | | | MIP6-Request + MIP6 |
| Binding Update | Bootstrapping AVPs | | Binding Update | Bootstrapping AVPs |
skipping to change at page 14, line 22 skipping to change at page 11, line 22
| Mobility Message Replay Protection | | | Mobility Message Replay Protection | |
| Option, Authentication Option) | | | Option, Authentication Option) | |
| | | | | |
| | MIP6-Answer + MIP6 | | | MIP6-Answer + MIP6 |
| Binding Acknowledgement | Bootstrapping AVPs | | Binding Acknowledgement | Bootstrapping AVPs |
|<------------------------------------|<--------------------| |<------------------------------------|<--------------------|
| (Mobile Node Identifier Option | | | (Mobile Node Identifier Option | |
| Mobility Message Replay Protection | | | Mobility Message Replay Protection | |
| Option, Authentication Option) | | | Option, Authentication Option) | |
Figure 3: Mobile IPv6 Bootstrapping using the Mobile IPv6 Figure 3: Mobile IPv6 Bootstrapping Using the Mobile IPv6
Authentication Protocol Authentication Protocol
4.3. Mobile IPv6 Session Management 4.3. Mobile IPv6 Session Management
The Diameter server may maintain state or may be stateless. This is The Diameter server may maintain state or may be stateless. This is
indicated in the Auth-Session-State AVP (or its absence). The HA indicated in the Auth-Session-State AVP (or its absence). The HA
MUST support the Authorization Session State Machine defined in MUST support the Authorization Session State Machine defined in
[RFC3588]. [RFC3588].
This specification makes an assumption that each SA created between This specification makes an assumption that each SA created between
the MN and the HA as a result of a successful IKEv2 negotiation or a the MN and the HA as a result of a successful IKEv2 negotiation or a
Mobile IPv6 Authentication Protocol exchange correspond to one Mobile IPv6 Authentication Protocol exchange corresponds to one
Diameter session. In IKEv2 case we specifically mean the created IKE Diameter session. In the IKEv2 case, we specifically mean the
SA. created IKE SA.
4.3.1. Session-Termination-Request 4.3.1. Session-Termination-Request
The Session-Termination-Request (STR) message [RFC3588] is sent by The Session-Termination-Request (STR) message [RFC3588] is sent by
the HA to inform the Diameter server that an authorized session is the HA to inform the Diameter server that an authorized session is
being terminated. This means that the HA MUST terminate the being terminated. This means that the HA MUST terminate the
corresponding Mobile IPv6 binding and also terminate the corresponding Mobile IPv6 binding and also terminate the
corresponding SA. corresponding SA.
4.3.2. Session-Termination-Answer 4.3.2. Session-Termination-Answer
The Session-Termination-Answer (STA) message [RFC3588] is sent by the The Session-Termination-Answer (STA) message [RFC3588] is sent by the
Diameter server to acknowledge the notification that the session has Diameter server to acknowledge the notification that the session has
been terminated. been terminated.
4.3.3. Abort-Session-Request 4.3.3. Abort-Session-Request
The Abort-Session-Request (ASR) message [RFC3588] is sent by the The Abort-Session-Request (ASR) message [RFC3588] is sent by the
Diameter server to the HA to terminate the authorized session. This Diameter server to the HA to terminate the authorized session. This
fulfills one of the requirement described in fulfills one of the requirement described in [RFC5637]. When the HA
[I-D.ietf-mext-aaa-ha-goals]. When the HA receives the ASR message, receives the ASR message, it MUST terminate the corresponding SA.
it MUST terminate the corresponding SA. Subsequently, the HA MUST Subsequently, the HA MUST take further actions to terminate the
take further actions to terminate the corresponding Mobile IPv6 corresponding Mobile IPv6 binding.
binding.
4.3.4. Abort-Session-Answer 4.3.4. Abort-Session-Answer
The Abort-Session-Answer (ASA) message [RFC3588] is sent by the Home The Abort-Session-Answer (ASA) message [RFC3588] is sent by the home
Agent in response to an ASR message. agent in response to an ASR message.
4.4. Accounting for Mobile IPv6 services 4.4. Accounting for Mobile IPv6 Services
The HA MUST be able act as a Diameter client collecting accounting The HA MUST be able act as a Diameter client collecting accounting
records needed for service control and charging. The HA MUST support records needed for service control and charging. The HA MUST support
the accounting procedures (specifically the command codes mentioned the accounting procedures (specifically the command codes mentioned
below) and the Accounting Session State Machine as defined in below) and the Accounting Session State Machine as defined in
[RFC3588]. The command codes, exchanged between the HA and Diameter [RFC3588]. The command codes, exchanged between the HA and Diameter
server for accounting purposes, are provided in the following server for accounting purposes, are provided in the following
subsections. subsections.
The Diameter application design guideline The Diameter application design guideline [DIME-APP] defines two
[I-D.ietf-dime-app-design-guide] defines two separate models for separate models for accounting:
accounting:
Split accounting model: Split accounting model:
According to this model, the accounting messages use the Diameter According to this model, the accounting messages use the Diameter
Base Accounting Application Identifier (value of 3). Since Base Accounting Application Identifier (value of 3). Since
accounting is treated as an independent application, accounting accounting is treated as an independent application, accounting
commands may be routed separately from the rest of application commands may be routed separately from the rest of application
messages and thus the accounting messages generally end up in a messages and thus the accounting messages generally end up in a
central accounting server. Since Diameter Mobile IPv6 application central accounting server. Since the Diameter Mobile IPv6
does not define its own unique accounting commands, this is the application does not define its own unique accounting commands,
preferred choice, since it permits use of centralized accounting this is the preferred choice, since it permits use of centralized
for several applications. accounting for several applications.
Coupled accounting model: Coupled accounting model:
In this model, the accounting messages will use either the MIP6I In this model, the accounting messages will use either the MIP6I
or the MIP6A Application Identifiers. This means that accounting or the MIP6A Application Identifiers. This means that accounting
messages will be routed like any other Mobile IPv6 application messages will be routed like any other Mobile IPv6 application
messages. This requires the Diameter server in charge of Mobile messages. This requires the Diameter server in charge of Mobile
IPv6 application to handle the accounting records (e.g., sends IPv6 application to handle the accounting records (e.g., sends
them to a proper accounting server). them to a proper accounting server).
skipping to change at page 17, line 9 skipping to change at page 13, line 24
4.4.2. Accounting-Answer 4.4.2. Accounting-Answer
The Accounting-Answer command [RFC3588] is sent by the Diameter The Accounting-Answer command [RFC3588] is sent by the Diameter
server to the HA to acknowledge an Accounting-Request. server to the HA to acknowledge an Accounting-Request.
5. Command Codes 5. Command Codes
5.1. Command Code for Mobile IPv6 with IKEv2 and EAP 5.1. Command Code for Mobile IPv6 with IKEv2 and EAP
For the use of Mobile IPv6 with IKEv2 and EAP this document reuses For the use of Mobile IPv6 with IKEv2 and EAP, this document reuses
the Diameter EAP application [RFC4072] commands: Diameter-EAP-Request the Diameter EAP application [RFC4072] commands: Diameter-EAP-Request
(DER) and Diameter-EAP-Answer (DEA). This specification extends the (DER) and Diameter-EAP-Answer (DEA). This specification extends the
existing DER and DEA command ABNFs with a number of AVPs to support existing DER and DEA command ABNFs with a number of AVPs to support
Mobile IPv6 split scenario bootstrapping. Other than new additional Mobile IPv6 split scenario bootstrapping. Other than new additional
AVPs and the corresponding additions to the command ABNFs, the AVPs and the corresponding additions to the command ABNFs, the
Diameter EAP application command ABNFs remain unchanged. The ABNF Diameter EAP application command ABNFs remain unchanged. The ABNF
language is defined in [RFC3588]. language is defined in [RFC3588].
Command-Name Abbrev. Code Reference Application Command-Name Abbrev. Code Reference Application
--------------------------------------------------------------------- ---------------------------------------------------------------------
skipping to change at page 17, line 32 skipping to change at page 13, line 47
Figure 4: Command Codes Figure 4: Command Codes
5.1.1. Diameter-EAP-Request 5.1.1. Diameter-EAP-Request
The Diameter-EAP-Request (DER) message, indicated by the Command-Code The Diameter-EAP-Request (DER) message, indicated by the Command-Code
field set to 268 and the 'R' bit set in the Command Flags field, is field set to 268 and the 'R' bit set in the Command Flags field, is
sent by the HA to the Diameter server to initiate a Mobile IPv6 sent by the HA to the Diameter server to initiate a Mobile IPv6
service authentication and authorization procedure. The service authentication and authorization procedure. The
Application-ID field of the Diameter Header MUST be set to the Application-ID field of the Diameter Header MUST be set to the
Diameter Mobile IPv6 IKE Application ID (value of TDB). Diameter Mobile IPv6 IKE Application ID (value of 7). The grouped
AVP has the following modified ABNF (as defined in [RFC3588]):
<Diameter-EAP-Request> ::= < Diameter Header: 268, REQ, PXY > <Diameter-EAP-Request> ::= < Diameter Header: 268, REQ, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Destination-Realm } { Destination-Realm }
{ Auth-Request-Type } { Auth-Request-Type }
[ Destination-Host ] [ Destination-Host ]
[ NAS-Identifier ] [ NAS-Identifier ]
skipping to change at page 18, line 33 skipping to change at page 14, line 33
*2[ MIP-Mobile-Node-Address ] *2[ MIP-Mobile-Node-Address ]
[ Chargeable-User-Identity ] [ Chargeable-User-Identity ]
[ Service-Selection ] [ Service-Selection ]
[ QoS-Capability ] [ QoS-Capability ]
* [ QoS-Resources ] * [ QoS-Resources ]
... ...
* [ AVP ] * [ AVP ]
Mobile IPv6 bootstrapping AVPs are only included in the first DER Mobile IPv6 bootstrapping AVPs are only included in the first DER
message send by the HA. The subsequent DER messages required by the message send by the HA. The subsequent DER messages required by the
EAP-method do not need to include any Mobile IPv6 bootstrapping AVPs. EAP method do not need to include any Mobile IPv6 bootstrapping AVPs.
The MN is both authenticated and authorized for the mobility service The MN is both authenticated and authorized for the mobility service
during the EAP authentication. Thus, the Auth-Request-Type AVP MUST during the EAP authentication. Thus, the Auth-Request-Type AVP MUST
be set to the value AUTHORIZE_AUTHENTICATE. be set to the value AUTHORIZE_AUTHENTICATE.
5.1.2. Diameter-EAP-Answer 5.1.2. Diameter-EAP-Answer
The Diameter-EAP-Answer (DEA) message, indicated by the Command-Code The Diameter-EAP-Answer (DEA) message, indicated by the Command-Code
field set to 268 and 'R' bit cleared in the Command Flags field, is field set to 268 and 'R' bit cleared in the Command Flags field, is
sent in response to the Diameter-EAP-Request message (DER). The sent in response to the Diameter-EAP-Request (DER) message. The
Application-Id field in the Diameter message header MUST be set to Application-Id field in the Diameter message header MUST be set to
the Diameter Mobile IPv6 IKE Application-Id (value of TBD). If the the Diameter Mobile IPv6 IKE Application-Id (value of 7). If the
Mobile IPv6 authentication procedure was successful then the response Mobile IPv6 authentication procedure was successful, then the
MAY include any set of bootstrapping AVPs. response MAY include any set of bootstrapping AVPs.
<Diameter-EAP-Answer> ::= < Diameter Header: 268, PXY > <Diameter-EAP-Answer> ::= < Diameter Header: 268, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Auth-Request-Type } { Auth-Request-Type }
{ Result-Code } { Result-Code }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
[ User-Name ] [ User-Name ]
[ EAP-Payload ] [ EAP-Payload ]
skipping to change at page 19, line 39 skipping to change at page 15, line 39
mobility service succeeds, then the Mobile IPv6 bootstrapping AVPs mobility service succeeds, then the Mobile IPv6 bootstrapping AVPs
are included in the last DEA message that also carries the EAP- are included in the last DEA message that also carries the EAP-
Success EAP payload. The other DEA messages required by the used Success EAP payload. The other DEA messages required by the used
EAP-method do not include any Mobile IPv6 bootstrapping AVPs. EAP-method do not include any Mobile IPv6 bootstrapping AVPs.
5.2. Command Codes for Mobile IPv6 Authentication Protocol Support 5.2. Command Codes for Mobile IPv6 Authentication Protocol Support
This section defines the commands that are used for support with the This section defines the commands that are used for support with the
Mobile IPv6 Authentication Protocol. Mobile IPv6 Authentication Protocol.
There are multiple ways of deploying and utilizing Mobile IPv6 There are multiple ways of deploying and utilizing the Mobile IPv6
Authentication Protocol, especially regarding the associated AAA Authentication Protocol, especially regarding the associated AAA
interactions. In order to support multiple deployment models this interactions. In order to support multiple deployment models, this
specification defines the MIP6-Auth-Mode AVP that in the request specification defines the MIP6-Auth-Mode AVP that in the request
message tells the mode that the HA supports. This specification message tells the mode that the HA supports. This specification
defines a method that requires the use of the MN-AAA option with the defines a method that requires the use of the MN-AAA option with the
Mobile IPv6 Authentication Protocol. Mobile IPv6 Authentication Protocol.
Command-Name Abbrev. Code Reference Application Command-Name Abbrev. Code Reference Application
--------------------------------------------------------------------- ---------------------------------------------------------------------
MIP6-Request MIR TBD 5.3.1 Diameter Mobile IPv6 Auth MIP6-Request MIR 325 5.3.1 Diameter Mobile IPv6 Auth
MIP6-Answer MIA TBD 5.3.2 Diameter Mobile IPv6 Auth MIP6-Answer MIA 325 5.3.2 Diameter Mobile IPv6 Auth
Command Codes Command Codes
5.2.1. MIP6-Request 5.2.1. MIP6-Request
The MIP6-Request (MIR), indicated by the Command-Code field set to The MIP6-Request (MIR), indicated by the Command-Code field set to
TBD and the 'R' bit set in the Command Flags field, is sent by the 325 and the 'R' bit set in the Command Flags field, is sent by the
HA, acting as a Diameter client, in order to request the HA, acting as a Diameter client, in order to request the
authentication and authorization of a MN. authentication and authorization of an MN.
Although the HA provides the Diameter server with replay protection Although the HA provides the Diameter server with replay protection-
related information, the HA is responsible for the replay protection. related information, the HA is responsible for the replay protection.
The message format is shown below. The message format is shown below.
<MIP6-Request> ::= < Diameter Header: TBD, REQ, PXY > <MIP6-Request> ::= < Diameter Header: 325, REQ, PXY >
< Session-ID > < Session-ID >
{ Auth-Application-Id } { Auth-Application-Id }
{ User-Name } { User-Name }
{ Destination-Realm } { Destination-Realm }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Auth-Request-Type } { Auth-Request-Type }
[ Destination-Host ] [ Destination-Host ]
[ Origin-State-Id ] [ Origin-State-Id ]
[ NAS-Identifier ] [ NAS-Identifier ]
skipping to change at page 21, line 49 skipping to change at page 17, line 49
* [ AVP ] * [ AVP ]
If the MN is both authenticated and authorized for the mobility If the MN is both authenticated and authorized for the mobility
service, then the Auth-Request-Type AVP is set to the value service, then the Auth-Request-Type AVP is set to the value
AUTHORIZE_AUTHENTICATE. This is the case when the MIP6-Auth-Mode is AUTHORIZE_AUTHENTICATE. This is the case when the MIP6-Auth-Mode is
set to the value MIP6_AUTH_MN_AAA. set to the value MIP6_AUTH_MN_AAA.
5.2.2. MIP6-Answer 5.2.2. MIP6-Answer
The MIP6-Answer (MIA) message, indicated by the Command-Code field The MIP6-Answer (MIA) message, indicated by the Command-Code field
set to TBD and the 'R' bit cleared in the Command Flags field, is set to 325 and the 'R' bit cleared in the Command Flags field, is
sent by the Diameter server in response to the MIP6-Request message. sent by the Diameter server in response to the MIP6-Request message.
The User-Name AVP MAY be included in the MIA if it is present in the The User-Name AVP MAY be included in the MIA if it is present in the
MIR. The Result-Code AVP MAY contain one of the values defined in MIR. The Result-Code AVP MAY contain one of the values defined in
Section 7, in addition to the values defined in [RFC3588]. Section 7, in addition to the values defined in [RFC3588].
An MIA message with the Result-Code AVP set to DIAMETER_SUCCESS MUST An MIA message with the Result-Code AVP set to DIAMETER_SUCCESS MUST
include the MIP-Mobile-Node-Address AVP. include the MIP-Mobile-Node-Address AVP.
The message format is shown below. The message format is shown below.
<MIP6-Answer> ::= < Diameter Header: TBD, PXY > <MIP6-Answer> ::= < Diameter Header: 325, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Result-Code } { Result-Code }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Auth-Request-Type } { Auth-Request-Type }
[ User-Name ] [ User-Name ]
[ Authorization-Lifetime ] [ Authorization-Lifetime ]
[ Auth-Session-State ] [ Auth-Session-State ]
[ Error-Message ] [ Error-Message ]
skipping to change at page 23, line 7 skipping to change at page 18, line 44
[ Origin-State-Id ] [ Origin-State-Id ]
* [ Proxy-Info ] * [ Proxy-Info ]
* [ Redirect-Host ] * [ Redirect-Host ]
[ Redirect-Host-Usage ] [ Redirect-Host-Usage ]
[ Redirect-Max-Cache-Time ] [ Redirect-Max-Cache-Time ]
* [ Failed-AVP ] * [ Failed-AVP ]
* [ AVP ] * [ AVP ]
6. AVPs 6. AVPs
To provide support for [RFC4285] and for [RFC4877] the AVPs in the To provide support for [RFC4285] and for [RFC4877], the AVPs in the
following subsections are needed. [RFC3588], [RFC4004] and [RFC4005] following subsections are needed. [RFC3588], [RFC4004], and
defined AVPs are reused whenever possible without changing the [RFC4005] defined AVPs are reused whenever possible without changing
existing semantics of those AVPs. the existing semantics of those AVPs.
+--------------------+ +--------------------+
| AVP Flag rules | | AVP Flag Rules |
+----+---+------+----+----+ +----+---+------+----+----+
AVP Defined | | |SHOULD|MUST|MAY | AVP Defined | | |SHOULD|MUST|MAY |
Attribute Name Code in Value Type |MUST|MAY| NOT | NOT|Encr| Attribute Name Code in Value Type |MUST|MAY| NOT | NOT|Encr|
+-----------------------------------------+----+---+------+----+----+ +------------------------------------------+----+---+------+----+----+
|MIP6-Feature- 124 RFC5447 Unsigned64 | M | P | | V | Y | |MIP6-Feature- 124 RFC 5447 Unsigned64 | M | P | | V | Y |
| Vector | | | | | | | Vector | | | | | |
+-----------------------------------------+----+---+------+----+----+ +------------------------------------------+----+---+------+----+----+
|MIP-Mobile- | M | P | | V | Y | |MIP-Mobile- | M | P | | V | Y |
| Node-Address 334 RFC4004 Address | | | | | | | Node-Address 333 RFC 4004 Address | | | | | |
+-----------------------------------------+----+---+------+----+----+ +------------------------------------------+----+---+------+----+----+
|MIP6-Agent-Info 486 RFC5447 Grouped | M | P | | V | Y | |MIP6-Agent-Info 486 RFC 5447 Grouped | M | P | | V | Y |
+-----------------------------------------+----+---+------+----+----+ +------------------------------------------+----+---+------+----+----+
|User-Name 1 RFC3588 UTF8String | M | P | | V | Y | |User-Name 1 RFC 3588 UTF8String | M | P | | V | Y |
+-----------------------------------------+----+---+------+----+----+ +------------------------------------------+----+---+------+----+----+
|Service- TBD 6.2 UTF8String | M | P | | V | Y | |Service- 493 6.2 UTF8String | M | P | | V | Y |
| Selection | | | | | | | Selection | | | | | |
+-----------------------------------------+----+---+------+----+----+ +------------------------------------------+----+---+------+----+----+
|QoS-Capability TBD Note 1 Grouped | M | P | | V | Y | |QoS-Capability 578 Note 1 Grouped | M | P | | V | Y |
+-----------------------------------------+----+---+------+----+----+ +------------------------------------------+----+---+------+----+----+
|QoS-Resources TBD Note 1 Grouped | M | P | | V | Y | |QoS-Resources 508 Note 1 Grouped | M | P | | V | Y |
+-----------------------------------------+----+---+------+----+----+ +------------------------------------------+----+---+------+----+----+
|MIP-MN-HA-MSA TBD 6.12 Grouped | M | P | | V | Y | |MIP-MN-HA-MSA 492 6.12 Grouped | M | P | | V | Y |
+-----------------------------------------+----+---+------+----+----+ +------------------------------------------+----+---+------+----+----+
|Chargeable-User- OctetString| M | P | | V | Y | |Chargeable-User- OctetString| M | P | | V | Y |
| Identity 89 6.19 | | | | | | | Identity 89 6.19 | | | | | |
+-----------------------------------------+----+---+------+----+----+ +------------------------------------------+----+---+------+----+----+
AVPs for Mobile IPv6 IKE Application AVPs for Mobile IPv6 IKE Application
Note 1: The QoS-Capability and the QoS-Resource AVPs are defined in Note 1: The QoS-Capability and the QoS-Resource AVPs are defined in
Sections 4.1 and 4.3 of [I-D.ietf-dime-qos-attributes]. Sections 4.1 and 4.3 of [RFC5777].
+--------------------+ +--------------------+
| AVP Flag rules | | AVP Flag Rules |
+----+---+------+----+----+ +----+---+------+----+----+
AVP Section | | |SHOULD|MUST|MAY | AVP Section | | |SHOULD|MUST|MAY |
Attribute Name Code Defined Value Type |MUST|MAY| NOT | NOT|Encr| Attribute Name Code Defined Value Type |MUST|MAY| NOT | NOT|Encr|
+------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |MIP6-Feature- 124 RFC 5447 Unsigned64 | M | P | | V | Y |
|MIP6-Feature- 124 RFC5447 Unsigned64 | M | P | | V | Y | | Vector | | | | | |
| Vector | | | | | | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |User-Name 1 RFC 3588 UTF8String | M | P | | V | Y |
|User-Name 1 RFC3588 UTF8String | M | P | | V | Y | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |Service- 493 6.2 UTF8String | M | P | | V | Y |
|Service- TBD 6.2 UTF8String | M | P | | V | Y | | Selection | | | | | |
| Selection | | | | | | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |MIP-MN-AAA-SPI 341 RFC 4004 Unsigned32 | M | P | | V | Y |
|MIP-MN-AAA-SPI 341 RFC4004 Unsigned32 | M | P | | V | Y | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |MIP-MN-HA-SPI 491 6.4 Unsigned32 | M | P | | V | Y |
|MIP-MN-HA-SPI TBD 6.4 Unsigned32 | M | P | | V | Y | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |MIP-Mobile- 333 RFC 4004 Address | M | P | | V | Y |
|MIP-Mobile- 333 RFC4004 Address | M | P | | V | Y | | Node-Address | | | | | |
| Node-Address | | | | | | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |MIP6-Agent-Info 486 RFC 5447 Grouped | M | P | | V | Y |
|MIP6-Agent-Info 486 RFC5447 Grouped | M | P | | V | Y | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |MIP-Careof- 487 6.7 Address | M | P | | V | Y |
|MIP-Careof- TBD 6.7 Address | M | P | | V | Y | | Address | | | | | |
| Address | | | | | | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |MIP- 488 6.8 OctetString| M | P | | V | Y |
|MIP- TBD 6.8 OctetString| M | P | | V | Y | | Authenticator | | | | | |
| Authenticator | | | | | | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |MIP-MAC- 489 6.9 OctetString| M | P | | V | Y |
|MIP-MAC- TBD 6.9 OctetString| M | P | | V | Y | | Mobility-Data | | | | | |
| Mobility-Data | | | | | | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |MIP-Session-Key 343 6.10 OctetString| M | P | | V | Y |
|MIP-Session-Key 343 6.10 OctetString| M | P | | V | Y | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |MIP-MSA- 367 RFC 4004 Unsigned32 | M | P | | V | Y |
|MIP-MSA- 367 RFC4004 Unsigned32 | M | P | | V | Y | | Lifetime | | | | | |
| Lifetime | | | | | | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |MIP-MN-HA-MSA 492 6.12 Grouped | M | P | | V | Y |
|MIP-MN-HA-MSA TBD 6.12 Grouped | M | P | | V | Y | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |MIP-Algorithm- 345 6.13 Enumerated | M | P | | V | Y |
|MIP-Algorithm- 345 6.13 Enumerated | M | P | | V | Y | | Type | | | | | |
| Type | | | | | | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |MIP-Replay-Mode 346 6.14 Enumerated | M | P | | V | Y |
|MIP-Replay-Mode 346 6.14 Enumerated | M | P | | V | Y | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |MIP-Timestamp 490 6.16 OctetString| M | P | | V | Y |
|MIP-Timestamp TBD 6.16 OctetString| M | P | | V | Y | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |QoS-Capability 578 Note 1 Grouped | M | P | | V | Y |
|QoS-Capability TBD Note 1 Grouped | M | P | | V | Y | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |QoS-Resources 508 Note 1 Grouped | M | P | | V | Y |
|QoS-Resources TBD Note 1 Grouped | M | P | | V | Y | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |Chargeable-User- OctetString| M | P | | V | Y |
|Chargeable-User- OctetString| M | P | | V | Y | | Identity 89 6.19 | | | | | |
| Identity 89 6.19 | | | | | | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |MIP6-Auth-Mode 494 6.20 Enumerated | M | P | | V | Y |
|MIP6-Auth-Mode TBD 6.20 Enumerated | M | P | | V | Y | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+ |Rest of the AVPs RFC 3588 | M | P | | V | Y |
|Rest of the AVPs RFC3588 | M | P | | V | Y | |in the MIR & MIA RFC 4005 | | | | | |
|in the MIR & MIA RFC4005 | | | | | | |excluding *[AVP] | | | | | |
|excluding *[AVP] | | | | | | +------------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+---+------+----+----+
AVPs for the Mobile IPv6 Auth Application AVPs for the Mobile IPv6 Auth Application
Note 1: The QoS-Capability and the QoS-Resource AVPs are defined in Note 1: The QoS-Capability and the QoS-Resource AVPs are defined in
Sections 4.1 and 4.3 of [I-D.ietf-dime-qos-attributes]. Sections 4.1 and 4.3 of [RFC5777].
6.1. User-Name AVP 6.1. User-Name AVP
The User-Name AVP (AVP Code 1) is of type UTF8String and contains an The User-Name AVP (AVP Code 1) is of type UTF8String and contains a
NAI extracted from the MN-NAI mobility option included in the Network Access Identifier (NAI) extracted from the MN-NAI mobility
received BU message. Alternatively, the NAI can be extracted from option included in the received BU message. Alternatively, the NAI
the IKEv2 IDi payload included in the IKE_AUTH message sent by the can be extracted from the IKEv2 IDi payload included in the IKE_AUTH
IKE initiator. message sent by the IKE initiator.
6.2. Service-Selection AVP 6.2. Service-Selection AVP
The Service-Selection AVP (AVP Code TBD) is of type UTF8String and The Service-Selection AVP (AVP Code 493) is of type UTF8String and
contains the name of the service or the external network that the contains the name of the service or the external network with which
mobility service should be associated with. In the scope of this the mobility service should be associated. In the scope of this
specification the value can extracted from the IKEv2 IDr payload, if specification, the value can be extracted from the IKEv2 IDr payload,
available in the IKE_AUTH message sent by the IKE initiator. if available in the IKE_AUTH message sent by the IKE initiator.
Alternatively, if the Mobile IPv6 Authentication Protocol is used, Alternatively, if the Mobile IPv6 Authentication Protocol is used,
then the Service-Selection AVP contains the string extracted from the then the Service-Selection AVP contains the string extracted from the
Service Selection Mobility Option [RFC5149], if available in the Service Selection Mobility Option [RFC5149], if available in the
received BU. Future specification may define additional ways to received BU. Future specifications may define additional ways to
populate the Service-Selection AVP with the required information. populate the Service-Selection AVP with the required information.
The AVP is also available to be used in messages sent from the The AVP is also available to be used in messages sent from the
Diameter server to the Diameter client. For example, if the request Diameter server to the Diameter client. For example, if the request
message did not contain the Service-Selection AVP but the MN was message did not contain the Service-Selection AVP but the MN was
assigned with a default service, the Diameter server MAY return the assigned with a default service, the Diameter server MAY return the
name of the assigned default service to the HA. name of the assigned default service to the HA.
If the Service-Selection AVP is present in both the request and the If the Service-Selection AVP is present in both the request and the
reply messages, it SHOULD contain the same service name. If the reply messages, it SHOULD contain the same service name. If the
services differ, the HA MAY treat that as authorization failure. services differ, the HA MAY treat that as authorization failure.
6.3. MIP-MN-AAA-SPI AVP 6.3. MIP-MN-AAA-SPI AVP
The MIP-MN-AAA-SPI AVP (AVP Code 341) is of type Unsigned32 and The MIP-MN-AAA-SPI AVP (AVP Code 341) is of type Unsigned32 and
contains an SPI code extracted from the Mobility Message contains a Security Parameter Index (SPI) code extracted from the
Authentication Option included in the received BU message. This AVP Mobility Message Authentication Option included in the received BU
is re-used from [RFC4004]. message. This AVP is reused from [RFC4004].
When the MIP6-Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA, this When the MIP6-Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA, this
AVP MUST be present in the MIR message. AVP MUST be present in the MIR message.
6.4. MIP-MN-HA-SPI AVP 6.4. MIP-MN-HA-SPI AVP
The MIP-MN-HA-SPI AVP (AVP Code TBD) is of type Unsigned32 and The MIP-MN-HA-SPI AVP (AVP Code 491) is of type Unsigned32 and
contains an SPI value that can be used with other parameters for contains an SPI value that can be used with other parameters for
identifying the security association required for the validation of identifying the security association required for the validation of
the Mobile IPv6 MN-HA Authentication Option. the Mobile IPv6 MN-HA Authentication Option.
When the MIP6-Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA, and the When the MIP6-Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA, and the
Diameter server returns a valid MIP-MN-HA-MSA AVP in the MIA message, Diameter server returns a valid MIP-MN-HA-MSA AVP in the MIA message,
this AVP MUST be present inside the MIP-MN-HA-MSA AVP. this AVP MUST be present inside the MIP-MN-HA-MSA AVP.
6.5. MIP-Mobile-Node-Address AVP 6.5. MIP-Mobile-Node-Address AVP
The MIP-Mobile-Node-Address AVP (AVP Code 333) is of type Address and The MIP-Mobile-Node-Address AVP (AVP Code 333) is of type Address and
contains the HA assigned IPv6 or IPv4 Home Address of the Mobile contains the HA assigned IPv6 or IPv4 home address of the mobile
Node. node.
If the MIP-Mobile-Node-Address AVP contains the unspecified IPv6 If the MIP-Mobile-Node-Address AVP contains the unspecified IPv6
address (0::0) or the all zeroes IPv4 address (0.0.0.0) in a request address (0::0) or the all-zeroes IPv4 address (0.0.0.0) in a request
message, then the HA expects the Diameter server to assign the Home message, then the HA expects the Diameter server to assign the home
Address in a subsequent answer message. If the Diameter server address in a subsequent answer message. If the Diameter server
assigns only an IPv6 Home Network Prefix to the Mobile Node the lower assigns only an IPv6 home network prefix to the mobile node, the
64 bits of the MIP-Mobile-Node-Address AVP provided address MUST be lower 64 bits of the MIP-Mobile-Node-Address AVP provided address
set to zero. MUST be set to zero.
This AVP is re-used from [RFC4004]. This AVP is reused from [RFC4004].
6.6. MIP6-Agent-Info AVP 6.6. MIP6-Agent-Info AVP
The MIP6-Agent-Info AVP (AVP Code 486) is defined in Section 4.2.1 of The MIP6-Agent-Info AVP (AVP Code 486) is defined in Section 4.2.1 of
[RFC5447] and contains the IPv6 or the IPv4 address information of [RFC5447] and contains the IPv6 or the IPv4 address information of
the HA. The HA address in a request message is the same as in the the HA. The HA address in a request message is the same as in the
received BU message that triggered the authentication and received BU message that triggered the authentication and
authorization procedure towards the Diameter server. One use case is authorization procedure towards the Diameter server. One use case
e.g., to inform the Diameter server of the dynamically assigned HA. is, e.g., to inform the Diameter server of the dynamically assigned
HA.
If the MIP6-Agent-Info AVP is present in an answer message and the If the MIP6-Agent-Info AVP is present in an answer message and the
Result-Code AVP is set to DIAMETER_SUCCESS_RELOCATE_HA, then the Result-Code AVP is set to DIAMETER_SUCCESS_RELOCATE_HA, then the
Diameter server is indicating to the HA that it MUST initiate a HA Diameter server is indicating to the HA that it MUST initiate an HA
switch procedure towards the MN (e.g., using the procedure defined in switch procedure towards the MN (e.g., using the procedure defined in
[RFC5142]). If the Result-Code AVP is set to any other value, then [RFC5142]). If the Result-Code AVP is set to any other value, then
the HA SHOULD initiate the HA switch procedure towards the MN. The the HA SHOULD initiate the HA switch procedure towards the MN. The
address information of the assigned HA is defined in the MIP6-Agent- address information of the assigned HA is defined in the MIP6-Agent-
Info AVP. Info AVP.
6.7. MIP-Careof-Address AVP 6.7. MIP-Careof-Address AVP
The MIP-Careof-Address AVP (AVP Code TBD) is of type Address and The MIP-Careof-Address AVP (AVP Code 487) is of type Address and
contains the IPv6 or the IPv4 Care-of Address of the Mobile Node. contains the IPv6 or the IPv4 care-of address of the mobile node.
The HA extracts this IP address from the received BU message. The HA extracts this IP address from the received BU message.
6.8. MIP-Authenticator AVP 6.8. MIP-Authenticator AVP
The MIP-Authenticator AVP (AVP Code TBD) is of type OctetString and The MIP-Authenticator AVP (AVP Code 488) is of type OctetString and
contains the Authenticator Data from the received BU message. The HA contains the Authenticator Data from the received BU message. The HA
extracts this data from the MN-AAA Mobility Message Authentication extracts this data from the MN-AAA Mobility Message Authentication
Option included in the received BU message. Option included in the received BU message.
When the MIP6-Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA, this When the MIP6-Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA, this
AVP MUST be present in the MIR message. AVP MUST be present in the MIR message.
6.9. MIP-MAC-Mobility-Data AVP 6.9. MIP-MAC-Mobility-Data AVP
The MIP-MAC-Mobility-Data AVP (AVP Code TBD) is of type OctetString The MIP-MAC-Mobility-Data AVP (AVP Code 489) is of type OctetString
and contains the MAC_Mobility_Data calculated by the HA as defined in and contains the MAC_Mobility_Data calculated by the HA as defined in
[RFC4285] for the MN-AAA Mobility Message Authentication Option. [RFC4285] for the MN-AAA Mobility Message Authentication Option.
When the MIP6-Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA, this When the MIP6-Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA, this
AVP MUST be present in the MIR message. AVP MUST be present in the MIR message.
6.10. MIP-Session-Key AVP 6.10. MIP-Session-Key AVP
The MIP-Session-Key AVP (AVP Code 343) is of type OctetString and The MIP-Session-Key AVP (AVP Code 343) is of type OctetString and
contains the MN-HA shared secret (i.e., the session key) for the contains the MN-HA shared secret (i.e., the session key) for the
associated Mobile IPv6 MH-HA authentication option. When the associated Mobile IPv6 MN-HA authentication option. When the
Diameter server computes the session key it is placed in this AVP. Diameter server computes the session key, it is placed in this AVP.
How the Diameter server computes the session key is not defined in How the Diameter server computes the session key is not defined in
this specification. The Session key derivation is deployment this specification. The Session key derivation is deployment
specific and needs to be defines in a respective deployment specific specific and needs to be defined in a respective deployment-specific
system specification. system specification.
This AVP is re-used from [RFC4004]. This AVP is reused from [RFC4004].
6.11. MIP-MSA-Lifetime AVP 6.11. MIP-MSA-Lifetime AVP
The MIP-MSA-Lifetime AVP (AVP Code 367) is of type Unsigned32 and The MIP-MSA-Lifetime AVP (AVP Code 367) is of type Unsigned32 and
represents the period of time (in seconds) for which the session key represents the period of time (in seconds) for which the session key
(see Section 6.10) is valid. The associated session key MUST NOT be (see Section 6.10) is valid. The associated session key MUST NOT be
used if the lifetime has expired. used if the lifetime has expired.
This AVP is re-used from [RFC4004]. This AVP is reused from [RFC4004].
6.12. MIP-MN-HA-MSA AVP 6.12. MIP-MN-HA-MSA AVP
The MIP-MN-HA-MSA AVP (AVP Code TBD) is of type Grouped and contains The MIP-MN-HA-MSA AVP (AVP Code 492) is of type Grouped and contains
the session related information for use with the Mobile IPv6 the session-related information for use with the Mobile IPv6
Authentication Protocol. Authentication Protocol.
MIP-MN-HA-MSA ::= < AVP Header: TBD > MIP-MN-HA-MSA ::= < AVP Header: 492 >
{ MIP-Session-Key } { MIP-Session-Key }
{ MIP-MSA-Lifetime } { MIP-MSA-Lifetime }
[ MIP-MN-HA-SPI ] [ MIP-MN-HA-SPI ]
[ MIP-Algorithm-Type ] [ MIP-Algorithm-Type ]
[ MIP-Replay-Mode ] [ MIP-Replay-Mode ]
* [ AVP ] * [ AVP ]
The MIP-MN-HA-SPI sub-AVP within the MIP-MN-HA-MSA grouped AVP The MIP-MN-HA-SPI sub-AVP within the MIP-MN-HA-MSA grouped AVP
identifies the security association required for the validation of identifies the security association required for the validation of
the Mobile IPv6 MN-HA Authentication Option. The absence of the MIP- the Mobile IPv6 MN-HA Authentication Option. The absence of the MIP-
Replay-Mode AVP MUST be treated as no replay protection was selected. Replay-Mode AVP MUST be treated as no replay protection was selected.
6.13. MIP-Algorithm-Type AVP 6.13. MIP-Algorithm-Type AVP
The MIP-Algorithm-Type AVP (AVP Code 345) is of type Enumerated and The MIP-Algorithm-Type AVP (AVP Code 345) is of type Enumerated and
contains Algorithm identifier for the associated Mobile IPv6 MN-HA contains the Algorithm identifier for the associated Mobile IPv6
Authentication Option. The Diameter server selects the algorithm MN-HA Authentication Option. The Diameter server selects the
type. Existing algorithm types are defined in [RFC4004] that also algorithm type. Existing algorithm types are defined in [RFC4004]
fulfill current RFC 4285 requirements. This AVP is re-used from that also fulfill current RFC 4285 requirements. This AVP is reused
[RFC4004]. from [RFC4004].
When the MIP6-Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA, and the When the MIP6-Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA, and the
Diameter server returns a valid MIP-MN-HA-MSA AVP in the MIA message, Diameter server returns a valid MIP-MN-HA-MSA AVP in the MIA message,
this AVP MUST be present inside the MIP-MN-HA-MSA AVP. this AVP MUST be present inside the MIP-MN-HA-MSA AVP.
6.14. MIP-Replay-Mode AVP 6.14. MIP-Replay-Mode AVP
The MIP-Replay-Mode AVP (AVP Code 346) is of type Enumerated and The MIP-Replay-Mode AVP (AVP Code 346) is of type Enumerated and
contains the replay mode the HA for authenticating the mobile node. contains the replay mode of the HA for authenticating the mobile
Out of all possible replay modes defined in [RFC4004], the following node. Out of all possible replay modes defined in [RFC4004], the
are supported by this specification: following are supported by this specification:
1 None 1 None
2 Timestamp 2 Timestamp
This AVP is re-used from [RFC4004]. This AVP is reused from [RFC4004].
6.15. MIP6-Feature-Vector AVP 6.15. MIP6-Feature-Vector AVP
The MIP6-Feature-Vector AVP (AVP Code 124) is defined in [RFC5447]. The MIP6-Feature-Vector AVP (AVP Code 124) is defined in [RFC5447].
However, this specification does not define any Mobile IPv6 split However, this specification does not define any Mobile IPv6 split
scenario bootstrapping specific capability flag. scenario bootstrapping specific capability flag.
6.16. MIP-Timestamp AVP 6.16. MIP-Timestamp AVP
The MIP-Timestamp AVP (AVP Code TBD) is of type OctetString and The MIP-Timestamp AVP (AVP Code 490) is of type OctetString and
contains eight octets timestamp value (i.e. 64 bits timestamp) from contains an 8-octet timestamp value (i.e., 64-bit timestamp) from the
the Mobility message replay protection option, defined in [RFC4285]. Mobility message replay protection option, defined in [RFC4285]. The
The HA extracts this value from the received BU message, if HA extracts this value from the received BU message, if available.
available. The HA includes this AVP in the MIR message when the MN- The HA includes this AVP in the MIR message when the MN-AAA Mobility
AAA Mobility Message Authentication Option is available in the Message Authentication Option is available in the received BU and the
received BU and the Diameter server is expected to return the key Diameter server is expected to return the key material required for
material required for the calculation and validation of the Mobile the calculation and validation of the Mobile IPv6 MN-HA
IPv6 MN-HA Authentication Option (and the MIP6-Auth-Mode AVP is set Authentication Option (and the MIP6-Auth-Mode AVP is set to value
to value MIP6_AUTH_MN_AAA). MIP6_AUTH_MN_AAA).
6.17. QoS-Capability AVP 6.17. QoS-Capability AVP
The QoS-Capability AVP is defined in [I-D.ietf-dime-qos-attributes] The QoS-Capability AVP is defined in [RFC5777] and contains a list of
and contains a list of supported Quality of Service profiles. supported Quality of Service profiles.
6.18. QoS-Resources AVP 6.18. QoS-Resources AVP
The QoS-Resources AVP is defined in [I-D.ietf-dime-qos-attributes] The QoS-Resources AVP is defined in [RFC5777] and provides QoS and
and provides QoS and packet filtering capabilities. packet filtering capabilities.
6.19. Chargeable-User-Identity AVP 6.19. Chargeable-User-Identity AVP
The Chargeable-User-Identity AVP (AVP code 89) is of type OctetString The Chargeable-User-Identity AVP (AVP Code 89) is of type OctetString
and contains an unique temporary handle of the user. The Chargeable- and contains a unique temporary handle of the user. The Chargeable-
User-Identity is defined in [RFC4372]. User-Identity is defined in [RFC4372].
6.20. MIP6-Auth-Mode AVP 6.20. MIP6-Auth-Mode AVP
The MIP6-Auth-Mode (AVP Code TBD) is of type Enumerated and contains The MIP6-Auth-Mode (AVP Code 494) is of type Enumerated and contains
information of the used Mobile IPv6 Authentication Protocol mode. information of the used Mobile IPv6 Authentication Protocol mode.
This specification defines only one value MIP6_AUTH_MN_AAA and the This specification defines only one value MIP6_AUTH_MN_AAA and the
corresponding AAA interactions when MN-AAA security association is corresponding AAA interactions when MN-AAA security association is
used to authenticate the Binding Update as described in [RFC4285]. used to authenticate the Binding Update as described in [RFC4285].
When the MIP6-Auth_Mode AVP is set to the value of MIP6_AUTH_MN_AAA, When the MIP6-Auth_Mode AVP is set to the value of MIP6_AUTH_MN_AAA,
the Auth-Request-Type AVP MUST be set to the value of the Auth-Request-Type AVP MUST be set to the value of
AUTHORIZE_AUTHENTICATE. AUTHORIZE_AUTHENTICATE.
If the Diameter server does not support the Mobile IPv6 If the Diameter server does not support the Mobile IPv6
Authentication Protocol usage mode proposed by the HA, then the Authentication Protocol usage mode proposed by the HA, then the
skipping to change at page 30, line 19 skipping to change at page 26, line 22
Diameter Mobile IPv6 applications, either MIP6I or MIP6A, are used in Diameter Mobile IPv6 applications, either MIP6I or MIP6A, are used in
the case of the coupled account model. Diameter Mobile IPv4 the case of the coupled account model. Diameter Mobile IPv4
application [RFC4004] accounting AVPs are reused in this document. application [RFC4004] accounting AVPs are reused in this document.
The following AVPs SHOULD be included in the accounting request The following AVPs SHOULD be included in the accounting request
message: message:
o Accounting-Input-Octets: Number of octets in IP packets received o Accounting-Input-Octets: Number of octets in IP packets received
from the mobile node. from the mobile node.
o Accounting-Output-Octets: Number of octets in IP packets sent by o Accounting-Output-Octets: Number of octets in IP packets sent by
the mobile node the mobile node.
o Accounting-Input-Packets: Number of IP packets received from the o Accounting-Input-Packets: Number of IP packets received from the
mobile node. mobile node.
o Accounting-Output-Packets: Number of IP packets sent by the mobile o Accounting-Output-Packets: Number of IP packets sent by the mobile
node. node.
o Acct-Multi-Session-Id: Used to link together multiple related o Acct-Multi-Session-Id: Used to link together multiple related
accounting sessions, where each session would have a unique accounting sessions, where each session would have a unique
Session-Id, but the same Acct-Multi-Session-Id AVP. Session-Id, but the same Acct-Multi-Session-Id AVP.
o Acct-Session-Time: Indicates the length of the current session in o Acct-Session-Time: Indicates the length of the current session in
seconds. seconds.
o MIP6-Feature-Vector: The supported features for this mobility o MIP6-Feature-Vector: The supported features for this mobility
service session. service session.
o MIP-Mobile-Node-Address: The Home Address of the mobile node. o MIP-Mobile-Node-Address: The home address of the mobile node.
o MIP-Agent-Info: The current home agent of the mobile node. o MIP-Agent-Info: The current home agent of the mobile node.
o Chargeable-User-Identity: The unique temporary identity of the o Chargeable-User-Identity: The unique temporary identity of the
user. This AVP MUST be included if it is available in the home user. This AVP MUST be included if it is available in the home
agent. agent.
o Service-Selection: Currently selected mobility service. o Service-Selection: Currently selected mobility service.
o QoS-Resources: Assigned QoS resources for the mobile node. o QoS-Resources: Assigned Quality-of-Service (QoS) resources for the
mobile node.
o QoS-Capability: The QoS capability related to the assigned QoS- o QoS-Capability: The QoS capability related to the assigned QoS-
Resources. Resources.
o MIP-Careof-Address: The current Care-of Address of the mobile o MIP-Careof-Address: The current care-of address of the mobile
node. node.
7. Result-Code AVP Values 7. Result-Code AVP Values
This section defines new Result-Code [RFC3588] values that MUST be This section defines new Result-Code [RFC3588] values that MUST be
supported by all Diameter implementations that conform to this supported by all Diameter implementations that conform to this
specification. specification.
7.1. Success 7.1. Success
Errors that fall within the Success category are used to inform a Errors that fall within the Success category are used to inform a
peer that a request has been successfully completed. peer that a request has been successfully completed.
DIAMETER_SUCCESS_RELOCATE_HA (Status Code TBD) DIAMETER_SUCCESS_RELOCATE_HA (Status Code 2009)
This result code is used by the Diameter server to inform the HA This result code is used by the Diameter server to inform the HA
that the MN MUST be switched to another HA. that the MN MUST be switched to another HA.
7.2. Permanent Failures 7.2. Permanent Failures
Errors that fall within the permanent failures category are used to Errors that fall within the Permanent Failures category are used to
inform the peer that the request failed and SHOULD NOT be attempted inform the peer that the request failed and SHOULD NOT be attempted
again. again.
DIAMETER_ERROR_MIP6_AUTH_MODE (Status Code TBD) DIAMETER_ERROR_MIP6_AUTH_MODE (Status Code 5041)
This error code is used by the Diameter server to inform the peer This error code is used by the Diameter server to inform the peer
that the requested Mobile IPv6 Authentication Protocol usage mode that the requested Mobile IPv6 Authentication Protocol usage mode
is not supported. is not supported.
8. AVP Occurrence Tables 8. AVP Occurrence Tables
The following tables present the AVPs defined in this document and The following tables present the AVPs defined in this document and
their occurrences in Diameter messages. Note that AVPs that can only their occurrences in Diameter messages. Note that AVPs that can only
be present within a Grouped AVP are not represented in this table. be present within a Grouped AVP are not represented in this table.
The table uses the following symbols: The tables use the following symbols:
0: 0:
The AVP MUST NOT be present in the message. The AVP MUST NOT be present in the message.
0+: 0+:
Zero or more instances of the AVP MAY be present in the message. Zero or more instances of the AVP MAY be present in the message.
0-1: 0-1:
Zero or one instance of the AVP MAY be present in the message. Zero or one instance of the AVP MAY be present in the message.
1: 1:
One instance of the AVP MUST be present in the message. One instance of the AVP MUST be present in the message.
8.1. DER, DEA, MIR and MIA AVP/Command-Code Table 8.1. DER, DEA, MIR, and MIA AVP/Command-Code Table
+-----------------------+ +-----------------------+
| Command-Code | | Command-Code |
|-----+-----+-----+-----+ |-----+-----+-----+-----+
AVP Name | DER | DEA | MIR | MIA | AVP Name | DER | DEA | MIR | MIA |
-------------------------------|-----+-----+-----+-----+ -------------------------------|-----+-----+-----+-----+
MIP6-Feature-Vector | 0-1 | 0-1 | 0-1 | 0-1 | MIP6-Feature-Vector | 0-1 | 0-1 | 0-1 | 0-1 |
MIP-Mobile-Node-Address | 1-2 | 0-2 | 1-2 | 0-2 | MIP-Mobile-Node-Address | 1-2 | 0-2 | 1-2 | 0-2 |
MIP-MN-AAA-SPI | 0 | 0 | 0-1 | 0 | MIP-MN-AAA-SPI | 0 | 0 | 0-1 | 0 |
MIP-MN-HA-SPI | 0 | 0 | 0-1 | 0 | MIP-MN-HA-SPI | 0 | 0 | 0-1 | 0 |
MIP6-Agent-Info | 1 | 0-1 | 1 | 0-1 | MIP6-Agent-Info | 1 | 0-1 | 1 | 0-1 |
skipping to change at page 36, line 13 skipping to change at page 29, line 35
-------------------------------------|------+------+ -------------------------------------|------+------+
9. IANA Considerations 9. IANA Considerations
This section contains the namespaces that have either been created in This section contains the namespaces that have either been created in
this specification or had their values assigned to existing this specification or had their values assigned to existing
namespaces managed by IANA. namespaces managed by IANA.
9.1. Command Codes 9.1. Command Codes
IANA is requested to allocate a command code value for the following IANA has allocated a command code value for the following new command
new commands from the Command Code namespace defined in [RFC3588]. from the Command Code namespace defined in [RFC3588]. See Section 5
See Section 5 for the assignment of the namespace in this for the assignment of the namespace in this specification.
specification.
Command Code | Value Command Code | Value
-----------------------------------+------ -----------------------------------+------
MIP6-Request (MIR) | TBD MIP6-Request/Answer (MIR/MIA) | 325
MIP6-Answer (MIA) | TBD
9.2. AVP Codes 9.2. AVP Codes
This specification requires IANA to register the following new AVPs IANA has registered the following new AVPs from the AVP Code
from the AVP Code namespace defined in [RFC3588]. namespace defined in [RFC3588].
o MIP-Careof-Address o MIP-Careof-Address
o MIP-Authenticator o MIP-Authenticator
o MIP-MAC-Mobility-Data o MIP-MAC-Mobility-Data
o MIP-Timestamp o MIP-Timestamp
o MIP-MN-HA-SPI o MIP-MN-HA-SPI
o MIP-MN-HA-MSA o MIP-MN-HA-MSA
skipping to change at page 36, line 48 skipping to change at page 30, line 22
o MIP-MN-HA-MSA o MIP-MN-HA-MSA
o Service-Selection o Service-Selection
o MIP6-Auth-Mode o MIP6-Auth-Mode
The AVPs are defined in Section 6. The AVPs are defined in Section 6.
9.3. Result-Code AVP Values 9.3. Result-Code AVP Values
This specification requests IANA to allocate new values to the IANA has allocated new values to the Result-Code AVP (AVP Code 268)
Result-Code AVP (AVP Code 268) namespace defined in [RFC3588]. See namespace defined in [RFC3588]. See Section 7 for the assignment of
Section 7 for the assignment of the namespace in this specification. the namespace in this specification.
Result-Code | Value Result-Code | Value
----------------------------------------------+------ ----------------------------------------------+------
DIAMETER_SUCCESS_RELOCATE_HA | TBD DIAMETER_SUCCESS_RELOCATE_HA | 2009
DIAMETER_ERROR_MIP6_AUTH_MODE | TBD DIAMETER_ERROR_MIP6_AUTH_MODE | 5041
9.4. Application Identifier 9.4. Application Identifier
This specification requires IANA to allocate two new values "Diameter IANA has allocated two new values "Diameter Mobile IPv6 IKE" and
Mobile IPv6 IKE" and "Diameter Mobile IPv6 Auth" from the Application "Diameter Mobile IPv6 Auth" from the Application Identifier namespace
Identifier namespace defined in [RFC3588]. defined in [RFC3588].
Application Identifier | Value Application Identifier | Value
-----------------------------------+------ -----------------------------------+------
Diameter Mobile IPv6 IKE (MIP6I) | TBD Diameter Mobile IPv6 IKE (MIP6I) | 7
Diameter Mobile IPv6 Auth (MIP6A) | TBD Diameter Mobile IPv6 Auth (MIP6A) | 8
9.5. Namespaces 9.5. Namespaces
IANA is requested to create a new registry "MIP6 Authentication Mode" IANA has created a new registry, "MIP6 Authentication Mode Registry",
registry for use with the enumerated MIP6-Auth-Mode AVP. The for use with the enumerated MIP6-Auth-Mode AVP. The registry
registry will initially contain the following value: initially contains the following value:
Token | Value | Description Token | Value | Description
---------------------------------------------+----------+------------ ---------------------------------------------+----------+------------
MIP6_AUTH_MN_AAA | 1 | RFC TBD MIP6_AUTH_MN_AAA | 1 | RFC 5778
Allocation of new values follow the example policies described in Allocation of new values follow the example policies described in
[RFC5226] new values for the MIP6-Auth-Mode AVP will be assigned [RFC5226]. New values for the MIP6-Auth-Mode AVP will be assigned
based on the "Specification Required" policy. The value 0 (zero) is based on the "Specification Required" policy. The value 0 (zero) is
reserved and the maximum value is 4294967295 (i.e. 2^32-1). reserved, and the maximum value is 4294967295 (i.e., 2^32-1).
10. Security Considerations 10. Security Considerations
The security considerations for the Diameter interaction required to The security considerations for the Diameter interaction required to
accomplish the split scenario are described in [RFC5026]. accomplish the split scenario are described in [RFC5026].
Additionally, the security considerations of the Diameter Base Additionally, the security considerations of the Diameter base
protocol [RFC3588], Diameter EAP application [RFC4072] are applicable protocol [RFC3588], and Diameter EAP application [RFC4072] are
to this document. applicable to this document.
The Diameter messages may be transported between the HA and the The Diameter messages may be transported between the HA and the
Diameter server via one or more AAA brokers or Diameter agents. In 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 this case, the HA to the Diameter server AAA communication relies on
security properties of the intermediating AAA inter-connection the security properties of the intermediating AAA inter-connection
networks, AAA brokers and Diameter agents (such as proxies). networks, AAA brokers, and Diameter agents (such as proxies).
In case of the Authentication Protocol for Mobile IPv6 [RFC4285], In the case of the Authentication Protocol for Mobile IPv6 [RFC4285],
this specification expects that the Diameter server derives the MN-HA this specification expects that the Diameter server derives the MN-HA
Security Association and returns the associated session key (i.e. the Security Association and returns the associated session key (i.e.,
MN-HA shared session key) to the HA. However, this specification the MN-HA shared session key) to the HA. However, this specification
does not define nor other IETF specification defines how the Diameter does not define nor do other IETF specifications define how the
server actually derives required keys. The details of the key Diameter server actually derives required keys. The details of the
derivation depends on the deployment where this specification is used key derivation depends on the deployment where this specification is
and therefore the security properties of the system depend on how used and therefore the security properties of the system depend on
this is done. how this is done.
11. Acknowledgements 11. Acknowledgements
The authors would like to thank Jari Arkko, Tolga Asversen, Pasi The authors would like to thank Jari Arkko, Tolga Asversen, Pasi
Eronen, Santiago Zapata Hernandez, Anders Kristensen, Avi Lior, John Eronen, Santiago Zapata Hernandez, Anders Kristensen, Avi Lior, John
Loughney, Ahmad Muhanna, Behcet Sarikaya, Basavaraj Patil, Vijay Loughney, Ahmad Muhanna, Behcet Sarikaya, Basavaraj Patil, Vijay
Devarapalli, Lionel Morand, Domagoj Premec, Semyon Mizikovsky and Devarapalli, Lionel Morand, Domagoj Premec, Semyon Mizikovsky, and
Yoshihiro Ohba for all the useful discussions. Ahmad Muhanna Yoshihiro Ohba for all the useful discussions. Ahmad Muhanna
provided a detailed review of the document in August 2007. Pasi provided a detailed review of the document in August 2007. Pasi
Eronen provided detailed comments and text proposals during the IESG Eronen provided detailed comments and text proposals during the IESG
review that helped to improved this document greatly. review that helped to improved this document greatly.
We would also like to thank our Area Director, Dan Romascanu, for his We would also like to thank our Area Director, Dan Romascanu, for his
support. support.
Hannes Tschofenig would like to thank the European Commission support Hannes Tschofenig would like to thank the European Commission support
in the co-funding of the ENABLE project, where this work is partly in the co-funding of the ENABLE project, where this work is partly
being developed. being developed.
Julien Bournelle would like to thank GET/INT since he began this work Julien Bournelle would like to thank GET/INT since he began this work
while he was under their employ. while he was under their employ.
Madjid Nakhjiri would like to thank Huawei USA as most of his Madjid Nakhjiri would like to thank Huawei USA as most of his
contributions to this draft were possible while he was under their contributions to this document were possible while he was under their
employ. employ.
12. References 12. References
12.1. Normative References 12.1. Normative References
[I-D.ietf-dime-qos-attributes] [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones, M., Requirement Levels", BCP 14, RFC 2119, March 1997.
and A. Lior, "Quality of Service Attributes for Diameter",
draft-ietf-dime-qos-attributes-11 (work in progress),
February 2009.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Requirement Levels", BCP 14, RFC 2119, March 1997. Arkko, "Diameter Base Protocol", RFC 3588,
September 2003.
[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. [RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
Arkko, "Diameter Base Protocol", RFC 3588, September 2003. in IPv6", RFC 3775, June 2004.
[RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support [RFC4004] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and
in IPv6", RFC 3775, June 2004. P. McCann, "Diameter Mobile IPv4 Application", RFC 4004,
August 2005.
[RFC4004] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and [RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton,
P. McCann, "Diameter Mobile IPv4 Application", RFC 4004, "Diameter Network Access Server Application", RFC 4005,
August 2005. August 2005.
[RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, [RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
"Diameter Network Access Server Application", RFC 4005, Authentication Protocol (EAP) Application", RFC 4072,
August 2005. August 2005.
[RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible [RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K.
Authentication Protocol (EAP) Application", RFC 4072, Chowdhury, "Mobile Node Identifier Option for Mobile IPv6
August 2005. (MIPv6)", RFC 4283, November 2005.
[RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. [RFC4285] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K.
Chowdhury, "Mobile Node Identifier Option for Mobile IPv6 Chowdhury, "Authentication Protocol for Mobile IPv6",
(MIPv6)", RFC 4283, November 2005. RFC 4285, January 2006.
[RFC4285] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. [RFC4306] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol",
Chowdhury, "Authentication Protocol for Mobile IPv6", RFC 4306, December 2005.
RFC 4285, January 2006.
[RFC4306] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol", [RFC4372] Adrangi, F., Lior, A., Korhonen, J., and J. Loughney,
RFC 4306, December 2005. "Chargeable User Identity", RFC 4372, January 2006.
[RFC4372] Adrangi, F., Lior, A., Korhonen, J., and J. Loughney, [RFC4877] Devarapalli, V. and F. Dupont, "Mobile IPv6 Operation
"Chargeable User Identity", RFC 4372, January 2006. with IKEv2 and the Revised IPsec Architecture", RFC 4877,
April 2007.
[RFC4877] Devarapalli, V. and F. Dupont, "Mobile IPv6 Operation with [RFC5026] Giaretta, G., Kempf, J., and V. Devarapalli, "Mobile IPv6
IKEv2 and the Revised IPsec Architecture", RFC 4877, Bootstrapping in Split Scenario", RFC 5026, October 2007.
April 2007.
[RFC5026] Giaretta, G., Kempf, J., and V. Devarapalli, "Mobile IPv6 [RFC5142] Haley, B., Devarapalli, V., Deng, H., and J. Kempf,
Bootstrapping in Split Scenario", RFC 5026, October 2007. "Mobility Header Home Agent Switch Message", RFC 5142,
January 2008.
[RFC5142] Haley, B., Devarapalli, V., Deng, H., and J. Kempf, [RFC5149] Korhonen, J., Nilsson, U., and V. Devarapalli, "Service
"Mobility Header Home Agent Switch Message", RFC 5142, Selection for Mobile IPv6", RFC 5149, February 2008.
January 2008.
[RFC5149] Korhonen, J., Nilsson, U., and V. Devarapalli, "Service [RFC5447] Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C.,
Selection for Mobile IPv6", RFC 5149, February 2008. and K. Chowdhury, "Diameter Mobile IPv6: Support for
Network Access Server to Diameter Server Interaction",
RFC 5447, February 2009.
[RFC5447] Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C., [RFC5777] Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones,
and K. Chowdhury, "Diameter Mobile IPv6: Support for M., Ed., and A. Lior, "Traffic Classification and Quality
Network Access Server to Diameter Server Interaction", of Service (QoS) Attributes for Diameter", RFC 5777,
RFC 5447, February 2009. February 2010.
12.2. Informative References 12.2. Informative References
[I-D.ietf-dime-app-design-guide] [DIME-APP] Fajardo, V., Asveren, T., Tschofenig, H., McGregor, G.,
Fajardo, V., Asveren, T., Tschofenig, H., McGregor, G., and J. Loughney, "Diameter Applications Design
and J. Loughney, "Diameter Applications Design Guidelines", Work in Progress, July 2009.
Guidelines", draft-ietf-dime-app-design-guide-08 (work in
progress), November 2008.
[I-D.ietf-mext-aaa-ha-goals] [RFC4640] Patel, A. and G. Giaretta, "Problem Statement for
Giaretta, G., Guardini, I., Demaria, E., Bournelle, J., bootstrapping Mobile IPv6 (MIPv6)", RFC 4640,
and R. Lopez, "AAA Goals for Mobile IPv6", September 2006.
draft-ietf-mext-aaa-ha-goals-01 (work in progress),
May 2008.
[I-D.ietf-mext-nemo-v4traversal] [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and IANA Considerations Section in RFCs", BCP 26, RFC 5226,
Routers", draft-ietf-mext-nemo-v4traversal-10 (work in May 2008.
progress), April 2009.
[RFC4640] Patel, A. and G. Giaretta, "Problem Statement for [RFC5555] Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts
bootstrapping Mobile IPv6 (MIPv6)", RFC 4640, and Routers", RFC 5555, June 2009.
September 2006.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5637] Giaretta, G., Guardini, I., Demaria, E., Bournelle, J.,
IANA Considerations Section in RFCs", BCP 26, RFC 5226, and R. Lopez, "Authentication, Authorization, and
May 2008. Accounting (AAA) Goals for Mobile IPv6", RFC 5637,
September 2009.
Authors' Addresses Authors' Addresses
Jouni Korhonen (editor) Jouni Korhonen (editor)
Nokia Siemens Networks Nokia Siemens Networks
Linnoitustie 6 Linnoitustie 6
Espoo FIN-02600 Espoo FIN-02600
Finland Finland
Email: jouni.nospam@gmail.com EMail: jouni.nospam@gmail.com
Hannes Tschofenig Hannes Tschofenig
Nokia Siemens Networks Nokia Siemens Networks
Linnoitustie 6 Linnoitustie 6
Espoo FIN-02600 Espoo FIN-02600
Finland Finland
Phone: +358 (50) 4871445 Phone: +358 (50) 4871445
Email: Hannes.Tschofenig@gmx.net EMail: Hannes.Tschofenig@gmx.net
URI: http://www.tschofenig.priv.at URI: http://www.tschofenig.priv.at
Julien Bournelle Julien Bournelle
Orange Labs Orange Labs
38-4O rue du general Leclerc 38-4O rue du general Leclerc
Issy-Les-Moulineaux 92794 Issy-Les-Moulineaux 92794
France France
Email: julien.bournelle@orange-ftgroup.com EMail: julien.bournelle@orange-ftgroup.com
Gerardo Giaretta Gerardo Giaretta
Qualcomm Qualcomm
5775 MoreHouse Dr 5775 Morehouse Dr
San Diego, CA 92121 San Diego, CA 92121
USA USA
Email: gerardo.giaretta@gmail.com EMail: gerardo.giaretta@gmail.com
Madjid Nakhjiri Madjid Nakhjiri
Motorola Motorola
USA USA
Email: madjid.nakhjiri@motorola.com EMail: madjid.nakhjiri@motorola.com
 End of changes. 154 change blocks. 
490 lines changed or deleted 478 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/