draft-ietf-dime-mip6-split-03.txt   draft-ietf-dime-mip6-split-04.txt 
Diameter Maintenance and J. Bournelle Diameter Maintenance and J. Bournelle
Extensions (DIME) France Telecom R&D Extensions (DIME) France Telecom R&D
Internet-Draft G. Giaretta Internet-Draft G. Giaretta
Intended status: Standards Track Qualcomm Intended status: Standards Track Qualcomm
Expires: December 31, 2007 H. Tschofenig Expires: January 9, 2008 H. Tschofenig
Nokia Siemens Networks Nokia Siemens Networks
M. Nakhjiri M. Nakhjiri
Huawei Huawei USA
June 29, 2007 July 8, 2007
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-03.txt draft-ietf-dime-mip6-split-04.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 40 skipping to change at page 1, line 40
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 December 31, 2007. This Internet-Draft will expire on January 9, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
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
that specifies the interaction between the Home Agent and the specifies the interaction between a Mobile IP Home Agent and the
Diameter server. Two different mechanisms for authentication of a MN Diameter server. Two different mechanisms for authentication of a MN
to the HA are supported. The first method consists of performing the to the HA are supported. The first method consists of performing the
Internet Key Exchange v2 (IKEv2) protocol along with the Extensible Internet Key Exchange v2 (IKEv2) protocol along with the Extensible
Authentication Protocol (EAP) with the Diameter server, while the Authentication Protocol (EAP) with the Diameter server, while the
second method utilizes the Mobile IPv6 Authentication option, as second method utilizes the Mobile IPv6 Authentication option, as
defined in RFC 4285. For Internet Key Exchange v2 with EAP-based defined in RFC 4285. For Internet Key Exchange v2 with EAP-based
authentication, the Diameter Mobile IPv6 application, defined in this authentication, the Diameter Mobile IPv6 application, defined in this
document, reuses the commands defined in the Diameter EAP document, reuses the commands defined in the Diameter EAP
application, while for supporting the RFC 4285-style MIPv6 application, while for supporting the RFC 4285-style MIPv6
Authentication Options, a new Diameter application is defined that Authentication Options, a new Diameter application and new command
reuses the Diameter Mobile IPv4 application. codes are defined.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Advertising Application Support . . . . . . . . . . . . . . . 3 3. Advertising Application Support . . . . . . . . . . . . . . . 5
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Protocol Description . . . . . . . . . . . . . . . . . . . . . 5 5. Protocol Description . . . . . . . . . . . . . . . . . . . . . 6
5.1. Support for Mobile IPv6 with IKEv2 and IPsec . . . . . . . 5 5.1. Support for Mobile IPv6 with IKEv2 and IPsec . . . . . . . 6
5.2. Support for the Mobile IPv6 Authentication Protocol . . . 7 5.2. Support for the Mobile IPv6 Authentication Protocol . . . 8
5.3. Mobile IPv6 Session Management . . . . . . . . . . . . . . 8 5.3. Mobile IPv6 Session Management . . . . . . . . . . . . . . 9
5.3.1. Session-Termination-Request Command . . . . . . . . . 8 5.3.1. Session-Termination-Request Command . . . . . . . . . 9
5.3.2. Session-Termination-Answer Command . . . . . . . . . . 8 5.3.2. Session-Termination-Answer Command . . . . . . . . . . 9
5.3.3. Abort-Session-Request Command . . . . . . . . . . . . 8 5.3.3. Abort-Session-Request Command . . . . . . . . . . . . 9
5.3.4. Abort-Session-Answer Command . . . . . . . . . . . . . 9 5.3.4. Abort-Session-Answer Command . . . . . . . . . . . . . 10
6. Command-Code and AVP Values . . . . . . . . . . . . . . . . . 9 5.4. Accounting for Mobile IPv6 services . . . . . . . . . . . 10
6.1. Command Code for EAP-based Authentication . . . . . . . . 9 5.4.1. Accounting-Request Command . . . . . . . . . . . . . . 10
6.1.1. Diameter-EAP-Request (DER) . . . . . . . . . . . . . . 9 5.4.2. Accounting-Answer Command . . . . . . . . . . . . . . 11
6.1.2. Diameter-EAP-Answer (DEA) . . . . . . . . . . . . . . 10 6. Command-Code and AVP Values . . . . . . . . . . . . . . . . . 11
6.2. Command Codes for RFC 4285 Support . . . . . . . . . . . . 10 6.1. Command Code for EAP-based Authentication . . . . . . . . 11
6.2.1. MIP6-Request-Message . . . . . . . . . . . . . . . . . 11 6.1.1. Diameter-EAP-Request (DER) . . . . . . . . . . . . . . 12
6.2.2. MIP6-Answer-Message . . . . . . . . . . . . . . . . . 11 6.1.2. Diameter-EAP-Answer (DEA) . . . . . . . . . . . . . . 12
6.2.3. Diameter AVPs . . . . . . . . . . . . . . . . . . . . 12 6.2. Command Codes for RFC 4285 Support . . . . . . . . . . . . 13
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 6.2.1. MIP6-Request-Message . . . . . . . . . . . . . . . . . 13
7.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 14 6.2.2. MIP6-Answer-Message . . . . . . . . . . . . . . . . . 14
7.2. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 15 6.2.3. Diameter AVPs . . . . . . . . . . . . . . . . . . . . 15
7.3. Application Identifier . . . . . . . . . . . . . . . . . . 15 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
8. Security Considerations . . . . . . . . . . . . . . . . . . . 15 7.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 18
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 7.2. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 18
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 7.3. Application Identifier . . . . . . . . . . . . . . . . . . 18
10.1. Normative References . . . . . . . . . . . . . . . . . . . 15 8. Security Considerations . . . . . . . . . . . . . . . . . . . 18
10.2. Informative References . . . . . . . . . . . . . . . . . . 16 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Intellectual Property and Copyright Statements . . . . . . . . . . 18 10.1. Normative References . . . . . . . . . . . . . . . . . . . 19
10.2. Informative References . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20
Intellectual Property and Copyright Statements . . . . . . . . . . 22
1. Introduction 1. Introduction
Performing the Mobile IPv6 protocol [1], requires assignment of a Performing the Mobile IPv6 protocol [1], requires the Mobile Node
Home Agent (HA) to a Mobile Node (MN). The MN needs to register its (MN) to own a Home Address (HoA) and assignment of a Home Agent (HA)
Mobile IPv6 session with the HA in order facilitate its reachability to MN. The MN needs to register its Mobile IPv6 session with the HA
and mobility, when away from home. in order facilitate its reachability and mobility, when away from
home. The registration process itself requires establishment of
IPsec security associations (SA) and cryptographic material between
the MN and HA. Providing the collection of home address, HA address
and keying material to establish the IP SA is generaally referred to
as the Mobile IPv6 bootstrapping problem [reference to RFC4640]. The
purpose of this specification is to provide Diameter support for such
bootstrapping in a split scenario [2] in a manner that satisfies the
requirements defined in [13].
From an operator (mobility service provider, MSP) perspective, it is From an operator (mobility service provider, MSP) perspective, it is
important to verify that the MN is authenticated and authorized to important to verify that the MN is authenticated and authorized to
utilize Mobile IPv6 service and that such services are accounted for. utilize Mobile IPv6 service and that such services are accounted for.
Thus, prior to processing the Mobile IPv6 service requests, the HA, Only when the MN is authenticated and authorized, the MSP allows the
participates in the authentication of the MN to verify the MN's boostrapping of Mobile IPv6 parameters at the MN and HA. Thus, prior
identity. The HA also participates in the Mobile IPv6 authorization to processing the Mobile IPv6 service requests, the HA, participates
process involving the Diameter infrastrucure. The HA due to its role in the authentication of the MN to verify the MN's identity. The HA
in traffic forwarding, also performs accounting for the Mobile IPv6 also participates in the Mobile IPv6 authorization process involving
service provided to the MN. the Diameter infrastrucure. The HA due to its role in traffic
forwarding, also performs accounting for the Mobile IPv6 service
provided to the MN.
Mobile IPv6 specifications allow two different methods for MN Mobile IPv6 specifications allow two different methods for MN
authentication, one based on IKEv2 and EAP [2], and another based on authentication, one based on IKEv2 and EAP [3], and another based on
the Mobile IPv6 Authentication Option [3]. The goal of this document the Mobile IPv6 Authentication Option [4]. The goal of this document
is to specify the Diameter procedures associated with the Mobile IPv6 is to specify the Diameter procedures associated with the Mobile IPv6
bootstrapping between the HA and the Diameter server for these two bootstrapping between the HA and the Diameter server for these two
Mobile IP authentication approaches. Mobile IP authentication approaches.
For that reason the Diameter Mobile IPv6 application provides two For that reason the Diameter Mobile IPv6 application provides two
different sets of commands. The first set of commands reuse the different sets of commands. The first set of commands reuse the
command already define in Diameter EAP application (though using the command already define in Diameter EAP application (though using the
Diameter Mobile IPv6 Application-Id). While the second set of Diameter Mobile IPv6 Application-Id), while the second set of
commands are new for Diameter and provide support the Mobile IPv6 commands are new for Diameter and provide support the Mobile IPv6
Authentication Option, defined in RFC 4285. Authentication Option, defined in RFC 4285.
For authorization signaling and management of Mobile IPv6 session for
the MN, this specification will use the existing procedures from base
Diameter specification [5].
For accounting of Mobile IPv6 services provided to the MN, this
specification uses the accounting application defined in [5].
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [4]. document are to be interpreted as described in RFC 2119 [6].
The MIPv6 bootstrapping terminology is taken from [5]. The MIPv6 bootstrapping terminology is taken from [7].
3. Advertising Application Support 3. Advertising Application Support
Diameter nodes conforming to this specification MUST advertise Diameter nodes conforming to this specification MUST advertise
support by including the Diameter Mobile IPv6 Application ID value of support by including the Diameter Mobile IPv6 Application ID value of
[TO BE ASSIGNED BY IANA] in the Auth-Application-Id AVP of the [TO BE ASSIGNED BY IANA] in the Auth-Application-Id AVP of the
Capabilities-Exchange-Request and Capabilities-Exchange-Answer Capabilities-Exchange-Request and Capabilities-Exchange-Answer
command [6] command [5]. The Acct-Application-id AVP needs to include the
Diameter Base Accounting Application ID value of 3 (to support the
split accounting model [draft-ietf-dime-app-design-guide]).
4. Overview 4. Overview
One task of the Mobile IPv6 bootstrapping procedure is to assign an One task of the Mobile IPv6 bootstrapping procedure is to assign an
appropriate HA to the MN. Furthermore, authorization and successful appropriate HA to the MN. Furthermore, authorization and successful
delivery of Mobile IPv6 to a MN through a HA, requires the HA to act delivery of Mobile IPv6 to a MN through a HA, requires the HA to act
as a client to the Diameter infrastructure interconnecting it to the as a client to the Diameter infrastructure interconnecting it to the
MSP. As a Diameter client, the HA needs to perform the following MSP. As a Diameter client, the HA needs to perform the following
operations: operations:
skipping to change at page 5, line 42 skipping to change at page 6, line 44
[Editor's Note: A description of the relationship with the front-end [Editor's Note: A description of the relationship with the front-end
protocols is needed.] protocols is needed.]
5. Protocol Description 5. Protocol Description
5.1. Support for Mobile IPv6 with IKEv2 and IPsec 5.1. Support for Mobile IPv6 with IKEv2 and IPsec
The use of IKEv2 between the MN and the HA allows the HA to The use of IKEv2 between the MN and the HA allows the HA to
authenticate the MN. When EAP is used with IKEv2, the Diameter EAP authenticate the MN. When EAP is used with IKEv2, the Diameter EAP
application, as defined in [7], is re-used. AVPs specific to Mobile application, as defined in [8], is re-used. AVPs specific to Mobile
IPv6 bootstrapping are added to this command. IPv6 bootstrapping are added to this command.
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.
Mobile Home Diameter Mobile Home Diameter
Node Agent Server Node Agent Server
------ ----- -------- ------ ----- --------
IKE_SA_INIT (1,2) IKE_SA_INIT (1,2)
<------------------------------> <------------------------------>
skipping to change at page 7, line 7 skipping to change at page 8, line 7
The MN and the HA start the interaction with an IKE_SA_INIT exchange. The MN and the HA start the interaction with an IKE_SA_INIT exchange.
In this phase cryptographic algorithms are negotiated, nonces and In this phase cryptographic algorithms are negotiated, nonces and
Diffie-Hellman parameters are exchanged. Message (3) starts the Diffie-Hellman parameters are exchanged. Message (3) starts the
IKE_AUTH phase. This second phase authenticates the previous IKE_AUTH phase. This second phase authenticates the previous
messages, exchanges identities and certificates and establishes the messages, exchanges identities and certificates and establishes the
first CHILD_SA. It is used to mutually authenticate the MN (acting first CHILD_SA. It is used to mutually authenticate the MN (acting
as an IKEv2 Initiator) and the HA (acting as an IKEv2 Responder). as an IKEv2 Initiator) and the HA (acting as an IKEv2 Responder).
The identity of the user/MN is provided in the IDi field. The MN The identity of the user/MN is provided in the IDi field. The MN
indicates its willingness to be authenticated via EAP by omitting the indicates its willingness to be authenticated via EAP by omitting the
AUTH field in message 3 (see [8]). AUTH field in message 3 (see [9]).
As part of the authentication process, the MN MAY request a Home- As part of the authentication process, the MN MAY request a Home-
Address, a Home Prefix or suggests one, see [9], using a CFG_REQUEST Address, a Home Prefix or suggests one, see [2], using a CFG_REQUEST
payload in the message 3. payload in the message 3.
The HA extracts the IDi field from the message 3 and sends a The HA extracts the IDi field from the message 3 and sends a
Diameter-EAP-Request (DER) message towards the authenticating Diameter-EAP-Request (DER) message towards the authenticating
Diameter server. Diameter server.
This message is routed to the MNs Diameter server/EAP server. The This message is routed to the MNs Diameter server/EAP server. The
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
skipping to change at page 7, line 44 skipping to change at page 8, line 44
limitation. limitation.
5.2. Support for the Mobile IPv6 Authentication Protocol 5.2. Support for the Mobile IPv6 Authentication Protocol
Figure 3 describes the sequence of messages sent and received between Figure 3 describes the sequence of messages sent and received between
the MN, the HA and the Diameter server during the registration when the MN, the HA and the Diameter server during the registration when
RFC 4285 is used. Binding Update (BU) and Binding Acknowledgement RFC 4285 is used. Binding Update (BU) and Binding Acknowledgement
(BA) messages are used in the registration process. This exchange (BA) messages are used in the registration process. This exchange
triggers the Diameter interaction. triggers the Diameter interaction.
According to [3] the MN uses the Mobile Node Identifier Option, According to [4] the MN uses the Mobile Node Identifier Option,
specifically the MN-NAI mobility option as defined in [11] to specifically the MN-NAI mobility option as defined in [14] to
identify itself while authenticating with the HA. identify itself while authenticating with the HA.
The MN may use the Message Identifier option for additional replay The MN may use the Message Identifier option for additional replay
protection. The authentication option may be used by the MN to protection. The authentication option may be used by the MN to
transfer authentication data when the MN and the HA are utilizing a transfer authentication data when the MN and the HA are utilizing a
mobility SPI. mobility SPI.
The BU initiates a MIP6-Request-Message to the Diameter server and The BU initiates a MIP6-Request-Message to the Diameter server and
the corresponding response is carried in a MIP6-Answer-Message. the corresponding response is carried in a MIP6-Answer-Message.
skipping to change at page 8, line 31 skipping to change at page 9, line 31
| (including MN-ID option, | (MN-HA key) | | (including MN-ID option, | (MN-HA key) |
| Message ID option [optional], | | | Message ID option [optional], | |
| authentication option) | | | authentication option) | |
Figure 3: MIPv6 Bootstrapping using RFC 4285 Figure 3: MIPv6 Bootstrapping using RFC 4285
5.3. Mobile IPv6 Session Management 5.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 [6]. MUST support the Authorization Session State Machine defined in [5].
Moreover the following 4 commands may be exchanged between the HA and Moreover the following 4 commands may be exchanged between the HA and
the Diameter server. the Diameter server.
5.3.1. Session-Termination-Request Command 5.3.1. Session-Termination-Request Command
The Session-Termination-Request (STR) message [6] 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.
5.3.2. Session-Termination-Answer Command 5.3.2. Session-Termination-Answer Command
The Session-Termination-Answer (STA) message [6] 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.
5.3.3. Abort-Session-Request Command 5.3.3. Abort-Session-Request Command
The Abort-Session-Request (ASR) message [6] is sent by the Diameter The Abort-Session-Request (ASR) message [5] is sent by the Diameter
server to terminates the session. This fulfills one of the server to terminates the session. This fulfills one of the
requirement described in [12]. requirement described in [13].
5.3.4. Abort-Session-Answer Command 5.3.4. Abort-Session-Answer Command
The Abort-Session-Answer (ASA) message [6] 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.
5.4. Accounting for Mobile IPv6 services
The HA MUST be able act as a Diameter client collecting accounting
records needed for service control and charging. The HA MUST support
the accounting procedures (specifically the command codes mentioned
below) and the Accounting Session State Machine as defined in [5].
The command codes, exchanged between the HA and Diameter server for
accounting purposes, are provided in the following subsections.
The Diameter application design guideline [15] defines two separate
model for accounting:
Split accounting model:
According to this model, the accounting messages use the Diameter
base accounting application ID (value of 3). Since accounting is
treated as an independent application, accounting commands may be
routed separately from the rest of application messages and thus
the accounting messages generally end up in a central accounting
server. Since Diameter Mobile IPv6 application does not define
its own unique accounting commands, this is the prefered choice,
since it permits use of centralized accounting for several
applications.
Coupled accounting model:
In this model, the accounting messages will use the application ID
of the Mobile IPv6 application. This means that accounting
messages will be routed like any other Mobile IPv6 application
messages. This requires the Diameter server in charge of Mobile
IPv6 application to handle the accounting records (e.g., sends
them to a proper accounting server)..
As mentioned above, the prefered choice is to use the split
accounting model and thus choose Diameter base accounting application
ID (value of 3) for accounting messages.
5.4.1. Accounting-Request Command
The Accounting-Request command [5] is sent by the HA to the Diameter
server to exchange accounting information regarding the MN with the
Diameter server.
5.4.2. Accounting-Answer Command
The Accounting-Answer command [5] is sent by the Diameter server to
the HA to acknowledge receiving an Accounting-Request.
6. Command-Code and AVP Values 6. Command-Code and AVP Values
This section defines the command codes and AVP values used by the The following commands are defined in this section:
Diameter Mobile IPv6 application:
Command-Name Abbrev. Code Reference Application
----------------------------------------------------------------------
MIP6-Request-Message MRM XXX TBD MIP6
MIP6-Answer-Message MAM XXX TBD MIP6
Figure 4: New Command Codes
The following defines the command codes used by the Diameter Mobile
IPv6 application:
Command-Name Abbrev. Code Reference Application Command-Name Abbrev. Code Reference Application
---------------------------------------------------------------------- ----------------------------------------------------------------------
Diameter-EAP-Request DER 268 RFC 4072 EAP Diameter-EAP-Request DER 268 RFC 4072 EAP
Diameter-EAP-Answer DEA 268 RFC 4072 EAP Diameter-EAP-Answer DEA 268 RFC 4072 EAP
MIP6-Request-Message MRM XXX TBD MIP6 MIP6-Request-Message MRM XXX TBD MIP6
MIP6-Answer-Message MAM XXX TBD MIP6 MIP6-Answer-Message MAM XXX TBD MIP6
Session-Termination-Request STR 275 RFC 3588 BASE
Session-Termination-Answer STA 275 RFC 3588 BASE
Abort-Session-Request ASR 275 RFC 3588 BASE
Abort-Session-Answer ASA 275 RFC 3588 BASE
Accounting-Request ACR 271 RFC 3588 BASE
Accounting-Answer ACA 271 RFC 3588 BASE
Figure 4: Command Codes Figure 5: Command Codes
6.1. Command Code for EAP-based Authentication 6.1. Command Code for EAP-based Authentication
This document re-uses the Diameter EAP application commands. The This document re-uses the Diameter EAP application commands. The
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
------------------------------------------------------------------ ------------------------------------------------------------------
Diameter-EAP-Request DER 268 RFC 4072 EAP Diameter-EAP-Request DER 268 RFC 4072 EAP
Diameter-EAP-Answer DEA 268 RFC 4072 EAP Diameter-EAP-Answer DEA 268 RFC 4072 EAP
Figure 5: Diameter EAP command codes used for MIPv6 Bootstrapping HA Figure 6: Diameter EAP command codes used for MIPv6 Bootstrapping HA
to HAAA Interface to HAAA Interface
[Editor's Note: The subsections below do not yet show the MIPv6
specific AVPs.]
6.1.1. Diameter-EAP-Request (DER) 6.1.1. Diameter-EAP-Request (DER)
The Diameter-EAP-Request (DER) message [7], indicated by the Command- The Diameter-EAP-Request (DER) message [8], 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 [8]. 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 >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Destination-Realm } { Destination-Realm }
{ Auth-Request-Type } { Auth-Request-Type }
skipping to change at page 10, line 12 skipping to change at page 12, line 30
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 >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Destination-Realm } { Destination-Realm }
{ Auth-Request-Type } { Auth-Request-Type }
[ Destination-Host ] [ Destination-Host ]
[ NAS-Identifier ]
[ NAS-IP-Address ]
[ NAS-IPv6-Address ]
[ NAS-Port-Type ]
[ User-Name ]
{ EAP-Payload }
[ MIP6-Feature-Vector ]
[ MIP-Mobile-Node-Address ]
... ...
* [ AVP ] * [ AVP ]
6.1.2. Diameter-EAP-Answer (DEA) 6.1.2. Diameter-EAP-Answer (DEA)
The Diameter-EAP-Answer (DEA) message defined in [7], indicated by The Diameter-EAP-Answer (DEA) message defined in [8], 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 [8]. 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].
<Diameter-EAP-Answer> ::= < Diameter Header: 268, PXY > <Diameter-EAP-Answer> ::= < Diameter Header: 268, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Auth-Request-Type } { Auth-Request-Type }
{ Result-Code } { Result-Code }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
[ User-Name ] [ User-Name ]
{ EAP-Payload }
[ Authorization-Lifetime ]
[ MIP-Mobile-Node-Address ]
[ MIP6-Feature-Vector ]
... ...
* [ AVP ] * [ AVP ]
6.2. Command Codes for RFC 4285 Support 6.2. Command Codes for RFC 4285 Support
This section defines Command-Code [6] values that MUST be supported This section defines Command-Code [5] values that MUST be supported
by all Diameter implementations conforming to this specification. by all Diameter implementations conforming to this specification.
The following Command Codes are defined in this specification. The following Command Codes are defined in this specification.
Command-Name Abbreviation Code Section Command-Name Abbreviation Code Section
------------------------------------------------------------------ ------------------------------------------------------------------
MIP6-Request-Message MRM TBD Section 6.2.1 MIP6-Request-Message MRM TBD Section 6.2.1
MIP6-Answer-Message MAM TBD Section 6.2.2 MIP6-Answer-Message MAM TBD Section 6.2.2
6.2.1. MIP6-Request-Message 6.2.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. The HA uses information
found in the Binding Update to construct the following AVPs, to be found in the Binding Update to construct the following AVPs, to be
included as part of the MRM: included as part of the MRM:
o Home Address (MIP6-Home-Address AVP) o Home Address (MIP-Mobile-Node-Address AVP)
o Mobile Node NAI (User-Name AVP [6]) o Mobile Node NAI (User-Name AVP [5])
o MN-AAA Authentication Extension (MIP-MN-AAA-Auth AVP) o MN-AAA Authentication Extension (MIP-MN-AAA-Auth AVP)
If the MN's home address is zero, the HA MUST NOT include a MIP6- If the MN's home address is zero, the HA MUST NOT include a MIP-
Home-Address AVP. Mobile-Node-Address AVP.
If the MN's home address is all ones, the HA MUST include a MIP6- If the MN's home address is all ones, the HA MUST include a MIP-
Home-Address AVP, set to all ones. Mobile-Node-Address AVP, set to all ones.
The message format is shown below: The message format is shown below:
<MIP6-Request-Message> ::= < Diameter Header: 260, 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 }
[ Acct-Multi-Session-Id ] [ Acct-Multi-Session-Id ]
[ Destination-Host ] [ Destination-Host ]
[ Origin-State-Id ] [ Origin-State-Id ]
[ NAS-Identifier ]
[ NAS-IP-Address ]
[ NAS-IPv6-Address ]
[NAS-Port-Type]
{ MIP-MN-AAA-Auth } [ MIP6-Feature-Vector ]
[ MIP6-Home-Address ] [ MIP-MN-AAA-Auth ]
[ MIP-Mobile-Node-Address ]
[ Authorization-Lifetime ] [ Authorization-Lifetime ]
[ Auth-Session-State ] [ Auth-Session-State ]
* [ Proxy-Info ] * [ Proxy-Info ]
* [ Route-Record ] * [ Route-Record ]
* [ AVP ] * [ AVP ]
6.2.2. MIP6-Answer-Message 6.2.2. MIP6-Answer-Message
The MIP6-Answer-Message (MAM) message, indicated by the Command-Code The MIP6-Answer-Message (MAM) message, indicated by the Command-Code
field set to TBD and the 'R' bit cleared in the Command Flags field, field 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- is sent by the Diameter server in response to the MIP6-Request-
Message message. The User-Name MAY be included in the MAM if it is Message message. The User-Name MAY be included in the MAM if it is
present in the MRM. The Result-Code AVP MAY contain one of the present in the MRM. The Result-Code AVP MAY contain one of the
values defined in Section 6.2.3.2, in addition to the values defined values defined in Section 6.2.3.2, in addition to the values defined
in RFC 3588 [6]. in RFC 3588 [5].
An MAM message with the Result-Code AVP set to DIAMETER_SUCCESS MUST An MAM message with the Result-Code AVP set to DIAMETER_SUCCESS MUST
include the MIP-Mobile-Node-Address AVP. The MIP-Home-Agent-Address include the MIP-Mobile-Node-Address AVP. The MIP-Home-Agent-Address
AVP contains the HA assigned to the MN, while the MIP-Mobile-Node- AVP contains the HA assigned to the MN, while the MIP-Mobile-Node-
Address AVP contains the home address that was assigned. Address AVP contains the home address that was assigned.
The message format is shown below: The message format is shown below:
<MIP6-Answer-Message> ::= < Diameter Header: 260, PXY > <MIP6-Answer-Message> ::= < Diameter Header: XXX, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Result-Code } { Result-Code }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
[ Acct-Multi-Session-Id ] [ Acct-Multi-Session-Id ]
[ 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 ]
[ MIP-MN-to-HA-MSA ] [ MIP-MN-to-HA-MSA ]
[ MIP-HA-to-MN-MSA ] [ MIP-HA-to-MN-MSA ]
[ MIP-MSA-Lifetime ] [ MIP-MSA-Lifetime ]
[ MIP6-Home-Address ] [ MIP-Session-Key]
[ MIP-Mobile-Node-Address ]
* [ MIP-Filter-Rule ]
[ Origin-State-Id ] [ Origin-State-Id ]
* [ Proxy-Info ] * [ Proxy-Info ]
* [ AVP ] * [ AVP ]
[Editor's Note: The MIP-Filter-Rule is based on IPFiltrRule, which is
currently being revised. Hence, this document should refer to the
updated functionality. Furthermore, the requirements document
indicates that QoS parameters may need to conveyed to the HA. Hence,
the revised version of the QoS-Filter-Rule / QoSFilterRule being
developed with [10] has to be used.]
6.2.3. Diameter AVPs 6.2.3. Diameter AVPs
The Diameter client uses AVPs dependent on the usage of RFC 4285 [3] The Diameter client uses AVPs dependent on the usage of RFC 4285 [4]
or RFC 4877 [2]. or RFC 4877 [3].
To provide support for RFC 4285 [3] the following AVPs defined in To provide support for RFC 4285 [4] the following AVPs defined in
[10] are reused in this application: [11] are reused in this application:
o MIP-HA-to-MN-MSA AVP
o MIP-MN-to-HA-MSA AVP o MIP-HA-to-MN-MSA AVP,
o MIP-MN-to-HA-MSA AVP,
o MIP-Session-Key AVP o MIP-Session-Key AVP
o MIP-Algorithm-Type AVP o MIP-Algorithm-Type AVP
o MIP-Replay-Mode AVP o MIP-Replay-Mode AVP
o MIP-MN-AAA-Auth AVP o MIP-MN-AAA-Auth AVP
o MIP-MN-AAA-SPI AVP o MIP-MN-AAA-SPI AVP
o MIP-Auth-Input-Data-Length AVP o MIP-Auth-Input-Data-Length AVP
o MIP-Authenticator-Length AVP o MIP-Authenticator-Length AVP
o MIP-Authenticator-Offset AVP o MIP-Authenticator-Offset AVP
o MIP-MSA-Lifetime AVP o MIP-MSA-Lifetime AVP
o MIP-Mobile-Node-Address (with an IPv6 address) o MIP-Mobile-Node-Address (with an IPv6 address)
For usage with the RFC 4877 [2] only the MIP-Mobile-Node-Address AVP
(with IPv6 address) is needed since all other keying related
parameters are provided by the Diameter EAP application.
6.2.3.1. Accounting AVPs 6.2.3.1. Accounting AVPs
This document reuses the accounting AVPs defined in Diameter Mobile This document reuses the accounting AVPs defined in Diameter Mobile
IPv4 application [10], namely: IPv4 application [11], namely:
Accounting-Input-Octets: Accounting-Input-Octets:
Number of octets in IP packets received from the user Number of octets in IP packets received from the user
Accounting-Output-Octets: Accounting-Output-Octets:
Number of octets in IP packets sent by the user Number of octets in IP packets sent by the user
Accounting-Input-Packets: Accounting-Input-Packets:
Number of IP packets received from the user Number of IP packets received from the user
Accounting-Output-Packets: Accounting-Output-Packets:
Number of IP packets sent by the user. Number of IP packets sent by the user.
6.2.3.2. Result-Code AVPs 6.2.3.2. Result-Code AVPs
This section defines new Result-Code [6] 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.
[Editor's Note: This section needs to list the result codes that are [Editor's Note: This section needs to list the result codes that are
used by this application.] used by this application.]
6.2.3.3. AVP Occurence Tables 6.2.3.3. AVP Occurence Tables
The following table describes the Diameter AVPs defined by this The following table describes the Diameter AVPs defined by this
document; their AVP Code values, types, and possible flag values; and document; their AVP Code values, types, and possible flag values; and
whether the AVP MAY be encrypted. whether the AVP MAY be encrypted.
6.2.3.3.1. Support for Mobile IPv6 with IKEv2 and IPsec 6.2.3.3.1. Support for Mobile IPv6 with IKEv2 and IPsec
+--------------------------+ +--------------------------+
| AVP Flag rules | | AVP Flag rules |
+----+-----+----+-----+----+ +----+-----+----+-----+----+
AVP Section | | |SHLD| MUST|MAY | AVP Defined | | |SHLD| MUST|MAY |
Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr| Attribute Name Code in Value Type |MUST| MAY | NOT| NOT|Encr|
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-Mobile- | | | | | | |MIP-Mobile- | | | | | |
|Node-Address TBD TBD Host-IP-Address| M | P | | V | Y | |Node-Address 334 RFC4004 Address | M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP6-Feature- | | | | | |
|Vector TBD 4.7.4 Unsigned64 | | P | | M,V | Y |
+-----------------------------------------+----+-----+----+-----+----+
The MIP6-Feature-Vector is defined in Section 4.7.4 of [12].
6.2.3.3.2. Support for the Mobile IPv6 Authentication Protocol 6.2.3.3.2. Support for the Mobile IPv6 Authentication Protocol
+--------------------------+ +--------------------------+
| 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|
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-MN-AAA-Auth 322 RFC4004 Grouped | M | P | | V | Y | |MIP-MN-AAA-Auth 322 RFC4004 Grouped | M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+
|MIP-Auth-Input- 338 RFC4004 Unsigned32 | M | P | | V | Y | |MIP-Auth-Input- 338 RFC4004 Unsigned32 | M | P | | V | Y |
| Data-Length | | | | | | | Data-Length | | | | | |
+-----------------------------------------+----+-----+----+-----+----+
|MIP- 339 RFC4004 Unsigned32 | M | P | | V | Y | |MIP- 339 RFC4004 Unsigned32 | M | P | | V | Y |
| Authenticator-Length | | | | | | | Authenticator-Length | | | | | |
+-----------------------------------------+----+-----+----+-----+----+
|MIP- 340 RFC4004 Unsigned32 | M | P | | V | Y | |MIP- 340 RFC4004 Unsigned32 | M | P | | V | Y |
| Authenticator-Offset | | | | | | | Authenticator-Offset | | | | | |
+-----------------------------------------+----+-----+----+-----+----+
|MIP-MN-AAA-SPI 341 RFC4004 Unsigned32 | M | P | | V | Y | |MIP-MN-AAA-SPI 341 RFC4004 Unsigned32 | M | P | | V | Y |
|MIP-Mobile- | | | | | |
|Node-Address TBD TBD Host-IP-Address| M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-Mobile- RFC4004 Address | | | | | |
|Node-Address 333 7.3 | M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+
|MIP6-Feature- | | | | | |
|Vector TBD 4.7.4 Unsigned64 | | P | | M,V | Y |
+-----------------------------------------+----+-----+----+-----+----+
The MIP6-Feature-Vector is defined in Section 4.7.4 of [12].
7. IANA Considerations 7. 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.
7.1. Command Codes 7.1. Command Codes
This specification reuses the values 260 and 262 from the Command This specification reuses the values 260 and 262 from the Command
Code namespace defined in [6]. See Section 6 for the assignment of Code namespace defined in [5]. See Section 6 for the assignment of
the namespace in this specification. the namespace in this specification.
7.2. Result-Code AVP Values 7.2. Result-Code AVP Values
This specification assigns the values TBD - TBD from the Result-Code This specification assigns the values TBD - TBD from the Result-Code
AVP (AVP Code 268) value namespace defined in [6]. See AVP (AVP Code 268) value namespace defined in [5]. See
Section 6.2.3.2 for the assignment of the namespace in this Section 6.2.3.2 for the assignment of the namespace in this
specification. specification.
7.3. Application Identifier 7.3. Application Identifier
This specification uses the value TBD to the Application Identifier This specification uses the value TBD to the Application Identifier
namespace defined in [6]. namespace defined in [5].
8. Security Considerations 8. 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 [9]. Additionally, accomplish the split scenario are described in in [2]. Additionally,
the security considerations of the Diameter Base protocol [6], the security considerations of the Diameter Base protocol [5],
Diameter EAP application [7] are applicable to this document. This Diameter EAP application [8] are applicable to this document. This
document does not introduce new security vulnerabilities. document does not introduce new security vulnerabilities.
9. Acknowledgements 9. Acknowledgements
The authors would like to thanks Jari Arkko, Tolga Asversen, Pasi The authors would like to thanks Jari Arkko, Tolga Asversen, Pasi
Eronen, Santiago Zapata Hernandez, Jouni Korhonen, Anders Kristensen, Eronen, Santiago Zapata Hernandez, Jouni Korhonen, Anders Kristensen,
Avi Lior, John Loughney, Ahmad Muhanna and Lionel Morand and Avi Lior, John Loughney, Ahmad Muhanna and Lionel Morand and
Yoshihiro Ohba for all the useful discussions. Jouni Korhonen Yoshihiro Ohba for all the useful discussions. Jouni Korhonen
provided a detailed draft review in June 2007. provided a detailed draft review in June 2007.
skipping to change at page 15, line 47 skipping to change at page 19, line 12
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.
10. References 10. References
10.1. Normative References 10.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] Devarapalli, V. and F. Dupont, "Mobile IPv6 Operation with [2] Giaretta, G., "Mobile IPv6 bootstrapping in split scenario",
draft-ietf-mip6-bootstrapping-split-05 (work in progress),
May 2007.
[3] 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.
[3] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury, [4] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury,
"Authentication Protocol for Mobile IPv6", RFC 4285, "Authentication Protocol for Mobile IPv6", RFC 4285,
January 2006. January 2006.
[4] Bradner, S., "Key words for use in RFCs to Indicate Requirement [5] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko,
"Diameter Base Protocol", RFC 3588, September 2003.
[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.
[5] Patel, A. and G. Giaretta, "Problem Statement for bootstrapping [7] Patel, A. and G. Giaretta, "Problem Statement for bootstrapping
Mobile IPv6 (MIPv6)", RFC 4640, September 2006. Mobile IPv6 (MIPv6)", RFC 4640, September 2006.
[6] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko, [8] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
"Diameter Base Protocol", RFC 3588, September 2003.
[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", [9] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol",
RFC 4306, December 2005. RFC 4306, December 2005.
[9] Giaretta, G., "Mobile IPv6 bootstrapping in split scenario", [10] Korhonen, J., "Quality of Service Attributes for Diameter and
draft-ietf-mip6-bootstrapping-split-05 (work in progress), RADIUS", draft-ietf-dime-qos-attributes-00 (work in progress),
May 2007. July 2007.
[10] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and P. [11] 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] Korhonen, J., "Diameter Mobile IPv6: Support for Network Access
Server to Diameter Server Interaction",
draft-ietf-dime-mip6-integrated-04 (work in progress),
May 2007.
10.2. Informative References 10.2. Informative References
[11] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury, [13] Giaretta, G., "AAA Goals for Mobile IPv6",
draft-ietf-mip6-aaa-ha-goals-03 (work in progress),
September 2006.
[14] 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.
[12] Giaretta, G., "AAA Goals for Mobile IPv6", [15] Fajardo, V., "Diameter Applications Design Guidelines",
draft-ietf-mip6-aaa-ha-goals-03 (work in progress), draft-ietf-dime-app-design-guide-01 (work in progress),
September 2006. June 2007.
[13] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J. [16] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J.
Loughney, "Diameter Credit-Control Application", RFC 4006, Loughney, "Diameter Credit-Control Application", RFC 4006,
August 2005. August 2005.
[14] Chowdhury, K. and A. Yegin, "MIP6-bootstrapping for the [17] Chowdhury, K. and A. Yegin, "MIP6-bootstrapping for the
Integrated Scenario", Integrated Scenario",
draft-ietf-mip6-bootstrapping-integrated-dhc-04 (work in draft-ietf-mip6-bootstrapping-integrated-dhc-04 (work in
progress), June 2007. progress), June 2007.
Authors' Addresses Authors' Addresses
Julien Bournelle Julien Bournelle
France Telecom R&D France Telecom R&D
38-4O rue du general Leclerc 38-4O rue du general Leclerc
Issy-Les-Moulineaux 92794 Issy-Les-Moulineaux 92794
 End of changes. 81 change blocks. 
133 lines changed or deleted 270 lines changed or added

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