draft-ietf-dime-mip6-split-13.txt   draft-ietf-dime-mip6-split-14.txt 
Diameter Maintenance and J. Korhonen Diameter Maintenance and J. Korhonen, Ed.
Extensions (DIME) TeliaSonera Extensions (DIME) H. Tschofenig
Internet-Draft H. Tschofenig Internet-Draft Nokia Siemens Networks
Intended status: Standards Track Nokia Siemens Networks Intended status: Standards Track J. Bournelle
Expires: April 30, 2009 J. Bournelle Expires: June 25, 2009 Orange Labs
Orange Labs
G. Giaretta G. Giaretta
Qualcomm Qualcomm
M. Nakhjiri M. Nakhjiri
Motorola Motorola
October 27, 2008 December 22, 2008
Diameter Mobile IPv6: Support for Home Agent to Diameter Server Diameter Mobile IPv6: Support for Home Agent to Diameter Server
Interaction Interaction
draft-ietf-dime-mip6-split-13.txt draft-ietf-dime-mip6-split-14.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 30, 2009. This Internet-Draft will expire on June 25, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (c) 2008 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
Abstract Abstract
Mobile IPv6 deployments may want to bootstrap their operations Mobile IPv6 deployments may want to bootstrap their operations
dynamically based on an interaction between the Home Agent and the dynamically based on an interaction between the Home Agent and the
Diameter server of the Mobile Service Provider (MSP). This document Diameter server of the Mobile Service Provider. This document
specifies the interaction between a Mobile IP Home Agent and that specifies the interaction between a Mobile IP Home Agent and that
Diameter server. Diameter server.
Several different mechanisms for authenticating a Mobile Node are Several different mechanisms for authenticating a Mobile Node are
supported. The usage of the Internet Key Exchange v2 (IKEv2) supported. The usage of the Internet Key Exchange v2 protocol allows
protocol allows different mechanisms, such as the Extensible different mechanisms, such as the Extensible Authentication Protocol,
Authentication Protocol (EAP), certificates and pre-shared secrets to certificates and pre-shared secrets to be used. Furthermore, another
be used. Furthermore, another method makes use of the Mobile IPv6 method makes use of the Mobile IPv6 Authentication Protocol. In
Authentication Protocol. In addition to authentication and addition to authentication and authorization, the configuration of
authorization, the configuration of Mobile IPv6 specific parameters Mobile IPv6 specific parameters and accounting is specified in this
and accounting is specified in this document. document.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 6
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 9
3. Application Identifiers . . . . . . . . . . . . . . . . . . . 7 3. Application Identifiers . . . . . . . . . . . . . . . . . . . 10
4. Protocol Description . . . . . . . . . . . . . . . . . . . . . 8 4. Protocol Description . . . . . . . . . . . . . . . . . . . . . 11
4.1. Support for Mobile IPv6 with IKEv2 and EAP . . . . . . . . 8 4.1. Support for Mobile IPv6 with IKEv2 and EAP . . . . . . . . 11
4.2. Support for the Mobile IPv6 Authentication Protocol . . . 11 4.2. Support for the Mobile IPv6 Authentication Protocol . . . 14
4.3. Mobile IPv6 Session Management . . . . . . . . . . . . . . 12 4.3. Mobile IPv6 Session Management . . . . . . . . . . . . . . 15
4.3.1. Session-Termination-Request . . . . . . . . . . . . . 12 4.3.1. Session-Termination-Request . . . . . . . . . . . . . 15
4.3.2. Session-Termination-Answer . . . . . . . . . . . . . . 12 4.3.2. Session-Termination-Answer . . . . . . . . . . . . . . 15
4.3.3. Abort-Session-Request . . . . . . . . . . . . . . . . 12 4.3.3. Abort-Session-Request . . . . . . . . . . . . . . . . 16
4.3.4. Abort-Session-Answer . . . . . . . . . . . . . . . . . 13 4.3.4. Abort-Session-Answer . . . . . . . . . . . . . . . . . 16
4.4. Accounting for Mobile IPv6 services . . . . . . . . . . . 13 4.4. Accounting for Mobile IPv6 services . . . . . . . . . . . 16
4.4.1. Accounting-Request . . . . . . . . . . . . . . . . . . 13 4.4.1. Accounting-Request . . . . . . . . . . . . . . . . . . 17
4.4.2. Accounting-Answer . . . . . . . . . . . . . . . . . . 14 4.4.2. Accounting-Answer . . . . . . . . . . . . . . . . . . 17
5. Command Codes . . . . . . . . . . . . . . . . . . . . . . . . 14 5. Command Codes . . . . . . . . . . . . . . . . . . . . . . . . 18
5.1. Command Code for Mobile IPv6 with IKEv2 and EAP . . . . . 14 5.1. Command Code for Mobile IPv6 with IKEv2 and EAP . . . . . 18
5.1.1. Diameter-EAP-Request . . . . . . . . . . . . . . . . . 14 5.1.1. Diameter-EAP-Request . . . . . . . . . . . . . . . . . 18
5.1.2. Diameter-EAP-Answer . . . . . . . . . . . . . . . . . 15 5.1.2. Diameter-EAP-Answer . . . . . . . . . . . . . . . . . 19
5.2. Command Codes for Mobile IPv6 Authentication Protocol 5.2. Command Codes for Mobile IPv6 Authentication Protocol
Support . . . . . . . . . . . . . . . . . . . . . . . . . 16 Support . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.2.1. MIP6-Request . . . . . . . . . . . . . . . . . . . . . 17 5.2.1. MIP6-Request . . . . . . . . . . . . . . . . . . . . . 21
5.2.2. MIP6-Answer . . . . . . . . . . . . . . . . . . . . . 18 5.2.2. MIP6-Answer . . . . . . . . . . . . . . . . . . . . . 22
6. AVPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 6. AVPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1. User-Name AVP . . . . . . . . . . . . . . . . . . . . . . 21 6.1. User-Name AVP . . . . . . . . . . . . . . . . . . . . . . 26
6.2. Service-Selection AVP . . . . . . . . . . . . . . . . . . 21 6.2. Service-Selection AVP . . . . . . . . . . . . . . . . . . 26
6.3. MIP-MN-AAA-SPI AVP . . . . . . . . . . . . . . . . . . . . 22 6.3. MIP-MN-AAA-SPI AVP . . . . . . . . . . . . . . . . . . . . 27
6.4. MIP-MN-HA-SPI AVP . . . . . . . . . . . . . . . . . . . . 22 6.4. MIP-MN-HA-SPI AVP . . . . . . . . . . . . . . . . . . . . 27
6.5. MIP-Mobile-Node-Address AVP . . . . . . . . . . . . . . . 22 6.5. MIP-Mobile-Node-Address AVP . . . . . . . . . . . . . . . 27
6.6. MIP6-Agent-Info AVP . . . . . . . . . . . . . . . . . . . 22 6.6. MIP6-Agent-Info AVP . . . . . . . . . . . . . . . . . . . 28
6.7. MIP-Careof-Address AVP . . . . . . . . . . . . . . . . . . 23 6.7. MIP-Careof-Address AVP . . . . . . . . . . . . . . . . . . 28
6.8. MIP-Authenticator AVP . . . . . . . . . . . . . . . . . . 23 6.8. MIP-Authenticator AVP . . . . . . . . . . . . . . . . . . 28
6.9. MIP-MAC-Mobility-Data AVP . . . . . . . . . . . . . . . . 23 6.9. MIP-MAC-Mobility-Data AVP . . . . . . . . . . . . . . . . 28
6.10. MIP-Session-Key AVP . . . . . . . . . . . . . . . . . . . 23 6.10. MIP-Session-Key AVP . . . . . . . . . . . . . . . . . . . 29
6.11. MIP-MSA-Lifetime AVP . . . . . . . . . . . . . . . . . . . 23 6.11. MIP-MSA-Lifetime AVP . . . . . . . . . . . . . . . . . . . 29
6.12. MIP-MN-HA-MSA AVP . . . . . . . . . . . . . . . . . . . . 24 6.12. MIP-MN-HA-MSA AVP . . . . . . . . . . . . . . . . . . . . 29
6.13. MIP-Algorithm-Type AVP . . . . . . . . . . . . . . . . . . 24 6.13. MIP-Algorithm-Type AVP . . . . . . . . . . . . . . . . . . 29
6.14. MIP-Replay-Mode AVP . . . . . . . . . . . . . . . . . . . 24 6.14. MIP-Replay-Mode AVP . . . . . . . . . . . . . . . . . . . 30
6.15. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . . . 24 6.15. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . . . 30
6.16. MIP-Timestamp AVP . . . . . . . . . . . . . . . . . . . . 25 6.16. MIP-Timestamp AVP . . . . . . . . . . . . . . . . . . . . 30
6.17. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 25 6.17. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 30
6.18. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 25 6.18. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 30
6.19. Chargeable-User-Identity AVP . . . . . . . . . . . . . . . 25 6.19. Chargeable-User-Identity AVP . . . . . . . . . . . . . . . 31
6.20. MIP6-Auth-Mode AVP . . . . . . . . . . . . . . . . . . . . 25 6.20. MIP6-Auth-Mode AVP . . . . . . . . . . . . . . . . . . . . 31
6.21. Coupled Accounting Model Accounting AVPs . . . . . . . . . 26 6.21. Accounting AVPs . . . . . . . . . . . . . . . . . . . . . 31
7. Result-Code AVP Values . . . . . . . . . . . . . . . . . . . . 26 7. Result-Code AVP Values . . . . . . . . . . . . . . . . . . . . 33
7.1. Success . . . . . . . . . . . . . . . . . . . . . . . . . 27 7.1. Success . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.2. Permanent Failures . . . . . . . . . . . . . . . . . . . . 27 7.2. Permanent Failures . . . . . . . . . . . . . . . . . . . . 33
8. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 27 8. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 34
8.1. DER, DEA, MIR and MIA AVP/Command-Code Table . . . . . . . 28 8.1. DER, DEA, MIR and MIA AVP/Command-Code Table . . . . . . . 34
8.2. Coupled Accounting Model AVP Table . . . . . . . . . . . . 28 8.2. Coupled Accounting Model AVP Table . . . . . . . . . . . . 35
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37
9.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 29 9.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 37
9.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . 29 9.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . 37
9.3. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 30 9.3. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 37
9.4. Application Identifier . . . . . . . . . . . . . . . . . . 30 9.4. Application Identifier . . . . . . . . . . . . . . . . . . 38
9.5. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 30 9.5. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 38
10. Security Considerations . . . . . . . . . . . . . . . . . . . 31 10. Security Considerations . . . . . . . . . . . . . . . . . . . 39
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 31 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 40
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 41
12.1. Normative References . . . . . . . . . . . . . . . . . . . 32 12.1. Normative References . . . . . . . . . . . . . . . . . . . 41
12.2. Informative References . . . . . . . . . . . . . . . . . . 33 12.2. Informative References . . . . . . . . . . . . . . . . . . 42
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 43
Intellectual Property and Copyright Statements . . . . . . . . . . 35
1. Introduction 1. Introduction
Performing the Mobile IPv6 protocol [1], requires the Mobile Node Performing the Mobile IPv6 protocol [RFC3775], requires the Mobile
(MN) to own a Home Address (HoA) and to have an assigned Home Agent Node (MN) to own a Home Address (HoA) and to have an assigned Home
(HA) to the MN. The MN needs to register with the HA in order to Agent (HA) to the MN. The MN needs to register with the HA in order
enable its reachability and mobility, when away from its home link. to enable its reachability and mobility, when away from its home
The registration process itself may require an establishment of IPsec link. The registration process itself may require an establishment
security associations (SA) and cryptographic material between the MN of IPsec security associations (SA) and cryptographic material
and HA. Alternatively, the registration process may be secured using between the MN and the HA. Alternatively, the registration process
a mobility message authentication option, which enables IPv6 mobility may be secured using a mobility message authentication option, which
in a MN without having to establish an IPsec SA with its HA. enables IPv6 mobility in a MN without having to establish an IPsec SA
Providing the collection of home address, HA address and keying with its HA. Providing the collection of home address, HA address
material is generally referred to as the Mobile IPv6 bootstrapping and keying material is generally referred to as the Mobile IPv6
problem [15]. The purpose of this specification is to provide bootstrapping problem [RFC4640]. The purpose of this specification
Diameter support for the interaction between the HA and the is to provide Diameter support for the interaction between the HA and
Authentication, Authorization, and Accounting (AAA) server. This the Authentication, Authorization, and Accounting (AAA) server. This
specification satisfies the requirements defined in [16] for the specification satisfies the requirements defined in
bootstrapping problem in the split scenario [2] and also specifies [I-D.ietf-mext-aaa-ha-goals] for the bootstrapping problem in the
Diameter support for the Authentication Protocol for Mobile IPv6 [3]. split scenario [RFC5026] and also specifies Diameter support for the
The Diameter support defined in this specification also applies to Authentication Protocol for Mobile IPv6 [RFC4285]. The Diameter
Dual Stack Mobile IPv6 [17]. support defined in this specification also applies to Dual Stack
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, the MSP allows 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 registrations, the HA participates in the authentication of the MN to
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: Asserting or helping with assertion of the Authentication: Verifying the MN's identity. As a Diameter client
correctness of the MN identity. As a Diameter client supporting supporting the new Diameter Mobile IPv6 application, the HA may
the new Diameter Mobile IPv6 application, the HA may need to need to support more than one authentication type depending on the
support more than one authentication type depending on the
environment. Although the authentication is performed by the AAA environment. Although the authentication is performed by the AAA
server there is an impact for the HA as different set of command server there is an impact for the HA as different set of command
codes are needed for the respective authentication procedures. 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 of the HA to provide accounting report 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 to support 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 AAA to abort 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 |
+--------+ +--------+
^ ^
skipping to change at page 6, line 37 skipping to change at page 7, 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 Authentication using two different mechanisms, namely using IPsec or the
Protocol for Mobile IPv6 [3]. For these two approaches several Authentication Protocol for Mobile IPv6 [RFC4285]. For these two
different authentication and key exchange solutions are available. approaches several different authentication and key exchange
When IPsec is used to protect Mobile IPv6 signaling messages, IKEv2 solutions are available. When IPsec is used to protect Mobile IPv6
is used [4]. IKEv2 supports EAP-based initiator authentication, signaling messages, Internet Key Exchange v2 (IKEv2) is used
certificates and pre-shared secrets. Alternatively, Authentication [RFC4877] for the setup of the IPsec SAs. IKEv2 supports Extensible
Protocol for Mobile IPv6 uses a mechanism that is very similar to the Authentication Protocol (EAP) based initiator authentication,
one used for protecting Mobile IPv4 signaling messages. certificates and pre-shared secrets. Alternatively, the
Authentication Protocol for Mobile IPv6 uses a mechanism that is very
similar to the one used for protecting Mobile IPv4 signaling
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
RFC 3588 [5]. RFC 3588 [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 RFC 2119 [6]. document are to be interpreted as described in RFC 2119 [RFC2119].
The Mobile IPv6 bootstrapping terminology is taken from [15]. 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 [5] with required EAP support [7]. AAA protocol based on Diameter [RFC3588] with required EAP support
[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. 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) TBD by IANA
Diameter Mobile IPv6 Auth (MIP6A) TBD by IANA Diameter Mobile IPv6 Auth (MIP6A) TBD by IANA
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 Mobile IPv6 when the MN is authenticated and authorized using the Mobile IPv6
Authentication Protocol. Authentication Protocol.
Mobile IPv6 related accounting generated by the HA uses either MIP6I Mobile IPv6 related accounting information generated by the HA uses
or MIP6A Application Identifier in the case of coupled accounting either the MIP6I or the MIP6A Application Identifier in the case of
model. Diameter Base Accounting Application Identifier (value of 3) coupled accounting model. The Diameter Base Accounting Application
is used in the case of split accounting model. Refer Section 4.4 for Identifier (value of 3) is used in case of the split accounting
more information regarding the accounting models. model. Refer to Section 4.4 for more information 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 [7], are re-used. application logic and procedures, as defined in [RFC4072], are re-
EAP methods that do not establish a shared key SHOULD NOT be used, as used. EAP methods that do not establish a shared key SHOULD NOT be
they are subject to a number of man-in-the-middle attacks as stated used, as they are subject to a number of man-in-the-middle attacks as
in Section 2.16 and Section 5 of RFC 4306 [8]. AVPs specific to stated in Section 2.16 and Section 5 of RFC 4306 [RFC4306]. AVPs
Mobile IPv6 bootstrapping are added to the EAP application commands. specific to Mobile IPv6 bootstrapping are added to the EAP
application commands.
Figure 3 shows the message flow involved during the authentication Figure 2 shows the message flow involved during the authentication
phase when EAP is used. phase when EAP is used.
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 9, line 50 skipping to change at page 12, 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 3: 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, nonces and
Diffie-Hellman parameters are exchanged. Message (3) starts the 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 [8]). 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 [4], using a CFG_REQUEST Address, a Home Prefix or suggests one, see [RFC4877], using a
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 setup IPsec SAs for Mobile IPv6 signaling.
In some deployment scenarios, the HA may also acts as a IKEv2 In some deployment scenarios, the HA may also acts as a IKEv2
Responder for IPsec VPN access. A problem in this case is that the Responder for IPsec VPN access. A challenge in this case is that the
IKEv2 responder may not know if IKEv2 is used for Mobile IPv6 service IKEv2 responder may not know if IKEv2 is used for Mobile IPv6 service
or for IPsec VPN access service. A network operator needs to be or for IPsec VPN access service. A network operator needs to be
aware of this limitation. The MN may provide a hint of the intended aware of this limitation. The MN may provide a hint of the intended
service, for example, by using different identities in the IKE_AUTH service, for example, by using different identities in the IKE_AUTH
message for the IPsec VPN service and Mobile IPv6 service. However, message for the IPsec VPN service and Mobile IPv6 service. However,
the use of different identities during the IKEv2 negotiation is the use of different identities during the IKEv2 negotiation is
deployment specific. Another possibility is to make the distinction deployment specific. Another possibility is to make the distinction
on the MN subscription basis. In this case the Diameter server can on the MN subscription basis. In this case the Diameter server can
inform the HA during the IKEv2 negotiation whether the MN is inform the HA during the IKEv2 negotiation whether the MN is
provisioned with an IPsec VPN access service or Mobile IPv6 service. provisioned with an IPsec VPN access service or Mobile IPv6 service.
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 4 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 [3] the MN uses the Mobile Node Identifier Option, According to [RFC4285] the MN uses the Mobile Node Identifier Option,
specifically the MN-NAI mobility option (as defined in [18]) to specifically the MN-NAI mobility option (as defined in [RFC4283]) to
identify itself. The HA MUST copy the MN-NAI mobility option value identify itself. The HA MUST copy the MN-NAI mobility option value
to the User-Name AVP in the subsequent request messages. 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.
In some architectures and network deployments the MN-HA security In some architectures and network deployments the MN-HA security
associations may be established as a result of a successful network associations may be established as a result of a successful network
access authentication. In such deployments, both MN and Diameter access authentication. In such deployments, both the MN and the
server share the keying material required for computation and Diameter server share the keying material required for computation
validation of the MN-HA Authentication Option, and a Security and validation of the MN-HA Authentication Option, and a Security
Parameter Index (SPI) for indexing an appropriate security Parameter Index (SPI) for indexing an appropriate security
association. Upon receiving a BU with a MN-HA Authentication Option, association. Upon receiving a BU with a MN-HA Authentication Option,
the HA retrieves the keying material required for the computation and the HA retrieves the keying material required for the computation and
validation of the MN-HA Authentication Option from the Diameter validation of the MN-HA Authentication Option from the Diameter
server. The Diameter request message sent by the HA must contain server. The Diameter request message sent by the HA must contain
enough information (such as SPI, MN-NAI, etc) so that the Diameter enough information (such as SPI, MN-NAI, etc) so that the Diameter
server is able to locate the matching MN-HA security association and server is able to locate the matching MN-HA security association and
return correct keying material back to the HA. return correct keying material back to the HA.
This specification assumes that in the case Mobile IPv6 This specification assumes that in the case Mobile IPv6
skipping to change at page 12, line 22 skipping to change at page 15, 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 4: 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 [5]. MUST support the Authorization Session State Machine defined in
Moreover, the following four commands may be exchanged between the HA [RFC3588].
and the Diameter server.
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
Mobile IPv6 Authentication Protocol exchange correspond to one
Diameter session.
4.3.1. Session-Termination-Request 4.3.1. Session-Termination-Request
The Session-Termination-Request (STR) message [5] is sent by the HA The Session-Termination-Request (STR) message [RFC3588] is sent by
to inform the Diameter server that an authorized session is being the HA to inform the Diameter server that an authorized session is
terminated. being terminated. This means that the HA MUST terminate the
corresponding Mobile IPv6 binding and also terminate the
corresponding SA.
4.3.2. Session-Termination-Answer 4.3.2. Session-Termination-Answer
The Session-Termination-Answer (STA) message [5] 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 [5] is sent by the Diameter The Abort-Session-Request (ASR) message [RFC3588] is sent by the
server to terminate the session. This fulfills one of the Diameter server to the HA to terminate the authorized session. This
requirement described in [16]. fulfills one of the requirement described in
[I-D.ietf-mext-aaa-ha-goals]. When the HA receives the ASR message,
it MUST terminate the corresponding SA. Subsequently, the HA MUST
take further actions to terminate the corresponding Mobile IPv6
binding.
4.3.4. Abort-Session-Answer 4.3.4. Abort-Session-Answer
The Abort-Session-Answer (ASA) message [5] is sent by the Home Agent The Abort-Session-Answer (ASA) message [RFC3588] is sent by the Home
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 [5]. below) and the Accounting Session State Machine as defined in
The command codes, exchanged between the HA and Diameter server for [RFC3588]. The command codes, exchanged between the HA and Diameter
accounting purposes, are provided in the following subsections. server for accounting purposes, are provided in the following
subsections.
The Diameter application design guideline [19] defines two separate The Diameter application design guideline
models for accounting: [I-D.ietf-dime-app-design-guide] defines two separate models for
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 Diameter Mobile IPv6 application
does not define its own unique accounting commands, this is the does not define its own unique accounting commands, this is the
preferred choice, since it permits use of centralized accounting preferred choice, since it permits use of centralized accounting
for several applications. for several applications.
Coupled accounting model: Coupled accounting model:
In this model, the accounting messages will use either the Mobile In this model, the accounting messages will use either the MIP6I
IPv6 Split or the Mobile IPv6 Auth Application Identifiers. This or the MIP6A Application Identifiers. This means that accounting
means that accounting messages will be routed like any other messages will be routed like any other Mobile IPv6 application
Mobile IPv6 application messages. This requires the Diameter messages. This requires the Diameter server in charge of Mobile
server in charge of Mobile IPv6 application to handle the IPv6 application to handle the accounting records (e.g., sends
accounting records (e.g., sends them to a proper accounting them to a proper accounting server).
server).
As mentioned above, the preferred choice is to use the split As mentioned above, the preferred choice is to use the split
accounting model and thus to choose Diameter Base Accounting accounting model and thus to choose Diameter Base Accounting
Application Identifier (value of 3) for accounting messages. Application Identifier (value of 3) for accounting messages.
4.4.1. Accounting-Request 4.4.1. Accounting-Request
The Accounting-Request command [5] is sent by the HA to the Diameter The Accounting-Request command [RFC3588] is sent by the HA to the
server to exchange accounting information regarding the MN with the Diameter server to exchange accounting information regarding the MN
Diameter server. with the Diameter server.
4.4.2. Accounting-Answer 4.4.2. Accounting-Answer
The Accounting-Answer command [5] is sent by the Diameter server to The Accounting-Answer command [RFC3588] is sent by the Diameter
the HA to acknowledge receiving 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 [7] commands: Diameter-EAP-Request (DER) the Diameter EAP application [RFC4072] commands: Diameter-EAP-Request
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 AVPs to support existing DER and DEA command ABNFs with a number 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. Diameter EAP application command ABNFs remain unchanged. The ABNF
language is defined in [RFC3588].
Command-Name Abbrev. Code Reference Application Command-Name Abbrev. Code Reference Application
--------------------------------------------------------------------- ---------------------------------------------------------------------
Diameter-EAP-Request DER 268 RFC 4072 Diameter Mobile IPv6 IKE Diameter-EAP-Request DER 268 RFC 4072 Diameter Mobile IPv6 IKE
Diameter-EAP-Answer DEA 268 RFC 4072 Diameter Mobile IPv6 IKE Diameter-EAP-Answer DEA 268 RFC 4072 Diameter Mobile IPv6 IKE
Figure 5: 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 TDB).
skipping to change at page 15, line 35 skipping to change at page 19, line 35
[ 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 is set during the EAP authentication. Thus, the Auth-Request-Type AVP MUST
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 message (DER). 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 TBD). If the
Mobile IPv6 authentication procedure was successful then the response Mobile IPv6 authentication procedure was successful then the response
MAY include any set of bootstrapping AVPs. MAY include any set of bootstrapping AVPs.
skipping to change at page 16, line 22 skipping to change at page 20, line 22
[ User-Name ] [ User-Name ]
[ EAP-Payload ] [ EAP-Payload ]
[ EAP-Reissued-Payload ] [ EAP-Reissued-Payload ]
[ EAP-Master-Session-Key ] [ EAP-Master-Session-Key ]
[ EAP-Key-Name ] [ EAP-Key-Name ]
[ Multi-Round-Time [ Multi-Round-Time
... ...
*2[ MIP-Mobile-Node-Address ] *2[ MIP-Mobile-Node-Address ]
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
[ MIP6-Agent-Info ] [ MIP6-Agent-Info ]
[ Service-Selection ]
* [ QoS-Resources ] * [ QoS-Resources ]
[ Chargeable-User-Identity ] [ Chargeable-User-Identity ]
... ...
* [ AVP ] * [ AVP ]
If the EAP-based authentication and the authorization for the If the EAP-based authentication and the authorization for the
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.
skipping to change at page 18, line 4 skipping to change at page 22, line 40
[ MIP-Timestamp ] [ MIP-Timestamp ]
[ QoS-Capability ] [ QoS-Capability ]
* [ QoS-Resources ] * [ QoS-Resources ]
[ Chargeable-User-Identity ] [ Chargeable-User-Identity ]
[ Service-Selection ] [ Service-Selection ]
[ Authorization-Lifetime ] [ Authorization-Lifetime ]
[ Auth-Session-State ] [ Auth-Session-State ]
* [ Proxy-Info ] * [ Proxy-Info ]
* [ Route-Record ] * [ Route-Record ]
* [ 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 he 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 TBD 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 MAY be included in the MIA if it is present in the MIR. The User-Name AVP MAY be included in the MIA if it is present in the
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 RFC 3588 [5]. Section 7, in addition to the values defined in RFC 3588 [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: XXX, PXY > <MIP6-Answer> ::= < Diameter Header: XXX, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Result-Code } { Result-Code }
skipping to change at page 18, line 42 skipping to change at page 23, line 30
[ Auth-Session-State ] [ Auth-Session-State ]
[ Error-Message ] [ Error-Message ]
[ Error-Reporting-Host ] [ Error-Reporting-Host ]
[ Re-Auth-Request-Type ] [ Re-Auth-Request-Type ]
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
[ MIP-Agent-Info ] [ MIP-Agent-Info ]
*2[ MIP-Mobile-Node-Address ] *2[ MIP-Mobile-Node-Address ]
[ MIP-MN-HA-MSA ] [ MIP-MN-HA-MSA ]
* [ QoS-Resources ] * [ QoS-Resources ]
[ Chargeable-User-Identity ] [ Chargeable-User-Identity ]
[ Service-Selection ]
[ 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 RFC 4285 [3] and for RFC 4877 [4] the AVPs in To provide support for RFC 4285 [RFC4285] and for RFC 4877 [RFC4877]
the following subsections are needed. RFC 3588, RFC 4004 and RFC the AVPs in the following subsections are needed. RFC 3588, RFC 4004
4005 [9] defined AVPs are reused whenever possible without changing and RFC 4005 [RFC4005] defined AVPs are reused whenever possible
the existing semantics of those AVPs. without changing the existing semantics of those AVPs.
+---------------------------+ +-------------------------+
| AVP Flag rules | | AVP Flag rules |
+-----+-----+----+-----+----+ +----+----+----+-----+----+
AVP Defined | | |SHLD| MUST|MAY | AVP Defined | | |SHLD| 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- TBD Note 1 Unsigned64 | M | P | | V | Y | |MIP6-Feature- TBD Note 1 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 334 RFC4004 Address | | | | | |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|MIP6-Agent-Info TBD Note 3 Grouped | M | P | | V | Y | |MIP6-Agent-Info TBD Note 3 Grouped | M | P | | V | Y |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|User-Name 1 RFC3588 UTF8String | M | P | | V | Y | |User-Name 1 RFC3588 UTF8String | M | P | | V | Y |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|Service- TBD 6.2 UTF8String | M | P | | V | Y | |Service- TBD 6.2 UTF8String | M | P | | V | Y |
| Selection | | | | | | | Selection | | | | | |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|QoS-Capability TBD Note 2 Grouped | M | P | | V | Y | |QoS-Capability TBD Note 2 Grouped | M | P | | V | Y |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|QoS-Resources TBD Note 2 Grouped | M | P | | V | Y | |QoS-Resources TBD Note 2 Grouped | M | P | | V | Y |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|MIP-MN-HA-MSA TBD 6.12 Grouped | M | P | | V | Y | |MIP-MN-HA-MSA TBD 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 MIP6-Feature-Vector is defined in Section 4.7.4 of [10]. Note 1: The MIP6-Feature-Vector AVP is defined in Section 4.7.4 of
[I-D.ietf-dime-mip6-integrated].
Note 2: The QoS-Capability and QoS-Resource AVPs are defined in Note 2: The QoS-Capability and the QoS-Resource AVPs are defined in
Sections 4.1 and 4.3 of [11]. Sections 4.1 and 4.3 of [I-D.ietf-dime-qos-attributes].
Note 3: The MIP6-Agent-Info is defined in Section 4.5.1 of [10]. Note 3: The MIP6-Agent-Info AVP is defined in Section 4.5.1 of
[I-D.ietf-dime-mip6-integrated].
+---------------------------+ +-------------------------+
| AVP Flag rules | | AVP Flag rules |
+-----+-----+----+-----+----+ +----+----+----+-----+----+
AVP Section | | |SHLD| MUST|MAY | AVP Section | | |SHLD| 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- TBD Note 1 Unsigned64 | M | P | | V | Y | |MIP6-Feature- TBD Note 1 Unsigned64 | M | P | | V | Y |
| Vector | | | | | | | Vector | | | | | |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|User-Name 1 RFC3588 UTF8String | M | P | | V | Y | |User-Name 1 RFC3588 UTF8String | M | P | | V | Y |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|Service- TBD 6.2 UTF8String | M | P | | V | Y | |Service- TBD 6.2 UTF8String | M | P | | V | Y |
| Selection | | | | | | | Selection | | | | | |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|MIP-MN-AAA-SPI 341 RFC4004 Unsigned32 | M | P | | V | Y | |MIP-MN-AAA-SPI 341 RFC4004 Unsigned32 | M | P | | V | Y |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|MIP-MN-HA-SPI TBD 6.4 Unsigned32 | M | P | | V | Y | |MIP-MN-HA-SPI TBD 6.4 Unsigned32 | M | P | | V | Y |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|MIP-Mobile- 333 RFC4004 Address | M | P | | V | Y | |MIP-Mobile- 333 RFC4004 Address | M | P | | V | Y |
| Node-Address | | | | | | | Node-Address | | | | | |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|MIP6-Agent-Info TBD Note 3 Grouped | M | P | | V | Y | |MIP6-Agent-Info TBD Note 3 Grouped | M | P | | V | Y |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|MIP-Careof- TBD 6.7 Address | M | P | | V | Y | |MIP-Careof- TBD 6.7 Address | M | P | | V | Y |
| Address | | | | | | | Address | | | | | |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|MIP- TBD 6.8 OctetString| M | P | | V | Y | |MIP- TBD 6.8 OctetString| M | P | | V | Y |
| Authenticator | | | | | | | Authenticator | | | | | |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|MIP-MAC- TBD 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 RFC4004 Unsigned32 | M | P | | V | Y | |MIP-MSA- 367 RFC4004 Unsigned32 | M | P | | V | Y |
| Lifetime | | | | | | | Lifetime | | | | | |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|MIP-MN-HA-MSA TBD 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 TBD 6.16 Time | M | P | | V | Y | |MIP-Timestamp TBD 6.16 Time | M | P | | V | Y |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|QoS-Capability TBD Note 2 Grouped | M | P | | M | Y | |QoS-Capability TBD Note 2 Grouped | M | P | | M | Y |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|QoS-Resources TBD Note 2 Grouped | M | P | | V | Y | |QoS-Resources TBD Note 2 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 TBD 6.20 Enumerated | M | P | | V | Y | |MIP6-Auth-Mode TBD 6.20 Enumerated | M | P | | V | Y |
+-----------------------------------------+-----+-----+----+-----+----+ +-----------------------------------------+----+----+----+-----+----+
|Rest of the AVPs RFC3588 | M | P | | V | Y | |Rest of the AVPs RFC3588 | M | P | | V | Y |
|in the MIR & MIA RFC4005 | | | | | | |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 MIP6-Feature-Vector is defined in Section 4.7.4 of [10]. Note 1: The MIP6-Feature-Vector AVP is defined in Section 4.7.4 of
[I-D.ietf-dime-mip6-integrated].
Note 2: The QoS-Capability and QoS-Resource AVPs are defined in Note 2: The QoS-Capability and the QoS-Resource AVPs are defined in
Sections 4.1 and 4.3 of [11]. Sections 4.1 and 4.3 of [I-D.ietf-dime-qos-attributes].
Note 3: The MIP6-Agent-Info is defined in Section 4.5.1 of [10]. Note 3: The MIP6-Agent-Info AVP is defined in Section 4.5.1 of
[I-D.ietf-dime-mip6-integrated].
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 an
NAI extracted from the MN-NAI mobility option included in the NAI extracted from the MN-NAI mobility option included in the
received BU message. Alternatively, the NAI can be extracted from received BU message. Alternatively, the NAI can be extracted from
the IKEv2 IDi payload included in the IKE_AUTH message sent by the the IKEv2 IDi payload included in the IKE_AUTH message sent by the
IKE initiator. 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 TBD) 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 that the
mobility service should be associated with. In the scope of this mobility service should be associated with. In the scope of this
specification the value can extracted from the IKEv2 IDr payload, if specification the value can extracted from the IKEv2 IDr payload, if
available in the IKE_AUTH message sent by the IKE initiator. 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 [20], if available in the received Service Selection Mobility Option [RFC5149], if available in the
BU. Future specification may define additional ways to populate the received BU. Future specification may define additional ways to
Service-Selection AVP with the required information. populate the Service-Selection AVP with the required information.
This specification uses the Service-Selection AVP only in the The AVP is also available to be used in messages sent from the
messages sent from the Diameter client to the Diameter Server. Diameter server to the Diameter client. For example, if the request
However, the AVP is also available to be used in messages sent from message did not contain the Service-Selection AVP but the MN was
the Diameter server to the Diameter client. assigned with a default service, the Diameter server MAY return the
name of the assigned default service to the HA.
If the Service-Selection AVP is present in both the request and the
reply messages, it SHOULD contain the same service name. If the
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 an SPI code extracted from the Mobility Message
Authentication Option included in the received BU message. The HA Authentication Option included in the received BU message. The HA
includes this AVP in the MIR message when the MN-AAA Mobility Message includes this AVP in the MIR message when the MN-AAA Mobility Message
Authentication Option is available in the received BU (and the MIP6- Authentication Option is available in the received BU (and the MIP6-
Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA). Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA).
This AVP is re-used from [12]. This AVP is re-used from [RFC4004].
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 TBD) is of type Unsigned32 and
contains an SPI code which 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 included in the MIR message, the Diameter server needs to return When included in the MIR message, the Diameter server needs to return
a valid MIP-MN-HA-MSA AVP in the corresponding MIA message. Either a valid MIP-MN-HA-MSA AVP in the corresponding MIA message. Either
the MIP-MN-HA-SPI AVP or the MIP-MN-AAA-SPI AVP MUST be present in the MIP-MN-HA-SPI AVP or the MIP-MN-AAA-SPI AVP MUST be present in
the MIR message, but not both. the MIR message, but not both.
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 unspecified IPv6 address If the MIP-Mobile-Node-Address AVP contains the unspecified IPv6
(0::0) or all zeroes IPv4 address (0.0.0.0) in a request message, address (0::0) or the all zeroes IPv4 address (0.0.0.0) in a request
then the HA expects the Diameter server to assign the Home Address in message, then the HA expects the Diameter server to assign the Home
a subsequent answer message. If the Diameter server assigns only an Address in a subsequent answer message. If the Diameter server
IPv6 Home Network Prefix to the Mobile Node the lower 64 bits of the assigns only an IPv6 Home Network Prefix to the Mobile Node the lower
MIP-Mobile-Node-Address AVP provided address MUST be set to zero. 64 bits of the MIP-Mobile-Node-Address AVP provided address MUST be
set to zero.
This AVP is re-used from [12]. This AVP is re-used from [RFC4004].
6.6. MIP6-Agent-Info AVP 6.6. MIP6-Agent-Info AVP
The MIP6-Agent-Info AVP is defined in Section 4.5.1 of [10] and The MIP6-Agent-Info AVP is defined in Section 4.5.1 of
contains the IPv6 or the IPv4 address information of the HA. The HA [I-D.ietf-dime-mip6-integrated] and contains the IPv6 or the IPv4
address in a request message is the same as in the received BU address information of the HA. The HA address in a request message
message that triggered the authentication and authorization procedure is the same as in the received BU message that triggered the
towards the Diameter server. authentication and authorization procedure towards the Diameter
server. One use case 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 a 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
[13]). If the Result-Code AVP is set to any other value, then the HA [RFC5142]). If the Result-Code AVP is set to any other value, then
SHOULD initiate the HA switch procedure towards the MN. The address the HA SHOULD initiate the HA switch procedure towards the MN. The
information of the assigned HA is defined in the MIP6-Agent-Info AVP. address information of the assigned HA is defined in the MIP6-Agent-
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 TBD) is of type Address and
contains the IPv6 Care-of Address of the Mobile Node. The HA contains the IPv6 Care-of Address of the Mobile Node. The HA
extracts this IP address from the received BU message. 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 TBD) is of type OctetString and
skipping to change at page 23, line 30 skipping to change at page 28, line 44
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. The HA includes this AVP Option included in the received BU message. The HA includes this AVP
in the MIR message and sets the Diameter server is expected to return in the MIR message and sets the Diameter server is expected to return
the key material required for the calculation and validation of the the key material required for the calculation and validation of the
Mobile IPv6 MN-HA Authentication Option (and the MIP6-Auth-Mode AVP Mobile IPv6 MN-HA Authentication Option (and the MIP6-Auth-Mode AVP
is set to value MIP6_AUTH_MN_AAA). is set to value MIP6_AUTH_MN_AAA).
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 TBD) is of type OctetString
and contains the calculated MAC_Mobility_Data, as defined in [3]. and contains the calculated MAC_Mobility_Data, as defined in
The HA includes this AVP in the MIR message when the MN-AAA Mobility [RFC4285]. The HA includes this AVP in the MIR message when the MN-
Message Authentication Option is available in the received BU and the AAA Mobility Message Authentication Option is available in the
Diameter server is expected to return the key material required for received BU and the Diameter server is expected to return the key
the calculation and validation of the Mobile IPv6 MN-HA material required for the calculation and validation of the Mobile
Authentication Option (and the MIP6-Auth-Mode AVP is set to value IPv6 MN-HA Authentication Option (and the MIP6-Auth-Mode AVP is set
MIP6_AUTH_MN_AAA). to value MIP6_AUTH_MN_AAA).
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 MH-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.
This AVP is re-used from [12]. This AVP is re-used 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 [12]. This AVP is re-used 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 TBD) 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: TBD >
{ MIP-Session-Key } { MIP-Session-Key }
{ MIP-MSA-Lifetime } { MIP-MSA-Lifetime }
skipping to change at page 24, line 34 skipping to change at page 29, line 49
the Mobile IPv6 MN-HA Authentication Option. the Mobile IPv6 MN-HA Authentication Option.
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 Algorithm identifier for the associated Mobile IPv6 MN-HA
Authentication Option. The Diameter server selects the algorithm Authentication Option. The Diameter server selects the algorithm
type. Existing algorithm types are defined in RFC 4004 that also type. Existing algorithm types are defined in RFC 4004 that also
fulfill current RFC 4285 requirements. fulfill current RFC 4285 requirements.
This AVP is re-used from [12]. This AVP is re-used from [RFC4004].
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 the HA for authenticating the mobile node.
The replay modes, defined in RFC 4004 [12], are supported. The replay modes, defined in RFC 4004 [RFC4004], are supported.
This AVP is re-used from [12]. This AVP is re-used from [RFC4004].
6.15. MIP6-Feature-Vector AVP 6.15. MIP6-Feature-Vector AVP
The MIP6-Feature-Vector AVP (AVP Code TBD) is of type Unsigned64 and The MIP6-Feature-Vector AVP (AVP Code TBD) is of type Unsigned64 and
defined in [10]. This document defines a new capability flag bit for defined in [I-D.ietf-dime-mip6-integrated]. This document defines a
signaling the support of Mobile IPv6 split scenario bootstrapping. new capability flag for signaling the support of Mobile IPv6 split
scenario bootstrapping.
MIP6_SPLIT (0x0000000100000000) MIP6_SPLIT (0x0000000100000000)
When this flag is set by the NAS then it means that the Mobile When this flag is set by the NAS then it means that the Mobile
IPv6 split scenario bootstrapping functionality is supported by IPv6 split scenario bootstrapping functionality is supported by
the NAS. When this flag is set by the Diameter server then the the NAS. When this flag is set by the Diameter server then the
Mobile IPv6 split scenario bootstrapping is supported by the Mobile IPv6 split scenario bootstrapping is supported by the
Diameter server. Diameter server.
6.16. MIP-Timestamp AVP 6.16. MIP-Timestamp AVP
The MIP-Timestamp AVP (AVP Code TBD) is of type Time and may contain The MIP-Timestamp AVP (AVP Code TBD) is of type Time and may contain
the timestamp value from the Mobility message replay protection the timestamp value from the Mobility message replay protection
option, defined in [3]. The HA extracts this value from the received option, defined in [RFC4285]. The HA extracts this value from the
BU message, if available. The HA includes this AVP in the MIR received BU message, if available. The HA includes this AVP in the
message when the MN-AAA Mobility Message Authentication Option is MIR message when the MN-AAA Mobility Message Authentication Option is
available in the received BU and the Diameter server is expected to available in the received BU and the Diameter server is expected to
return the key material required for the calculation and validation return the key material required for the calculation and validation
of the Mobile IPv6 MN-HA Authentication Option (and the MIP6-Auth- of the Mobile IPv6 MN-HA Authentication Option (and the MIP6-Auth-
Mode AVP is set to value MIP6_AUTH_MN_AAA). Mode AVP is set to value MIP6_AUTH_MN_AAA).
6.17. QoS-Capability AVP 6.17. QoS-Capability AVP
The QoS-Capability AVP is defined in [11] and contains a list of The QoS-Capability AVP is defined in [I-D.ietf-dime-qos-attributes]
supported Quality of Service profiles. and contains a list of supported Quality of Service profiles.
6.18. QoS-Resources AVP 6.18. QoS-Resources AVP
The QoS-Resources AVP is defined in [11] and provides QoS and packet The QoS-Resources AVP is defined in [I-D.ietf-dime-qos-attributes]
filtering capabilities. and provides QoS and 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 an unique temporary handle of the user. The Chargeable-
User-Identity is defined in RFC 4372 [14]. User-Identity is defined in RFC 4372 [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 TBD) 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. When the MIP6-Auth_Mode AVP used to authenticate the Binding Update. When the MIP6-Auth_Mode AVP
is set to the value of MIP6_AUTH_MN_AAA, the Auth-Request-Type AVP is set to the value of MIP6_AUTH_MN_AAA, the Auth-Request-Type AVP
MUST be set to the value of AUTHORIZE_AUTHENTICATE. MUST be set to the value of AUTHORIZE_AUTHENTICATE.
If the Diameter server does not support the Mobile IPv6 If the Diameter server does not support the Mobile IPv6
Authentication Protocol use mode proposed by the HA, then the Authentication Protocol usage mode proposed by the HA, then the
Diameter server MUST fail the authentication/authorization and set Diameter server MUST fail the authentication/authorization and MUST
the Result-Code AVP to the value of DIAMETER_ERROR_AUTH_MODE. set the Result-Code AVP to the value of DIAMETER_ERROR_AUTH_MODE.
6.21. Coupled Accounting Model Accounting AVPs 6.21. Accounting AVPs
Diameter Mobile IPv6 application is used in the case of the coupled Diameter Mobile IPv6 applications, either MIP6I or MIP6A, are used in
account model. Diameter Mobile IPv4 application [12] accounting AVPs the case of the coupled account model. Diameter Mobile IPv4
are reused in this document. The following AVPs SHOULD be included application [RFC4004] accounting AVPs are reused in this document.
in the accounting request message: The following AVPs SHOULD be included in the accounting request
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 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 [5] 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 TBD)
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_END_TO_END_MIP6_KEY_ENCRYPTION (Status Code TBD)
This error code is used by the Diameter server to inform the peer
that the requested Mobile IPv6 session keys could not be delivered
via a security association.
DIAMETER_ERROR_MIP6_AUTH_MODE (Status Code TBD) DIAMETER_ERROR_MIP6_AUTH_MODE (Status Code TBD)
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
skipping to change at page 28, line 32 skipping to change at page 35, line 21
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 |
MIP-Careof-Address | 0 | 0 | 0-1 | 0 | MIP-Careof-Address | 0 | 0 | 0-1 | 0 |
MIP-Authenticator | 0 | 0 | 0-1 | 0 | MIP-Authenticator | 0 | 0 | 0-1 | 0 |
MIP-MAC-Mobility-Data | 0 | 0 | 0-1 | 0 | MIP-MAC-Mobility-Data | 0 | 0 | 0-1 | 0 |
MIP-MSA-Lifetime | 0 | 0 | 0 | 1 | MIP-MSA-Lifetime | 0 | 0 | 0 | 1 |
MIP-MN-HA-MSA | 0 | 0 | 0 | 0-1 | MIP-MN-HA-MSA | 0 | 0 | 0 | 0-1 |
MIP-Timestamp | 0 | 0 | 0-1 | 0-1 | MIP-Timestamp | 0 | 0 | 0-1 | 0-1 |
User-Name | 0-1 | 0-1 | 1 | 0-1 | User-Name | 0-1 | 0-1 | 1 | 0-1 |
Service-Selection | 0-1 | 0 | 0-1 | 0 | Service-Selection | 0-1 | 0-1 | 0-1 | 0-1 |
QoS-Resources | *0 | *0 | *0 | *0 | QoS-Resources | *0 | *0 | *0 | *0 |
QoS-Capability | 0-1 | 0 | 0-1 | 0 | QoS-Capability | 0-1 | 0 | 0-1 | 0 |
Chargeable-User-Identity | 0-1 | 0-1 | 0-1 | 0-1 | Chargeable-User-Identity | 0-1 | 0-1 | 0-1 | 0-1 |
MIP6-Auth-Mode | 0 | 0 | 1 | 0 | MIP6-Auth-Mode | 0 | 0 | 1 | 0 |
+-----+-----+-----+-----+ +-----+-----+-----+-----+
8.2. Coupled Accounting Model AVP Table 8.2. Coupled Accounting Model AVP Table
The table in this section is used to represent which AVPs defined in The table in this section is used to represent which AVPs defined in
this document are to be present in the Accounting messages, as this document are to be present in the Accounting messages, as
defined in [5]. defined in [RFC3588].
+-------------+ +-------------+
| Command-Code| | Command-Code|
|------+------+ |------+------+
Attribute Name | ACR | ACA | Attribute Name | ACR | ACA |
-------------------------------------|------+------+ -------------------------------------|------+------+
Accounting-Input-Octets | 0-1 | 0-1 | Accounting-Input-Octets | 0-1 | 0-1 |
Accounting-Input-Packets | 0-1 | 0-1 | Accounting-Input-Packets | 0-1 | 0-1 |
Accounting-Output-Octets | 0-1 | 0-1 | Accounting-Output-Octets | 0-1 | 0-1 |
Accounting-Output-Packets | 0-1 | 0-1 | Accounting-Output-Packets | 0-1 | 0-1 |
skipping to change at page 29, line 36 skipping to change at page 37, line 14
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 values for the following IANA is requested to allocate a command code values for the following
new commands from the Command Code namespace defined in [5]. See new commands from the Command Code namespace defined in [RFC3588].
Section 5 for the assignment of the namespace in this specification. See Section 5 for the assignment of the namespace in this
specification.
Command Code | Value Command Code | Value
-----------------------------------+------ -----------------------------------+------
MIP6-Request (MIR) | TBD MIP6-Request (MIR) | TBD
MIP6-Answer (MIA) | TBD MIP6-Answer (MIA) | TBD
9.2. AVP Codes 9.2. AVP Codes
This specification requires IANA to register the following new AVPs This specification requires IANA to register the following new AVPs
from the AVP Code namespace defined in [5]. from the AVP Code 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
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 This specification requests IANA to allocate new values to the
Result-Code AVP (AVP Code 268) namespace defined in [5]. See Result-Code AVP (AVP Code 268) namespace defined in [RFC3588]. See
Section 7 for the assignment of the namespace in this specification. Section 7 for the assignment of the namespace in this specification.
Result-Code | Value Result-Code | Value
----------------------------------------------+------ ----------------------------------------------+------
DIAMETER_SUCCESS_RELOCATE_HA | TBD DIAMETER_SUCCESS_RELOCATE_HA | TBD
DIAMETER_ERROR_END_TO_END_MIP6_KEY_ENCRYPTION | TBD
DIAMETER_ERROR_MIP6_AUTH_MODE | TBD DIAMETER_ERROR_MIP6_AUTH_MODE | TBD
9.4. Application Identifier 9.4. Application Identifier
This specification requires IANA to allocate two new values "Diameter This specification requires IANA to allocate two new values "Diameter
Mobile IPv6 IKE" and "Diameter Mobile IPv6 Auth" from the Application Mobile IPv6 IKE" and "Diameter Mobile IPv6 Auth" from the Application
Identifier namespace defined in [5]. Identifier namespace defined in [RFC3588].
Application Identifier | Value Application Identifier | Value
-----------------------------------+------ -----------------------------------+------
Diameter Mobile IPv6 IKE (MIP6I) | TBD Diameter Mobile IPv6 IKE (MIP6I) | TBD
Diameter Mobile IPv6 Auth (MIP6A) | TBD Diameter Mobile IPv6 Auth (MIP6A) | TBD
9.5. Namespaces 9.5. Namespaces
This specification defines new values to the "Mobility Capability" This specification defines new values to the "Mobility Capability"
registry (see [10]) for use with the MIP6-Feature-Vector AVP: registry (see [I-D.ietf-dime-mip6-integrated]) for use with the MIP6-
Feature-Vector AVP:
Token | Value | Description Token | Value | Description
---------------------------------+----------------------+------------ ---------------------------------+----------------------+------------
MIP6_SPLIT | 0x0000000100000000 | RFC TBD MIP6_SPLIT | 0x0000000100000000 | RFC TBD
IANA is requested to create a new registry "MIP6 Authentication Mode" IANA is requested to create a new registry "MIP6 Authentication Mode"
registry for use with the enumerated MIP6-Auth-Mode AVP. The registry for use with the enumerated MIP6-Auth-Mode AVP. The
registry will initially contain the following values: registry will initially contain the following values:
Token | Value | Description Token | Value | Description
---------------------------------------------+----------+------------ ---------------------------------------------+----------+------------
MIP6_AUTH_MN_AAA | 1 | RFC TBD MIP6_AUTH_MN_AAA | 1 | RFC TBD
Allocation of new values follow the example policies described in Allocation of new values follow the example policies described in
[21] new values for the MIP6-Auth-Mode AVP will be assigned based on [RFC5226] new values for the MIP6-Auth-Mode AVP will be assigned
the "Specification Required" policy. based on the "Specification Required" policy.
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 in [2]. Additionally, accomplish the split scenario are described in in [RFC5026].
the security considerations of the Diameter Base protocol [5], Additionally, the security considerations of the Diameter Base
Diameter EAP application [7] are applicable to this document. protocol [RFC3588], Diameter EAP application [RFC4072] are 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 rely on the
security properties of the intermediate AAA brokers and Diameter security properties of the intermediate AAA brokers and Diameter
agents (such as proxies). agents (such as proxies).
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
skipping to change at page 32, line 7 skipping to change at page 41, line 9
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 draft were possible while he was under their
employ. employ.
12. References 12. References
12.1. Normative References 12.1. Normative References
[1] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in [I-D.ietf-dime-mip6-integrated]
IPv6", RFC 3775, June 2004. Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C.,
and K. Chowdhury, "Diameter Mobile IPv6: Support for
Network Access Server to Diameter Server Interaction",
draft-ietf-dime-mip6-integrated-11 (work in progress),
November 2008.
[2] Giaretta, G., Kempf, J., and V. Devarapalli, "Mobile IPv6 [I-D.ietf-dime-qos-attributes]
Bootstrapping in Split Scenario", RFC 5026, October 2007. Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones, M.,
and A. Lior, "Quality of Service Attributes for Diameter",
draft-ietf-dime-qos-attributes-09 (work in progress),
December 2008.
[3] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury, [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
"Authentication Protocol for Mobile IPv6", Requirement Levels", BCP 14, RFC 2119, March 1997.
draft-ietf-mip6-rfc4285bis-03 (work in progress), July 2008.
[4] Devarapalli, V. and F. Dupont, "Mobile IPv6 Operation with [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
IKEv2 and the Revised IPsec Architecture", RFC 4877, Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
April 2007.
[5] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko, [RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
"Diameter Base Protocol", RFC 3588, September 2003. in IPv6", RFC 3775, June 2004.
[6] Bradner, S., "Key words for use in RFCs to Indicate Requirement [RFC4004] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and
Levels", BCP 14, RFC 2119, March 1997. P. McCann, "Diameter Mobile IPv4 Application", RFC 4004,
August 2005.
[7] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible [RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton,
"Diameter Network Access Server Application", RFC 4005,
August 2005.
[RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
Authentication Protocol (EAP) Application", RFC 4072, Authentication Protocol (EAP) Application", RFC 4072,
August 2005. August 2005.
[8] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol", [RFC4306] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol",
RFC 4306, December 2005. RFC 4306, December 2005.
[9] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter [RFC4372] Adrangi, F., Lior, A., Korhonen, J., and J. Loughney,
Network Access Server Application", RFC 4005, August 2005. "Chargeable User Identity", RFC 4372, January 2006.
[10] Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C., and
K. Chowdhury, "Diameter Mobile IPv6: Support for Network Access
Server to Diameter Server Interaction",
draft-ietf-dime-mip6-integrated-10 (work in progress),
September 2008.
[11] Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones, M., and
A. Lior, "Quality of Service Attributes for Diameter",
draft-ietf-dime-qos-attributes-07 (work in progress),
June 2008.
[12] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and P. [RFC4877] Devarapalli, V. and F. Dupont, "Mobile IPv6 Operation with
McCann, "Diameter Mobile IPv4 Application", RFC 4004, IKEv2 and the Revised IPsec Architecture", RFC 4877,
August 2005. April 2007.
[13] Haley, B., Devarapalli, V., Deng, H., and J. Kempf, "Mobility [RFC5026] Giaretta, G., Kempf, J., and V. Devarapalli, "Mobile IPv6
Header Home Agent Switch Message", RFC 5142, January 2008. Bootstrapping in Split Scenario", RFC 5026, October 2007.
[14] Adrangi, F., Lior, A., Korhonen, J., and J. Loughney, [RFC5142] Haley, B., Devarapalli, V., Deng, H., and J. Kempf,
"Chargeable User Identity", RFC 4372, January 2006. "Mobility Header Home Agent Switch Message", RFC 5142,
January 2008.
12.2. Informative References 12.2. Informative References
[15] Patel, A. and G. Giaretta, "Problem Statement for bootstrapping [I-D.ietf-dime-app-design-guide]
Mobile IPv6 (MIPv6)", RFC 4640, September 2006. Fajardo, V., Asveren, T., Tschofenig, H., McGregor, G.,
and J. Loughney, "Diameter Applications Design
Guidelines", draft-ietf-dime-app-design-guide-08 (work in
progress), November 2008.
[16] Giaretta, G., Guardini, I., Demaria, E., Bournelle, J., and R. [I-D.ietf-mext-aaa-ha-goals]
Lopez, "AAA Goals for Mobile IPv6", Giaretta, G., Guardini, I., Demaria, E., Bournelle, J.,
draft-ietf-mext-aaa-ha-goals-01 (work in progress), May 2008. and R. Lopez, "AAA Goals for Mobile IPv6",
draft-ietf-mext-aaa-ha-goals-01 (work in progress),
May 2008.
[17] Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and [I-D.ietf-mext-nemo-v4traversal]
Routers", draft-ietf-mext-nemo-v4traversal-05 (work in Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and
progress), July 2008. Routers (DSMIPv6)", draft-ietf-mext-nemo-v4traversal-07
(work in progress), December 2008.
[18] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury, [RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K.
"Mobile Node Identifier Option for Mobile IPv6 (MIPv6)", Chowdhury, "Mobile Node Identifier Option for Mobile IPv6
RFC 4283, November 2005. (MIPv6)", RFC 4283, November 2005.
[19] Fajardo, V., Asveren, T., Tschofenig, H., McGregor, G., and J. [RFC4285] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K.
Loughney, "Diameter Applications Design Guidelines", Chowdhury, "Authentication Protocol for Mobile IPv6",
draft-ietf-dime-app-design-guide-07 (work in progress), RFC 4285, January 2006.
July 2008.
[20] Korhonen, J., Nilsson, U., and V. Devarapalli, "Service [RFC4640] Patel, A. and G. Giaretta, "Problem Statement for
bootstrapping Mobile IPv6 (MIPv6)", RFC 4640,
September 2006.
[RFC5149] Korhonen, J., Nilsson, U., and V. Devarapalli, "Service
Selection for Mobile IPv6", RFC 5149, February 2008. Selection for Mobile IPv6", RFC 5149, February 2008.
[21] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
Authors' Addresses Authors' Addresses
Jouni Korhonen Jouni Korhonen (editor)
TeliaSonera Nokia Siemens Networks
P.O.Box 970 Linnoitustie 6
Sonera FIN-00051 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 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
skipping to change at page 35, line 4 skipping to change at line 1527
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
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 172 change blocks. 
367 lines changed or deleted 436 lines changed or added

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