< draft-ietf-dime-mip6-split-16.txt   draft-ietf-dime-mip6-split-17.txt >
Diameter Maintenance and J. Korhonen, Ed. Diameter Maintenance and J. Korhonen, Ed.
Extensions (DIME) H. Tschofenig Extensions (DIME) H. Tschofenig
Internet-Draft Nokia Siemens Networks Internet-Draft Nokia Siemens Networks
Intended status: Standards Track J. Bournelle Intended status: Standards Track J. Bournelle
Expires: July 2, 2009 Orange Labs Expires: October 30, 2009 Orange Labs
G. Giaretta G. Giaretta
Qualcomm Qualcomm
M. Nakhjiri M. Nakhjiri
Motorola Motorola
December 29, 2008 April 28, 2009
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-16.txt draft-ietf-dime-mip6-split-17.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 July 2, 2009. This Internet-Draft will expire on October 30, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2008 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents in effect on the date of
(http://trustee.ietf.org/license-info) in effect on the date of publication of this document (http://trustee.ietf.org/license-info).
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document.
to this document.
Abstract Abstract
Mobile IPv6 deployments may want to bootstrap their operations Mobile IPv6 deployments may want to bootstrap their operations
dynamically based on an interaction between the Home Agent and the dynamically based on an interaction between the Home Agent and the
Diameter server of the Mobile Service Provider. This document Diameter server of the Mobile Service Provider. This document
specifies the interaction between a Mobile IP Home Agent and that specifies the interaction between a Mobile IP Home Agent and a
Diameter server. Diameter server.
Several different mechanisms for authenticating a Mobile Node are This document defines the Home Agent to the Diameter server
supported. The usage of the Internet Key Exchange v2 protocol allows communication when the mobile node authenticates using the Internet
different mechanisms, such as the Extensible Authentication Protocol, Key Exchange v2 protocol with the Extensible Authentication Protocol
certificates and pre-shared secrets to be used. Furthermore, another or using the Mobile IPv6 Authentication Protocol. In addition to
method makes use of the Mobile IPv6 Authentication Protocol. In authentication and authorization, the configuration of Mobile IPv6
addition to authentication and authorization, the configuration of specific parameters and accounting is specified in this document.
Mobile IPv6 specific parameters and accounting is specified in this
document.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 9 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 8
3. Application Identifiers . . . . . . . . . . . . . . . . . . . 10 3. Application Identifiers . . . . . . . . . . . . . . . . . . . 9
4. Protocol Description . . . . . . . . . . . . . . . . . . . . . 11 4. Protocol Description . . . . . . . . . . . . . . . . . . . . . 10
4.1. Support for Mobile IPv6 with IKEv2 and EAP . . . . . . . . 11 4.1. Support for Mobile IPv6 with IKEv2 and EAP . . . . . . . . 10
4.2. Support for the Mobile IPv6 Authentication Protocol . . . 14 4.2. Support for the Mobile IPv6 Authentication Protocol . . . 13
4.3. Mobile IPv6 Session Management . . . . . . . . . . . . . . 15 4.3. Mobile IPv6 Session Management . . . . . . . . . . . . . . 14
4.3.1. Session-Termination-Request . . . . . . . . . . . . . 15 4.3.1. Session-Termination-Request . . . . . . . . . . . . . 14
4.3.2. Session-Termination-Answer . . . . . . . . . . . . . . 15 4.3.2. Session-Termination-Answer . . . . . . . . . . . . . . 14
4.3.3. Abort-Session-Request . . . . . . . . . . . . . . . . 16 4.3.3. Abort-Session-Request . . . . . . . . . . . . . . . . 15
4.3.4. Abort-Session-Answer . . . . . . . . . . . . . . . . . 16 4.3.4. Abort-Session-Answer . . . . . . . . . . . . . . . . . 15
4.4. Accounting for Mobile IPv6 services . . . . . . . . . . . 16 4.4. Accounting for Mobile IPv6 services . . . . . . . . . . . 15
4.4.1. Accounting-Request . . . . . . . . . . . . . . . . . . 17 4.4.1. Accounting-Request . . . . . . . . . . . . . . . . . . 16
4.4.2. Accounting-Answer . . . . . . . . . . . . . . . . . . 17 4.4.2. Accounting-Answer . . . . . . . . . . . . . . . . . . 16
5. Command Codes . . . . . . . . . . . . . . . . . . . . . . . . 18 5. Command Codes . . . . . . . . . . . . . . . . . . . . . . . . 17
5.1. Command Code for Mobile IPv6 with IKEv2 and EAP . . . . . 18 5.1. Command Code for Mobile IPv6 with IKEv2 and EAP . . . . . 17
5.1.1. Diameter-EAP-Request . . . . . . . . . . . . . . . . . 18 5.1.1. Diameter-EAP-Request . . . . . . . . . . . . . . . . . 17
5.1.2. Diameter-EAP-Answer . . . . . . . . . . . . . . . . . 19 5.1.2. Diameter-EAP-Answer . . . . . . . . . . . . . . . . . 18
5.2. Command Codes for Mobile IPv6 Authentication Protocol 5.2. Command Codes for Mobile IPv6 Authentication Protocol
Support . . . . . . . . . . . . . . . . . . . . . . . . . 20 Support . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.2.1. MIP6-Request . . . . . . . . . . . . . . . . . . . . . 21 5.2.1. MIP6-Request . . . . . . . . . . . . . . . . . . . . . 20
5.2.2. MIP6-Answer . . . . . . . . . . . . . . . . . . . . . 22 5.2.2. MIP6-Answer . . . . . . . . . . . . . . . . . . . . . 21
6. AVPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 6. AVPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
6.1. User-Name AVP . . . . . . . . . . . . . . . . . . . . . . 26 6.1. User-Name AVP . . . . . . . . . . . . . . . . . . . . . . 25
6.2. Service-Selection AVP . . . . . . . . . . . . . . . . . . 26 6.2. Service-Selection AVP . . . . . . . . . . . . . . . . . . 25
6.3. MIP-MN-AAA-SPI AVP . . . . . . . . . . . . . . . . . . . . 27 6.3. MIP-MN-AAA-SPI AVP . . . . . . . . . . . . . . . . . . . . 25
6.4. MIP-MN-HA-SPI AVP . . . . . . . . . . . . . . . . . . . . 27 6.4. MIP-MN-HA-SPI AVP . . . . . . . . . . . . . . . . . . . . 26
6.5. MIP-Mobile-Node-Address AVP . . . . . . . . . . . . . . . 27 6.5. MIP-Mobile-Node-Address AVP . . . . . . . . . . . . . . . 26
6.6. MIP6-Agent-Info AVP . . . . . . . . . . . . . . . . . . . 28 6.6. MIP6-Agent-Info AVP . . . . . . . . . . . . . . . . . . . 26
6.7. MIP-Careof-Address AVP . . . . . . . . . . . . . . . . . . 28 6.7. MIP-Careof-Address AVP . . . . . . . . . . . . . . . . . . 27
6.8. MIP-Authenticator AVP . . . . . . . . . . . . . . . . . . 28 6.8. MIP-Authenticator AVP . . . . . . . . . . . . . . . . . . 27
6.9. MIP-MAC-Mobility-Data AVP . . . . . . . . . . . . . . . . 28 6.9. MIP-MAC-Mobility-Data AVP . . . . . . . . . . . . . . . . 27
6.10. MIP-Session-Key AVP . . . . . . . . . . . . . . . . . . . 29 6.10. MIP-Session-Key AVP . . . . . . . . . . . . . . . . . . . 27
6.11. MIP-MSA-Lifetime AVP . . . . . . . . . . . . . . . . . . . 29 6.11. MIP-MSA-Lifetime AVP . . . . . . . . . . . . . . . . . . . 27
6.12. MIP-MN-HA-MSA AVP . . . . . . . . . . . . . . . . . . . . 29 6.12. MIP-MN-HA-MSA AVP . . . . . . . . . . . . . . . . . . . . 28
6.13. MIP-Algorithm-Type AVP . . . . . . . . . . . . . . . . . . 29 6.13. MIP-Algorithm-Type AVP . . . . . . . . . . . . . . . . . . 28
6.14. MIP-Replay-Mode AVP . . . . . . . . . . . . . . . . . . . 30 6.14. MIP-Replay-Mode AVP . . . . . . . . . . . . . . . . . . . 28
6.15. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . . . 30 6.15. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . . . 29
6.16. MIP-Timestamp AVP . . . . . . . . . . . . . . . . . . . . 30 6.16. MIP-Timestamp AVP . . . . . . . . . . . . . . . . . . . . 29
6.17. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 30 6.17. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 29
6.18. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 30 6.18. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 29
6.19. Chargeable-User-Identity AVP . . . . . . . . . . . . . . . 31 6.19. Chargeable-User-Identity AVP . . . . . . . . . . . . . . . 29
6.20. MIP6-Auth-Mode AVP . . . . . . . . . . . . . . . . . . . . 31 6.20. MIP6-Auth-Mode AVP . . . . . . . . . . . . . . . . . . . . 29
6.21. Accounting AVPs . . . . . . . . . . . . . . . . . . . . . 31 6.21. Accounting AVPs . . . . . . . . . . . . . . . . . . . . . 30
7. Result-Code AVP Values . . . . . . . . . . . . . . . . . . . . 33 7. Result-Code AVP Values . . . . . . . . . . . . . . . . . . . . 32
7.1. Success . . . . . . . . . . . . . . . . . . . . . . . . . 33 7.1. Success . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.2. Permanent Failures . . . . . . . . . . . . . . . . . . . . 33 7.2. Permanent Failures . . . . . . . . . . . . . . . . . . . . 32
8. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 34 8. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 33
8.1. DER, DEA, MIR and MIA AVP/Command-Code Table . . . . . . . 34 8.1. DER, DEA, MIR and MIA AVP/Command-Code Table . . . . . . . 33
8.2. Coupled Accounting Model AVP Table . . . . . . . . . . . . 35 8.2. Coupled Accounting Model AVP Table . . . . . . . . . . . . 34
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
9.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 37 9.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 36
9.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . 37 9.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . 36
9.3. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 37 9.3. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 36
9.4. Application Identifier . . . . . . . . . . . . . . . . . . 38 9.4. Application Identifier . . . . . . . . . . . . . . . . . . 37
9.5. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 38 9.5. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 37
10. Security Considerations . . . . . . . . . . . . . . . . . . . 39 10. Security Considerations . . . . . . . . . . . . . . . . . . . 38
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 40 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 39
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 41 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 40
12.1. Normative References . . . . . . . . . . . . . . . . . . . 41 12.1. Normative References . . . . . . . . . . . . . . . . . . . 40
12.2. Informative References . . . . . . . . . . . . . . . . . . 42 12.2. Informative References . . . . . . . . . . . . . . . . . . 41
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 43 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 42
1. Introduction 1. Introduction
Performing the Mobile IPv6 protocol [RFC3775], requires the Mobile Performing the Mobile IPv6 protocol [RFC3775], requires the Mobile
Node (MN) to own a Home Address (HoA) and to have an assigned Home Node (MN) to own a Home Address (HoA) and to have an assigned Home
Agent (HA) to the MN. The MN needs to register with the HA in order Agent (HA) to the MN. The MN needs to register with the HA in order
to enable its reachability and mobility, when away from its home to enable its reachability and mobility, when away from its home
link. The registration process itself may require an establishment link. The registration process itself may require an establishment
of IPsec security associations (SA) and cryptographic material of IPsec security associations (SA) and cryptographic material
between the MN and the HA. Alternatively, the registration process between the MN and the HA. Alternatively, the registration process
skipping to change at page 8, line 19 skipping to change at page 7, line 19
o IKEv2 usage with EAP o IKEv2 usage with EAP
o Mobile IPv6 Authentication Protocol o Mobile IPv6 Authentication Protocol
New authentication mechanisms may be added later by separate New authentication mechanisms may be added later by separate
specifications. specifications.
For accounting of Mobile IPv6 services provided to the MN, this For accounting of Mobile IPv6 services provided to the MN, this
specification uses the Diameter Base Protocol accounting defined in specification uses the Diameter Base Protocol accounting defined in
RFC 3588 [RFC3588]. [RFC3588].
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in [RFC2119].
The Mobile IPv6 bootstrapping terminology is taken from [RFC4640]. The Mobile IPv6 bootstrapping terminology is taken from [RFC4640].
Additional terminology is defined below: Additional terminology is defined below:
Authentication, Authorization, and Accounting (AAA): Authentication, Authorization, and Accounting (AAA):
AAA protocol based on Diameter [RFC3588] with required EAP support AAA protocol based on Diameter [RFC3588] with required EAP support
[RFC4072]. [RFC4072].
Home AAA (AAAH): Home AAA (AAAH):
skipping to change at page 11, line 14 skipping to change at page 10, line 14
4. Protocol Description 4. Protocol Description
4.1. Support for Mobile IPv6 with IKEv2 and EAP 4.1. Support for Mobile IPv6 with IKEv2 and EAP
The use of IKEv2 with EAP between the MN and the HA allows the AAA to The use of IKEv2 with EAP between the MN and the HA allows the AAA to
authenticate the MN. When EAP is used with IKEv2, the Diameter EAP authenticate the MN. When EAP is used with IKEv2, the Diameter EAP
application logic and procedures, as defined in [RFC4072], are re- application logic and procedures, as defined in [RFC4072], are re-
used. EAP methods that do not establish a shared key SHOULD NOT be used. EAP methods that do not establish a shared key SHOULD NOT be
used, as they are subject to a number of man-in-the-middle attacks as used, as they are subject to a number of man-in-the-middle attacks as
stated in Section 2.16 and Section 5 of RFC 4306 [RFC4306]. AVPs stated in Section 2.16 and Section 5 of [RFC4306]. AVPs specific to
specific to Mobile IPv6 bootstrapping are added to the EAP Mobile IPv6 bootstrapping are added to the EAP application commands.
application commands.
Figure 2 shows the message flow involved during the authentication Figure 2 shows the message flow involved during the authentication
phase when EAP is used. phase when EAP is used. The communication between the mobile node
and the home agent use the conventions defined in [RFC4306].
Similarly, the communication between the home agent and the Diameter
server use the conventions defined in [RFC4072].
Mobile Home Diameter Mobile Home Diameter
Node Agent Server Node Agent Server
| | | | | |
| HDR, SAi1, KEi, Ni (1) | | | HDR, SAi1, KEi, Ni (1) | |
|-------------------------------->| | |-------------------------------->| |
| | | | | |
| HDR, SAr1, KEr, Nr, [CERTREQ](2)| | | HDR, SAr1, KEr, Nr, [CERTREQ](2)| |
|<--------------------------------| | |<--------------------------------| |
| | | | | |
skipping to change at page 12, line 35 skipping to change at page 11, line 35
|-------------------------------->| 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) + |
| | MIP6 Bootstrapping AVPs | | | MIP6 Bootstrapping AVPs |
| 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,] | |
skipping to change at page 13, line 37 skipping to change at page 12, line 37
chosen, a number of DER and DEA messages carry the method specific chosen, a number of DER and DEA messages carry the method specific
exchanges between the MN and the Diameter server/EAP server. exchanges between the MN and the Diameter server/EAP server.
At the end of the EAP authentication phase, the Diameter server At the end of the EAP authentication phase, the Diameter server
indicates the result of the authentication in the Result-Code AVP and indicates the result of the authentication in the Result-Code AVP and
provides the corresponding EAP packet (EAP Success or EAP Failure). provides the corresponding EAP packet (EAP Success or EAP Failure).
The last IKEv2 message sent by the HA contains the Home Address or The last IKEv2 message sent by the HA contains the Home Address or
the Home Prefix. In the latter case, a CREATE_CHILD_SA exchange is the Home Prefix. In the latter case, a CREATE_CHILD_SA exchange is
necessary to setup IPsec SAs for Mobile IPv6 signaling. necessary to setup IPsec SAs for Mobile IPv6 signaling.
In some deployment scenarios, the HA may also acts as a IKEv2 In some deployment scenarios, the HA may also act as an IKEv2
Responder for IPsec VPN access. A challenge in this case is that the Responder for a conventional IPsec VPN access. The challenge in this
IKEv2 responder may not know if IKEv2 is used for Mobile IPv6 service case is that the IKEv2 responder may not know if IKEv2 is used for
or for IPsec VPN access service. A network operator needs to be Mobile IPv6 service or for IPsec VPN access service. A network
aware of this limitation. The MN may provide a hint of the intended operator needs to be aware of this limitation. One solution already
service, for example, by using different identities in the IKE_AUTH supported by IKEv2 is to use different responder identities when
message for the IPsec VPN service and Mobile IPv6 service. However, operating as a conventional IPsec VPN gateway or as a HA. The MN can
the use of different identities during the IKEv2 negotiation is then indicate the preferred responder type using the appropriate IDr
deployment specific. Another possibility is to make the distinction payload in the IKE_AUTH message.
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 the Mobile IPv6 Authentication Protocol 4.2. Support for the Mobile IPv6 Authentication Protocol
Figure 3 shows the message sequence between the MN, the HA and the Figure 3 shows the message sequence between the MN, the HA and the
Diameter server during the registration when Mobile IPv6 Diameter server during the registration when Mobile IPv6
Authentication Protocol is used. A BU and a Binding Acknowledgement Authentication Protocol is used. A BU and a Binding Acknowledgement
skipping to change at page 14, line 31 skipping to change at page 13, line 31
The procedure described in this specification for the Mobile IPv6 The procedure described in this specification for the Mobile IPv6
Authentication Protocol is only needed for the initially received BU Authentication Protocol is only needed for the initially received BU
for which the HA does not have an existing security association. for which the HA does not have an existing security association.
When the HA receives subsequent BUs, they are processed locally in When the HA receives subsequent BUs, they are processed locally in
the HA. It is RECOMMENDED that the HA sends an accounting request the HA. It is RECOMMENDED that the HA sends an accounting request
message every time it receives a Binding Update. However, the HA MAY message every time it receives a Binding Update. However, the HA MAY
re-authorize the MN with the Diameter server at any time depending on re-authorize the MN with the Diameter server at any time depending on
the deployment and the local policy. the deployment and the local policy.
In some architectures and network deployments the MN-HA security
associations may be established as a result of a successful network
access authentication. In such deployments, both the MN and the
Diameter server share the keying material required for computation
and 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.
This specification assumes that in the case Mobile IPv6 This specification assumes that in the case Mobile IPv6
Authentication Protocol is used, the MN-AAA option is included in the Authentication Protocol is used, the MN-AAA option is included in the
BU. Other possible uses of Mobile IPv6 Authentication Protocol are BU as defined in [RFC4285] and the Diameter server computes required
out of scope of this specification and would require a new session keys after having successfully authenticated the MN. The
specification to describe the detailed behavior of the HA-AAAH computation of the session keys is out of scope of this
interface. However, the HA-AAAH interface has been designed in a way specification. Other possible ways of using Mobile IPv6
that the Mobile IPv6 Authentication Protocol may also be used without Authentication Protocol are also out of scope of this specification
the MN-AAA option. and would require a new specification to describe the detailed
behavior of the HA-AAAH interface and corresponding session key
derivation.
Mobile Home Diameter Mobile Home Diameter
Node Agent Server Node Agent Server
| | | | | |
| | MIP6-Request + MIP6 | | | MIP6-Request + MIP6 |
| Binding Update | Bootstrapping AVPs | | Binding Update | Bootstrapping AVPs |
|------------------------------------>|-------------------->| |------------------------------------>|-------------------->|
| (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 15, line 35 skipping to change at page 14, line 35
4.3. Mobile IPv6 Session Management 4.3. Mobile IPv6 Session Management
The Diameter server may maintain state or may be stateless. This is The Diameter server may maintain state or may be stateless. This is
indicated in the Auth-Session-State AVP (or its absence). The HA indicated in the Auth-Session-State AVP (or its absence). The HA
MUST support the Authorization Session State Machine defined in MUST support the Authorization Session State Machine defined in
[RFC3588]. [RFC3588].
This specification makes an assumption that each SA created between This specification makes an assumption that each SA created between
the MN and the HA as a result of a successful IKEv2 negotiation or a the MN and the HA as a result of a successful IKEv2 negotiation or a
Mobile IPv6 Authentication Protocol exchange correspond to one Mobile IPv6 Authentication Protocol exchange correspond to one
Diameter session. Diameter session. In IKEv2 case we specifically mean the created IKE
SA.
4.3.1. Session-Termination-Request 4.3.1. Session-Termination-Request
The Session-Termination-Request (STR) message [RFC3588] is sent by The Session-Termination-Request (STR) message [RFC3588] is sent by
the HA to inform the Diameter server that an authorized session is the HA to inform the Diameter server that an authorized session is
being terminated. This means that the HA MUST terminate the being terminated. This means that the HA MUST terminate the
corresponding Mobile IPv6 binding and also terminate the corresponding Mobile IPv6 binding and also terminate the
corresponding SA. corresponding SA.
4.3.2. Session-Termination-Answer 4.3.2. Session-Termination-Answer
skipping to change at page 18, line 12 skipping to change at page 17, line 12
The Accounting-Answer command [RFC3588] is sent by the Diameter The Accounting-Answer command [RFC3588] is sent by the Diameter
server to the HA to acknowledge an Accounting-Request. server to the HA to acknowledge an Accounting-Request.
5. Command Codes 5. Command Codes
5.1. Command Code for Mobile IPv6 with IKEv2 and EAP 5.1. Command Code for Mobile IPv6 with IKEv2 and EAP
For the use of Mobile IPv6 with IKEv2 and EAP this document reuses For the use of Mobile IPv6 with IKEv2 and EAP this document reuses
the Diameter EAP application [RFC4072] commands: Diameter-EAP-Request the Diameter EAP application [RFC4072] commands: Diameter-EAP-Request
(DER) and Diameter-EAP-Answer (DEA). This specification extends the (DER) and Diameter-EAP-Answer (DEA). This specification extends the
existing DER and DEA command ABNFs with a number AVPs to support existing DER and DEA command ABNFs with a number of AVPs to support
Mobile IPv6 split scenario bootstrapping. Other than new additional Mobile IPv6 split scenario bootstrapping. Other than new additional
AVPs and the corresponding additions to the command ABNFs, the AVPs and the corresponding additions to the command ABNFs, the
Diameter EAP application command ABNFs remain unchanged. The ABNF Diameter EAP application command ABNFs remain unchanged. The ABNF
language is defined in [RFC3588]. language is defined in [RFC3588].
Command-Name Abbrev. Code Reference Application Command-Name Abbrev. Code Reference Application
--------------------------------------------------------------------- ---------------------------------------------------------------------
Diameter-EAP-Request DER 268 RFC 4072 Diameter Mobile IPv6 IKE Diameter-EAP-Request DER 268 RFC 4072 Diameter Mobile IPv6 IKE
Diameter-EAP-Answer DEA 268 RFC 4072 Diameter Mobile IPv6 IKE Diameter-EAP-Answer DEA 268 RFC 4072 Diameter Mobile IPv6 IKE
skipping to change at page 20, line 17 skipping to change at page 19, line 17
{ 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-Reissued-Payload ]
[ EAP-Master-Session-Key ] [ EAP-Master-Session-Key ]
[ EAP-Key-Name ] [ EAP-Key-Name ]
[ Multi-Round-Time [ Multi-Round-Time ]
... ...
*2[ MIP-Mobile-Node-Address ] *2[ MIP-Mobile-Node-Address ]
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
[ MIP6-Agent-Info ] [ MIP6-Agent-Info ]
[ Service-Selection ] [ Service-Selection ]
* [ QoS-Resources ] * [ QoS-Resources ]
[ Chargeable-User-Identity ] [ Chargeable-User-Identity ]
... ...
* [ AVP ] * [ AVP ]
skipping to change at page 20, line 47 skipping to change at page 19, line 47
Mobile IPv6 Authentication Protocol. Mobile IPv6 Authentication Protocol.
There are multiple ways of deploying and utilizing Mobile IPv6 There are multiple ways of deploying and utilizing Mobile IPv6
Authentication Protocol, especially regarding the associated AAA Authentication Protocol, especially regarding the associated AAA
interactions. In order to support multiple deployment models this interactions. In order to support multiple deployment models this
specification defines the MIP6-Auth-Mode AVP that in the request specification defines the MIP6-Auth-Mode AVP that in the request
message tells the mode that the HA supports. This specification message tells the mode that the HA supports. This specification
defines a method that requires the use of the MN-AAA option with the defines a method that requires the use of the MN-AAA option with the
Mobile IPv6 Authentication Protocol. Mobile IPv6 Authentication Protocol.
Command-Name Abbrev. Code Reference Application Command-Name Abbrev. Code Reference Application
--------------------------------------------------------------------- ---------------------------------------------------------------------
MIP6-Request MIR TBD 5.3.1 Diameter Mobile IPv6 Auth MIP6-Request MIR TBD 5.3.1 Diameter Mobile IPv6 Auth
MIP6-Answer MIA TBD 5.3.2 Diameter Mobile IPv6 Auth MIP6-Answer MIA TBD 5.3.2 Diameter Mobile IPv6 Auth
Command Codes Command Codes
5.2.1. MIP6-Request 5.2.1. MIP6-Request
The MIP6-Request (MIR), indicated by the Command-Code field set to The MIP6-Request (MIR), indicated by the Command-Code field set to
TBD and the 'R' bit set in the Command Flags field, is sent by the 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 HA, acting as a Diameter client, in order to request the
authentication and authorization of a MN. authentication and authorization of a MN.
Although the HA provides the Diameter server with a replay protection Although the HA provides the Diameter server with replay protection
related information, the HA is responsible for the replay protection. related information, the HA is responsible for the replay protection.
The message format is shown below. The message format is shown below.
<MIP6-Request> ::= < Diameter Header: XXX, REQ, PXY > <MIP6-Request> ::= < Diameter Header: TBD, REQ, PXY >
< Session-ID > < Session-ID >
{ Auth-Application-Id } { Auth-Application-Id }
{ User-Name } { User-Name }
{ Destination-Realm } { Destination-Realm }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Auth-Request-Type } { Auth-Request-Type }
[ Destination-Host ] [ Destination-Host ]
[ Origin-State-Id ] [ Origin-State-Id ]
[ NAS-Identifier ] [ NAS-Identifier ]
skipping to change at page 23, line 4 skipping to change at page 22, line 4
AUTHORIZE_AUTHENTICATE. This is the case when the MIP6-Auth-Mode is AUTHORIZE_AUTHENTICATE. This is the case when the MIP6-Auth-Mode is
set to the value MIP6_AUTH_MN_AAA. set to the value MIP6_AUTH_MN_AAA.
5.2.2. MIP6-Answer 5.2.2. MIP6-Answer
The MIP6-Answer (MIA) message, indicated by the Command-Code field The MIP6-Answer (MIA) message, indicated by the Command-Code field
set to TBD and the 'R' bit cleared in the Command Flags field, is set to TBD and the 'R' bit cleared in the Command Flags field, is
sent by the Diameter server in response to the MIP6-Request message. sent by the Diameter server in response to the MIP6-Request message.
The User-Name AVP MAY be included in the MIA if it is present in the The User-Name AVP MAY be included in the MIA if it is present in the
MIR. The Result-Code AVP MAY contain one of the values defined in MIR. The Result-Code AVP MAY contain one of the values defined in
Section 7, in addition to the values defined in RFC 3588 [RFC3588]. Section 7, in addition to the values defined in [RFC3588].
An MIA message with the Result-Code AVP set to DIAMETER_SUCCESS MUST An MIA message with the Result-Code AVP set to DIAMETER_SUCCESS MUST
include the MIP-Mobile-Node-Address AVP. include the MIP-Mobile-Node-Address AVP.
The message format is shown below. The message format is shown below.
<MIP6-Answer> ::= < Diameter Header: XXX, PXY > <MIP6-Answer> ::= < Diameter Header: TBD, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Result-Code } { Result-Code }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Auth-Request-Type } { Auth-Request-Type }
[ User-Name ] [ User-Name ]
[ Authorization-Lifetime ] [ Authorization-Lifetime ]
[ Auth-Session-State ] [ Auth-Session-State ]
[ Error-Message ] [ Error-Message ]
skipping to change at page 24, line 7 skipping to change at page 23, line 7
[ Origin-State-Id ] [ Origin-State-Id ]
* [ Proxy-Info ] * [ Proxy-Info ]
* [ Redirect-Host ] * [ Redirect-Host ]
[ Redirect-Host-Usage ] [ Redirect-Host-Usage ]
[ Redirect-Max-Cache-Time ] [ Redirect-Max-Cache-Time ]
* [ Failed-AVP ] * [ Failed-AVP ]
* [ AVP ] * [ AVP ]
6. AVPs 6. AVPs
To provide support for RFC 4285 [RFC4285] and for RFC 4877 [RFC4877] To provide support for [RFC4285] and for [RFC4877] the AVPs in the
the AVPs in the following subsections are needed. RFC 3588, RFC 4004 following subsections are needed. [RFC3588], [RFC4004] and [RFC4005]
and RFC 4005 [RFC4005] defined AVPs are reused whenever possible defined AVPs are reused whenever possible without changing the
without changing the existing semantics of those AVPs. existing semantics of those AVPs.
+-------------------------+ +--------------------+
| AVP Flag rules | | AVP Flag rules |
+----+----+----+-----+----+ +----+---+------+----+----+
AVP Defined | | |SHLD| MUST|MAY | AVP Defined | | |SHOULD|MUST|MAY |
Attribute Name Code in Value Type |MUST| MAY| NOT| NOT|Encr| Attribute Name Code in Value Type |MUST|MAY| NOT | NOT|Encr|
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|MIP6-Feature- TBD Note 1 Unsigned64 | M | P | | V | Y | |MIP6-Feature- 124 RFC5447 Unsigned64 | M | P | | V | Y |
| Vector | | | | | | | Vector | | | | | |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|MIP-Mobile- | M | P | | V | Y | |MIP-Mobile- | M | P | | V | Y |
| Node-Address 334 RFC4004 Address | | | | | | | Node-Address 334 RFC4004 Address | | | | | |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|MIP6-Agent-Info TBD Note 3 Grouped | M | P | | V | Y | |MIP6-Agent-Info 486 RFC5447 Grouped | M | P | | V | Y |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|User-Name 1 RFC3588 UTF8String | M | P | | V | Y | |User-Name 1 RFC3588 UTF8String | M | P | | V | Y |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|Service- TBD 6.2 UTF8String | M | P | | V | Y | |Service- TBD 6.2 UTF8String | M | P | | V | Y |
| Selection | | | | | | | Selection | | | | | |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|QoS-Capability TBD Note 2 Grouped | M | P | | V | Y | |QoS-Capability TBD Note 1 Grouped | M | P | | V | Y |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|QoS-Resources TBD Note 2 Grouped | M | P | | V | Y | |QoS-Resources TBD Note 1 Grouped | M | P | | V | Y |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|MIP-MN-HA-MSA TBD 6.12 Grouped | M | P | | V | Y | |MIP-MN-HA-MSA TBD 6.12 Grouped | M | P | | V | Y |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|Chargeable-User- OctetString| M | P | | V | Y | |Chargeable-User- OctetString| M | P | | V | Y |
| Identity 89 6.19 | | | | | | | Identity 89 6.19 | | | | | |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
AVPs for Mobile IPv6 IKE Application AVPs for Mobile IPv6 IKE Application
Note 1: The MIP6-Feature-Vector AVP is defined in Section 4.7.4 of Note 1: The QoS-Capability and the QoS-Resource AVPs are defined in
[I-D.ietf-dime-mip6-integrated].
Note 2: The QoS-Capability and the QoS-Resource AVPs are defined in
Sections 4.1 and 4.3 of [I-D.ietf-dime-qos-attributes]. Sections 4.1 and 4.3 of [I-D.ietf-dime-qos-attributes].
Note 3: The MIP6-Agent-Info AVP is defined in Section 4.5.1 of +--------------------+
[I-D.ietf-dime-mip6-integrated]. | AVP Flag rules |
+----+---+------+----+----+
AVP Section | | |SHOULD|MUST|MAY |
Attribute Name Code Defined Value Type |MUST|MAY| NOT | NOT|Encr|
+-------------------------+ +-----------------------------------------+----+---+------+----+----+
| AVP Flag rules | |MIP6-Feature- 124 RFC5447 Unsigned64 | M | P | | V | Y |
+----+----+----+-----+----+ | Vector | | | | | |
AVP Section | | |SHLD| MUST|MAY | +-----------------------------------------+----+---+------+----+----+
Attribute Name Code Defined Value Type |MUST| MAY| NOT| NOT|Encr| |User-Name 1 RFC3588 UTF8String | M | P | | V | Y |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|MIP6-Feature- TBD Note 1 Unsigned64 | M | P | | V | Y | |Service- TBD 6.2 UTF8String | M | P | | V | Y |
| Vector | | | | | | | Selection | | | | | |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|User-Name 1 RFC3588 UTF8String | M | P | | V | Y | |MIP-MN-AAA-SPI 341 RFC4004 Unsigned32 | M | P | | V | Y |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|Service- TBD 6.2 UTF8String | M | P | | V | Y | |MIP-MN-HA-SPI TBD 6.4 Unsigned32 | M | P | | V | Y |
| Selection | | | | | | +-----------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+----+----+-----+----+ |MIP-Mobile- 333 RFC4004 Address | M | P | | V | Y |
|MIP-MN-AAA-SPI 341 RFC4004 Unsigned32 | M | P | | V | Y | | Node-Address | | | | | |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|MIP-MN-HA-SPI TBD 6.4 Unsigned32 | M | P | | V | Y | |MIP6-Agent-Info 486 RFC5447 Grouped | M | P | | V | Y |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|MIP-Mobile- 333 RFC4004 Address | M | P | | V | Y | |MIP-Careof- TBD 6.7 Address | M | P | | V | Y |
| Node-Address | | | | | | | Address | | | | | |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|MIP6-Agent-Info TBD Note 3 Grouped | M | P | | V | Y | |MIP- TBD 6.8 OctetString| M | P | | V | Y |
+-----------------------------------------+----+----+----+-----+----+ | Authenticator | | | | | |
|MIP-Careof- TBD 6.7 Address | M | P | | V | Y | +-----------------------------------------+----+---+------+----+----+
| Address | | | | | | |MIP-MAC- TBD 6.9 OctetString| M | P | | V | Y |
+-----------------------------------------+----+----+----+-----+----+ | Mobility-Data | | | | | |
|MIP- TBD 6.8 OctetString| M | P | | V | Y | +-----------------------------------------+----+---+------+----+----+
| Authenticator | | | | | | |MIP-Session-Key 343 6.10 OctetString| M | P | | V | Y |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|MIP-MAC- TBD 6.9 OctetString| M | P | | V | Y | |MIP-MSA- 367 RFC4004 Unsigned32 | M | P | | V | Y |
| Mobility-Data | | | | | | | Lifetime | | | | | |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|MIP-Session-Key 343 6.10 OctetString| M | P | | V | Y | |MIP-MN-HA-MSA TBD 6.12 Grouped | M | P | | V | Y |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|MIP-MSA- 367 RFC4004 Unsigned32 | M | P | | V | Y | |MIP-Algorithm- 345 6.13 Enumerated | M | P | | V | Y |
| Lifetime | | | | | | | Type | | | | | |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|MIP-MN-HA-MSA TBD 6.12 Grouped | M | P | | V | Y | |MIP-Replay-Mode 346 6.14 Enumerated | M | P | | V | Y |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|MIP-Algorithm- 345 6.13 Enumerated | M | P | | V | Y | |MIP-Timestamp TBD 6.16 OctetString| M | P | | V | Y |
| Type | | | | | | +-----------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+----+----+-----+----+ |QoS-Capability TBD Note 1 Grouped | M | P | | V | Y |
|MIP-Replay-Mode 346 6.14 Enumerated | M | P | | V | Y | +-----------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+----+----+-----+----+ |QoS-Resources TBD Note 1 Grouped | M | P | | V | Y |
|MIP-Timestamp TBD 6.16 Time | M | P | | V | Y | +-----------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+----+----+-----+----+ |Chargeable-User- OctetString| M | P | | V | Y |
|QoS-Capability TBD Note 2 Grouped | M | P | | M | Y | | Identity 89 6.19 | | | | | |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|QoS-Resources TBD Note 2 Grouped | M | P | | V | Y | |MIP6-Auth-Mode TBD 6.20 Enumerated | M | P | | V | Y |
+-----------------------------------------+----+----+----+-----+----+ +-----------------------------------------+----+---+------+----+----+
|Chargeable-User- OctetString| M | P | | V | Y | |Rest of the AVPs RFC3588 | M | P | | V | Y |
| Identity 89 6.19 | | | | | | |in the MIR & MIA RFC4005 | | | | | |
+-----------------------------------------+----+----+----+-----+----+ |excluding *[AVP] | | | | | |
|MIP6-Auth-Mode TBD 6.20 Enumerated | M | P | | V | Y | +-----------------------------------------+----+---+------+----+----+
+-----------------------------------------+----+----+----+-----+----+
|Rest of the AVPs RFC3588 | M | P | | V | Y |
|in the MIR & MIA RFC4005 | | | | | |
|excluding *[AVP] | | | | | |
+-----------------------------------------+----+----+----+-----+----+
AVPs for the Mobile IPv6 Auth Application AVPs for the Mobile IPv6 Auth Application
Note 1: The MIP6-Feature-Vector AVP is defined in Section 4.7.4 of Note 1: The QoS-Capability and the QoS-Resource AVPs are defined in
[I-D.ietf-dime-mip6-integrated].
Note 2: The QoS-Capability and the QoS-Resource AVPs are defined in
Sections 4.1 and 4.3 of [I-D.ietf-dime-qos-attributes]. Sections 4.1 and 4.3 of [I-D.ietf-dime-qos-attributes].
Note 3: The MIP6-Agent-Info AVP is defined in Section 4.5.1 of
[I-D.ietf-dime-mip6-integrated].
6.1. User-Name AVP 6.1. User-Name AVP
The User-Name AVP (AVP Code 1) is of type UTF8String and contains an The User-Name AVP (AVP Code 1) is of type UTF8String and contains an
NAI extracted from the MN-NAI mobility option included in the NAI extracted from the MN-NAI mobility option included in the
received BU message. Alternatively, the NAI can be extracted from received BU message. Alternatively, the NAI can be extracted from
the IKEv2 IDi payload included in the IKE_AUTH message sent by the the IKEv2 IDi payload included in the IKE_AUTH message sent by the
IKE initiator. IKE initiator.
6.2. Service-Selection AVP 6.2. Service-Selection AVP
skipping to change at page 27, line 14 skipping to change at page 25, line 51
name of the assigned default service to the HA. name of the assigned default service to the HA.
If the Service-Selection AVP is present in both the request and the If the Service-Selection AVP is present in both the request and the
reply messages, it SHOULD contain the same service name. If the reply messages, it SHOULD contain the same service name. If the
services differ, the HA MAY treat that as authorization failure. services differ, the HA MAY treat that as authorization failure.
6.3. MIP-MN-AAA-SPI AVP 6.3. MIP-MN-AAA-SPI AVP
The MIP-MN-AAA-SPI AVP (AVP Code 341) is of type Unsigned32 and The MIP-MN-AAA-SPI AVP (AVP Code 341) is of type Unsigned32 and
contains an SPI code extracted from the Mobility Message contains an SPI code extracted from the Mobility Message
Authentication Option included in the received BU message. The HA Authentication Option included in the received BU message. This AVP
includes this AVP in the MIR message when the MN-AAA Mobility Message is re-used from [RFC4004].
Authentication Option is available in the received BU (and the MIP6-
Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA).
This AVP is re-used from [RFC4004]. When the MIP6-Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA, this
AVP MUST be present in the MIR message.
6.4. MIP-MN-HA-SPI AVP 6.4. MIP-MN-HA-SPI AVP
The MIP-MN-HA-SPI AVP (AVP Code TBD) is of type Unsigned32 and The MIP-MN-HA-SPI AVP (AVP Code TBD) is of type Unsigned32 and
contains an SPI value that can be used with other parameters for contains an SPI value that can be used with other parameters for
identifying the security association required for the validation of identifying the security association required for the validation of
the Mobile IPv6 MN-HA Authentication Option. the Mobile IPv6 MN-HA Authentication Option.
When included in the MIR message, the Diameter server needs to return When the MIP6-Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA, and the
a valid MIP-MN-HA-MSA AVP in the corresponding MIA message. Either Diameter server returns a valid MIP-MN-HA-MSA AVP in the MIA message,
the MIP-MN-HA-SPI AVP or the MIP-MN-AAA-SPI AVP MUST be present in this AVP MUST be present inside the MIP-MN-HA-MSA AVP.
the MIR message, but not both.
6.5. MIP-Mobile-Node-Address AVP 6.5. MIP-Mobile-Node-Address AVP
The MIP-Mobile-Node-Address AVP (AVP Code 333) is of type Address and The MIP-Mobile-Node-Address AVP (AVP Code 333) is of type Address and
contains the HA assigned IPv6 or IPv4 Home Address of the Mobile contains the HA assigned IPv6 or IPv4 Home Address of the Mobile
Node. Node.
If the MIP-Mobile-Node-Address AVP contains the unspecified IPv6 If the MIP-Mobile-Node-Address AVP contains the unspecified IPv6
address (0::0) or the all zeroes IPv4 address (0.0.0.0) in a request address (0::0) or the all zeroes IPv4 address (0.0.0.0) in a request
message, then the HA expects the Diameter server to assign the Home message, then the HA expects the Diameter server to assign the Home
Address in a subsequent answer message. If the Diameter server Address in a subsequent answer message. If the Diameter server
assigns only an IPv6 Home Network Prefix to the Mobile Node the lower assigns only an IPv6 Home Network Prefix to the Mobile Node the lower
64 bits of the MIP-Mobile-Node-Address AVP provided address MUST be 64 bits of the MIP-Mobile-Node-Address AVP provided address MUST be
set to zero. set to zero.
This AVP is re-used from [RFC4004]. This AVP is re-used from [RFC4004].
6.6. MIP6-Agent-Info AVP 6.6. MIP6-Agent-Info AVP
The MIP6-Agent-Info AVP is defined in Section 4.5.1 of The MIP6-Agent-Info AVP (AVP Code 486) is defined in Section 4.2.1 of
[I-D.ietf-dime-mip6-integrated] and contains the IPv6 or the IPv4 [RFC5447] and contains the IPv6 or the IPv4 address information of
address information of the HA. The HA address in a request message the HA. The HA address in a request message is the same as in the
is the same as in the received BU message that triggered the received BU message that triggered the authentication and
authentication and authorization procedure towards the Diameter authorization procedure towards the Diameter server. One use case is
server. One use case is e.g., to inform the Diameter server of the e.g., to inform the Diameter server of the dynamically assigned HA.
dynamically assigned HA.
If the MIP6-Agent-Info AVP is present in an answer message and the If the MIP6-Agent-Info AVP is present in an answer message and the
Result-Code AVP is set to DIAMETER_SUCCESS_RELOCATE_HA, then the Result-Code AVP is set to DIAMETER_SUCCESS_RELOCATE_HA, then the
Diameter server is indicating to the HA that it MUST initiate a HA Diameter server is indicating to the HA that it MUST initiate a HA
switch procedure towards the MN (e.g., using the procedure defined in switch procedure towards the MN (e.g., using the procedure defined in
[RFC5142]). If the Result-Code AVP is set to any other value, then [RFC5142]). If the Result-Code AVP is set to any other value, then
the HA SHOULD initiate the HA switch procedure towards the MN. The the HA SHOULD initiate the HA switch procedure towards the MN. The
address information of the assigned HA is defined in the MIP6-Agent- address information of the assigned HA is defined in the MIP6-Agent-
Info AVP. Info AVP.
6.7. MIP-Careof-Address AVP 6.7. MIP-Careof-Address AVP
The MIP-Careof-Address AVP (AVP Code TBD) is of type Address and The MIP-Careof-Address AVP (AVP Code TBD) is of type Address and
contains the IPv6 Care-of Address of the Mobile Node. The HA contains the IPv6 or the IPv4 Care-of Address of the Mobile Node.
extracts this IP address from the received BU message. The HA extracts this IP address from the received BU message.
6.8. MIP-Authenticator AVP 6.8. MIP-Authenticator AVP
The MIP-Authenticator AVP (AVP Code TBD) is of type OctetString and The MIP-Authenticator AVP (AVP Code TBD) is of type OctetString and
contains the Authenticator Data from the received BU message. The HA contains the Authenticator Data from the received BU message. The HA
extracts this data from the MN-AAA Mobility Message Authentication extracts this data from the MN-AAA Mobility Message Authentication
Option included in the received BU message. The HA includes this AVP Option included in the received BU message.
in the MIR message and sets the Diameter server is expected to return
the key material required for the calculation and validation of the When the MIP6-Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA, this
Mobile IPv6 MN-HA Authentication Option (and the MIP6-Auth-Mode AVP AVP MUST be present in the MIR message.
is set to value MIP6_AUTH_MN_AAA).
6.9. MIP-MAC-Mobility-Data AVP 6.9. MIP-MAC-Mobility-Data AVP
The MIP-MAC-Mobility-Data AVP (AVP Code TBD) is of type OctetString The MIP-MAC-Mobility-Data AVP (AVP Code TBD) is of type OctetString
and contains the calculated MAC_Mobility_Data, as defined in and contains the MAC_Mobility_Data calculated by the HA as defined in
[RFC4285]. The HA includes this AVP in the MIR message when the MN- [RFC4285] for the MN-AAA Mobility Message Authentication Option.
AAA Mobility Message Authentication Option is available in the
received BU and the Diameter server is expected to return the key When the MIP6-Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA, this
material required for the calculation and validation of the Mobile AVP MUST be present in the MIR message.
IPv6 MN-HA Authentication Option (and the MIP6-Auth-Mode AVP is set
to value MIP6_AUTH_MN_AAA).
6.10. MIP-Session-Key AVP 6.10. MIP-Session-Key AVP
The MIP-Session-Key AVP (AVP Code 343) is of type OctetString and The MIP-Session-Key AVP (AVP Code 343) is of type OctetString and
contains the MN-HA shared secret (i.e., the session key) for the contains the MN-HA shared secret (i.e., the session key) for the
associated Mobile IPv6 MH-HA authentication option. When the associated Mobile IPv6 MH-HA authentication option. When the
Diameter server computes the session key it is placed in this AVP. Diameter server computes the session key it is placed in this AVP.
How the Diameter server computes the session key is not defined in
this specification. The Session key derivation is deployment
specific and needs to be defines in a respective deployment specific
system specification.
This AVP is re-used from [RFC4004]. This AVP is re-used from [RFC4004].
6.11. MIP-MSA-Lifetime AVP 6.11. MIP-MSA-Lifetime AVP
The MIP-MSA-Lifetime AVP (AVP Code 367) is of type Unsigned32 and The MIP-MSA-Lifetime AVP (AVP Code 367) is of type Unsigned32 and
represents the period of time (in seconds) for which the session key represents the period of time (in seconds) for which the session key
(see Section 6.10) is valid. The associated session key MUST NOT be (see Section 6.10) is valid. The associated session key MUST NOT be
used if the lifetime has expired. used if the lifetime has expired.
skipping to change at page 29, line 39 skipping to change at page 28, line 21
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 ]
The MIP-MN-HA-SPI sub-AVP within the MIP-MN-HA-MSA grouped AVP The MIP-MN-HA-SPI sub-AVP within the MIP-MN-HA-MSA grouped AVP
identifies the security association required for the validation of identifies the security association required for the validation of
the Mobile IPv6 MN-HA Authentication Option. the Mobile IPv6 MN-HA Authentication Option. The absence of the MIP-
Replay-Mode AVP MUST be treated as no replay protection was selected.
6.13. MIP-Algorithm-Type AVP 6.13. MIP-Algorithm-Type AVP
The MIP-Algorithm-Type AVP (AVP Code 345) is of type Enumerated and The MIP-Algorithm-Type AVP (AVP Code 345) is of type Enumerated and
contains Algorithm identifier for the associated Mobile IPv6 MN-HA contains 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 [RFC4004] that also
fulfill current RFC 4285 requirements. fulfill current RFC 4285 requirements. This AVP is re-used from
[RFC4004].
This AVP is re-used from [RFC4004]. When the MIP6-Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA, and the
Diameter server returns a valid MIP-MN-HA-MSA AVP in the MIA message,
this AVP MUST be present inside the MIP-MN-HA-MSA AVP.
6.14. MIP-Replay-Mode AVP 6.14. MIP-Replay-Mode AVP
The MIP-Replay-Mode AVP (AVP Code 346) is of type Enumerated and The MIP-Replay-Mode AVP (AVP Code 346) is of type Enumerated and
contains the replay mode the HA for authenticating the mobile node. contains the replay mode the HA for authenticating the mobile node.
The replay modes, defined in RFC 4004 [RFC4004], are supported. Out of all possible replay modes defined in [RFC4004], the following
are supported by this specification:
1 None
2 Timestamp
This AVP is re-used from [RFC4004]. This AVP is re-used from [RFC4004].
6.15. MIP6-Feature-Vector AVP 6.15. MIP6-Feature-Vector AVP
The MIP6-Feature-Vector AVP (AVP Code TBD) is of type Unsigned64 and The MIP6-Feature-Vector AVP (AVP Code 124) is defined in [RFC5447].
defined in [I-D.ietf-dime-mip6-integrated]. This document defines a However, this specification does not define any Mobile IPv6 split
new capability flag for signaling the support of Mobile IPv6 split scenario bootstrapping specific capability flag.
scenario bootstrapping.
MIP6_SPLIT (0x0000000100000000)
When this flag is set by the NAS then it means that the Mobile
IPv6 split scenario bootstrapping functionality is supported by
the NAS. When this flag is set by the Diameter server then the
Mobile IPv6 split scenario bootstrapping is supported by the
Diameter server.
6.16. MIP-Timestamp AVP 6.16. MIP-Timestamp AVP
The MIP-Timestamp AVP (AVP Code TBD) is of type Time and may contain The MIP-Timestamp AVP (AVP Code TBD) is of type OctetString and
the timestamp value from the Mobility message replay protection contains eight octets timestamp value (i.e. 64 bits timestamp) from
option, defined in [RFC4285]. The HA extracts this value from the the Mobility message replay protection option, defined in [RFC4285].
received BU message, if available. The HA includes this AVP in the The HA extracts this value from the received BU message, if
MIR message when the MN-AAA Mobility Message Authentication Option is available. The HA includes this AVP in the MIR message when the MN-
available in the received BU and the Diameter server is expected to AAA Mobility Message Authentication Option is available in the
return the key material required for the calculation and validation received BU and the Diameter server is expected to return the key
of the Mobile IPv6 MN-HA Authentication Option (and the MIP6-Auth- material required for the calculation and validation of the Mobile
Mode AVP is set to value MIP6_AUTH_MN_AAA). IPv6 MN-HA Authentication Option (and the MIP6-Auth-Mode AVP is set
to value MIP6_AUTH_MN_AAA).
6.17. QoS-Capability AVP 6.17. QoS-Capability AVP
The QoS-Capability AVP is defined in [I-D.ietf-dime-qos-attributes] The QoS-Capability AVP is defined in [I-D.ietf-dime-qos-attributes]
and contains a list of supported Quality of Service profiles. and contains a list of supported Quality of Service profiles.
6.18. QoS-Resources AVP 6.18. QoS-Resources AVP
The QoS-Resources AVP is defined in [I-D.ietf-dime-qos-attributes] The QoS-Resources AVP is defined in [I-D.ietf-dime-qos-attributes]
and provides QoS and packet filtering capabilities. and provides QoS and packet filtering capabilities.
6.19. Chargeable-User-Identity AVP 6.19. Chargeable-User-Identity AVP
The Chargeable-User-Identity AVP (AVP code 89) is of type OctetString The Chargeable-User-Identity AVP (AVP code 89) is of type OctetString
and contains an unique temporary handle of the user. The Chargeable- and contains an unique temporary handle of the user. The Chargeable-
User-Identity is defined in RFC 4372 [RFC4372]. User-Identity is defined in [RFC4372].
6.20. MIP6-Auth-Mode AVP 6.20. MIP6-Auth-Mode AVP
The MIP6-Auth-Mode (AVP Code TBD) is of type Enumerated and contains The MIP6-Auth-Mode (AVP Code TBD) is of type Enumerated and contains
information of the used Mobile IPv6 Authentication Protocol mode. information of the used Mobile IPv6 Authentication Protocol mode.
This specification defines only one value MIP6_AUTH_MN_AAA and the This specification defines only one value MIP6_AUTH_MN_AAA and the
corresponding AAA interactions when MN-AAA security association is corresponding AAA interactions when MN-AAA security association is
used to authenticate the Binding Update. When the MIP6-Auth_Mode AVP used to authenticate the Binding Update as described in [RFC4285].
is set to the value of MIP6_AUTH_MN_AAA, the Auth-Request-Type AVP When the MIP6-Auth_Mode AVP is set to the value of MIP6_AUTH_MN_AAA,
MUST be set to the value of AUTHORIZE_AUTHENTICATE. the Auth-Request-Type AVP MUST be set to the value of
AUTHORIZE_AUTHENTICATE.
If the Diameter server does not support the Mobile IPv6 If the Diameter server does not support the Mobile IPv6
Authentication Protocol usage mode proposed by the HA, then the Authentication Protocol usage mode proposed by the HA, then the
Diameter server MUST fail the authentication/authorization and MUST Diameter server MUST fail the authentication/authorization and MUST
set the Result-Code AVP to the value of DIAMETER_ERROR_AUTH_MODE. set the Result-Code AVP to the value of DIAMETER_ERROR_AUTH_MODE.
6.21. Accounting AVPs 6.21. Accounting AVPs
Diameter Mobile IPv6 applications, either MIP6I or MIP6A, are used in Diameter Mobile IPv6 applications, either MIP6I or MIP6A, are used in
the case of the coupled account model. Diameter Mobile IPv4 the case of the coupled account model. Diameter Mobile IPv4
skipping to change at page 35, line 22 skipping to change at page 34, line 22
MIP-MN-HA-SPI | 0 | 0 | 0-1 | 0 | MIP-MN-HA-SPI | 0 | 0 | 0-1 | 0 |
MIP6-Agent-Info | 1 | 0-1 | 1 | 0-1 | MIP6-Agent-Info | 1 | 0-1 | 1 | 0-1 |
MIP-Careof-Address | 0 | 0 | 0-1 | 0 | MIP-Careof-Address | 0 | 0 | 0-1 | 0 |
MIP-Authenticator | 0 | 0 | 0-1 | 0 | MIP-Authenticator | 0 | 0 | 0-1 | 0 |
MIP-MAC-Mobility-Data | 0 | 0 | 0-1 | 0 | MIP-MAC-Mobility-Data | 0 | 0 | 0-1 | 0 |
MIP-MSA-Lifetime | 0 | 0 | 0 | 1 | MIP-MSA-Lifetime | 0 | 0 | 0 | 1 |
MIP-MN-HA-MSA | 0 | 0 | 0 | 0-1 | MIP-MN-HA-MSA | 0 | 0 | 0 | 0-1 |
MIP-Timestamp | 0 | 0 | 0-1 | 0-1 | MIP-Timestamp | 0 | 0 | 0-1 | 0-1 |
User-Name | 0-1 | 0-1 | 1 | 0-1 | User-Name | 0-1 | 0-1 | 1 | 0-1 |
Service-Selection | 0-1 | 0-1 | 0-1 | 0-1 | Service-Selection | 0-1 | 0-1 | 0-1 | 0-1 |
QoS-Resources | *0 | *0 | *0 | *0 | QoS-Resources | 0+ | 0+ | 0+ | 0+ |
QoS-Capability | 0-1 | 0 | 0-1 | 0 | QoS-Capability | 0-1 | 0 | 0-1 | 0 |
Chargeable-User-Identity | 0-1 | 0-1 | 0-1 | 0-1 | Chargeable-User-Identity | 0-1 | 0-1 | 0-1 | 0-1 |
MIP6-Auth-Mode | 0 | 0 | 1 | 0 | MIP6-Auth-Mode | 0 | 0 | 1 | 0 |
+-----+-----+-----+-----+ +-----+-----+-----+-----+
8.2. Coupled Accounting Model AVP Table 8.2. Coupled Accounting Model AVP Table
The table in this section is used to represent which AVPs defined in The table in this section is used to represent which AVPs defined in
this document are to be present in the Accounting messages, as this document are to be present in the Accounting messages, as
defined in [RFC3588]. defined in [RFC3588].
skipping to change at page 36, line 22 skipping to change at page 35, line 22
Accounting-Output-Octets | 0-1 | 0-1 | Accounting-Output-Octets | 0-1 | 0-1 |
Accounting-Output-Packets | 0-1 | 0-1 | Accounting-Output-Packets | 0-1 | 0-1 |
Acct-Multi-Session-Id | 0-1 | 0-1 | Acct-Multi-Session-Id | 0-1 | 0-1 |
Acct-Session-Time | 0-1 | 0-1 | Acct-Session-Time | 0-1 | 0-1 |
MIP6-Feature-Vector | 0-1 | 0-1 | MIP6-Feature-Vector | 0-1 | 0-1 |
MIP6-Agent-Info | 0-1 | 0-1 | MIP6-Agent-Info | 0-1 | 0-1 |
MIP-Mobile-Node-Address | 0-2 | 0-2 | MIP-Mobile-Node-Address | 0-2 | 0-2 |
Event-Timestamp | 0-1 | 0 | Event-Timestamp | 0-1 | 0 |
MIP-Careof-Address | 0-1 | 0 | MIP-Careof-Address | 0-1 | 0 |
Service-Selection | 0-1 | 0 | Service-Selection | 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 | 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
IANA is requested to allocate a command code values for the following IANA is requested to allocate a command code value for the following
new commands from the Command Code namespace defined in [RFC3588]. new commands from the Command Code namespace defined in [RFC3588].
See Section 5 for the assignment of the namespace in this See Section 5 for the assignment of the namespace in this
specification. specification.
Command Code | Value Command Code | Value
-----------------------------------+------ -----------------------------------+------
MIP6-Request (MIR) | TBD MIP6-Request (MIR) | TBD
MIP6-Answer (MIA) | TBD MIP6-Answer (MIA) | TBD
9.2. AVP Codes 9.2. AVP Codes
skipping to change at page 38, line 24 skipping to change at page 37, line 24
Mobile IPv6 IKE" and "Diameter Mobile IPv6 Auth" from the Application Mobile IPv6 IKE" and "Diameter Mobile IPv6 Auth" from the Application
Identifier namespace defined in [RFC3588]. Identifier namespace defined in [RFC3588].
Application Identifier | Value Application Identifier | Value
-----------------------------------+------ -----------------------------------+------
Diameter Mobile IPv6 IKE (MIP6I) | TBD Diameter Mobile IPv6 IKE (MIP6I) | TBD
Diameter Mobile IPv6 Auth (MIP6A) | TBD Diameter Mobile IPv6 Auth (MIP6A) | TBD
9.5. Namespaces 9.5. Namespaces
This specification defines new values to the "Mobility Capability"
registry (see [I-D.ietf-dime-mip6-integrated]) for use with the MIP6-
Feature-Vector AVP:
Token | Value | Description
---------------------------------+----------------------+------------
MIP6_SPLIT | 0x0000000100000000 | RFC TBD
IANA is requested to create a new registry "MIP6 Authentication Mode" IANA is requested to create a new registry "MIP6 Authentication Mode"
registry for use with the enumerated MIP6-Auth-Mode AVP. The registry for use with the enumerated MIP6-Auth-Mode AVP. The
registry will initially contain the following values: registry will initially contain the following value:
Token | Value | Description Token | Value | Description
---------------------------------------------+----------+------------ ---------------------------------------------+----------+------------
MIP6_AUTH_MN_AAA | 1 | RFC TBD MIP6_AUTH_MN_AAA | 1 | RFC TBD
Allocation of new values follow the example policies described in Allocation of new values follow the example policies described in
[RFC5226] new values for the MIP6-Auth-Mode AVP will be assigned [RFC5226] new values for the MIP6-Auth-Mode AVP will be assigned
based on the "Specification Required" policy. based on the "Specification Required" policy. The value 0 (zero) is
reserved and the maximum value is 4294967295 (i.e. 2^32-1).
10. Security Considerations 10. Security Considerations
The security considerations for the Diameter interaction required to The security considerations for the Diameter interaction required to
accomplish the split scenario are described in in [RFC5026]. accomplish the split scenario are described in [RFC5026].
Additionally, the security considerations of the Diameter Base Additionally, the security considerations of the Diameter Base
protocol [RFC3588], Diameter EAP application [RFC4072] are applicable protocol [RFC3588], Diameter EAP application [RFC4072] are applicable
to this document. to this document.
The Diameter messages may be transported between the HA and the The Diameter messages may be transported between the HA and the
Diameter server via one or more AAA brokers or Diameter agents. In Diameter server via one or more AAA brokers or Diameter agents. In
this case the HA to the Diameter server AAA communication rely on the this case the HA to the Diameter server AAA communication rely on the
security properties of the intermediate AAA brokers and Diameter security properties of the intermediating AAA inter-connection
agents (such as proxies). networks, AAA brokers and Diameter agents (such as proxies).
In case of the Authentication Protocol for Mobile IPv6 [RFC4285],
this specification expects that the Diameter server derives the MN-HA
Security Association and returns the associated session key (i.e. the
MN-HA shared session key) to the HA. However, this specification
does not define nor other IETF specification defines how the Diameter
server actually derives required keys. The details of the key
derivation depends on the deployment where this specification is used
and therefore the security properties of the system depend on how
this is done.
11. Acknowledgements 11. Acknowledgements
The authors would like to thank Jari Arkko, Tolga Asversen, Pasi The authors would like to thank Jari Arkko, Tolga Asversen, Pasi
Eronen, Santiago Zapata Hernandez, Anders Kristensen, Avi Lior, John Eronen, Santiago Zapata Hernandez, Anders Kristensen, Avi Lior, John
Loughney, Ahmad Muhanna, Behcet Sarikaya, Basavaraj Patil, Vijay Loughney, Ahmad Muhanna, Behcet Sarikaya, Basavaraj Patil, Vijay
Devarapalli, Lionel Morand, Domagoj Premec, Semyon Mizikovsky and Devarapalli, Lionel Morand, Domagoj Premec, Semyon Mizikovsky and
Yoshihiro Ohba for all the useful discussions. Ahmad Muhanna Yoshihiro Ohba for all the useful discussions. Ahmad Muhanna
provided a detailed review of the document in August 2007. provided a detailed review of the document in August 2007. Pasi
Eronen provided detailed comments and text proposals during the IESG
review that helped to improved this document greatly.
We would also like to thank our Area Director, Dan Romascanu, for his We would also like to thank our Area Director, Dan Romascanu, for his
support. support.
Hannes Tschofenig would like to thank the European Commission support Hannes Tschofenig would like to thank the European Commission support
in the co-funding of the ENABLE project, where this work is partly in the co-funding of the ENABLE project, where this work is partly
being developed. being developed.
Julien Bournelle would like to thank GET/INT since he began this work Julien Bournelle would like to thank GET/INT since he began this work
while he was under their employ. while he was under their employ.
Madjid Nakhjiri would like to thank Huawei USA as most of his Madjid Nakhjiri would like to thank Huawei USA as most of his
contributions to this draft were possible while he was under their contributions to this draft were possible while he was under their
employ. employ.
12. References 12. References
12.1. Normative References 12.1. Normative References
[I-D.ietf-dime-mip6-integrated]
Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C.,
and K. Chowdhury, "Diameter Mobile IPv6: Support for
Network Access Server to Diameter Server Interaction",
draft-ietf-dime-mip6-integrated-11 (work in progress),
November 2008.
[I-D.ietf-dime-qos-attributes] [I-D.ietf-dime-qos-attributes]
Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones, M., Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones, M.,
and A. Lior, "Quality of Service Attributes for Diameter", and A. Lior, "Quality of Service Attributes for Diameter",
draft-ietf-dime-qos-attributes-09 (work in progress), draft-ietf-dime-qos-attributes-11 (work in progress),
December 2008. February 2009.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Arkko, "Diameter Base Protocol", RFC 3588, September 2003. Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
[RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support [RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
in IPv6", RFC 3775, June 2004. in IPv6", RFC 3775, June 2004.
skipping to change at page 41, line 47 skipping to change at page 40, line 40
August 2005. August 2005.
[RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible [RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
Authentication Protocol (EAP) Application", RFC 4072, Authentication Protocol (EAP) Application", RFC 4072,
August 2005. August 2005.
[RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. [RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K.
Chowdhury, "Mobile Node Identifier Option for Mobile IPv6 Chowdhury, "Mobile Node Identifier Option for Mobile IPv6
(MIPv6)", RFC 4283, November 2005. (MIPv6)", RFC 4283, November 2005.
[RFC4285] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K.
Chowdhury, "Authentication Protocol for Mobile IPv6",
RFC 4285, January 2006.
[RFC4306] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol", [RFC4306] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol",
RFC 4306, December 2005. RFC 4306, December 2005.
[RFC4372] Adrangi, F., Lior, A., Korhonen, J., and J. Loughney, [RFC4372] Adrangi, F., Lior, A., Korhonen, J., and J. Loughney,
"Chargeable User Identity", RFC 4372, January 2006. "Chargeable User Identity", RFC 4372, January 2006.
[RFC4877] Devarapalli, V. and F. Dupont, "Mobile IPv6 Operation with [RFC4877] 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.
[RFC5026] Giaretta, G., Kempf, J., and V. Devarapalli, "Mobile IPv6 [RFC5026] 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.
[RFC5142] Haley, B., Devarapalli, V., Deng, H., and J. Kempf, [RFC5142] Haley, B., Devarapalli, V., Deng, H., and J. Kempf,
"Mobility Header Home Agent Switch Message", RFC 5142, "Mobility Header Home Agent Switch Message", RFC 5142,
January 2008. January 2008.
[RFC5149] Korhonen, J., Nilsson, U., and V. Devarapalli, "Service
Selection for Mobile IPv6", RFC 5149, February 2008.
[RFC5447] Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C.,
and K. Chowdhury, "Diameter Mobile IPv6: Support for
Network Access Server to Diameter Server Interaction",
RFC 5447, February 2009.
12.2. Informative References 12.2. Informative References
[I-D.ietf-dime-app-design-guide] [I-D.ietf-dime-app-design-guide]
Fajardo, V., Asveren, T., Tschofenig, H., McGregor, G., Fajardo, V., Asveren, T., Tschofenig, H., McGregor, G.,
and J. Loughney, "Diameter Applications Design and J. Loughney, "Diameter Applications Design
Guidelines", draft-ietf-dime-app-design-guide-08 (work in Guidelines", draft-ietf-dime-app-design-guide-08 (work in
progress), November 2008. progress), November 2008.
[I-D.ietf-mext-aaa-ha-goals] [I-D.ietf-mext-aaa-ha-goals]
Giaretta, G., Guardini, I., Demaria, E., Bournelle, J., Giaretta, G., Guardini, I., Demaria, E., Bournelle, J.,
and R. Lopez, "AAA Goals for Mobile IPv6", and R. Lopez, "AAA Goals for Mobile IPv6",
draft-ietf-mext-aaa-ha-goals-01 (work in progress), draft-ietf-mext-aaa-ha-goals-01 (work in progress),
May 2008. May 2008.
[I-D.ietf-mext-nemo-v4traversal] [I-D.ietf-mext-nemo-v4traversal]
Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and
Routers (DSMIPv6)", draft-ietf-mext-nemo-v4traversal-07 Routers", draft-ietf-mext-nemo-v4traversal-10 (work in
(work in progress), December 2008. progress), April 2009.
[RFC4285] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K.
Chowdhury, "Authentication Protocol for Mobile IPv6",
RFC 4285, January 2006.
[RFC4640] Patel, A. and G. Giaretta, "Problem Statement for [RFC4640] Patel, A. and G. Giaretta, "Problem Statement for
bootstrapping Mobile IPv6 (MIPv6)", RFC 4640, bootstrapping Mobile IPv6 (MIPv6)", RFC 4640,
September 2006. September 2006.
[RFC5149] Korhonen, J., Nilsson, U., and V. Devarapalli, "Service
Selection for Mobile IPv6", RFC 5149, February 2008.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
Authors' Addresses Authors' Addresses
Jouni Korhonen (editor) Jouni Korhonen (editor)
Nokia Siemens Networks Nokia Siemens Networks
Linnoitustie 6 Linnoitustie 6
Espoo FIN-02600 Espoo FIN-02600
 End of changes. 65 change blocks. 
329 lines changed or deleted 305 lines changed or added

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