draft-ietf-dime-mip6-integrated-06.txt   draft-ietf-dime-mip6-integrated-07.txt 
Diameter Maintenance and J. Korhonen, Ed. Diameter Maintenance and J. Korhonen, Ed.
Extensions (DIME) TeliaSonera Extensions (DIME) TeliaSonera
Internet-Draft J. Bournelle Internet-Draft J. Bournelle
Intended status: Standards Track France Telecom R&D Intended status: Standards Track France Telecom R&D
Expires: May 9, 2008 H. Tschofenig Expires: May 22, 2008 H. Tschofenig
C. Perkins
Nokia Siemens Networks Nokia Siemens Networks
C. Perkins
Nokia
K. Chowdhury K. Chowdhury
Starent Networks Starent Networks
November 6, 2007 November 19, 2007
Diameter Mobile IPv6: Support for Network Access Server to Diameter Diameter Mobile IPv6: Support for Network Access Server to Diameter
Server Interaction Server Interaction
draft-ietf-dime-mip6-integrated-06.txt draft-ietf-dime-mip6-integrated-07.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 41 skipping to change at page 1, line 42
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 9, 2008. This Internet-Draft will expire on May 22, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
A Mobile IPv6 node requires a Home Agent address, a home address, and A Mobile IPv6 node requires a Home Agent address, a home address, and
a security association with its Home Agent before it can start a security association with its Home Agent before it can start
utilizing Mobile IPv6. RFC 3775 requires that some or all of these utilizing Mobile IPv6. RFC 3775 requires that some or all of these
skipping to change at page 2, line 17 skipping to change at page 3, line 7
aims to make this information dynamically available to the Mobile aims to make this information dynamically available to the Mobile
Node. An important aspect of the Mobile IPv6 bootstrapping solution Node. An important aspect of the Mobile IPv6 bootstrapping solution
is to support interworking with existing authentication, is to support interworking with existing authentication,
authorization and accounting infrastructure. This document describes authorization and accounting infrastructure. This document describes
the MIPv6 bootstrapping using the Diameter Network Access Server the MIPv6 bootstrapping using the Diameter Network Access Server
(NAS) to home Authentication, Authorization and Accounting server (NAS) to home Authentication, Authorization and Accounting server
(HAAA) interface. (HAAA) interface.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 3 2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 4
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Commands, AVPs and Advertising Application Support . . . . . . 6 4. Commands, AVPs and Advertising Application Support . . . . . . 7
4.1. Advertising Application Support . . . . . . . . . . . . . 6 4.1. Advertising Application Support . . . . . . . . . . . . . 7
4.2. Command Codes . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Command Codes . . . . . . . . . . . . . . . . . . . . . . 7
4.3. Diameter-EAP-Request (DER) . . . . . . . . . . . . . . . . 7 4.3. Diameter-EAP-Request (DER) . . . . . . . . . . . . . . . . 8
4.4. Diameter-EAP-Answer (DEA) . . . . . . . . . . . . . . . . 7 4.4. Diameter-EAP-Answer (DEA) . . . . . . . . . . . . . . . . 8
4.5. AA-Request (AAR) . . . . . . . . . . . . . . . . . . . . . 8 4.5. AA-Request (AAR) . . . . . . . . . . . . . . . . . . . . . 9
4.6. AA-Answer (AAA) . . . . . . . . . . . . . . . . . . . . . 8 4.6. AA-Answer (AAA) . . . . . . . . . . . . . . . . . . . . . 9
4.7. Attribute Value Pair Definitions . . . . . . . . . . . . . 9 4.7. Attribute Value Pair Definitions . . . . . . . . . . . . . 10
4.7.1. MIP6-Agent-Info . . . . . . . . . . . . . . . . . . . 9 4.7.1. MIP6-Agent-Info . . . . . . . . . . . . . . . . . . . 10
4.7.2. MIP-Home-Agent-Address AVP . . . . . . . . . . . . . . 9 4.7.2. MIP-Home-Agent-Address AVP . . . . . . . . . . . . . . 10
4.7.3. MIP-Home-Agent-Host AVP . . . . . . . . . . . . . . . 10 4.7.3. MIP-Home-Agent-Host AVP . . . . . . . . . . . . . . . 11
4.7.4. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . 10 4.7.4. MIP6-Home-Link-Prefix AVP . . . . . . . . . . . . . . 11
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.7.5. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . 11
5.1. Home Agent Assignment by the NAS . . . . . . . . . . . . . 11 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.2. Home Agent Assignment by the Diameter Server . . . . . . . 12 5.1. Home Agent Assignment by the NAS . . . . . . . . . . . . . 12
5.3. Home Agent Assignment by NAS or Diameter Server . . . . . 13 5.2. Home Agent Assignment by the Diameter Server . . . . . . . 13
6. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 14 5.3. Home Agent Assignment by NAS or Diameter Server . . . . . 14
6.1. AAR, AAA, DER and DEA Commands AVP Table . . . . . . . . . 14 6. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 15
7. MIPv6 Bootstrapping NAS to HAAA Interface AVPs . . . . . . . . 15 6.1. AAR, AAA, DER and DEA Commands AVP Table . . . . . . . . . 15
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 7. MIPv6 Bootstrapping NAS to HAAA Interface AVPs . . . . . . . . 16
8.1. Registration of new AVPs . . . . . . . . . . . . . . . . . 16 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
8.2. New Registry: Mobility Capability . . . . . . . . . . . . 16 8.1. Registration of new AVPs . . . . . . . . . . . . . . . . . 17
9. Security Considerations . . . . . . . . . . . . . . . . . . . 16 8.2. New Registry: Mobility Capability . . . . . . . . . . . . 17
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 9. Security Considerations . . . . . . . . . . . . . . . . . . . 17
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18
11.1. Normative References . . . . . . . . . . . . . . . . . . . 17 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
11.2. Informative References . . . . . . . . . . . . . . . . . . 17 11.1. Normative References . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 11.2. Informative References . . . . . . . . . . . . . . . . . . 18
Intellectual Property and Copyright Statements . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
Intellectual Property and Copyright Statements . . . . . . . . . . 21
1. Introduction 1. Introduction
The Mobile IPv6 (MIPv6) specification [1] requires a Mobile Node (MN) The Mobile IPv6 (MIPv6) specification [1] requires a Mobile Node (MN)
to perform registration with a Home Agent (HA) with information about to perform registration with a Home Agent (HA) with information about
its current point of attachment (care-of address). The HA creates its current point of attachment (care-of address). The HA creates
and maintains binding between the MN's Home Address and the MN's and maintains binding between the MN's Home Address and the MN's
Care-of Address. Care-of Address.
In order to register with a HA, the MN needs to know some information In order to register with a HA, the MN needs to know some information
skipping to change at page 6, line 14 skipping to change at page 7, line 14
the mobile node. the mobile node.
4. Commands, AVPs and Advertising Application Support 4. Commands, AVPs and Advertising Application Support
This section describes command codes, defines AVPs and advertised This section describes command codes, defines AVPs and advertised
application identifiers for the Diameter MIPv6 bootstrapping in the application identifiers for the Diameter MIPv6 bootstrapping in the
NAS to HAAA interface. NAS to HAAA interface.
4.1. Advertising Application Support 4.1. Advertising Application Support
Diameter nodes conforming to this specification MUST include the This document defines a number of MIPv6 bootstrapping NAS to HAAA
value of 1 (NASREQ application) or 5 (EAP application) in the Auth- interface (integrated scenario) related AVPs that can be used in
Application-Id and the Acct-Application-Id AVP of the Capabilities- existing Diameter applications where permitted by the command ABNF
Exchange-Request / Capabilities-Exchange-Answer commands [3]. and in all new applications. This document shows explicit examples
using NASREQ [3] and EAP [4] applications.
4.2. Command Codes 4.2. Command Codes
This document re-uses the Diameter NASREQ application [4] and the EAP This document shows re-use of the Diameter NASREQ application [3] and
application commands [5]. The following commands are used to carry the EAP application commands [4] as an example of the MIPv6
MIPv6 related bootstrapping AVPs: bootstrapping NAS to HAAA interface. The following commands are used
to carry MIPv6 related bootstrapping AVPs:
Command-Name Abbrev. Code Reference Application Command-Name Abbrev. Code Reference Application
Diameter-EAP-Request DER 268 RFC 4072 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
AA-Request AAR 265 RFC 4005 NASREQ AA-Request AAR 265 RFC 4005 NASREQ
AA-Answer AAA 265 RFC 4005 NASREQ AA-Answer AAA 265 RFC 4005 NASREQ
Figure 2: MIPv6 Bootstrapping NAS to HAAA Interface Command Codes Figure 2: MIPv6 Bootstrapping NAS to HAAA Interface Command Codes
When the Re-Auth-Request (RAR), Re-Auth-Answer (RAA), Session- When the Re-Auth-Request (RAR), Re-Auth-Answer (RAA), Session-
Termination-Request (STR), Session-Termination-Answer (STA), Abort- Termination-Request (STR), Session-Termination-Answer (STA), Abort-
Session-Request (ASR), Abort-Session-Answer (ASA), Accounting-Request Session-Request (ASR), Abort-Session-Answer (ASA), Accounting-Request
(ACR), and Accounting-Answer (ACA) commands are used together with (ACR), and Accounting-Answer (ACA) commands are used together with
the MIPv6 bootstrapping NAS to HAAA interface, they follow the rules the MIPv6 bootstrapping NAS to HAAA interface, they follow the rules
in the Diameter NASREQ [4], EAP [5] and RFC 3588 [3] applications. defined in RFC 3588 [5] and the respective used applications. The
The accounting commands use the Application Identifier value of 3 accounting commands use the Application Identifier value of 3
(Diameter Base Accounting); the others use 0 (Diameter Common (Diameter Base Accounting); the others use 0 (Diameter Common
Messages). Messages).
All request messages SHOULD contain the User-Name AVP containing the All request messages SHOULD contain the User-Name AVP containing the
identity of the MN in NAI format. It is out of scope how the NAS identity of the MN in NAI format. It is out of scope how the NAS
finds out the MN identity However, for example, the NAS could use the finds out the MN identity However, for example, the NAS could use the
MN identity provided by the network access authentication mechanism. MN identity provided by the network access authentication mechanism.
4.3. Diameter-EAP-Request (DER) 4.3. Diameter-EAP-Request (DER)
The Diameter-EAP-Request (DER) message [5], indicated by the Command- The Diameter-EAP-Request (DER) message [4], 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 NAS to the Diameter server to initiate a network is sent by the NAS to the Diameter server to initiate a network
access authentication and authorization procedure. The DER message access authentication and authorization procedure. The DER message
format is the same as defined in [5]. The message MAY include format is the same as defined in [4]. The message MAY include
optional MIPv6 bootstrapping AVPs: optional MIPv6 bootstrapping AVPs:
<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 }
* [ MIP6-Agent-Info ] * [ MIP6-Agent-Info ]
* [ MIP6-Home-Link-Prefix ]
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
[ User-Name ] [ User-Name ]
[ Destination-Host ] [ Destination-Host ]
... ...
* [ AVP ] * [ AVP ]
4.4. Diameter-EAP-Answer (DEA) 4.4. Diameter-EAP-Answer (DEA)
The Diameter-EAP-Answer (DEA) message defined in [5], indicated by The Diameter-EAP-Answer (DEA) message defined in [4], 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 network access authentication procedure was successful (DER). If the network access 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 [5] with an addition The DEA message format is the same as defined in [4] with an addition
of optional MIPv6 bootstrapping AVPs: of optional MIPv6 bootstrapping AVPs:
<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 }
* [ MIP6-Agent-Info ] * [ MIP6-Agent-Info ]
* [ MIP6-Home-Link-Prefix ]
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
[ User-Name ] [ User-Name ]
... ...
* [ AVP ] * [ AVP ]
4.5. AA-Request (AAR) 4.5. AA-Request (AAR)
The AA-Request (AAR) message [4], indicated by the Command-Code field The AA-Request (AAR) message [3], indicated by the Command-Code field
set to 265 and 'R' bit set in the Command Flags field, is sent by the set to 265 and 'R' bit set in the Command Flags field, is sent by the
NAS to the Diameter server to initiate a network access NAS to the Diameter server to initiate a network access
authentication and authorization procedure. The AAR message format authentication and authorization procedure. The AAR message format
is the same as defined in [4]. The message MAY include optional is the same as defined in [3]. The message MAY include optional
MIPv6 bootstrapping AVPs: MIPv6 bootstrapping AVPs:
<AA-Request> ::= < Diameter Header: 265, REQ, PXY > <AA-Request> ::= < Diameter Header: 265, REQ, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Destination-Realm } { Destination-Realm }
{ Auth-Request-Type } { Auth-Request-Type }
* [ MIP6-Agent-Info ] * [ MIP6-Agent-Info ]
* [ MIP6-Home-Link-Prefix ]
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
[ User-Name ] [ User-Name ]
[ Destination-Host ] [ Destination-Host ]
... ...
* [ AVP ] * [ AVP ]
4.6. AA-Answer (AAA) 4.6. AA-Answer (AAA)
The AA-Answer (AAA) message, indicated by the Command-Code field set The AA-Answer (AAA) message, indicated by the Command-Code field set
to 265 and 'R' bit cleared in the Command Flags field is sent in to 265 and 'R' bit cleared in the Command Flags field is sent in
response to the AA-Request (AAR) message for confirmation of the response to the AA-Request (AAR) message for confirmation of the
result of MIPv6 HA bootstrapping. If the network access result of MIPv6 HA bootstrapping. If the network access
authentication procedure was successful then the response MAY include authentication procedure was successful then the response MAY include
any set of bootstrapping AVPs. any set of bootstrapping AVPs.
The AAA message format is the same as defined in [4] with an addition The AAA message format is the same as defined in [3] with an addition
of optional MIPv6 bootstrapping AVPs: of optional MIPv6 bootstrapping AVPs:
<AA-Answer> ::= < Diameter Header: 265, PXY > <AA-Answer> ::= < Diameter Header: 265, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Auth-Request-Type } { Auth-Request-Type }
{ Result-Code } { Result-Code }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
* [ MIP6-Agent-Info ] * [ MIP6-Agent-Info ]
* [ MIP6-Home-Link-Prefix ]
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
[ User-Name ] [ User-Name ]
... ...
* [ AVP ] * [ AVP ]
4.7. Attribute Value Pair Definitions 4.7. Attribute Value Pair Definitions
4.7.1. MIP6-Agent-Info 4.7.1. MIP6-Agent-Info
skipping to change at page 10, line 18 skipping to change at page 11, line 19
contains the identity of the assigned HA. Both the Destination-Realm contains the identity of the assigned HA. Both the Destination-Realm
and the Destination-Host AVP of the HA are included in the grouped and the Destination-Host AVP of the HA are included in the grouped
AVP. The usage of this AVP is equivalent to the MIP-Home-Agent- AVP. The usage of this AVP is equivalent to the MIP-Home-Agent-
Address AVP but offers an additional level of indirection via the DNS Address AVP but offers an additional level of indirection via the DNS
infrastructure. infrastructure.
This AVP MAY also be attached by the NAS or by the intermediate local This AVP MAY also be attached by the NAS or by the intermediate local
Diameter proxy when sent to the Diameter server in a request message Diameter proxy when sent to the Diameter server in a request message
as a hint of a locally assigned HA. as a hint of a locally assigned HA.
4.7.4. MIP6-Feature-Vector AVP 4.7.4. MIP6-Home-Link-Prefix AVP
The MIP6-Home-Link-Prefix AVP (AVP Code TBD) is of type OctetString
and contains the Mobile IPv6 home network prefix information in a
network byte order. The home network prefix MUST be encoded as the
8-bit prefix length information followed by the 128-bit field for the
available home network prefix.
4.7.5. MIP6-Feature-Vector AVP
The MIP6-Feature-Vector AVP (AVP Code TBD) is of type Unsigned64 and The MIP6-Feature-Vector AVP (AVP Code TBD) is of type Unsigned64 and
contains a 64 bits flags field of supported capabilities of the NAS/ contains a 64 bits flags field of supported capabilities of the NAS/
ASP. Sending and receiving the MIP6-Feature-Vector AVP with value 0 ASP. Sending and receiving the MIP6-Feature-Vector AVP with value 0
MUST be supported, although that does not provide much guidance about MUST be supported, although that does not provide much guidance about
specific needs of bootstrapping. specific needs of bootstrapping.
The NAS MAY include this AVP to indicate capabilities of the NAS/ASP The NAS MAY include this AVP to indicate capabilities of the NAS/ASP
to the Diameter server. For example, the NAS may indicate that a to the Diameter server. For example, the NAS may indicate that a
local home agent can be provided. Similarly, the Diameter server MAY local home agent can be provided. Similarly, the Diameter server MAY
include this AVP to inform the NAS/ASP about which of the NAS/ASP include this AVP to inform the NAS/ASP about which of the NAS/ASP
indicated capabilities are supported or authorized by the ASA/MSA(/ indicated capabilities are supported or authorized by the ASA/MSA(/
MSP). MSP).
The following capabilities are defined in this document: The following capabilities are defined in this document:
MOBILITY_CAPABILITY (0x0000000000000000)
The MIP6-Feature-Vector AVP MAY contain value 0 (zero) with the
semantics that Mobile IPv6 bootstrapping is generally supported.
This value represents the default when the MIP6-Feature-Vector AVP
is included in a message.
MIP6_INTEGRATED (0x0000000000000001) MIP6_INTEGRATED (0x0000000000000001)
The entity that sets the flag has an impact on the semantic. When When this flag is set by the NAS then it means that the Mobile
this flag is set by the NAS then it means that the Mobile IPv6 IPv6 integrated scenario bootstrapping functionality is supported
integrated scenario bootstrapping functionality is supported by by the NAS. When this flag is set by the Diameter server then the
the NAS. When this flag is set by the Diameter server then the
Mobile IPv6 integrated scenario bootstrapping is supported by the Mobile IPv6 integrated scenario bootstrapping is supported by the
Diameter server. Diameter server.
LOCAL_HOME_AGENT_ASSIGNMENT (0x0000000000000002) LOCAL_HOME_AGENT_ASSIGNMENT (0x0000000000000002)
The entity that sets the flag has an impact on the semantic. When When this flag is set by the NAS then a local home agent can be
this flag is set by the NAS then a local home agent can be
assigned to the MN. When this flag is set by the Diameter server assigned to the MN. When this flag is set by the Diameter server
then the assignment of location HAs is authorized by the Diameter then the assignment of location HAs is authorized by the Diameter
server. server.
The following examples show how the LOCAL_HOME_AGENT_ASSIGNMENT
capability and the MIP-Home-Agent-Host AVP are used to assign a home
agent. Below is an example of a request message combinations:
LOCAL-bit HA-Address Meaning
0 - NAS is not able to assign a local HA
0 ASP-HA Same as above. HA-Address must be ignored
1 - NAS can/wishes to assign a local HA
1 ASP-HA Same as above and NAS also provides a hint
of the assigned HA
Then the same as above for an answer message combinations:
LOCAL-bit HA-Address Meaning
0 - No HA allowed -> no mobility
0 MSP-HA Local HA is not allowed. AAA assigns a HA
1 - Local HA is allowed. No AAA assigned HA
1 MSP-HA Local HA is allowed. AAA also assigns its
own HA. NAS can choose whether to assign
a local HA or the AAA provided HA to the
mobile node
5. Examples 5. Examples
5.1. Home Agent Assignment by the NAS 5.1. Home Agent Assignment by the NAS
In this scenario we consider the case where the NAS wishes to In this scenario we consider the case where the NAS wishes to
allocate a local HA to the MN. The NAS will also inform the Diameter allocate a local HA to the MN. The NAS will also inform the Diameter
server about the HA address it has assigned to the visiting MN (e.g., server about the HA address it has assigned to the visiting MN (e.g.,
2001:db8:1:c020::1). The Diameter-EAP-Request message therefore has 2001:db8:1:c020::1). The Diameter-EAP-Request message therefore has
the MIP6-Feature-Vector with the LOCAL_HOME_AGENT_ASSIGNMENT and the the MIP6-Feature-Vector with the LOCAL_HOME_AGENT_ASSIGNMENT and the
MIP6_INTEGRATED set. The MIP6-Agent-Info AVP contains the MIP-Home- MIP6_INTEGRATED set. The MIP6-Agent-Info AVP contains the MIP-Home-
skipping to change at page 14, line 48 skipping to change at page 15, line 48
Diameter returns the MIP6-Feature-Vector AVP with Diameter returns the MIP6-Feature-Vector AVP with
LOCAL_HOME_AGENT_ASSIGNMENT bit unset and HA address it plans to LOCAL_HOME_AGENT_ASSIGNMENT bit unset and HA address it plans to
allocate for the MN. allocate for the MN.
6. AVP Occurrence Tables 6. AVP Occurrence Tables
6.1. AAR, AAA, DER and DEA Commands AVP Table 6.1. AAR, AAA, DER and DEA Commands AVP Table
The following table lists the additional MIPv6 bootstrapping NAS to The following table lists the additional MIPv6 bootstrapping NAS to
HAAA interface AVPs that may optionally be present in the AAR and AAA HAAA interface AVPs that may optionally be present in the AAR and AAA
Commands [4] or in the DER and DEA Commands [5]. Commands [3] or in the DER and DEA Commands [4].
+-----------------------+ +-----------------------+
| Command-Code | | Command-Code |
|-----+-----+-----+-----+ |-----+-----+-----+-----+
Attribute Name | AAR | AAA | DER | DEA | Attribute Name | AAR | AAA | DER | DEA |
-------------------------------|-----+-----|-----+-----+ -------------------------------|-----+-----|-----+-----+
MIP6-Agent-Info | 0+ | 0+ | 0+ | 0+ | MIP6-Agent-Info | 0+ | 0+ | 0+ | 0+ |
MIP6-Feature-Vector | 0-1 | 0-1 | 0-1 | 0-1 | MIP6-Feature-Vector | 0-1 | 0-1 | 0-1 | 0-1 |
MIP6-Home-Link-Prefix | 0+ | 0+ | 0+ | 0+ |
+-----+-----+-----+-----+ +-----+-----+-----+-----+
Figure 6: AAR, AAA, DER and DEA Commands AVP Table Figure 6: AAR, AAA, DER and DEA Commands AVP Table
7. MIPv6 Bootstrapping NAS to HAAA Interface AVPs 7. MIPv6 Bootstrapping NAS to HAAA Interface AVPs
This section defines AVPs that are specific to Diameter MIPv6 This section defines AVPs that are specific to Diameter MIPv6
bootstrapping NAS to HAAA interface and MAY be included in the bootstrapping NAS to HAAA interface and MAY be included in the
Diameter EAP [5] and the NASREQ [4] application messages. The Diameter EAP [4] and the NASREQ [3] application messages. The
Diameter AVP rules are defined in the Diameter Base [3], Section 4. Diameter AVP rules are defined in the Diameter Base [5], Section 4.
These AVP rules are observed in AVPs defined in this section. These AVP rules are observed in AVPs defined in this section.
The following table describes the Diameter AVPs, their AVP Code The following table describes the Diameter AVPs, their AVP Code
values, types, possible flag values, and whether the AVP MAY be values, types, possible flag values, and whether the AVP MAY be
encrypted. The Diameter base [3] specifies the AVP Flag rules for encrypted. The Diameter base [5] specifies the AVP Flag rules for
AVPs in Section 4.5. AVPs in Section 4.5.
+---------------------+ +---------------------+
| AVP Flag rules | | AVP Flag rules |
+----+-----+----+-----+----+ +----+-----+----+-----+----+
AVP Section | | |SHLD|MUST | | AVP Section | | |SHLD|MUST | |
Attribute Name Code Defined Data Type |MUST| MAY |NOT |NOT |Encr| Attribute Name Code Defined Data Type |MUST| MAY |NOT |NOT |Encr|
------------------------------------------+----+-----+----+-----+----+ ------------------------------------------+----+-----+----+-----+----+
MIP6-Agent-Info TBD 4.7.1 Grouped | | M,P | | V | Y | MIP6-Agent-Info TBD 4.7.1 Grouped | | P | | V,M | Y |
MIP-Home-Agent- | | | | | | MIP-Home-Agent- | | | | | |
Address 334 4.7.2 Address | | M,P | | V | Y | Address 334 4.7.2 Address | | P | | V,M | Y |
MIP-Home-Agent- | | | | | | MIP-Home-Agent- | | | | | |
Host 348 4.7.3 Grouped | | M,P | | V | Y | Host 348 4.7.3 Grouped | | P | | V,M | Y |
MIP6-Feature- | | | | | | MIP6-Feature- | | | | | |
Vector TBD 4.7.4 Unsigned64 | | M,P | | V | Y | Vector TBD 4.7.5 Unsigned64 | | P | | V,M | Y |
MIP6-Home-Link- TBD 4.7.4 OctetString| | P | | V,M | Y |
Prefix | | | | | |
------------------------------------------+----+-----+----+-----+----+ ------------------------------------------+----+-----+----+-----+----+
Figure 7: AVP Flag Rules Table Figure 7: AVP Flag Rules Table
8. IANA Considerations 8. IANA Considerations
8.1. Registration of new AVPs 8.1. Registration of new AVPs
This specification defines the following new AVPs: This specification defines the following new AVPs:
MIP6-Agent-Info is set to TBD MIP6-Agent-Info is set to TBD
MIP6-Feature-Vector is set to TBD MIP6-Feature-Vector is set to TBD
MIP6-Home-Link-Prefix is set to TBD
8.2. New Registry: Mobility Capability 8.2. New Registry: Mobility Capability
IANA is requested to create a new registry for the Mobility IANA is requested to create a new registry for the Mobility
Capability as described in Section 4.7.4. Capability as described in Section 4.7.5.
Token | Value | Description Token | Value | Description
----------------------------------+----------------------+------------ ----------------------------------+----------------------+------------
MOBILITTY_CAPABILITY | 0x0000000000000000 | [RFC TBD]
MIP6_INTEGRATED | 0x0000000000000001 | [RFC TBD] MIP6_INTEGRATED | 0x0000000000000001 | [RFC TBD]
LOCAL_HOME_AGENT_ASSIGNMENT | 0x0000000000000002 | [RFC TBD] LOCAL_HOME_AGENT_ASSIGNMENT | 0x0000000000000002 | [RFC TBD]
Available for Assignment via IANA | 2^x | Available for Assignment via IANA | 2^x |
Allocation rule: Only numeric values that are 2^x (power of two) are Allocation rule: Only numeric values that are 2^x (power of two) are
allowed based on the allocation policy described below. allowed based on the allocation policy described below.
Following the policies outlined in [1] new values with a description Following the policies outlined in [1] new values with a description
of their semantic for usage with the MIP6-Feature-Vector AVP together of their semantic for usage with the MIP6-Feature-Vector AVP together
with a Token will be assigned after Expert Review initiated by the with a Token will be assigned after Expert Review initiated by the
skipping to change at page 16, line 42 skipping to change at page 17, line 44
Updates can be provided based on expert approval only. A designated Updates can be provided based on expert approval only. A designated
expert will be appointed by the O&M Area Directors. No mechanism to expert will be appointed by the O&M Area Directors. No mechanism to
mark entries as "deprecated" is envisioned. Based on expert approval mark entries as "deprecated" is envisioned. Based on expert approval
it is possible to delete entries from the registry. it is possible to delete entries from the registry.
9. Security Considerations 9. Security Considerations
The security considerations for the Diameter interaction required to The security considerations for the Diameter interaction required to
accomplish the integrated scenario are described in [11]. accomplish the integrated scenario are described in [11].
Additionally, the security considerations of the Diameter base Additionally, the security considerations of the Diameter base
protocol [3], Diameter NASREQ application [4] / Diameter EAP [5] protocol [5], Diameter NASREQ application [3] / Diameter EAP [4]
application (with respect to network access authentication and the application (with respect to network access authentication and the
transport of keying material) are applicable to this document. This transport of keying material) are applicable to this document. This
document does not introduce new security vulnerabilities. document does not introduce new security vulnerabilities.
10. Acknowledgements 10. Acknowledgements
This document is heavily based on the ongoing work for RADIUS MIPv6 This document is heavily based on the ongoing work for RADIUS MIPv6
interaction. Hence, credits go to respective authors for their work interaction. Hence, credits go to respective authors for their work
with draft-ietf-mip6-radius. Furthermore, the author would like to with draft-ietf-mip6-radius. Furthermore, the author would like to
thank the authors of draft-le-aaa-diameter-mobileipv6 (Franck Le, thank the authors of draft-le-aaa-diameter-mobileipv6 (Franck Le,
Basavaraj Patil, Charles E. Perkins, Stefano Faccin) for their work Basavaraj Patil, Charles E. Perkins, Stefano Faccin) for their work
in context of MIPv6 Diameter interworking. Their work influenced in context of MIPv6 Diameter interworking. Their work influenced
this document. Jouni Korhonen would like to thank Academy of Finland this document. Jouni Korhonen would like to thank Academy of Finland
and TEKES MERCoNe Project for providing funding to work on this and TEKES MERCoNe Project for providing funding to work on this
document. Julien Bournelle would like to thank GET/INT since he document. Julien Bournelle would like to thank GET/INT since he
began to work on this document while he was in their employ. Authors began to work on this document while he was in their employ. Authors
would also like to acknowledge Raymond Hsu for his valuable feedback would also like to acknowledge Raymond Hsu for his valuable feedback
on local HA assignment and Wolfgang Fritsche for his thorough review. on local HA assignment and Wolfgang Fritsche for his thorough review.
Finally, we would like to Domagoj Premec for his review comments.
11. References 11. References
11.1. Normative References 11.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] Bradner, S., "Key words for use in RFCs to Indicate Requirement [2] 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.
[3] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko, [3] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter
"Diameter Base Protocol", RFC 3588, September 2003.
[4] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter
Network Access Server Application", RFC 4005, August 2005. Network Access Server Application", RFC 4005, August 2005.
[5] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible [4] 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.
[5] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko,
"Diameter Base Protocol", RFC 3588, September 2003.
[6] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and P. [6] 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.
11.2. Informative References 11.2. Informative References
[7] Giaretta, G., Kempf, J., and V. Devarapalli, "Mobile IPv6 [7] Giaretta, G., Kempf, J., and V. Devarapalli, "Mobile IPv6
Bootstrapping in Split Scenario", RFC 5026, October 2007. Bootstrapping in Split Scenario", RFC 5026, October 2007.
[8] Patel, A. and G. Giaretta, "Problem Statement for bootstrapping [8] Patel, A. and G. Giaretta, "Problem Statement for bootstrapping
skipping to change at page 18, line 39 skipping to change at page 20, line 4
Email: julien.bournelle@orange-ftgroup.com Email: julien.bournelle@orange-ftgroup.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
Charles E. Perkins Charles E. Perkins
Nokia Siemens Networks Palo Alto Systems Research Center
313 Fairchild Drive 975 Page Mill Road, Suite 200
Mountain View CA 94043 Palo Alto CA 94304-1003
US USA
Phone: +1-650-496-4402
Email: charles.perkins@nokia.com
Phone: +1 650 625-2986
Email: charliep@nsn.com
Kuntal Chowdhury Kuntal Chowdhury
Starent Networks Starent Networks
30 International Place 30 International Place
Tewksbury MA 01876 Tewksbury MA 01876
US US
Phone: +1 214 550 1416 Phone: +1 214 550 1416
Email: kchowdhury@starentnetworks.com Email: kchowdhury@starentnetworks.com
Full Copyright Statement Full Copyright Statement
 End of changes. 44 change blocks. 
90 lines changed or deleted 125 lines changed or added

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