idnits 2.17.1 draft-ietf-dime-mip6-split-12.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 23. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 1550. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1561. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1568. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1574. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (September 23, 2008) is 5692 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 3775 (ref. '1') (Obsoleted by RFC 6275) ** Downref: Normative reference to an Informational draft: draft-ietf-mip6-rfc4285bis (ref. '3') ** Obsolete normative reference: RFC 3588 (ref. '5') (Obsoleted by RFC 6733) ** Obsolete normative reference: RFC 4306 (ref. '8') (Obsoleted by RFC 5996) ** Obsolete normative reference: RFC 4005 (ref. '9') (Obsoleted by RFC 7155) == Outdated reference: A later version (-12) exists of draft-ietf-dime-mip6-integrated-10 == Outdated reference: A later version (-15) exists of draft-ietf-dime-qos-attributes-07 == Outdated reference: A later version (-10) exists of draft-ietf-mext-nemo-v4traversal-05 == Outdated reference: A later version (-28) exists of draft-ietf-dime-app-design-guide-07 == Outdated reference: A later version (-14) exists of draft-ietf-monami6-multiplecoa-09 -- Obsolete informational reference (is this intentional?): RFC 5226 (ref. '22') (Obsoleted by RFC 8126) Summary: 6 errors (**), 0 flaws (~~), 6 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Diameter Maintenance and J. Korhonen 3 Extensions (DIME) TeliaSonera 4 Internet-Draft H. Tschofenig 5 Intended status: Standards Track Nokia Siemens Networks 6 Expires: March 27, 2009 J. Bournelle 7 Orange Labs 8 G. Giaretta 9 Qualcomm 10 M. Nakhjiri 11 Motorola 12 September 23, 2008 14 Diameter Mobile IPv6: Support for Home Agent to Diameter Server 15 Interaction 16 draft-ietf-dime-mip6-split-12.txt 18 Status of this Memo 20 By submitting this Internet-Draft, each author represents that any 21 applicable patent or other IPR claims of which he or she is aware 22 have been or will be disclosed, and any of which he or she becomes 23 aware will be disclosed, in accordance with Section 6 of BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF), its areas, and its working groups. Note that 27 other groups may also distribute working documents as Internet- 28 Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/ietf/1id-abstracts.txt. 38 The list of Internet-Draft Shadow Directories can be accessed at 39 http://www.ietf.org/shadow.html. 41 This Internet-Draft will expire on March 27, 2009. 43 Copyright Notice 45 Copyright (C) The IETF Trust (2008). 47 Abstract 49 Mobile IPv6 deployments may want to bootstrap their operations 50 dynamically based on an interaction between the Home Agent and the 51 Diameter server of the Mobile Service Provider (MSP). This document 52 specifies the interaction between a Mobile IP Home Agent and that 53 Diameter server. 55 Several different mechanisms for authenticating a Mobile Node are 56 supported. The usage of the Internet Key Exchange v2 (IKEv2) 57 protocol allows different mechanisms, such as the Extensible 58 Authentication Protocol (EAP), certificates and pre-shared secrets to 59 be used. Furthermore, another method makes use of the Mobile IPv6 60 Authentication Protocol. In addition to authentication and 61 authorization, the configuration of Mobile IPv6 specific parameters 62 and accounting is specified in this document. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 67 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7 68 3. Application Identifiers . . . . . . . . . . . . . . . . . . . 7 69 4. Protocol Description . . . . . . . . . . . . . . . . . . . . . 8 70 4.1. Support for Mobile IPv6 with IKEv2 and EAP . . . . . . . . 8 71 4.2. Support for the Mobile IPv6 Authentication Protocol . . . 11 72 4.3. Mobile IPv6 Session Management . . . . . . . . . . . . . . 12 73 4.3.1. Session-Termination-Request . . . . . . . . . . . . . 12 74 4.3.2. Session-Termination-Answer . . . . . . . . . . . . . . 12 75 4.3.3. Abort-Session-Request . . . . . . . . . . . . . . . . 12 76 4.3.4. Abort-Session-Answer . . . . . . . . . . . . . . . . . 13 77 4.4. Accounting for Mobile IPv6 services . . . . . . . . . . . 13 78 4.4.1. Accounting-Request . . . . . . . . . . . . . . . . . . 13 79 4.4.2. Accounting-Answer . . . . . . . . . . . . . . . . . . 14 80 5. Command Codes . . . . . . . . . . . . . . . . . . . . . . . . 14 81 5.1. Command Code for Mobile IPv6 with IKEv2 and EAP . . . . . 14 82 5.1.1. Diameter-EAP-Request . . . . . . . . . . . . . . . . . 14 83 5.1.2. Diameter-EAP-Answer . . . . . . . . . . . . . . . . . 15 84 5.2. Command Codes for Mobile IPv6 Authentication Protocol 85 Support . . . . . . . . . . . . . . . . . . . . . . . . . 16 86 5.2.1. MIP6-Request . . . . . . . . . . . . . . . . . . . . . 17 87 5.2.2. MIP6-Answer . . . . . . . . . . . . . . . . . . . . . 18 88 6. AVPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 89 6.1. User-Name AVP . . . . . . . . . . . . . . . . . . . . . . 21 90 6.2. Service-Selection AVP . . . . . . . . . . . . . . . . . . 21 91 6.3. MIP-MN-AAA-SPI AVP . . . . . . . . . . . . . . . . . . . . 22 92 6.4. MIP-MN-HA-SPI AVP . . . . . . . . . . . . . . . . . . . . 22 93 6.5. MIP-Mobile-Node-Address AVP . . . . . . . . . . . . . . . 22 94 6.6. MIP6-Agent-Info AVP . . . . . . . . . . . . . . . . . . . 22 95 6.7. MIP-Careof-Address AVP . . . . . . . . . . . . . . . . . . 23 96 6.8. MIP-Authenticator AVP . . . . . . . . . . . . . . . . . . 23 97 6.9. MIP-MAC-Mobility-Data AVP . . . . . . . . . . . . . . . . 23 98 6.10. MIP-Session-Key AVP . . . . . . . . . . . . . . . . . . . 23 99 6.11. MIP-MSA-Lifetime AVP . . . . . . . . . . . . . . . . . . . 23 100 6.12. MIP-MN-HA-MSA AVP . . . . . . . . . . . . . . . . . . . . 24 101 6.13. MIP-Algorithm-Type AVP . . . . . . . . . . . . . . . . . . 24 102 6.14. MIP-Replay-Mode AVP . . . . . . . . . . . . . . . . . . . 24 103 6.15. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . . . 24 104 6.16. MIP-Timestamp AVP . . . . . . . . . . . . . . . . . . . . 26 105 6.17. QoS-Capability AVP . . . . . . . . . . . . . . . . . . . . 26 106 6.18. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 26 107 6.19. Chargeable-User-Identity AVP . . . . . . . . . . . . . . . 26 108 6.20. MIP6-Auth-Mode AVP . . . . . . . . . . . . . . . . . . . . 26 109 6.21. Coupled Accounting Model Accounting AVPs . . . . . . . . . 27 110 7. Result-Code AVP Values . . . . . . . . . . . . . . . . . . . . 27 111 7.1. Success . . . . . . . . . . . . . . . . . . . . . . . . . 28 112 7.2. Permanent Failures . . . . . . . . . . . . . . . . . . . . 28 113 8. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 28 114 8.1. DER, DEA, MIR and MIA AVP/Command-Code Table . . . . . . . 29 115 8.2. Coupled Accounting Model AVP Table . . . . . . . . . . . . 29 116 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 117 9.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . 30 118 9.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . 30 119 9.3. Result-Code AVP Values . . . . . . . . . . . . . . . . . . 31 120 9.4. Application Identifier . . . . . . . . . . . . . . . . . . 31 121 9.5. Namespaces . . . . . . . . . . . . . . . . . . . . . . . . 31 122 9.6. Mobile IPv6 Status Codes . . . . . . . . . . . . . . . . . 32 123 10. Security Considerations . . . . . . . . . . . . . . . . . . . 32 124 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 32 125 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 33 126 12.1. Normative References . . . . . . . . . . . . . . . . . . . 33 127 12.2. Informative References . . . . . . . . . . . . . . . . . . 34 128 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 35 129 Intellectual Property and Copyright Statements . . . . . . . . . . 37 131 1. Introduction 133 Performing the Mobile IPv6 protocol [1], requires the Mobile Node 134 (MN) to own a Home Address (HoA) and to have an assigned Home Agent 135 (HA) to the MN. The MN needs to register with the HA in order to 136 enable its reachability and mobility, when away from its home link. 137 The registration process itself may require an establishment of IPSec 138 security associations (SA) and cryptographic material between the MN 139 and HA. Alternatively, the registration process may be secured using 140 a mobility message authentication option, which enables IPv6 mobility 141 in a MN without having to establish an IPSec SA with its HA. 142 Providing the collection of home address, HA address and keying 143 material is generally referred to as the Mobile IPv6 bootstrapping 144 problem [15]. The purpose of this specification is to provide 145 Diameter support for the interaction between the HA and the 146 Authentication, Authorization, and Accounting (AAA) server. This 147 specification satisfies the requirements defined in [16] for the 148 bootstrapping problem in the split scenario [2] and also specifies 149 Diameter support for the Authentication Protocol for Mobile IPv6 [3]. 150 The Diameter support defined in this specification also applies to 151 Dual Stack Mobile IPv6 [17]. 153 From a Mobility Service Provider (MSP) perspective, it is important 154 to verify that the MN is authenticated and authorized to utilize 155 Mobile IPv6 service, and is accounted for those. Only when the MN is 156 authenticated and authorized, the MSP allows the bootstrapping of 157 Mobile IPv6 parameters. Thus, prior to processing the Mobile IPv6 158 registrations, the HA, participates in the authentication of the MN 159 to verify the MN's identity. The HA also participates in the Mobile 160 IPv6 authorization process involving the Diameter infrastructure. 161 The HA, due to its role in traffic forwarding, may also perform 162 accounting for the Mobile IPv6 service provided to the MN. 164 This document enables the following functionality: 166 Authentication: Asserting or helping with assertion of the 167 correctness of the MN identity. As a Diameter client supporting 168 the new Diameter Mobile IPv6 application, the HA may need to 169 support more than one authentication type depending on the 170 environment. Although the authentication is performed by the AAA 171 server there is an impact for the HA as different set of command 172 codes are needed for the respective authentication procedures. 174 Authorization: The HA must verify that the user is authorized to the 175 Mobile IPv6 service using the assistance of the MSP Diameter 176 servers. This is accomplished through the use of new Diameter 177 applications specifically designed for performing Mobile IPv6 178 authorization decisions. This document defines required AAA 179 procedures and requires the HA to support them and to participate 180 in this authorization signaling. 182 Accounting: For accounting purposes and capacity planning, it is 183 required of the HA to provide accounting report to the Diameter 184 infrastructure and thus to support the related Diameter accounting 185 procedures. 187 Session Management: The management of the mobility services may 188 require the AAA to abort or the HA to terminate the Mobile IPv6 189 service before the binding expires. This document defines 190 procedures for the AAA based session management. 192 Figure 1 depicts the reference architecture for this document. 194 +--------+ 195 |Diameter| 196 |Server | 197 +--------+ 198 ^ 199 Back-End | Diameter Mobile IPv6 200 Protocol | HA<->AAA Server 201 Support | Interaction 202 | (this document) 203 v 204 +---------+ +---------------+ 205 | Mobile | Front-End Protocol |Home Agent / | 206 | Node |<-------------------->|Diameter Client| 207 +---------+ IKEv2 or RFC 4285 +---------------+ 209 Figure 1: Architecture Overview 211 Mobile IPv6 signaling between the MN and the HA can be protected 212 using two different mechanisms, namely using IPSec or Authentication 213 Protocol for Mobile IPv6 [3]. For these two approaches several 214 different authentication and key exchange solutions are available. 215 When IPSec is used to protect Mobile IPv6 signaling messages, IKEv2 216 is used [4]. IKEv2 supports EAP-based initiator authentication, 217 certificates and pre-shared secrets. Alternatively, Authentication 218 Protocol for Mobile IPv6 uses a mechanism that is very similar to the 219 one used for protecting Mobile IPv4 signaling messages. 221 The ability to use different credentials and methods to authenticate 222 the MN has an impact on the AAA interactions between the HA (acting 223 as a Diameter client) and the Diameter Server. This specification is 224 only limited to the following MN authentication methods: 226 o IKEv2 usage with EAP 227 o Mobile IPv6 Authentication Protocol 229 New authentication mechanisms may be added later by separate 230 specifications. 232 For accounting of Mobile IPv6 services provided to the MN, this 233 specification uses the Diameter Base Protocol accounting defined in 234 RFC 3588 [5]. 236 2. Terminology 238 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 239 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 240 document are to be interpreted as described in RFC 2119 [6]. 242 The Mobile IPv6 bootstrapping terminology is taken from [15]. 243 Additional terminology is defined below: 245 Authentication, Authorization, and Accounting (AAA): 247 AAA protocol based on Diameter [5] with required EAP support [7]. 249 Home AAA (AAAH): 251 An authentication, authorization and accounting server located in 252 user's home network i.e., in the home realm. 254 3. Application Identifiers 256 This specification defines two new Diameter applications and their 257 respective Application Identifiers: 259 Diameter Mobile IPv6 IKE (MIP6I) TBD by IANA 260 Diameter Mobile IPv6 Auth (MIP6A) TBD by IANA 262 The MIP6I Application Identifier is used when the MN is authenticated 263 and authorized using IKEv2. The MIP6A Application Identifier is used 264 when the MN is authenticated and authorized using Mobile IPv6 265 Authentication Protocol. 267 Mobile IPv6 related accounting generated by the HA uses either MIP6I 268 or MIP6A Application Identifier in the case of coupled accounting 269 model. Diameter Base Accounting Application Identifier (value of 3) 270 is used in the case of split accounting model. Refer Section 4.4 for 271 more information regarding the accounting models. 273 4. Protocol Description 275 4.1. Support for Mobile IPv6 with IKEv2 and EAP 277 The use of IKEv2 with EAP between the MN and the HA allows the AAA to 278 authenticate the MN. When EAP is used with IKEv2, the Diameter EAP 279 application logic and procedures, as defined in [7], are re-used. 280 EAP methods that do not establish a shared key SHOULD NOT be used, as 281 they are subject to a number of man-in-the-middle attacks as stated 282 in Section 2.16 and Section 5 of RFC 4306 [8]. AVPs specific to 283 Mobile IPv6 bootstrapping are added to the EAP application commands. 285 Figure 3 shows the message flow involved during the authentication 286 phase when EAP is used. 288 Mobile Home Diameter 289 Node Agent Server 290 | | | 291 | HDR, SAi1, KEi, Ni (1) | | 292 |-------------------------------->| | 293 | | | 294 | HDR, SAr1, KEr, Nr, [CERTREQ](2)| | 295 |<--------------------------------| | 296 | | | 297 | HDR, SK{IDi,[CERTREQ,] [IDr,] | | 298 | [CP(CFG_REQUEST),] | | 299 | SAi2, TSi, TSr} (3) | DER (EAP-Response) (4) + | 300 |-------------------------------->| MIP6 Bootstrapping AVPs | 301 | |------------------------->| 302 | | | 303 | | DEA (EAP-Request) (5) | 304 | HDR, SK{IDr, [CERT,] AUTH, EAP} |<-------------------------| 305 |<------------------------------- | | 306 | | | 307 | HDR, SK{EAP} | | 308 |-------------------------------->| DER (EAP-Response) | 309 | |------------------------->| 310 | | | 311 | | DEA (EAP-Request) | 312 | HDR, SK{EAP-Request} |<-------------------------| 313 |<--------------------------------| | 314 | | | 315 | HDR, SK{EAP-Response} | | 316 |-------------------------------->| DER (EAP-Response) | 317 | |------------------------->| 318 | ... | ... | 319 | | | 320 | | DEA (EAP-Success) + | 321 | | MIP6 Bootstrapping AVPs | 322 | HDR, SK{EAP-Success} |<-------------------------| 323 |<--------------------------------| | 324 | | | 325 | HDR, SK{AUTH} | | 326 |-------------------------------->| | 327 | | | 328 | HDR, SK{AUTH, [CP(CFG_REPLY,] | | 329 | SAr2, TSi, TSr} | | 330 |<--------------------------------| | 331 | | | 333 Figure 3: Mobile IPv6 bootstrapping using IKEv2 and EAP 335 The MN and the HA start the interaction with an IKE_SA_INIT exchange. 337 In this phase cryptographic algorithms are negotiated, nonces and 338 Diffie-Hellman parameters are exchanged. Message (3) starts the 339 IKE_AUTH phase. This second phase authenticates the previous 340 messages, exchanges identities and certificates and establishes the 341 first CHILD_SA. It is used to mutually authenticate the MN (acting 342 as an IKEv2 Initiator) and the HA (acting as an IKEv2 Responder). 343 The identity of the user/MN is provided in the IDi field. The MN 344 indicates its willingness to be authenticated via EAP by omitting the 345 AUTH field in message (3) (see Section 2.16 of [8]). 347 As part of the authentication process, the MN MAY request a Home- 348 Address, a Home Prefix or suggests one, see [4], using a CFG_REQUEST 349 payload in the message (3). 351 The HA extracts the IDi field from the message (3) and sends a 352 Diameter-EAP-Request (DER) message (4) towards the authenticating 353 Diameter server. The EAP-Payload AVP contains a EAP-Response/ 354 Identity with the identity extracted from the IDi field. 356 This message is routed to the MN's Diameter server/EAP server. The 357 Diameter server selects the EAP method and replies with the Diameter- 358 EAP-Answer (DEA) Message. Depending on the type of EAP method 359 chosen, a number of DER and DEA messages carry the method specific 360 exchanges between the MN and the Diameter server/EAP server. 362 At the end of the EAP authentication phase, the Diameter server 363 indicates the result of the authentication in the Result-Code AVP and 364 provides the corresponding EAP packet (EAP Success or EAP Failure). 365 The last IKEv2 message sent by the HA contains the Home Address or 366 the Home Prefix. In the latter case, a CREATE_CHILD_SA exchange is 367 necessary to setup IPSec SAs for Mobile IPv6 signaling. 369 In some deployment scenarios, the HA may also acts as a IKEv2 370 Responder for IPSec VPN access. A problem in this case is that the 371 IKEv2 responder may not know if IKEv2 is used for Mobile IPv6 service 372 or for IPSec VPN access service. A network operator needs to be 373 aware of this limitation. The MN may provide a hint of the intended 374 service, for example, by using different identities in the IKE_AUTH 375 message for the IPSec VPN service and Mobile IPv6 service. However, 376 the use of different identities during the IKEv2 negotiation is 377 deployment specific. Another possibility is to make the distinction 378 on the MN subscription basis. In this case the Diameter server can 379 inform the HA during the IKEv2 negotiation whether the MN is 380 provisioned with an IPSec VPN access service or Mobile IPv6 service. 382 Eventually, when the HA receives a Binding Update (BU), the HA 383 authenticates and authorizes the MN. It is RECOMMENDED that the HA 384 sends an accounting request message every time it receives a BU. 386 4.2. Support for the Mobile IPv6 Authentication Protocol 388 Figure 4 shows the message sequence between the MN, the HA and the 389 Diameter server during the registration when Mobile IPv6 390 Authentication Protocol is used. A BU and a Binding Acknowledgement 391 (BA) messages are used in the binding registration process. 393 Receiving a BU at the HA initiates a MIP6-Request to be sent to the 394 Diameter server. The Diameter server in turn responds with a MIP6- 395 Answer. The HA may assign a Home Address to the MN and provide it to 396 the Diameter server in the MIP-Mobile-Node-Address AVP. 398 According to [3] the MN uses the Mobile Node Identifier Option, 399 specifically the MN-NAI mobility option (as defined in [18]) to 400 identify itself. The HA MUST copy the MN-NAI mobility option value 401 to the User-Name AVP in the subsequent request messages. 403 The procedure described in this specification for the Mobile IPv6 404 Authentication Protocol is only needed for the initially received BU 405 for which the HA does not have an existing security association. 406 When the HA receives subsequent BUs, they are processed locally in 407 the HA. It is RECOMMENDED that the HA sends an accounting request 408 message every time it receives a Binding Update. However, the HA MAY 409 re-authorize the MN with the Diameter server at any time depending on 410 the deployment and the local policy. 412 In some architectures and network deployments the MN-HA security 413 associations may be established as a result of a successful network 414 access authentication. In such deployments, both MN and Diameter 415 server share the keying material required for computation and 416 validation of the MN-HA Authentication Option, and a Security 417 Parameter Index (SPI) for indexing an appropriate security 418 association. Upon receiving a BU with a MN-HA Authentication Option, 419 the HA retrieves the keying material required for the computation and 420 validation of the MN-HA Authentication Option from the Diameter 421 server. The Diameter request message sent by the HA must contain 422 enough information (such as SPI, MN-NAI, etc) so that the Diameter 423 server is able to locate the matching MN-HA security association and 424 return correct keying material back to the HA. 426 This specification assumes that in the case Mobile IPv6 427 Authentication Protocol is used, the MN-AAA option is included in the 428 BU. Other possible uses of Mobile IPv6 Authentication Protocol are 429 out of scope of this specification and would require a new 430 specification to describe the detailed behavior of the HA-AAAH 431 interface. However, the HA-AAAH interface has been designed in a way 432 that the Mobile IPv6 Authentication Protocol may also be used without 433 the MN-AAA option. 435 Mobile Home Diameter 436 Node Agent Server 437 | | | 438 | | MIP6-Request + MIP6 | 439 | Binding Update | Bootstrapping AVPs | 440 |------------------------------------>|-------------------->| 441 | (Mobile Node Identifier Option, | | 442 | Mobility Message Replay Protection | | 443 | Option, Authentication Option) | | 444 | | | 445 | | MIP6-Answer + MIP6 | 446 | Binding Acknowledgement | Bootstrapping AVPs | 447 |<------------------------------------|<--------------------| 448 | (Mobile Node Identifier Option | | 449 | Mobility Message Replay Protection | | 450 | Option, Authentication Option) | | 452 Figure 4: Mobile IPv6 Bootstrapping using the Mobile IPv6 453 Authentication Protocol 455 4.3. Mobile IPv6 Session Management 457 The Diameter server may maintain state or may be stateless. This is 458 indicated in the Auth-Session-State AVP (or its absence). The HA 459 MUST support the Authorization Session State Machine defined in [5]. 460 Moreover, the following four commands may be exchanged between the HA 461 and the Diameter server. 463 4.3.1. Session-Termination-Request 465 The Session-Termination-Request (STR) message [5] is sent by the HA 466 to inform the Diameter server that an authorized session is being 467 terminated. 469 4.3.2. Session-Termination-Answer 471 The Session-Termination-Answer (STA) message [5] is sent by the 472 Diameter server to acknowledge the notification that the session has 473 been terminated. 475 4.3.3. Abort-Session-Request 477 The Abort-Session-Request (ASR) message [5] is sent by the Diameter 478 server to terminate the session. This fulfills one of the 479 requirement described in [16]. 481 4.3.4. Abort-Session-Answer 483 The Abort-Session-Answer (ASA) message [5] is sent by the Home Agent 484 in response to an ASR message. 486 4.4. Accounting for Mobile IPv6 services 488 The HA MUST be able act as a Diameter client collecting accounting 489 records needed for service control and charging. The HA MUST support 490 the accounting procedures (specifically the command codes mentioned 491 below) and the Accounting Session State Machine as defined in [5]. 492 The command codes, exchanged between the HA and Diameter server for 493 accounting purposes, are provided in the following subsections. 495 The Diameter application design guideline [19] defines two separate 496 models for accounting: 498 Split accounting model: 500 According to this model, the accounting messages use the Diameter 501 Base Accounting Application Identifier (value of 3). Since 502 accounting is treated as an independent application, accounting 503 commands may be routed separately from the rest of application 504 messages and thus the accounting messages generally end up in a 505 central accounting server. Since Diameter Mobile IPv6 application 506 does not define its own unique accounting commands, this is the 507 preferred choice, since it permits use of centralized accounting 508 for several applications. 510 Coupled accounting model: 512 In this model, the accounting messages will use either the Mobile 513 IPv6 Split or the Mobile IPv6 Auth Application Identifiers. This 514 means that accounting messages will be routed like any other 515 Mobile IPv6 application messages. This requires the Diameter 516 server in charge of Mobile IPv6 application to handle the 517 accounting records (e.g., sends them to a proper accounting 518 server). 520 As mentioned above, the preferred choice is to use the split 521 accounting model and thus to choose Diameter Base Accounting 522 Application Identifier (value of 3) for accounting messages. 524 4.4.1. Accounting-Request 526 The Accounting-Request command [5] is sent by the HA to the Diameter 527 server to exchange accounting information regarding the MN with the 528 Diameter server. 530 4.4.2. Accounting-Answer 532 The Accounting-Answer command [5] is sent by the Diameter server to 533 the HA to acknowledge receiving an Accounting-Request. 535 5. Command Codes 537 5.1. Command Code for Mobile IPv6 with IKEv2 and EAP 539 For the use of Mobile IPv6 with IKEv2 and EAP this document reuses 540 the Diameter EAP application [7] commands: Diameter-EAP-Request (DER) 541 and Diameter-EAP-Answer (DEA). This specification extends the 542 existing DER and DEA command ABNFs with a number AVPs to support 543 Mobile IPv6 split scenario bootstrapping. Other than new additional 544 AVPs and the corresponding additions to the command ABNFs, the 545 Diameter EAP application command ABNFs remain unchanged. 547 Command-Name Abbrev. Code Reference Application 548 --------------------------------------------------------------------- 549 Diameter-EAP-Request DER 268 RFC 4072 Diameter Mobile IPv6 IKE 550 Diameter-EAP-Answer DEA 268 RFC 4072 Diameter Mobile IPv6 IKE 552 Figure 5: Command Codes 554 5.1.1. Diameter-EAP-Request 556 The Diameter-EAP-Request (DER) message, indicated by the Command-Code 557 field set to 268 and the 'R' bit set in the Command Flags field, is 558 sent by the HA to the Diameter server to initiate a Mobile IPv6 559 service authentication and authorization procedure. The 560 Application-ID field of the Diameter Header MUST be set to the 561 Diameter Mobile IPv6 IKE Application ID (value of TDB). 563 ::= < Diameter Header: 268, REQ, PXY > 564 < Session-Id > 565 { Auth-Application-Id } 566 { Origin-Host } 567 { Origin-Realm } 568 { Destination-Realm } 569 { Auth-Request-Type } 570 [ Destination-Host ] 571 [ NAS-Identifier ] 572 [ NAS-IP-Address ] 573 [ NAS-IPv6-Address ] 574 [ NAS-Port-Type ] 575 [ User-Name ] 576 ... 577 { EAP-Payload } 578 ... 579 [ MIP6-Feature-Vector ] 580 [ MIP6-Agent-Info ] 581 *2[ MIP-Mobile-Node-Address ] 582 [ Chargeable-User-Identity ] 583 [ Service-Selection ] 584 [ QoS-Capability ] 585 * [ QoS-Resources ] 586 ... 587 * [ AVP ] 589 Mobile IPv6 bootstrapping AVPs are only included in the first DER 590 message send by the HA. The subsequent DER messages required by the 591 EAP-method do not need to include any Mobile IPv6 bootstrapping AVPs. 592 The MN is both authenticated and authorized for the mobility service 593 during the EAP authentication. Thus the Auth-Request-Type AVP is set 594 to the value AUTHORIZE_AUTHENTICATE. 596 5.1.2. Diameter-EAP-Answer 598 The Diameter-EAP-Answer (DEA) message, indicated by the Command-Code 599 field set to 268 and 'R' bit cleared in the Command Flags field, is 600 sent in response to the Diameter-EAP-Request message (DER). The 601 Application-Id field in the Diameter message header MUST be set to 602 the Diameter Mobile IPv6 IKE Application-Id (value of TBD). If the 603 Mobile IPv6 authentication procedure was successful then the response 604 MAY include any set of bootstrapping AVPs. 606 ::= < Diameter Header: 268, PXY > 607 < Session-Id > 608 { Auth-Application-Id } 609 { Auth-Request-Type } 610 { Result-Code } 611 { Origin-Host } 612 { Origin-Realm } 613 [ User-Name ] 614 [ EAP-Payload ] 615 [ EAP-Reissued-Payload ] 616 [ EAP-Master-Session-Key ] 617 [ EAP-Key-Name ] 618 [ Multi-Round-Time 619 ... 620 *2[ MIP-Mobile-Node-Address ] 621 [ MIP6-Feature-Vector ] 622 [ MIP6-Agent-Info ] 623 * [ QoS-Resources ] 624 [ Chargeable-User-Identity ] 625 ... 626 * [ AVP ] 628 If the EAP-based authentication and the authorization for the 629 mobility service succeeds, then the Mobile IPv6 bootstrapping AVPs 630 are included in the last DEA message that also carries the EAP- 631 Success EAP payload. The other DEA messages required by the used 632 EAP-method do not include any Mobile IPv6 bootstrapping AVPs. 634 5.2. Command Codes for Mobile IPv6 Authentication Protocol Support 636 This section defines the commands that are used for support with the 637 Mobile IPv6 Authentication Protocol. 639 There are multiple ways of deploying and utilizing Mobile IPv6 640 Authentication Protocol, especially regarding the associated AAA 641 interactions. In order to support multiple deployment models this 642 specification defines the MIP6-Auth-Mode AVP that in the request 643 message tells the mode that the HA supports. This specification 644 defines a method that requires the use of the MN-AAA option with the 645 Mobile IPv6 Authentication Protocol. 647 Command-Name Abbrev. Code Reference Application 648 --------------------------------------------------------------------- 649 MIP6-Request MIR TBD 5.3.1 Diameter Mobile IPv6 Auth 650 MIP6-Answer MIA TBD 5.3.2 Diameter Mobile IPv6 Auth 652 Command Codes 654 5.2.1. MIP6-Request 656 The MIP6-Request (MIR), indicated by the Command-Code field set to 657 TBD and the 'R' bit set in the Command Flags field, is sent by the 658 HA, acting as a Diameter client, in order to request the 659 authentication and authorization of a MN. 661 Although the HA provides the Diameter server with a replay protection 662 related information, the HA is responsible for the replay protection. 664 The message format is shown below. 666 ::= < Diameter Header: XXX, REQ, PXY > 667 < Session-ID > 668 { Auth-Application-Id } 669 { User-Name } 670 { Destination-Realm } 671 { Origin-Host } 672 { Origin-Realm } 673 { Auth-Request-Type } 674 [ Destination-Host ] 675 [ Origin-State-Id ] 676 [ NAS-Identifier ] 677 [ NAS-IP-Address ] 678 [ NAS-IPv6-Address ] 679 [ NAS-Port-Type ] 680 [ Called-Station-Id ] 681 [ Calling-Station-Id ] 682 [ MIP6-Feature-Vector ] 683 { MIP6-Auth-Mode } 684 [ MIP-MN-AAA-SPI ] 685 [ MIP-MN-HA-SPI ] 686 1*2{ MIP-Mobile-Node-Address } 687 { MIP6-Agent-Info } 688 { MIP-Careof-Address } 689 [ MIP-Authenticator ] 690 [ MIP-MAC-Mobility-Data ] 691 [ MIP-Timestamp ] 692 [ QoS-Capability ] 693 * [ QoS-Resources ] 694 [ Chargeable-User-Identity ] 695 [ Service-Selection ] 696 [ Authorization-Lifetime ] 697 [ Auth-Session-State ] 698 * [ Proxy-Info ] 699 * [ Route-Record ] 700 * [ AVP ] 702 If the MN is both authenticated and authorized for the mobility 703 service, then he Auth-Request-Type AVP is set to the value 704 AUTHORIZE_AUTHENTICATE. This is the case when the MIP6-Auth-Mode is 705 set to the value MIP6_AUTH_MN_AAA. 707 5.2.2. MIP6-Answer 709 The MIP6-Answer (MIA) message, indicated by the Command-Code field 710 set to TBD and the 'R' bit cleared in the Command Flags field, is 711 sent by the Diameter server in response to the MIP6-Request message. 712 The User-Name MAY be included in the MIA if it is present in the MIR. 713 The Result-Code AVP MAY contain one of the values defined in 714 Section 7, in addition to the values defined in RFC 3588 [5]. 716 An MIA message with the Result-Code AVP set to DIAMETER_SUCCESS MUST 717 include the MIP-Mobile-Node-Address AVP. 719 The message format is shown below. 721 ::= < Diameter Header: XXX, PXY > 722 < Session-Id > 723 { Auth-Application-Id } 724 { Result-Code } 725 { Origin-Host } 726 { Origin-Realm } 727 { Auth-Request-Type } 728 [ User-Name ] 729 [ Authorization-Lifetime ] 730 [ Auth-Session-State ] 731 [ Error-Message ] 732 [ Error-Reporting-Host ] 733 [ Re-Auth-Request-Type ] 734 [ MIP6-Feature-Vector ] 735 [ MIP-Agent-Info ] 736 *2[ MIP-Mobile-Node-Address ] 737 [ MIP-MN-HA-MSA ] 738 * [ QoS-Resources ] 739 [ Chargeable-User-Identity ] 740 [ Origin-State-Id ] 741 * [ Proxy-Info ] 742 * [ Redirect-Host ] 743 [ Redirect-Host-Usage ] 744 [ Redirect-Max-Cache-Time ] 745 * [ Failed-AVP ] 746 * [ AVP ] 748 6. AVPs 750 To provide support for RFC 4285 [3] and for RFC 4877 [4] the AVPs in 751 the following subsections are needed. RFC 3588, RFC 4004 and RFC 752 4005 [9] defined AVPs are reused whenever possible without changing 753 the existing semantics of those AVPs. 755 +---------------------------+ 756 | AVP Flag rules | 757 +-----+-----+----+-----+----+ 758 AVP Defined | | |SHLD| MUST|MAY | 759 Attribute Name Code in Value Type |MUST | MAY | NOT| NOT|Encr| 760 +-----------------------------------------+-----+-----+----+-----+----+ 761 |MIP6-Feature- TBD Note 1 Unsigned64 | M | P | | V | Y | 762 | Vector | | | | | | 763 +-----------------------------------------+-----+-----+----+-----+----+ 764 |MIP-Mobile- | M | P | | V | Y | 765 | Node-Address 334 RFC4004 Address | | | | | | 766 +-----------------------------------------+-----+-----+----+-----+----+ 767 |MIP6-Agent-Info TBD Note 3 Grouped | M | P | | V | Y | 768 +-----------------------------------------+-----+-----+----+-----+----+ 769 |User-Name 1 RFC3588 UTF8String | M | P | | V | Y | 770 +-----------------------------------------+-----+-----+----+-----+----+ 771 |Service- TBD 6.2 UTF8String | M | P | | V | Y | 772 | Selection | | | | | | 773 +-----------------------------------------+-----+-----+----+-----+----+ 774 |QoS-Capability TBD Note 2 Grouped | M | P | | V | Y | 775 +-----------------------------------------+-----+-----+----+-----+----+ 776 |QoS-Resources TBD Note 2 Grouped | M | P | | V | Y | 777 +-----------------------------------------+-----+-----+----+-----+----+ 778 |MIP-MN-HA-MSA TBD 6.12 Grouped | M | P | | V | Y | 779 +-----------------------------------------+-----+-----+----+-----+----+ 780 |Chargeable-User- OctetString| M | P | | V | Y | 781 | Identity 89 6.19 | | | | | | 782 +-----------------------------------------+-----+-----+----+-----+----+ 784 AVPs for Mobile IPv6 IKE Application 786 Note 1: The MIP6-Feature-Vector is defined in Section 4.7.4 of [10]. 788 Note 2: The QoS-Capability and QoS-Resource AVPs are defined in 789 Sections 4.1 and 4.3 of [11]. 791 Note 3: The MIP6-Agent-Info is defined in Section 4.5.1 of [10]. 793 +---------------------------+ 794 | AVP Flag rules | 795 +-----+-----+----+-----+----+ 796 AVP Section | | |SHLD| MUST|MAY | 797 Attribute Name Code Defined Value Type |MUST | MAY | NOT| NOT|Encr| 798 +-----------------------------------------+-----+-----+----+-----+----+ 799 |MIP6-Feature- TBD Note 1 Unsigned64 | M | P | | V | Y | 800 | Vector | | | | | | 801 +-----------------------------------------+-----+-----+----+-----+----+ 802 |User-Name 1 RFC3588 UTF8String | M | P | | V | Y | 803 +-----------------------------------------+-----+-----+----+-----+----+ 804 |Service- TBD 6.2 UTF8String | M | P | | V | Y | 805 | Selection | | | | | | 806 +-----------------------------------------+-----+-----+----+-----+----+ 807 |MIP-MN-AAA-SPI 341 RFC4004 Unsigned32 | M | P | | V | Y | 808 +-----------------------------------------+-----+-----+----+-----+----+ 809 |MIP-MN-HA-SPI TBD 6.4 Unsigned32 | M | P | | V | Y | 810 +-----------------------------------------+-----+-----+----+-----+----+ 811 |MIP-Mobile- 333 RFC4004 Address | M | P | | V | Y | 812 | Node-Address | | | | | | 813 +-----------------------------------------+-----+-----+----+-----+----+ 814 |MIP6-Agent-Info TBD Note 3 Grouped | M | P | | V | Y | 815 +-----------------------------------------+-----+-----+----+-----+----+ 816 |MIP-Careof- TBD 6.7 Address | M | P | | V | Y | 817 | Address | | | | | | 818 +-----------------------------------------+-----+-----+----+-----+----+ 819 |MIP- TBD 6.8 OctetString| M | P | | V | Y | 820 | Authenticator | | | | | | 821 +-----------------------------------------+-----+-----+----+-----+----+ 822 |MIP-MAC- TBD 6.9 OctetString| M | P | | V | Y | 823 | Mobility-Data | | | | | | 824 +-----------------------------------------+-----+-----+----+-----+----+ 825 |MIP-Session-Key 343 6.10 OctetString| M | P | | V | Y | 826 +-----------------------------------------+-----+-----+----+-----+----+ 827 |MIP-MSA- 367 RFC4004 Unsigned32 | M | P | | V | Y | 828 | Lifetime | | | | | | 829 +-----------------------------------------+-----+-----+----+-----+----+ 830 |MIP-MN-HA-MSA TBD 6.12 Grouped | M | P | | V | Y | 831 +-----------------------------------------+-----+-----+----+-----+----+ 832 |MIP-Algorithm- 345 6.13 Enumerated | M | P | | V | Y | 833 | Type | | | | | | 834 +-----------------------------------------+-----+-----+----+-----+----+ 835 |MIP-Replay-Mode 346 6.14 Enumerated | M | P | | V | Y | 836 +-----------------------------------------+-----+-----+----+-----+----+ 837 |MIP-Timestamp TBD 6.16 Time | M | P | | V | Y | 838 +-----------------------------------------+-----+-----+----+-----+----+ 839 |QoS-Capability TBD Note 2 Grouped | M | P | | M | Y | 840 +-----------------------------------------+-----+-----+----+-----+----+ 841 |QoS-Resources TBD Note 2 Grouped | M | P | | V | Y | 842 +-----------------------------------------+-----+-----+----+-----+----+ 843 |Chargeable-User- OctetString| M | P | | V | Y | 844 | Identity 89 6.19 | | | | | | 845 +-----------------------------------------+-----+-----+----+-----+----+ 846 |MIP6-Auth-Mode TBD 6.20 Enumerated | M | P | | V | Y | 847 +-----------------------------------------+-----+-----+----+-----+----+ 848 |Rest of the AVPs RFC3588 | M | P | | V | Y | 849 |in the MIR & MIA RFC4005 | | | | | | 850 |excluding *[AVP] | | | | | | 851 +-----------------------------------------+-----+-----+----+-----+----+ 853 AVPs for the Mobile IPv6 Auth Application 855 Note 1: The MIP6-Feature-Vector is defined in Section 4.7.4 of [10]. 857 Note 2: The QoS-Capability and QoS-Resource AVPs are defined in 858 Sections 4.1 and 4.3 of [11]. 860 Note 3: The MIP6-Agent-Info is defined in Section 4.5.1 of [10]. 862 6.1. User-Name AVP 864 The User-Name AVP (AVP Code 1) is of type UTF8String and contains an 865 NAI extracted from the MN-NAI mobility option included in the 866 received BU message. Alternatively, the NAI can be extracted from 867 the IKEv2 IDi payload included in the IKE_AUTH message sent by the 868 IKE initiator. 870 6.2. Service-Selection AVP 872 The Service-Selection AVP (AVP Code TBD) is of type UTF8String and 873 contains the name of the service or the external network that the 874 mobility service should be associated with. In the scope of this 875 specification the value can extracted from the IKEv2 IDr payload, if 876 available in the IKE_AUTH message sent by the IKE initiator. 877 Alternatively, if the Mobile IPv6 Authentication Protocol is used, 878 then the Service-Selection AVP contains the string extracted from the 879 Service Selection Mobility Option [20], if available in the received 880 BU. Future specification may define additional ways to populate the 881 Service-Selection AVP with the required information. 883 This specification uses the Service-Selection AVP only in the 884 messages sent from the Diameter client to the Diameter Server. 885 However, the AVP is also available to be used in messages sent from 886 the Diameter server to the Diameter client. 888 6.3. MIP-MN-AAA-SPI AVP 890 The MIP-MN-AAA-SPI AVP (AVP Code 341) is of type Unsigned32 and 891 contains an SPI code extracted from the Mobility Message 892 Authentication Option included in the received BU message. The HA 893 includes this AVP in the MIR message when the MN-AAA Mobility Message 894 Authentication Option is available in the received BU (and the MIP6- 895 Auth-Mode AVP is set to value MIP6_AUTH_MN_AAA). 897 This AVP is re-used from [12]. 899 6.4. MIP-MN-HA-SPI AVP 901 The MIP-MN-HA-SPI AVP (AVP Code TBD) is of type Unsigned32 and 902 contains an SPI code which can be used with other parameters for 903 identifying the security association required for the validation of 904 the Mobile IPv6 MN-HA Authentication Option. 906 When included in the MIR message, the Diameter server needs to return 907 a valid MIP-MN-HA-MSA AVP in the corresponding MIA message. Either 908 the MIP-MN-HA-SPI AVP or the MIP-MN-AAA-SPI AVP MUST be present in 909 the MIR message, but not both. 911 6.5. MIP-Mobile-Node-Address AVP 913 The MIP-Mobile-Node-Address AVP (AVP Code 333) is of type Address and 914 contains the HA assigned IPv6 or IPv4 Home Address of the Mobile 915 Node. 917 If the MIP-Mobile-Node-Address AVP contains unspecified IPv6 address 918 (0::0) or all zeroes IPv4 address (0.0.0.0) in a request message, 919 then the HA expects the Diameter server to assign the Home Address in 920 a subsequent answer message. If the Diameter server assigns only an 921 IPv6 Home Network Prefix to the Mobile Node the lower 64 bits of the 922 MIP-Mobile-Node-Address AVP provided address MUST be set to zero. 924 This AVP is re-used from [12]. 926 6.6. MIP6-Agent-Info AVP 928 The MIP6-Agent-Info AVP is defined in Section 4.5.1 of [10] and 929 contains the IPv6 or the IPv4 address information of the HA. The HA 930 address in a request message is the same as in the received BU 931 message that triggered the authentication and authorization procedure 932 towards the Diameter server. 934 If the MIP6-Agent-Info AVP is present in an answer message and the 935 Result-Code AVP is set to DIAMETER_SUCCESS_RELOCATE_HA, then the 936 Diameter server is indicating to the HA that it MUST initiate a HA 937 switch procedure towards the MN (e.g., using the procedure defined in 938 [13]). If the Result-Code AVP is set to any other value, then the HA 939 SHOULD initiate the HA switch procedure towards the MN. The address 940 information of the assigned HA is defined in the MIP6-Agent-Info AVP. 942 6.7. MIP-Careof-Address AVP 944 The MIP-Careof-Address AVP (AVP Code TBD) is of type Address and 945 contains the IPv6 Care-of Address of the Mobile Node. The HA 946 extracts this IP address from the received BU message. 948 6.8. MIP-Authenticator AVP 950 The MIP-Authenticator AVP (AVP Code TBD) is of type OctetString and 951 contains the Authenticator Data from the received BU message. The HA 952 extracts this data from the MN-AAA Mobility Message Authentication 953 Option included in the received BU message. The HA includes this AVP 954 in the MIR message and sets the Diameter server is expected to return 955 the key material required for the calculation and validation of the 956 Mobile IPv6 MN-HA Authentication Option (and the MIP6-Auth-Mode AVP 957 is set to value MIP6_AUTH_MN_AAA). 959 6.9. MIP-MAC-Mobility-Data AVP 961 The MIP-MAC-Mobility-Data AVP (AVP Code TBD) is of type OctetString 962 and contains the calculated MAC_Mobility_Data, as defined in [3]. 963 The HA includes this AVP in the MIR message when the MN-AAA Mobility 964 Message Authentication Option is available in the received BU and the 965 Diameter server is expected to return the key material required for 966 the calculation and validation of the Mobile IPv6 MN-HA 967 Authentication Option (and the MIP6-Auth-Mode AVP is set to value 968 MIP6_AUTH_MN_AAA). 970 6.10. MIP-Session-Key AVP 972 The MIP-Session-Key AVP (AVP Code 343) is of type OctetString and 973 contains the MN-HA shared secret (i.e., the session key) for the 974 associated Mobile IPv6 MH-HA authentication option. When the 975 Diameter server computes the session key it is placed in this AVP. 977 This AVP is re-used from [12]. 979 6.11. MIP-MSA-Lifetime AVP 981 The MIP-MSA-Lifetime AVP (AVP Code 367) is of type Unsigned32 and 982 represents the period of time (in seconds) for which the session key 983 (see Section 6.10) is valid. The associated session key MUST NOT be 984 used if the lifetime has expired. 986 This AVP is re-used from [12]. 988 6.12. MIP-MN-HA-MSA AVP 990 The MIP-MN-HA-MSA AVP (AVP Code TBD) is of type Grouped and contains 991 the session related information for use with the Mobile IPv6 992 Authentication Protocol. 994 MIP-MN-HA-MSA ::= < AVP Header: TBD > 995 { MIP-Session-Key } 996 { MIP-MSA-Lifetime } 997 [ MIP-MN-HA-SPI ] 998 [ MIP-Algorithm-Type ] 999 [ MIP-Replay-Mode ] 1000 * [ AVP ] 1002 The MIP-MN-HA-SPI sub-AVP within the MIP-MN-HA-MSA grouped AVP 1003 identifies the security association required for the validation of 1004 the Mobile IPv6 MN-HA Authentication Option. 1006 6.13. MIP-Algorithm-Type AVP 1008 The MIP-Algorithm-Type AVP (AVP Code 345) is of type Enumerated and 1009 contains Algorithm identifier for the associated Mobile IPv6 MN-HA 1010 Authentication Option. The Diameter server selects the algorithm 1011 type. Existing algorithm types are defined in RFC 4004 that also 1012 fulfill current RFC 4285 requirements. 1014 This AVP is re-used from [12]. 1016 6.14. MIP-Replay-Mode AVP 1018 The MIP-Replay-Mode AVP (AVP Code 346) is of type Enumerated and 1019 contains the replay mode the HA for authenticating the mobile node. 1020 The replay modes, defined in RFC 4004 [12], are supported. 1022 This AVP is re-used from [12]. 1024 6.15. MIP6-Feature-Vector AVP 1026 This AVP is defined in [10]. This document defines a new capability 1027 bit for signaling the support of Mobile IPv6 route optimization. The 1028 following capability is defined in this document: 1030 MIP6_SPLIT (0x0000000100000000) 1032 When this flag is set by the NAS then it means that the Mobile 1033 IPv6 split scenario bootstrapping functionality is supported by 1034 the NAS. When this flag is set by the Diameter server then the 1035 Mobile IPv6 split scenario bootstrapping is supported by the 1036 Diameter server. 1038 RO_SUPPORTED (0x0000000200000000) 1040 Route optimization is supported. When the HA sets this bit, it 1041 indicates support for the route optimization. If this bit is 1042 unset in the returned Mobility-Capability AVP, the AAAH does not 1043 authorize route optimization for the MN. 1045 In a case the HA or the AAAH cannot authorize the use of route 1046 optimization then the HA SHOULD send a Binding Acknowledgement 1047 with a Status Code set to ACCEPTED_BUT_NO_ROUTE_OPTIMIZATION 1048 (status code TBD). This Status Code indicates that the binding 1049 registration succeeded but the HA will fail all possible 1050 subsequent route optimization attempts because of subscription or 1051 operator policy. 1053 USER_TRAFFIC_ENCRYPTION (0x0000000400000000) 1055 User plane traffic encryption is supported. When the HA sets this 1056 bit, it indicates support for the user plane traffic encryption 1057 between the MN and the HA. If this bit is unset in the returned 1058 Mobility-Capability AVP, the AAAH does not authorize user plane 1059 traffic encryption because of subscription or operator policy. 1061 In the case the AAAH cannot authorize the use of user plane 1062 traffic encryption then the HA SHOULD send a Binding 1063 Acknowledgement with a Status Code set to 1064 ACCEPTED_BUT_NO_TRAFFIC_ENCRYPTION (status code TBD). This Status 1065 Code indicates that the binding registration succeeded but the HA 1066 will silently discard all encrypted user plane packets sent by the 1067 MN to the HA. 1069 VPN_GW_MODE (0x0000000800000000) 1071 The HA is supposed to act as a IPSec VPN gateway for the user. 1072 When the HA sets this bit, it indicates support for acting as a 1073 standalone IPSec VPN gateway. If this bit is unset in the 1074 returned Mobility-Capability AVP, the AAAH does not authorize the 1075 HA to act as a standalone IPSec VPN gateway for the MN because of 1076 subscription or operator policy. 1078 MCOA_SUPPORTED (0x0000001000000000) 1080 Multiple Care-of Addresses (MCoA) [21] are supported. When the HA 1081 sets this bit, it indicates support for the MCoA. If this bit is 1082 unset in the returned Mobility-Capability AVP, the AAAH does not 1083 authorize the use of MCoA for the MN. 1085 In a case the HA or the AAAH cannot authorize the use of the MCoA 1086 then the HA SHOULD send a Binding Acknowledgement with a Status 1087 Code set to ACCEPTED_BUT_NO_MCOA (status code TBD). This Status 1088 Code indicates that the binding registration succeeded but the HA 1089 will fail all possible subsequent attempts to use MCoA because of 1090 subscription or operator policy. 1092 6.16. MIP-Timestamp AVP 1094 The MIP-Timestamp AVP (AVP Code TBD) is of type Time and may contain 1095 the timestamp value from the Mobility message replay protection 1096 option, defined in [3]. The HA extracts this value from the received 1097 BU message, if available. The HA includes this AVP in the MIR 1098 message when the MN-AAA Mobility Message Authentication Option is 1099 available in the received BU and the Diameter server is expected to 1100 return the key material required for the calculation and validation 1101 of the Mobile IPv6 MN-HA Authentication Option (and the MIP6-Auth- 1102 Mode AVP is set to value MIP6_AUTH_MN_AAA). 1104 6.17. QoS-Capability AVP 1106 The QoS-Capability AVP is defined in [11] and contains a list of 1107 supported Quality of Service profiles. 1109 6.18. QoS-Resources AVP 1111 The QoS-Resources AVP is defined in [11] and provides QoS and packet 1112 filtering capabilities. 1114 6.19. Chargeable-User-Identity AVP 1116 The Chargeable-User-Identity AVP (AVP code 89) is of type OctetString 1117 and contains an unique temporary handle of the user. The Chargeable- 1118 User-Identity is defined in RFC 4372 [14]. 1120 6.20. MIP6-Auth-Mode AVP 1122 The MIP6-Auth-Mode (AVP Code TBD) is of type Enumerated and contains 1123 information of the used Mobile IPv6 Authentication Protocol mode. 1124 This specification defines only one value MIP6_AUTH_MN_AAA and the 1125 corresponding AAA interactions when MN-AAA security association is 1126 used to authenticate the Binding Update. When the MIP6-Auth_Mode AVP 1127 is set to the value of MIP6_AUTH_MN_AAA, the Auth-Request-Type AVP 1128 MUST be set to the value of AUTHORIZE_AUTHENTICATE. 1130 If the Diameter server does not support the Mobile IPv6 1131 Authentication Protocol use mode proposed by the HA, then the 1132 Diameter server MUST fail the authentication/authorization and set 1133 the Result-Code AVP to the value of DIAMETER_ERROR_AUTH_MODE. 1135 6.21. Coupled Accounting Model Accounting AVPs 1137 Diameter Mobile IPv6 application is used in the case of the coupled 1138 account model. Diameter Mobile IPv4 application [12] accounting AVPs 1139 are reused in this document. The following AVPs SHOULD be included 1140 in the accounting request message: 1142 o Accounting-Input-Octets: Number of octets in IP packets received 1143 from the mobile node. 1144 o Accounting-Output-Octets: Number of octets in IP packets sent by 1145 the mobile node 1146 o Accounting-Input-Packets: Number of IP packets received from the 1147 mobile node. 1148 o Accounting-Output-Packets: Number of IP packets sent by the mobile 1149 node. 1150 o Acct-Multi-Session-Id: Used to link together multiple related 1151 accounting sessions, where each session would have a unique 1152 Session-Id, but the same Acct-Multi-Session-Id AVP. 1153 o Acct-Session-Time: Indicates the length of the current session in 1154 seconds. 1155 o MIP6-Feature-Vector: The supported features for this mobility 1156 service session. 1157 o MIP-Mobile-Node-Address: The Home Address of the mobile node. 1158 o MIP-Agent-Info: The current home agent of the mobile node. 1159 o Chargeable-User-Identity: The unique temporary identity of the 1160 user. This AVP MUST be included if it is available in the home 1161 agent. 1162 o Service-Selection: Currently selected mobility service. 1163 o QoS-Resources: Assigned QoS resources for the mobile node. 1164 o QoS-Capability: The QoS capability related to the assigned QoS- 1165 Resources. 1166 o MIP-Careof-Address: The current Care-of Address of the mobile 1167 node. 1169 7. Result-Code AVP Values 1171 This section defines new Result-Code [5] values that MUST be 1172 supported by all Diameter implementations that conform to this 1173 specification. 1175 7.1. Success 1177 Errors that fall within the Success category are used to inform a 1178 peer that a request has been successfully completed. 1180 DIAMETER_SUCCESS_RELOCATE_HA (Status Code TBD) 1182 This result code is used by the Diameter server to inform the HA 1183 that the MN MUST be switched to another HA. 1185 7.2. Permanent Failures 1187 Errors that fall within the permanent failures category are used to 1188 inform the peer that the request failed and SHOULD NOT be attempted 1189 again. 1191 DIAMETER_ERROR_END_TO_END_MIP6_KEY_ENCRYPTION (Status Code TBD) 1193 This error code is used by the Diameter server to inform the peer 1194 that the requested Mobile IPv6 session keys could not be delivered 1195 via a security association. 1196 DIAMETER_ERROR_MIP6_AUTH_MODE (Status Code TBD) 1198 This error code is used by the Diameter server to inform the peer 1199 that the requested Mobile IPv6 Authentication Protocol usage mode 1200 is not supported. 1202 8. AVP Occurrence Tables 1204 The following tables present the AVPs defined in this document and 1205 their occurrences in Diameter messages. Note that AVPs that can only 1206 be present within a Grouped AVP are not represented in this table. 1208 The table uses the following symbols: 1210 0: 1212 The AVP MUST NOT be present in the message. 1214 0+: 1216 Zero or more instances of the AVP MAY be present in the message. 1218 0-1: 1220 Zero or one instance of the AVP MAY be present in the message. 1222 1: 1224 One instance of the AVP MUST be present in the message. 1226 8.1. DER, DEA, MIR and MIA AVP/Command-Code Table 1228 +-----------------------+ 1229 | Command-Code | 1230 |-----+-----+-----+-----+ 1231 AVP Name | DER | DEA | MIR | MIA | 1232 -------------------------------|-----+-----+-----+-----+ 1233 MIP6-Feature-Vector | 0-1 | 0-1 | 0-1 | 0-1 | 1234 MIP-Mobile-Node-Address | 1-2 | 0-2 | 1-2 | 0-2 | 1235 MIP-MN-AAA-SPI | 0 | 0 | 0-1 | 0 | 1236 MIP-MN-HA-SPI | 0 | 0 | 0-1 | 0 | 1237 MIP6-Agent-Info | 1 | 0-1 | 1 | 0-1 | 1238 MIP-Careof-Address | 0 | 0 | 0-1 | 0 | 1239 MIP-Authenticator | 0 | 0 | 0-1 | 0 | 1240 MIP-MAC-Mobility-Data | 0 | 0 | 0-1 | 0 | 1241 MIP-MSA-Lifetime | 0 | 0 | 0 | 1 | 1242 MIP-MN-HA-MSA | 0 | 0 | 0 | 0-1 | 1243 MIP-Timestamp | 0 | 0 | 0-1 | 0-1 | 1244 User-Name | 0-1 | 0-1 | 1 | 0-1 | 1245 Service-Selection | 0-1 | 0 | 0-1 | 0 | 1246 QoS-Resources | *0 | *0 | *0 | *0 | 1247 QoS-Capability | 0-1 | 0 | 0-1 | 0 | 1248 Chargeable-User-Identity | 0-1 | 0-1 | 0-1 | 0-1 | 1249 MIP6-Auth-Mode | 0 | 0 | 1 | 0 | 1250 +-----+-----+-----+-----+ 1252 8.2. Coupled Accounting Model AVP Table 1254 The table in this section is used to represent which AVPs defined in 1255 this document are to be present in the Accounting messages, as 1256 defined in [5]. 1258 +-------------+ 1259 | Command-Code| 1260 |------+------+ 1261 Attribute Name | ACR | ACA | 1262 -------------------------------------|------+------+ 1263 Accounting-Input-Octets | 0-1 | 0-1 | 1264 Accounting-Input-Packets | 0-1 | 0-1 | 1265 Accounting-Output-Octets | 0-1 | 0-1 | 1266 Accounting-Output-Packets | 0-1 | 0-1 | 1267 Acct-Multi-Session-Id | 0-1 | 0-1 | 1268 Acct-Session-Time | 0-1 | 0-1 | 1269 MIP6-Feature-Vector | 0-1 | 0-1 | 1270 MIP6-Agent-Info | 0-1 | 0-1 | 1271 MIP-Mobile-Node-Address | 0-2 | 0-2 | 1272 Event-Timestamp | 0-1 | 0 | 1273 MIP-Careof-Address | 0-1 | 0 | 1274 Service-Selection | 0-1 | 0 | 1275 QoS-Capability | *0 | *0 | 1276 QoS-Resources | *0 | *0 | 1277 Chargeable-User-Identity | 0-1 | 0 | 1278 -------------------------------------|------+------+ 1280 9. IANA Considerations 1282 This section contains the namespaces that have either been created in 1283 this specification or had their values assigned to existing 1284 namespaces managed by IANA. 1286 9.1. Command Codes 1288 IANA is requested to allocate a command code values for the following 1289 new commands from the Command Code namespace defined in [5]. See 1290 Section 5 for the assignment of the namespace in this specification. 1292 Command Code | Value 1293 -----------------------------------+------ 1294 MIP6-Request (MIR) | TBD 1295 MIP6-Answer (MIA) | TBD 1297 9.2. AVP Codes 1299 This specification requires IANA to register the following new AVPs 1300 from the AVP Code namespace defined in [5]. 1302 o MIP-Careof-Address 1303 o MIP-Authenticator 1304 o MIP-MAC-Mobility-Data 1305 o MIP-Timestamp 1306 o MIP-MN-HA-SPI 1307 o MIP-MN-HA-MSA 1308 o Service-Selection 1309 o MIP6-Auth-Mode 1311 The AVPs are defined in Section 6. 1313 9.3. Result-Code AVP Values 1315 This specification requests IANA to allocate new values to the 1316 Result-Code AVP (AVP Code 268) namespace defined in [5]. See 1317 Section 7 for the assignment of the namespace in this specification. 1319 Result-Code | Value 1320 ----------------------------------------------+------ 1321 DIAMETER_SUCCESS_RELOCATE_HA | TBD 1322 DIAMETER_ERROR_END_TO_END_MIP6_KEY_ENCRYPTION | TBD 1323 DIAMETER_ERROR_MIP6_AUTH_MODE | TBD 1325 9.4. Application Identifier 1327 This specification requires IANA to allocate two new values "Diameter 1328 Mobile IPv6 IKE" and "Diameter Mobile IPv6 Auth" from the Application 1329 Identifier namespace defined in [5]. 1331 Application Identifier | Value 1332 -----------------------------------+------ 1333 Diameter Mobile IPv6 IKE (MIP6I) | TBD 1334 Diameter Mobile IPv6 Auth (MIP6A) | TBD 1336 9.5. Namespaces 1338 This specification defines new values to the "Mobility Capability" 1339 registry (see [10]) for use with the MIP6-Feature-Vector AVP: 1341 Token | Value | Description 1342 ---------------------------------+----------------------+------------ 1343 MIP6_SPLIT | 0x0000000100000000 | RFC TBD 1344 RO_SUPPORTED | 0x0000000200000000 | RFC TBD 1345 USER_TRAFFIC_ENCRYPTION | 0x0000000400000000 | RFC TBD 1346 VPN_GW_MODE | 0x0000000800000000 | RFC TBD 1347 MCOA_SUPPORTED | 0x0000001000000000 | RFC TBD 1348 IANA is requested to create a new registry "MIP6 Authentication Mode" 1349 registry for use with the enumerated MIP6-Auth-Mode AVP. The 1350 registry will initially contain the following values: 1352 Token | Value | Description 1353 ---------------------------------------------+----------+------------ 1354 MIP6_AUTH_MN_AAA | 1 | RFC TBD 1356 Allocation of new values follow the example policies described in 1357 [22] new values for the MIP6-Auth-Mode AVP will be assigned based on 1358 the "Specification Required" policy. 1360 9.6. Mobile IPv6 Status Codes 1362 This specification defines new Mobile IPv6 [1] Status Code values. 1363 The Status Code must be allocated from the range 0-127: 1365 Status Code | Value | Description 1366 ----------------------------------------+---------------+------------ 1367 ACCEPTED_BUT_NO_ROUTE_OPTIMIZATION | is set to TBD | RFC TBD 1368 ACCEPTED_BUT_NO_TRAFFIC_ENCRYPTION | is set to TBD | RFC TBD 1369 ACCEPTED_BUT_NO_MCOA | is set to TBD | RFC TBD 1371 10. Security Considerations 1373 The security considerations for the Diameter interaction required to 1374 accomplish the split scenario are described in in [2]. Additionally, 1375 the security considerations of the Diameter Base protocol [5], 1376 Diameter EAP application [7] are applicable to this document. 1378 The Diameter messages may be transported between the HA and the 1379 Diameter server via one or more AAA brokers or Diameter agents. In 1380 this case the HA to the Diameter server AAA communication rely on the 1381 security properties of the intermediate AAA brokers and Diameter 1382 agents (such as proxies). 1384 11. Acknowledgements 1386 The authors would like to thank Jari Arkko, Tolga Asversen, Pasi 1387 Eronen, Santiago Zapata Hernandez, Anders Kristensen, Avi Lior, John 1388 Loughney, Ahmad Muhanna, Behcet Sarikaya, Basavaraj Patil, Vijay 1389 Devarapalli, Lionel Morand, Domagoj Premec, Semyon Mizikovsky and 1390 Yoshihiro Ohba for all the useful discussions. Ahmad Muhanna 1391 provided a detailed review of the document in August 2007. 1393 We would also like to thank our Area Director, Dan Romascanu, for his 1394 support. 1396 Hannes Tschofenig would like to thank the European Commission support 1397 in the co-funding of the ENABLE project, where this work is partly 1398 being developed. 1400 Julien Bournelle would like to thank GET/INT since he began this work 1401 while he was under their employ. 1403 Madjid Nakhjiri would like to thank Huawei USA as most of his 1404 contributions to this draft were possible while he was under their 1405 employ. 1407 12. References 1409 12.1. Normative References 1411 [1] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in 1412 IPv6", RFC 3775, June 2004. 1414 [2] Giaretta, G., Kempf, J., and V. Devarapalli, "Mobile IPv6 1415 Bootstrapping in Split Scenario", RFC 5026, October 2007. 1417 [3] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury, 1418 "Authentication Protocol for Mobile IPv6", 1419 draft-ietf-mip6-rfc4285bis-03 (work in progress), July 2008. 1421 [4] Devarapalli, V. and F. Dupont, "Mobile IPv6 Operation with 1422 IKEv2 and the Revised IPsec Architecture", RFC 4877, 1423 April 2007. 1425 [5] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko, 1426 "Diameter Base Protocol", RFC 3588, September 2003. 1428 [6] Bradner, S., "Key words for use in RFCs to Indicate Requirement 1429 Levels", BCP 14, RFC 2119, March 1997. 1431 [7] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible 1432 Authentication Protocol (EAP) Application", RFC 4072, 1433 August 2005. 1435 [8] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol", 1436 RFC 4306, December 2005. 1438 [9] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, "Diameter 1439 Network Access Server Application", RFC 4005, August 2005. 1441 [10] Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C., and 1442 K. Chowdhury, "Diameter Mobile IPv6: Support for Network Access 1443 Server to Diameter Server Interaction", 1444 draft-ietf-dime-mip6-integrated-10 (work in progress), 1445 September 2008. 1447 [11] Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones, M., and 1448 A. Lior, "Quality of Service Attributes for Diameter", 1449 draft-ietf-dime-qos-attributes-07 (work in progress), 1450 June 2008. 1452 [12] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and P. 1453 McCann, "Diameter Mobile IPv4 Application", RFC 4004, 1454 August 2005. 1456 [13] Haley, B., Devarapalli, V., Deng, H., and J. Kempf, "Mobility 1457 Header Home Agent Switch Message", RFC 5142, January 2008. 1459 [14] Adrangi, F., Lior, A., Korhonen, J., and J. Loughney, 1460 "Chargeable User Identity", RFC 4372, January 2006. 1462 12.2. Informative References 1464 [15] Patel, A. and G. Giaretta, "Problem Statement for bootstrapping 1465 Mobile IPv6 (MIPv6)", RFC 4640, September 2006. 1467 [16] Giaretta, G., Guardini, I., Demaria, E., Bournelle, J., and R. 1468 Lopez, "AAA Goals for Mobile IPv6", 1469 draft-ietf-mext-aaa-ha-goals-01 (work in progress), May 2008. 1471 [17] Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and 1472 Routers", draft-ietf-mext-nemo-v4traversal-05 (work in 1473 progress), July 2008. 1475 [18] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury, 1476 "Mobile Node Identifier Option for Mobile IPv6 (MIPv6)", 1477 RFC 4283, November 2005. 1479 [19] Fajardo, V., Asveren, T., Tschofenig, H., McGregor, G., and J. 1480 Loughney, "Diameter Applications Design Guidelines", 1481 draft-ietf-dime-app-design-guide-07 (work in progress), 1482 July 2008. 1484 [20] Korhonen, J., Nilsson, U., and V. Devarapalli, "Service 1485 Selection for Mobile IPv6", RFC 5149, February 2008. 1487 [21] Wakikawa, R., Devarapalli, V., Ernst, T., and K. Nagami, 1488 "Multiple Care-of Addresses Registration", 1489 draft-ietf-monami6-multiplecoa-09 (work in progress), 1490 August 2008. 1492 [22] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA 1493 Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. 1495 Authors' Addresses 1497 Jouni Korhonen 1498 TeliaSonera 1499 P.O.Box 970 1500 Sonera FIN-00051 1501 Finland 1503 Email: jouni.korhonen@teliasonera.com 1505 Hannes Tschofenig 1506 Nokia Siemens Networks 1507 Linnoitustie 6 1508 Espoo 02600 1509 Finland 1511 Phone: +358 (50) 4871445 1512 Email: Hannes.Tschofenig@gmx.net 1513 URI: http://www.tschofenig.priv.at 1515 Julien Bournelle 1516 Orange Labs 1517 38-4O rue du general Leclerc 1518 Issy-Les-Moulineaux 92794 1519 France 1521 Email: julien.bournelle@orange-ftgroup.com 1523 Gerardo Giaretta 1524 Qualcomm 1525 5775 MoreHouse Dr 1526 San Diego, CA 92121 1527 USA 1529 Email: gerardo.giaretta@gmail.com 1530 Madjid Nakhjiri 1531 Motorola 1532 USA 1534 Email: madjid.nakhjiri@motorola.com 1536 Full Copyright Statement 1538 Copyright (C) The IETF Trust (2008). 1540 This document is subject to the rights, licenses and restrictions 1541 contained in BCP 78, and except as set forth therein, the authors 1542 retain all their rights. 1544 This document and the information contained herein are provided on an 1545 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1546 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 1547 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 1548 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1549 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1550 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1552 Intellectual Property 1554 The IETF takes no position regarding the validity or scope of any 1555 Intellectual Property Rights or other rights that might be claimed to 1556 pertain to the implementation or use of the technology described in 1557 this document or the extent to which any license under such rights 1558 might or might not be available; nor does it represent that it has 1559 made any independent effort to identify any such rights. Information 1560 on the procedures with respect to rights in RFC documents can be 1561 found in BCP 78 and BCP 79. 1563 Copies of IPR disclosures made to the IETF Secretariat and any 1564 assurances of licenses to be made available, or the result of an 1565 attempt made to obtain a general license or permission for the use of 1566 such proprietary rights by implementers or users of this 1567 specification can be obtained from the IETF on-line IPR repository at 1568 http://www.ietf.org/ipr. 1570 The IETF invites any interested party to bring to its attention any 1571 copyrights, patents or patent applications, or other proprietary 1572 rights that may cover technology that may be required to implement 1573 this standard. Please address the information to the IETF at 1574 ietf-ipr@ietf.org. 1576 Acknowledgment 1578 Funding for the RFC Editor function is provided by the IETF 1579 Administrative Support Activity (IASA).