draft-ietf-dime-mip6-split-02.txt   draft-ietf-dime-mip6-split-03.txt 
Diameter Maintenance and J. Bournelle, Ed. Diameter Maintenance and J. Bournelle
Extensions (DIME) GET/INT Extensions (DIME) France Telecom R&D
Internet-Draft G. Giaretta Internet-Draft G. Giaretta
Intended status: Standards Track Telecom Italia Intended status: Standards Track Qualcomm
Expires: November 4, 2007 H. Tschofenig Expires: December 31, 2007 H. Tschofenig
Nokia Siemens Networks Nokia Siemens Networks
M. Nakhjiri M. Nakhjiri
Huawei Huawei
May 3, 2007 June 29, 2007
Diameter Mobile IPv6: HA <-> HAAA Support Diameter Mobile IPv6: Support for Home Agent to Diameter Server
draft-ietf-dime-mip6-split-02 Interaction
draft-ietf-dime-mip6-split-03.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 39 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 November 4, 2007. This Internet-Draft will expire on December 31, 2007.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
In a Mobile IPv6 deployment the need for an interaction between the Mobile IPv6 deployments may want to bootstrap their operations
Home Agent, the AAA infrastructure of the Mobile Service Provider dynamically based on an interaction between the Home Agent and the
(MSP) and the Mobility Service Authorizer (MSA) has been identified. Diameter server of the Mobile Service Provider (MSP). This document
that specifies the interaction between the Home Agent and the
This document describes a new Diameter application, called Mobile Diameter server. Two different mechanisms for authentication of a MN
IPv6 Authorization Application, used in conjunction with the Diameter to the HA are supported. The first method consists of performing the
EAP Application is used to perform the necessary AAA functions before Internet Key Exchange v2 (IKEv2) protocol along with the Extensible
executing Mobile IPv6 services. This document also specifies the Authentication Protocol (EAP) with the Diameter server, while the
role of the Home Agent as part of the AAA infrastructure supporting second method utilizes the Mobile IPv6 Authentication option, as
the Diameter Mobile IPv6 Authorization Application. defined in RFC 4285. For Internet Key Exchange v2 with EAP-based
authentication, the Diameter Mobile IPv6 application, defined in this
document, reuses the commands defined in the Diameter EAP
application, while for supporting the RFC 4285-style MIPv6
Authentication Options, a new Diameter application is defined that
reuses the Diameter Mobile IPv4 application.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Diameter MIP6 HA-to-AAAH Overview . . . . . . . . . . . . . . 4 3. Advertising Application Support . . . . . . . . . . . . . . . 3
4. Diameter Mobile IPv6 HA-to-AAAH Support . . . . . . . . . . . 5 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Authentication . . . . . . . . . . . . . . . . . . . . . . 6 5. Protocol Description . . . . . . . . . . . . . . . . . . . . . 5
4.1.1. HA with EAP Support . . . . . . . . . . . . . . . . . 6 5.1. Support for Mobile IPv6 with IKEv2 and IPsec . . . . . . . 5
4.1.2. HA without EAP Support . . . . . . . . . . . . . . . . 8 5.2. Support for the Mobile IPv6 Authentication Protocol . . . 7
4.2. Authorization . . . . . . . . . . . . . . . . . . . . . . 8 5.3. Mobile IPv6 Session Management . . . . . . . . . . . . . . 8
4.3. Accounting . . . . . . . . . . . . . . . . . . . . . . . . 9 5.3.1. Session-Termination-Request Command . . . . . . . . . 8
4.4. Mobile IPv6 Session Management . . . . . . . . . . . . . . 9 5.3.2. Session-Termination-Answer Command . . . . . . . . . . 8
4.4.1. Session-Termination-Request Command . . . . . . . . . 9 5.3.3. Abort-Session-Request Command . . . . . . . . . . . . 8
4.4.2. Session-Termination-Answer Command . . . . . . . . . . 9 5.3.4. Abort-Session-Answer Command . . . . . . . . . . . . . 9
4.4.3. Abort-Session-Request Command . . . . . . . . . . . . 9 6. Command-Code and AVP Values . . . . . . . . . . . . . . . . . 9
4.4.4. Abort-Session-Answer Command . . . . . . . . . . . . . 10 6.1. Command Code for EAP-based Authentication . . . . . . . . 9
5. Command-Code Values . . . . . . . . . . . . . . . . . . . . . 10 6.1.1. Diameter-EAP-Request (DER) . . . . . . . . . . . . . . 9
5.1. MIP6-Authorization-Request . . . . . . . . . . . . . . . . 10 6.1.2. Diameter-EAP-Answer (DEA) . . . . . . . . . . . . . . 10
5.2. MIP6-Authorization-Answer . . . . . . . . . . . . . . . . 10 6.2. Command Codes for RFC 4285 Support . . . . . . . . . . . . 10
6. Result-Code AVPs . . . . . . . . . . . . . . . . . . . . . . . 10 6.2.1. MIP6-Request-Message . . . . . . . . . . . . . . . . . 11
7. Mandatory AVPs . . . . . . . . . . . . . . . . . . . . . . . . 10 6.2.2. MIP6-Answer-Message . . . . . . . . . . . . . . . . . 11
8. Accounting AVPs . . . . . . . . . . . . . . . . . . . . . . . 11 6.2.3. Diameter AVPs . . . . . . . . . . . . . . . . . . . . 12
9. AVP Occurence Tables . . . . . . . . . . . . . . . . . . . . . 11 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
10. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 11 7.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 14
10.1. Authentication Token . . . . . . . . . . . . . . . . . . . 11 7.2. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 15
10.2. HA as a Single Physical Device . . . . . . . . . . . . . . 11 7.3. Application Identifier . . . . . . . . . . . . . . . . . . 15
10.3. Triggering the MIP6 Authorization Application . . . . . . 11 8. Security Considerations . . . . . . . . . . . . . . . . . . . 15
10.4. RFC4285 Support . . . . . . . . . . . . . . . . . . . . . 12 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
12. Security Considerations . . . . . . . . . . . . . . . . . . . 12 10.1. Normative References . . . . . . . . . . . . . . . . . . . 15
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 10.2. Informative References . . . . . . . . . . . . . . . . . . 16
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17
14.1. Normative References . . . . . . . . . . . . . . . . . . . 12 Intellectual Property and Copyright Statements . . . . . . . . . . 18
14.2. Informative References . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
Intellectual Property and Copyright Statements . . . . . . . . . . 15
1. Introduction 1. Introduction
With the Mobile IPv6 protocol [1], a Mobile Node (MN) is assigned a Performing the Mobile IPv6 protocol [1], requires assignment of a
Home Agent which is in charge of relaying IPv6 packets destined to Home Agent (HA) to a Mobile Node (MN). The MN needs to register its
MN's Home Address to the MN's current address. Moreover, the Mobile Mobile IPv6 session with the HA in order facilitate its reachability
Node and its Home Agent (HA) must share IPsec Security Associations and mobility, when away from home.
to protect Mobile IPv6 signalling. Note that it is possible to use
another method than IPsec to secure signalling messages, but in this
document, only IPsec is considered. One of the problem is to
dynamically set-up these Security Associations and to assign the Home
Agent Address and the Home Address to the Mobile Node. This problem
is known as the Mobile IPv6 bootstrapping problem and is detailed in
[2]. Two possible bootstrapping scenarios have been identified,
namely the Integrated and the Split Scenario. With the Integrated
Scenario (see [3]), the Home Agent Address is delivered during the
process of network access authentication, while in the Split scenario
(see [4]), the Home Agent information is discovered using the DNS
infrastructure. In both cases, the Mobile Node has the Home Agent
information and it interacts with the Home Agent using IKEv2 [5].
From an operator perspective, it is important to verify that the user From an operator (mobility service provider, MSP) perspective, it is
(MN) is authorized to utilize Mobile IPv6 service and that such important to verify that the MN is authenticated and authorized to
services are accounted for. The Home Agent, while verifying the utilize Mobile IPv6 service and that such services are accounted for.
user's identity, also participates in the Mobile IPv6 authorization Thus, prior to processing the Mobile IPv6 service requests, the HA,
process and due to its role in traffic forwarding performs accounting participates in the authentication of the MN to verify the MN's
for this service. For this reason, it is important for the Home identity. The HA also participates in the Mobile IPv6 authorization
Agent to act as part of the service provider's AAA infrastructure. process involving the Diameter infrastrucure. The HA due to its role
in traffic forwarding, also performs accounting for the Mobile IPv6
service provided to the MN.
The goal of this document is to specify a new Diameter application, Mobile IPv6 specifications allow two different methods for MN
called Diameter Mobile IPv6 Authorization Application specifying the authentication, one based on IKEv2 and EAP [2], and another based on
authorization and accounting procedures associated for Mobile IPv6 the Mobile IPv6 Authentication Option [3]. The goal of this document
service. Furthermore, the document specifies the role of Home Agent is to specify the Diameter procedures associated with the Mobile IPv6
as a Diameter client to support this application. This modular bootstrapping between the HA and the Diameter server for these two
approach provides flexibility for the choice of authentication in Mobile IP authentication approaches.
conjunction with Mobile IPv6 services. For instance, the HA can use
the Diameter EAP Application [6] or other procedures for performing For that reason the Diameter Mobile IPv6 application provides two
authentications through a Diameter server. Note that this different sets of commands. The first set of commands reuse the
application can be used both in Integrated and Split scenarios. command already define in Diameter EAP application (though using the
Diameter Mobile IPv6 Application-Id). While the second set of
commands are new for Diameter and provide support the Mobile IPv6
Authentication Option, defined in RFC 4285.
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 [7]. document are to be interpreted as described in RFC 2119 [4].
The MIPv6 bootstrapping terminology is taken from [2].
3. Diameter MIP6 HA-to-AAAH Overview
The Home Agent offers the Mobile IPv6 service to the Mobile Node. As
a Diameter client, the delivered Home Agent performs the following
operations:
Authentication: The Home Agent must verify the identity of the user
provided in the IKEv2 exchange.
Authorization: The Home Agent must verify that the user is The MIPv6 bootstrapping terminology is taken from [5].
authorized to use the Mobile IPv6 service.
Accounting: For billing purposes and capacity planning, the Home 3. Advertising Application Support
Agent provides accounting report to the AAA infrastructure.
Figure 1 shows the architecture of the solution described in this Diameter nodes conforming to this specification MUST advertise
document. support by including the Diameter Mobile IPv6 Application ID value of
[TO BE ASSIGNED BY IANA] in the Auth-Application-Id AVP of the
Capabilities-Exchange-Request and Capabilities-Exchange-Answer
command [6]
MSP MSA 4. Overview
+--------+ +-------------+
+--+ IKEv2 +--+ | Diameter EAP | +--------+ |
|MN|<------>|HA|<-------------------------->|AAAH-EAP| |
+--+ | +--+ |(AUTHENTICATE_ONLY) | +--------+ |
| ^ | | |
| | | | |
| | Diameter MIP6 Authz/Acc | +---------+ |
| +---------------------------->|AAAH-MIP6| |
| | | +---------+ |
+--------+ +-------------+
Figure 1: Architecture Overview One task of the Mobile IPv6 bootstrapping procedure is to assign an
appropriate HA to the MN. Furthermore, authorization and successful
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
MSP. As a Diameter client, the HA needs to perform the following
operations:
For the authentication part, it is likely that operators will use EAP Authentication: Asserting or helping in assertion of the correctness
within IKEv2 to authenticate the user since it is the easiest way for of the MN identity. As a Diameter client supporting the new
operator to leverage their AAA infrastructure for IKEv2 initiator Diameter Mobile IPv6 application, the HA may need to support two
authentication. The Diameter EAP Application [6] is the application different types of authentication by supporting the different
that permits carrying EAP packets between an access device and a AAA command sets that are required for each authentication method.
server. However, this application is primarly defined to perform AAA
operations for network access service and not for Mobile IPv6
service. For this reason, it is recommended that, when EAP is used
for authentication, the Diameter EAP application will be used only
for Authentication purpose. This implies that the Home Agent will
use the Diameter EAP Application in "AUTHENTICATE_ONLY" mode. This
is realized by setting the Auth-Request-Type AVP to
AUTHENTICATE_ONLY. In this document, the AAA server contacted for
Authentication is called AAAH-EAP. This server belongs to the MSA.
To explicitely authorize the Mobile IPv6 service, in this document, Authorization: The HA must verify that the user is authorized to use
we define a new Diameter application, called Mobile IPv6 the Mobile IPv6 service using the assistance of the MSP Diameter
Authorization Application. The application requires two new servers. This is accomplised through use of new Diameter commands
messages, namely: MIP6-Authorization-Request (MAR) and MIP6- specifically designed for performing Mobile IPv6 authorization
Authorization-Answer (MAA). The HA, acting as a Diameter client for decisions. This document defines these commands and requires the
this new application, sends a MIP6-Authorization-Request message HA to support use of these authorization commands and to
containing identity of the user to the Mobility service authorizer participate in this authorization signaling.
(e.g., HAAA for MIP6 service) to verify that this user is authorized
to use Mobile IPv6 service. This message is sent towards Diameter
server called AAAH-MIP6 in this document. This server belongs to the
MSA.
This message may also contain some specific authorization AVPs Accounting: For billing purposes and capacity planning, it is
concerning Home-Address Allocation and Home-Address DNS registration. required of the HA to provide accounting report to the Diameter
The response is contained in the MIP6-Authorization-Answer. As this infrastructure and thus to support the related Diameter accounting
application needs a new Application-Id [[[To Be assigned by IANA]]], procedures.
it has to be noted that the Mobile IPv6 authorization requests may be
routed to a different AAA server (AAAH-MIP6) than the AAA server used
for Authentication request (AAAH-EAP).
When the verification of user authorization to receive Mobile IPv6 Figure 1 depicts the architecture.
service is complete, the Home-Agent start performing Accounting
operation by sending accounting message (ACR) with the AVP Acct-
Application-ID set to [[[To Be Assigned by IANA]]]. These messages
contain specific Mobile IPv6 AVPs and are sent to the AAAH-MIP6.
4. Diameter Mobile IPv6 HA-to-AAAH Support +---------------------------+ +-----------------+
|Visited MSP | | Home MSP/MSA |
| | | |
| | | |
| +--------+ | | +--------+ |
| |Local | Diameter | | |Home | |
| |Diameter|<---------------------->|Diameter| |
| |Proxy | | | |Server | |
| +--------+ | | +--------+ |
| ^ | | ^ |
| | | | | |
| | Diameter | |Diameter| |
| v | | v |
| +-------+ | | +-------+ |
| |Home | | | |Home | |
| |Agent | | | |Agent | |
| +-------+ | | +-------+ |
| ^ | | ^ |
+-----|---------------------+ +--------|--------+
| |
| |
| +---------+ |
| | Mobile | |
+--------->| Node |<-----------+
IKEv2 or RFC 4285 +---------+ IKEv2 or RFC 4285
Although the main goal of this document is to specify the Figure 1: Architecture Overview
authorization and accounting for Mobile IPv6 application, the intent
is also to provide guidance on the AAA operations expected from HA.
Hence, this document provides guidance on the procedures required
from the HA as part of the authentication process. As EAP is
considered as a strong choice in performing authentication, this
document explains the use of Diameter EAP application in cases where
the prior authentication between MN and HA is done through use of
EAP. Therefore, the HA performs AAA operations for Mobile IPv6 by
using two Diameter Applications, namely: Diameter EAP[6] and Diameter
Mobile IPv6 (specified by this document).
If EAP is used within IKEv2, the HA uses the procedures of Diameter [Editor's Note: A description of the relationship with the front-end
EAP application (DER/DEA) with the Auth-Request-Type set to protocols is needed.]
AUTHENTICATE_ONLY.
4.1. Authentication 5. Protocol Description
As mentioned before, prior to performing authorization process, the 5.1. Support for Mobile IPv6 with IKEv2 and IPsec
HA must authenticate the user. The use of IKEv2 between the MN and
the HA allows the HA to authenticate the Mobile Node. Traditional
IKE authentication procedures require existence of pre-shared secrets
or certificates between MN and HA. However, given the possible lack
of prior knowledge between MN and HA, the more desired approach is to
use EAP and the AAA infrastructure to authenticate the user during
IKEv2.
4.1.1. HA with EAP Support 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
application, as defined in [7], is re-used. AVPs specific to Mobile
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 Node HA/Diameter Client Home AAA/EAP Server(AAAH-EAP) Mobile Home Diameter
Node Agent Server
------ ----- --------
IKE_SA_INIT (1,2) IKE_SA_INIT (1,2)
<------------------------------> <------------------------------>
HDR, SK{IDi,[CERTREQ,] [IDr,] HDR, SK{IDi,[CERTREQ,] [IDr,]
[CP(CFG_REQUEST),] [CP(CFG_REQUEST),]
SAi2, TSi, TSr} (3) SAi2, TSi, TSr} (3)
-------------------------------> ------------------------------->
DER (EAP-Response)(AUTHENTICATE_ONLY) DER (EAP-Response) (4)
------------------------> ------------------------>
DEA (EAP-Request) DEA (EAP-Request) (5)
<------------------------ <------------------------
HDR, SK {IDr, [CERT,] AUTH, HDR, SK {IDr, [CERT,] AUTH,
EAP } EAP }
<------------------------------- <-------------------------------
HDR, SK {EAP} HDR, SK {EAP}
--------------------------------> -------------------------------->
DER (EAP-Response)(AUTHENTICATE_ONLY) 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)
------------------------> ------------------------>
... ... ... ...
skipping to change at page 7, line 47 skipping to change at page 6, line 48
HDR, SK{EAP-Success} HDR, SK{EAP-Success}
<------------------------------- <-------------------------------
HDR, SK{AUTH} HDR, SK{AUTH}
-------------------------------> ------------------------------->
HDR, SK {AUTH, [CP(CFG_REPLY,] SAr2, TSi, TSr } HDR, SK {AUTH, [CP(CFG_REPLY,] SAr2, TSi, TSr }
<------------------------------- <-------------------------------
Figure 2: IKEv2 Diameter EAP Message Flow Figure 2: IKEv2 Diameter EAP Message Flow
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 a 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 Mobile Node first CHILD_SA. It is used to mutually authenticate the MN (acting
(acting as an IKEv2 Initiator) and the Home Agent (acting as an IKEv2 as an IKEv2 Initiator) and the HA (acting as an IKEv2 Responder).
Responder). The identity of the User/Mobile Node is provided in the The identity of the user/MN is provided in the IDi field. The MN
field IDi. The Mobile Node indicates its willingness to be indicates its willingness to be authenticated via EAP by omitting the
authenticated by EAP by omitting the field AUTH in message 3 (cf. AUTH field in message 3 (see [8]).
[5]). The Mobile Node authenticates the Home Agent by requesting a
certificate. This is done by including the field [CERTREQ] in
message 3.
As part of the authentication process, the Mobile Node MAY request a
Home-Address, a Home Prefix or suggests one [4]. This is done by
using a CFG_REQUEST payload in the message 3.
The Home Agent extracts the IDi field from the message 3 and sends a As part of the authentication process, the MN MAY request a Home-
Diameter-EAP-Request message towards the authenticating Diameter Address, a Home Prefix or suggests one, see [9], using a CFG_REQUEST
server AAAH-EAP. The User-Name AVP of the DER message MUST be set to payload in the message 3.
the IDi field and the Auth-Request-Type MUST be set to
AUTHENTICATE_ONLY. This message is routed through the AAA
infrastructure to the home AAA server (AAAH-EAP) of this Mobile Node.
The AAAH-EAP chooses an authentication method and replies with the
DEA Message.
At the end of the EAP authentication phase, the AAAH-EAP indicates The HA extracts the IDi field from the message 3 and sends a
the result of the authentication in the Result-Code AVP and provides Diameter-EAP-Request (DER) message towards the authenticating
the corresponding EAP packet (EAP Success or EAP Failure). The last Diameter server.
IKEv2 message sent by the Home Agent contains the Home Address or the
Home Prefix. In the latter case, a CREATE_CHILD_SA exchange is
necessary to setup IPsec SAs for Mobile IPv6 signalling.
4.1.2. HA without EAP Support This message is routed to the MNs Diameter server/EAP server. The
Diameter server selects the EAP method and replies with the DEA
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 the Diameter server/EAP server.
To be completed. At the end of the EAP authentication phase, the Diameter server
indicates the result of the authentication in the Result-Code AVP and
provides the corresponding EAP packet (EAP Success or EAP Failure).
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
necessary to setup IPsec SAs for Mobile IPv6 signalling.
4.2. Authorization In some deployment scenario, the HA may also acts as a IKEv2
Responder for IPsec VPN access. A problem in this case is that the
IKEv2 responder may not know if IK Ev2 is used for MIP6 service or
for IPsec VPN access. A network operator needs to be aware of this
limitation.
Following the successful authentication, the Home Agent must ensure 5.2. Support for the Mobile IPv6 Authentication Protocol
that the Mobile Node is authorized to use the Mobile IPv6 service.
For this purpose, the Home Agent sends a MIP6-Authorization-Request
(MAR) message containing identity of the user towards the AAAH-MIP6.
The Application-ID of this message is set to [TO BE ASSIGNED]. The
identity is extracted from the IDi field provided in the message 3 of
the IKEv2 exchange. The home AAA server (AAAH-MIP6) replies with a
MIP6-Authorization-Answer which contains the result of the
authorization process. This latter message MAY contain configuration
policies to be applied at the Home Agent.
As part of the authorization request for the Mobile IPv6 service. Figure 3 describes the sequence of messages sent and received between
The Home Agent may require specific authorization for this MN. As an the MN, the HA and the Diameter server during the registration when
example, it may request if this user is allowed to auto-assign its RFC 4285 is used. Binding Update (BU) and Binding Acknowledgement
Home-Address. (BA) messages are used in the registration process. This exchange
triggers the Diameter interaction.
4.3. Accounting According to [3] the MN uses the Mobile Node Identifier Option,
specifically the MN-NAI mobility option as defined in [11] to
identify itself while authenticating with the HA.
Concerning accounting, the Diameter Mobile IPv4 Application [8] The MN may use the Message Identifier option for additional replay
defines the following AVPs: protection. The authentication option may be used by the MN to
transfer authentication data when the MN and the HA are utilizing a
mobility SPI.
o Accounting-Input-Octets: Number of octets in IP packets received The BU initiates a MIP6-Request-Message to the Diameter server and
from the user the corresponding response is carried in a MIP6-Answer-Message.
o Accounting-Output-Octets: Number of octets in IP packets sent by
the user
o Accounting-Input-Packets: Number of IP packets received from the
user
o Accounting-Output-Packets: Number of IP packets sent by the user.
These AVPs may be re-used for the Mobile IPv6 service. However, due Mobile Home AAA
to routing optimization techniques introduced with Mobile IPv6 the HA Node Agent Server
does not see the entire traffic exchanged between the MN and the CN. | | |
| | |
| Binding Update |MIP6-Request-Message |
(a)|------------------------------------>|-------------------->|
| (including MN-ID option, | |
| Message ID option [optional], | |
| authentication option) | |
| | |
| | |
| Binding Acknowledgement |MIP6-Answer-Message |
(b)|<------------------------------------|<--------------------|
| (including MN-ID option, | (MN-HA key) |
| Message ID option [optional], | |
| authentication option) | |
[Editor's Note: As the document describing goals for this interface Figure 3: MIPv6 Bootstrapping using RFC 4285
is not finalized, other parameters may be needed in the future.]
4.4. Mobile IPv6 Session Management 5.3. Mobile IPv6 Session Management
Concerning Mobile IPv6 session, the AAAH (AAAH-MIP6) server may The Diameter server may maintain state or may be stateless. This is
maintain state or may be stateless. This is indicated in the Auth- indicated in the Auth-Session-State AVP (or its absence). The HA
Session-State AVP (or its abscence) in the MAA message. The Home MUST support the Authorization Session State Machine defined in [6].
Agent MUST support the Authorization Session State Machine defined in Moreover the following 4 commands may be exchanged between the HA and
[9]. Moreover the following 4 commands may be exchanged between the the Diameter server.
Home Agent and the home AAA server.
4.4.1. Session-Termination-Request Command 5.3.1. Session-Termination-Request Command
The Session-Termination-Request (STR) message [9] is sent by the Home The Session-Termination-Request (STR) message [6] is sent by the HA
Agent to inform the Diameter server that an authorized session is to inform the Diameter server that an authorized session is being
being terminated. terminated.
4.4.2. Session-Termination-Answer Command 5.3.2. Session-Termination-Answer Command
The Session-Termination-Answer (STA) message [9] is sent by the The Session-Termination-Answer (STA) message [6] is sent by the
Diameter server to acknowledge the notification that the session has Diameter server to acknowledge the notification that the session has
been terminated. been terminated.
4.4.3. Abort-Session-Request Command 5.3.3. Abort-Session-Request Command
The Abort-Session-Request (ASR) message [9] is sent by the Diameter The Abort-Session-Request (ASR) message [6] 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 [11]. requirement described in [12].
4.4.4. Abort-Session-Answer Command 5.3.4. Abort-Session-Answer Command
The Abort-Session-Answer (ASA) message [9] is sent by the Home Agent The Abort-Session-Answer (ASA) message [6] is sent by the Home Agent
in response to an ASR message. in response to an ASR message.
5. Command-Code Values 6. Command-Code and AVP Values
This section defines Command-Code [9] value that MUST be supported by This section defines the command codes and AVP values used by the
all Diameter implementations conforming to this specification. The Diameter Mobile IPv6 application:
following Command Codes are defined in this specification:
Command-Name Abbrev. Code Reference Application
----------------------------------------------------------------------
Diameter-EAP-Request DER 268 RFC 4072 EAP
Diameter-EAP-Answer DEA 268 RFC 4072 EAP
MIP6-Request-Message MRM XXX TBD MIP6
MIP6-Answer-Message MAM XXX TBD MIP6
Figure 4: Command Codes
6.1. Command Code for EAP-based Authentication
This document re-uses the Diameter EAP application commands. The
following commands are used to carry MIPv6 related bootstrapping
AVPs:
Command-Name Abbrev. Code Reference Application
------------------------------------------------------------------
Diameter-EAP-Request DER 268 RFC 4072 EAP
Diameter-EAP-Answer DEA 268 RFC 4072 EAP
Figure 5: Diameter EAP command codes used for MIPv6 Bootstrapping HA
to HAAA Interface
[Editor's Note: The subsections below do not yet show the MIPv6
specific AVPs.]
6.1.1. Diameter-EAP-Request (DER)
The Diameter-EAP-Request (DER) message [7], indicated by the Command-
Code field set to 268 and the 'R' bit set in the Command Flags field,
is sent by the HA to the Diameter server to initiate a Mobile IPv6
service authentication and authorization procedure. The DER message
format is the same as defined in [7]. The Application-ID field of
the Diameter Header MUST be set to the Diameter Mobile IPv6
Application ID [TO BE ASSIGNED TO IANA].
<Diameter-EAP-Request> ::= < Diameter Header: 268, REQ, PXY >
< Session-Id >
{ Auth-Application-Id }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Auth-Request-Type }
[ Destination-Host ]
...
* [ AVP ]
6.1.2. Diameter-EAP-Answer (DEA)
The Diameter-EAP-Answer (DEA) message defined in [7], indicated by
the Command-Code field set to 268 and 'R' bit cleared in the Command
Flags field, is sent in response to the Diameter-EAP-Request message
(DER). If the Mobile IPv6 authentication procedure was successful
then the response MAY include any set of bootstrapping AVPs.
The DEA message format is the same as defined in [7]. The
Application-Id field in the Diameter header MUST be set to the
Diameter Mobile IPv6 Application-Id [TO BE ASSIGNED BY IANA].
<Diameter-EAP-Answer> ::= < Diameter Header: 268, PXY >
< Session-Id >
{ Auth-Application-Id }
{ Auth-Request-Type }
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
...
* [ AVP ]
6.2. Command Codes for RFC 4285 Support
This section defines Command-Code [6] values that MUST be supported
by all Diameter implementations conforming to this specification.
The following Command Codes are defined in this specification.
Command-Name Abbreviation Code Section Command-Name Abbreviation Code Section
--------------------------------------------------------- ------------------------------------------------------------------
MIP6-Authorization-Request MAR TBD MIP6-Request-Message MRM TBD Section 6.2.1
MIP6-Authorization-Answer MAA TBD MIP6-Answer-Message MAM TBD Section 6.2.2
Figure 3 6.2.1. MIP6-Request-Message
5.1. MIP6-Authorization-Request 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
the HA, acting as a Diameter client, in order to request the
authentication and authorization of a MN. The HA uses information
found in the Binding Update to construct the following AVPs, to be
included as part of the MRM:
The MIP6-Authorization-Request (MAR), indicated by the Command-Code o Home Address (MIP6-Home-Address AVP)
field set to TBD and the 'R' bit set in the Command Flags field is o Mobile Node NAI (User-Name AVP [6])
sent by the Home Agent acting as a Diameter Client. This message is o MN-AAA Authentication Extension (MIP-MN-AAA-Auth AVP)
used by the Home-Agent to authorize the Mobile IPv6 service.
5.2. MIP6-Authorization-Answer If the MN's home address is zero, the HA MUST NOT include a MIP6-
Home-Address AVP.
The MIP6-Authorization-Answer (MAA), indicated by the Command-Code If the MN's home address is all ones, the HA MUST include a MIP6-
field set to TBD and the 'R' bit cleared in the Command Flags field Home-Address AVP, set to all ones.
is sent by the AAAH (AAAH-MIP6) in response to MIP6-Authorization-
Request.
6. Result-Code AVPs The message format is shown below:
This section defines new Result-Code [9] values that MUST be <MIP6-Request-Message> ::= < Diameter Header: 260, REQ, PXY >
supported by all Diameter implementations that conform to this < Session-ID >
specification. { Auth-Application-Id }
{ User-Name }
{ Destination-Realm }
{ Origin-Host }
{ Origin-Realm }
[ Acct-Multi-Session-Id ]
[ Destination-Host ]
[ Origin-State-Id ]
To be completed. { MIP-MN-AAA-Auth }
[ MIP6-Home-Address ]
7. Mandatory AVPs [ Authorization-Lifetime ]
[ Auth-Session-State ]
* [ Proxy-Info ]
* [ Route-Record ]
* [ AVP ]
To be completed. 6.2.2. MIP6-Answer-Message
8. Accounting AVPs 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,
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
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
in RFC 3588 [6].
To be completed. 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
AVP contains the HA assigned to the MN, while the MIP-Mobile-Node-
Address AVP contains the home address that was assigned.
9. AVP Occurence Tables The message format is shown below:
To be completed. <MIP6-Answer-Message> ::= < Diameter Header: 260, PXY >
< Session-Id >
{ Auth-Application-Id }
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ Acct-Multi-Session-Id ]
[ User-Name ]
[ Authorization-Lifetime ]
[ Auth-Session-State ]
[ Error-Message ]
[ Error-Reporting-Host ]
[ Re-Auth-Request-Type ]
10. Open Issues [ MIP-MN-to-HA-MSA ]
[ MIP-HA-to-MN-MSA ]
[ MIP-MSA-Lifetime ]
[ MIP6-Home-Address ]
10.1. Authentication Token [ Origin-State-Id ]
* [ Proxy-Info ]
* [ AVP ]
Authentication and Authorization/Accounting process may be handled by 6.2.3. Diameter AVPs
two different AAA servers, namely AAAH-EAP and AAAH-MIP6. As such,
the AAAH-MIP6 does not know if the MN has been correctly
authenticated before authorizing the service.
The issue is to know wether we need to provide a proof to the AAAH- The Diameter client uses AVPs dependent on the usage of RFC 4285 [3]
MIP6 that the MN is correctly authenticated by AAAH-EAP or RFC 4877 [2].
10.2. HA as a Single Physical Device To provide support for RFC 4285 [3] the following AVPs defined in
[10] are reused in this application:
o MIP-HA-to-MN-MSA AVP
o MIP-MN-to-HA-MSA AVP
o MIP-Session-Key AVP
o MIP-Algorithm-Type AVP
o MIP-Replay-Mode AVP
o MIP-MN-AAA-Auth AVP
o MIP-MN-AAA-SPI AVP
o MIP-Auth-Input-Data-Length AVP
o MIP-Authenticator-Length AVP
o MIP-Authenticator-Offset AVP
o MIP-MSA-Lifetime AVP
o MIP-Mobile-Node-Address (with an IPv6 address)
The HA acts as a IKEv2 responder with the MN. As such, it can be For usage with the RFC 4877 [2] only the MIP-Mobile-Node-Address AVP
colocated with a VPN concentrator. (with IPv6 address) is needed since all other keying related
parameters are provided by the Diameter EAP application.
The issue is how the HA know that the MN want MIP6 service. 6.2.3.1. Accounting AVPs
10.3. Triggering the MIP6 Authorization Application This document reuses the accounting AVPs defined in Diameter Mobile
IPv4 application [10], namely:
If EAP is used to authenticate the MN, the HA uses two applications Accounting-Input-Octets:
to perform AAA operations: Diameter EAP and the MIP6 Authorization
Application.
The issue is to know when the MIP6 Authorization Application must be Number of octets in IP packets received from the user
used by the HA. Accounting-Output-Octets:
This issue is tied with the "HA as a single box" one. If the only Number of octets in IP packets sent by the user
way for the HA to know that it was for mip6 is to wait for a BU from Accounting-Input-Packets:
the MN, then the Application can be used only after the reception of
the BU. However, if we want to do HoA-Allocation authorization by
the AAAH-MIP6, this implies that the application must be used before
the end of the IKEv2 exchange and thus before the BU reception
10.4. RFC4285 Support Number of IP packets received from the user
Accounting-Output-Packets:
This document deals with the HA-to-AAAH support in case IKEv2 is used Number of IP packets sent by the user.
to setup IPsec SAs between MN and HA to secure Mobile IPv6
signalling.
The issue is wether support for RFC 4285 mechanism should also be 6.2.3.2. Result-Code AVPs
handled by this document.
11. IANA Considerations This section defines new Result-Code [6] values that MUST be
supported by all Diameter implementations that conform to this
specification.
To be completed. [Editor's Note: This section needs to list the result codes that are
used by this application.]
12. Security Considerations 6.2.3.3. AVP Occurence Tables
To be completed. The following table describes the Diameter AVPs defined by this
document; their AVP Code values, types, and possible flag values; and
whether the AVP MAY be encrypted.
13. Acknowledgements 6.2.3.3.1. Support for Mobile IPv6 with IKEv2 and IPsec
+--------------------------+
| AVP Flag rules |
+----+-----+----+-----+----+
AVP Section | | |SHLD| MUST|MAY |
Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr|
+-----------------------------------------+----+-----+----+-----+----+
|MIP-Mobile- | | | | | |
|Node-Address TBD TBD Host-IP-Address| M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+
6.2.3.3.2. Support for the Mobile IPv6 Authentication Protocol
+--------------------------+
| AVP Flag rules |
+----+-----+----+-----+----+
AVP Section | | |SHLD| MUST|MAY |
Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr|
+-----------------------------------------+----+-----+----+-----+----+
|MIP-MN-AAA-Auth 322 RFC4004 Grouped | M | P | | V | Y |
|MIP-Auth-Input- 338 RFC4004 Unsigned32 | M | P | | V | Y |
| Data-Length | | | | | |
|MIP- 339 RFC4004 Unsigned32 | M | P | | V | Y |
| Authenticator-Length | | | | | |
|MIP- 340 RFC4004 Unsigned32 | M | P | | V | Y |
| Authenticator-Offset | | | | | |
|MIP-MN-AAA-SPI 341 RFC4004 Unsigned32 | M | P | | V | Y |
|MIP-Mobile- | | | | | |
|Node-Address TBD TBD Host-IP-Address| M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+
7. IANA Considerations
This section contains the namespaces that have either been created in
this specification or had their values assigned to existing
namespaces managed by IANA.
7.1. Command Codes
This specification reuses the values 260 and 262 from the Command
Code namespace defined in [6]. See Section 6 for the assignment of
the namespace in this specification.
7.2. Result-Code AVP Values
This specification assigns the values TBD - TBD from the Result-Code
AVP (AVP Code 268) value namespace defined in [6]. See
Section 6.2.3.2 for the assignment of the namespace in this
specification.
7.3. Application Identifier
This specification uses the value TBD to the Application Identifier
namespace defined in [6].
8. Security Considerations
The security considerations for the Diameter interaction required to
accomplish the split scenario are described in in [9]. Additionally,
the security considerations of the Diameter Base protocol [6],
Diameter EAP application [7] are applicable to this document. This
document does not introduce new security vulnerabilities.
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, Lionel Morand. The authors would Avi Lior, John Loughney, Ahmad Muhanna and Lionel Morand and
particularly like to thank Yoshihiro Ohba for suggesting the idea of Yoshihiro Ohba for all the useful discussions. Jouni Korhonen
creating a specific authorization application for Mobile IPv6 and to provided a detailed draft review in June 2007.
use Diameter EAP for the authentication part.
The authors would like to thank the European Commission support in Hannes Tschofenig would like to thank the European Commission support
the co-funding of the ENABLE project, where this work is partly being in the co-funding of the ENABLE project, where this work is partly
developed. being developed.
Julien Bournelle would like to thank Orange-FT which partly funded Julien Bournelle would like to thank GET/INT since he began this work
this work. while he was under their employ.
14. References 10. References
14.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] Patel, A. and G. Giaretta, "Problem Statement for bootstrapping [2] Devarapalli, V. and F. Dupont, "Mobile IPv6 Operation with
Mobile IPv6 (MIPv6)", RFC 4640, September 2006. IKEv2 and the Revised IPsec Architecture", RFC 4877,
April 2007.
[3] Chowdhury, K. and A. Yegin, "MIP6-bootstrapping for the [3] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury,
Integrated Scenario", "Authentication Protocol for Mobile IPv6", RFC 4285,
draft-ietf-mip6-bootstrapping-integrated-dhc-03 (work in January 2006.
progress), April 2007.
[4] Giaretta, G., "Mobile IPv6 bootstrapping in split scenario", [4] Bradner, S., "Key words for use in RFCs to Indicate Requirement
draft-ietf-mip6-bootstrapping-split-04 (work in progress), Levels", BCP 14, RFC 2119, March 1997.
December 2006.
[5] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol", [5] Patel, A. and G. Giaretta, "Problem Statement for bootstrapping
RFC 4306, December 2005. Mobile IPv6 (MIPv6)", RFC 4640, September 2006.
[6] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible [6] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko,
"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.
[7] Bradner, S., "Key words for use in RFCs to Indicate Requirement [8] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol",
Levels", BCP 14, RFC 2119, March 1997. RFC 4306, December 2005.
[8] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and P. [9] Giaretta, G., "Mobile IPv6 bootstrapping in split scenario",
draft-ietf-mip6-bootstrapping-split-05 (work in progress),
May 2007.
[10] 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.
[9] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko, 10.2. Informative References
"Diameter Base Protocol", RFC 3588, September 2003.
[10] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter
Network Access Server Application", RFC 4005, August 2005.
14.2. Informative References [11] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury,
"Mobile Node Identifier Option for Mobile IPv6 (MIPv6)",
RFC 4283, November 2005.
[11] Giaretta, G., "AAA Goals for Mobile IPv6", [12] Giaretta, G., "AAA Goals for Mobile IPv6",
draft-ietf-mip6-aaa-ha-goals-03 (work in progress), draft-ietf-mip6-aaa-ha-goals-03 (work in progress),
September 2006. September 2006.
[12] Alfano, F., "Diameter Quality of Service Application",
draft-tschofenig-dime-diameter-qos-01 (work in progress),
October 2006.
[13] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J. [13] 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
Integrated Scenario",
draft-ietf-mip6-bootstrapping-integrated-dhc-04 (work in
progress), June 2007.
Authors' Addresses Authors' Addresses
Julien Bournelle (editor) Julien Bournelle
GET/INT France Telecom R&D
9 rue Charles Fourier 38-4O rue du general Leclerc
Evry 91011 Issy-Les-Moulineaux 92794
France France
Email: julien.bournelle@int-evry.fr Email: julien.bournelle@orange-ftgroup.com
Gerardo Giaretta Gerardo Giaretta
Telecom Italia Lab Qualcomm
via G. Reiss Romoli, 274
TORINO, 10148
Italy
Email: gerardo.giaretta@telecomitalia.it Email: gerardo.giaretta@gmail.com
Hannes Tschofenig Hannes Tschofenig
Nokia Siemens Networks Nokia Siemens Networks
Otto-Hahn-Ring 6 Otto-Hahn-Ring 6
Munich, Bavaria 81739 Munich, Bavaria 81739
Germany Germany
Email: Hannes.Tschofenig@nsn.com Email: Hannes.Tschofenig@nsn.com
URI: http://www.tschofenig.com URI: http://www.tschofenig.com
Madjid Nakhjiri Madjid Nakhjiri
Huawei USA Huawei USA
12040, 98th AVE NE, suite 200B
Kirkland, WA 98033
USA USA
Email: mnakhjiri@huawei.com Email: mnakhjiri@huawei.com
URI:
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
 End of changes. 114 change blocks. 
371 lines changed or deleted 531 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/