idnits 2.17.1 draft-ietf-dmm-lma-controlled-mag-params-03.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 5, 2017) is 2637 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: August 9, 2017 J. Lee 6 Sangmyung University 7 Q. Fu 8 China Mobile 9 L. Bertz 10 Sprint 11 February 5, 2017 13 LMA Controlled MAG Session Parameters 14 draft-ietf-dmm-lma-controlled-mag-params-03.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 (LMA) in Proxy Mobile IPv6 (PMIPv6) signaling 21 for notifying the mobile access gateway (MAG) to conform to various 22 parameters contained in this extension. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on August 9, 2017. 41 Copyright Notice 43 Copyright (c) 2017 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 3 60 2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3 61 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 62 3. Protocol Extension . . . . . . . . . . . . . . . . . . . . . 3 63 3.1. Format of the LCMP Sub-Options . . . . . . . . . . . . . 4 64 3.1.1. Binding Re-registration Control Sub-Option . . . . . 5 65 3.1.2. Heartbeat Control Sub-Option . . . . . . . . . . . . 6 66 4. Protocol Configuration Variables . . . . . . . . . . . . . . 6 67 4.1. Local Mobility Anchor - Configuration Variables . . . . . 6 68 5. Protocol Considerations . . . . . . . . . . . . . . . . . . . 8 69 5.1. Local Mobility Anchor Considerations . . . . . . . . . . 8 70 5.2. Mobile Access Gateway Considerations . . . . . . . . . . 9 71 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 72 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 73 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 74 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 75 9.1. Normative References . . . . . . . . . . . . . . . . . . 10 76 9.2. Informative References . . . . . . . . . . . . . . . . . 11 77 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 79 1. Introduction 81 A large PMIPv6 deployment, such as residential deployment, can have 82 tens of thousands of MAGs spread across geographical locations. 83 While it can be operationally challenging to manage such a large 84 number of MAGs, it can also be very difficult to ensure configuration 85 consistency across all the MAGs if they are not centrally managed. 86 Configuring aggressive values of parameters such as re-registration 87 timeout and heartbeat interval can potentially create considerable 88 signaling load on the LMA. This document provides a new option to 89 enable the LMA to control various parameters on the MAG such as the 90 re-registration frequency [RFC5213] and heartbeat frequency 91 [RFC5847]. With this option, the configuration of these tunable 92 parameters done centrally on the LMA enables Service Providers to 93 have better control on the behavior of the MAGs with deterministic 94 singaling load on the LMA. 96 2. Conventions and Terminology 98 2.1. Conventions 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 102 document are to be interpreted as described in [RFC2119]. 104 2.2. Terminology 106 All the terms used in this document are to be interpreted as defined 107 in [RFC5213], [RFC5847] and [RFC7563]. 109 3. Protocol Extension 111 The LMA Controlled MAG Parameters (LCMP) option is a mobility header 112 option used to exchange information related to the parameters that a 113 LMA enforces on a MAG. The option can be included in Proxy Binding 114 Acknowledge (PBA) message only, and there MUST NOT be more than a 115 single instance of this mobility option in the PBA message. This 116 mobility option MUST contain one or more LCMP sub-options. The 117 suboptions are defined in Section 3.1. The alignment of this option 118 MUST be 4n [RFC2460]. 120 0 1 2 3 121 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 122 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 123 | Type | Length | Reserved | 124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 125 | ... LCMP Sub-option(s) ... ~ 126 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 128 Figure 1: LMA Controlled MAG Parameters Option 130 Type 132 MUST be set to the value of IANA-1, indicating that it is a LMA- 133 Controlled-MAG-Parameters option. 135 Length 137 8-bit unsigned integer indicating the length in octets of the 138 option, excluding the Type and Length fields. 140 Reserved 142 MUST be set to zero when sending and ignored when received. 144 LCMP Sub-option(s) 146 LCMP Sub-options are described in the below sections. The sub- 147 options are optional and can be present in any order. 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 alignment of the sub-option MUST be 4n. The format 155 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 Refresh 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 Refresh 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 The LMA MUST allow the following variables to be configured by the 269 system management. The configured values for these protocol 270 variables MUST survive server reboots and service restarts. 272 EnableLCMPSubOptReregControl 273 This flag indicates the operational state of the Binding Re- 274 registration Control sub-option support. The default value for 275 this flag is set to (0), indicating that support for the Binding 276 Re-registration Control sub-option is disabled. 278 EnableLCMPSubOptHeartbeatControl 280 This flag indicates the operational state of the Heartbeat Control 281 sub-option support. The default value for this flag is set to 282 (0), indicating that support for the Heartbeat Control sub-option 283 is disabled. 285 The following variables MAY be defined at various granularities such 286 as per binding, per peering MAG, per cluster of MAGs or any other 287 custom grouping. Regardless of the granularity of this 288 configuration, the LMA MUST be able to determine the value of these 289 variables on an individual binding basis by way of configuration 290 hierarchy. 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 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 is 1 second. 306 LCMPMaximumRetransmissionTime 308 This variable is used to set the maximum delay in seconds before 309 the last PBU retransmission message of the exponential back-off 310 process. This variable is same as MAX_BINDACK_TIMEOUT mentioned 311 in Section 6.9.4 of [RFC5213]. The default value is 32 seconds. 313 LCMPHeartbeatInterval 315 This variable is used to set the time delay in seconds after a 316 successful heartbeat exchange (heartbeat request followed by 317 response) when the next heartbeat exchange can be triggered. The 318 default value is 60 seconds. It SHOULD NOT be set to less than 30 319 seconds or more than 3600 seconds. The value of this variable MAY 320 be derived from the variable HEARTBEAT_INTERVAL defined in 321 Section 5 of [RFC5847] if configured on the LMA. 323 LCMPHeartbeatRetransmissionDelay 325 This variable is used to set the minimum time delay in seconds 326 before a heartbeat message is retransmitted. The value of this 327 variable SHOULD be less than LCMPHeartbeatInterval. The default 328 value is 5 seconds. 330 LCMPHeartbeatMaxRetransmissions 332 This variable is used to set the maximum number of heartbeat 333 retransmissions. The default value for this variable is 3. The 334 value of this variable MAY be derived from the variable 335 MISSING_HEARTBEATS_ALLOWED defined in Section 5 of [RFC5847] if 336 configured on the LMA. 338 5. Protocol Considerations 340 The following considerations apply to the LMA and the MAG. 342 The conceptual Binding Cache Entry data structure maintained by the 343 LMA, described in Section 5.1 of [RFC5213] and the conceptual Binding 344 Update List entry data structure maintained by the MAG, described in 345 Section 6.1 of [RFC5213], MUST be extended to store the LCMP option 346 related information elements associated with the current session. 347 Specifically the following parameters MUST be defined: 349 o LCMPReregistrationStartTime 351 o LCMPInitialRetransmissionTime 353 o LCMPMaximumRetransmissionTime 355 o LCMPHeartbeatInterval 357 o LCMPHeartbeatRetransmissionDelay 359 o LCMPHeartbeatMaxRetransmissions 361 5.1. Local Mobility Anchor Considerations 363 On receiving a PBU message [RFC5213] from a MAG, the LMA MUST check 364 if the variable EnableLCMPSubOptReregControl is configured and set to 365 (1). If yes, and if all of LCMPReregistrationStartTime, 366 LCMPInitialRetransmissionTime and LCMPMaximumRetransmissionTime are 367 set to NON_ZERO values, then it MUST include Binding Re-registration 368 Control Sub-Option in the LCMP mobility option which is in turn 369 included in the PBA message. If the variable 370 EnableLCMPSubOptReregControl is configured and set to (1) and if any 371 of LCMPReregistrationStartTime, LCMPInitialRetransmissionTime and 372 LCMPMaximumRetransmissionTime is set to ZERO value, then the LMA MUST 373 report a configuration error and reject the binding request by 374 sending a PBA message with status code '128-Reason Unspecified' 375 [RFC5213]. 377 The LMA MUST also check if variable EnableLCMPSubOptHeartbeatControl 378 is configured and set to (1). If yes, and if all of 379 LCMPHeartbeatInterval, LCMPHeartbeatRetransmissionDelay and 380 LCMPHeartbeatMaxRetransmissions are set to NON_ZERO values, then it 381 MUST include Heartbeat Control Sub-Option in the LCMP mobility option 382 which is in turn included in the PBA message. If the variable 383 EnableLCMPSubOptHeartbeatControl is set to (1) and if any of 384 LCMPHeartbeatInterval, LCMPHeartbeatRetransmissionDelay and 385 LCMPHeartbeatMaxRetransmissions is set to ZERO value, then the LMA 386 MUST report a configuration error and reject the binding request by 387 sending a PBA message with status code '128-Reason Unspecified' 388 [RFC5213]. 390 5.2. Mobile Access Gateway Considerations 392 If the PBA message [RFC5213] received from the LMA contains the LCMP 393 mobility option and the Binding Re-registration Control Sub-Option, 394 then the MAG MUST overwrite the binding re-registration related timer 395 parameters configured locally on the MAG with the parameters received 396 in Binding Re-registration Control Sub-Option. If any of the 397 parameters in the Binding Re-registration Control Sub-Option is ZERO, 398 then the PBA message MUST be ignored and an error message SHOULD be 399 logged. 401 Similarly, if the LCMP mobility option contains the Heartbeat Control 402 Sub-Option, then the MAG MUST overwrite the heartbeat related timer 403 parameters configured locally on the MAG with the parameters received 404 in the Heartbeat Control Sub-Option. If any of the parameters in the 405 Heartbeat Control Sub-Option except HB-Retransmission-Delay is ZERO, 406 then the PBA message MUST be ignored and error message SHOULD be 407 logged. 409 6. IANA Considerations 411 This document requires the following IANA actions in the "Mobile IPv6 412 Parameters" registry. 414 o Action 1: This specification defines a new mobility header option, 415 "LMA Controlled MAG Parameters". This mobility option is 416 described in Section 3. The type value (IANA-1) for this option 417 needs to be assigned from the same numbering space as allocated 418 for the other mobility options, as defined in [RFC6275]. 420 o Action 2: This specification defines a new mobility sub-option 421 format, the LCMP Parameters sub-option. The format of this 422 mobility sub-option is described in Section 3.1. This sub-option 423 can be carried in the LCMP Parameters option. The type value for 424 this sub-option needs to be managed by IANA, under the registry 425 "LMA Controlled MAG Parameters Sub-Option Type Values". This 426 specification reserves the following type values. Approval of new 427 LCMP Parameters sub-option type values are to be made through IANA 428 Expert Review. 430 +---+-----------------------------------------------------+ 431 | 0 | Reserved | 432 +---+-----------------------------------------------------+ 433 | 1 | Binding Re-registration Control Sub-Option | 434 +---+-----------------------------------------------------+ 435 | 2 | Heartbeat Control Sub-Option | 436 +---+-----------------------------------------------------+ 438 7. Security Considerations 440 The LCMP Parameters option defined in this specification is for use 441 in PBA message. This option is carried like any other mobility 442 header option as specified in [RFC6275] and does not require any 443 special security considerations. 445 8. Acknowledgements 447 The authors would like to thank the DMM working group for all the 448 comments and discussions on this document. The authors would also 449 like to thank Suresh Krishnan and Ralph Droms for their review 450 feedback. 452 9. References 454 9.1. Normative References 456 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 457 Requirement Levels", BCP 14, RFC 2119, 458 DOI 10.17487/RFC2119, March 1997, 459 . 461 [RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V., 462 Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", 463 RFC 5213, DOI 10.17487/RFC5213, August 2008, 464 . 466 [RFC5847] Devarapalli, V., Ed., Koodli, R., Ed., Lim, H., Kant, N., 467 Krishnan, S., and J. Laganier, "Heartbeat Mechanism for 468 Proxy Mobile IPv6", RFC 5847, DOI 10.17487/RFC5847, June 469 2010, . 471 [RFC7563] Pazhyannur, R., Speicher, S., Gundavelli, S., Korhonen, 472 J., and J. Kaippallimalil, "Extensions to the Proxy Mobile 473 IPv6 (PMIPv6) Access Network Identifier Option", RFC 7563, 474 DOI 10.17487/RFC7563, June 2015, 475 . 477 9.2. Informative References 479 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 480 (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, 481 December 1998, . 483 [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility 484 Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July 485 2011, . 487 Authors' Addresses 489 Dhananjay Patki 490 Cisco 491 Cessna Business Park SEZ, Kadubeesanahalli 492 Bangalore, Karnataka 560087 493 India 495 Email: dhpatki@cisco.com 497 Sri Gundavelli 498 Cisco 499 170 West Tasman Drive 500 San Jose, CA 95134 501 USA 503 Email: sgundave@cisco.com 504 Jong-Hyouk Lee 505 Sangmyung University 506 31, Sangmyeongdae-gil, Dongnam-gu 507 Cheonan 330-720 508 Republic of Korea 510 Email: jonghyouk@smu.ac.kr 512 Qiao Fu 513 China Mobile 514 Xuanwumenxi Ave. No.32 515 Beijing 516 China 518 Email: fuqiao1@outlook.com 520 Lyle T Bertz 521 Sprint 522 Kansas 523 USA 525 Email: Lyle.T.Bertz@sprint.com