draft-ietf-dime-mip6-split-06.txt   draft-ietf-dime-mip6-split-07.txt 
Diameter Maintenance and J. Korhonen, Ed. 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: May 22, 2008 J. Bournelle Expires: August 28, 2008 J. Bournelle
France Telecom R&D Orange Labs
G. Giaretta G. Giaretta
Qualcomm Qualcomm
M. Nakhjiri M. Nakhjiri
Motorola Motorola
November 19, 2007 February 25, 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-06.txt draft-ietf-dime-mip6-split-07.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 May 22, 2008. This Internet-Draft will expire on August 28, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). 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 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. Advertising Application Support . . . . . . . . . . . . . . . 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 . . . 9
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 . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.4. Support for the Mobile IPv6 Authentication Protocol . . . 10 4.4. Support for the Mobile IPv6 Authentication Protocol . . . 10
4.5. Mobile IPv6 Session Management . . . . . . . . . . . . . . 11 4.5. Mobile IPv6 Session Management . . . . . . . . . . . . . . 11
4.5.1. Session-Termination-Request Command . . . . . . . . . 11 4.5.1. Session-Termination-Request . . . . . . . . . . . . . 11
4.5.2. Session-Termination-Answer Command . . . . . . . . . . 11 4.5.2. Session-Termination-Answer . . . . . . . . . . . . . . 11
4.5.3. Abort-Session-Request Command . . . . . . . . . . . . 11 4.5.3. Abort-Session-Request . . . . . . . . . . . . . . . . 11
4.5.4. Abort-Session-Answer Command . . . . . . . . . . . . . 11 4.5.4. Abort-Session-Answer . . . . . . . . . . . . . . . . . 12
4.6. Accounting for Mobile IPv6 services . . . . . . . . . . . 11 4.6. Accounting for Mobile IPv6 services . . . . . . . . . . . 12
4.6.1. Accounting-Request Command . . . . . . . . . . . . . . 12 4.6.1. Accounting-Request . . . . . . . . . . . . . . . . . . 12
4.6.2. Accounting-Answer Command . . . . . . . . . . . . . . 12 4.6.2. Accounting-Answer . . . . . . . . . . . . . . . . . . 13
5. Command Codes . . . . . . . . . . . . . . . . . . . . . . . . 12 5. Command Codes . . . . . . . . . . . . . . . . . . . . . . . . 13
5.1. Command Code for Mobile IPv6 with IKEv2 and EAP . . . . . 12 5.1. Command Code for Mobile IPv6 with IKEv2 and EAP . . . . . 13
5.1.1. Diameter-EAP-Request (DER) . . . . . . . . . . . . . . 13 5.1.1. Diameter-EAP-Request . . . . . . . . . . . . . . . . . 13
5.1.2. Diameter-EAP-Answer (DEA) . . . . . . . . . . . . . . 13 5.1.2. Diameter-EAP-Answer . . . . . . . . . . . . . . . . . 14
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 . . . . . . . . 14 Certificate- and PSK-based Authentication . . . . . . . . 15
5.2.1. AA-Request (AAR) . . . . . . . . . . . . . . . . . . . 14 5.2.1. AA-Request . . . . . . . . . . . . . . . . . . . . . . 15
5.2.2. AA-Answer (AAA) . . . . . . . . . . . . . . . . . . . 15 5.2.2. AA-Answer . . . . . . . . . . . . . . . . . . . . . . 16
5.3. Command Codes for MIPv6 Authentication Protocol Support . 16 5.3. Command Codes for MIPv6 Authentication Protocol Support . 17
5.3.1. MIP6-Request-Message . . . . . . . . . . . . . . . . . 16 5.3.1. MIP6-Request-Message . . . . . . . . . . . . . . . . . 17
5.3.2. MIP6-Answer-Message . . . . . . . . . . . . . . . . . 17 5.3.2. MIP6-Answer-Message . . . . . . . . . . . . . . . . . 18
6. AVPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6. AVPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.1. User-Name AVP . . . . . . . . . . . . . . . . . . . . . . 20 6.1. User-Name AVP . . . . . . . . . . . . . . . . . . . . . . 22
6.2. MIP-MN-AAA-SPI AVP . . . . . . . . . . . . . . . . . . . . 21 6.2. Called-Station-Id AVP . . . . . . . . . . . . . . . . . . 22
6.3. MIP-MN-to-HA-SPI AVP . . . . . . . . . . . . . . . . . . . 21 6.3. MIP-MN-AAA-SPI AVP . . . . . . . . . . . . . . . . . . . . 22
6.4. MIP-Mobile-Node-Address AVP . . . . . . . . . . . . . . . 21 6.4. MIP-MN-HA-SPI AVP . . . . . . . . . . . . . . . . . . . . 22
6.5. MIP-Home-Agent-Address AVP . . . . . . . . . . . . . . . . 21 6.5. MIP-Mobile-Node-Address AVP . . . . . . . . . . . . . . . 22
6.6. MIP-Careof-Address AVP . . . . . . . . . . . . . . . . . . 21 6.6. MIP-Home-Agent-Address AVP . . . . . . . . . . . . . . . . 23
6.7. MIP-Authenticator AVP . . . . . . . . . . . . . . . . . . 22 6.7. MIP-Careof-Address AVP . . . . . . . . . . . . . . . . . . 23
6.8. MIP-MAC-Mobility-Data AVP . . . . . . . . . . . . . . . . 22 6.8. MIP-Authenticator AVP . . . . . . . . . . . . . . . . . . 23
6.9. MIP-Session-Key AVP . . . . . . . . . . . . . . . . . . . 22 6.9. MIP-MAC-Mobility-Data AVP . . . . . . . . . . . . . . . . 23
6.10. MIP-MSA-Lifetime AVP . . . . . . . . . . . . . . . . . . . 22 6.10. MIP-Session-Key AVP . . . . . . . . . . . . . . . . . . . 23
6.11. MIP-MN-to-HA-MSA AVP . . . . . . . . . . . . . . . . . . . 22 6.11. MIP-MSA-Lifetime AVP . . . . . . . . . . . . . . . . . . . 23
6.12. MIP-Algorithm-Type AVP . . . . . . . . . . . . . . . . . . 23 6.12. MIP-MN-HA-MSA AVP . . . . . . . . . . . . . . . . . . . . 24
6.13. MIP-Replay-Mode AVP . . . . . . . . . . . . . . . . . . . 23 6.13. MIP-Algorithm-Type AVP . . . . . . . . . . . . . . . . . . 24
6.14. MIP-nonce AVP . . . . . . . . . . . . . . . . . . . . . . 23 6.14. MIP-Replay-Mode AVP . . . . . . . . . . . . . . . . . . . 24
6.15. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . . . 23 6.15. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . . . 24
6.16. MIP-Timestamp AVP . . . . . . . . . . . . . . . . . . . . 23 6.16. MIP-Timestamp AVP . . . . . . . . . . . . . . . . . . . . 25
6.17. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 24 6.17. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 25
6.18. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 24 6.18. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 25
6.19. Accounting AVPs . . . . . . . . . . . . . . . . . . . . . 24 6.19. Coupled Accounting Model Accounting AVPs . . . . . . . . . 25
7. Result-Code AVP Values . . . . . . . . . . . . . . . . . . . . 25 7. Result-Code AVP Values . . . . . . . . . . . . . . . . . . . . 26
7.1. Transient Failures . . . . . . . . . . . . . . . . . . . . 25 7.1. Permanent Failures . . . . . . . . . . . . . . . . . . . . 26
7.2. Permanent Failures . . . . . . . . . . . . . . . . . . . . 25 8. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 27
8. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 26 8.1. AAR, AAA, DER, DEA, MRM and MAM AVP/Command-Code Table . . 27
8.1. AAR, AAA, DER, DEA, MRM and MAM AVP/Command-Code Table . . 26 8.2. Coupled Accounting Model AVP Table . . . . . . . . . . . . 28
8.2. Accounting AVP Table . . . . . . . . . . . . . . . . . . . 27 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 9.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 28
9.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 27 9.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . 28
9.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . 27 9.3. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 29
9.3. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 28 9.4. Application Identifier . . . . . . . . . . . . . . . . . . 29
9.4. Application Identifier . . . . . . . . . . . . . . . . . . 28 9.5. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 29
9.5. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 28 9.6. Mobile IPv6 Status Codes . . . . . . . . . . . . . . . . . 29
9.6. Mobile IPv6 Status Codes . . . . . . . . . . . . . . . . . 28 10. Security Considerations . . . . . . . . . . . . . . . . . . . 29
10. Security Considerations . . . . . . . . . . . . . . . . . . . 28 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 30
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 29 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 30
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29 12.1. Normative References . . . . . . . . . . . . . . . . . . . 30
12.1. Normative References . . . . . . . . . . . . . . . . . . . 29 12.2. Informative References . . . . . . . . . . . . . . . . . . 31
12.2. Informative References . . . . . . . . . . . . . . . . . . 30 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30 Intellectual Property and Copyright Statements . . . . . . . . . . 33
Intellectual Property and Copyright Statements . . . . . . . . . . 32
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 enable
its reachability and mobility, when away from home. The registration its reachability and mobility, when away from home. The registration
process itself requires establishment of IPsec security associations process itself requires establishment of IPSec security associations
(SA) and cryptographic material between the MN and HA. Providing the (SA) and cryptographic material between the MN and HA. Providing the
collection of home address, HA address and keying material is collection of home address, HA address and keying material is
generally referred to as the Mobile IPv6 bootstrapping problem [13]. generally referred to as the Mobile IPv6 bootstrapping problem [13].
The purpose of this specification is to provide Diameter support for The purpose of this specification is to provide Diameter support for
the interaction between the HA and the AAA server required to solve the interaction between the HA and the AAA server required to solve
the bootstrapping problem in the split scenario [2] in a manner that the bootstrapping problem in the split scenario [2] in a manner that
satisfies the requirements defined in [14]. satisfies the requirements defined in [14].
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
skipping to change at page 6, line 30 skipping to change at page 6, line 30
| (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 protected using
two different mechanisms, namely using IPsec and via the MIPv6 two different mechanisms, namely using IPSec and via the MIPv6
Authentication Protocol [3]. The important aspect is, however, that Authentication Protocol [3]. The important aspect is, however, that
for these two approaches several different authentication and key for these two approaches several different authentication and key
exchange solutions are available. To establish IPsec security exchange solutions are available. To establish IPSec security
associations, protecting of Mobile IPv6 signaling messages IKEv2 is associations, protecting of Mobile IPv6 signaling messages IKEv2 is
used [4]. IKEv2 supports EAP-based authentication, certificates and used [4]. IKEv2 supports EAP-based authentication, certificates and
pre-shared secrets. For protecting using the MIPv6 Authentication pre-shared secrets. For protecting using the MIPv6 Authentication
Protocol [3] a mechanism has been designed that is very similar to Protocol [3] a mechanism has been designed that is very similar to
the one used by Mobile IPv4. 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:
skipping to change at page 8, line 30 skipping to change at page 8, line 30
| | DEA (EAP-Request) (5) | | | DEA (EAP-Request) (5) |
| HDR, SK{IDr, [CERT,] AUTH, EAP} |<-------------------------| | HDR, SK{IDr, [CERT,] AUTH, EAP} |<-------------------------|
|<------------------------------- | | |<------------------------------- | |
| | | | | |
| HDR, SK{EAP} | | | HDR, SK{EAP} | |
|-------------------------------->| DER (EAP-Response) | |-------------------------------->| DER (EAP-Response) |
| |------------------------->| | |------------------------->|
| | | | | |
| | DEA (EAP-Request) | | | DEA (EAP-Request) |
| HDR, SK{EAP-Request} |<-------------------------| | HDR, SK{EAP-Request} |<-------------------------|
|<------------------------------- | | |<--------------------------------| |
| | | | | |
| HDR, SK{EAP-Response} | | | HDR, SK{EAP-Response} | |
|-------------------------------->| DER (EAP-Response) | |-------------------------------->| DER (EAP-Response) |
| |------------------------->| | |------------------------->|
| ... | ... | | ... | ... |
| | | | | |
| | DEA (EAP-Success) | | | DEA (EAP-Success) |
| |<-------------------------| | |<-------------------------|
| HDR, SK{EAP-Success} | | | HDR, SK{EAP-Success} | |
|<------------------------------- | | |<--------------------------------| |
| | | | | |
| 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 with IKEv2 and EAP Figure 2: Mobile IPv6 bootstrapping using IKEv2 and EAP
The MN and the HA start the interaction with an IKE_SA_INIT exchange. The MN and the HA start the interaction with an IKE_SA_INIT exchange.
In this phase cryptographic algorithms are negotiated, nonces and In this phase cryptographic algorithms are negotiated, nonces and
Diffie-Hellman parameters are exchanged. Message (3) starts the Diffie-Hellman parameters are exchanged. Message (3) starts the
IKE_AUTH phase. This second phase authenticates the previous IKE_AUTH phase. This second phase authenticates the previous
messages, exchanges identities and certificates and establishes the messages, exchanges identities and certificates and establishes the
first CHILD_SA. It is used to mutually authenticate the MN (acting first CHILD_SA. It is used to mutually authenticate the MN (acting
as an IKEv2 Initiator) and the HA (acting as an IKEv2 Responder). as an IKEv2 Initiator) and the HA (acting as an IKEv2 Responder).
The identity of the user/MN is provided in the IDi field. The MN The identity of the user/MN is provided in the IDi field. The MN
skipping to change at page 9, line 35 skipping to change at page 9, line 35
Diameter server selects the EAP method and replies with the DEA Diameter server selects the EAP method and replies with the DEA
Message. Depending on the type of EAP method chosen, a number of DER Message. Depending on the type of EAP method chosen, a number of DER
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 scenario, 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 MIP6 service or for
IPsec VPN access. The IKEv2 responder may A network operator needs IPSec VPN access. The IKEv2 responder may A network operator needs
to be aware of this limitation. to be aware of this limitation.
Eventually, when the HA receives a Binding Update (BU), the HA
authenticates and authorizes the MN. It is RECOMMENDED that the HA
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 Home Agent to populate the User- This identity is then used by the Home Agent to populate the User-
Name AVP in the succeeding AA-Request message. Further PKI-related Name AVP in the succeeding AA-Request message. Further PKI-related
procedures such as certificate revocation checking are out of scope procedures such as certificate revocation checking are out of scope
of this 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 used to authorize the MN for the Diameter NASREQ application [9] is re-used to authorize the MN for
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 Home Agent to populate the User-Name AVP in
the succeeding AA-Request message. the succeeding AA-Request message.
4.4. Support for the Mobile IPv6 Authentication Protocol 4.4. Support for the Mobile IPv6 Authentication Protocol
Figure 3 describes the sequence of messages sent and received between Figure 3 shows the message sequence between the MN, the HA and the
the MN, the HA and the Diameter server during the registration when Diameter server during the registration when MIPv6 Authentication
MIPv6 Authentication Protocol is used. Binding Update (BU) and Protocol is used. BU and Binding Acknowledgement (BA) messages are
Binding Acknowledgement (BA) messages are used in the registration used in the binding registration process. This exchange triggers the
process. This exchange triggers the Diameter interaction. Diameter interaction.
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 [16]) to
identify itself. identify itself.
Receiving the BU at the HA initiates a MIP6-Request-Message to the Receiving the BU at the HA initiates a MIP6-Request-Message to the
Diameter server, which in turn responds with a MIP6-Answer-Message. Diameter server, which in turn responds with a MIP6-Answer-Message.
The Home Agent also provides the assigned Home Address to the The Home Agent also provides the assigned Home Address to the
Diameter server in the MIP-Mobile-Node-Address AVP. Diameter server in the MIP-Mobile-Node-Address AVP.
The procedure described here for the Mobile IPv6 Authentication
Protocol is only needed for the initial BU received by the HA. When
the HA receives subsequent BUs, they are processed locally in the HA.
It is RECOMMENDED that the HA sends an accounting request message
every time it receives a Binding Update.
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) | |
| | | | | |
skipping to change at page 11, line 13 skipping to change at page 11, line 32
Figure 3: MIPv6 Bootstrapping using the MIPv6 Authentication Protocol Figure 3: MIPv6 Bootstrapping using the MIPv6 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 Command 4.5.1. Session-Termination-Request
The Session-Termination-Request (STR) message [5] is sent by the HA The Session-Termination-Request (STR) message [5] is sent by the HA
to inform the Diameter server that an authorized session is being to inform the Diameter server that an authorized session is being
terminated. terminated.
4.5.2. Session-Termination-Answer Command 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 Command 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 [14].
4.5.4. Abort-Session-Answer Command 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].
skipping to change at page 12, line 24 skipping to change at page 12, line 47
of the Mobile IPv6 application. This means that accounting of the Mobile IPv6 application. This means that accounting
messages will be routed like any other Mobile IPv6 application messages will be routed like any other Mobile IPv6 application
messages. This requires the Diameter server in charge of Mobile messages. This requires the Diameter server in charge of Mobile
IPv6 application to handle the accounting records (e.g., sends IPv6 application to handle the accounting records (e.g., sends
them to a proper accounting server). them to a proper accounting server).
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 ID (value of 3) for accounting messages.
4.6.1. Accounting-Request Command 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 Command 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 usage of Mobile IPv6 with IKEv2 and EAP this document re-uses the
Diameter EAP application [7] commands. The following commands are Diameter EAP application [7] commands. The following commands are
used to carry MIPv6 related bootstrapping AVPs. used to carry MIPv6 related bootstrapping AVPs.
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 (TBD)
Diameter-EAP-Answer DEA 268 RFC 4072 Diameter Mobile IPv6 (TBD) Diameter-EAP-Answer DEA 268 RFC 4072 Diameter Mobile IPv6 (TBD)
Figure 4: Command Codes Figure 4: Command Codes
5.1.1. Diameter-EAP-Request (DER) 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
Application ID [TO BE ASSIGNED TO IANA]. Application ID [TO BE ASSIGNED TO IANA].
<Diameter-EAP-Request> ::= < Diameter Header: 268, REQ, PXY > <Diameter-EAP-Request> ::= < Diameter Header: 268, REQ, PXY >
skipping to change at page 13, line 28 skipping to change at page 14, line 18
{ 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]
...
{ EAP-Payload } { EAP-Payload }
... ...
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
{ MIP-Home-Agent-Address } { MIP-Home-Agent-Address }
{ MIP-Careof-Address }
{ MIP-Mobile-Node-Address } { MIP-Mobile-Node-Address }
[ QoS-Capability ] [ QoS-Capability ]
* [ QoS-Resources ] * [ QoS-Resources ]
... ...
* [ AVP ] * [ AVP ]
5.1.2. Diameter-EAP-Answer (DEA) 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). If the Mobile IPv6 authentication procedure was successful
then the response MAY include any set of bootstrapping AVPs. then the response MAY include any set of bootstrapping AVPs.
The DEA message format is the same as defined in [7]. The The DEA message format is the same as defined in [7]. 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 Application-Id [TO BE ASSIGNED BY IANA].
skipping to change at page 14, line 36 skipping to change at page 15, line 36
following commands are used to carry MIPv6 related bootstrapping following commands are used to carry MIPv6 related bootstrapping
AVPs. 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 (TBD)
AA-Answer AAA 265 RFC 4005 Diameter Mobile IPv6 (TBD) AA-Answer AAA 265 RFC 4005 Diameter Mobile IPv6 (TBD)
Figure 7: Command Codes Figure 7: Command Codes
5.2.1. AA-Request (AAR) 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 Application
ID [TO BE ASSIGNED TO IANA]. ID [TO BE ASSIGNED TO IANA].
<AA-Request> ::= < Diameter Header: 265, REQ, PXY > <AA-Request> ::= < Diameter Header: 265, REQ, PXY >
skipping to change at page 15, line 19 skipping to change at page 16, line 19
{ 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]
...
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
{ MIP-Home-Agent-Address } { MIP-Home-Agent-Address }
{ MIP-Careof-Address }
{ MIP-Mobile-Node-Address } { MIP-Mobile-Node-Address }
...
[ QoS-Capability ] [ QoS-Capability ]
* [ QoS-Resources ] * [ QoS-Resources ]
... ...
* [ AVP ] * [ AVP ]
5.2.2. AA-Answer (AAA) 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 Application-Id [TO BE ASSIGNED BY IANA].
skipping to change at page 16, line 18 skipping to change at page 17, line 18
{ 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 ] [ MIP-Mobile-Node-Address ]
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
[ MIP-MN-HA-MSA ]
* [ QoS-Resources ] * [ QoS-Resources ]
... ...
* [ AVP ] * [ AVP ]
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 SHOULD NOT be user's long term secret and it is
RECOMMENDED that a short-term keying material specifically created
for this purpose is used instead.
5.3. Command Codes for MIPv6 Authentication Protocol Support 5.3. Command Codes for MIPv6 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. MIPv6 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 (TBD)
MIP6-Answer-Message MAM TBD 5.3.2 Diameter Mobile IPv6 (TBD) MIP6-Answer-Message MAM TBD 5.3.2 Diameter Mobile IPv6 (TBD)
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. The HA uses information authentication and authorization of a MN.
found in the Binding Update to construct the following AVPs, to be
included as part of the MRM:
o Home Address (MIP-Mobile-Node-Address AVP) Although the HA provides the Diameter server with a replay protection
o Mobile Node NAI (User-Name AVP [5]) related information, the HA is responsible for the replay protection.
o MN-AAA Authentication Option (MIP-MN-AAA-Auth AVP)
o Care-of Address (MIP-Careof-Address AVP)
o Mobility message replay protection Option using timestamps (MIP-
Timestamp AVP)
The message format is shown below. The message format is shown below.
<MIP6-Request-Message> ::= < Diameter Header: XXX, REQ, PXY > <MIP6-Request-Message> ::= < Diameter Header: XXX, REQ, PXY >
< Session-ID > < Session-ID >
{ Auth-Application-Id } { Auth-Application-Id }
{ User-Name } { User-Name }
{ Destination-Realm } { Destination-Realm }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
skipping to change at page 17, line 24 skipping to change at page 18, line 24
[ 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 ]
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
[ MIP-MN-AAA-SPI ] [ MIP-MN-AAA-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 ]
[ Authorization-Lifetime ] [ Authorization-Lifetime ]
[ Auth-Session-State ] [ Auth-Session-State ]
* [ Proxy-Info ] * [ Proxy-Info ]
* [ Route-Record ] * [ Route-Record ]
skipping to change at page 18, line 22 skipping to change at page 19, line 22
[ User-Name ] [ User-Name ]
[ Authorization-Lifetime ] [ Authorization-Lifetime ]
[ 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-Session-Key ] [ MIP-MN-HA-MSA ]
[ MIP-MSA-Lifetime ]
[ MIP-MN-to-HA-MSA ]
* [ QoS-Resources ] * [ QoS-Resources ]
[ Origin-State-Id ] [ Origin-State-Id ]
* [ Proxy-Info ] * [ Proxy-Info ]
* [ AVP ] * [ AVP ]
The QoS-Resources AVP is defined in [10].
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
existing semantics of those AVPs. existing semantics of those AVPs.
+--------------------------+ +--------------------------+
| AVP Flag rules | | AVP Flag rules |
+----+-----+----+-----+----+ +----+-----+----+-----+----+
skipping to change at page 19, line 20 skipping to change at page 20, line 20
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP6-Feature- TBD Note 1 Unsigned64 | M | P | | V | Y | |MIP6-Feature- TBD Note 1 Unsigned64 | M | P | | V | Y |
| Vector | | | | | | | Vector | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-Mobile- | M | P | | V | Y | |MIP-Mobile- | M | P | | V | Y |
|Node-Address 334 RFC4004 Address | | | | | | |Node-Address 334 RFC4004 Address | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|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 |
+-----------------------------------------+----+-----+----+-----+----+
|Called- 30 RFC4005 UTF8String | M | P | | V | Y |
| Station-Id | | | | | |
+-----------------------------------------+----+-----+----+-----+----+
|QoS-Capability TBD Note 2 Grouped | | P | | M,V | Y | |QoS-Capability TBD Note 2 Grouped | | P | | M,V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|QoS-Resources TBD Note 2 Grouped | | P | | M,V | Y | |QoS-Resources TBD Note 2 Grouped | | P | | M,V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-MN-HA-MSA TBD 6.12. Grouped | M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+
AVPs for Mobile IPv6 with IKEv2 AVPs for Mobile IPv6 with IKEv2
Note 1: The MIP6-Feature-Vector is defined in Section 4.7.4 of [11]. 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 [10]. 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 |
+-----------------------------------------+----+-----+----+-----+----+
|MIP-MN-AAA-SPI 341 RFC4004 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-MN-AAA-SPI 341 RFC4004 Unsigned32 | M | P | | V | Y | |MIP-Careof- TBD 6.7 Address | M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+
|MIP-MN-to- TBD 6.3 Unsigned32 | M | P | | V | Y |
| HA-SPI | | | | | |
+-----------------------------------------+----+-----+----+-----+----+
|MIP-Careof- TBD 6.6 Address | M | P | | V | Y |
| Address | | | | | | | Address | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP- TBD 6.7 OctetString| M | P | | V | Y | |MIP- TBD 6.8 OctetString| M | P | | V | Y |
| Authenticator | | | | | | | Authenticator | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-MAC- TBD 6.8 OctetString| M | P | | V | Y | |MIP-MAC- TBD 6.9 OctetString| M | P | | V | Y |
| Mobility-Data | | | | | | | Mobility-Data | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-Session-Key 343 6.9 OctetString| M | P | | V | Y | |MIP-Session-Key 343 6.10 OctetString| M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+
|MIP-Timestamp TBD 6.16 Time | 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-to- 331 RFC4004 Grouped | M | P | | V | Y | |MIP-MN-HA-MSA TBD 6.12 Grouped | M | P | | V | Y |
| HA-MSA | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-Algorithm- 345 6.12 Enumerated | M | P | | V | Y | |MIP-Algorithm- 345 6.13 Enumerated | M | P | | V | Y |
| Type | | | | | | | Type | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-Replay-Mode 346 6.13 Enumerated | M | P | | V | Y | |MIP-Replay-Mode 346 6.14 Enumerated | M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-Nonce 335 6.14 OctetString| 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 | | P | | M,V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|QoS-Resources TBD Note 2 Grouped | | P | | M,V | Y | |QoS-Resources TBD Note 2 Grouped | | P | | M,V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
AVPs for the Mobile IPv6 Authentication Protocol AVPs for the Mobile IPv6 Authentication Protocol
Note 1: The MIP6-Feature-Vector is defined in Section 4.7.4 of [11]. 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 [10]. Sections 4.1 and 4.3 of [11].
6.1. User-Name AVP 6.1. User-Name AVP
The User-Name AVP (AVP Code 2) 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_SA_INIT message. the IKEv2 IDi payload included in the IKE_AUTH message sent by the
IKE initiator.
6.2. MIP-MN-AAA-SPI AVP 6.2. Called-Station-Id AVP
The Called-Station-Id AVP (AVP Code 30) is of type UTF8String and
contains the string extracted from the IKEv2 IDr payload, if
available in the IKE_AUTH message sent by the IKE initiator.
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.3. MIP-MN-to-HA-SPI AVP 6.4. MIP-MN-HA-SPI AVP
The MIP-MN-to-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 provided by the Diameter server for the Mobile
IPv6 MN-HA Authentication Option. IPv6 MN-HA Authentication Option.
This AVP is re-used from [12] that introduces the AVP but erroneously 6.5. MIP-Mobile-Node-Address AVP
does not define the AVP Code.
6.4. 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 Home Address of the Mobile
Node. Node.
If the MIP-Mobile-Node-Address AVP contains unspecified IPv6 address If the MIP-Mobile-Node-Address AVP contains unspecified IPv6 address
(0::0) in a request message, then the Home Agent expects the Diameter (0::0) in a request message, then the Home Agent expects the Diameter
server to assign the Home Address in a subsequent reply message. In server to assign the Home Address in a subsequent reply message. In
case the Diameter server assigns only a Home Network Prefix to the case the Diameter server assigns only a Home Network Prefix to the
Mobile Node the lower 64 bits of the MIP-Mobile-Node-Address AVP Mobile Node the lower 64 bits of the MIP-Mobile-Node-Address AVP
provided address MUST be set to zero. provided address MUST be set to zero.
This AVP is re-used from [12]. This AVP is re-used from [12].
6.5. 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 address of the Home Agent. The Home Agent address
is the same as in the received BU message that triggered the is the same as in the received BU message that triggered the
authentication and authorization procedure towards the Diameter authentication and authorization procedure towards the Diameter
server. This AVP is re-used from [12]. server. This AVP is re-used from [12].
6.6. 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 Home Agent
extracts this IP address from the received BU message. extracts this IP address from the received BU message.
6.7. 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
Home Agent extracts this data from the MN-AAA Mobility Message Home Agent extracts this data from the MN-AAA Mobility Message
Authentication Option included in the received BU message. Authentication Option included in the received BU message.
6.8. 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.9. MIP-Session-Key AVP 6.10. MIP-Session-Key AVP
The AVP (AVP Code 343) is of type OctetString and contains the MN-HA The MIP-Session-Key AVP (AVP Code 343) is of type OctetString and
shared secret (i.e., the session key) for the associated Mobile IPv6 contains the MN-HA shared secret (i.e., the session key) for the
MH-HA authentication option. When the Diameter server computes the associated Mobile IPv6 MH-HA authentication option. When the
session key it is placed in this AVP. Diameter server computes the session key it is placed in this AVP.
The MIP-Session-Key AVP may also be used to convey a pre-shared
secret when IKEv2 is used with PSK-based initiator authentication.
This AVP is re-used from [12]. This AVP is re-used from [12].
6.10. MIP-MSA-Lifetime AVP 6.11. MIP-MSA-Lifetime AVP
The AVP (AVP Code 367) is of type Unsigned32 and represents the The MIP-MSA-Lifetime AVP (AVP Code 367) is of type Unsigned32 and
period of time (in seconds) for which the session key (see represents the period of time (in seconds) for which the session key
Section 6.9) or nonce (see Section 6.14) is valid. The associated (see Section 6.10) is valid. The associated session key MUST NOT be
session key or nonce 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.11. MIP-MN-to-HA-MSA AVP 6.12. MIP-MN-HA-MSA AVP
The AVP (AVP Code 331) is of type Grouped and contains the session The MIP-MN-HA-MSA AVP (AVP Code TBD) is of type Grouped and contains
related information for use with the MIPv6 Authentication Protocol. the session related information for use with the MIPv6 Authentication
Protocol.
MIP-MN-to-HA-MSA ::= < AVP Header: 331 > MIP-MN-HA-MSA ::= < AVP Header: TBD >
{ MIP-Session-Key } { MIP-Session-Key }
[ MIP-MN-to-HA-SPI ] { MIP-MSA-Lifetime }
[ MIP-MN-HA-SPI ]
[ MIP-Algorithm-Type ] [ MIP-Algorithm-Type ]
[ MIP-Replay-Mode ] [ MIP-Replay-Mode ]
[ MIP-nonce ]
* [ AVP ] * [ AVP ]
This AVP is re-used from [12]. 6.13. MIP-Algorithm-Type AVP
6.12. MIP-Algorithm-Type AVP
The AVP (AVP Code 345) is of type Enumerated and contains Algorithm The MIP-Algorithm-Type AVP (AVP Code 345) is of type Enumerated and
identifier for the associated Mobile IPv6 MN-HA Authentication contains Algorithm identifier for the associated Mobile IPv6 MN-HA
Option. The Diameter server selects the algorithm type. Existing Authentication Option. The Diameter server selects the algorithm
algorithm types are defined in RFC 4004 that also fulfill current RFC type. Existing algorithm types are defined in RFC 4004 that also
4285 requirements. This AVP is re-used from [12]. fulfill current RFC 4285 requirements.
6.13. MIP-Replay-Mode AVP This AVP is re-used from [12].
The AVP (AVP Code 346) is of type Enumerated and contains the replay 6.14. MIP-Replay-Mode AVP
mode the Home Agent for authenticating the mobile node. The replay
modes, defined in RFC 4004 [12], are supported. This AVP is re-used
from [12].
6.14. MIP-nonce AVP The MIP-Replay-Mode AVP (AVP Code 346) is of type Enumerated and
contains the replay mode the Home Agent for authenticating the mobile
node. The replay modes, defined in RFC 4004 [12], are supported.
The AVP (AVP Code 335) is of type OctetString and contains the nonce This AVP is re-used from [12].
sent to the Mobile Node. This AVP is re-used from [12].
6.15. MIP6-Feature-Vector AVP 6.15. MIP6-Feature-Vector AVP
This AVP is defined in [11]. 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 Home Agent sets this
bit, it indicates support for the route optimization. If this bit bit, it indicates support for the route optimization. If this bit
is unset in the returned Mobility-Capability AVP, the HAAA does is unset in the returned Mobility-Capability AVP, the AAAH does
not authorize route optimization for the MN. not authorize route optimization for the MN.
In a case the Home Agent or the HAAA cannot authorize the use of In a case the Home Agent or the AAAH cannot authorize the use of
route optimization then the Home Agent SHOULD send a Binding route optimization then the Home Agent SHOULD send a Binding
Acknowledgement with a Status Code set to Acknowledgement with a Status Code set to
ACCEPTED_BUT_NO_ROUTE_OPTIMIZATION (status code TBD). This Status ACCEPTED_BUT_NO_ROUTE_OPTIMIZATION (status code TBD). This Status
Code indicates that the binding registration succeeded but the Code indicates that the binding registration succeeded but the
Home Agent will fail all possible subsequent route optimization Home Agent will fail all possible subsequent route optimization
attempts because of subscription or operator policy. attempts because of subscription or operator policy.
USER_TRAFFIC_ENCRYPTION (0x0000000100000000)
User plane traffic encryption is supported. When the Home Agent
sets this bit, it indicates support for the user plane traffic
encryption between the MN and the Home Agent. If this bit is
unset in the returned Mobility-Capability AVP, the AAAH does not
authorize user plane traffic encryption for the MN because of
subscription or operator policy.
In the case the AAAH cannot authorize the use of route
optimization then the Home Agent SHOULD send a Binding
Acknowledgement with a Status Code set to
ACCEPTED_BUT_NO_TRAFFIC_ENCRYPTION (status code TBD). This Status
Code indicates that the binding registration succeeded but the
Home Agent will silently discard all encrypted user plane packets
sent by the MN to the Home Agent.
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 Home Agent extracts this value from the
received BU message, if available. received BU message, if available.
The support for replay protection is an optional feature in [3].
When the Diameter server checks the timestamp provided by the MN via
the HA and recognizes a clock-drift (outside a locally defined replay
protection window) then it MUST initiate the re-synchronization
procedure by returning a MIP6-Answer-Message with Result-Code set to
MIP6-TIMESTAMP-MISMATCH and attaches the MIP-Timestamp AVP including
it's current time back to the HA.
6.17. QoS-Capability AVP 6.17. QoS-Capability AVP
The QoS-Capability AVP is defined in [10] 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 [10] and provides QoS and packet The QoS-Resources AVP is defined in [11] and provides QoS and packet
filtering capabilities. filtering capabilities.
6.19. Accounting AVPs 6.19. Coupled Accounting Model Accounting AVPs
This document reuses the accounting AVPs defined in Diameter Mobile
IPv4 application [12], namely:
o Accounting-Input-Octets
Number of octets in IP packets received from the mobile node.
o Accounting-Output-Octets:
Number of octets in IP packets sent by the mobile node.
o Accounting-Input-Packets:
Number of IP packets received from the mobile node.
o Accounting-Output-Packets: Diameter Mobile IPv6 application is used in the case of the coupled
account model. Diameter Mobile IPv4 application [12] accounting AVPs
are reused in this document. The following AVPs MUST be included in
the accounting request message:
Number of IP packets sent by the mobile node. o Accounting-Input-Octets: Number of octets in IP packets received
from the mobile node.
o Accounting-Output-Octets: Number of octets in IP packets sent by
the mobile node
o Accounting-Input-Packets: Number of IP packets received from the
mobile node.
o Accounting-Output-Packets: Number of IP packets sent by the mobile
node.
o Acct-Multi-Session-Id: Used to link together multiple related
accounting sessions, where each session would have a unique
Session-Id, but the same Acct-Multi-Session-Id AVP.
o Acct-Session-Time: Indicates the length of the current session in
seconds.
o MIP6-Feature-Vector: The supported features for this mobility
service session.
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.
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: o QoS-Resources: Assigned QoS resources for the mobile node.
o QoS-Capability: The QoS capability related to the assigned QoS-
Assigned QoS resources for the mobile node. Resources.
o MIP-Careof-Address: The current Care-of Address of the mobile
o QoS-Capability: node.
The QoS capability related to the assigned QoS-Resources.
o MIP-Mobile-Node-Address:
The Home Address of the mobile node.
o MIP-Careof-Address:
The current Care-of Address of the mobile node.
o MIP-Home-Agent-Address:
The current home agent of the mobile 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. Transient Failures 7.1. Permanent Failures
Errors in the transient failures category are used to inform a peer
that the request could not be satisfied at the time it was received,
but that it may be able to satisfy the request in the future.
MIP6-TIMESTAMP-MISMATCH (Status Code TBD)
This error code is used by the home agent to indicate to the HA
that the timestamp value provided as part of the MN-AAA option has
an unacceptable clock-drift.
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 26, line 40 skipping to change at page 27, line 40
+-----------------------------------+ +-----------------------------------+
| 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 | 0-1 | 1 | 0-1 | 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-Home-Agent-Address | 0-1 | 0 | 0-1 | 0 | 1 | 0 |
MIP-Careof-Address | 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-to-HA-MSA | 0 | 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 |
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 |
+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+
8.2. Accounting 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|
|------+------+ |------+------+
Attribute Name | ACR | ACA | Attribute Name | ACR | ACA |
-------------------------------------|------+------+ -------------------------------------|------+------+
Accounting-Input-Octets | 1 | 0-1 | Accounting-Input-Octets | 1 | 0-1 |
Accounting-Input-Packets | 1 | 0-1 | Accounting-Input-Packets | 1 | 0-1 |
Accounting-Output-Octets | 1 | 0-1 | Accounting-Output-Octets | 1 | 0-1 |
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 |
QoS-Capability | *0 | *0 | QoS-Capability | *0 | *0 |
QoS-Resources | *0 | *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 28, line 6 skipping to change at page 29, line 9
9.2. AVP Codes 9.2. AVP Codes
This specification requires IANA to register the following new AVPs This specification requires IANA to register the following new AVPs
from the AVP Code namespace defined in [5]. from the AVP Code namespace defined in [5].
o MIP-Careof-Address o MIP-Careof-Address
o MIP-Authenticator o MIP-Authenticator
o MIP-MAC-Mobility-Data o MIP-MAC-Mobility-Data
o MIP-Timestamp o MIP-Timestamp
o MIP-MN-to-HA-SPI o MIP-MN-HA-SPI
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.
9.4. Application Identifier 9.4. Application Identifier
This specification requires IANA to allocate a new value for This specification requires IANA to allocate a new value for
"Diameter Mobile IPv6" from the Application Identifier namespace "Diameter Mobile IPv6" from the Application Identifier namespace
defined in [5]. defined in [5].
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 [11]) 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
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
10. Security Considerations 10. Security Considerations
The security considerations for the Diameter interaction required to The security considerations for the Diameter interaction required to
accomplish the split scenario are described in in [2]. Additionally, accomplish the split scenario are described in in [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
skipping to change at page 29, line 34 skipping to change at page 30, line 35
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.
[3] Patel, A., "Authentication Protocol for Mobile IPv6", [3] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury,
draft-ietf-mip6-rfc4285bis-01 (work in progress), October 2007. "Authentication Protocol for Mobile IPv6",
draft-ietf-mip6-rfc4285bis-02 (work in progress),
December 2007.
[4] Devarapalli, V. and F. Dupont, "Mobile IPv6 Operation with [4] Devarapalli, V. and F. Dupont, "Mobile IPv6 Operation with
IKEv2 and the Revised IPsec Architecture", RFC 4877, IKEv2 and the Revised IPsec Architecture", RFC 4877,
April 2007. April 2007.
[5] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko, [5] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko,
"Diameter Base Protocol", RFC 3588, September 2003. "Diameter Base Protocol", RFC 3588, September 2003.
[6] Bradner, S., "Key words for use in RFCs to Indicate Requirement [6] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
skipping to change at page 30, line 9 skipping to change at page 31, line 15
[7] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible [7] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
Authentication Protocol (EAP) Application", RFC 4072, Authentication Protocol (EAP) Application", RFC 4072,
August 2005. August 2005.
[8] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol", [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., Tschofenig, H., Arumaithurai, M., and M. Jones, [10] Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C., and
"Quality of Service Attributes for Diameter",
draft-ietf-dime-qos-attributes-03 (work in progress),
November 2007.
[11] 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-06 (work in progress), draft-ietf-dime-mip6-integrated-08 (work in progress),
November 2007. February 2008.
[11] Korhonen, J., Tschofenig, H., Arumaithurai, M., and M. Jones,
"Quality of Service Attributes for Diameter",
draft-ietf-dime-qos-attributes-04 (work in progress),
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.
12.2. Informative References 12.2. Informative References
[13] Patel, A. and G. Giaretta, "Problem Statement for bootstrapping [13] 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., "AAA Goals for Mobile IPv6", [14] Giaretta, G., Guardini, I., Demaria, E., Bournelle, J., and R.
draft-ietf-mip6-aaa-ha-goals-03 (work in progress), Lopez, "AAA Goals for Mobile IPv6",
September 2006. draft-ietf-mext-aaa-ha-goals-00 (work in progress),
December 2007.
[15] Fajardo, V., Asveren, T., Tschofenig, H., and G. McGregor, [15] Fajardo, V., Asveren, T., Tschofenig, H., McGregor, G., and J.
"Diameter Applications Design Guidelines", Loughney, "Diameter Applications Design Guidelines",
draft-ietf-dime-app-design-guide-05 (work in progress), draft-ietf-dime-app-design-guide-06 (work in progress),
November 2007. January 2008.
[16] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury, [16] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury,
"Mobile Node Identifier Option for Mobile IPv6 (MIPv6)", "Mobile Node Identifier Option for Mobile IPv6 (MIPv6)",
RFC 4283, November 2005. RFC 4283, November 2005.
Authors' Addresses Authors' Addresses
Jouni Korhonen (editor) Jouni Korhonen
TeliaSonera TeliaSonera
Teollisuuskatu 13 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
Otto-Hahn-Ring 6 Linnoitustie 6
Munich, Bavaria 81739 Espoo 02600
Germany Finland
Email: Hannes.Tschofenig@nsn.com Phone: +358 (50) 4871445
Email: Hannes.Tschofenig@gmx.net
URI: http://www.tschofenig.com URI: http://www.tschofenig.com
Julien Bournelle Julien Bournelle
France Telecom R&D 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
skipping to change at page 32, line 7 skipping to change at page 33, line 7
Email: gerardo.giaretta@gmail.com Email: gerardo.giaretta@gmail.com
Madjid Nakhjiri Madjid Nakhjiri
Motorola Motorola
USA USA
Email: madjid.nakhjiri@motorola.com Email: madjid.nakhjiri@motorola.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 End of changes. 122 change blocks. 
272 lines changed or deleted 286 lines changed or added

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