draft-ietf-dime-mip6-split-07.txt   draft-ietf-dime-mip6-split-08.txt 
Diameter Maintenance and J. Korhonen Diameter Maintenance and J. Korhonen
Extensions (DIME) TeliaSonera Extensions (DIME) TeliaSonera
Internet-Draft H. Tschofenig Internet-Draft H. Tschofenig
Intended status: Standards Track Nokia Siemens Networks Intended status: Standards Track Nokia Siemens Networks
Expires: August 28, 2008 J. Bournelle Expires: November 29, 2008 J. Bournelle
Orange Labs Orange Labs
G. Giaretta G. Giaretta
Qualcomm Qualcomm
M. Nakhjiri M. Nakhjiri
Motorola Motorola
February 25, 2008 May 28, 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-07.txt draft-ietf-dime-mip6-split-08.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes 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. 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
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 August 28, 2008. This Internet-Draft will expire on November 29, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
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 (MSP). 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 (IKEv2)
protocol allows different mechanisms, such as the Extensible protocol allows different mechanisms, such as the Extensible
Authentication Protocol (EAP), certificates and pre-shared secrets to Authentication Protocol (EAP), certificates and pre-shared secrets to
be used. Furthermore, another method makes use of the Mobile IPv6 be used. Furthermore, another method makes use of the Mobile IPv6
Authentication protocol. In addition to authentication and Authentication Protocol. In addition to authentication and
authorization, the configuration of Mobile IPv6 specific parameters authorization, the configuration of Mobile IPv6 specific parameters
and accounting is specified in this document. and accounting is specified in this document.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. Advertising Application Support . . . . . . . . . . . . . . . 7 3. Application Identifiers . . . . . . . . . . . . . . . . . . . 7
4. Protocol Description . . . . . . . . . . . . . . . . . . . . . 7 4. Protocol Description . . . . . . . . . . . . . . . . . . . . . 7
4.1. Support for Mobile IPv6 with IKEv2 and EAP . . . . . . . . 7 4.1. Support for Mobile IPv6 with IKEv2 and EAP . . . . . . . . 7
4.2. Support for Mobile IPv6 with IKEv2 and Certificates . . . 9 4.2. Support for Mobile IPv6 with IKEv2 and Certificates . . . 11
4.3. Support for Mobile IPv6 with IKEv2 and Pre-Shared 4.3. Support for Mobile IPv6 with IKEv2 and Pre-Shared
Secrets . . . . . . . . . . . . . . . . . . . . . . . . . 10 Secrets . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.4. Support for the Mobile IPv6 Authentication Protocol . . . 10 4.4. Support for the Mobile IPv6 Authentication Protocol . . . 11
4.5. Mobile IPv6 Session Management . . . . . . . . . . . . . . 11 4.5. Mobile IPv6 Session Management . . . . . . . . . . . . . . 12
4.5.1. Session-Termination-Request . . . . . . . . . . . . . 11 4.5.1. Session-Termination-Request . . . . . . . . . . . . . 12
4.5.2. Session-Termination-Answer . . . . . . . . . . . . . . 11 4.5.2. Session-Termination-Answer . . . . . . . . . . . . . . 13
4.5.3. Abort-Session-Request . . . . . . . . . . . . . . . . 11 4.5.3. Abort-Session-Request . . . . . . . . . . . . . . . . 13
4.5.4. Abort-Session-Answer . . . . . . . . . . . . . . . . . 12 4.5.4. Abort-Session-Answer . . . . . . . . . . . . . . . . . 13
4.6. Accounting for Mobile IPv6 services . . . . . . . . . . . 12 4.6. Accounting for Mobile IPv6 services . . . . . . . . . . . 13
4.6.1. Accounting-Request . . . . . . . . . . . . . . . . . . 12 4.6.1. Accounting-Request . . . . . . . . . . . . . . . . . . 14
4.6.2. Accounting-Answer . . . . . . . . . . . . . . . . . . 13 4.6.2. Accounting-Answer . . . . . . . . . . . . . . . . . . 14
5. Command Codes . . . . . . . . . . . . . . . . . . . . . . . . 13 5. Command Codes . . . . . . . . . . . . . . . . . . . . . . . . 14
5.1. Command Code for Mobile IPv6 with IKEv2 and EAP . . . . . 13 5.1. Command Code for Mobile IPv6 with IKEv2 and EAP . . . . . 14
5.1.1. Diameter-EAP-Request . . . . . . . . . . . . . . . . . 13 5.1.1. Diameter-EAP-Request . . . . . . . . . . . . . . . . . 14
5.1.2. Diameter-EAP-Answer . . . . . . . . . . . . . . . . . 14 5.1.2. Diameter-EAP-Answer . . . . . . . . . . . . . . . . . 15
5.2. Command Code for Mobile IPv6 with IKEv2 and 5.2. Command Code for Mobile IPv6 with IKEv2 and
Certificate- and PSK-based Authentication . . . . . . . . 15 Certificate- and PSK-based Authentication . . . . . . . . 16
5.2.1. AA-Request . . . . . . . . . . . . . . . . . . . . . . 15 5.2.1. AA-Request . . . . . . . . . . . . . . . . . . . . . . 16
5.2.2. AA-Answer . . . . . . . . . . . . . . . . . . . . . . 16 5.2.2. AA-Answer . . . . . . . . . . . . . . . . . . . . . . 17
5.3. Command Codes for MIPv6 Authentication Protocol Support . 17 5.3. Command Codes for Mobile IPv6 Authentication Protocol
5.3.1. MIP6-Request-Message . . . . . . . . . . . . . . . . . 17 Support . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.3.2. MIP6-Answer-Message . . . . . . . . . . . . . . . . . 18 5.3.1. MIP6-Request-Message . . . . . . . . . . . . . . . . . 18
6. AVPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.3.2. MIP6-Answer-Message . . . . . . . . . . . . . . . . . 19
6.1. User-Name AVP . . . . . . . . . . . . . . . . . . . . . . 22 6. AVPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.2. Called-Station-Id AVP . . . . . . . . . . . . . . . . . . 22 6.1. User-Name AVP . . . . . . . . . . . . . . . . . . . . . . 23
6.3. MIP-MN-AAA-SPI AVP . . . . . . . . . . . . . . . . . . . . 22 6.2. Called-Station-Id AVP . . . . . . . . . . . . . . . . . . 23
6.4. MIP-MN-HA-SPI AVP . . . . . . . . . . . . . . . . . . . . 22 6.3. MIP-MN-AAA-SPI AVP . . . . . . . . . . . . . . . . . . . . 23
6.5. MIP-Mobile-Node-Address AVP . . . . . . . . . . . . . . . 22 6.4. MIP-MN-HA-SPI AVP . . . . . . . . . . . . . . . . . . . . 23
6.6. MIP-Home-Agent-Address AVP . . . . . . . . . . . . . . . . 23 6.5. MIP-Mobile-Node-Address AVP . . . . . . . . . . . . . . . 23
6.7. MIP-Careof-Address AVP . . . . . . . . . . . . . . . . . . 23 6.6. MIP-Home-Agent-Address AVP . . . . . . . . . . . . . . . . 24
6.8. MIP-Authenticator AVP . . . . . . . . . . . . . . . . . . 23 6.7. MIP-Careof-Address AVP . . . . . . . . . . . . . . . . . . 24
6.9. MIP-MAC-Mobility-Data AVP . . . . . . . . . . . . . . . . 23 6.8. MIP-Authenticator AVP . . . . . . . . . . . . . . . . . . 24
6.10. MIP-Session-Key AVP . . . . . . . . . . . . . . . . . . . 23 6.9. MIP-MAC-Mobility-Data AVP . . . . . . . . . . . . . . . . 24
6.11. MIP-MSA-Lifetime AVP . . . . . . . . . . . . . . . . . . . 23 6.10. MIP-Session-Key AVP . . . . . . . . . . . . . . . . . . . 24
6.12. MIP-MN-HA-MSA AVP . . . . . . . . . . . . . . . . . . . . 24 6.11. MIP-MSA-Lifetime AVP . . . . . . . . . . . . . . . . . . . 25
6.13. MIP-Algorithm-Type AVP . . . . . . . . . . . . . . . . . . 24 6.12. MIP-MN-HA-MSA AVP . . . . . . . . . . . . . . . . . . . . 25
6.14. MIP-Replay-Mode AVP . . . . . . . . . . . . . . . . . . . 24 6.13. MIP-Algorithm-Type AVP . . . . . . . . . . . . . . . . . . 25
6.15. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . . . 24 6.14. MIP-Replay-Mode AVP . . . . . . . . . . . . . . . . . . . 25
6.16. MIP-Timestamp AVP . . . . . . . . . . . . . . . . . . . . 25 6.15. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . . . 25
6.17. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 25 6.16. MIP-Timestamp AVP . . . . . . . . . . . . . . . . . . . . 26
6.18. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 25 6.17. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 27
6.19. Coupled Accounting Model Accounting AVPs . . . . . . . . . 25 6.18. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 27
7. Result-Code AVP Values . . . . . . . . . . . . . . . . . . . . 26 6.19. Chargeable-User-Identity AVP . . . . . . . . . . . . . . . 27
7.1. Permanent Failures . . . . . . . . . . . . . . . . . . . . 26 6.20. Coupled Accounting Model Accounting AVPs . . . . . . . . . 27
8. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 27 7. Result-Code AVP Values . . . . . . . . . . . . . . . . . . . . 28
8.1. AAR, AAA, DER, DEA, MRM and MAM AVP/Command-Code Table . . 27 7.1. Success . . . . . . . . . . . . . . . . . . . . . . . . . 28
8.2. Coupled Accounting Model AVP Table . . . . . . . . . . . . 28 7.2. Permanent Failures . . . . . . . . . . . . . . . . . . . . 28
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 8. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 28
9.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 28 8.1. AAR, AAA, DER, DEA, MRM and MAM AVP/Command-Code Table . . 29
9.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . 28 8.2. Coupled Accounting Model AVP Table . . . . . . . . . . . . 29
9.3. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 29 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
9.4. Application Identifier . . . . . . . . . . . . . . . . . . 29 9.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 30
9.5. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 29 9.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . 30
9.6. Mobile IPv6 Status Codes . . . . . . . . . . . . . . . . . 29 9.3. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 31
10. Security Considerations . . . . . . . . . . . . . . . . . . . 29 9.4. Application Identifier . . . . . . . . . . . . . . . . . . 31
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 30 9.5. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 31
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 30 9.6. Mobile IPv6 Status Codes . . . . . . . . . . . . . . . . . 31
12.1. Normative References . . . . . . . . . . . . . . . . . . . 30 10. Security Considerations . . . . . . . . . . . . . . . . . . . 32
12.2. Informative References . . . . . . . . . . . . . . . . . . 31 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Intellectual Property and Copyright Statements . . . . . . . . . . 33 12.1. Normative References . . . . . . . . . . . . . . . . . . . 32
12.2. Informative References . . . . . . . . . . . . . . . . . . 33
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 34
Intellectual Property and Copyright Statements . . . . . . . . . . 36
1. Introduction 1. Introduction
Performing the Mobile IPv6 protocol [1], requires the Mobile Node Performing the Mobile IPv6 protocol [1], requires the Mobile Node
(MN) to own a Home Address (HoA) and to have an assigned Home Agent (MN) to own a Home Address (HoA) and to have an assigned Home Agent
(HA) to the MN. The MN needs to register with the HA in order enable (HA) to the MN. The MN needs to register with the HA in order to
its reachability and mobility, when away from home. The registration enable its reachability and mobility, when away from its home link.
process itself requires establishment of IPSec security associations The registration process itself may require an establishment of IPSec
(SA) and cryptographic material between the MN and HA. Providing the security associations (SA) and cryptographic material between the MN
collection of home address, HA address and keying material is and HA. Alternatively, the registration process may be secured using
generally referred to as the Mobile IPv6 bootstrapping problem [13]. a mobility message authentication option, which enables IPv6 mobility
The purpose of this specification is to provide Diameter support for in a MN without having to establish an IPSec SA with its HA.
the interaction between the HA and the AAA server required to solve Providing the collection of home address, HA address and keying
the bootstrapping problem in the split scenario [2] in a manner that material is generally referred to as the Mobile IPv6 bootstrapping
satisfies the requirements defined in [14]. problem [15]. The purpose of this specification is to provide
Diameter support for the interaction between the HA and the AAA
server. This specification satisfies the requirements defined in
[16] for the bootstrapping problem in the split scenario [2] and also
specifies Diameter support for the Authentication Protocol for Mobile
IPv6 [3]. The Diameter support defined in this specification also
applies to Dual Stack Mobile IPv6 [17].
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 that such services are accounted for. Only Mobile IPv6 service, and is accounted for those. Only when the MN is
when the MN is authenticated and authorized, the MSP allows the authenticated and authorized, the MSP allows the bootstrapping of
bootstrapping of Mobile IPv6 parameters. Thus, prior to processing Mobile IPv6 parameters. Thus, prior to processing the Mobile IPv6
the Mobile IPv6 registrations, the HA, participates in the registrations, the HA, participates in the authentication of the MN
authentication of the MN to verify the MN's identity. The HA also to verify the MN's identity. The HA also participates in the Mobile
participates in the Mobile IPv6 authorization process involving the IPv6 authorization process involving the Diameter infrastructure.
Diameter infrastructure. The HA, due to its role in traffic The HA, due to its role in traffic forwarding, may also perform
forwarding, may also perform accounting for the Mobile IPv6 service accounting for the Mobile IPv6 service provided to the MN.
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: Asserting or helping with assertion of the
correctness of the MN identity. As a Diameter client supporting correctness of the MN identity. As a Diameter client supporting
the new Diameter Mobile IPv6 application, the HA may need to the new Diameter Mobile IPv6 application, the HA may 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 use Authorization: The HA must verify that the user is authorized to the
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
commands specifically designed for performing Mobile IPv6 applications specifically designed for performing Mobile IPv6
authorization decisions. This document defines these commands and authorization decisions. This document defines required AAA
requires the HA to support them and to participate in this procedures and requires the HA to support them and to participate
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 of the HA to provide accounting report 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
require the AAA to abort or the HA to terminate the Mobile IPv6
service before the binding expires. This document defines
procedures for the AAA based session management.
Figure 1 depicts the reference architecture for this document. Figure 1 depicts the reference architecture for this document.
+--------+ +--------+
|Diameter| |Diameter|
|Server | |Server |
+--------+ +--------+
^ ^
Back-End | Diameter MIPv6 Back-End | Diameter Mobile IPv6
Protocol | HA<->AAA Server Protocol | HA<->AAA Server
Support | Interaction Support | Interaction
| (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 protected using Mobile IPv6 signaling between the MN and the HA can be protected
two different mechanisms, namely using IPSec and via the MIPv6 using two different mechanisms, namely using IPSec or Authentication
Authentication Protocol [3]. The important aspect is, however, that Protocol for Mobile IPv6 [3]. For these two approaches several
for these two approaches several different authentication and key different authentication and key exchange solutions are available.
exchange solutions are available. To establish IPSec security When IPSec is used to protect Mobile IPv6 signaling messages, IKEv2
associations, protecting of Mobile IPv6 signaling messages IKEv2 is is used [4]. IKEv2 supports EAP-based authentication, certificates
used [4]. IKEv2 supports EAP-based authentication, certificates and and pre-shared secrets. Alternatively, Authentication Protocol for
pre-shared secrets. For protecting using the MIPv6 Authentication Mobile IPv6 uses a mechanism that is very similar to the one used for
Protocol [3] a mechanism has been designed that is very similar to protecting Mobile IPv4 signaling messages.
the one used by Mobile IPv4.
The ability to use different credentials has an impact on the The ability to use different credentials has an impact on the
interaction between the HA (acting as a Diameter client) and the interaction between the HA (acting as a Diameter client) and the
Diameter Server. For that reason this document illustrates the usage Diameter Server. For that reason this document illustrates the usage
of these authentication mechanisms with different subsections for: of these authentication mechanisms with different subsections for:
o IKEv2 usage with EAP o IKEv2 usage with EAP
o IKEv2 usage with certificates and pre-shared secrets o IKEv2 usage with certificates and pre-shared secrets
o MIPv6 Authentication Protocol o Mobile IPv6 Authentication Protocol
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 accounting application defined in [5]. specification uses the Diameter Base Protocol accounting defined in
RFC 3588 [5].
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 [6].
The MIPv6 bootstrapping terminology is taken from [13]. The Mobile IPv6 bootstrapping terminology is taken from [15].
3. Advertising Application Support 3. Application Identifiers
Diameter nodes conforming to this specification MUST advertise This specification defines two new Diameter applications and their
support by including the Diameter Mobile IPv6 Application ID value of respective Application Identifiers:
[TO BE ASSIGNED BY IANA] in the Auth-Application-Id AVP of the
Capabilities-Exchange-Request and Capabilities-Exchange-Answer Diameter Mobile IPv6 IKE (MIP6I) TBD by IANA
command [5]. The Acct-Application-id AVP needs to include the Diameter Mobile IPv6 Auth (MIP6A) TBD by IANA
Diameter Base Accounting Application ID value of 3 (to support the
split accounting model [15]). The MIP6I Application Identifier is used when the MN is authenticated
and authorized using IKEv2. The MIP6A Application Identifier is used
when the MN is authenticated and authorized using Mobile IPv6
Authentication Protocol.
Mobile IPv6 related accounting generated by the HA uses either MIP6I
or MIP6A Application Identifier in the case of coupled accounting
model. Diameter Base Accounting Application Identifier (value of 3)
is used in the case of split accounting model. Refer Section 4.6 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, as defined in [7], is re-used. EAP methods that do not application, as defined in [7], is re-used. EAP methods that do not
establish a shared key SHOULD NOT be used, as they are subject to a establish a shared key SHOULD NOT be used, as they are subject to a
number of man-in-the-middle attacks as stated in Section 2.16 and number of man-in-the-middle attacks as stated in Section 2.16 and
Section 5 of RFC 4306 [8]. AVPs specific to Mobile IPv6 Section 5 of RFC 4306 [8]. AVPs specific to Mobile IPv6
bootstrapping are added to the EAP application commands. bootstrapping are added to the EAP application commands.
Figure 2 shows the message flow involved during the authentication Figure 3 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 8, line 50 skipping to change at page 9, line 50
|<--------------------------------| | |<--------------------------------| |
| | | | | |
| HDR, SK{AUTH} | | | HDR, SK{AUTH} | |
|-------------------------------->| | |-------------------------------->| |
| | | | | |
| HDR, SK{AUTH, [CP(CFG_REPLY,] | | | HDR, SK{AUTH, [CP(CFG_REPLY,] | |
| SAr2, TSi, TSr} | | | SAr2, TSi, TSr} | |
|<--------------------------------| | |<--------------------------------| |
| | | | | |
Figure 2: Mobile IPv6 bootstrapping using IKEv2 and EAP Figure 3: 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
skipping to change at page 9, line 37 skipping to change at page 10, line 37
and DEA messages carry the method specific exchanges between the MN and DEA messages carry the method specific exchanges between the MN
and the Diameter server/EAP server. 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 scenario, 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 problem in this case is that the
IKEv2 responder may not know if IKEv2 is used for MIP6 service or for IKEv2 responder may not know if IKEv2 is used for Mobile IPv6 service
IPSec VPN access. The IKEv2 responder may A network operator needs or for IPSec VPN access service. A network operator needs to be
to be aware of this limitation. aware of this limitation. The MN may provide a hint of the intended
service, for example, by using different identities in the IKE_AUTH
message for the IPSec VPN service and Mobile IPv6 service. However,
the use of different identities during the IKEv2 negotiation is
deployment specific. Another possibility is to make the distinction
on the MN subscription basis. In this case the Diameter server can
inform the HA during the IKEv2 negotiation whether the MN is
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 Mobile IPv6 with IKEv2 and Certificates 4.2. Support for Mobile IPv6 with IKEv2 and Certificates
When IKEv2 is used with certificate-based authentication, the When IKEv2 is used with certificate-based authentication, the
Diameter NASREQ application [9] is used to authorize the MN for the Diameter NASREQ application [9] is used to authorize the MN for the
Mobile IPv6 service. The IDi payload extracted from the IKE_AUTH Mobile IPv6 service. The IDi payload extracted from the IKE_AUTH
message MUST correspond to the identity in the MN's certificate. message MUST correspond to the identity in the MN's certificate.
This identity is then used by the HA to populate the User-Name AVP in
This identity is then used by the Home Agent to populate the User- the succeeding AA-Request message. Further PKI-related procedures
Name AVP in the succeeding AA-Request message. Further PKI-related such as certificate revocation checking are out of scope of this
procedures such as certificate revocation checking are out of scope document.
of this document.
4.3. Support for Mobile IPv6 with IKEv2 and Pre-Shared Secrets 4.3. Support for Mobile IPv6 with IKEv2 and Pre-Shared Secrets
When IKEv2 is used with PSK-based initiator authentication, the When IKEv2 is used with PSK-based initiator authentication, the
Diameter NASREQ application [9] is re-used to authorize the MN for Diameter NASREQ application [9] is re-used to authorize the MN for
the Mobile IPv6 service. The IDi payload extracted from the IKE_AUTH the Mobile IPv6 service. The IDi payload extracted from the IKE_AUTH
message has to contain an identity that is meaningful for the message has to contain an identity that is meaningful for the
Diameter infrastructure, such as a Network Access Identifier (NAI), Diameter infrastructure, such as a Network Access Identifier (NAI),
and is then used by the Home Agent to populate the User-Name AVP in and is then used by the HA to populate the User-Name AVP in the
the succeeding AA-Request message. succeeding AA-Request message.
4.4. Support for the Mobile IPv6 Authentication Protocol 4.4. Support for the Mobile IPv6 Authentication Protocol
Figure 3 shows the message sequence between the MN, the HA and the Figure 4 shows the message sequence between the MN, the HA and the
Diameter server during the registration when MIPv6 Authentication Diameter server during the registration when Mobile IPv6
Protocol is used. BU and Binding Acknowledgement (BA) messages are Authentication Protocol is used. A BU and a Binding Acknowledgement
used in the binding registration process. This exchange triggers the (BA) messages are used in the binding registration process.
Diameter interaction.
Receiving a BU at the HA initiates a MIP6-Request-Message to be sent
to the Diameter server. The Diameter server in turn responds with a
MIP6-Answer-Message. The HA may assign a Home Address to the MN and
provide it to the Diameter server in the MIP-Mobile-Node-Address AVP.
According to [3] the MN uses the Mobile Node Identifier Option, According to [3] the MN uses the Mobile Node Identifier Option,
specifically the MN-NAI mobility option (as defined in [16]) to specifically the MN-NAI mobility option (as defined in [18]) to
identify itself. identify itself. The HA MUST copy the MN-NAI mobility option value
to the User-Name AVP in the subsequent request messages.
Receiving the BU at the HA initiates a MIP6-Request-Message to the The procedure described in this specification for the Mobile IPv6
Diameter server, which in turn responds with a MIP6-Answer-Message. Authentication Protocol is only needed for the initial BU received by
The Home Agent also provides the assigned Home Address to the the HA. When the HA receives subsequent BUs, they are processed
Diameter server in the MIP-Mobile-Node-Address AVP. locally in the HA. It is RECOMMENDED that the HA sends an accounting
request 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 the deployment and the local policy.
The procedure described here for the Mobile IPv6 Authentication In some architectures and network deployments the MN-HA security
Protocol is only needed for the initial BU received by the HA. When associations may be established as a result of a successful network
the HA receives subsequent BUs, they are processed locally in the HA. access authentication. In such deployments, both MN and Diameter
It is RECOMMENDED that the HA sends an accounting request message server share the keying material required for computation and
every time it receives a Binding Update. validation of the MN-HA Authentication Option, and a Security
Parameter Index (SPI) for indexing an appropriate security
association. Upon receiving a BU with a MN-HA Authentication Option,
the HA retrieves the keying material required for the computation and
validation of the MN-HA Authentication Option from the Diameter
server. The Diameter request message sent by the HA must contain
enough information (such as SPI, MN-NAI, etc) so that the Diameter
server is able to locate the matching MN-HA security association and
return correct keying material back to the HA.
Mobile Home Diameter Mobile Home Diameter
Node Agent Server Node Agent Server
| | | | | |
| | | | | |
| Binding Update |MIP6-Request-Message | | Binding Update |MIP6-Request-Message |
|------------------------------------>|-------------------->| |------------------------------------>|-------------------->|
| (Mobile Node Identifier Option, | | | (Mobile Node Identifier Option, | |
| Mobility Message Replay Protection | | | Mobility Message Replay Protection | |
| Option, Authentication Option) | | | Option, Authentication Option) | |
| | | | | |
| | | | | |
| Binding Acknowledgement |MIP6-Answer-Message | | Binding Acknowledgement |MIP6-Answer-Message |
|<------------------------------------|<--------------------| |<------------------------------------|<--------------------|
| (Mobile Node Identifier Option | | | (Mobile Node Identifier Option | |
| Mobility Message Replay Protection | | | Mobility Message Replay Protection | |
| Option, Authentication Option) | | | Option, Authentication Option) | |
Figure 3: MIPv6 Bootstrapping using the MIPv6 Authentication Protocol Figure 4: Mobile IPv6 Bootstrapping using the Mobile IPv6
Authentication Protocol
4.5. Mobile IPv6 Session Management 4.5. 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 [5].
Moreover, the following four commands may be exchanged between the HA Moreover, the following four commands may be exchanged between the HA
and the Diameter server. and the Diameter server.
4.5.1. Session-Termination-Request 4.5.1. Session-Termination-Request
skipping to change at page 11, line 48 skipping to change at page 13, line 15
4.5.2. Session-Termination-Answer 4.5.2. Session-Termination-Answer
The Session-Termination-Answer (STA) message [5] is sent by the The Session-Termination-Answer (STA) message [5] 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.5.3. Abort-Session-Request 4.5.3. Abort-Session-Request
The Abort-Session-Request (ASR) message [5] is sent by the Diameter The Abort-Session-Request (ASR) message [5] is sent by the Diameter
server to terminate the session. This fulfills one of the server to terminate the session. This fulfills one of the
requirement described in [14]. requirement described in [16].
4.5.4. Abort-Session-Answer 4.5.4. Abort-Session-Answer
The Abort-Session-Answer (ASA) message [5] is sent by the Home Agent The Abort-Session-Answer (ASA) message [5] is sent by the Home Agent
in response to an ASR message. in response to an ASR message.
4.6. Accounting for Mobile IPv6 services 4.6. 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 [5].
The command codes, exchanged between the HA and Diameter server for The command codes, exchanged between the HA and Diameter server for
accounting purposes, are provided in the following subsections. accounting purposes, are provided in the following subsections.
The Diameter application design guideline [15] defines two separate The Diameter application design guideline [19] defines two separate
models for accounting: 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 ID (value of 3). Since accounting is Base Accounting Application Identifier (value of 3). Since
treated as an independent application, accounting commands may be accounting is treated as an independent application, accounting
routed separately from the rest of application messages and thus commands may be routed separately from the rest of application
the accounting messages generally end up in a central accounting messages and thus the accounting messages generally end up in a
server. Since Diameter Mobile IPv6 application does not define central accounting server. Since Diameter Mobile IPv6 application
its own unique accounting commands, this is the preferred choice, does not define its own unique accounting commands, this is the
since it permits use of centralized accounting for several preferred choice, since it permits use of centralized accounting
applications. for several applications.
Coupled accounting model: Coupled accounting model:
In this model, the accounting messages will use the application ID In this model, the accounting messages will use either the Mobile
of the Mobile IPv6 application. This means that accounting IPv6 Split or the Mobile IPv6 Auth Application Identifiers. This
messages will be routed like any other Mobile IPv6 application means that accounting messages will be routed like any other
messages. This requires the Diameter server in charge of Mobile Mobile IPv6 application messages. This requires the Diameter
IPv6 application to handle the accounting records (e.g., sends server in charge of Mobile IPv6 application to handle the
them to a proper accounting server). accounting records (e.g., sends them to a proper accounting
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 ID (value of 3) for accounting messages. Application Identifier (value of 3) for accounting messages.
4.6.1. Accounting-Request 4.6.1. Accounting-Request
The Accounting-Request command [5] is sent by the HA to the Diameter The Accounting-Request command [5] is sent by the HA to the Diameter
server to exchange accounting information regarding the MN with the server to exchange accounting information regarding the MN with the
Diameter server. Diameter server.
4.6.2. Accounting-Answer 4.6.2. Accounting-Answer
The Accounting-Answer command [5] is sent by the Diameter server to The Accounting-Answer command [5] is sent by the Diameter server to
the HA to acknowledge receiving an Accounting-Request. the HA to acknowledge receiving 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 usage of Mobile IPv6 with IKEv2 and EAP this document re-uses the For the use of Mobile IPv6 with IKEv2 and EAP this document re-uses
Diameter EAP application [7] commands. The following commands are the Diameter EAP application [7] commands. The command ABNFs are
used to carry MIPv6 related bootstrapping AVPs. extended with a number AVPs to support Mobile IPv6 split scenario
bootstrapping. Other than new additional AVPs and the corresponding
additions to the command ABNFs, the Diameter EAP application command
ABNFs remain unchanged.
Command-Name Abbrev. Code Reference Application Command-Name Abbrev. Code Reference Application
----------------------------------------------------------------------- ---------------------------------------------------------------------
Diameter-EAP-Request DER 268 RFC 4072 Diameter Mobile IPv6 (TBD) Diameter-EAP-Request DER 268 RFC 4072 Diameter Mobile IPv6 IKE
Diameter-EAP-Answer DEA 268 RFC 4072 Diameter Mobile IPv6 (TBD) Diameter-EAP-Answer DEA 268 RFC 4072 Diameter Mobile IPv6 IKE
Figure 4: Command Codes Figure 5: Command Codes
5.1.1. Diameter-EAP-Request 5.1.1. Diameter-EAP-Request
The Diameter-EAP-Request (DER) message [7], indicated by the Command- The Diameter-EAP-Request (DER) message [7], indicated by the Command-
Code field set to 268 and the 'R' bit set in the Command Flags field, Code 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 is sent by the HA to the Diameter server to initiate a Mobile IPv6
service authentication and authorization procedure. The DER message service authentication and authorization procedure. The DER message
format is the same as defined in [7]. The Application-ID field of format is the same as defined in [7]. The Application-ID field of
the Diameter Header MUST be set to the Diameter Mobile IPv6 the Diameter Header MUST be set to the Diameter Mobile IPv6 IKE
Application ID [TO BE ASSIGNED TO IANA]. Application ID (value of TDB).
<Diameter-EAP-Request> ::= < Diameter Header: 268, REQ, PXY > <Diameter-EAP-Request> ::= < Diameter Header: 268, REQ, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Destination-Realm } { Destination-Realm }
{ Auth-Request-Type } { Auth-Request-Type }
[ Destination-Host ] [ Destination-Host ]
[ NAS-Identifier ] [ NAS-Identifier ]
[ NAS-IP-Address ] [ NAS-IP-Address ]
[ NAS-IPv6-Address ] [ NAS-IPv6-Address ]
[ NAS-Port-Type ] [ NAS-Port-Type ]
[ User-Name ] [ User-Name ]
... ...
[ Called-Station-Id] [ Called-Station-Id]
... ...
{ EAP-Payload } { EAP-Payload }
... ...
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
{ MIP-Home-Agent-Address } 1*2{ MIP-Home-Agent-Address }
{ MIP-Mobile-Node-Address } 1*2{ MIP-Mobile-Node-Address }
[ Chargeable-User-Identity ]
[ QoS-Capability ] [ QoS-Capability ]
* [ QoS-Resources ] * [ QoS-Resources ]
... ...
* [ AVP ] * [ AVP ]
5.1.2. Diameter-EAP-Answer 5.1.2. Diameter-EAP-Answer
The Diameter-EAP-Answer (DEA) message defined in [7], indicated by The Diameter-EAP-Answer (DEA) message defined in [7], indicated by
the Command-Code field set to 268 and 'R' bit cleared in the Command the Command-Code field set to 268 and 'R' bit cleared in the Command
Flags field, is sent in response to the Diameter-EAP-Request message Flags field, is sent in response to the Diameter-EAP-Request message
(DER). If the Mobile IPv6 authentication procedure was successful (DER). The DEA message format is the same as defined in [7]. The
then the response MAY include any set of bootstrapping AVPs. 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 DEA message format is the same as defined in [7]. The Mobile IPv6 authentication procedure was successful then the response
Application-Id field in the Diameter header MUST be set to the MAY include any set of bootstrapping AVPs.
Diameter Mobile IPv6 Application-Id [TO BE ASSIGNED BY IANA].
<Diameter-EAP-Answer> ::= < Diameter Header: 268, PXY > <Diameter-EAP-Answer> ::= < Diameter Header: 268, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Auth-Request-Type } { Auth-Request-Type }
{ Result-Code } { Result-Code }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
[ User-Name ] [ User-Name ]
[ EAP-Payload ] [ EAP-Payload ]
[ EAP-Reissued-Payload ]
[ EAP-Master-Session-Key ]
[ EAP-Key-Name ]
[ Multi-Round-Time
... ...
*2[ MIP-Mobile-Node-Address ]
[ MIP-Mobile-Node-Address ]
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
*2[ MIP-Home-Agent-Address ]
* [ QoS-Resources ] * [ QoS-Resources ]
[ Chargeable-User-Identity ]
... ...
* [ AVP ] * [ AVP ]
5.2. Command Code for Mobile IPv6 with IKEv2 and Certificate- and PSK- 5.2. Command Code for Mobile IPv6 with IKEv2 and Certificate- and PSK-
based Authentication based Authentication
This document re-uses the Diameter NASREQ application commands. The This document re-uses the Diameter NASREQ application commands. The
following commands are used to carry MIPv6 related bootstrapping following commands are used to carry Mobile IPv6 related
AVPs. bootstrapping AVPs.
Command-Name Abbrev. Code Reference Application Command-Name Abbrev. Code Reference Application
----------------------------------------------------------------------- ---------------------------------------------------------------------
AA-Request AAR 265 RFC 4005 Diameter Mobile IPv6 (TBD) AA-Request AAR 265 RFC 4005 Diameter Mobile IPv6 IKE
AA-Answer AAA 265 RFC 4005 Diameter Mobile IPv6 (TBD) AA-Answer AAA 265 RFC 4005 Diameter Mobile IPv6 IKE
Figure 7: Command Codes Figure 8: Command Codes
5.2.1. AA-Request 5.2.1. AA-Request
The AA-Request (AAR) message [9], indicated by the Command-Code field The AA-Request (AAR) message [9], indicated by the Command-Code field
set to 265 and the 'R' bit set in the Command Flags field, is sent by set to 265 and the 'R' bit set in the Command Flags field, is sent by
the HA to the Diameter server to initiate a Mobile IPv6 service the HA to the Diameter server to initiate a Mobile IPv6 service
authentication and authorization procedure. The AAR message format authentication and authorization procedure. The AAR message format
is the same as defined in [9]. The Application-ID field of the is the same as defined in [9]. The Application-ID field of the
Diameter Header MUST be set to the Diameter Mobile IPv6 Application Diameter Header MUST be set to the Diameter Mobile IPv6 IKE
ID [TO BE ASSIGNED TO IANA]. Application ID (value of TBD).
<AA-Request> ::= < Diameter Header: 265, REQ, PXY > <AA-Request> ::= < Diameter Header: 265, REQ, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Destination-Realm } { Destination-Realm }
{ Auth-Request-Type } { Auth-Request-Type }
[ Destination-Host ] [ Destination-Host ]
[ NAS-Identifier ] [ NAS-Identifier ]
[ NAS-IP-Address ] [ NAS-IP-Address ]
[ NAS-IPv6-Address ] [ NAS-IPv6-Address ]
[ NAS-Port-Type ] [ NAS-Port-Type ]
[ User-Name ] [ User-Name ]
... ...
[ Called-Station-Id] [ Called-Station-Id]
... ...
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
{ MIP-Home-Agent-Address } 1*2{ MIP-Home-Agent-Address }
{ MIP-Mobile-Node-Address } 1*2{ MIP-Mobile-Node-Address }
[ Chargeable-User-Identity ]
... ...
[ QoS-Capability ] [ QoS-Capability ]
* [ QoS-Resources ] * [ QoS-Resources ]
... ...
* [ AVP ] * [ AVP ]
5.2.2. AA-Answer 5.2.2. AA-Answer
The AA-Answer (AAA) message defined in [9], indicated by the Command- The AA-Answer (AAA) message defined in [9], indicated by the Command-
Code field set to 265 and 'R' bit cleared in the Command Flags field, Code field set to 265 and 'R' bit cleared in the Command Flags field,
is sent in response to the AA-Request message (AAR). If the Mobile is sent in response to the AA-Request message (AAR). If the Mobile
IPv6 authentication procedure was successful then the response MAY IPv6 authentication procedure was successful then the response MAY
include any set of bootstrapping AVPs. include any set of bootstrapping AVPs.
The AAA message format is the same as defined in [9]. The The AAA message format is the same as defined in [9]. The
Application-Id field in the Diameter header MUST be set to the Application-Id field in the Diameter header MUST be set to the
Diameter Mobile IPv6 Application-Id [TO BE ASSIGNED BY IANA]. Diameter Mobile IPv6 IKE Application-Id (value of TBD).
<AA-Answer> ::= < Diameter Header: 265, PXY > <AA-Answer> ::= < Diameter Header: 265, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Auth-Request-Type } { Auth-Request-Type }
{ Result-Code } { Result-Code }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
[ User-Name ] [ User-Name ]
[ Authorization-Lifetime ] [ Authorization-Lifetime ]
... ...
[ MIP-Mobile-Node-Address ] *2[ MIP-Mobile-Node-Address ]
*2[ MIP-Home-Agent-Address ]
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
[ MIP-MN-HA-MSA ] [ MIP-MN-HA-MSA ]
* [ QoS-Resources ] * [ QoS-Resources ]
[ Chargeable-User-Identity ]
... ...
* [ AVP ] * [ AVP ]
When IKEv2 is used with PSK-based initiator authentication, the pre- When IKEv2 is used with PSK-based initiator authentication, the pre-
shared secret is carried inside the MIP-MN-HA-MSA AVP. The pre- shared secret is carried inside the MIP-MN-HA-MSA AVP. The pre-
shared secret SHOULD NOT be user's long term secret and it is shared secret SHOULD NOT be user's long term secret and it is
RECOMMENDED that a short-term keying material specifically created RECOMMENDED that a short-term keying material specifically created
for this purpose is used instead. for this purpose is used instead.
5.3. Command Codes for MIPv6 Authentication Protocol Support 5.3. Command Codes for Mobile IPv6 Authentication Protocol Support
This section defines the commands that are used for support with the This section defines the commands that are used for support with the
MIPv6 Authentication Protocol. Mobile IPv6 Authentication Protocol.
Command-Name Abbrev. Code Reference Application Command-Name Abbrev. Code Reference Application
---------------------------------------------------------------------- ---------------------------------------------------------------------
MIP6-Request-Message MRM TBD 5.3.1 Diameter Mobile IPv6 (TBD) MIP6-Request-Message MRM TBD 5.3.1 Diameter Mobile IPv6 Auth
MIP6-Answer-Message MAM TBD 5.3.2 Diameter Mobile IPv6 (TBD) MIP6-Answer-Message MAM TBD 5.3.2 Diameter Mobile IPv6 Auth
Command Codes Command Codes
5.3.1. MIP6-Request-Message 5.3.1. MIP6-Request-Message
The MIP6-Request-Message (MRM), indicated by the Command-Code field The MIP6-Request-Message (MRM), indicated by the Command-Code field
set to TBD and the 'R' bit set in the Command Flags field, is sent by set to TBD and the 'R' bit set in the Command Flags field, is sent by
the HA, acting as a Diameter client, in order to request the the HA, acting as a Diameter client, in order to request the
authentication and authorization of a MN. authentication and authorization of a MN.
skipping to change at page 18, line 20 skipping to change at page 19, line 22
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
[ Acct-Multi-Session-Id ] [ Acct-Multi-Session-Id ]
[ Destination-Host ] [ Destination-Host ]
[ Origin-State-Id ] [ Origin-State-Id ]
[ NAS-Identifier ] [ NAS-Identifier ]
[ NAS-IP-Address ] [ NAS-IP-Address ]
[ NAS-IPv6-Address ] [ NAS-IPv6-Address ]
[ NAS-Port-Type ] [ NAS-Port-Type ]
[ Called-Station-Id ]
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
[ MIP-MN-AAA-SPI ] [ MIP-MN-AAA-SPI ]
[ MIP-MN-HA-SPI ]
{ MIP-Mobile-Node-Address } { MIP-Mobile-Node-Address }
{ MIP-Home-Agent-Address } { MIP-Home-Agent-Address }
[ MIP-Careof-Address ] [ MIP-Careof-Address ]
[ MIP-Authenticator ] [ MIP-Authenticator ]
[ MIP-MAC-Mobility-Data ] [ MIP-MAC-Mobility-Data ]
[ MIP-Timestamp ] [ MIP-Timestamp ]
[ QoS-Capability ] [ QoS-Capability ]
* [ QoS-Resources ] * [ QoS-Resources ]
[ Chargeable-User-Identity ]
[ Authorization-Lifetime ] [ Authorization-Lifetime ]
[ Auth-Session-State ] [ Auth-Session-State ]
* [ Proxy-Info ] * [ Proxy-Info ]
* [ Route-Record ] * [ Route-Record ]
* [ AVP ] * [ AVP ]
5.3.2. MIP6-Answer-Message 5.3.2. MIP6-Answer-Message
The MIP6-Answer-Message (MAM) message, indicated by the Command-Code The MIP6-Answer-Message (MAM) message, indicated by the Command-Code
skipping to change at page 19, line 24 skipping to change at page 20, line 29
[ 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-Home-Agent-Address ] [ MIP-Home-Agent-Address ]
[ MIP-Mobile-Node-Address ] [ MIP-Mobile-Node-Address ]
[ MIP-MN-HA-MSA ] [ MIP-MN-HA-MSA ]
* [ QoS-Resources ] * [ QoS-Resources ]
[ Chargeable-User-Identity ]
[ Origin-State-Id ] [ Origin-State-Id ]
* [ Proxy-Info ] * [ Proxy-Info ]
* [ 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 [3] and for RFC 4877 [4] the AVPs in
the following subsections are needed. RFC 3588, RFC 4004 and RFC the following subsections are needed. RFC 3588, RFC 4004 and RFC
4005 defined AVPs are reused whenever possible without changing the 4005 defined AVPs are reused whenever possible without changing the
skipping to change at page 20, line 25 skipping to change at page 21, line 25
| Node-Address 334 RFC4004 Address | | | | | | | Node-Address 334 RFC4004 Address | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-Home- 334 RFC4004 Address | M | P | | V | Y | |MIP-Home- 334 RFC4004 Address | M | P | | V | Y |
| Agent-Address | | | | | | | Agent-Address | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|User-Name 1 RFC3588 UTF8String | M | P | | V | Y | |User-Name 1 RFC3588 UTF8String | M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|Called- 30 RFC4005 UTF8String | M | P | | V | Y | |Called- 30 RFC4005 UTF8String | M | P | | V | Y |
| Station-Id | | | | | | | Station-Id | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|QoS-Capability TBD Note 2 Grouped | | P | | M,V | Y | |QoS-Capability TBD Note 2 Grouped | M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|QoS-Resources TBD Note 2 Grouped | | P | | M,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 |
| Identity 89 6.19 | | | | | |
+-----------------------------------------+----+-----+----+-----+----+
AVPs for Mobile IPv6 with IKEv2 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 is defined in Section 4.7.4 of [10].
Note 2: The QoS-Capability and QoS-Resource AVPs are defined in Note 2: The QoS-Capability and QoS-Resource AVPs are defined in
Sections 4.1 and 4.3 of [11]. Sections 4.1 and 4.3 of [11].
+--------------------------+ +--------------------------+
| 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 |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|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 | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-Home- 334 RFC4004 Address | M | P | | V | Y | |MIP-Home- 334 RFC4004 Address | M | P | | V | Y |
| Agent-Address | | | | | | | Agent-Address | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|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 | | P | | M,V | Y | |QoS-Capability TBD Note 2 Grouped | | M,P | | M | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|QoS-Resources TBD Note 2 Grouped | | P | | M,V | Y | |QoS-Resources TBD Note 2 Grouped | | M,P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
AVPs for the Mobile IPv6 Authentication Protocol |Chargeable-User- OctetString| | M,P | | V | Y |
| Identity 89 6.19 | | | | | |
+-----------------------------------------+----+-----+----+-----+----+
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 is defined in Section 4.7.4 of [10].
Note 2: The QoS-Capability and QoS-Resource AVPs are defined in Note 2: The QoS-Capability and QoS-Resource AVPs are defined in
Sections 4.1 and 4.3 of [11]. Sections 4.1 and 4.3 of [11].
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. Called-Station-Id AVP 6.2. Called-Station-Id AVP
The Called-Station-Id AVP (AVP Code 30) is of type UTF8String and The Called-Station-Id AVP (AVP Code 30) is of type UTF8String and
contains the string extracted from the IKEv2 IDr payload, if contains the string 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. If the
Mobile IPv6 Authentication Protocol is used, then the
Called-Station-Id AVP contains the string extracted from the Service
Selection Mobility Option [20], if available in the received BU.
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. Authentication Option included in the received BU message.
This AVP is re-used from [12]. This AVP is re-used from [12].
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 provided by the Diameter server for the Mobile contains an SPI code which can be used with other parameters for
IPv6 MN-HA Authentication Option. identifying the security association required for the validation of
the Mobile IPv6 MN-HA Authentication Option.
When included in the MRM message, the Diameter server needs to return
a valid MIP-MN-HA-MSA AVP in the corresponding MAM message.
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 Home Agent assigned IPv6 Home Address of the Mobile contains the Home Agent assigned IPv6 or IPv4 Home Address of the
Node. Mobile Node.
If the MIP-Mobile-Node-Address AVP contains unspecified IPv6 address If the MIP-Mobile-Node-Address AVP contains unspecified IPv6 address
(0::0) in a request message, then the Home Agent expects the Diameter (0::0) or all zeroes IPv4 address (0.0.0.0) in a request message,
server to assign the Home Address in a subsequent reply message. In then the HA expects the Diameter server to assign the Home Address in
case the Diameter server assigns only a Home Network Prefix to the a subsequent answer message. If the Diameter server assigns only an
Mobile Node the lower 64 bits of the MIP-Mobile-Node-Address AVP IPv6 Home Network Prefix to the Mobile Node the lower 64 bits of the
provided address MUST be set to zero. 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 [12].
6.6. MIP-Home-Agent-Address AVP 6.6. MIP-Home-Agent-Address AVP
The MIP-Home-Agent-Address AVP (AVP Code 334) is of type Address and The MIP-Home-Agent-Address AVP (AVP Code 334) is of type Address and
contains the IPv6 address of the Home Agent. The Home Agent address contains the IPv6 or the IPv4 address of the HA. The HA address in a
is the same as in the received BU message that triggered the request message is the same as in the received BU message that
authentication and authorization procedure towards the Diameter triggered the authentication and authorization procedure towards the
server. This AVP is re-used from [12]. Diameter server.
If the MIP-Home-Agent-Address AVP is present in an answer message and
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
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
SHOULD initiate the Home Agent switch procedure towards the MN. The
address of the assigned HA is defined in the MIP-Home-Agent-Address
AVP.
This AVP is re-used from [12].
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 Home Agent 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
contains the Authenticator Data from the received BU message. The contains the Authenticator Data from the received BU message. The HA
Home Agent extracts this data from the MN-AAA Mobility Message extracts this data from the MN-AAA Mobility Message Authentication
Authentication Option included in the received BU message. Option included in the received BU message.
6.9. MIP-MAC-Mobility-Data AVP 6.9. MIP-MAC-Mobility-Data AVP
The MIP-MAC-Mobility-Data AVP (AVP Code TBD) is of type OctetString The MIP-MAC-Mobility-Data AVP (AVP Code 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 [3].
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
skipping to change at page 24, line 8 skipping to change at page 25, line 19
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 [12].
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 MIPv6 Authentication the session related information for use with the Mobile IPv6
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 }
[ MIP-MN-HA-SPI ] [ MIP-MN-HA-SPI ]
[ MIP-Algorithm-Type ] [ MIP-Algorithm-Type ]
[ MIP-Replay-Mode ] [ MIP-Replay-Mode ]
* [ AVP ] * [ AVP ]
6.13. MIP-Algorithm-Type AVP 6.13. MIP-Algorithm-Type AVP
skipping to change at page 24, line 32 skipping to change at page 25, line 43
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 [12].
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 Home Agent for authenticating the mobile contains the replay mode the HA for authenticating the mobile node.
node. The replay modes, defined in RFC 4004 [12], are supported. The replay modes, defined in RFC 4004 [12], are supported.
This AVP is re-used from [12]. This AVP is re-used from [12].
6.15. MIP6-Feature-Vector AVP 6.15. MIP6-Feature-Vector AVP
This AVP is defined in [10]. This document defines a new capability This AVP is defined in [10]. This document defines a new capability
bit for signaling the support of Mobile IPv6 route optimization. The bit for signaling the support of Mobile IPv6 route optimization. The
following capability is defined in this document: following capability is defined in this document:
RO_SUPPORTED (0x0000000800000000) RO_SUPPORTED (0x0000000800000000)
Route optimization is supported. When the Home Agent sets this Route optimization is supported. When the HA sets this bit, it
bit, it indicates support for the route optimization. If this bit indicates support for the route optimization. If this bit is
is unset in the returned Mobility-Capability AVP, the AAAH does unset in the returned Mobility-Capability AVP, the AAAH does not
not authorize route optimization for the MN. authorize route optimization for the MN.
In a case the Home Agent or the AAAH cannot authorize the use of In a case the HA or the AAAH cannot authorize the use of route
route optimization then the Home Agent SHOULD send a Binding optimization then the HA SHOULD send a Binding Acknowledgement
Acknowledgement with a Status Code set to with a Status Code set to ACCEPTED_BUT_NO_ROUTE_OPTIMIZATION
ACCEPTED_BUT_NO_ROUTE_OPTIMIZATION (status code TBD). This Status (status code TBD). This Status Code indicates that the binding
Code indicates that the binding registration succeeded but the registration succeeded but the HA will fail all possible
Home Agent will fail all possible subsequent route optimization subsequent route optimization attempts because of subscription or
attempts because of subscription or operator policy. operator policy.
USER_TRAFFIC_ENCRYPTION (0x0000000100000000) USER_TRAFFIC_ENCRYPTION (0x0000000100000000)
User plane traffic encryption is supported. When the Home Agent User plane traffic encryption is supported. When the HA sets this
sets this bit, it indicates support for the user plane traffic bit, it indicates support for the user plane traffic encryption
encryption between the MN and the Home Agent. If this bit is between the MN and the HA. If this bit is unset in the returned
unset in the returned Mobility-Capability AVP, the AAAH does not Mobility-Capability AVP, the AAAH does not authorize user plane
authorize user plane traffic encryption for the MN because of traffic encryption for the MN because of subscription or operator
subscription or operator policy. policy.
In the case the AAAH cannot authorize the use of route In the case the AAAH cannot authorize the use of route
optimization then the Home Agent SHOULD send a Binding optimization then the HA SHOULD send a Binding Acknowledgement
Acknowledgement with a Status Code set to with a Status Code set to ACCEPTED_BUT_NO_TRAFFIC_ENCRYPTION
ACCEPTED_BUT_NO_TRAFFIC_ENCRYPTION (status code TBD). This Status (status code TBD). This Status Code indicates that the binding
Code indicates that the binding registration succeeded but the registration succeeded but the HA will silently discard all
Home Agent will silently discard all encrypted user plane packets encrypted user plane packets sent by the MN to the Home Agent.
sent by the MN to the Home Agent.
VPN_GW_MODE (0x0000000200000000)
The HA is supposed to act as a IPSec VPN gateway for the user.
When the Home Agent sets this bit, it indicates support for acting
as a standalone IPSec VPN gateway. If this bit is unset in the
returned Mobility-Capability AVP, the AAAH does not authorize the
HA to act as a standalone IPSec VPN gateway for the MN because of
subscription or operator policy.
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 Home Agent extracts this value from the option, defined in [3]. The HA extracts this value from the received
received BU message, if available. BU message, if available.
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 [11] and contains a list of
supported Quality of Service profiles. supported Quality of Service profiles.
6.18. QoS-Resources AVP 6.18. QoS-Resources AVP
The QoS-Resources AVP is defined in [11] and provides QoS and packet The QoS-Resources AVP is defined in [11] and provides QoS and packet
filtering capabilities. filtering capabilities.
6.19. Coupled Accounting Model Accounting AVPs 6.19. Chargeable-User-Identity AVP
The Chargeable-User-Identity AVP (AVP code 89) is of type OctetString
and contains an unique temporary handle of the user. The Chargeable-
User-Identity is defined in RFC 4372 [14].
6.20. Coupled Accounting Model Accounting AVPs
Diameter Mobile IPv6 application is used in the case of the coupled Diameter Mobile IPv6 application is used in the case of the coupled
account model. Diameter Mobile IPv4 application [12] accounting AVPs account model. Diameter Mobile IPv4 application [12] accounting AVPs
are reused in this document. The following AVPs MUST be included in are reused in this document. The following AVPs MUST be included in
the accounting request message: 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
skipping to change at page 26, line 22 skipping to change at page 27, line 45
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-Home-Agent-Address: The current home agent of the mobile node. o MIP-Home-Agent-Address: The current home agent of the mobile node.
o Chargeable-User-Identity: The unique temporary identity of the
user. This AVP MUST be included if it is available in the home
agent.
Other APVs that SHOULD be included in the accounting request message Other APVs that SHOULD be included in the accounting request message
include: include:
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 [5] 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. Permanent Failures 7.1. Success
Errors that fall within the Success category are used to inform a
peer that a request has been successfully completed.
DIAMETER_SUCCESS_RELOCATE_HA (Status Code TBD)
This result code is used by the Diameter server to inform the HA
that the MN MUST be switched to another HA.
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) DIAMETER_ERROR_END_TO_END_MIP6_KEY_ENCRYPTION (Status Code TBD)
This error is used by the Diameter server to inform the peer that This error is used by the Diameter server to inform the peer that
the requested Mobile IPv6 session keys could not be delivered via the requested Mobile IPv6 session keys could not be delivered via
a security association. a security association.
skipping to change at page 27, line 37 skipping to change at page 29, line 29
One instance of the AVP MUST be present in the message. One instance of the AVP MUST be present in the message.
8.1. AAR, AAA, DER, DEA, MRM and MAM AVP/Command-Code Table 8.1. AAR, AAA, DER, DEA, MRM and MAM AVP/Command-Code Table
+-----------------------------------+ +-----------------------------------+
| Command-Code | | Command-Code |
|-----+-----+-----+-----+-----+-----+ |-----+-----+-----+-----+-----+-----+
AVP Name | AAR | AAA | DER | DEA | MRM | MAM | AVP Name | AAR | AAA | DER | DEA | MRM | MAM |
-------------------------------|-----+-----|-----+-----+-----+-----+ -------------------------------|-----+-----|-----+-----+-----+-----+
MIP6-Feature-Vector | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 | MIP6-Feature-Vector | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |
MIP-Mobile-Node-Address | 1 | 0-1 | 1 | 0-1 | 1 | 0-1 | MIP-Mobile-Node-Address | 1-2 | 0-2 | 1-2 | 0-2 | 1 | 0-1 |
MIP-MN-AAA-SPI | 0 | 0 | 0 | 0 | 0-1 | 0 | MIP-MN-AAA-SPI | 0 | 0 | 0 | 0 | 0-1 | 0 |
MIP-Home-Agent-Address | 0-1 | 0 | 0-1 | 0 | 1 | 0 | MIP-MN-HA-SPI | 0 | 0 | 0 | 0 | 0-1 | 0 |
MIP-Home-Agent-Address | 1-2 | 0-2 | 1-2 | 0-2 | 1 | 0-1 |
MIP-Careof-Address | 0 | 0 | 0 | 0 | 0-1 | 0 | MIP-Careof-Address | 0 | 0 | 0 | 0 | 0-1 | 0 |
MIP-Authenticator | 0 | 0 | 0 | 0 | 0-1 | 0 | MIP-Authenticator | 0 | 0 | 0 | 0 | 0-1 | 0 |
MIP-MAC-Mobility-Data | 0 | 0 | 0 | 0 | 0-1 | 0 | MIP-MAC-Mobility-Data | 0 | 0 | 0 | 0 | 0-1 | 0 |
MIP-MSA-Lifetime | 0 | 0 | 0 | 0 | 0 | 1 | MIP-MSA-Lifetime | 0 | 0 | 0 | 0 | 0 | 1 |
MIP-MN-HA-MSA | 0 | 0-1 | 0 | 0 | 0 | 0-1 | MIP-MN-HA-MSA | 0 | 0-1 | 0 | 0 | 0 | 0-1 |
MIP-Timestamp | 0 | 0 | 0 | 0 | 0-1 | 0-1 | MIP-Timestamp | 0 | 0 | 0 | 0 | 0-1 | 0-1 |
User-Name | 0-1 | 0-1 | 0-1 | 0-1 | 1 | 0-1 | User-Name | 0-1 | 0-1 | 0-1 | 0-1 | 1 | 0-1 |
Called-Station-Id | 0-1 | 0 | 0-1 | 0 | 0-1 | 0 | Called-Station-Id | 0-1 | 0 | 0-1 | 0 | 0-1 | 0 |
QoS-Resources | *0 | *0 | *0 | *0 | *0 | *0 | QoS-Resources | *0 | *0 | *0 | *0 | *0 | *0 |
QoS-Capability | 0-1 | 0 | 0-1 | 0 | 0-1 | 0 | QoS-Capability | 0-1 | 0 | 0-1 | 0 | 0-1 | 0 |
Chargeable-User-Identity | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |
+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+
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 [5].
+-------------+ +-------------+
| Command-Code| | Command-Code|
skipping to change at page 28, line 29 skipping to change at page 30, line 23
Accounting-Output-Packets | 1 | 0-1 | Accounting-Output-Packets | 1 | 0-1 |
Acct-Multi-Session-Id | 1 | 0-1 | Acct-Multi-Session-Id | 1 | 0-1 |
Acct-Session-Time | 1 | 0-1 | Acct-Session-Time | 1 | 0-1 |
MIP6-Feature-Vector | 1 | 0-1 | MIP6-Feature-Vector | 1 | 0-1 |
MIP-Home-Agent-Address | 1 | 0-1 | MIP-Home-Agent-Address | 1 | 0-1 |
MIP-Mobile-Node-Address | 1 | 0-1 | MIP-Mobile-Node-Address | 1 | 0-1 |
Event-Timestamp | 0-1 | 0 | Event-Timestamp | 0-1 | 0 |
MIP-Careof-Address | 0-1 | 0 | MIP-Careof-Address | 0-1 | 0 |
QoS-Capability | *0 | *0 | QoS-Capability | *0 | *0 |
QoS-Resources | *0 | *0 | QoS-Resources | *0 | *0 |
Chargeable-User-Identity | 0-1 | 0 |
-------------------------------------|------+------+ -------------------------------------|------+------+
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
skipping to change at page 29, line 20 skipping to change at page 31, line 11
o MIP-MN-HA-MSA o MIP-MN-HA-MSA
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 [5]. 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
----------------------------------------------+------
DIAMETER_SUCCESS_RELOCATE_HA | TBD
DIAMETER_ERROR_END_TO_END_MIP6_KEY_ENCRYPTION | TBD
9.4. Application Identifier 9.4. Application Identifier
This specification requires IANA to allocate a new value for This specification requires IANA to allocate two new values "Diameter
"Diameter Mobile IPv6" from the Application Identifier namespace Mobile IPv6 IKE" and "Diameter Mobile IPv6 Auth" from the Application
defined in [5]. Identifier namespace defined in [5].
Application Identifier | Value
-----------------------------------+------
Diameter Mobile IPv6 IKE (MIP6I) | TBD
Diameter Mobile IPv6 Auth (MIP6A) | TBD
9.5. Namespaces 9.5. Namespaces
This specification defines a new value to the Mobility Capability This specification defines a new value to the Mobility Capability
registry (see [10]) for use with the MIP6-Feature-Vector AVP: registry (see [10]) for use with the MIP6-Feature-Vector AVP:
Token | Value | Description Token | Value | Description
---------------------------------+----------------------+------------ ---------------------------------+----------------------+------------
RO_SUPPORTED | 0x0000000800000000 | RFC TBD RO_SUPPORTED | 0x0000000800000000 | RFC TBD
USER_TRAFFIC_ENCRYPTION | 0x0000000100000000 | RFC TBD USER_TRAFFIC_ENCRYPTION | 0x0000000100000000 | RFC TBD
VPN_GW_MODE | 0x0000000200000000 | RFC TBD
9.6. Mobile IPv6 Status Codes 9.6. Mobile IPv6 Status Codes
This specification defines a new Mobile IPv6 [1] Status Code value. This specification defines a new Mobile IPv6 [1] Status Code value.
The Status Code must be allocated from the range 0-127: The Status Code must be allocated from the range 0-127:
Status Code | Value | Description Status Code | Value | Description
----------------------------------------+---------------+------------ ----------------------------------------+---------------+------------
ACCEPTED_BUT_NO_ROUTE_OPTIMIZATION | is set to TBD | RFC TBD ACCEPTED_BUT_NO_ROUTE_OPTIMIZATION | is set to TBD | RFC TBD
ACCEPTED_BUT_NO_TRAFFIC_ENCRYPTION | is set to TBD | RFC TBD ACCEPTED_BUT_NO_TRAFFIC_ENCRYPTION | is set to TBD | RFC TBD
skipping to change at page 30, line 11 skipping to change at page 32, line 18
accomplish the split scenario are described in in [2]. Additionally, accomplish the split scenario are described in in [2]. Additionally,
the security considerations of the Diameter Base protocol [5], the security considerations of the Diameter Base protocol [5],
Diameter EAP application [7] are applicable to this document. This Diameter EAP application [7] are applicable to this document. This
document does not introduce new security vulnerabilities. document does not introduce new security vulnerabilities.
11. Acknowledgements 11. Acknowledgements
The authors would like to thank Jari Arkko, Tolga Asversen, Pasi The authors would like to thank Jari Arkko, Tolga Asversen, Pasi
Eronen, Santiago Zapata Hernandez, Anders Kristensen, Avi Lior, John Eronen, Santiago Zapata Hernandez, Anders Kristensen, Avi Lior, John
Loughney, Ahmad Muhanna, Behcet Sarikaya, Basavaraj Patil, Vijay Loughney, Ahmad Muhanna, Behcet Sarikaya, Basavaraj Patil, Vijay
Devarapalli, Lionel Morand, Domagoj Premec and Yoshihiro Ohba for all Devarapalli, Lionel Morand, Domagoj Premec, Semyon Mizikovsky and
the useful discussions. Ahmad Muhanna provided a detailed review of Yoshihiro Ohba for all the useful discussions. Ahmad Muhanna
the document in August 2007. provided a detailed review of the document in August 2007.
We would also like to thank our Area Director, Dan Romascanu, for his We would also like to thank our Area Director, Dan Romascanu, for his
support. support.
Hannes Tschofenig would like to thank the European Commission support Hannes Tschofenig would like to thank the European Commission support
in the co-funding of the ENABLE project, where this work is partly in the co-funding of the ENABLE project, where this work is partly
being developed. being developed.
Julien Bournelle would like to thank GET/INT since he began this work Julien Bournelle would like to thank GET/INT since he began this work
while he was under their employ. while he was under their employ.
Madjid Nakhjiri would like to thank Huawei USA as most of his
contributions to this draft were possible while he was under their
employ.
12. References 12. References
12.1. Normative References 12.1. Normative References
[1] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in [1] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in
IPv6", RFC 3775, June 2004. IPv6", RFC 3775, June 2004.
[2] Giaretta, G., Kempf, J., and V. Devarapalli, "Mobile IPv6 [2] Giaretta, G., Kempf, J., and V. Devarapalli, "Mobile IPv6
Bootstrapping in Split Scenario", RFC 5026, October 2007. Bootstrapping in Split Scenario", RFC 5026, October 2007.
skipping to change at page 31, line 18 skipping to change at page 33, line 28
[8] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol", [8] 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 [9] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter
Network Access Server Application", RFC 4005, August 2005. Network Access Server Application", RFC 4005, August 2005.
[10] Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C., and [10] Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C., and
K. Chowdhury, "Diameter Mobile IPv6: Support for Network Access K. Chowdhury, "Diameter Mobile IPv6: Support for Network Access
Server to Diameter Server Interaction", Server to Diameter Server Interaction",
draft-ietf-dime-mip6-integrated-08 (work in progress), draft-ietf-dime-mip6-integrated-09 (work in progress),
February 2008. May 2008.
[11] Korhonen, J., Tschofenig, H., Arumaithurai, M., and M. Jones, [11] Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones, M., and
"Quality of Service Attributes for Diameter", A. Lior, "Quality of Service Attributes for Diameter",
draft-ietf-dime-qos-attributes-04 (work in progress), draft-ietf-dime-qos-attributes-06 (work in progress), May 2008.
January 2008.
[12] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and P. [12] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and P.
McCann, "Diameter Mobile IPv4 Application", RFC 4004, McCann, "Diameter Mobile IPv4 Application", RFC 4004,
August 2005. August 2005.
[13] Haley, B., Devarapalli, V., Deng, H., and J. Kempf, "Mobility
Header Home Agent Switch Message", RFC 5142, January 2008.
[14] Adrangi, F., Lior, A., Korhonen, J., and J. Loughney,
"Chargeable User Identity", RFC 4372, January 2006.
12.2. Informative References 12.2. Informative References
[13] Patel, A. and G. Giaretta, "Problem Statement for bootstrapping [15] Patel, A. and G. Giaretta, "Problem Statement for bootstrapping
Mobile IPv6 (MIPv6)", RFC 4640, September 2006. Mobile IPv6 (MIPv6)", RFC 4640, September 2006.
[14] Giaretta, G., Guardini, I., Demaria, E., Bournelle, J., and R. [16] Giaretta, G., Guardini, I., Demaria, E., Bournelle, J., and R.
Lopez, "AAA Goals for Mobile IPv6", Lopez, "AAA Goals for Mobile IPv6",
draft-ietf-mext-aaa-ha-goals-00 (work in progress), draft-ietf-mext-aaa-ha-goals-01 (work in progress), May 2008.
December 2007.
[15] Fajardo, V., Asveren, T., Tschofenig, H., McGregor, G., and J. [17] Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and
Routers", draft-ietf-mext-nemo-v4traversal-03 (work in
progress), May 2008.
[18] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury,
"Mobile Node Identifier Option for Mobile IPv6 (MIPv6)",
RFC 4283, November 2005.
[19] Fajardo, V., Asveren, T., Tschofenig, H., McGregor, G., and J.
Loughney, "Diameter Applications Design Guidelines", Loughney, "Diameter Applications Design Guidelines",
draft-ietf-dime-app-design-guide-06 (work in progress), draft-ietf-dime-app-design-guide-06 (work in progress),
January 2008. January 2008.
[16] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury, [20] Korhonen, J., Nilsson, U., and V. Devarapalli, "Service
"Mobile Node Identifier Option for Mobile IPv6 (MIPv6)", Selection for Mobile IPv6", RFC 5149, February 2008.
RFC 4283, November 2005.
Authors' Addresses Authors' Addresses
Jouni Korhonen Jouni Korhonen
TeliaSonera TeliaSonera
P.O.Box 970 P.O.Box 970
Sonera FIN-00051 Sonera FIN-00051
Finland Finland
Email: jouni.korhonen@teliasonera.com Email: jouni.korhonen@teliasonera.com
Hannes Tschofenig Hannes Tschofenig
Nokia Siemens Networks Nokia Siemens Networks
Linnoitustie 6 Linnoitustie 6
Espoo 02600 Espoo 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.com URI: http://www.tschofenig.priv.at
Julien Bournelle Julien Bournelle
Orange Labs Orange Labs
38-4O rue du general Leclerc 38-4O rue du general Leclerc
Issy-Les-Moulineaux 92794 Issy-Les-Moulineaux 92794
France France
Email: julien.bournelle@orange-ftgroup.com Email: julien.bournelle@orange-ftgroup.com
Gerardo Giaretta Gerardo Giaretta
Qualcomm Qualcomm
5775 MoreHouse Dr 5775 MoreHouse Dr
San Diego, CA 92121 San Diego, CA 92121
USA USA
Email: gerardo.giaretta@gmail.com Email: gerardo.giaretta@gmail.com
Madjid Nakhjiri Madjid Nakhjiri
Motorola Motorola
 End of changes. 111 change blocks. 
282 lines changed or deleted 423 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/