draft-ietf-dime-mip6-split-09.txt   draft-ietf-dime-mip6-split-10.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: December 5, 2008 J. Bournelle Expires: January 7, 2009 J. Bournelle
Orange Labs Orange Labs
G. Giaretta G. Giaretta
Qualcomm Qualcomm
M. Nakhjiri M. Nakhjiri
Motorola Motorola
June 3, 2008 July 6, 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-09.txt draft-ietf-dime-mip6-split-10.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 December 5, 2008. This Internet-Draft will expire on January 7, 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 34 skipping to change at page 3, line 34
5. Command Codes . . . . . . . . . . . . . . . . . . . . . . . . 14 5. Command Codes . . . . . . . . . . . . . . . . . . . . . . . . 14
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 Code for Mobile IPv6 with IKEv2 and 5.2. Command Code for Mobile IPv6 with IKEv2 and
Certificate- and PSK-based Authentication . . . . . . . . 16 Certificate- and PSK-based Authentication . . . . . . . . 16
5.2.1. AA-Request . . . . . . . . . . . . . . . . . . . . . . 16 5.2.1. AA-Request . . . . . . . . . . . . . . . . . . . . . . 16
5.2.2. AA-Answer . . . . . . . . . . . . . . . . . . . . . . 17 5.2.2. AA-Answer . . . . . . . . . . . . . . . . . . . . . . 17
5.3. Command Codes for Mobile IPv6 Authentication Protocol 5.3. Command Codes for Mobile IPv6 Authentication Protocol
Support . . . . . . . . . . . . . . . . . . . . . . . . . 18 Support . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.3.1. MIP6-Request-Message . . . . . . . . . . . . . . . . . 18 5.3.1. MIP6-Request . . . . . . . . . . . . . . . . . . . . . 18
5.3.2. MIP6-Answer-Message . . . . . . . . . . . . . . . . . 19 5.3.2. MIP6-Answer . . . . . . . . . . . . . . . . . . . . . 19
6. AVPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 6. AVPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.1. User-Name AVP . . . . . . . . . . . . . . . . . . . . . . 23 6.1. User-Name AVP . . . . . . . . . . . . . . . . . . . . . . 23
6.2. Called-Station-Id AVP . . . . . . . . . . . . . . . . . . 23 6.2. Service-Selection AVP . . . . . . . . . . . . . . . . . . 23
6.3. MIP-MN-AAA-SPI AVP . . . . . . . . . . . . . . . . . . . . 23 6.3. MIP-MN-AAA-SPI AVP . . . . . . . . . . . . . . . . . . . . 23
6.4. MIP-MN-HA-SPI AVP . . . . . . . . . . . . . . . . . . . . 23 6.4. MIP-MN-HA-SPI AVP . . . . . . . . . . . . . . . . . . . . 23
6.5. MIP-Mobile-Node-Address AVP . . . . . . . . . . . . . . . 23 6.5. MIP-Mobile-Node-Address AVP . . . . . . . . . . . . . . . 24
6.6. MIP-Home-Agent-Address AVP . . . . . . . . . . . . . . . . 24 6.6. MIP6-Agent-Info AVP . . . . . . . . . . . . . . . . . . . 24
6.7. MIP-Careof-Address AVP . . . . . . . . . . . . . . . . . . 24 6.7. MIP-Careof-Address AVP . . . . . . . . . . . . . . . . . . 24
6.8. MIP-Authenticator AVP . . . . . . . . . . . . . . . . . . 24 6.8. MIP-Authenticator AVP . . . . . . . . . . . . . . . . . . 24
6.9. MIP-MAC-Mobility-Data AVP . . . . . . . . . . . . . . . . 24 6.9. MIP-MAC-Mobility-Data AVP . . . . . . . . . . . . . . . . 25
6.10. MIP-Session-Key AVP . . . . . . . . . . . . . . . . . . . 24 6.10. MIP-Session-Key AVP . . . . . . . . . . . . . . . . . . . 25
6.11. MIP-MSA-Lifetime AVP . . . . . . . . . . . . . . . . . . . 25 6.11. MIP-MSA-Lifetime AVP . . . . . . . . . . . . . . . . . . . 25
6.12. MIP-MN-HA-MSA AVP . . . . . . . . . . . . . . . . . . . . 25 6.12. MIP-MN-HA-MSA AVP . . . . . . . . . . . . . . . . . . . . 25
6.13. MIP-Algorithm-Type AVP . . . . . . . . . . . . . . . . . . 25 6.13. MIP-Algorithm-Type AVP . . . . . . . . . . . . . . . . . . 26
6.14. MIP-Replay-Mode AVP . . . . . . . . . . . . . . . . . . . 25 6.14. MIP-Replay-Mode AVP . . . . . . . . . . . . . . . . . . . 26
6.15. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . . . 25 6.15. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . . . 26
6.16. MIP-Timestamp AVP . . . . . . . . . . . . . . . . . . . . 27 6.16. MIP-Timestamp AVP . . . . . . . . . . . . . . . . . . . . 27
6.17. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 27 6.17. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 28
6.18. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 27 6.18. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 28
6.19. Chargeable-User-Identity AVP . . . . . . . . . . . . . . . 27 6.19. Chargeable-User-Identity AVP . . . . . . . . . . . . . . . 28
6.20. Coupled Accounting Model Accounting AVPs . . . . . . . . . 27 6.20. Coupled Accounting Model Accounting AVPs . . . . . . . . . 28
7. Result-Code AVP Values . . . . . . . . . . . . . . . . . . . . 28 7. Result-Code AVP Values . . . . . . . . . . . . . . . . . . . . 29
7.1. Success . . . . . . . . . . . . . . . . . . . . . . . . . 28 7.1. Success . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.2. Permanent Failures . . . . . . . . . . . . . . . . . . . . 28 7.2. Permanent Failures . . . . . . . . . . . . . . . . . . . . 29
8. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 29 8. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 30
8.1. AAR, AAA, DER, DEA, MRM and MAM AVP/Command-Code Table . . 29 8.1. AAR, AAA, DER, DEA, MIR and MIA AVP/Command-Code Table . . 30
8.2. Coupled Accounting Model AVP Table . . . . . . . . . . . . 30 8.2. Coupled Accounting Model AVP Table . . . . . . . . . . . . 31
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32
9.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 30 9.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 32
9.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . 31 9.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . 32
9.3. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 31 9.3. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 33
9.4. Application Identifier . . . . . . . . . . . . . . . . . . 31 9.4. Application Identifier . . . . . . . . . . . . . . . . . . 33
9.5. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 31 9.5. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 33
9.6. Mobile IPv6 Status Codes . . . . . . . . . . . . . . . . . 32 9.6. Mobile IPv6 Status Codes . . . . . . . . . . . . . . . . . 34
10. Security Considerations . . . . . . . . . . . . . . . . . . . 32 10. Security Considerations . . . . . . . . . . . . . . . . . . . 34
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 32 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 34
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 33 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35
12.1. Normative References . . . . . . . . . . . . . . . . . . . 33 12.1. Normative References . . . . . . . . . . . . . . . . . . . 35
12.2. Informative References . . . . . . . . . . . . . . . . . . 34 12.2. Informative References . . . . . . . . . . . . . . . . . . 36
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 34 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 36
Intellectual Property and Copyright Statements . . . . . . . . . . 36 Intellectual Property and Copyright Statements . . . . . . . . . . 38
1. Introduction 1. Introduction
Performing the Mobile IPv6 protocol [1], requires the Mobile Node Performing the Mobile IPv6 protocol [1], requires the Mobile Node
(MN) to own a Home Address (HoA) and to have an assigned Home Agent (MN) to own a Home Address (HoA) and to have an assigned Home Agent
(HA) to the MN. The MN needs to register with the HA in order to (HA) to the MN. The MN needs to register with the HA in order to
enable its reachability and mobility, when away from its home link. enable its reachability and mobility, when away from its home link.
The registration process itself may require an establishment of IPSec The registration process itself may require an establishment of IPSec
security associations (SA) and cryptographic material between the MN security associations (SA) and cryptographic material between the MN
and HA. Alternatively, the registration process may be secured using and HA. Alternatively, the registration process may be secured using
skipping to change at page 7, line 46 skipping to change at page 7, line 46
model. Diameter Base Accounting Application Identifier (value of 3) model. Diameter Base Accounting Application Identifier (value of 3)
is used in the case of split accounting model. Refer Section 4.6 for is used in the case of split accounting model. Refer Section 4.6 for
more information regarding the accounting models. more information regarding the accounting models.
4. Protocol Description 4. Protocol Description
4.1. Support for Mobile IPv6 with IKEv2 and EAP 4.1. Support for Mobile IPv6 with IKEv2 and EAP
The use of IKEv2 with EAP between the MN and the HA allows the AAA to The use of IKEv2 with EAP between the MN and the HA allows the AAA to
authenticate the MN. When EAP is used with IKEv2, the Diameter EAP authenticate the MN. When EAP is used with IKEv2, the Diameter EAP
application, as defined in [7], is re-used. EAP methods that do not application logic and procedures, as defined in [7], are re-used.
establish a shared key SHOULD NOT be used, as they are subject to a EAP methods that do not establish a shared key SHOULD NOT be used, as
number of man-in-the-middle attacks as stated in Section 2.16 and they are subject to a number of man-in-the-middle attacks as stated
Section 5 of RFC 4306 [8]. AVPs specific to Mobile IPv6 in Section 2.16 and Section 5 of RFC 4306 [8]. AVPs specific to
bootstrapping are added to the EAP application commands. Mobile IPv6 bootstrapping are added to the EAP application commands.
Figure 3 shows the message flow involved during the authentication Figure 3 shows the message flow involved during the authentication
phase when EAP is used. phase when EAP is used.
Mobile Home Diameter Mobile Home Diameter
Node Agent Server Node Agent Server
| | | | | |
| HDR, SAi1, KEi, Ni (1) | | | HDR, SAi1, KEi, Ni (1) | |
|-------------------------------->| | |-------------------------------->| |
| | | | | |
skipping to change at page 10, line 24 skipping to change at page 10, line 24
As part of the authentication process, the MN MAY request a Home- As part of the authentication process, the MN MAY request a Home-
Address, a Home Prefix or suggests one, see [4], using a CFG_REQUEST Address, a Home Prefix or suggests one, see [4], using a CFG_REQUEST
payload in the message (3). payload in the message (3).
The HA extracts the IDi field from the message (3) and sends a The HA extracts the IDi field from the message (3) and sends a
Diameter-EAP-Request (DER) message (4) towards the authenticating Diameter-EAP-Request (DER) message (4) towards the authenticating
Diameter server. The EAP-Payload AVP contains a EAP-Response/ Diameter server. The EAP-Payload AVP contains a EAP-Response/
Identity with the identity extracted from the IDi field. Identity with the identity extracted from the IDi field.
This message is routed to the MNs Diameter server/EAP server. The This message is routed to the MN's Diameter server/EAP server. The
Diameter server selects the EAP method and replies with the DEA Diameter server selects the EAP method and replies with the Diameter-
Message. Depending on the type of EAP method chosen, a number of DER EAP-Answer (DEA) Message. Depending on the type of EAP method
and DEA messages carry the method specific exchanges between the MN chosen, a number of DER and DEA messages carry the method specific
and the Diameter server/EAP server. exchanges between the MN and the Diameter server/EAP server.
At the end of the EAP authentication phase, the Diameter server At the end of the EAP authentication phase, the Diameter server
indicates the result of the authentication in the Result-Code AVP and indicates the result of the authentication in the Result-Code AVP and
provides the corresponding EAP packet (EAP Success or EAP Failure). provides the corresponding EAP packet (EAP Success or EAP Failure).
The last IKEv2 message sent by the HA contains the Home Address or 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 the Home Prefix. In the latter case, a CREATE_CHILD_SA exchange is
necessary to setup IPSec SAs for Mobile IPv6 signaling. necessary to setup IPSec SAs for Mobile IPv6 signaling.
In some deployment scenarios, the HA may also acts as a IKEv2 In some deployment scenarios, the HA may also acts as a IKEv2
Responder for IPSec VPN access. A problem in this case is that the Responder for IPSec VPN access. A problem in this case is that the
skipping to change at page 11, line 8 skipping to change at page 11, line 8
inform the HA during the IKEv2 negotiation whether the MN is inform the HA during the IKEv2 negotiation whether the MN is
provisioned with an IPSec VPN access service or Mobile IPv6 service. provisioned with an IPSec VPN access service or Mobile IPv6 service.
Eventually, when the HA receives a Binding Update (BU), the HA Eventually, when the HA receives a Binding Update (BU), the HA
authenticates and authorizes the MN. It is RECOMMENDED that the HA authenticates and authorizes the MN. It is RECOMMENDED that the HA
sends an accounting request message every time it receives a BU. sends an accounting request message every time it receives a BU.
4.2. Support for Mobile IPv6 with IKEv2 and Certificates 4.2. Support for Mobile IPv6 with IKEv2 and Certificates
When IKEv2 is used with certificate-based authentication, the When IKEv2 is used with certificate-based authentication, the
Diameter NASREQ application [9] is used to authorize the MN for the Diameter NASREQ application logic and procedures, as defined in [9],
Mobile IPv6 service. The IDi payload extracted from the IKE_AUTH are re-used to authorize the MN for the Mobile IPv6 service. The IDi
message MUST correspond to the identity in the MN's certificate. payload extracted from the IKE_AUTH message MUST correspond to the
This identity is then used by the HA to populate the User-Name AVP in identity in the MN's certificate. This identity is then used by the
the succeeding AA-Request message. Further PKI-related procedures HA to populate the User-Name AVP in the succeeding AA-Request
such as certificate revocation checking are out of scope of this message. Further PKI-related procedures such as certificate
document. revocation checking are out of scope of this document.
4.3. Support for Mobile IPv6 with IKEv2 and Pre-Shared Secrets 4.3. Support for Mobile IPv6 with IKEv2 and Pre-Shared Secrets
When IKEv2 is used with PSK-based initiator authentication, the When IKEv2 is used with PSK-based initiator authentication, the
Diameter NASREQ application [9] is re-used to authorize the MN for Diameter NASREQ application [9] is re-used to authorize the MN for
the Mobile IPv6 service. The IDi payload extracted from the IKE_AUTH the Mobile IPv6 service. The IDi payload extracted from the IKE_AUTH
message has to contain an identity that is meaningful for the message has to contain an identity that is meaningful for the
Diameter infrastructure, such as a Network Access Identifier (NAI), Diameter infrastructure, such as a Network Access Identifier (NAI),
and is then used by the HA to populate the User-Name AVP in the and is then used by the HA to populate the User-Name AVP in the
succeeding AA-Request message. succeeding AA-Request message.
4.4. Support for the Mobile IPv6 Authentication Protocol 4.4. Support for the Mobile IPv6 Authentication Protocol
Figure 4 shows the message sequence between the MN, the HA and the Figure 4 shows the message sequence between the MN, the HA and the
Diameter server during the registration when Mobile IPv6 Diameter server during the registration when Mobile IPv6
Authentication Protocol is used. A BU and a Binding Acknowledgement Authentication Protocol is used. A BU and a Binding Acknowledgement
(BA) messages are used in the binding registration process. (BA) messages are used in the binding registration process.
Receiving a BU at the HA initiates a MIP6-Request-Message to be sent Receiving a BU at the HA initiates a MIP6-Request to be sent to the
to the Diameter server. The Diameter server in turn responds with a Diameter server. The Diameter server in turn responds with a MIP6-
MIP6-Answer-Message. The HA may assign a Home Address to the MN and Answer. The HA may assign a Home Address to the MN and provide it to
provide it to the Diameter server in the MIP-Mobile-Node-Address AVP. the Diameter server in the MIP-Mobile-Node-Address AVP.
According to [3] the MN uses the Mobile Node Identifier Option, According to [3] the MN uses the Mobile Node Identifier Option,
specifically the MN-NAI mobility option (as defined in [18]) to specifically the MN-NAI mobility option (as defined in [18]) to
identify itself. The HA MUST copy the MN-NAI mobility option value identify itself. The HA MUST copy the MN-NAI mobility option value
to the User-Name AVP in the subsequent request messages. to the User-Name AVP in the subsequent request messages.
The procedure described in this specification for the Mobile IPv6 The procedure described in this specification for the Mobile IPv6
Authentication Protocol is only needed for the initial BU received by Authentication Protocol is only needed for the initial BU received by
the HA. When the HA receives subsequent BUs, they are processed the HA. When the HA receives subsequent BUs, they are processed
locally in the HA. It is RECOMMENDED that the HA sends an accounting locally in the HA. It is RECOMMENDED that the HA sends an accounting
skipping to change at page 12, line 20 skipping to change at page 12, line 20
validation of the MN-HA Authentication Option from the Diameter validation of the MN-HA Authentication Option from the Diameter
server. The Diameter request message sent by the HA must contain server. The Diameter request message sent by the HA must contain
enough information (such as SPI, MN-NAI, etc) so that the Diameter enough information (such as SPI, MN-NAI, etc) so that the Diameter
server is able to locate the matching MN-HA security association and server is able to locate the matching MN-HA security association and
return correct keying material back to the HA. return correct keying material back to the HA.
Mobile Home Diameter Mobile Home Diameter
Node Agent Server Node Agent Server
| | | | | |
| | | | | |
| Binding Update |MIP6-Request-Message | | Binding Update |MIP6-Request |
|------------------------------------>|-------------------->| |------------------------------------>|-------------------->|
| (Mobile Node Identifier Option, | | | (Mobile Node Identifier Option, | |
| Mobility Message Replay Protection | | | Mobility Message Replay Protection | |
| Option, Authentication Option) | | | Option, Authentication Option) | |
| | | | | |
| | | | | |
| Binding Acknowledgement |MIP6-Answer-Message | | Binding Acknowledgement |MIP6-Answer |
|<------------------------------------|<--------------------| |<------------------------------------|<--------------------|
| (Mobile Node Identifier Option | | | (Mobile Node Identifier Option | |
| Mobility Message Replay Protection | | | Mobility Message Replay Protection | |
| Option, Authentication Option) | | | Option, Authentication Option) | |
Figure 4: Mobile IPv6 Bootstrapping using the Mobile IPv6 Figure 4: Mobile IPv6 Bootstrapping using the Mobile IPv6
Authentication Protocol Authentication Protocol
4.5. Mobile IPv6 Session Management 4.5. Mobile IPv6 Session Management
skipping to change at page 14, line 26 skipping to change at page 14, line 26
4.6.2. Accounting-Answer 4.6.2. Accounting-Answer
The Accounting-Answer command [5] is sent by the Diameter server to The Accounting-Answer command [5] is sent by the Diameter server to
the HA to acknowledge receiving an Accounting-Request. the HA to acknowledge receiving an Accounting-Request.
5. Command Codes 5. Command Codes
5.1. Command Code for Mobile IPv6 with IKEv2 and EAP 5.1. Command Code for Mobile IPv6 with IKEv2 and EAP
For the use of Mobile IPv6 with IKEv2 and EAP this document re-uses For the use of Mobile IPv6 with IKEv2 and EAP this document reuses
the Diameter EAP application [7] commands. The command ABNFs are the Diameter EAP application [7] commands: Diameter-EAP-Request (DER)
extended with a number AVPs to support Mobile IPv6 split scenario and Diameter-EAP-Answer (DEA). This specification extends the
bootstrapping. Other than new additional AVPs and the corresponding existing DER and DEA command ABNFs with a number AVPs to support
additions to the command ABNFs, the Diameter EAP application command Mobile IPv6 split scenario bootstrapping. Other than new additional
ABNFs remain unchanged. AVPs and the corresponding additions to the command ABNFs, the
Diameter EAP application command ABNFs remain unchanged.
Command-Name Abbrev. Code Reference Application Command-Name Abbrev. Code Reference Application
--------------------------------------------------------------------- ---------------------------------------------------------------------
Diameter-EAP-Request DER 268 RFC 4072 Diameter Mobile IPv6 IKE Diameter-EAP-Request DER 268 RFC 4072 Diameter Mobile IPv6 IKE
Diameter-EAP-Answer DEA 268 RFC 4072 Diameter Mobile IPv6 IKE Diameter-EAP-Answer DEA 268 RFC 4072 Diameter Mobile IPv6 IKE
Figure 5: Command Codes Figure 5: Command Codes
5.1.1. Diameter-EAP-Request 5.1.1. Diameter-EAP-Request
The Diameter-EAP-Request (DER) message [7], indicated by the Command- The Diameter-EAP-Request (DER) message, indicated by the Command-Code
Code field set to 268 and the 'R' bit set in the Command Flags field, field set to 268 and the 'R' bit set in the Command Flags field, is
is sent by the HA to the Diameter server to initiate a Mobile IPv6 sent by the HA to the Diameter server to initiate a Mobile IPv6
service authentication and authorization procedure. The DER message service authentication and authorization procedure. The
format is the same as defined in [7]. The Application-ID field of Application-ID field of the Diameter Header MUST be set to the
the Diameter Header MUST be set to the Diameter Mobile IPv6 IKE Diameter Mobile IPv6 IKE Application ID (value of TDB).
Application ID (value of TDB).
<Diameter-EAP-Request> ::= < Diameter Header: 268, REQ, PXY > <Diameter-EAP-Request> ::= < Diameter Header: 268, REQ, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Destination-Realm } { Destination-Realm }
{ Auth-Request-Type } { Auth-Request-Type }
[ Destination-Host ] [ Destination-Host ]
[ NAS-Identifier ] [ NAS-Identifier ]
[ NAS-IP-Address ] [ NAS-IP-Address ]
[ NAS-IPv6-Address ] [ NAS-IPv6-Address ]
[ NAS-Port-Type ] [ NAS-Port-Type ]
[ User-Name ] [ User-Name ]
... ...
[ Called-Station-Id]
...
{ EAP-Payload } { EAP-Payload }
... ...
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
1*2{ MIP-Home-Agent-Address } *2[ MIP6-Agent-Info ]
1*2{ MIP-Mobile-Node-Address } *2[ MIP-Mobile-Node-Address ]
[ Chargeable-User-Identity ] [ Chargeable-User-Identity ]
[ Service-Selection ]
[ QoS-Capability ] [ QoS-Capability ]
* [ QoS-Resources ] * [ QoS-Resources ]
... ...
* [ AVP ] * [ AVP ]
5.1.2. Diameter-EAP-Answer 5.1.2. Diameter-EAP-Answer
The Diameter-EAP-Answer (DEA) message defined in [7], indicated by The Diameter-EAP-Answer (DEA) message, indicated by the Command-Code
the Command-Code field set to 268 and 'R' bit cleared in the Command field set to 268 and 'R' bit cleared in the Command Flags field, is
Flags field, is sent in response to the Diameter-EAP-Request message sent in response to the Diameter-EAP-Request message (DER). The
(DER). The DEA message format is the same as defined in [7]. The
Application-Id field in the Diameter message header MUST be set to Application-Id field in the Diameter message header MUST be set to
the Diameter Mobile IPv6 IKE Application-Id (value of TBD). If the the Diameter Mobile IPv6 IKE Application-Id (value of TBD). If the
Mobile IPv6 authentication procedure was successful then the response Mobile IPv6 authentication procedure was successful then the response
MAY include any set of bootstrapping AVPs. MAY include any set of 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 }
skipping to change at page 16, line 21 skipping to change at page 16, line 21
{ Origin-Realm } { Origin-Realm }
[ User-Name ] [ User-Name ]
[ EAP-Payload ] [ EAP-Payload ]
[ EAP-Reissued-Payload ] [ EAP-Reissued-Payload ]
[ EAP-Master-Session-Key ] [ EAP-Master-Session-Key ]
[ EAP-Key-Name ] [ EAP-Key-Name ]
[ Multi-Round-Time [ Multi-Round-Time
... ...
*2[ MIP-Mobile-Node-Address ] *2[ MIP-Mobile-Node-Address ]
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
*2[ MIP-Home-Agent-Address ] *2[ MIP6-Agent-Info ]
* [ QoS-Resources ] * [ QoS-Resources ]
[ Chargeable-User-Identity ] [ Chargeable-User-Identity ]
... ...
* [ AVP ] * [ AVP ]
5.2. Command Code for Mobile IPv6 with IKEv2 and Certificate- and PSK- 5.2. Command Code for Mobile IPv6 with IKEv2 and Certificate- and PSK-
based Authentication based Authentication
This document re-uses the Diameter NASREQ application commands. The For the use of Mobile IPv6 with IKEv2, and certificate- and PSK-based
following commands are used to carry Mobile IPv6 related authentication this document reuses the Diameter NASREQ application
bootstrapping AVPs. [9] commands: AA-Request (AAR) and AA-Answer (AAA). This
specification extends the existing AAR and AAA command ABNFs with a
number AVPs to support Mobile IPv6 split scenario bootstrapping.
Other than new additional AVPs and the corresponding additions to the
command ABNFs, the Diameter NASREQ application command ABNFs remain
unchanged.
Command-Name Abbrev. Code Reference Application Command-Name Abbrev. Code Reference Application
--------------------------------------------------------------------- ---------------------------------------------------------------------
AA-Request AAR 265 RFC 4005 Diameter Mobile IPv6 IKE AA-Request AAR 265 RFC 4005 Diameter Mobile IPv6 IKE
AA-Answer AAA 265 RFC 4005 Diameter Mobile IPv6 IKE AA-Answer AAA 265 RFC 4005 Diameter Mobile IPv6 IKE
Figure 8: Command Codes Figure 8: Command Codes
5.2.1. AA-Request 5.2.1. AA-Request
The AA-Request (AAR) message [9], indicated by the Command-Code field The AA-Request (AAR) message, indicated by the Command-Code field set
set to 265 and the 'R' bit set in the Command Flags field, is sent by to 265 and the 'R' bit set in the Command Flags field, is sent by the
the HA to the Diameter server to initiate a Mobile IPv6 service HA to the Diameter server to initiate a Mobile IPv6 service
authentication and authorization procedure. The AAR message format authentication and authorization procedure. The Application-ID field
is the same as defined in [9]. The Application-ID field of the of the Diameter Header MUST be set to the Diameter Mobile IPv6 IKE
Diameter Header MUST be set to the Diameter Mobile IPv6 IKE
Application ID (value of TBD). Application ID (value of TBD).
<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 }
[ Destination-Host ] [ Destination-Host ]
[ NAS-Identifier ] [ NAS-Identifier ]
[ NAS-IP-Address ] [ NAS-IP-Address ]
[ NAS-IPv6-Address ] [ NAS-IPv6-Address ]
[ NAS-Port-Type ] [ NAS-Port-Type ]
[ User-Name ] [ User-Name ]
... ...
[ Called-Station-Id]
...
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
1*2{ MIP-Home-Agent-Address } *2[ MIP5-Agent-Info ]
1*2{ MIP-Mobile-Node-Address } *2[ MIP-Mobile-Node-Address ]
[ Chargeable-User-Identity ] [ Chargeable-User-Identity ]
... [ Service-Selection ]
[ QoS-Capability ] [ QoS-Capability ]
* [ QoS-Resources ] * [ QoS-Resources ]
... ...
* [ AVP ] * [ AVP ]
5.2.2. AA-Answer 5.2.2. AA-Answer
The AA-Answer (AAA) message defined in [9], indicated by the Command- The AA-Answer (AAA) message, indicated by the Command-Code field set
Code field set to 265 and 'R' bit cleared in the Command Flags field, to 265 and 'R' bit cleared in the Command Flags field, is sent in
is sent in response to the AA-Request message (AAR). If the Mobile response to the AA-Request message (AAR). If the Mobile IPv6
IPv6 authentication procedure was successful then the response MAY authentication procedure was successful then the response MAY include
include any set of bootstrapping AVPs. any set of bootstrapping AVPs. The Application-Id field in the
Diameter header MUST be set to the Diameter Mobile IPv6 IKE
The AAA message format is the same as defined in [9]. The Application-Id (value of TBD).
Application-Id field in the Diameter header MUST be set to the
Diameter Mobile IPv6 IKE Application-Id (value of TBD).
<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 }
[ User-Name ] [ User-Name ]
[ Authorization-Lifetime ] [ Authorization-Lifetime ]
skipping to change at page 18, line 15 skipping to change at page 18, line 15
<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 }
[ User-Name ] [ User-Name ]
[ Authorization-Lifetime ] [ Authorization-Lifetime ]
... ...
*2[ MIP-Mobile-Node-Address ] *2[ MIP-Mobile-Node-Address ]
*2[ MIP-Home-Agent-Address ] *2[ MIP6-Agent-Info ]
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
[ MIP-MN-HA-MSA ] [ MIP-MN-HA-MSA ]
* [ QoS-Resources ] * [ QoS-Resources ]
[ Chargeable-User-Identity ] [ Chargeable-User-Identity ]
... ...
* [ AVP ] * [ AVP ]
When IKEv2 is used with PSK-based initiator authentication, the pre- When IKEv2 is used with PSK-based initiator authentication, the pre-
shared secret is carried inside the MIP-MN-HA-MSA AVP. The pre- shared secret is carried inside the MIP-MN-HA-MSA AVP. The pre-
shared secret SHOULD NOT be user's long term secret and it is shared secret SHOULD NOT be user's long term secret and it is
RECOMMENDED that a short-term keying material specifically created RECOMMENDED that a short-term keying material specifically created
for this purpose is used instead. for this purpose is used instead.
5.3. Command Codes for Mobile IPv6 Authentication Protocol Support 5.3. Command Codes for Mobile IPv6 Authentication Protocol Support
This section defines the commands that are used for support with the This section defines the commands that are used for support with the
Mobile IPv6 Authentication Protocol. Mobile IPv6 Authentication Protocol.
Command-Name Abbrev. Code Reference Application Command-Name Abbrev. Code Reference Application
--------------------------------------------------------------------- ---------------------------------------------------------------------
MIP6-Request-Message MRM TBD 5.3.1 Diameter Mobile IPv6 Auth MIP6-Request MIR TBD 5.3.1 Diameter Mobile IPv6 Auth
MIP6-Answer-Message MAM TBD 5.3.2 Diameter Mobile IPv6 Auth MIP6-Answer MIA TBD 5.3.2 Diameter Mobile IPv6 Auth
Command Codes Command Codes
5.3.1. MIP6-Request-Message 5.3.1. MIP6-Request
The MIP6-Request-Message (MRM), indicated by the Command-Code field The MIP6-Request (MIR), indicated by the Command-Code field set to
set to TBD and the 'R' bit set in the Command Flags field, is sent by TBD and the 'R' bit set in the Command Flags field, is sent by the
the HA, acting as a Diameter client, in order to request the HA, acting as a Diameter client, in order to request the
authentication and authorization of a MN. authentication and authorization of a MN.
Although the HA provides the Diameter server with a replay protection Although the HA provides the Diameter server with a replay protection
related information, the HA is responsible for the replay protection. related information, the HA is responsible for the replay protection.
The message format is shown below. The message format is shown below.
<MIP6-Request-Message> ::= < Diameter Header: XXX, REQ, PXY > <MIP6-Request> ::= < Diameter Header: XXX, REQ, PXY >
< Session-ID > < Session-ID >
{ Auth-Application-Id } { Auth-Application-Id }
{ User-Name } { User-Name }
{ Destination-Realm } { Destination-Realm }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
[ Acct-Multi-Session-Id ]
[ Destination-Host ] [ Destination-Host ]
[ Origin-State-Id ] [ Origin-State-Id ]
[ NAS-Identifier ] [ NAS-Identifier ]
[ NAS-IP-Address ] [ NAS-IP-Address ]
[ NAS-IPv6-Address ] [ NAS-IPv6-Address ]
[ NAS-Port-Type ] [ NAS-Port-Type ]
[ Called-Station-Id ] [ Called-Station-Id ]
[ Calling-Station-Id ]
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
[ MIP-MN-AAA-SPI ] [ MIP-MN-AAA-SPI ]
[ MIP-MN-HA-SPI ] [ MIP-MN-HA-SPI ]
{ MIP-Mobile-Node-Address } { MIP-Mobile-Node-Address }
{ MIP-Home-Agent-Address } { MIP6-Agent-Info }
[ MIP-Careof-Address ] [ MIP-Careof-Address ]
[ MIP-Authenticator ] [ MIP-Authenticator ]
[ MIP-MAC-Mobility-Data ] [ MIP-MAC-Mobility-Data ]
[ MIP-Timestamp ] [ MIP-Timestamp ]
[ QoS-Capability ] [ QoS-Capability ]
* [ QoS-Resources ] * [ QoS-Resources ]
[ Chargeable-User-Identity ] [ Chargeable-User-Identity ]
[ Service-Selection ]
[ Authorization-Lifetime ] [ Authorization-Lifetime ]
[ Auth-Session-State ] [ Auth-Session-State ]
* [ Proxy-Info ] * [ Proxy-Info ]
* [ Route-Record ] * [ Route-Record ]
* [ AVP ] * [ AVP ]
5.3.2. MIP6-Answer-Message 5.3.2. MIP6-Answer
The MIP6-Answer-Message (MAM) message, indicated by the Command-Code The MIP6-Answer (MIA) message, indicated by the Command-Code field
field set to TBD and the 'R' bit cleared in the Command Flags field, set to TBD and the 'R' bit cleared in the Command Flags field, is
is sent by the Diameter server in response to the MIP6-Request- sent by the Diameter server in response to the MIP6-Request message.
Message message. The User-Name MAY be included in the MAM if it is The User-Name MAY be included in the MIA if it is present in the MIR.
present in the MRM. The Result-Code AVP MAY contain one of the The Result-Code AVP MAY contain one of the values defined in
values defined in Section 7, in addition to the values defined in RFC Section 7, in addition to the values defined in RFC 3588 [5].
3588 [5].
An MAM message with the Result-Code AVP set to DIAMETER_SUCCESS MUST An MIA message with the Result-Code AVP set to DIAMETER_SUCCESS MUST
include the MIP-Mobile-Node-Address AVP. include the MIP-Mobile-Node-Address AVP.
The message format is shown below. The message format is shown below.
<MIP6-Answer-Message> ::= < Diameter Header: XXX, PXY > <MIP6-Answer> ::= < Diameter Header: XXX, PXY >
< Session-Id > < Session-Id >
{ Auth-Application-Id } { Auth-Application-Id }
{ Result-Code } { Result-Code }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
[ Acct-Multi-Session-Id ] [ Acct-Multi-Session-Id ]
[ User-Name ] [ User-Name ]
[ Authorization-Lifetime ] [ Authorization-Lifetime ]
[ Auth-Session-State ] [ Auth-Session-State ]
[ Error-Message ] [ Error-Message ]
skipping to change at page 20, line 23 skipping to change at page 20, line 20
{ Result-Code } { Result-Code }
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
[ Acct-Multi-Session-Id ] [ Acct-Multi-Session-Id ]
[ User-Name ] [ User-Name ]
[ Authorization-Lifetime ] [ Authorization-Lifetime ]
[ Auth-Session-State ] [ Auth-Session-State ]
[ Error-Message ] [ Error-Message ]
[ Error-Reporting-Host ] [ Error-Reporting-Host ]
[ Re-Auth-Request-Type ] [ Re-Auth-Request-Type ]
[ MIP6-Feature-Vector ] [ MIP6-Feature-Vector ]
[ MIP-Home-Agent-Address ] [ MIP-Agent-Info ]
[ MIP-Mobile-Node-Address ] [ MIP-Mobile-Node-Address ]
[ MIP-MN-HA-MSA ] [ MIP-MN-HA-MSA ]
* [ QoS-Resources ] * [ QoS-Resources ]
[ Chargeable-User-Identity ] [ Chargeable-User-Identity ]
[ Origin-State-Id ] [ Origin-State-Id ]
* [ Proxy-Info ] * [ Proxy-Info ]
* [ Redirect-Host ]
[ Redirect-Host-Usage ]
[ Redirect-Max-Cache-Time ]
* [ Failed-AVP ]
* [ AVP ] * [ AVP ]
6. AVPs 6. AVPs
To provide support for RFC 4285 [3] and for RFC 4877 [4] the AVPs in To provide support for RFC 4285 [3] and for RFC 4877 [4] the AVPs in
the following subsections are needed. RFC 3588, RFC 4004 and RFC the following subsections are needed. RFC 3588, RFC 4004 and RFC
4005 defined AVPs are reused whenever possible without changing the 4005 defined AVPs are reused whenever possible without changing the
existing semantics of those AVPs. existing semantics of those AVPs.
+--------------------------+ +--------------------------+
skipping to change at page 21, line 17 skipping to change at page 21, line 17
+----+-----+----+-----+----+ +----+-----+----+-----+----+
AVP Defined | | |SHLD| MUST|MAY | AVP Defined | | |SHLD| MUST|MAY |
Attribute Name Code in Value Type |MUST| MAY | NOT| NOT|Encr| Attribute Name Code in Value Type |MUST| MAY | NOT| NOT|Encr|
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP6-Feature- TBD Note 1 Unsigned64 | M | P | | V | Y | |MIP6-Feature- TBD Note 1 Unsigned64 | M | P | | V | Y |
| Vector | | | | | | | Vector | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-Mobile- | M | P | | V | Y | |MIP-Mobile- | M | P | | V | Y |
| Node-Address 334 RFC4004 Address | | | | | | | Node-Address 334 RFC4004 Address | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-Home- 334 RFC4004 Address | M | P | | V | Y | |MIP6-Agent-Info TBD Note 3 Grouped | M | P | | V | Y |
| Agent-Address | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|User-Name 1 RFC3588 UTF8String | M | P | | V | Y | |User-Name 1 RFC3588 UTF8String | M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|Called- 30 RFC4005 UTF8String | M | P | | V | Y | |Service- TBD 6.2 UTF8String | M | P | | V | Y |
| Station-Id | | | | | | | Selection | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|QoS-Capability TBD Note 2 Grouped | M | P | | V | Y | |QoS-Capability TBD Note 2 Grouped | M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|QoS-Resources TBD Note 2 Grouped | M | P | | V | Y | |QoS-Resources TBD Note 2 Grouped | M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-MN-HA-MSA TBD 6.12. Grouped | M | P | | V | Y | |MIP-MN-HA-MSA TBD 6.12. Grouped | M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|Chargeable-User- OctetString| | M,P | | V | Y | |Chargeable-User- OctetString| | M,P | | V | Y |
| Identity 89 6.19 | | | | | | | Identity 89 6.19 | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
AVPs for Mobile IPv6 IKE Application AVPs for Mobile IPv6 IKE Application
Note 1: The MIP6-Feature-Vector is defined in Section 4.7.4 of [10]. Note 1: The MIP6-Feature-Vector is defined in Section 4.7.4 of [10].
Note 2: The QoS-Capability and QoS-Resource AVPs are defined in Note 2: The QoS-Capability and QoS-Resource AVPs are defined in
Sections 4.1 and 4.3 of [11]. Sections 4.1 and 4.3 of [11].
Note 3: The MIP6-Agent-Info is defined in Section 4.5.1 of [10].
+--------------------------+ +--------------------------+
| AVP Flag rules | | AVP Flag rules |
+----+-----+----+-----+----+ +----+-----+----+-----+----+
AVP Section | | |SHLD| MUST|MAY | AVP Section | | |SHLD| MUST|MAY |
Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr| Attribute Name Code Defined Value Type |MUST| MAY | NOT| NOT|Encr|
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP6-Feature- TBD Note 1 Unsigned64 | M | P | | V | Y | |MIP6-Feature- TBD Note 1 Unsigned64 | M | P | | V | Y |
| Vector | | | | | | | Vector | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|User-Name 1 RFC3588 UTF8String | M | P | | V | Y | |User-Name 1 RFC3588 UTF8String | M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|Service- TBD 6.2 UTF8String | M | P | | V | Y |
| Selection | | | | | |
+-----------------------------------------+----+-----+----+-----+----+
|MIP-MN-AAA-SPI 341 RFC4004 Unsigned32 | | M,P | | V | Y | |MIP-MN-AAA-SPI 341 RFC4004 Unsigned32 | | M,P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-MN-HA-SPI TBD 6.4 Unsigned32 | M | P | | V | Y | |MIP-MN-HA-SPI TBD 6.4 Unsigned32 | M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-Mobile- 333 RFC4004 Address | M | P | | V | Y | |MIP-Mobile- 333 RFC4004 Address | M | P | | V | Y |
| Node-Address | | | | | | | Node-Address | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-Home- 334 RFC4004 Address | M | P | | V | Y | |MIP6-Agent-Info TBD Note 3 Grouped | M | P | | V | Y |
| Agent-Address | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-Careof- TBD 6.7 Address | | M,P | | V | Y | |MIP-Careof- TBD 6.7 Address | M | P | | V | Y |
| Address | | | | | | | Address | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP- TBD 6.8 OctetString| | M,P | | V | Y | |MIP- TBD 6.8 OctetString| | M,P | | V | Y |
| Authenticator | | | | | | | Authenticator | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-MAC- TBD 6.9 OctetString| | M,P | | V | Y | |MIP-MAC- TBD 6.9 OctetString| | M,P | | V | Y |
| Mobility-Data | | | | | | | Mobility-Data | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-Session-Key 343 6.10 OctetString| M | P | | V | Y | |MIP-Session-Key 343 6.10 OctetString| M | P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
skipping to change at page 22, line 45 skipping to change at page 22, line 48
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|MIP-Timestamp TBD 6.16 Time | | M,P | | V | Y | |MIP-Timestamp TBD 6.16 Time | | M,P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|QoS-Capability TBD Note 2 Grouped | | M,P | | M | Y | |QoS-Capability TBD Note 2 Grouped | | M,P | | M | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|QoS-Resources TBD Note 2 Grouped | | M,P | | V | Y | |QoS-Resources TBD Note 2 Grouped | | M,P | | V | Y |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|Chargeable-User- OctetString| | M,P | | V | Y | |Chargeable-User- OctetString| | M,P | | V | Y |
| Identity 89 6.19 | | | | | | | Identity 89 6.19 | | | | | |
+-----------------------------------------+----+-----+----+-----+----+ +-----------------------------------------+----+-----+----+-----+----+
|Rest of the AVPs RFC3588 | M | P | | V | Y |
|in the MIR & MIA RFC4005 | | | | | |
|excluding *[AVP] | | | | | |
+-----------------------------------------+----+-----+----+-----+----+
AVPs for the Mobile IPv6 Auth Application AVPs for the Mobile IPv6 Auth Application
Note 1: The MIP6-Feature-Vector is defined in Section 4.7.4 of [10]. Note 1: The MIP6-Feature-Vector is defined in Section 4.7.4 of [10].
Note 2: The QoS-Capability and QoS-Resource AVPs are defined in Note 2: The QoS-Capability and QoS-Resource AVPs are defined in
Sections 4.1 and 4.3 of [11]. Sections 4.1 and 4.3 of [11].
Note 3: The MIP6-Agent-Info is defined in Section 4.5.1 of [10].
6.1. User-Name AVP 6.1. User-Name AVP
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. Called-Station-Id AVP 6.2. Service-Selection AVP
The Called-Station-Id AVP (AVP Code 30) 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 string extracted from the IKEv2 IDr payload, if
available in the IKE_AUTH message sent by the IKE initiator. If the available in the IKE_AUTH message sent by the IKE initiator. If the
Mobile IPv6 Authentication Protocol is used, then the Mobile IPv6 Authentication Protocol is used, then the Service-
Called-Station-Id AVP contains the string extracted from the Service Selection AVP contains the string extracted from the Service
Selection Mobility Option [20], if available in the received BU. Selection Mobility Option [20], if available in the received BU.
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. Authentication Option included in the received BU message. The HA
includes this AVP in the MIR message when the MN-AAA Mobility Message
Authentication Option is available in the received BU. The HA sets
the 'M'-bit for this AVP when the Diameter server is expected to
return the key material required for the calculation and validation
of the Mobile IPv6 MN-HA Authentication Option.
This AVP is re-used from [12]. This AVP is re-used from [12].
6.4. MIP-MN-HA-SPI AVP 6.4. MIP-MN-HA-SPI AVP
The MIP-MN-HA-SPI AVP (AVP Code TBD) is of type Unsigned32 and The MIP-MN-HA-SPI AVP (AVP Code TBD) is of type Unsigned32 and
contains an SPI code which can be used with other parameters for contains an SPI code which can be used with other parameters for
identifying the security association required for the validation of identifying the security association required for the validation of
the Mobile IPv6 MN-HA Authentication Option. the Mobile IPv6 MN-HA Authentication Option.
When included in the MRM message, the Diameter server needs to return When included in the MIR message, the Diameter server needs to return
a valid MIP-MN-HA-MSA AVP in the corresponding MAM message. a valid MIP-MN-HA-MSA AVP in the corresponding MIA message. Either
the MIP-MN-HA-SPI AVP or the MIP-MN-AAA-SPI AVP MUST be present in
the MIR message, but not both.
6.5. MIP-Mobile-Node-Address AVP 6.5. MIP-Mobile-Node-Address AVP
The MIP-Mobile-Node-Address AVP (AVP Code 333) is of type Address and The MIP-Mobile-Node-Address AVP (AVP Code 333) is of type Address and
contains the HA assigned IPv6 or IPv4 Home Address of the Mobile contains the HA assigned IPv6 or IPv4 Home Address of the Mobile
Node. Node.
If the MIP-Mobile-Node-Address AVP contains unspecified IPv6 address If the MIP-Mobile-Node-Address AVP contains unspecified IPv6 address
(0::0) or all zeroes IPv4 address (0.0.0.0) in a request message, (0::0) or all zeroes IPv4 address (0.0.0.0) in a request message,
then the HA expects the Diameter server to assign the Home Address in then the HA expects the Diameter server to assign the Home Address in
a subsequent answer message. If the Diameter server assigns only an a subsequent answer message. If the Diameter server assigns only an
IPv6 Home Network Prefix to the Mobile Node the lower 64 bits of the IPv6 Home Network Prefix to the Mobile Node the lower 64 bits of the
MIP-Mobile-Node-Address AVP provided address MUST be set to zero. MIP-Mobile-Node-Address AVP provided address MUST be set to zero.
This AVP is re-used from [12]. This AVP is re-used from [12].
6.6. MIP-Home-Agent-Address AVP 6.6. MIP6-Agent-Info AVP
The MIP-Home-Agent-Address AVP (AVP Code 334) is of type Address and The MIP6-Agent-Info AVP is defined in Section 4.5.1 of [10] and
contains the IPv6 or the IPv4 address of the HA. The HA address in a contains the IPv6 or the IPv4 address information of the HA. The HA
request message is the same as in the received BU message that address in a request message is the same as in the received BU
triggered the authentication and authorization procedure towards the message that triggered the authentication and authorization procedure
Diameter server. towards the Diameter server.
If the MIP-Home-Agent-Address AVP is present in an answer message and If the MIP6-Agent-Info AVP is present in an answer message and the
the Result-Code AVP is set to DIAMETER_SUCCESS_RELOCATE_HA, then the Result-Code AVP is set to DIAMETER_SUCCESS_RELOCATE_HA, then the
Diameter server is indicating to the HA that it MUST initiate a HA Diameter server is indicating to the HA that it MUST initiate a HA
switch procedure towards the MN (e.g., using the procedure defined in switch procedure towards the MN (e.g., using the procedure defined in
[13]). If the Result-Code AVP is set to any other value, then the HA [13]). If the Result-Code AVP is set to any other value, then the HA
SHOULD initiate the HA switch procedure towards the MN. The address SHOULD initiate the HA switch procedure towards the MN. The address
of the assigned HA is defined in the MIP-Home-Agent-Address AVP. information of the assigned HA is defined in the MIP6-Agent-Info AVP.
This AVP is re-used from [12].
6.7. MIP-Careof-Address AVP 6.7. MIP-Careof-Address AVP
The MIP-Careof-Address AVP (AVP Code TBD) is of type Address and The MIP-Careof-Address AVP (AVP Code TBD) is of type Address and
contains the IPv6 Care-of Address of the Mobile Node. The HA contains the IPv6 Care-of Address of the Mobile Node. The HA
extracts this IP address from the received BU message. extracts this IP address from the received BU message.
6.8. MIP-Authenticator AVP 6.8. MIP-Authenticator AVP
The MIP-Authenticator AVP (AVP Code TBD) is of type OctetString and The MIP-Authenticator AVP (AVP Code TBD) is of type OctetString and
contains the Authenticator Data from the received BU message. The HA contains the Authenticator Data from the received BU message. The HA
extracts this data from the MN-AAA Mobility Message Authentication extracts this data from the MN-AAA Mobility Message Authentication
Option included in the received BU message. Option included in the received BU message. The HA includes this AVP
in the MIR message and sets the 'M'-bit when the Diameter server is
expected to return the key material required for the calculation and
validation of the Mobile IPv6 MN-HA Authentication Option.
6.9. MIP-MAC-Mobility-Data AVP 6.9. MIP-MAC-Mobility-Data AVP
The MIP-MAC-Mobility-Data AVP (AVP Code TBD) is of type OctetString The MIP-MAC-Mobility-Data AVP (AVP Code TBD) is of type OctetString
and contains the calculated MAC_Mobility_Data, as defined in [3]. and contains the calculated MAC_Mobility_Data, as defined in [3].
The HA includes this AVP in the MIR message when the MN-AAA Mobility
Message Authentication Option is available in the received BU. The
HA sets the 'M'-bit for this AVP when the Diameter server is expected
to return the key material required for the calculation and
validation of the Mobile IPv6 MN-HA Authentication Option.
6.10. MIP-Session-Key AVP 6.10. MIP-Session-Key AVP
The MIP-Session-Key AVP (AVP Code 343) is of type OctetString and The MIP-Session-Key AVP (AVP Code 343) is of type OctetString and
contains the MN-HA shared secret (i.e., the session key) for the contains the MN-HA shared secret (i.e., the session key) for the
associated Mobile IPv6 MH-HA authentication option. When the associated Mobile IPv6 MH-HA authentication option. When the
Diameter server computes the session key it is placed in this AVP. Diameter server computes the session key it is placed in this AVP.
The MIP-Session-Key AVP may also be used to convey a pre-shared The MIP-Session-Key AVP may also be used to convey a pre-shared
secret when IKEv2 is used with PSK-based initiator authentication. secret when IKEv2 is used with PSK-based initiator authentication.
skipping to change at page 25, line 29 skipping to change at page 26, line 4
the session related information for use with the Mobile IPv6 the session related information for use with the Mobile IPv6
Authentication Protocol. Authentication Protocol.
MIP-MN-HA-MSA ::= < AVP Header: TBD > MIP-MN-HA-MSA ::= < AVP Header: TBD >
{ MIP-Session-Key } { MIP-Session-Key }
{ MIP-MSA-Lifetime } { MIP-MSA-Lifetime }
[ MIP-MN-HA-SPI ] [ MIP-MN-HA-SPI ]
[ MIP-Algorithm-Type ] [ MIP-Algorithm-Type ]
[ MIP-Replay-Mode ] [ MIP-Replay-Mode ]
* [ AVP ] * [ AVP ]
The MIP-MN-HA-SPI sub-AVP within the MIP-MN-HA-MSA grouped AVP
identifies the security association required for the validation of
the Mobile IPv6 MN-HA Authentication Option.
6.13. MIP-Algorithm-Type AVP 6.13. MIP-Algorithm-Type AVP
The MIP-Algorithm-Type AVP (AVP Code 345) is of type Enumerated and The MIP-Algorithm-Type AVP (AVP Code 345) is of type Enumerated and
contains Algorithm identifier for the associated Mobile IPv6 MN-HA contains Algorithm identifier for the associated Mobile IPv6 MN-HA
Authentication Option. The Diameter server selects the algorithm Authentication Option. The Diameter server selects the algorithm
type. Existing algorithm types are defined in RFC 4004 that also type. Existing algorithm types are defined in RFC 4004 that also
fulfill current RFC 4285 requirements. fulfill current RFC 4285 requirements.
This AVP is re-used from [12]. This AVP is re-used from [12].
skipping to change at page 27, line 6 skipping to change at page 27, line 32
VPN_GW_MODE (0x0000000800000000) VPN_GW_MODE (0x0000000800000000)
The HA is supposed to act as a IPSec VPN gateway for the user. The HA is supposed to act as a IPSec VPN gateway for the user.
When the HA sets this bit, it indicates support for acting as a When the HA sets this bit, it indicates support for acting as a
standalone IPSec VPN gateway. If this bit is unset in the standalone IPSec VPN gateway. If this bit is unset in the
returned Mobility-Capability AVP, the AAAH does not authorize the returned Mobility-Capability AVP, the AAAH does not authorize the
HA to act as a standalone IPSec VPN gateway for the MN because of HA to act as a standalone IPSec VPN gateway for the MN because of
subscription or operator policy. subscription or operator policy.
MCOA_SUPPORTED (0x0000001000000000)
Multiple Care-of Addresses (MCoA) [21] are supported. When the HA
sets this bit, it indicates support for the MCoA. If this bit is
unset in the returned Mobility-Capability AVP, the AAAH does not
authorize the use of MCoA for the MN.
In a case the HA or the AAAH cannot authorize the use of the MCoA
then the HA SHOULD send a Binding Acknowledgement with a Status
Code set to ACCEPTED_BUT_NO_MCOA (status code TBD). This Status
Code indicates that the binding registration succeeded but the HA
will fail all possible subsequent attempts to use MCoA because of
subscription or operator policy.
6.16. MIP-Timestamp AVP 6.16. MIP-Timestamp AVP
The MIP-Timestamp AVP (AVP Code TBD) is of type Time and may contain The MIP-Timestamp AVP (AVP Code TBD) is of type Time and may contain
the timestamp value from the Mobility message replay protection the timestamp value from the Mobility message replay protection
option, defined in [3]. The HA extracts this value from the received option, defined in [3]. The HA extracts this value from the received
BU message, if available. BU message, if available. The HA includes this AVP in the MIR
message when the MN-AAA Mobility Message Authentication Option is
available in the received BU. The HA sets the 'M'-bit for this AVP
when the Diameter server is expected to return the key material
required for the calculation and validation of the Mobile IPv6 MN-HA
Authentication Option.
6.17. QoS-Capability AVP 6.17. QoS-Capability AVP
The QoS-Capability AVP is defined in [11] and contains a list of The QoS-Capability AVP is defined in [11] and contains a list of
supported Quality of Service profiles. supported Quality of Service profiles. The HA sets the 'M'-bit for
this AVP in the request message if it requires the Diameter server to
understand and support QoS treatment for MNs. In all other occasions
the HA MUST NOT set the 'M'-bit.
6.18. QoS-Resources AVP 6.18. QoS-Resources AVP
The QoS-Resources AVP is defined in [11] and provides QoS and packet The QoS-Resources AVP is defined in [11] and provides QoS and packet
filtering capabilities. filtering capabilities. The HA sets the 'M'-bit for this AVP in the
request message if it requires the Diameter server to understand and
support QoS treatment for MNs. The Diameter server sets the 'M'-bit
for this AVP only if the corresponding request message had the
'M'-bit set for the QoS-Resources AVP. In all other occasions the HA
or the Diameter MUST NOT set the 'M'-bit.
6.19. Chargeable-User-Identity AVP 6.19. Chargeable-User-Identity AVP
The Chargeable-User-Identity AVP (AVP code 89) is of type OctetString The Chargeable-User-Identity AVP (AVP code 89) is of type OctetString
and contains an unique temporary handle of the user. The Chargeable- and contains an unique temporary handle of the user. The Chargeable-
User-Identity is defined in RFC 4372 [14]. User-Identity is defined in RFC 4372 [14].
The HA sets the 'M'-bit for the Chargeable-User-Id AVP if the
Diameter server is required to understand this AVP and the HA expects
the Diameter server to return a meaningful identity back to the HA.
The Diameter server sets the 'M'-bit for the returned Chargeable-
User-Id AVP only if the corresponding request message had the 'M'-bit
set for the Chargeable-User-Id AVP. In all other occasions the HA or
the Diameter MUST NOT set the 'M'-bit.
6.20. Coupled Accounting Model Accounting AVPs 6.20. Coupled Accounting Model Accounting AVPs
Diameter Mobile IPv6 application is used in the case of the coupled Diameter Mobile IPv6 application is used in the case of the coupled
account model. Diameter Mobile IPv4 application [12] accounting AVPs account model. Diameter Mobile IPv4 application [12] accounting AVPs
are reused in this document. The following AVPs MUST be included in are reused in this document. The following AVPs SHOULD be included
the accounting request message: in the accounting request message:
o Accounting-Input-Octets: Number of octets in IP packets received o Accounting-Input-Octets: Number of octets in IP packets received
from the mobile node. from the mobile node.
o Accounting-Output-Octets: Number of octets in IP packets sent by o Accounting-Output-Octets: Number of octets in IP packets sent by
the mobile node the mobile node
o Accounting-Input-Packets: Number of IP packets received from the o Accounting-Input-Packets: Number of IP packets received from the
mobile node. mobile node.
o Accounting-Output-Packets: Number of IP packets sent by the mobile o Accounting-Output-Packets: Number of IP packets sent by the mobile
node. node.
o Acct-Multi-Session-Id: Used to link together multiple related o Acct-Multi-Session-Id: Used to link together multiple related
skipping to change at page 28, line 4 skipping to change at page 29, line 18
the mobile node the mobile node
o Accounting-Input-Packets: Number of IP packets received from the o Accounting-Input-Packets: Number of IP packets received from the
mobile node. mobile node.
o Accounting-Output-Packets: Number of IP packets sent by the mobile o Accounting-Output-Packets: Number of IP packets sent by the mobile
node. node.
o Acct-Multi-Session-Id: Used to link together multiple related o Acct-Multi-Session-Id: Used to link together multiple related
accounting sessions, where each session would have a unique accounting sessions, where each session would have a unique
Session-Id, but the same Acct-Multi-Session-Id AVP. Session-Id, but the same Acct-Multi-Session-Id AVP.
o Acct-Session-Time: Indicates the length of the current session in o Acct-Session-Time: Indicates the length of the current session in
seconds. seconds.
o MIP6-Feature-Vector: The supported features for this mobility o MIP6-Feature-Vector: The supported features for this mobility
service session. service session.
o MIP-Mobile-Node-Address: The Home Address of the mobile node. o MIP-Mobile-Node-Address: The Home Address of the mobile node.
o MIP-Home-Agent-Address: The current home agent of the mobile node. o MIP-Agent-Info: The current home agent of the mobile node.
o Chargeable-User-Identity: The unique temporary identity of the o Chargeable-User-Identity: The unique temporary identity of the
user. This AVP MUST be included if it is available in the home user. This AVP MUST be included if it is available in the home
agent. agent.
o Service-Selection: Currently selected mobility service.
Other APVs that SHOULD be included in the accounting request message
include:
o QoS-Resources: Assigned QoS resources for the mobile node. o QoS-Resources: Assigned QoS resources for the mobile node.
o QoS-Capability: The QoS capability related to the assigned QoS- o QoS-Capability: The QoS capability related to the assigned QoS-
Resources. Resources.
o MIP-Careof-Address: The current Care-of Address of the mobile o MIP-Careof-Address: The current Care-of Address of the mobile
node. node.
7. Result-Code AVP Values 7. Result-Code AVP Values
This section defines new Result-Code [5] values that MUST be This section defines new Result-Code [5] values that MUST be
supported by all Diameter implementations that conform to this supported by all Diameter implementations that conform to this
skipping to change at page 29, line 29 skipping to change at page 30, line 36
Zero or more instances of the AVP MAY be present in the message. Zero or more instances of the AVP MAY be present in the message.
0-1: 0-1:
Zero or one instance of the AVP MAY be present in the message. Zero or one instance of the AVP MAY be present in the message.
1: 1:
One instance of the AVP MUST be present in the message. One instance of the AVP MUST be present in the message.
8.1. AAR, AAA, DER, DEA, MRM and MAM AVP/Command-Code Table 8.1. AAR, AAA, DER, DEA, MIR and MIA AVP/Command-Code Table
+-----------------------------------+ +-----------------------------------+
| Command-Code | | Command-Code |
|-----+-----+-----+-----+-----+-----+ |-----+-----+-----+-----+-----+-----+
AVP Name | AAR | AAA | DER | DEA | MRM | MAM | AVP Name | AAR | AAA | DER | DEA | MIR | MIA |
-------------------------------|-----+-----|-----+-----+-----+-----+ -------------------------------|-----+-----|-----+-----+-----+-----+
MIP6-Feature-Vector | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 | MIP6-Feature-Vector | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |
MIP-Mobile-Node-Address | 1-2 | 0-2 | 1-2 | 0-2 | 1 | 0-1 | MIP-Mobile-Node-Address | 1-2 | 0-2 | 1-2 | 0-2 | 1 | 0-1 |
MIP-MN-AAA-SPI | 0 | 0 | 0 | 0 | 0-1 | 0 | MIP-MN-AAA-SPI | 0 | 0 | 0 | 0 | 0-1 | 0 |
MIP-MN-HA-SPI | 0 | 0 | 0 | 0 | 0-1 | 0 | MIP-MN-HA-SPI | 0 | 0 | 0 | 0 | 0-1 | 0 |
MIP-Home-Agent-Address | 1-2 | 0-2 | 1-2 | 0-2 | 1 | 0-1 | MIP6-Agent-Info | 1-2 | 0-2 | 1-2 | 0-2 | 1 | 0-1 |
MIP-Careof-Address | 0 | 0 | 0 | 0 | 0-1 | 0 | MIP-Careof-Address | 0 | 0 | 0 | 0 | 0-1 | 0 |
MIP-Authenticator | 0 | 0 | 0 | 0 | 0-1 | 0 | MIP-Authenticator | 0 | 0 | 0 | 0 | 0-1 | 0 |
MIP-MAC-Mobility-Data | 0 | 0 | 0 | 0 | 0-1 | 0 | MIP-MAC-Mobility-Data | 0 | 0 | 0 | 0 | 0-1 | 0 |
MIP-MSA-Lifetime | 0 | 0 | 0 | 0 | 0 | 1 | MIP-MSA-Lifetime | 0 | 0 | 0 | 0 | 0 | 1 |
MIP-MN-HA-MSA | 0 | 0-1 | 0 | 0 | 0 | 0-1 | MIP-MN-HA-MSA | 0 | 0-1 | 0 | 0 | 0 | 0-1 |
MIP-Timestamp | 0 | 0 | 0 | 0 | 0-1 | 0-1 | MIP-Timestamp | 0 | 0 | 0 | 0 | 0-1 | 0-1 |
User-Name | 0-1 | 0-1 | 0-1 | 0-1 | 1 | 0-1 | User-Name | 0-1 | 0-1 | 0-1 | 0-1 | 1 | 0-1 |
Called-Station-Id | 0-1 | 0 | 0-1 | 0 | 0-1 | 0 | Service-Selection | 0-1 | 0 | 0-1 | 0 | 0-1 | 0 |
QoS-Resources | *0 | *0 | *0 | *0 | *0 | *0 | QoS-Resources | *0 | *0 | *0 | *0 | *0 | *0 |
QoS-Capability | 0-1 | 0 | 0-1 | 0 | 0-1 | 0 | QoS-Capability | 0-1 | 0 | 0-1 | 0 | 0-1 | 0 |
Chargeable-User-Identity | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 | Chargeable-User-Identity | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |
+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+
8.2. Coupled Accounting Model AVP Table 8.2. Coupled Accounting Model AVP Table
The table in this section is used to represent which AVPs defined in The table in this section is used to represent which AVPs defined in
this document are to be present in the Accounting messages, as this document are to be present in the Accounting messages, as
defined in [5]. defined in [5].
+-------------+ +-------------+
| Command-Code| | Command-Code|
|------+------+ |------+------+
Attribute Name | ACR | ACA | Attribute Name | ACR | ACA |
-------------------------------------|------+------+ -------------------------------------|------+------+
Accounting-Input-Octets | 1 | 0-1 | Accounting-Input-Octets | 0-1 | 0-1 |
Accounting-Input-Packets | 1 | 0-1 | Accounting-Input-Packets | 0-1 | 0-1 |
Accounting-Output-Octets | 1 | 0-1 | Accounting-Output-Octets | 0-1 | 0-1 |
Accounting-Output-Packets | 1 | 0-1 | Accounting-Output-Packets | 0-1 | 0-1 |
Acct-Multi-Session-Id | 1 | 0-1 | Acct-Multi-Session-Id | 0-1 | 0-1 |
Acct-Session-Time | 1 | 0-1 | Acct-Session-Time | 0-1 | 0-1 |
MIP6-Feature-Vector | 1 | 0-1 | MIP6-Feature-Vector | 0-1 | 0-1 |
MIP-Home-Agent-Address | 1 | 0-1 | MIP6-Agent-Info | 0-1 | 0-1 |
MIP-Mobile-Node-Address | 1 | 0-1 | MIP-Mobile-Node-Address | 0-1 | 0-1 |
Event-Timestamp | 0-1 | 0 | Event-Timestamp | 0-1 | 0 |
MIP-Careof-Address | 0-1 | 0 | MIP-Careof-Address | 0-1 | 0 |
Service-Selection | 0-1 | 0 |
QoS-Capability | *0 | *0 | QoS-Capability | *0 | *0 |
QoS-Resources | *0 | *0 | QoS-Resources | *0 | *0 |
Chargeable-User-Identity | 0-1 | 0 | Chargeable-User-Identity | 0-1 | 0 |
-------------------------------------|------+------+ -------------------------------------|------+------+
9. IANA Considerations 9. IANA Considerations
This section contains the namespaces that have either been created in This section contains the namespaces that have either been created in
this specification or had their values assigned to existing this specification or had their values assigned to existing
namespaces managed by IANA. namespaces managed by IANA.
9.1. Command Codes 9.1. Command Codes
IANA is requested to allocate a command code value for the MIP6- IANA is requested to allocate a command code values for the following
Request-Message (MRM) and for the MIP6-Answer-Message (MAM) from the new commands from the Command Code namespace defined in [5]. See
Command Code namespace defined in [5]. See Section 5 for the Section 5 for the assignment of the namespace in this specification.
assignment of the namespace in this specification.
Command Code | Value
-----------------------------------+------
MIP6-Request (MIR) | TBD
MIP6-Answer (MIA) | TBD
9.2. AVP Codes 9.2. AVP Codes
This specification requires IANA to register the following new AVPs This specification requires IANA to register the following new AVPs
from the AVP Code namespace defined in [5]. from the AVP Code namespace defined in [5].
o MIP-Careof-Address o MIP-Careof-Address
o MIP-Authenticator o MIP-Authenticator
o MIP-MAC-Mobility-Data o MIP-MAC-Mobility-Data
o MIP-Timestamp o MIP-Timestamp
o MIP-MN-HA-SPI o MIP-MN-HA-SPI
o MIP-MN-HA-MSA o MIP-MN-HA-MSA
o Service-Selection
The AVPs are defined in Section 6. The AVPs are defined in Section 6.
9.3. Result-Code AVP Values 9.3. Result-Code AVP Values
This specification requests IANA to allocate new values to the This specification requests IANA to allocate new values to the
Result-Code AVP (AVP Code 268) namespace defined in [5]. See Result-Code AVP (AVP Code 268) namespace defined in [5]. See
Section 7 for the assignment of the namespace in this specification. Section 7 for the assignment of the namespace in this specification.
Result-Code | Value Result-Code | Value
skipping to change at page 32, line 5 skipping to change at page 33, line 48
This specification defines a new value to the Mobility Capability This specification defines a new value to the Mobility Capability
registry (see [10]) for use with the MIP6-Feature-Vector AVP: registry (see [10]) for use with the MIP6-Feature-Vector AVP:
Token | Value | Description Token | Value | Description
---------------------------------+----------------------+------------ ---------------------------------+----------------------+------------
MIP6_SPLIT | 0x0000000100000000 | RFC TBD MIP6_SPLIT | 0x0000000100000000 | RFC TBD
RO_SUPPORTED | 0x0000000200000000 | RFC TBD RO_SUPPORTED | 0x0000000200000000 | RFC TBD
USER_TRAFFIC_ENCRYPTION | 0x0000000400000000 | RFC TBD USER_TRAFFIC_ENCRYPTION | 0x0000000400000000 | RFC TBD
VPN_GW_MODE | 0x0000000800000000 | RFC TBD VPN_GW_MODE | 0x0000000800000000 | RFC TBD
MCOA_SUPPORTED | 0x0000001000000000 | RFC TBD
9.6. Mobile IPv6 Status Codes 9.6. Mobile IPv6 Status Codes
This specification defines a new Mobile IPv6 [1] Status Code value. This specification defines new Mobile IPv6 [1] Status Code values.
The Status Code must be allocated from the range 0-127: The Status Code must be allocated from the range 0-127:
Status Code | Value | Description Status Code | Value | Description
----------------------------------------+---------------+------------ ----------------------------------------+---------------+------------
ACCEPTED_BUT_NO_ROUTE_OPTIMIZATION | is set to TBD | RFC TBD ACCEPTED_BUT_NO_ROUTE_OPTIMIZATION | is set to TBD | RFC TBD
ACCEPTED_BUT_NO_TRAFFIC_ENCRYPTION | is set to TBD | RFC TBD ACCEPTED_BUT_NO_TRAFFIC_ENCRYPTION | is set to TBD | RFC TBD
ACCEPTED_BUT_NO_MCOA | is set to TBD | RFC TBD
10. Security Considerations 10. Security Considerations
The security considerations for the Diameter interaction required to The security considerations for the Diameter interaction required to
accomplish the split scenario are described in in [2]. Additionally, accomplish the split scenario are described in in [2]. Additionally,
the security considerations of the Diameter Base protocol [5], the security considerations of the Diameter Base protocol [5],
Diameter EAP application [7] are applicable to this document. This Diameter EAP application [7] are applicable to this document. This
document does not introduce new security vulnerabilities. document does not introduce new security vulnerabilities.
11. Acknowledgements 11. Acknowledgements
skipping to change at page 33, line 46 skipping to change at page 35, line 46
Network Access Server Application", RFC 4005, August 2005. Network Access Server Application", RFC 4005, August 2005.
[10] Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C., and [10] Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C., and
K. Chowdhury, "Diameter Mobile IPv6: Support for Network Access K. Chowdhury, "Diameter Mobile IPv6: Support for Network Access
Server to Diameter Server Interaction", Server to Diameter Server Interaction",
draft-ietf-dime-mip6-integrated-09 (work in progress), draft-ietf-dime-mip6-integrated-09 (work in progress),
May 2008. May 2008.
[11] Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones, M., and [11] Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones, M., and
A. Lior, "Quality of Service Attributes for Diameter", A. Lior, "Quality of Service Attributes for Diameter",
draft-ietf-dime-qos-attributes-06 (work in progress), May 2008. draft-ietf-dime-qos-attributes-07 (work in progress),
June 2008.
[12] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and P. [12] 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.
[13] Haley, B., Devarapalli, V., Deng, H., and J. Kempf, "Mobility [13] Haley, B., Devarapalli, V., Deng, H., and J. Kempf, "Mobility
Header Home Agent Switch Message", RFC 5142, January 2008. Header Home Agent Switch Message", RFC 5142, January 2008.
[14] Adrangi, F., Lior, A., Korhonen, J., and J. Loughney, [14] Adrangi, F., Lior, A., Korhonen, J., and J. Loughney,
"Chargeable User Identity", RFC 4372, January 2006. "Chargeable User Identity", RFC 4372, January 2006.
skipping to change at page 34, line 19 skipping to change at page 36, line 21
12.2. Informative References 12.2. Informative References
[15] Patel, A. and G. Giaretta, "Problem Statement for bootstrapping [15] Patel, A. and G. Giaretta, "Problem Statement for bootstrapping
Mobile IPv6 (MIPv6)", RFC 4640, September 2006. Mobile IPv6 (MIPv6)", RFC 4640, September 2006.
[16] Giaretta, G., Guardini, I., Demaria, E., Bournelle, J., and R. [16] 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-01 (work in progress), May 2008. draft-ietf-mext-aaa-ha-goals-01 (work in progress), May 2008.
[17] Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and [17] Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and
Routers", draft-ietf-mext-nemo-v4traversal-03 (work in Routers", draft-ietf-mext-nemo-v4traversal-04 (work in
progress), May 2008. progress), June 2008.
[18] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury, [18] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury,
"Mobile Node Identifier Option for Mobile IPv6 (MIPv6)", "Mobile Node Identifier Option for Mobile IPv6 (MIPv6)",
RFC 4283, November 2005. RFC 4283, November 2005.
[19] Fajardo, V., Asveren, T., Tschofenig, H., McGregor, G., and J. [19] Fajardo, V., Asveren, T., Tschofenig, H., McGregor, G., and J.
Loughney, "Diameter Applications Design Guidelines", Loughney, "Diameter Applications Design Guidelines",
draft-ietf-dime-app-design-guide-06 (work in progress), draft-ietf-dime-app-design-guide-06 (work in progress),
January 2008. January 2008.
[20] Korhonen, J., Nilsson, U., and V. Devarapalli, "Service [20] Korhonen, J., Nilsson, U., and V. Devarapalli, "Service
Selection for Mobile IPv6", RFC 5149, February 2008. Selection for Mobile IPv6", RFC 5149, February 2008.
[21] Wakikawa, R., Devarapalli, V., Ernst, T., and K. Nagami,
"Multiple Care-of Addresses Registration",
draft-ietf-monami6-multiplecoa-08 (work in progress), May 2008.
Authors' Addresses Authors' Addresses
Jouni Korhonen Jouni Korhonen
TeliaSonera TeliaSonera
P.O.Box 970 P.O.Box 970
Sonera FIN-00051 Sonera FIN-00051
Finland Finland
Email: jouni.korhonen@teliasonera.com Email: jouni.korhonen@teliasonera.com
Hannes Tschofenig Hannes Tschofenig
 End of changes. 91 change blocks. 
193 lines changed or deleted 256 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/