draft-ietf-dime-mip6-integrated-08.txt   draft-ietf-dime-mip6-integrated-09.txt 
Diameter Maintenance and J. Korhonen Diameter Maintenance and J. Korhonen
Extensions (DIME) TeliaSonera Extensions (DIME) TeliaSonera
Internet-Draft J. Bournelle Internet-Draft J. Bournelle
Intended status: Standards Track Orange Labs Intended status: Standards Track Orange Labs
Expires: August 17, 2008 H. Tschofenig Expires: November 27, 2008 H. Tschofenig
Nokia Siemens Networks Nokia Siemens Networks
C. Perkins C. Perkins
K. Chowdhury K. Chowdhury
Starent Networks Starent Networks
February 14, 2008 May 26, 2008
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-08.txt draft-ietf-dime-mip6-integrated-09.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 42 skipping to change at page 1, line 42
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 17, 2008. This Internet-Draft will expire on November 27, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2008).
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
parameters are statically configured. Mobile IPv6 bootstrapping work parameters are statically configured. Mobile IPv6 bootstrapping work
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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 4 2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Commands, AVPs and Advertising Application Support . . . . . . 7 4. Commands, AVPs and Advertising Application Support . . . . . . 6
4.1. Advertising Application Support . . . . . . . . . . . . . 7 4.1. Advertising Application Support . . . . . . . . . . . . . 6
4.2. Command Codes . . . . . . . . . . . . . . . . . . . . . . 7 4.2. Command Codes . . . . . . . . . . . . . . . . . . . . . . 6
4.3. Diameter-EAP-Request (DER) . . . . . . . . . . . . . . . . 8 4.3. Diameter-EAP-Request (DER) . . . . . . . . . . . . . . . . 7
4.4. Diameter-EAP-Answer (DEA) . . . . . . . . . . . . . . . . 8 4.4. Diameter-EAP-Answer (DEA) . . . . . . . . . . . . . . . . 7
4.5. AA-Request (AAR) . . . . . . . . . . . . . . . . . . . . . 9 4.5. Attribute Value Pair Definitions . . . . . . . . . . . . . 8
4.6. AA-Answer (AAA) . . . . . . . . . . . . . . . . . . . . . 9 4.5.1. MIP6-Agent-Info . . . . . . . . . . . . . . . . . . . 8
4.7. Attribute Value Pair Definitions . . . . . . . . . . . . . 10 4.5.2. MIP-Home-Agent-Address AVP . . . . . . . . . . . . . . 9
4.7.1. MIP6-Agent-Info . . . . . . . . . . . . . . . . . . . 10 4.5.3. MIP-Home-Agent-Host AVP . . . . . . . . . . . . . . . 9
4.7.2. MIP-Home-Agent-Address AVP . . . . . . . . . . . . . . 11 4.5.4. MIP6-Home-Link-Prefix AVP . . . . . . . . . . . . . . 9
4.7.3. MIP-Home-Agent-Host AVP . . . . . . . . . . . . . . . 11 4.5.5. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . 9
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5.2. Home Agent Assignment by the Diameter Server . . . . . . . 12
5.1. Home Agent Assignment by the NAS . . . . . . . . . . . . . 13 5.3. Home Agent Assignment by NAS or Diameter Server . . . . . 12
5.2. Home Agent Assignment by the Diameter Server . . . . . . . 14 6. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 14
5.3. Home Agent Assignment by NAS or Diameter Server . . . . . 14 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
6. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 16 7.1. Registration of new AVPs . . . . . . . . . . . . . . . . . 14
6.1. AAR, AAA, DER and DEA Commands AVP Table . . . . . . . . . 16 7.2. New Registry: Mobility Capability . . . . . . . . . . . . 14
7. MIPv6 Bootstrapping NAS to HAAA Interface AVPs . . . . . . . . 16 8. Security Considerations . . . . . . . . . . . . . . . . . . . 15
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
8.1. Registration of new AVPs . . . . . . . . . . . . . . . . . 17 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
8.2. New Registry: Mobility Capability . . . . . . . . . . . . 17 10.1. Normative References . . . . . . . . . . . . . . . . . . . 15
9. Security Considerations . . . . . . . . . . . . . . . . . . . 18 10.2. Informative References . . . . . . . . . . . . . . . . . . 16
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Intellectual Property and Copyright Statements . . . . . . . . . . 18
11.1. Normative References . . . . . . . . . . . . . . . . . . . 18
11.2. Informative References . . . . . . . . . . . . . . . . . . 19
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 7, line 18 skipping to change at page 6, line 18
authorization and user's policy profile, the Diameter server may authorization and user's policy profile, the Diameter server may
return several MIPv6 bootstrapping related parameters to the NAS. return several MIPv6 bootstrapping related parameters to the NAS.
The NAS to HAAA interface described in this document is not tied to The NAS to HAAA interface described in this document is not tied to
DHCPv6 as the only mechanism to convey MIPv6 related configuration DHCPv6 as the only mechanism to convey MIPv6 related configuration
parameters from the NAS/Diameter client to the mobile node. parameters from the NAS/Diameter client to the mobile node.
4. Commands, AVPs and Advertising Application Support 4. Commands, AVPs and Advertising Application Support
4.1. Advertising Application Support 4.1. Advertising Application Support
This document defines a number of MIPv6 bootstrapping NAS to HAAA This document does not define a new application. On the other hand
interface (integrated scenario) related AVPs. These AVPs can be used it defines a number of MIPv6 bootstrapping NAS to HAAA interface
with present and future Diameter applications, where permitted by the (integrated scenario) related AVPs. These AVPs can be used with
command ABNF. This document does not define a new application. All present and future Diameter applications, where permitted by the
examples in this document reuse NASREQ [3] and EAP [4] applications. command ABNF. The examples using existing applications and their
commands in the following sections are for informational purposes
only. The examples in this document reuse EAP [3] application and
its respective commands.
4.2. Command Codes 4.2. Command Codes
This document shows re-use of the Diameter NASREQ application [3] and This document shows re-use of the Diameter EAP application commands
the EAP application commands [4] as an example of the MIPv6 [3] as an example of the MIPv6 bootstrapping NAS to HAAA interface.
bootstrapping NAS to HAAA interface. The following commands are used Refer to Section 6 and Figure 6 for AVP occurance definitions in
to carry MIPv6 related bootstrapping AVPs: Diameter commands. 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-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
defined in RFC 3588 [5] and the rules for the specific Diameter defined in RFC 3588 [4] and the rules for the specific Diameter
application the AVPs defined in this document are used with. The application the AVPs defined in this document are used with. 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. The NAS could, for example, use the MN finds out the MN identity. The NAS could, for example, use the MN
identity provided by the network access authentication mechanism. 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 [4], indicated by the Command- The Diameter-EAP-Request (DER) message [3], 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 [4]. The message MAY include format is the same as defined in [3]. 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 }
skipping to change at page 8, line 39 skipping to change at page 7, line 39
* [ MIP6-Home-Link-Prefix ] * [ 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 [4], indicated by The Diameter-EAP-Answer (DEA) message defined in [3], 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 [4] with an addition The DEA message format is the same as defined in [3] 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-Home-Link-Prefix ]
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
[ User-Name ] [ User-Name ]
... ...
* [ AVP ] * [ AVP ]
4.5. AA-Request (AAR) 4.5. Attribute Value Pair Definitions
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
NAS to the Diameter server to initiate a network access
authentication and authorization procedure. The AAR message format
is the same as defined in [3]. The message MAY include optional
MIPv6 bootstrapping AVPs:
<AA-Request> ::= < Diameter Header: 265, REQ, PXY >
< Session-Id >
{ Auth-Application-Id }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Auth-Request-Type }
* [ MIP6-Agent-Info ]
* [ MIP6-Home-Link-Prefix ]
[ MIP6-Feature-Vector ]
[ User-Name ]
[ Destination-Host ]
...
* [ AVP ]
4.6. AA-Answer (AAA)
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
response to the AA-Request (AAR) message for confirmation of the
result of MIPv6 HA bootstrapping. If the network access
authentication procedure was successful then the response MAY include
any set of bootstrapping AVPs.
The AAA message format is the same as defined in [3] with an addition
of optional MIPv6 bootstrapping AVPs:
<AA-Answer> ::= < Diameter Header: 265, PXY >
< Session-Id >
{ Auth-Application-Id }
{ Auth-Request-Type }
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
* [ MIP6-Agent-Info ]
* [ MIP6-Home-Link-Prefix ]
[ MIP6-Feature-Vector ]
[ User-Name ]
...
* [ AVP ]
4.7. Attribute Value Pair Definitions
4.7.1. MIP6-Agent-Info 4.5.1. MIP6-Agent-Info
The MIP6-Agent-Info AVP (AVP code TBD) is type of Grouped and The MIP6-Agent-Info AVP (AVP code TBD) is type of Grouped and
contains necessary information to assign a HA to the MN. When the contains necessary information to assign a HA to the MN. When the
MIP6-Agent-Info AVP is present in a message, it MUST contain either MIP6-Agent-Info AVP is present in a message, it MUST contain either
the MIP-Home-Agent-Address AVP or the MIP-Home-Agent-Host AVP, or the MIP-Home-Agent-Address AVP or the MIP-Home-Agent-Host AVP, or
both AVPs. The grouped AVP has the following grammar: both AVPs. The grouped AVP has the following grammar:
<MIP6-Agent-Info> ::= < AVP Header: TBD > <MIP6-Agent-Info> ::= < AVP Header: TBD >
[ MIP-Home-Agent-Address ] [ MIP-Home-Agent-Address ]
[ MIP-Home-Agent-Host ] [ MIP-Home-Agent-Host ]
skipping to change at page 11, line 9 skipping to change at page 9, line 5
an agent may use the MIP-Home-Agent-Host AVP, for instance, to find an agent may use the MIP-Home-Agent-Host AVP, for instance, to find
out the realm where the HA is located. out the realm where the HA is located.
This AVP MAY also be attached by the NAS or by intermediating This AVP MAY also be attached by the NAS or by intermediating
Diameter proxies in a request message when sent to the Diameter Diameter proxies in a request message when sent to the Diameter
server as a hint of a locally assigned HA. This AVP MAY also be server as a hint of a locally assigned HA. This AVP MAY also be
attached by the intermediating Diameter proxies in a reply message attached by the intermediating Diameter proxies in a reply message
from the Diameter server, if locally assigned HAs are authorized by from the Diameter server, if locally assigned HAs are authorized by
the Diameter server. the Diameter server.
4.7.2. MIP-Home-Agent-Address AVP 4.5.2. MIP-Home-Agent-Address AVP
The MIP-Home-Agent-Address AVP (AVP Code 334 [6]) is of type Address The MIP-Home-Agent-Address AVP (AVP Code 334 [5]) is of type Address
and contains the HA address. The Diameter server MAY decide to and contains the HA address. The Diameter server MAY decide to
assign a HA to the MN that is in close proximity to the point of assign a HA to the MN that is in close proximity to the point of
attachment (e.g., determined by the NAS-Identifier AVP). There may attachment (e.g., determined by the NAS-Identifier AVP). There may
be other reasons for dynamically assigning HAs to the MN, for example be other reasons for dynamically assigning HAs to the MN, for example
to share the traffic load. to share the traffic load.
4.7.3. MIP-Home-Agent-Host AVP 4.5.3. MIP-Home-Agent-Host AVP
The MIP-Home-Agent-Host AVP (AVP Code 348 [6]) is of type Grouped and The MIP-Home-Agent-Host AVP (AVP Code 348 [5]) is of type Grouped and
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 by using Address AVP but offers an additional level of indirection by using
the DNS infrastructure. the DNS infrastructure.
Depending on the actual deployment and DNS configuration the Depending on the actual deployment and DNS configuration the
Destination-Host AVP MAY represent one or more home agents. It is Destination-Host AVP MAY represent one or more home agents. It is
RECOMMENDED that the Destination-Host AVP identifies exactly one HA. RECOMMENDED that the Destination-Host AVP identifies exactly one HA.
4.7.4. MIP6-Home-Link-Prefix AVP 4.5.4. MIP6-Home-Link-Prefix AVP
The MIP6-Home-Link-Prefix AVP (AVP Code TBD) is of type OctetString The MIP6-Home-Link-Prefix AVP (AVP Code TBD) is of type OctetString
and contains the Mobile IPv6 home network prefix information in and contains the Mobile IPv6 home network prefix information in
network byte order. The home network prefix MUST be encoded as the 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 8-bit prefix length information followed by the 128-bit field for the
available home network prefix. available home network prefix.
4.7.5. MIP6-Feature-Vector AVP 4.5.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 bit flags field of supported capabilities of the NAS/ contains a 64 bit 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 HA can be provided. Similarly, the Diameter server MAY include local HA can be provided. Similarly, the Diameter server MAY include
skipping to change at page 16, line 7 skipping to change at page 14, line 7
Figure 5: Home Agent Assignment by NAS or Diameter Server Figure 5: Home Agent Assignment by NAS or Diameter Server
If the Diameter server does not accept locally assigned HA, the If the Diameter server does not accept locally assigned HA, the
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
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 be present in any Diameter application
Commands [3] or in the DER and DEA Commands [4]. request and answer commands, where permitted by the command ABNF.
+-----------------------+
| Command-Code |
|-----+-----+-----+-----+
Attribute Name | AAR | AAA | DER | DEA |
-------------------------------|-----+-----|-----+-----+
MIP6-Agent-Info | 0+ | 0+ | 0+ | 0+ |
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
7. MIPv6 Bootstrapping NAS to HAAA Interface AVPs
This section defines AVPs that are specific to Diameter MIPv6
bootstrapping NAS to HAAA interface and MAY be included in the
Diameter EAP [4] and the NASREQ [3] application messages. The
Diameter AVP rules are defined in the Diameter Base [5], Section 4.
These AVP rules are observed in AVPs defined in this section.
The following table describes the Diameter AVPs, their AVP Code
values, types, possible flag values, and whether the AVP MAY be
encrypted. The Diameter base [5] specifies the AVP Flag rules for
AVPs in Section 4.5.
+---------------------+ +-----------+
| AVP Flag rules | | Command |
+----+-----+----+-----+----+ |-----+-----+
AVP Section | | |SHLD|MUST | | Attribute Name | Req | Ans |
Attribute Name Code Defined Data Type |MUST| MAY |NOT |NOT |Encr| -------------------------------|-----+-----|
------------------------------------------+----+-----+----+-----+----+ MIP6-Agent-Info | 0+ | 0+ |
MIP6-Agent-Info TBD 4.7.1 Grouped | | P | | V,M | Y | MIP6-Feature-Vector | 0-1 | 0-1 |
MIP-Home-Agent- | | | | | | MIP6-Home-Link-Prefix | 0+ | 0+ |
Address 334 4.7.2 Address | | P | | V,M | Y | +-----+-----+
MIP-Home-Agent- | | | | | |
Host 348 4.7.3 Grouped | | P | | V,M | Y |
MIP6-Feature- | | | | | |
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 6: Generic Request and Answer Commands AVP Table
8. IANA Considerations 7. IANA Considerations
8.1. Registration of new AVPs 7.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 MIP6-Home-Link-Prefix is set to TBD
8.2. New Registry: Mobility Capability 7.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.5. Capability as described in Section 4.5.5.
Token | Value | Description Token | Value | Description
----------------------------------+----------------------+------------ ----------------------------------+----------------------+------------
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
O&M Area Directors in consultation with the DIME working group chairs O&M Area Directors in consultation with the DIME working group chairs
or the working group chairs of a designated successor working group. or the working group chairs of a designated successor working group.
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 8. 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 [5], Diameter NASREQ application [3] / Diameter EAP [4] protocol [4], Diameter NASREQ application [6] / Diameter EAP [3]
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 9. 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. Finally, we would like to Domagoj Premec for his review comments.
We would like to thank Alper Yegin, Robert Marks, David Frascone for We would like to thank Alper Yegin, Robert Marks, David Frascone for
their comments at the second WGLC. their comments at the second WGLC.
11. References 10. References
11.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] 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., Zorn, G., Spence, D., and D. Mitton, "Diameter [3] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
Network Access Server Application", RFC 4005, August 2005.
[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, [4] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko,
"Diameter Base Protocol", RFC 3588, September 2003. "Diameter Base Protocol", RFC 3588, September 2003.
[6] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and P. [5] 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 [6] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter
Network Access Server Application", RFC 4005, August 2005.
10.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
Mobile IPv6 (MIPv6)", RFC 4640, September 2006. Mobile IPv6 (MIPv6)", RFC 4640, September 2006.
[9] Giaretta, G., Guardini, I., Demaria, E., Bournelle, J., and R. [9] Giaretta, G., Guardini, I., Demaria, E., Bournelle, J., and R.
Lopez, "AAA Goals for Mobile IPv6", Lopez, "AAA Goals for Mobile IPv6",
draft-ietf-mext-aaa-ha-goals-00 (work in progress), draft-ietf-mext-aaa-ha-goals-01 (work in progress), May 2008.
December 2007.
[10] Manner, J. and M. Kojo, "Mobility Related Terminology", [10] Manner, J. and M. Kojo, "Mobility Related Terminology",
RFC 3753, June 2004. RFC 3753, June 2004.
[11] Chowdhury, K. and A. Yegin, "MIP6-bootstrapping for the [11] Chowdhury, K. and A. Yegin, "MIP6-bootstrapping for the
Integrated Scenario", Integrated Scenario",
draft-ietf-mip6-bootstrapping-integrated-dhc-05 (work in draft-ietf-mip6-bootstrapping-integrated-dhc-06 (work in
progress), July 2007. progress), April 2008.
Authors' Addresses Authors' Addresses
Jouni Korhonen Jouni Korhonen
TeliaSonera TeliaSonera
Teollisuuskatu 13 Teollisuuskatu 13
Sonera FIN-00051 Sonera FIN-00051
Finland Finland
Email: jouni.korhonen@teliasonera.com Email: jouni.korhonen@teliasonera.com
skipping to change at page 20, line 20 skipping to change at page 17, line 20
Email: julien.bournelle@orange-ftgroup.com Email: julien.bournelle@orange-ftgroup.com
Hannes Tschofenig Hannes Tschofenig
Nokia Siemens Networks Nokia Siemens Networks
Linnoitustie 6 Linnoitustie 6
Espoo 02600 Espoo 02600
Finland Finland
Phone: +358 (50) 4871445 Phone: +358 (50) 4871445
Email: Hannes.Tschofenig@nsn.com Email: Hannes.Tschofenig@nsn.com
URI: http://www.tschofenig.com URI: http://www.tschofenig.priv.at
Charles E. Perkins Charles E. Perkins
Phone: +1-650-496-4402 Phone: +1-650-496-4402
Email: charliep@computer.org Email: charliep@computer.org
Kuntal Chowdhury Kuntal Chowdhury
Starent Networks Starent Networks
30 International Place 30 International Place
Tewksbury MA 01876 Tewksbury MA 01876
skipping to change at page 21, line 44 skipping to change at line 799
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 42 change blocks. 
187 lines changed or deleted 91 lines changed or added

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