idnits 2.17.1 draft-ietf-dmm-lma-controlled-mag-params-00.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 (December 16, 2015) is 3047 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: June 18, 2016 J. Lee 6 Sangmyung University 7 Q. Fu 8 China Mobile 9 L. Bertz 10 Sprint 11 December 16, 2015 13 LMA Controlled MAG Session Parameters 14 draft-ietf-dmm-lma-controlled-mag-params-00.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 June 18, 2016. 40 Copyright Notice 42 Copyright (c) 2015 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 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 . . . . . . . . . . . . . 6 65 4. Protocol Configuration Variables . . . . . . . . . . . . . . . 6 66 4.1. Local Mobility Anchor - Configuration Variables . . . . . 7 67 5. Protocol Considerations . . . . . . . . . . . . . . . . . . . 8 68 5.1. Local Mobility Anchor Considerations . . . . . . . . . . . 9 69 5.2. Mobile Access Gateway Considerations . . . . . . . . . . . 10 70 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 71 7. Security Considerations . . . . . . . . . . . . . . . . . . . 11 72 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 73 8.1. Normative References . . . . . . . . . . . . . . . . . . . 11 74 8.2. Informative References . . . . . . . . . . . . . . . . . . 11 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 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 aggresive 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 requirement for 117 this option is 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 3.1. Format of the LCMP Sub-Options 145 The LMA Controlled MAG Parameters sub-options are used for carrying 146 information elements related to various parameters that need to be 147 configured on the MAG. These sub-options can be included in the LMA 148 Controlled MAG Parameters option defined in Section 3. The format of 149 this sub-option is as follows. The alignment requirement for the 150 sub-option is 4n. The sub-options are optional and can be present in 151 any order. 153 0 1 2 3 154 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 155 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 156 | LCMP Type | LCMP Length | Sub-Option Data ~ 157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 159 Figure 2: LMA Controlled MAG Parameters Sub-Option 161 Type 163 8-bit unsigned integer indicating the type of the LMA Controlled 164 MAG Parameters sub-option. This specification defines the 165 following types: 167 0 - Reserved 169 1 - Binding Refresh Control Sub-Option 171 2 - Heartbeat Control Sub-Option 173 Length 175 8-bit unsigned integer indicating the number of octets needed to 176 encode the Option Data, excluding the LCMP Type and LCMP Length 177 fields of the sub-option. 179 3.1.1. Binding Re-registration Control Sub-Option 181 The Binding Re-registration Control Sub-Option is a mobility sub- 182 option carried in the LMA Controlled MAG Parameters mobility option 183 defined in Section 3.1. This sub-option carries re-registration 184 related timer values. There MUST be no more than a single instance 185 of this sub-option in LMA Controlled MAG Parameters option. The 186 format of this sub-option is defined below. 188 0 1 2 3 189 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 190 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 191 | LCMP Type = 1 | LCMP Length | Re-registration-Start-Time | 192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 193 | Initial-Retransmission-Time | Maximum-Retransmission-Time | 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 196 Figure 3: Binding Re-registration Control Sub-Option 198 Re-registration-Start-Time 200 16-bit unsigned integer indicating the number of time units before 201 the expiry of the PMIPv6 binding lifetime when the registration 202 refresh process needs to be activated. One time unit is 4 203 seconds. 205 Initial-Retransmission-Time 207 16-bit unsigned integer indicating minimum delay in seconds before 208 the first PBU retransmission of the exponential back-off process. 210 Maximum-Retransmission-Time 212 16-bit unsigned integer indicating maximum delay in seconds before 213 the last PBU retransmission message of the exponential back-off 214 process. 216 3.1.2. Heartbeat Control Sub-Option 218 0 1 2 3 219 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 220 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 221 | LCMP Type = 2 | LCMP Length | HB-Interval | 222 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 223 | HB-Retransmission-Delay | HB-Max-Retransmissions | 224 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 226 Figure 4: Heartbeat Control Sub-Option 228 HB-Interval 230 16-bit unsigned integer indicating heartbeat interval, i.e. time 231 delay in seconds after a successful heartbeat exchange (request 232 followed by response) when the next heartbeat exchange can be 233 triggered. 235 HB-Retransmission-Delay 237 16-bit unsigned integer indicating minimum time delay in seconds 238 before a heartbeat message is retransmitted. 240 HB-Max-Retransmissions 242 16-bit unsigned integer indicating maximum number of heartbeat 243 retransmissions. 245 4. Protocol Configuration Variables 246 4.1. Local Mobility Anchor - Configuration Variables 248 The local mobility anchor MUST allow the following variables to be 249 configured by the system management. The configured values for these 250 protocol variables MUST survive server reboots and service restarts. 252 EnableLCMPSubOptReregControl 254 This flag indicates the operational state of the Binding Re- 255 registration Control sub-option support. The default value for 256 this flag is set to (0), indicating that support for the Binding 257 Re-registration Control sub-option is disabled. 259 When this flag on the mobile access gateway is set to a value of 260 (1), the local mobility anchor SHOULD include this sub-option in 261 the Proxy Binding Acknowledge messages that it sends to the mobile 262 access gateway; otherwise, it SHOULD NOT include the sub-option. 263 There can be situations where the local mobility anchor is unable 264 to obtain the Binding Re-registration Control information and may 265 not be able to construct this sub-option. 267 EnableLCMPSubOptHeartbeatControl 269 This flag indicates the operational state of the Heartbeat Control 270 sub-option support. The default value for this flag is set to 271 (0), indicating that support for the Heartbeat Control sub-option 272 is disabled. 274 When this flag on the mobile access gateway is set to a value of 275 (1), the local mobility anchor SHOULD include this sub-option in 276 the Proxy Binding Acknowledge messages that it sends to the mobile 277 access gateway; otherwise, it SHOULD NOT include the sub-option. 278 There can be situations where the local mobility anchor is unable 279 to obtain the Heartbeat Control information and may not be able to 280 construct this sub-option. 282 The following variables MAY be defined at various granularity such as 283 per binding, per peering MAG, per cluster of MAGs or any other custom 284 grouping. Regardless of the granularity of this configuration, the 285 local mobility anchor should be able to determine the value of these 286 variables on an individual binding basis by way of configuration 287 hierarchy. 289 LCMPReregistrationStartTime 291 This variable is used to set the minimum time interval in number 292 of seconds before the expiry of the PMIPv6 binding lifetime when 293 the registration refresh process SHOULD be activated. 295 LCMPInitialRetransmissionTime 297 This variable is used to set the minimum delay in seconds before 298 the first PBU retransmission of the exponential back-off process. 299 This variable is same as INITIAL_BINDACK_TIMEOUT mentioned in 300 Section 6.9.4 of [RFC5213]. 302 LCMPMaximumRetransmissionTime 304 This variable is used to set the maximum delay in seconds before 305 the last PBU retransmission message of the exponential back-off 306 process. This variable is same as MAX_BINDACK_TIMEOUT mentioned 307 in Section 6.9.4 of [RFC5213]. 309 LCMPHeartbeatInterval 311 This variable is used to set the time delay in seconds after a 312 successful heartbeat exchange (request followed by response) when 313 the next heartbeat exchange can be triggered. The default value 314 is 60 seconds. It SHOULD NOT be set to less than 30 seconds or 315 more than 3600 seconds. The value of this variable MAY be derived 316 from the variable HEARTBEAT_INTERVAL defined in Section 5 of 317 [RFC5847] if defined on the local mobility anchor. 319 LCMPHeartbeatRetransmissionDelay 321 This variable is used to set the minimum time delay in seconds 322 before a heartbeat message is retransmitted.. The value of this 323 variable SHOULD be less than LCMP_HEARTBEAT_INTERVAL. The default 324 value is 5 seconds. 326 LCMPHeartbeatMaxRetransmissions 328 This variable is used to set the maximum number of heartbeat 329 retransmissions. The default value for this variable is 3. The 330 value of this variable MAY be derived from the variable 331 MISSING_HEARTBEATS_ALLOWED defined in Section 5 of [RFC5847] if 332 defined on the local mobility anchor. 334 5. Protocol Considerations 336 The following considerations apply to the local mobility anchor and 337 the mobile access gateway. 339 The conceptual Binding Cache Entry data structure maintained by the 340 local mobility anchor, described in Section 5.1 of [RFC5213] and the 341 conceptual Binding Update List entry data structure maintained by the 342 mobile access gateway, described in Section 6.1 of [RFC5213], MUST be 343 extended to store the LMA Controlled MAG Parameters option related 344 information elements associated with the current session. 345 Specifically the following parameters MUST be defined: 347 o LCMPReregistrationStartTime 349 o LCMPInitialRetransmissionTime 351 o LCMPMaximumRetransmissionTime 353 o LCMPHeartbeatInterval 355 o LCMPHeartbeatRetransmissionDelay 357 o LCMPHeartbeatMaxRetransmissions 359 5.1. Local Mobility Anchor Considerations 361 o On receiving a Proxy Binding Update message [RFC5213] from a 362 mobile access gateway, the local mobility anchor should check if 363 EnableLCMPSubOptReregControl is set to (1). If yes, and if all of 364 LCMPReregistrationStartTime, LCMPInitialRetransmissionTime and 365 LCMPMaximumRetransmissionTime are set to NON_ZERO values, then in 366 SHOULD include Binding Re-registration Control Sub-Option in the 367 LMA Controlled MAG Parameters mobility option which is in turn 368 included in the Proxy Binding Acknowledge message. 370 o If EnableLCMPSubOptReregControl is set to (1) and if any of 371 LCMPReregistrationStartTime, LCMPInitialRetransmissionTime and 372 LCMPMaximumRetransmissionTime is set to ZERO value, then the local 373 mobility anchor should report a configuration error. 375 o The local mobility anchor should also check if 376 EnableLCMPSubOptHeartbeatControl is set to (1). If yes, and if 377 all of LCMPHeartbeatInterval, LCMPHeartbeatRetransmissionDelay and 378 LCMPHeartbeatMaxRetransmissions are set to NON_ZERO values, then 379 in SHOULD include Heartbeat Control Sub-Option in the LMA 380 Controlled MAG Parameters mobility option which is in turn 381 included in the Proxy Binding Acknowledge message. 383 o If EnableLCMPSubOptHeartbeatControl is set to (1) and if any of 384 LCMPHeartbeatInterval, LCMPHeartbeatRetransmissionDelay and 385 LCMPHeartbeatMaxRetransmissions is set to ZERO value, then the 386 local mobility anchor should report a configuration error. 388 5.2. Mobile Access Gateway Considerations 390 o On Receiving Proxy Binding Acknowledge message [RFC5213] from the 391 local mobility anchor with LMA Controlled MAG Parameters mobility 392 option, the mobile access gateway MUST overwrite the binding re- 393 registration related timer parameters with the parameters received 394 in Binding Re-registration Control Sub-Option, if present in the 395 LMA Controlled MAG Parameters mobility option. Similarly, the 396 mobile access gateway MUST overwrite the heartbeat related timer 397 parameters with the parameters reveived in Heartbeat Control Sub- 398 Option, if present in the LMA Controlled MAG Parameters mobility 399 option. 401 o If any of the parameters in the Binding Re-registration Control 402 Sub-Option is ZERO, then the sub-option MUST be ignored and an 403 error message SHOULD be logged. 405 o If any of the parameters in the Heartbeat Control Sub-Option 406 except HB-Retransmission-Delay is ZERO, then the sub-option MUST 407 be ignored and error message SHOULD be logged. 409 6. IANA Considerations 411 This document requires the following IANA actions. 413 o Action 1: This specification defines a new mobility header option, 414 the LMA Controlled MAG Parameters. This mobility option is 415 described in Section 3. The type value (IANA-1) for this option 416 needs to be assigned from the same numbering space as allocated 417 for the other mobility options, as defined in [RFC6275]. 419 o Action 2: This specification defines a new mobility sub-option 420 format, the LMA Controlled MAG Parameters sub-option. The format 421 of this mobility sub-option is described in Section 3.1. This 422 sub-option can be carried in the LMA Controlled MAG Parameters 423 option. The type value for this sub-option needs to be managed by 424 IANA, under the registry "LMA Controlled MAG Parameters Sub-Option 425 Type Values". This specification reserves the following type 426 values. Approval of new LMA Controlled MAG Parameters sub-option 427 type values are to be made through IANA Expert Review. 429 +---+-----------------------------------------------------+ 430 | 0 | Reserved | 431 +---+-----------------------------------------------------+ 432 | 1 | Binding Re-registration Control Sub-Option | 433 +---+-----------------------------------------------------+ 434 | 2 | Heartbeat Control Sub-Option | 435 +---+-----------------------------------------------------+ 437 7. Security Considerations 439 The LMA Controlled MAG Parameters option defined in this 440 specification is for use in Proxy Binding Acknowledgement message. 441 This option is carried like any other mobility header option as 442 specified in [RFC6275] and does not require any special security 443 considerations. 445 8. References 447 8.1. Normative References 449 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 450 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 451 RFC2119, March 1997, 452 . 454 [RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V., 455 Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", 456 RFC 5213, DOI 10.17487/RFC5213, August 2008, 457 . 459 [RFC5847] Devarapalli, V., Ed., Koodli, R., Ed., Lim, H., Kant, N., 460 Krishnan, S., and J. Laganier, "Heartbeat Mechanism for 461 Proxy Mobile IPv6", RFC 5847, DOI 10.17487/RFC5847, 462 June 2010, . 464 [RFC7563] Pazhyannur, R., Speicher, S., Gundavelli, S., Korhonen, 465 J., and J. Kaippallimalil, "Extensions to the Proxy Mobile 466 IPv6 (PMIPv6) Access Network Identifier Option", RFC 7563, 467 DOI 10.17487/RFC7563, June 2015, 468 . 470 8.2. Informative References 472 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 473 (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, 474 December 1998, . 476 [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility 477 Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, 478 July 2011, . 480 Authors' Addresses 482 Dhananjay Patki 483 Cisco 484 Cessna Business Park SEZ, Kadubeesanahalli 485 Bangalore, Karnataka 560087 486 India 488 Email: dhpatki@cisco.com 490 Sri Gundavelli 491 Cisco 492 170 West Tasman Drive 493 San Jose, CA 95134 494 USA 496 Email: sgundave@cisco.com 498 Jong-Hyouk Lee 499 Sangmyung University 500 31, Sangmyeongdae-gil, Dongnam-gu 501 Cheonan 330-720 502 Republic of Korea 504 Email: jonghyouk@smu.ac.kr 506 Qiao Fu 507 China Mobile 508 Xuanwumenxi Ave. No.32 509 Beijing 510 China 512 Email: fuqiao1@outlook.com 514 Lyle T Bertz 515 Sprint 516 Kansas 517 USA 519 Email: Lyle.T.Bertz@sprint.com