idnits 2.17.1 draft-ietf-netext-bulk-re-registration-12.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 and authors Copyright Line does not match the current year -- The document date (February 14, 2012) is 4417 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Netext Working Group F. Abinader, Ed. 3 Internet-Draft Instituto Nokia de Tecnologia 4 Intended status: Standards Track S. Gundavelli, Ed. 5 Expires: August 17, 2012 K. Leung 6 Cisco 7 S. Krishnan 8 Ericsson 9 D. Premec 10 Unaffiliated 11 February 14, 2012 13 Bulk Binding Update Support for Proxy Mobile IPv6 14 draft-ietf-netext-bulk-re-registration-12 16 Abstract 18 For extending the lifetime of a mobility session, the Proxy Mobile 19 IPv6 specification requires the mobile access gateway to send a Proxy 20 Binding Update message to the local mobility anchor on a per-session 21 basis. In the absence of signaling semantics for performing 22 operations with group specific scope, it results in significant 23 amount of signaling traffic on a periodic basis between a given 24 mobile access gateway and a local mobility anchor. This document 25 defines optimizations to the binding update and revocation operations 26 in Proxy Mobile IPv6 for performing operations with group specific 27 scope with the use of a group identifier. 29 Status of this Memo 31 This Internet-Draft is submitted in full conformance with the 32 provisions of BCP 78 and BCP 79. 34 Internet-Drafts are working documents of the Internet Engineering 35 Task Force (IETF). Note that other groups may also distribute 36 working documents as Internet-Drafts. The list of current Internet- 37 Drafts is at http://datatracker.ietf.org/drafts/current/. 39 Internet-Drafts are draft documents valid for a maximum of six months 40 and may be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet-Drafts as reference 42 material or to cite them other than as "work in progress." 44 This Internet-Draft will expire on August 17, 2012. 46 Copyright Notice 48 Copyright (c) 2012 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 2. Conventions & Terminology . . . . . . . . . . . . . . . . . . 4 65 2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 5 66 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5 67 3. Bulk Binding Update Overview . . . . . . . . . . . . . . . . . 5 68 3.1. Motivation . . . . . . . . . . . . . . . . . . . . . . . . 5 69 3.2. General Operation . . . . . . . . . . . . . . . . . . . . 6 70 4. Message formats . . . . . . . . . . . . . . . . . . . . . . . 9 71 4.1. Extensions to Proxy Binding Update Message . . . . . . . . 9 72 4.2. Extensions to Proxy Binding Acknowledgment Message . . . . 10 73 4.3. Mobile Node Group Identifier Option . . . . . . . . . . . 10 74 4.4. Status Codes . . . . . . . . . . . . . . . . . . . . . . . 11 75 5. Protocol Considerations . . . . . . . . . . . . . . . . . . . 12 76 5.1. MAG Considerations . . . . . . . . . . . . . . . . . . . . 12 77 5.1.1. Extensions to Binding Update List Entry Data 78 Structure . . . . . . . . . . . . . . . . . . . . . . 12 79 5.1.2. Requesting Bulk Binding Update Support for a 80 Mobility Session . . . . . . . . . . . . . . . . . . . 12 81 5.1.3. Supporting Bulk Binding Updates . . . . . . . . . . . 14 82 5.2. LMA Considerations . . . . . . . . . . . . . . . . . . . . 15 83 5.2.1. Extensions to Binding Cache Entry Data Structure . . . 15 84 5.2.2. Enabling Bulk Binding Update Support for a 85 Mobility Session . . . . . . . . . . . . . . . . . . . 16 86 5.2.3. Supporting Bulk Binding Updates . . . . . . . . . . . 18 87 6. Protocol Configuration Variables . . . . . . . . . . . . . . . 19 88 6.1. Local Mobility Anchor - Configuration Variables . . . . . 19 89 6.2. Mobile Access Gateway - Configuration Variables . . . . . 20 90 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 91 8. Security Considerations . . . . . . . . . . . . . . . . . . . 21 92 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 21 93 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22 94 10.1. Normative References . . . . . . . . . . . . . . . . . . . 22 95 10.2. Informative References . . . . . . . . . . . . . . . . . . 22 97 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22 99 1. Introduction 101 The Proxy Mobile IPv6 base specification [RFC5213] requires the 102 Mobile Node Identifier option to be present in the mobility signaling 103 messages, such as in the Proxy Binding Update and Proxy Binding 104 Acknowledgement messages. It essentially limits the operational 105 scope of the binding update operation to a single mobility session. 106 These signaling messages lack the capability to identify a group of 107 mobility sessions, so the binding update and revocation related 108 operations can be performed on all the mobility sessions that are 109 part of that group. 111 There is a need to have semantics for associating a group identity to 112 a mobility session, so the scope of the binding update and revocation 113 related operations can be extended to all the mobility sessions 114 identified by the group identifier. The group identifier therefore 115 provides a considerably improved mechanism for protocol operations 116 which would otherwise require multiple atomic transactions on a per 117 mobility session basis. Following are some of the use-cases where 118 the group identifier can be used. 120 o For extending the lifetime of a mobility session, the mobile 121 access gateway periodically sends a Proxy Binding Update message 122 to the local mobility anchor on a per-session basis. This process 123 can be optimized by allowing the mobile access gateway to send a 124 single Proxy Binding Update [RFC5213] message for a group of 125 mobility sessions, identified by a group identifier. The local 126 mobility anchor upon accepting the request can update the lifetime 127 of all the mobility sessions that are part of that group. 129 o A local mobility anchor, or a mobile access gateway service hosted 130 on blade architecture system, on detecting a failure of a specific 131 service card, can potentially request the peer to revoke all the 132 sessions that are hosted on that service card, identified by a 133 common group identifier. Potentially, a single Binding Revocation 134 Request [RFC5846] message carrying the group identifier can be 135 used to revoke all the sessions hosted on that service card, which 136 otherwise needs to be handled on a per-session basis. 138 This document defines a new mobility option, Mobile Node Group 139 Identifier option, and the extensions to binding update and binding 140 revocation related procedures for performing binding operations with 141 group specific scope. 143 2. Conventions & Terminology 144 2.1. Conventions 146 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 147 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 148 document are to be interpreted as described in RFC 2119 [RFC2119]. 150 2.2. Terminology 152 All the mobility related terms used in this document are to be 153 interpreted as defined in the base Proxy Mobile IPv6 specifications 154 [RFC5213] and [RFC5844]. Additionally, this document uses the 155 following abbreviations: 157 Bulk Binding Update 159 A binding update operation that has group specific scope. A 160 binding operation is associated with a specific mobility session. 161 However, a Bulk binding update operation is associated with 162 multiple mobility sessions. This operation is not relevant for 163 new mobility session creation. 165 Bulk Binding Update Group 167 A group of mobility sessions that are part of the same logical 168 group and therefore share a common group identifier. This group 169 is the bulk binding update group. This bulk binding update group 170 is maintained by both the mobile access gateway and the local 171 mobility anchor, and the grouping logic is local to that node. A 172 mobility session therefore can be identified by two bulk binding 173 update group identifiers, one specific group created by the mobile 174 access gateway and the other specific group created by the local 175 mobility anchor. The bulk binding update group identifiers are 176 exchanged as part of the initial mobility session creation. The 177 mobility entities thereafter can perform binding update related 178 operations such as lifetime extension and revocation operations on 179 an entire bulk binding update group, identified by a group 180 identifier. 182 3. Bulk Binding Update Overview 184 3.1. Motivation 186 In a typical Proxy Mobile IPv6 domain, a local mobility anchor serves 187 multiple mobile access gateways and the capacity of that node with 188 respect to the number of mobility sessions that it can host is quite 189 high, typically in the order of few millions. As the number of 190 mobility sessions hosted by a local mobility anchor goes up, so is 191 the amount of signaling traffic related to periodic binding update 192 related traffic. 194 The currently specified approach of binding update procedure for 195 extending the lifetime, where the mobile access gateway is required 196 to send a unique binding update message for each mobility session, 197 even when there is no change to the session state is inefficient or 198 sub-optimal. These periodic binding update messages consume 199 significant amount of network resources, both in terms of processing 200 power and in terms of network bandwidth and at both the peers. There 201 is an opportunity to optimize the signaling procedures by allowing 202 the local mobility anchor and the mobile access gateway to perform 203 bulk binding update operations. This document specifies extensions 204 to Proxy Mobile IPv6 signaling for performing binding update and 205 revocation operations on a group of mobility sessions. These 206 extensions do not take away the existing functionality of performing 207 binding operations on a single mobility session. 209 3.2. General Operation 211 The bulk binding update mechanism specified in this document allows 212 the mobile access gateway and the local mobility anchor to perform 213 binding update and revocation operations on a group of mobility 214 sessions. As part of the initial signaling during mobility session 215 establishment, the local mobility anchor and the mobile access 216 gateway exchange the respective bulk binding update group identifiers 217 for that mobility session. Subsequently both the peers can perform 218 bulk operations on those groups by presenting the bulk binding update 219 group identifier in the signaling messages. 221 A mobile access gateway when sending a Proxy Binding Update message 222 after detecting a new mobile node on its access link, can request the 223 local mobility anchor to assign a bulk binding update group 224 identifier for the mobile node's mobility session. This is indicated 225 by setting the (B) flag in the Proxy Binding Update to a value of 226 (1). The mobile access gateway will also assign a bulk binding 227 update group identifier (or it may assign a default bulk binding 228 update group - ALL-Sessions) and include that in the Mobile Node 229 Group Identifier option. 231 The local mobility anchor upon accepting the request will group the 232 mobility session to a specific bulk binding update group (or it may 233 assign it to the default bulk binding update group - ALL-Sessions) 234 and return this bulk binding update group identifier in Proxy Binding 235 Acknowledgement message. It will also set the (B) flag in the Proxy 236 Binding Acknowledgement message to a value of (1). The bulk binding 237 update group identifier is carried in the Mobile Node Group 238 Identifier option, described in Section 4.3. 240 Once the bulk binding update group identifiers are exchanged, the 241 local mobility anchor and the mobile access gateway can perform 242 binding operations on those entire groups, by including the bulk 243 binding update group identifier in the signaling messages. For 244 example, the mobile access gateway can extend the lifetime of all the 245 mobility sessions that are part of a group by sending a single Proxy 246 Binding Update message with that bulk binding update group 247 identifier. Similarly, the local mobility anchor can revoke all the 248 mobility sessions that are part of a group, by including that group 249 identifier in the Proxy Binding Revocation message. 251 Figure 1 explains the operational sequence of the bulk binding update 252 and revocation operations on a group of mobile nodes, MN1, MN2 and 253 MN3. 255 MAG LMA 256 (1) | | 257 MN1-------| (2) PBU | 258 |--------------------------->| 259 | * (3) 260 | (4) PBA | 261 |<---------------------------| 262 * (5) | 263 (6) | | 264 MN2-------| | 265 * (7)........................| 266 (8) | | 267 MN3-------| | 268 * (9)........................| 269 | | 270 | (10) PBU | 271 |--------------------------->| 272 | * (11) 273 | (12) PBA | 274 |<---------------------------| 275 * (13) 276 | | 277 | (14) BRI | 278 |<---------------------------| 279 | * (15) 280 | (16) BRA | 281 |--------------------------->| 282 * (17) | 283 | | 285 Figure 1: Exchange of Group Identifier 287 o (1) to (2): MAG detects the mobile node's (MN1) attachment to the 288 access link. The MAG groups the mobile node to a specific bulk 289 binding update group, (M1). The MAG notifies this group 290 identifier to the LMA by including it in the Mobile Node Group 291 Identifier option of the PBU message. 293 o (3): The LMA upon accepting the PBU, creates a mobility session 294 and groups the mobility session to a specific bulk binding update 295 group, (L1). The LMA updates the mobile node's BCE entry to 296 include the bulk binding update group identifier, (L1) and the 297 bulk binding update group identifier presented by the MAG, (M1). 298 The LMA also notifies the MAG about the bulk binding update group 299 identifier (L1), by including it in the PBA. 301 o (4) to (5): The MAG upon receiving the PBA updates the BUL entry 302 for that mobility session to include the bulk binding update group 303 identifiers (L1) and (M1). At this point, both the LMA and MAG 304 are aware of the mobile node's bulk binding update group 305 identifiers assigned by the peers. 307 o (6) to (9): The above steps (1 through 5) are repeated here for 308 MN2 and MN3, details are omitted. At the end of step (9), the MAG 309 completes the signaling with the LMA. The MAG assigns the mobile 310 nodes, MN2 and MN3 to bulk binding update groups, M1 and M2 311 respectively, while the LMA assigns them both to the same to the 312 bulk binding update group, (L1). 314 o At this point, LMA has assigned MN1, MN2 and MN3 to the bulk 315 binding update group of (L1), while the MAG has assigned MN1 and 316 MN2 to the group (M1) and MN3 to group (M2). Both the peers can 317 now perform binding operations on a group of mobility sessions 318 identified by the respective bulk binding update group identifier. 320 o (10) to (13): The MAG sends a periodic binding update message for 321 extending the lifetime of all the mobility sessions that are part 322 of the bulk binding update group, (M1). It includes the bulk 323 binding update group identifier, (M1) in the PBU. The LMA upon 324 accepting the PBU, extends the lifetime of both MN1 and MN2, which 325 are part of the group (M1). 327 o (14) to (16): The LMA decides to revoke all the sessions that are 328 part of bulk binding update group, L1. The LMA sends a BRI 329 message with the bulk binding update group identifier, (L1). The 330 MAG upon accepting the BRI message revokes all the MN1, MN2 and 331 MN3 mobility sessions, which are part of that bulk binding update 332 group, (L1). 334 4. Message formats 336 This section identifies the extensions to Proxy Mobile IPv6 signaling 337 messages that are required for supporting this specification. 339 4.1. Extensions to Proxy Binding Update Message 341 0 1 2 3 342 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 344 | Sequence # | 345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 346 |A|H|L|K|M|R|P|F|T|B| Reserved | Lifetime | 347 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 348 | | 349 . . 350 . Mobility options . 351 . . 352 | | 353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 355 Figure 2 357 A new flag, Bulk-Binding-Update (B) flag is defined in the Proxy 358 Binding Update message specified in [RFC5213]. The bit-value of 359 Bulk-Binding-Update (B) flag in the flags field of the message will 360 be (IANA-1). 362 If the Bulk-Binding-Update flag (B) is set to a value of (1), it 363 informs the local mobility anchor to enable bulk binding update 364 support for the mobility session associated with this message. If 365 the (B) flag is set to a value of (0), the local mobility anchor MUST 366 exclude the mobility session associated with this message, from any 367 bulk binding related operations and any binding update, or binding 368 revocation operations with bulk specific scope will not be relevant 369 to that mobility session. 371 This flag is relevant only for Proxy Mobile IPv6 and therefore MUST 372 be set to value of (0), when the (P) flag is set to a value of (0). 374 All other fields in the Proxy Binding Update message and the mobility 375 options that can be carried in the message confirm to the respective 376 specifications. 378 4.2. Extensions to Proxy Binding Acknowledgment Message 380 0 1 2 3 381 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 382 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 383 | Status |K|R|P|T|B| Res.| 384 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 385 | Sequence # | Lifetime | 386 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 387 | | 388 . . 389 . Mobility options . 390 . . 391 | | 392 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 394 Figure 3: Proxy Binding Acknowledgment Message 396 A new flag, Bulk-Binding-Update (B) flag is defined in the Proxy 397 Binding Acknowledgment message specified in [RFC5213]. The bit-value 398 of Bulk-Binding-Update (B) flag in the flags field of the message is 399 (IANA-2). 401 If the Bulk-Binding-Update flag (B) is set to a value of (1), it 402 serves as an indication to the mobile access gateway that the local 403 mobility anchor has enabled bulk binding update support for the 404 mobility session associated with this message. The value of the flag 405 MUST be set to the value of (0), if the value of the (B) flag in the 406 Proxy Binding Update message that it received from the mobile access 407 gateway was set to a value of (0). 409 This flag is relevant only for Proxy Mobile IPv6 and therefore MUST 410 be set to value of (0), when the (P) flag is set to a value of (0). 412 All other fields in the Proxy Binding Acknowledgment message and the 413 mobility options that can be carried in the message conform to the 414 respective specifications. 416 4.3. Mobile Node Group Identifier Option 418 A new option, Mobile Node Group Identifier option is defined for 419 using it in Proxy Mobile IPv6 signaling messages exchanged between a 420 local mobility anchor and a mobile access gateway. This option is 421 used for carrying the mobile node's group identifier. There can be 422 multiple instances of this option in a given signaling message, 423 however, each of the instance SHOULD have a different sub-type value. 424 This option is a generic option and this specification uses only the 425 sub-type value of (1). 427 The type value for this option is (IANA-3). 429 0 1 2 3 430 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 431 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 432 | Type | Length | Sub-type | Reserved | 433 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 434 | Mobile Node Group Identifier | 435 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 437 Figure 4: Mobile Node Group Identifier Option 439 Type 440 <(IANA-3)> 442 Length 443 This is an 8-bit unsigned integer indicating the length in octets 444 of this option, excluding the type and length fields. The value 445 for this field MUST be set to a value of (6). 447 Sub-type 448 This 8-bit field identifies the specific mobile node's group type. 449 This number space will be managed by the IANA. The sub-type value 450 of (1) is reserved for Bulk Binding Update Group. 452 Reserved 453 This 8-bit field is unused for now. The value MUST be initialized 454 to (0) by the sender and MUST be ignored by the receiver. 456 Mobile Node Group Identifier This 32-bit field contains the mobile 457 node's group identifier. The value of (0) is reserved and SHOULD 458 NOT be used. The value of (1) ALL-SESSIONS, is the default group 459 of all mobility sessions established between a given local 460 mobility anchor and a mobile access gateway. 462 4.4. Status Codes 464 This document defines the following new Status codes values for use 465 in the Proxy Binding Acknowledgement message. These values are to be 466 allocated from the same numbering space, as defined in Section 6.1.8 467 of [RFC6275]. 469 INVALID_MOBILE_NODE_GROUP_IDENTIFIER: (IANA-5) 470 Invalid group identifier value in the request 472 5. Protocol Considerations 474 5.1. MAG Considerations 476 The following are the considerations relevant for the mobile access 477 gateway when supporting this specification. 479 5.1.1. Extensions to Binding Update List Entry Data Structure 481 The conceptual Binding Update List entry data structure maintained by 482 the mobile access gateway, described in Section 6.1 of [RFC5213], is 483 extended to include the following REQUIRED additional fields. 485 o MAG-Bulk-Binding-Update-Group-Id - It is the bulk binding update 486 group identifier assigned by this mobile access gateway for this 487 mobility session. This is a 32-bit unsigned integer. This 488 identifier is not globally unique within a Proxy Mobile IPv6 489 domain, the same group identifier value may be used by other 490 nodes. 492 o LMA-Bulk-Binding-Update-Group-Id - It is the bulk binding update 493 group identifier assigned by the local mobility anchor for this 494 mobility session. This is a 32-bit unsigned integer. This 495 identifier is received in the Mobile Node Group Identifier option 496 of the Proxy Binding Acknowledgement message. This identifier is 497 not globally unique within a Proxy Mobile IPv6 domain, the same 498 group identifier value may be used by other nodes. 500 5.1.2. Requesting Bulk Binding Update Support for a Mobility Session 502 The following are the considerations for the mobile access gateway 503 for requesting bulk binding update support for a mobility session." 505 o When sending a Proxy Binding Update message to the local mobility 506 anchor, the mobile access gateway can choose to request the local 507 mobility anchor to enable bulk binding update support for the 508 mobility session associated with that Proxy Binding Update 509 request. When making such request, the Bulk-Binding-Update flag 510 (B) in the request MUST be set to a value of (1) and the Mobile 511 Node Group Identifier option MUST be present. The decision to 512 request the bulk binding update support for a mobile node is a 513 matter of local policy at the mobile access gateway and is 514 controlled by the configuration variable, 515 RequestBulkBindingUpdateSupportForMobilitySession. 517 o The mobile access gateway MUST assign a bulk binding update group 518 identifier for the mobility session. Considerations on how the 519 mobile access gateway assigns a group identifier to a mobility 520 session is outside the scope of this document. This group 521 identifier can be unique to the service card on which the mobility 522 session is hosted, or based on other grouping considerations. 523 When there is no such group assignment is done, the mobile access 524 gateway SHOULD assign the default group identifier value of (ALL- 525 SESSIONS). This assigned group identifier value MUST be present 526 in the Mobile Node Group Identifier option and the the sub-type 527 value in the option MUST be set to value of (1) (bulk binding 528 update group). 530 o If the received Proxy Binding Acknowledgment message has the Bulk- 531 Binding-Update flag (B) in the reply set to a value of (0), this 532 is in response to a Proxy Binding Update request with the Bulk- 533 Binding-Update flag (B) set to a value of (1), it is an indication 534 that the local mobility anchor has denied the request for enabling 535 bulk binding update support for that mobility session and that the 536 mobility session is not associated with any bulk binding update 537 group. The mobile access gateway SHOULD set the bulk binding 538 update group identifier values, LMA-Bulk-Binding-Update-Group-Id 539 and MAG-Bulk-Binding-Update-Group-Id values to (0), in the Binding 540 Update List entry for that mobility session. Furthermore, the 541 mobility session should be excluded from any bulk binding update 542 operations. 544 o If the received Proxy Binding Acknowledgment message has the 545 status code value set to (0) (Proxy Binding Update accepted) and 546 the Bulk-Binding-Update flag (B) in the reply is set to a value of 547 (1), it is an indication that the local mobility anchor has 548 accepted the request to allow bulk binding update support for that 549 mobility session. Furthermore, the Mobile Node Group Identifier 550 option in the reply, with sub-type value of (1) (bulk binding 551 update group), contains the bulk binding update group identifier 552 for that mobility session assigned by the local mobility anchor. 553 The mobile access gateway MUST update the LMA-Bulk-Binding-Update- 554 Group-Id and MAG-Bulk-Binding-Update-Group-Id parameters in the 555 Binding Update List entry for that mobility session. However, if 556 the received Proxy Binding Acknowledgement message has the Bulk- 557 Binding-Update flag (B) set to a value of (1), but if the Mobile 558 Node Group Identifier option is not present, the message MUST be 559 considered as malformed and ignored. 561 o At any point of time, the mobile access gateway chooses to request 562 the local mobility anchor to disable bulk binding update support 563 for a mobility session, it MUST send a Proxy Binding Update 564 message with the (B) flag set to a value of (0) and the Mobile 565 Node Group Identifier option MUST NOT be present. This message is 566 sent as a normal binding update request for lifetime extension. 567 Requirements from section 6.9.1 [RFC5213] apply. Furthermore, the 568 mobile access gateway MUST update Binding Update List entry, by 569 setting the bulk binding update group identifier values, LMA-Bulk- 570 Binding-Update-Group-Id and MAG-Bulk-Binding-Update-Group-Id 571 values to (0) and the mobility session MUST be excluded from any 572 bulk binding update operations. 574 5.1.3. Supporting Bulk Binding Updates 576 The following section identifies the considerations for mobile access 577 gateway for performing binding update and revocation operations with 578 group specific scope. 580 o For extending the lifetime of all mobility sessions that share the 581 same bulk binding update group identifier, the mobile access 582 gateway can choose to send a Bulk binding update request. For 583 making such request, it can send a Proxy Binding Update message to 584 the local mobility anchor, including the Mobile Node Group 585 Identifier option with sub-type value of (1) (bulk binding update 586 group), and with the Bulk-Binding-Update flag (B) set to a value 587 of (0). The identifier value in the option MUST be set to the 588 bulk binding update group identifier of the group for which bulk 589 binding update operation is being requested. The message MUST NOT 590 include any individual session identifiers such as, Mobile Node 591 Identifier option [RFC4283], Home Network Prefix option [RFC5213], 592 the IPv4 Home Address Request option [RFC5844], or the GRE Key 593 option [RFC5845]. All the Considerations from section 5.3.3 594 [RFC5213] MUST be followed when sending the bulk binding update 595 request, with the exception related to the use of Mobile Node 596 Group Identifier option in place of the individual session 597 identifiers (Mobile Node Identifier option, Home Network Prefix 598 option, GRE Key option, IPv4 Home Address Address Request option). 600 o When requesting binding revocation for all the sessions that share 601 the same bulk binding update group identifier, the mobile access 602 gateway can choose to send a bulk revocation request. For making 603 such request, it can send a Binding Revocation Indication message 604 [RFC5846] to the local mobility anchor, including the Mobile Node 605 Group Identifier option, with sub-type value of (1) (bulk binding 606 update group). The identifier value in the option MUST be set to 607 the bulk binding update group identifier of the group for which 608 bulk binding update operation is being requested. The message 609 MUST NOT include any individual session identifiers such as, 610 Mobile Node Identifier option [RFC4283], Home Network Prefix 611 option [RFC5213], the IPv4 Home Address Request option [RFC5844] 612 or the GRE Key option [RFC5845]. All the Considerations from 613 section 9.2 [RFC5846] MUST be followed when sending the bulk 614 binding update request, with the exception related to the use of 615 Mobile Node Group Identifier option in place of the individual 616 session identifiers (Mobile Node Identifier option, Home Network 617 Prefix option, GRE Key option, IPv4 Home Address Address Request 618 option). 620 o Any time the mobile access gateway receives a Binding Revocation 621 Indication message [RFC5846], with a Mobile Node Group Identifier 622 option present in the request and with sub-type value of (1) (bulk 623 binding update group), this message serves as a bulk revocation 624 request, with the request scope for revoking of all the mobility 625 sessions that are part of that bulk binding update group specific 626 to that local mobility anchor, and identified by the group 627 identifier in Mobile Node Group Identifier option. 629 o All the considerations from [RFC5846] apply when processing 630 binding revocation request, except making the scope of the 631 operation apply to a set of mobility sessions identified by the 632 bulk binding update group identifier present in the request. 634 o If the received Binding Revocation Indication message includes a 635 Mobile Node Identifier option [RFC4283], Home Network Prefix 636 option [RFC5213], the IPv4 Home Address Request option [RFC5844], 637 or the GRE Key Option [RFC5845], the mobile access gateway MUST 638 consider this as an invalid message; it MUST reject the Binding 639 Revocation Indication message and send a Binding Revocation 640 Acknowledgement message with the Status field set to a value of 641 128 (Binding Does NOT Exist). 643 5.2. LMA Considerations 645 The following are the considerations relevant for local mobility 646 anchor when supporting this specification. 648 5.2.1. Extensions to Binding Cache Entry Data Structure 650 The conceptual Binding Cache entry data structure maintained by the 651 local mobility anchor, described in Section 5.1 of [RFC5213], is 652 extended to include the following REQUIRED additional fields. 654 o MAG-Bulk-Binding-Update-Group-Id - It is the bulk binding update 655 group identifier assigned by the mobile access gateway for this 656 mobility session. This is a 32-bit unsigned integer. This 657 identifier is received in the Mobile Node Group Identifier option 658 of the Proxy Binding Acknowledgement message. This identifier is 659 not globally unique within a Proxy Mobile IPv6 domain, the same 660 group identifier value may be used by other nodes. 662 o LMA-Bulk-Binding-Update-Group-Id - It is the bulk binding update 663 group identifier assigned by this local mobility anchor for this 664 mobility session. This is a 32-bit unsigned integer. This 665 identifier is not globally unique within a Proxy Mobile IPv6 666 domain, the same group identifier value may be used by other 667 nodes. 669 5.2.2. Enabling Bulk Binding Update Support for a Mobility Session 671 The local mobility anchor will process a received Proxy Binding 672 Update message as specified in [RFC5213]. However, if the (B) flag 673 in the received Proxy Binding Update message is set to a value of (1) 674 and if it includes a Mobile Node Group Identifier option with sub- 675 type value of (1) (bulk binding update group), following processing 676 takes place: 678 o If the (B) flag in the received Proxy Binding Update message is 679 set to a value of (1) and with the Mobile Node Group Identifier 680 option present in the request, the message serves as a request to 681 the local mobility anchor to enable bulk binding update support 682 for that mobility session. 684 o Upon successful processing and acceptance of the Proxy Binding 685 Update, the local mobility anchor can choose to enable bulk 686 binding update support for this mobility session. The decision 687 whether to enable bulk binding update support for that mobility 688 session is a matter of local policy and is controlled by the 689 configuration variable, AcceptBulkBindingUpdateReqMobilitySession. 691 o For enabling the bulk binding update support for the mobility 692 session, the local mobility anchor MUST associate the mobility 693 session to a specific bulk binding update group locally. The 694 specific details on how the local mobility anchor associates the 695 given mobility session to a specific bulk binding update group is 696 outside the scope of this document. The local mobility anchor can 697 choose to assign a default bulk binding update group identifier 698 value of (ALL-SESSIONS), indicating that all the mobility sessions 699 from that mobile access gateway are part of that group. The local 700 mobility anchor SHOULD update the bulk binding update group 701 identifier values in the Binding Cache entry, LMA-Bulk-Binding- 702 Update-Group-Id and MAG-Bulk-Binding-Update-Group-Id to the 703 respective values. 705 o If the bulk binding update support is enabled for the mobile 706 node's mobility session, the local mobility anchor MUST send the 707 assigned bulk binding update group identifier as part of the 708 Mobile Node Group Identifier option, with sub-type value of (1) 709 (bulk binding update group) in the Proxy Binding Acknowledgment 710 message that it sends to the mobile access gateway. The (B) flag 711 in the Proxy Binding Acknowledgment message MUST be set to value 712 of (1). 714 o If the bulk binding update support is not enabled for the mobility 715 session, the local mobility anchor MUST NOT include the Mobile 716 Node Group Identifier option with a sub-type value of (1) (bulk 717 binding update group), in the Proxy Binding Acknowledgment message 718 that it sends to the mobile access gateway. Furthermore, the (B) 719 flag in the Proxy Binding Acknowledgment message MUST be set to 720 value of (0). It is to be noted that the Mobile Node Group 721 Identifier option is a generic option and new sub-types may be 722 defined by future specifications. 724 o If the received Proxy Binding Update message is not a bulk binding 725 update request, (i.e., the (B) flag is set to a value of (0) and 726 the Mobile Node Group Identifier option with sub-type value of (1) 727 (bulk binding update group) is not present), but is a request for 728 extending the lifetime of an existing mobility session, for which 729 the bulk binding update support is already enabled, then the local 730 mobility anchor MUST process the request as specified in 731 [RFC5213]. However, the value of (0) in the (B) flag in the 732 message serves as a request for the local mobility anchor to 733 disable bulk binding update support for that mobility session. 734 Upon accepting the request, the local mobility anchor SHOULD set 735 the parameters, LMA-Bulk-Binding-Update-Group-Id and MAG-Bulk- 736 Binding-Update-Group-Id in the Binding Cache entry to a value of 737 (0) and the mobility session MUST be excluded from any bulk 738 binding update operations. 740 o Any time the local mobility anchor detects that the mobile node 741 has roamed and changed its point of attachment to a new mobile 742 access gateway, it SHOULD also update the bulk binding update 743 group identifier of the mobility session. Additionally, it should 744 also update the existing group identifiers associated with that 745 session. As part of sending the Proxy Binding Acknowledgment to 746 the new mobile access gateway, it MUST include the updated group 747 identifier in the Mobile Node Group identifier option, with a sub- 748 type value of (1). However, if the if the received Proxy Binding 749 Update from the new mobile access gateway did not have the (B) 750 flag set to a value of (1), then it MUST NOT include the mobility 751 session in any of bulk binding update group and MUST NOT include 752 the Mobile Node Group identifier option with the sub-type value of 753 (1). 755 o Any time a mobile node's mobility session is de-registered by the 756 mobile access gateway, or the session is revoked for 757 administrative or any other reasons, the mobility session MUST 758 also be removed from the bulk binding update group. 760 5.2.3. Supporting Bulk Binding Updates 762 The following section identifies the considerations for local 763 mobility anchor for performing bulk binding update and revocation 764 operations with group specific scope. 766 o Any time the local mobility anchor receives a Proxy Binding Update 767 message with the (B) flag in the request is set to a value of (0) 768 and if a Mobile Node Group Identifier option present in the 769 request and with sub-type value of (1) (bulk binding update 770 group), the local mobility anchor MUST consider the request as a 771 bulk binding update request, with the request scope for all the 772 mobility sessions that are part of that bulk binding update group, 773 specific to that mobile access gateway, and identified by the 774 group identifier in Mobile Node Group Identifier option. However, 775 if the received request also includes any individual session 776 identifiers such as, Mobile Node Identifier option [RFC4283], Home 777 Network Prefix option [RFC5213], the IPv4 Home Address Request 778 option [RFC5844], or the GRE Key option [RFC5845] the local 779 mobility anchor MUST consider this as an invalid message; it MUST 780 reject the Proxy Binding Update message and send a Proxy Binding 781 Acknowledgement message with the Status field set to 782 INVALID_MOBILE_NODE_GROUP_IDENTIFIER (Invalid group identifier 783 value in the request). 785 o The local mobility anchor MUST consider the message as a request 786 for extending the lifetime of all the mobility sessions that are 787 associated to each of group identifier from the Mobile Node Group 788 Identifier option. However, if the Mobile Node Group Identifier 789 option, with sub-type value of (1) (bulk binding update group), 790 has an unknown group identifier, then the local mobility anchor 791 MUST reject the Proxy Binding Update message and send a Proxy 792 Binding Acknowledgement message with the Status field set to 793 INVALID_MOBILE_NODE_GROUP_IDENTIFIER (Invalid group identifier 794 value in the request). 796 o Upon accepting the bulk binding update request, the local mobility 797 anchor SHOULD extend the lifetime for all the mobility sessions 798 that are part of bulk binding update group identified by the group 799 identifier in the Mobile Node Group Identifier in the message. 800 Considerations from [RFC5213] MUST be applied for extending the 801 lifetime of a mobile node's session. It MUST also send a Proxy 802 Binding Acknowledgment message with the Status field value set to 803 0 (Proxy Binding Update accepted). The lifetime field in the 804 message MUST be set to the allocated lifetime for all the mobility 805 sessions. The message MUST also include the Mobile Node Group 806 Identifier option, with sub-type value of (1) (bulk binding update 807 group), with the identifier value copied from the Mobile Node 808 Group Identifier option present in the received Proxy Binding 809 Update message. 811 o If the local mobility anchor rejects the bulk binding update 812 request for any administrative reason, then it MUST NOT update the 813 lifetime in the binding cache entries of any of the mobile nodes 814 identified by the group identifier. The local mobility anchor 815 SHOULD send a Proxy Binding Acknowledgment indicating the reason 816 for the rejection in the status code. 818 o Any time the local mobility anchor receives a Binding Revocation 819 Indication Message [RFC5846], with a Mobile Node Group Identifier 820 option present in the request and with sub-type value of (1) (bulk 821 binding update group), the local mobility anchor MUST consider the 822 request as a bulk revocation request, with the request scope 823 including all the mobility sessions that are part of that bulk 824 binding update group, specific to that mobile access gateway, and 825 identified by the group identifier in Mobile Node Group Identifier 826 option. However, if the received request also includes a Mobile 827 Node Identifier option [RFC4283], Home Network Prefix option 828 [RFC5213], the IPv4 Home Address Request option [RFC5844], or the 829 GRE Key Option [RFC5845], the local mobility anchor MUST consider 830 this as an invalid message; it MUST reject the Binding Revocation 831 Indication message and send a Binding Revocation Acknowledgement 832 message with the Status field set to a value of 128 (Binding Does 833 NOT Exist). All the considerations from [RFC5846] apply when 834 processing binding revocation request, except making the scope of 835 the operation apply to a set of mobility sessions identified by 836 the group identifier present in the request. 838 o Upon accepting the Binding Revocation Indication request and 839 completing the operation, the local mobility anchor MUST send a 840 Binding Revocation Acknowledgement message with the Status field 841 set to a value of 0 (success). The message MUST include the 842 Mobile Node Group Identifier option, with the identifier value 843 copied from the Mobile Node Group Identifier option present in the 844 received Binding Revocation Indication message. 846 6. Protocol Configuration Variables 848 6.1. Local Mobility Anchor - Configuration Variables 850 This specification adds a new configuration variable for the local 851 mobility anchor. The configured value for this variable is expected 852 to survive server reboots and service restarts. 854 AcceptBulkBindingUpdateReqMobilitySession 856 This flag indicates whether or not the local mobility anchor will 857 accept the request from the mobile access gateway to enable bulk 858 binding update support for the mobility session. The default 859 value for this flag is set to (1), indicating that it will accept 860 the request from the mobile access gateway. If the value of the 861 flag is set to (0), the local mobility anchor will deny the 862 request. 864 6.2. Mobile Access Gateway - Configuration Variables 866 This specification adds a new configuration variable for the mobile 867 access gateway. The configured value for this variable is expected 868 to survive server reboots and service restarts. 870 RequestBulkBindingUpdateSupportForMobilitySession 872 This flag indicates whether or not the mobile access gateway will 873 request the local mobility anchor to enable bulk binding update 874 support for the mobility session. The default value for this flag 875 is set to (1), indicating that the the mobile access gateway will 876 set the bulk binding update flag (B) in the Proxy Binding Update 877 request to a value of (1). If the flag is set to a value of (0), 878 the mobile access gateway will set the bulk binding update flag 879 (B) in the Proxy Binding Update to a value of (0). 881 7. IANA Considerations 883 This document requires the following five IANA actions. 885 o Action-1: This specification defines a new flag (B) to the Proxy 886 Binding Update message, specified in [RFC5213]. This flag is 887 described in Section 4.1. The value of the flag (B) needs to be 888 allocated from the Binding Update Flags registry. 890 o Action-2: This specification defines a new flag (B) to the Proxy 891 Binding Acknowledgment message, specified in [RFC5213]. This flag 892 is described in Section 4.2. The value of the flag (B) needs to 893 be allocated from the Binding Acknowledgment Flags registry. 895 o Action-3: This specification defines a new Mobility Header option, 896 the Mobile Node Group Identifier option. This option is described 897 in Section 4.3. The Type value for this option needs to be 898 assigned from the same numbering space as allocated for the other 899 mobility options [RFC6275]. 901 o Action-4: The Sub-type field of the Mobile Node Group Identifier 902 option introduces a new number space. This number space needs to 903 be managed by IANA, under the Registry, Mobile Node Group 904 Identifier Type Registry. This specification reserves the sub- 905 type value of (1) (Bulk Binding Update Group). Approval of new 906 sub-type values are to be made through IANA Expert Review. The 907 value range of this field is 0 through 255, but the values 0 and 908 255 are marked as reserved. The remaining values 2-254 are 909 available for allocation. 911 o Action-5: This document also defines a new status value 912 INVALID_MOBILE_NODE_GROUP_IDENTIFIER (Invalid group identifier 913 value in the request: IANA-5) for use in Proxy Binding 914 Acknowledgement message, as described in Section 4.4. This value 915 is to be assigned from the same number space as allocated for 916 other Status codes [RFC6275]. The allocated value has to be 917 greater than 128. 919 8. Security Considerations 921 The Mobile Node Group Identifier option defined in this specification 922 is for use in Proxy Binding Update and Proxy Binding Acknowledgement 923 messages. This option is carried like any other mobility header 924 option and it does not require any other special security 925 considerations. 927 The bulk binding update and the bulk revocation operations specified 928 in this document, perform operations on a group of mobility sessions. 929 If proper authorization checks are not in place, a malicious node may 930 be able to hijack a mobile node's mobility session or may carry out a 931 denial- of-service attack. To prevent this attack, this 932 specification requires the local mobility anchor to allow only 933 authorized mobile access gateways to perform bulk operations. 935 9. Acknowledgements 937 The authors would like to specially thank Jouni Korhonen, Basavaraj 938 Patil, Carlos Jesus Bernardos Cano, Dirk Von-Hugo, Pete Resnick, and 939 Jari Arkko for their reviews and inputs to this document. 941 10. References 942 10.1. Normative References 944 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 945 Requirement Levels", BCP 14, RFC 2119, March 1997. 947 [RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., 948 and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008. 950 [RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy 951 Mobile IPv6", RFC 5844, May 2010. 953 [RFC5846] Muhanna, A., Khalil, M., Gundavelli, S., Chowdhury, K., 954 and P. Yegani, "Binding Revocation for IPv6 Mobility", 955 RFC 5846, June 2010. 957 [RFC6275] Perkins, C., Johnson, D., and J. Arkko, "Mobility Support 958 in IPv6", RFC 6275, July 2011. 960 10.2. Informative References 962 [RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. 963 Chowdhury, "Mobile Node Identifier Option for Mobile IPv6 964 (MIPv6)", RFC 4283, November 2005. 966 [RFC5845] Muhanna, A., Khalil, M., Gundavelli, S., and K. Leung, 967 "Generic Routing Encapsulation (GRE) Key Option for Proxy 968 Mobile IPv6", RFC 5845, June 2010. 970 Authors' Addresses 972 Fuad Abinader (editor) 973 Instituto Nokia de Tecnologia 974 Av. Torquato Tapajos, 7200 - Km. 12 - Col Terra Nova 975 Manaus, AM 69048-660 976 BRAZIL 978 Email: fabinader@gmail.com 979 Sri Gundavelli (editor) 980 Cisco 981 170 West Tasman Drive 982 San Jose, CA 95134 983 USA 985 Phone: 986 Fax: 987 Email: sgundave@cisco.com 988 URI: 990 Kent Leung 991 Cisco 992 170 West Tasman Drive 993 San Jose, CA 95134 994 USA 996 Phone: 997 Fax: 998 Email: kleung@cisco.com 999 URI: 1001 Suresh Krishnan 1002 Ericsson 1003 8400 Decarie Blvd. 1004 Town of Mount Royal, QC 1005 Canada 1007 Phone: +1 514 345 7900 x42871 1008 Fax: 1009 Email: suresh.krishnan@ericsson.com 1010 URI: 1012 Domagoj Premec 1013 Unaffiliated 1015 Email: domagoj.premec@gmail.com