idnits 2.17.00 (12 Aug 2021) /tmp/idnits39028/draft-ietf-dmm-lma-controlled-mag-params-05.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 (May 31, 2017) is 1809 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 informational reference (is this intentional?): RFC 2460 (Obsoleted by RFC 8200) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DMM WG D. Patki 3 Internet-Draft S. Gundavelli 4 Intended status: Standards Track Cisco 5 Expires: December 2, 2017 J. Lee 6 Sangmyung University 7 Q. Fu 8 China Mobile 9 L. Bertz 10 Sprint 11 May 31, 2017 13 LMA Controlled MAG Session Parameters 14 draft-ietf-dmm-lma-controlled-mag-params-05.txt 16 Abstract 18 This specification defines a new extension, LMA-Controlled-MAG- 19 Session-Params to Proxy Mobile IPv6. This option can be used by the 20 local mobility anchor in Proxy Mobile IPv6 signaling for notifying 21 the mobile access gateway to conform to various configuration 22 parameters such as heartbeat parameters and binding refresh 23 parameters. 25 Status of this Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on December 2, 2017. 42 Copyright Notice 44 Copyright (c) 2017 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 3 61 2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3 62 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 63 3. Protocol Extension . . . . . . . . . . . . . . . . . . . . . . 3 64 3.1. Format of the LCMP Sub-Options . . . . . . . . . . . . . . 4 65 3.1.1. Binding Re-registration Control Sub-Option . . . . . . 5 66 3.1.2. Heartbeat Control Sub-Option . . . . . . . . . . . . . 6 67 4. Protocol Configuration Variables . . . . . . . . . . . . . . . 7 68 4.1. Local Mobility Anchor - Configuration Variables . . . . . 7 69 5. Protocol Considerations . . . . . . . . . . . . . . . . . . . 8 70 5.1. Local Mobility Anchor Considerations . . . . . . . . . . . 9 71 5.2. Mobile Access Gateway Considerations . . . . . . . . . . . 10 72 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 73 7. Security Considerations . . . . . . . . . . . . . . . . . . . 11 74 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11 75 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 76 9.1. Normative References . . . . . . . . . . . . . . . . . . . 11 77 9.2. Informative References . . . . . . . . . . . . . . . . . . 11 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 80 1. Introduction 82 A large Proxy Mobile IPv6 (PMIPv6) [RFC5213] deployment, such as 83 residential deployment, can have tens of thousands of mobile access 84 gateways (MAG) spread across geographical locations. While it can be 85 operationally challenging to manage such a large number of MAGs, it 86 can also be very difficult to ensure configuration consistency across 87 all the MAGs if they are not centrally managed. Configuring 88 aggressive values of parameters such as re-registration timeout and 89 heartbeat interval can potentially create considerable signaling load 90 on the local mobility anchor (LMA). This document provides a new 91 option to enable the LMA to control various parameters on the MAG 92 such as the re-registration frequency [RFC5213] and heartbeat 93 frequency [RFC5847]. With this option, the configuration of these 94 tunable parameters done centrally on the LMA enables Service 95 Providers to have better control on the behavior of the MAGs with 96 deterministic signaling load on the LMA. 98 2. Conventions and Terminology 100 2.1. Conventions 102 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 103 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 104 document are to be interpreted as described in [RFC2119]. 106 2.2. Terminology 108 All the terms used in this document are to be interpreted as defined 109 in [RFC5213], [RFC5847] and [RFC7563]. 111 3. Protocol Extension 113 The LMA Controlled MAG Parameters (LCMP) option is a mobility header 114 option used to exchange information related to the parameters that a 115 LMA enforces on a MAG. The option can be included in Proxy Binding 116 Acknowledge (PBA) message only, and there MUST NOT be more than a 117 single instance of this mobility option in the PBA message. This 118 mobility option MUST contain one or more LCMP sub-options. The sub- 119 options are defined in Section 3.1. The LCMP option has an alignment 120 requirement of 4n+2 [RFC2460]. 122 0 1 2 3 123 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 124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 125 | Type | Length | 126 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 127 | LCMP Sub-option(s) ~ 128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 130 Figure 1: LMA Controlled MAG Parameters Option 132 Type 134 MUST be set to the value of IANA-1, indicating that it is a LMA- 135 Controlled-MAG-Parameters option. 137 Length 139 8-bit unsigned integer indicating the length in octets of the 140 option, excluding the Type and Length fields. 142 LCMP Sub-option(s) 144 LCMP Sub-options are described in the below sections. The sub- 145 options can be present in any order. Inclusion of any specifc 146 sub-option is optional, but at least one sub-option MUST be 147 present. 149 3.1. Format of the LCMP Sub-Options 151 The LCMP sub-options are used for carrying information elements 152 related to various parameters that need to be configured on the MAG. 153 These sub-options can be included in the LCMP option defined in 154 Section 3. The LCMP sub-options have an alignment requirement of 4n. 155 The format of this sub-option is as follows. 157 0 1 2 3 158 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 159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 | LCMP Type | LCMP Length | Sub-Option Data ~ 161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 163 Figure 2: LMA Controlled MAG Parameters Sub-Option 165 Type 167 8-bit unsigned integer indicating the type of the LCMP sub-option. 168 This specification defines the following types: 170 0 - Reserved 172 1 - Binding Re-registration Control Sub-Option 174 2 - Heartbeat Control Sub-Option 176 Length 178 8-bit unsigned integer indicating the number of octets needed to 179 encode the Option Data, excluding the LCMP Type and LCMP Length 180 fields of the sub-option. 182 3.1.1. Binding Re-registration Control Sub-Option 184 The Binding Re-registration Control Sub-Option is a mobility sub- 185 option carried in the LCMP mobility option defined in Section 3.1. 186 This sub-option carries re-registration related timer values. There 187 MUST be no more than a single instance of this sub-option in LCMP 188 option. The format of this sub-option is defined below. 190 0 1 2 3 191 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 192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 193 | LCMP Type = 1 | LCMP Length | Re-registration-Start-Time | 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 | Initial-Retransmission-Time | Maximum-Retransmission-Time | 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 198 Figure 3: Binding Re-registration Control Sub-Option 200 LCMP Type 202 1 for Binding Re-registration Control Sub-Option 204 LCMP Length 206 6 208 Re-registration-Start-Time 210 16-bit unsigned integer indicating the number of time units before 211 the expiry of the PMIPv6 binding lifetime when the registration 212 refresh process needs to be activated. One time unit is 4 213 seconds. 215 Initial-Retransmission-Time 217 16-bit unsigned integer indicating minimum delay in seconds before 218 the first Proxy Binding Update (PBU) retransmission of the 219 exponential back-off process. 221 Maximum-Retransmission-Time 223 16-bit unsigned integer indicating maximum delay in seconds before 224 the last PBU retransmission message of the exponential back-off 225 process. 227 3.1.2. Heartbeat Control Sub-Option 229 0 1 2 3 230 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 231 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 232 | LCMP Type = 2 | LCMP Length | HB-Interval | 233 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 234 | HB-Retransmission-Delay | HB-Max-Retransmissions | 235 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 237 Figure 4: Heartbeat Control Sub-Option 239 LCMP Type 241 2 for Heartbeat Control Sub-Option 243 LCMP Length 245 6 247 HB-Interval 249 16-bit unsigned integer indicating heartbeat interval, i.e. time 250 delay in seconds after a successful heartbeat exchange (heartbeat 251 request followed by response) when the next heartbeat exchange can 252 be triggered. 254 HB-Retransmission-Delay 256 16-bit unsigned integer indicating minimum time delay in seconds 257 before a heartbeat message is retransmitted. 259 HB-Max-Retransmissions 261 16-bit unsigned integer indicating maximum number of heartbeat 262 retransmissions. 264 4. Protocol Configuration Variables 266 4.1. Local Mobility Anchor - Configuration Variables 268 This specification defines the following variables to be configured 269 by the system management. The configured values for these protocol 270 variables MUST survive server reboots and service restarts. 272 EnableLCMPSubOptReregControl 274 This flag indicates the operational state of the Binding Re- 275 registration Control sub-option support. The default value of 276 this flag is (0), indicating that support for the Binding Re- 277 registration Control sub-option is disabled. 279 EnableLCMPSubOptHeartbeatControl 281 This flag indicates the operational state of the Heartbeat Control 282 sub-option support. The default value of this flag is (0), 283 indicating that support for the Heartbeat Control sub-option is 284 disabled. 286 The following variables MAY be defined at various granularities such 287 as per binding, per cluster of bindings, per peering MAG, per cluster 288 of peering MAGs or any other custom grouping. Regardless of the 289 granularity of this configuration, the LMA MUST be able to determine 290 the value of these variables for every individual binding. 292 LCMPReregistrationStartTime 294 This variable is used to set the minimum time interval in number 295 of seconds before the expiry of the PMIPv6 binding lifetime when 296 the registration refresh process SHOULD be activated. The default 297 value of this variable is 10 units, where each unit is 4 seconds. 299 LCMPInitialRetransmissionTime 301 This variable is used to set the minimum delay in seconds before 302 the first PBU retransmission of the exponential back-off process. 303 This variable is same as INITIAL_BINDACK_TIMEOUT mentioned in 304 Section 6.9.4 of [RFC5213]. The default value of this variable is 305 1 second. 307 LCMPMaximumRetransmissionTime 309 This variable is used to set the maximum delay in seconds before 310 the last PBU retransmission message of the exponential back-off 311 process. This variable is same as MAX_BINDACK_TIMEOUT mentioned 312 in Section 6.9.4 of [RFC5213]. The default value of this variable 313 is 32 seconds. 315 LCMPHeartbeatInterval 317 This variable is used to set the time delay in seconds after a 318 successful heartbeat exchange (heartbeat request followed by 319 response) when the next heartbeat exchange can be triggered. The 320 default value of this variable is 60 seconds. The time delay 321 SHOULD NOT be less than 30 seconds or more than 3600 seconds. The 322 value of this variable MAY be derived from the variable 323 HEARTBEAT_INTERVAL defined in Section 5 of [RFC5847] if configured 324 on the LMA. 326 LCMPHeartbeatRetransmissionDelay 328 This variable is used to set the minimum time delay in seconds 329 before a heartbeat message is retransmitted. The value of this 330 variable SHOULD be less than LCMPHeartbeatInterval. The default 331 value of this variable is 5 seconds. 333 LCMPHeartbeatMaxRetransmissions 335 This variable is used to set the maximum number of heartbeat 336 retransmissions. The default value of this variable is 3. The 337 value of this variable MAY be derived from the variable 338 MISSING_HEARTBEATS_ALLOWED defined in Section 5 of [RFC5847] if 339 configured on the LMA. 341 5. Protocol Considerations 343 The following considerations apply to the LMA and the MAG. 345 For supporting this extension, the conceptual Binding Cache Entry 346 data structure maintained by the LMA, described in Section 5.1 of 347 [RFC5213] and the conceptual Binding Update List entry data structure 348 maintained by the MAG, described in Section 6.1 of [RFC5213], need to 349 be extended to store the LCMP option related information elements 350 defined below. 352 o LCMPReregistrationStartTime 354 o LCMPInitialRetransmissionTime 356 o LCMPMaximumRetransmissionTime 358 o LCMPHeartbeatInterval 360 o LCMPHeartbeatRetransmissionDelay 362 o LCMPHeartbeatMaxRetransmissions 364 5.1. Local Mobility Anchor Considerations 366 On receiving a PBU message [RFC5213] from a MAG, the LMA MUST check 367 if the variable EnableLCMPSubOptReregControl is configured and set to 368 (1). If yes, and if all of LCMPReregistrationStartTime, 369 LCMPInitialRetransmissionTime and LCMPMaximumRetransmissionTime are 370 set to NON_ZERO values, then it MUST include Binding Re-registration 371 Control Sub-Option in the LCMP mobility option which is in turn 372 included in the PBA message. If the variable 373 EnableLCMPSubOptReregControl is configured and set to (1) and if any 374 of LCMPReregistrationStartTime, LCMPInitialRetransmissionTime and 375 LCMPMaximumRetransmissionTime is set to ZERO value, then the LMA MUST 376 report a configuration error and reject the binding request by 377 sending a PBA message with status code '128-Reason Unspecified' 378 [RFC5213]. 380 The LMA MUST also check if variable EnableLCMPSubOptHeartbeatControl 381 is configured and set to (1). If yes, and if all of 382 LCMPHeartbeatInterval, LCMPHeartbeatRetransmissionDelay and 383 LCMPHeartbeatMaxRetransmissions are set to NON_ZERO values, then it 384 MUST include Heartbeat Control Sub-Option in the LCMP mobility option 385 which is in turn included in the PBA message. If the variable 386 EnableLCMPSubOptHeartbeatControl is set to (1) and if any of 387 LCMPHeartbeatInterval, LCMPHeartbeatRetransmissionDelay and 388 LCMPHeartbeatMaxRetransmissions is set to ZERO value, then the LMA 389 MUST report a configuration error and reject the binding request by 390 sending a PBA message with status code '128-Reason Unspecified' 391 [RFC5213]. 393 5.2. Mobile Access Gateway Considerations 395 If the PBA message [RFC5213] received from the LMA contains the LCMP 396 mobility option and the Binding Re-registration Control Sub-Option, 397 then the MAG MUST overwrite the binding re-registration related timer 398 parameters configured locally on the MAG with the parameters received 399 in Binding Re-registration Control Sub-Option. If any of the 400 parameters in the Binding Re-registration Control Sub-Option is ZERO, 401 then the PBA message MUST be ignored and an error message SHOULD be 402 logged. 404 Similarly, if the LCMP mobility option contains the Heartbeat Control 405 Sub-Option, then the MAG MUST overwrite the heartbeat related timer 406 parameters configured locally on the MAG with the parameters received 407 in the Heartbeat Control Sub-Option. If any of the parameters in the 408 Heartbeat Control Sub-Option except HB-Retransmission-Delay is ZERO, 409 then the PBA message MUST be ignored and error message SHOULD be 410 logged. 412 6. IANA Considerations 414 This document requires the following IANA actions in the "Mobile IPv6 415 Parameters" registry. 417 o Action 1: This specification defines a new mobility header option, 418 "LMA Controlled MAG Parameters". This mobility option is 419 described in Section 3. The type value (IANA-1) for this option 420 needs to be assigned from the same numbering space as allocated 421 for the other mobility options, as defined in [RFC6275]. 423 o Action 2: This specification defines a new mobility sub-option 424 format, the LCMP Parameters sub-option. The format of this 425 mobility sub-option is described in Section 3.1. This sub-option 426 can be carried in the LCMP Parameters option. The type value for 427 this sub-option needs to be managed by IANA, under the registry 428 "LMA Controlled MAG Parameters Sub-Option Type Values". This 429 specification reserves the following type values. Approval of new 430 LCMP Parameters sub-option type values are to be made through IANA 431 Expert Review. 433 +---+-----------------------------------------------------+ 434 | 0 | Reserved | 435 +---+-----------------------------------------------------+ 436 | 1 | Binding Re-registration Control Sub-Option | 437 +---+-----------------------------------------------------+ 438 | 2 | Heartbeat Control Sub-Option | 439 +---+-----------------------------------------------------+ 441 7. Security Considerations 443 The LCMP Parameters option defined in this specification allows the 444 configuration of re-registration and heartbeat frequencies. This 445 option is defined for carrying it in Proxy Binding Update and Proxy 446 Binding Acknowledgement messages. This option is carried like any 447 other mobility header option as specified in [RFC5213] and does not 448 require any special security considerations. 450 8. Acknowledgements 452 The authors would like to thank the DMM working group for all the 453 comments and discussions on this document. The authors would also 454 like to thank Suresh Krishnan, Ralph Droms, Mirja Kuehlewind, Alexey 455 Melnikov and Ben Campbell for their review feedback. 457 9. References 459 9.1. Normative References 461 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 462 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 463 RFC2119, March 1997, 464 . 466 [RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V., 467 Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", 468 RFC 5213, DOI 10.17487/RFC5213, August 2008, 469 . 471 [RFC5847] Devarapalli, V., Ed., Koodli, R., Ed., Lim, H., Kant, N., 472 Krishnan, S., and J. Laganier, "Heartbeat Mechanism for 473 Proxy Mobile IPv6", RFC 5847, DOI 10.17487/RFC5847, 474 June 2010, . 476 [RFC7563] Pazhyannur, R., Speicher, S., Gundavelli, S., Korhonen, 477 J., and J. Kaippallimalil, "Extensions to the Proxy Mobile 478 IPv6 (PMIPv6) Access Network Identifier Option", RFC 7563, 479 DOI 10.17487/RFC7563, June 2015, 480 . 482 9.2. Informative References 484 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 485 (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, 486 December 1998, . 488 [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility 489 Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, 490 July 2011, . 492 Authors' Addresses 494 Dhananjay Patki 495 Cisco 496 Cessna Business Park SEZ, Kadubeesanahalli 497 Bangalore, Karnataka 560087 498 India 500 Email: dhpatki@cisco.com 502 Sri Gundavelli 503 Cisco 504 170 West Tasman Drive 505 San Jose, CA 95134 506 USA 508 Email: sgundave@cisco.com 510 Jong-Hyouk Lee 511 Sangmyung University 512 31, Sangmyeongdae-gil, Dongnam-gu 513 Cheonan 330-720 514 Republic of Korea 516 Email: jonghyouk@smu.ac.kr 518 Qiao Fu 519 China Mobile 520 Xuanwumenxi Ave. No.32 521 Beijing 522 P.R. China 524 Email: fuqiao1@outlook.com 525 Lyle T Bertz 526 Sprint 527 Kansas 528 USA 530 Email: Lyle.T.Bertz@sprint.com