idnits 2.17.1 draft-ietf-dmm-lma-controlled-mag-params-02.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 (July 1, 2016) is 2854 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: January 2, 2017 J. Lee 6 Sangmyung University 7 Q. Fu 8 China Mobile 9 L. Bertz 10 Sprint 11 July 1, 2016 13 LMA Controlled MAG Session Parameters 14 draft-ietf-dmm-lma-controlled-mag-params-02.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 LMA in PMIPv6 signaling for notifying the MAG to conform to various 21 parameters contained in this extension. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on January 2, 2017. 40 Copyright Notice 42 Copyright (c) 2016 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 3 59 2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3 60 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 61 3. Protocol Extension . . . . . . . . . . . . . . . . . . . . . 3 62 3.1. Format of the LCMP Sub-Options . . . . . . . . . . . . . 4 63 3.1.1. Binding Re-registration Control Sub-Option . . . . . 5 64 3.1.2. Heartbeat Control Sub-Option . . . . . . . . . . . . 5 65 4. Protocol Configuration Variables . . . . . . . . . . . . . . 6 66 4.1. Local Mobility Anchor - Configuration Variables . . . . . 6 67 5. Protocol Considerations . . . . . . . . . . . . . . . . . . . 8 68 5.1. Local Mobility Anchor Considerations . . . . . . . . . . 9 69 5.2. Mobile Access Gateway Considerations . . . . . . . . . . 9 70 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 71 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 72 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 73 8.1. Normative References . . . . . . . . . . . . . . . . . . 10 74 8.2. Informative References . . . . . . . . . . . . . . . . . 11 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 77 1. Introduction 79 A large PMIPv6 deployment, such as residential deployment, can have 80 tens of thousands of MAGs spread across geographical locations. 81 While it can be operationally challenging to manage such a large 82 number of MAGs, it can also be very difficult to ensure configuration 83 consistency across all the MAGs if they are not centrally managed. 84 Configuring aggressive values of parameters such as re-registration 85 timeout and heartbeat interval can potentially create considerable 86 signaling load on the LMA. This document provides a new option to 87 enable the LMA to control various parameters on the MAG such as the 88 re-registration frequency [RFC5213] and heartbeat frequency 89 [RFC5847]. With this option, the configuration of these tunable 90 parameters done centrally on the LMA enables Service Providers to 91 have better control on the behavior of the MAGs with deterministic 92 singaling load on the LMA. 94 2. Conventions and Terminology 96 2.1. Conventions 98 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 99 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 100 document are to be interpreted as described in [RFC2119]. 102 2.2. Terminology 104 All the terms used in this document are to be interpreted as defined 105 in [RFC5213], [RFC5847] and [RFC7563]. 107 3. Protocol Extension 109 The LMA Controlled MAG Parameters (LCMP) option is a mobility header 110 option used to exchange information related to the parameters that a 111 local mobility anchor enforces on a mobile access gateway. The 112 option can be included in Proxy Binding Acknowledgement (PBA) message 113 only, and there MUST NOT be more than a single instance of this 114 mobility option in a mobility message. This mobility option MUST 115 contain one or more LMA Controlled MAG Parameters sub-options. The 116 suboptions are defined in Section 3.1. The alignment of this option 117 MUST be 4n [RFC2460]. 119 0 1 2 3 120 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 121 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 122 | Type | Length | Reserved | 123 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 124 | ... LCMP Sub-option(s) ... ~ 125 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 127 Figure 1: LMA Controlled MAG Parameters Option 129 Type 131 MUST be set to the value of IANA-1, indicating that it is a LMA- 132 Controlled-MAG-Parameters option. 134 Length 136 8-bit unsigned integer indicating the length in octets of the 137 option, excluding the Type and Length fields. 139 Reserved 141 MUST be set to zero when sending and ignored when received. 143 LCMP Sub-option(s) 145 LCMP Sub-options are described in the below sections. The sub- 146 options are optional and can be present in any order. 148 3.1. Format of the LCMP Sub-Options 150 The LMA Controlled MAG Parameters sub-options are used for carrying 151 information elements related to various parameters that need to be 152 configured on the MAG. These sub-options can be included in the LMA 153 Controlled MAG Parameters option defined in Section 3. The alignment 154 of the sub-option MUST be 4n. The format of this sub-option is as 155 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 LMA Controlled 168 MAG Parameters sub-option. This specification defines the 169 following types: 171 0 - Reserved 173 1 - Binding Refresh Control Sub-Option 175 2 - Heartbeat Control Sub-Option 177 Length 179 8-bit unsigned integer indicating the number of octets needed to 180 encode the Option Data, excluding the LCMP Type and LCMP Length 181 fields of the sub-option. 183 3.1.1. Binding Re-registration Control Sub-Option 185 The Binding Re-registration Control Sub-Option is a mobility sub- 186 option carried in the LMA Controlled MAG Parameters mobility option 187 defined in Section 3.1. This sub-option carries re-registration 188 related timer values. There MUST be no more than a single instance 189 of this sub-option in LMA Controlled MAG Parameters option. The 190 format of this sub-option is defined below. 192 0 1 2 3 193 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 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 | LCMP Type = 1 | LCMP Length | Re-registration-Start-Time | 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 | Initial-Retransmission-Time | Maximum-Retransmission-Time | 198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 200 Figure 3: Binding Re-registration Control Sub-Option 202 Re-registration-Start-Time 204 16-bit unsigned integer indicating the number of time units before 205 the expiry of the PMIPv6 binding lifetime when the registration 206 refresh process needs to be activated. One time unit is 4 207 seconds. 209 Initial-Retransmission-Time 211 16-bit unsigned integer indicating minimum delay in seconds before 212 the first PBU retransmission of the exponential back-off process. 214 Maximum-Retransmission-Time 216 16-bit unsigned integer indicating maximum delay in seconds before 217 the last PBU retransmission message of the exponential back-off 218 process. 220 3.1.2. Heartbeat Control Sub-Option 221 0 1 2 3 222 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 223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 224 | LCMP Type = 2 | LCMP Length | HB-Interval | 225 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 226 | HB-Retransmission-Delay | HB-Max-Retransmissions | 227 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 229 Figure 4: Heartbeat Control Sub-Option 231 HB-Interval 233 16-bit unsigned integer indicating heartbeat interval, i.e. time 234 delay in seconds after a successful heartbeat exchange (request 235 followed by response) when the next heartbeat exchange can be 236 triggered. 238 HB-Retransmission-Delay 240 16-bit unsigned integer indicating minimum time delay in seconds 241 before a heartbeat message is retransmitted. 243 HB-Max-Retransmissions 245 16-bit unsigned integer indicating maximum number of heartbeat 246 retransmissions. 248 4. Protocol Configuration Variables 250 4.1. Local Mobility Anchor - Configuration Variables 252 The local mobility anchor MUST allow the following variables to be 253 configured by the system management. The configured values for these 254 protocol variables MUST survive server reboots and service restarts. 256 EnableLCMPSubOptReregControl 258 This flag indicates the operational state of the Binding Re- 259 registration Control sub-option support. The default value for 260 this flag is set to (0), indicating that support for the Binding 261 Re-registration Control sub-option is disabled. 263 When this flag on the local mobility anchor is set to a value of 264 (1), the local mobility anchor SHOULD include this sub-option in 265 the Proxy Binding Acknowledge messages that it sends to the mobile 266 access gateway; otherwise, it MUST NOT include the sub-option. 267 There can be situations where the local mobility anchor is unable 268 to obtain the Binding Re-registration Control information and may 269 not be able to construct this sub-option. 271 EnableLCMPSubOptHeartbeatControl 273 This flag indicates the operational state of the Heartbeat Control 274 sub-option support. The default value for this flag is set to 275 (0), indicating that support for the Heartbeat Control sub-option 276 is disabled. 278 When this flag on the local mobility anchor is set to a value of 279 (1), the local mobility anchor SHOULD include this sub-option in 280 the Proxy Binding Acknowledge messages that it sends to the mobile 281 access gateway; otherwise, it MUST NOT include the sub-option. 282 There can be situations where the local mobility anchor is unable 283 to obtain the Heartbeat Control information and may not be able to 284 construct this sub-option. 286 The following variables MAY be defined at various granularity such as 287 per binding, per peering MAG, per cluster of MAGs or any other custom 288 grouping. Regardless of the granularity of this configuration, the 289 local mobility anchor should be able to determine the value of these 290 variables on an individual binding basis by way of configuration 291 hierarchy. 293 LCMPReregistrationStartTime 295 This variable is used to set the minimum time interval in number 296 of seconds before the expiry of the PMIPv6 binding lifetime when 297 the registration refresh process SHOULD be activated. The default 298 value is 10 units, where each unit is 4 seconds. 300 LCMPInitialRetransmissionTime 302 This variable is used to set the minimum delay in seconds before 303 the first PBU retransmission of the exponential back-off process. 304 This variable is same as INITIAL_BINDACK_TIMEOUT mentioned in 305 Section 6.9.4 of [RFC5213]. The default value is 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 is 32 seconds. 314 LCMPHeartbeatInterval 315 This variable is used to set the time delay in seconds after a 316 successful heartbeat exchange (request followed by response) when 317 the next heartbeat exchange can be triggered. The default value 318 is 60 seconds. It SHOULD NOT be set to less than 30 seconds or 319 more than 3600 seconds. The value of this variable MAY be derived 320 from the variable HEARTBEAT_INTERVAL defined in Section 5 of 321 [RFC5847] if defined on the local mobility anchor. 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 LCMP_HEARTBEAT_INTERVAL. 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 defined on the local mobility anchor. 338 5. Protocol Considerations 340 The following considerations apply to the local mobility anchor and 341 the mobile access gateway. 343 The conceptual Binding Cache Entry data structure maintained by the 344 local mobility anchor, described in Section 5.1 of [RFC5213] and the 345 conceptual Binding Update List entry data structure maintained by the 346 mobile access gateway, described in Section 6.1 of [RFC5213], MUST be 347 extended to store the LMA Controlled MAG Parameters option related 348 information elements associated with the current session. 349 Specifically the following parameters MUST be defined: 351 o LCMPReregistrationStartTime 353 o LCMPInitialRetransmissionTime 355 o LCMPMaximumRetransmissionTime 357 o LCMPHeartbeatInterval 359 o LCMPHeartbeatRetransmissionDelay 361 o LCMPHeartbeatMaxRetransmissions 363 5.1. Local Mobility Anchor Considerations 365 o On receiving a Proxy Binding Update message [RFC5213] from a 366 mobile access gateway, the local mobility anchor should check if 367 EnableLCMPSubOptReregControl is set to (1). If yes, and if all of 368 LCMPReregistrationStartTime, LCMPInitialRetransmissionTime and 369 LCMPMaximumRetransmissionTime are set to NON_ZERO values, then in 370 SHOULD include Binding Re-registration Control Sub-Option in the 371 LMA Controlled MAG Parameters mobility option which is in turn 372 included in the Proxy Binding Acknowledge message. 374 o If EnableLCMPSubOptReregControl is set to (1) and if any of 375 LCMPReregistrationStartTime, LCMPInitialRetransmissionTime and 376 LCMPMaximumRetransmissionTime is set to ZERO value, then the local 377 mobility anchor should report a configuration error. 379 o The local mobility anchor should also check if 380 EnableLCMPSubOptHeartbeatControl is set to (1). If yes, and if 381 all of LCMPHeartbeatInterval, LCMPHeartbeatRetransmissionDelay and 382 LCMPHeartbeatMaxRetransmissions are set to NON_ZERO values, then 383 in SHOULD include Heartbeat Control Sub-Option in the LMA 384 Controlled MAG Parameters mobility option which is in turn 385 included in the Proxy Binding Acknowledge message. 387 o If EnableLCMPSubOptHeartbeatControl is set to (1) and if any of 388 LCMPHeartbeatInterval, LCMPHeartbeatRetransmissionDelay and 389 LCMPHeartbeatMaxRetransmissions is set to ZERO value, then the 390 local mobility anchor should report a configuration error. 392 5.2. Mobile Access Gateway Considerations 394 o On Receiving Proxy Binding Acknowledge message [RFC5213] from the 395 local mobility anchor with LMA Controlled MAG Parameters mobility 396 option, the mobile access gateway MUST overwrite the binding re- 397 registration related timer parameters with the parameters received 398 in Binding Re-registration Control Sub-Option, if present in the 399 LMA Controlled MAG Parameters mobility option. Similarly, the 400 mobile access gateway MUST overwrite the heartbeat related timer 401 parameters with the parameters received in Heartbeat Control Sub- 402 Option, if present in the LMA Controlled MAG Parameters mobility 403 option. 405 o If any of the parameters in the Binding Re-registration Control 406 Sub-Option is ZERO, then the sub-option MUST be ignored and an 407 error message SHOULD be logged. 409 o If any of the parameters in the Heartbeat Control Sub-Option 410 except HB-Retransmission-Delay is ZERO, then the sub-option MUST 411 be ignored and error message SHOULD be logged. 413 6. IANA Considerations 415 This document requires the following IANA actions. 417 o Action 1: This specification defines a new mobility header option, 418 the 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 LMA Controlled MAG Parameters sub-option. The format 425 of this mobility sub-option is described in Section 3.1. This 426 sub-option can be carried in the LMA Controlled MAG Parameters 427 option. The type value for this sub-option needs to be managed by 428 IANA, under the registry "LMA Controlled MAG Parameters Sub-Option 429 Type Values". This specification reserves the following type 430 values. Approval of new LMA Controlled MAG Parameters sub-option 431 type values are to be made through IANA 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 LMA Controlled MAG Parameters option defined in this 444 specification is for use in Proxy Binding Acknowledgement message. 445 This option is carried like any other mobility header option as 446 specified in [RFC6275] and does not require any special security 447 considerations. 449 8. References 451 8.1. Normative References 453 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 454 Requirement Levels", BCP 14, RFC 2119, 455 DOI 10.17487/RFC2119, March 1997, 456 . 458 [RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V., 459 Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", 460 RFC 5213, DOI 10.17487/RFC5213, August 2008, 461 . 463 [RFC5847] Devarapalli, V., Ed., Koodli, R., Ed., Lim, H., Kant, N., 464 Krishnan, S., and J. Laganier, "Heartbeat Mechanism for 465 Proxy Mobile IPv6", RFC 5847, DOI 10.17487/RFC5847, June 466 2010, . 468 [RFC7563] Pazhyannur, R., Speicher, S., Gundavelli, S., Korhonen, 469 J., and J. Kaippallimalil, "Extensions to the Proxy Mobile 470 IPv6 (PMIPv6) Access Network Identifier Option", RFC 7563, 471 DOI 10.17487/RFC7563, June 2015, 472 . 474 8.2. Informative References 476 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 477 (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, 478 December 1998, . 480 [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility 481 Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July 482 2011, . 484 Authors' Addresses 486 Dhananjay Patki 487 Cisco 488 Cessna Business Park SEZ, Kadubeesanahalli 489 Bangalore, Karnataka 560087 490 India 492 Email: dhpatki@cisco.com 494 Sri Gundavelli 495 Cisco 496 170 West Tasman Drive 497 San Jose, CA 95134 498 USA 500 Email: sgundave@cisco.com 501 Jong-Hyouk Lee 502 Sangmyung University 503 31, Sangmyeongdae-gil, Dongnam-gu 504 Cheonan 330-720 505 Republic of Korea 507 Email: jonghyouk@smu.ac.kr 509 Qiao Fu 510 China Mobile 511 Xuanwumenxi Ave. No.32 512 Beijing 513 China 515 Email: fuqiao1@outlook.com 517 Lyle T Bertz 518 Sprint 519 Kansas 520 USA 522 Email: Lyle.T.Bertz@sprint.com