draft-ietf-dime-mip6-split-11.txt   draft-ietf-dime-mip6-split-12.txt 
Diameter Maintenance and J. Korhonen Diameter Maintenance and J. Korhonen
Extensions (DIME) TeliaSonera Extensions (DIME) TeliaSonera
Internet-Draft H. Tschofenig Internet-Draft H. Tschofenig
Intended status: Standards Track Nokia Siemens Networks Intended status: Standards Track Nokia Siemens Networks
Expires: March 20, 2009 J. Bournelle Expires: March 27, 2009 J. Bournelle
Orange Labs Orange Labs
G. Giaretta G. Giaretta
Qualcomm Qualcomm
M. Nakhjiri M. Nakhjiri
Motorola Motorola
September 16, 2008 September 23, 2008
Diameter Mobile IPv6: Support for Home Agent to Diameter Server Diameter Mobile IPv6: Support for Home Agent to Diameter Server
Interaction Interaction
draft-ietf-dime-mip6-split-11.txt draft-ietf-dime-mip6-split-12.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 March 20, 2009. This Internet-Draft will expire on March 27, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
Mobile IPv6 deployments may want to bootstrap their operations Mobile IPv6 deployments may want to bootstrap their operations
dynamically based on an interaction between the Home Agent and the dynamically based on an interaction between the Home Agent and the
Diameter server of the Mobile Service Provider (MSP). This document Diameter server of the Mobile Service Provider (MSP). This document
skipping to change at page 3, line 32 skipping to change at page 3, line 32
5.1. Command Code for Mobile IPv6 with IKEv2 and EAP . . . . . 14 5.1. Command Code for Mobile IPv6 with IKEv2 and EAP . . . . . 14
5.1.1. Diameter-EAP-Request . . . . . . . . . . . . . . . . . 14 5.1.1. Diameter-EAP-Request . . . . . . . . . . . . . . . . . 14
5.1.2. Diameter-EAP-Answer . . . . . . . . . . . . . . . . . 15 5.1.2. Diameter-EAP-Answer . . . . . . . . . . . . . . . . . 15
5.2. Command Codes for Mobile IPv6 Authentication Protocol 5.2. Command Codes for Mobile IPv6 Authentication Protocol
Support . . . . . . . . . . . . . . . . . . . . . . . . . 16 Support . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.2.1. MIP6-Request . . . . . . . . . . . . . . . . . . . . . 17 5.2.1. MIP6-Request . . . . . . . . . . . . . . . . . . . . . 17
5.2.2. MIP6-Answer . . . . . . . . . . . . . . . . . . . . . 18 5.2.2. MIP6-Answer . . . . . . . . . . . . . . . . . . . . . 18
6. AVPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 6. AVPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.1. User-Name AVP . . . . . . . . . . . . . . . . . . . . . . 21 6.1. User-Name AVP . . . . . . . . . . . . . . . . . . . . . . 21
6.2. Service-Selection AVP . . . . . . . . . . . . . . . . . . 21 6.2. Service-Selection AVP . . . . . . . . . . . . . . . . . . 21
6.3. MIP-MN-AAA-SPI AVP . . . . . . . . . . . . . . . . . . . . 21 6.3. MIP-MN-AAA-SPI AVP . . . . . . . . . . . . . . . . . . . . 22
6.4. MIP-MN-HA-SPI AVP . . . . . . . . . . . . . . . . . . . . 22 6.4. MIP-MN-HA-SPI AVP . . . . . . . . . . . . . . . . . . . . 22
6.5. MIP-Mobile-Node-Address AVP . . . . . . . . . . . . . . . 22 6.5. MIP-Mobile-Node-Address AVP . . . . . . . . . . . . . . . 22
6.6. MIP6-Agent-Info AVP . . . . . . . . . . . . . . . . . . . 22 6.6. MIP6-Agent-Info AVP . . . . . . . . . . . . . . . . . . . 22
6.7. MIP-Careof-Address AVP . . . . . . . . . . . . . . . . . . 22 6.7. MIP-Careof-Address AVP . . . . . . . . . . . . . . . . . . 23
6.8. MIP-Authenticator AVP . . . . . . . . . . . . . . . . . . 23 6.8. MIP-Authenticator AVP . . . . . . . . . . . . . . . . . . 23
6.9. MIP-MAC-Mobility-Data AVP . . . . . . . . . . . . . . . . 23 6.9. MIP-MAC-Mobility-Data AVP . . . . . . . . . . . . . . . . 23
6.10. MIP-Session-Key AVP . . . . . . . . . . . . . . . . . . . 23 6.10. MIP-Session-Key AVP . . . . . . . . . . . . . . . . . . . 23
6.11. MIP-MSA-Lifetime AVP . . . . . . . . . . . . . . . . . . . 23 6.11. MIP-MSA-Lifetime AVP . . . . . . . . . . . . . . . . . . . 23
6.12. MIP-MN-HA-MSA AVP . . . . . . . . . . . . . . . . . . . . 23 6.12. MIP-MN-HA-MSA AVP . . . . . . . . . . . . . . . . . . . . 24
6.13. MIP-Algorithm-Type AVP . . . . . . . . . . . . . . . . . . 24 6.13. MIP-Algorithm-Type AVP . . . . . . . . . . . . . . . . . . 24
6.14. MIP-Replay-Mode AVP . . . . . . . . . . . . . . . . . . . 24 6.14. MIP-Replay-Mode AVP . . . . . . . . . . . . . . . . . . . 24
6.15. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . . . 24 6.15. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . . . 24
6.16. MIP-Timestamp AVP . . . . . . . . . . . . . . . . . . . . 26 6.16. MIP-Timestamp AVP . . . . . . . . . . . . . . . . . . . . 26
6.17. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 26 6.17. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 26
6.18. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 26 6.18. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 26
6.19. Chargeable-User-Identity AVP . . . . . . . . . . . . . . . 26 6.19. Chargeable-User-Identity AVP . . . . . . . . . . . . . . . 26
6.20. MIP6-Auth-Mode AVP . . . . . . . . . . . . . . . . . . . . 26 6.20. MIP6-Auth-Mode AVP . . . . . . . . . . . . . . . . . . . . 26
6.21. Coupled Accounting Model Accounting AVPs . . . . . . . . . 27 6.21. Coupled Accounting Model Accounting AVPs . . . . . . . . . 27
7. Result-Code AVP Values . . . . . . . . . . . . . . . . . . . . 27 7. Result-Code AVP Values . . . . . . . . . . . . . . . . . . . . 27
7.1. Success . . . . . . . . . . . . . . . . . . . . . . . . . 27 7.1. Success . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.2. Permanent Failures . . . . . . . . . . . . . . . . . . . . 28 7.2. Permanent Failures . . . . . . . . . . . . . . . . . . . . 28
8. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 28 8. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 28
8.1. DER, DEA, MIR and MIA AVP/Command-Code Table . . . . . . . 29 8.1. DER, DEA, MIR and MIA AVP/Command-Code Table . . . . . . . 29
8.2. Coupled Accounting Model AVP Table . . . . . . . . . . . . 29 8.2. Coupled Accounting Model AVP Table . . . . . . . . . . . . 29
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
9.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 30 9.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 30
9.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . 30 9.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . 30
9.3. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 31 9.3. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 31
9.4. Application Identifier . . . . . . . . . . . . . . . . . . 31 9.4. Application Identifier . . . . . . . . . . . . . . . . . . 31
9.5. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 31 9.5. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 31
skipping to change at page 21, line 35 skipping to change at page 21, line 35
The User-Name AVP (AVP Code 1) is of type UTF8String and contains an The User-Name AVP (AVP Code 1) is of type UTF8String and contains an
NAI extracted from the MN-NAI mobility option included in the NAI extracted from the MN-NAI mobility option included in the
received BU message. Alternatively, the NAI can be extracted from received BU message. Alternatively, the NAI can be extracted from
the IKEv2 IDi payload included in the IKE_AUTH message sent by the the IKEv2 IDi payload included in the IKE_AUTH message sent by the
IKE initiator. IKE initiator.
6.2. Service-Selection AVP 6.2. Service-Selection AVP
The Service-Selection AVP (AVP Code TBD) is of type UTF8String and The Service-Selection AVP (AVP Code TBD) is of type UTF8String and
contains the string extracted from the IKEv2 IDr payload, if contains the name of the service or the external network that the
available in the IKE_AUTH message sent by the IKE initiator. If the mobility service should be associated with. In the scope of this
Mobile IPv6 Authentication Protocol is used, then the Service- specification the value can extracted from the IKEv2 IDr payload, if
Selection AVP contains the string extracted from the Service available in the IKE_AUTH message sent by the IKE initiator.
Selection Mobility Option [20], if available in the received BU. Alternatively, if the Mobile IPv6 Authentication Protocol is used,
then the Service-Selection AVP contains the string extracted from the
Service Selection Mobility Option [20], if available in the received
BU. Future specification may define additional ways to populate the
Service-Selection AVP with the required information.
This specification uses the Service-Selection AVP only in the
messages sent from the Diameter client to the Diameter Server.
However, the AVP is also available to be used in messages sent from
the Diameter server to the Diameter client.
6.3. MIP-MN-AAA-SPI AVP 6.3. MIP-MN-AAA-SPI AVP
The MIP-MN-AAA-SPI AVP (AVP Code 341) is of type Unsigned32 and The MIP-MN-AAA-SPI AVP (AVP Code 341) is of type Unsigned32 and
contains an SPI code extracted from the Mobility Message contains an SPI code extracted from the Mobility Message
Authentication Option included in the received BU message. The HA Authentication Option included in the received BU message. The HA
includes this AVP in the MIR message when the MN-AAA Mobility Message includes this AVP in the MIR message when the MN-AAA Mobility Message
Authentication Option is available in the received BU (and the MIP6- Authentication Option is available in the received BU (and the MIP6-
Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA). Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA).
 End of changes. 9 change blocks. 
13 lines changed or deleted 22 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/