Debian Codegraph @

rfc8127.html

raw
1 <pre>Internet Engineering Task Force (IETF) D. Patki
2 Request for Comments: 8127 S. Gundavelli
3 Category: Standards Track Cisco
4 ISSN: 2070-1721 J. Lee
5 Sangmyung University
6 Q. Fu
7 China Mobile
8 L. Bertz
9 Sprint
10 August 2017
11
12
13 <span class="h1">Mobile Access Gateway Configuration Parameters Controlled</span>
14 <span class="h1">by the Local Mobility Anchor</span>
15
16 Abstract
17
18 This specification defines a new extension,
19 LMA-Controlled-MAG-Session-Params, to Proxy Mobile IPv6. This option
20 can be used by the local mobility anchor (LMA) in a Proxy Mobile IPv6
21 domain for signaling a mobile access gateway (MAG) on enforcing
22 specific values for various configuration parameters such as
23 heartbeat and binding refresh parameters.
24
25 Status of This Memo
26
27 This is an Internet Standards Track document.
28
29 This document is a product of the Internet Engineering Task Force
30 (IETF). It represents the consensus of the IETF community. It has
31 received public review and has been approved for publication by the
32 Internet Engineering Steering Group (IESG). Further information on
33 Internet Standards is available in <a href="./rfc7841#section-2">Section&nbsp;2 of RFC 7841</a>.
34
35 Information about the current status of this document, any errata,
36 and how to provide feedback on it may be obtained at
37 <a href="http://www.rfc-editor.org/info/rfc8127">http://www.rfc-editor.org/info/rfc8127</a>.
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Patki, et al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc8127">RFC 8127</a> LMA-Controlled MAG Configuration Parameters August 2017</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2017 IETF Trust and the persons identified as the
60 document authors. All rights reserved.
61
62 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
63 Provisions Relating to IETF Documents
64 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
65 publication of this document. Please review these documents
66 carefully, as they describe your rights and restrictions with respect
67 to this document. Code Components extracted from this document must
68 include Simplified BSD License text as described in Section 4.e of
69 the Trust Legal Provisions and are provided without warranty as
70 described in the Simplified BSD License.
71
72 Table of Contents
73
74 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
75 <a href="#section-2">2</a>. Conventions and Terminology . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
76 <a href="#section-2.1">2.1</a>. Conventions . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
77 <a href="#section-2.2">2.2</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
78 <a href="#section-3">3</a>. Protocol Extension . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
79 <a href="#section-3.1">3.1</a>. Format of the LCMP Sub-Options . . . . . . . . . . . . . <a href="#page-5">5</a>
80 <a href="#section-3.1.1">3.1.1</a>. Binding Re-registration Control Sub-Option . . . . . <a href="#page-6">6</a>
81 <a href="#section-3.1.2">3.1.2</a>. Heartbeat Control Sub-Option . . . . . . . . . . . . <a href="#page-7">7</a>
82 <a href="#section-4">4</a>. Protocol Configuration Variables . . . . . . . . . . . . . . <a href="#page-8">8</a>
83 <a href="#section-4.1">4.1</a>. Local Mobility Anchor -- Configuration Variables . . . . <a href="#page-8">8</a>
84 <a href="#section-5">5</a>. Protocol Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
85 <a href="#section-5.1">5.1</a>. Local Mobility Anchor Considerations . . . . . . . . . . <a href="#page-10">10</a>
86 <a href="#section-5.2">5.2</a>. Mobile Access Gateway Considerations . . . . . . . . . . <a href="#page-10">10</a>
87 <a href="#section-6">6</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
88 <a href="#section-7">7</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
89 <a href="#section-8">8</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
90 <a href="#section-8.1">8.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
91 <a href="#section-8.2">8.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
92 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
93 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Patki, et al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc8127">RFC 8127</a> LMA-Controlled MAG Configuration Parameters August 2017</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 A large Proxy Mobile IPv6 (PMIPv6) [<a href="./rfc5213" title="&quot;Proxy Mobile IPv6&quot;">RFC5213</a>] deployment, such as
116 residential deployment, can have tens of thousands of mobile access
117 gateways (MAGs) spread across geographical locations. While it can
118 be operationally challenging to manage such a large number of MAGs,
119 it can also be very difficult to ensure configuration consistency
120 across all the MAGs if they are not centrally managed. Configuring
121 aggressive values of parameters such as re-registration timeout and
122 heartbeat interval can potentially create considerable signaling load
123 on the local mobility anchor (LMA). This document provides a new
124 option to enable the LMA to control various parameters on the MAG
125 such as the re-registration frequency [<a href="./rfc5213" title="&quot;Proxy Mobile IPv6&quot;">RFC5213</a>] and heartbeat
126 frequency [<a href="./rfc5847" title="&quot;Heartbeat Mechanism for Proxy Mobile IPv6&quot;">RFC5847</a>]. With this option, the configuration of these
127 tunable parameters enforced centrally from the LMA enables Service
128 Providers to have better control on the behavior of the MAGs with
129 deterministic signaling load on the LMA.
130
131 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions and Terminology</span>
132
133 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Conventions</span>
134
135 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
136 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
137 "OPTIONAL" in this document are to be interpreted as described in
138 <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a> [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>] [<a href="./rfc8174" title="&quot;Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words&quot;">RFC8174</a>] when, and only when, they appear in all
139 capitals, as shown here.
140
141 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Terminology</span>
142
143 All the terms used in this document are to be interpreted as defined
144 in [<a href="./rfc5213" title="&quot;Proxy Mobile IPv6&quot;">RFC5213</a>], [<a href="./rfc5847" title="&quot;Heartbeat Mechanism for Proxy Mobile IPv6&quot;">RFC5847</a>], and [<a href="./rfc7563" title="&quot;Extensions to the Proxy Mobile IPv6 (PMIPv6) Access Network Identifier Option&quot;">RFC7563</a>].
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164 <span class="grey">Patki, et al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc8127">RFC 8127</a> LMA-Controlled MAG Configuration Parameters August 2017</span>
167
168
169 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Protocol Extension</span>
170
171 The LMA-Controlled MAG Parameters (LCMPs) option is a mobility header
172 option used to exchange information related to the parameters that an
173 LMA enforces on a MAG. This option can be included only in the Proxy
174 Binding Acknowledge (PBA) message, and there MUST NOT be more than a
175 single instance of this mobility option in a given PBA message. This
176 option MUST contain one or more LCMP sub-options. Each LCMP sub-
177 option carries a specific configuration parameter. The sub-options
178 are defined in <a href="#section-3.1">Section 3.1</a>. The LCMP option has an alignment
179 requirement of 4n+2 [<a href="./rfc8200" title="&quot;Internet Protocol, Version 6 (IPv6) Specification&quot;">RFC8200</a>].
180
181 0 1 2 3
182 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
183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
184 | Type | Length |
185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
186 | LCMP Sub-Option(s) ~
187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
188
189 Figure 1: LMA-Controlled MAG Parameters Option
190
191 Type
192
193 MUST be set to the value of 62, indicating that it is an
194 LMA-Controlled-MAG-Parameters option.
195
196 Length
197
198 8-bit unsigned integer indicating the length in octets of the
199 option, excluding the Type and Length fields.
200
201 LCMP Sub-Option(s)
202
203 LCMP sub-options are described in the sections below. The sub-
204 options can be present in any order. Inclusion of any specific
205 sub-option is optional, but at least one sub-option MUST be
206 present.
207
208
209
210
211
212
213
214
215
216
217
218
219
220 <span class="grey">Patki, et al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc8127">RFC 8127</a> LMA-Controlled MAG Configuration Parameters August 2017</span>
223
224
225 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Format of the LCMP Sub-Options</span>
226
227 The LCMP sub-options are used for carrying information elements
228 related to various parameters that need to be configured on the MAG.
229 These sub-options can be included in the LCMP option defined in
230 <a href="#section-3">Section 3</a>. The LCMP sub-options have an alignment requirement of 4n.
231 The format of this sub-option is as follows.
232
233 0 1 2 3
234 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
235 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
236 | LCMP Type | LCMP Length | Sub-Option Data ~
237 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
238
239 Figure 2: LMA-Controlled MAG Parameters Sub-Option
240
241 Type
242
243 8-bit unsigned integer indicating the type of the LCMP sub-option.
244 This specification defines the following types:
245
246 0 - Reserved
247
248 1 - Binding Re-registration Control Sub-Option
249
250 2 - Heartbeat Control Sub-Option
251
252 Length
253
254 8-bit unsigned integer indicating the number of octets needed to
255 encode the Option Data, excluding the LCMP Type and LCMP Length
256 fields of the sub-option.
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276 <span class="grey">Patki, et al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc8127">RFC 8127</a> LMA-Controlled MAG Configuration Parameters August 2017</span>
279
280
281 <span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. Binding Re-registration Control Sub-Option</span>
282
283 The Binding Re-registration Control Sub-Option is a mobility sub-
284 option carried in the LCMP mobility option defined in <a href="#section-3">Section 3</a>.
285 This sub-option carries timer values related to re-registration.
286 There MUST be no more than a single instance of this sub-option in
287 the LCMP option. The format of this sub-option is defined below.
288
289 0 1 2 3
290 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
291 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
292 | LCMP Type = 1 | LCMP Length | Re-registration-Start-Time |
293 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
294 | Initial-Retransmission-Time | Maximum-Retransmission-Time |
295 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
296
297 Figure 3: Binding Re-registration Control Sub-Option
298
299 LCMP Type
300
301 1 for the Binding Re-registration Control Sub-Option.
302
303 LCMP Length
304
305 6
306
307 Re-registration-Start-Time
308
309 16-bit unsigned integer indicating the number of time units before
310 the expiry of the PMIPv6 binding lifetime when the registration
311 refresh process needs to be activated. One time unit is 4
312 seconds.
313
314 Initial-Retransmission-Time
315
316 16-bit unsigned integer indicating minimum delay in seconds before
317 the first Proxy Binding Update (PBU) retransmission of the
318 exponential backoff process.
319
320 Maximum-Retransmission-Time
321
322 16-bit unsigned integer indicating maximum delay in seconds before
323 the last PBU retransmission message of the exponential backoff
324 process.
325
326
327
328
329
330
331
332 <span class="grey">Patki, et al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc8127">RFC 8127</a> LMA-Controlled MAG Configuration Parameters August 2017</span>
335
336
337 <span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a>. Heartbeat Control Sub-Option</span>
338
339 0 1 2 3
340 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
341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
342 | LCMP Type = 2 | LCMP Length | HB-Interval |
343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
344 | HB-Retransmission-Delay | HB-Max-Retransmissions |
345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
346
347 Figure 4: Heartbeat Control Sub-Option
348
349 LCMP Type
350
351 2 for the Heartbeat Control Sub-Option.
352
353 LCMP Length
354
355 6
356
357 HB-Interval
358
359 16-bit unsigned integer indicating the heartbeat interval, i.e.,
360 time delay in seconds after a successful heartbeat exchange
361 (heartbeat request followed by response) when the next heartbeat
362 exchange can be triggered.
363
364 HB-Retransmission-Delay
365
366 16-bit unsigned integer indicating minimum time delay in seconds
367 before a heartbeat message is retransmitted.
368
369 HB-Max-Retransmissions
370
371 16-bit unsigned integer indicating maximum number of heartbeat
372 retransmissions.
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388 <span class="grey">Patki, et al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc8127">RFC 8127</a> LMA-Controlled MAG Configuration Parameters August 2017</span>
391
392
393 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Protocol Configuration Variables</span>
394
395 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Local Mobility Anchor -- Configuration Variables</span>
396
397 This specification defines the following variables to be configured
398 by the system management. The configured values for these protocol
399 variables MUST survive server reboots and service restarts.
400
401 EnableLCMPSubOptReregControl
402
403 This flag indicates the operational state of the Binding
404 Re-registration Control Sub-Option support. The default value of
405 this flag is (0), indicating that support for the Binding
406 Re-registration Control Sub-Option is disabled.
407
408 EnableLCMPSubOptHeartbeatControl
409
410 This flag indicates the operational state of the Heartbeat Control
411 Sub-Option support. The default value of this flag is (0),
412 indicating that support for the Heartbeat Control Sub-Option is
413 disabled.
414
415 The following variables MAY be defined at various granularities such
416 as per binding, per cluster of bindings, per peering MAG, per cluster
417 of peering MAGs, or any other custom grouping. Regardless of the
418 granularity of this configuration, the LMA MUST be able to determine
419 the value of these variables for every individual binding.
420
421 LCMPReregistrationStartTime
422
423 This variable is used to set the minimum time interval in number
424 of seconds before the expiry of the PMIPv6 binding lifetime when
425 the registration refresh process SHOULD be activated. The default
426 value of this variable is 10 units, where each unit is 4 seconds.
427
428 LCMPInitialRetransmissionTime
429
430 This variable is used to set the minimum delay in seconds before
431 the first PBU retransmission of the exponential backoff process.
432 This variable is the same as INITIAL_BINDACK_TIMEOUT mentioned in
433 <a href="./rfc5213#section-6.9.4">Section&nbsp;6.9.4 of [RFC5213]</a>. The default value of this variable is
434 1 second.
435
436
437
438
439
440
441
442
443
444 <span class="grey">Patki, et al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc8127">RFC 8127</a> LMA-Controlled MAG Configuration Parameters August 2017</span>
447
448
449 LCMPMaximumRetransmissionTime
450
451 This variable is used to set the maximum delay in seconds before
452 the last PBU retransmission message of the exponential backoff
453 process. This variable is the same as MAX_BINDACK_TIMEOUT
454 mentioned in <a href="./rfc5213#section-6.9.4">Section&nbsp;6.9.4 of [RFC5213]</a>. The default value of
455 this variable is 32 seconds.
456
457 LCMPHeartbeatInterval
458
459 This variable is used to set the time delay in seconds after a
460 successful heartbeat exchange (heartbeat request followed by
461 response) when the next heartbeat exchange can be triggered. The
462 default value of this variable is 60 seconds. The time delay
463 SHOULD NOT be less than 30 seconds or more than 3600 seconds. The
464 value of this variable MAY be derived from the variable
465 HEARTBEAT_INTERVAL defined in <a href="./rfc5847#section-5">Section&nbsp;5 of [RFC5847]</a> if configured
466 on the LMA.
467
468 LCMPHeartbeatRetransmissionDelay
469
470 This variable is used to set the minimum time delay in seconds
471 before a heartbeat message is retransmitted. The value of this
472 variable SHOULD be less than LCMPHeartbeatInterval. The default
473 value of this variable is 5 seconds.
474
475 LCMPHeartbeatMaxRetransmissions
476
477 This variable is used to set the maximum number of heartbeat
478 retransmissions. The default value of this variable is 3. The
479 value of this variable MAY be derived from the variable
480 MISSING_HEARTBEATS_ALLOWED defined in <a href="./rfc5847#section-5">Section&nbsp;5 of [RFC5847]</a> if
481 configured on the LMA.
482
483 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Protocol Considerations</span>
484
485 The following considerations apply to the LMA and the MAG.
486
487 For supporting this extension, the conceptual Binding Cache Entry
488 data structure maintained by the LMA, described in <a href="./rfc5213#section-5.1">Section&nbsp;5.1 of
489 [RFC5213]</a>, and the conceptual Binding Update List entry data
490 structure maintained by the MAG, described in <a href="./rfc5213#section-6.1">Section&nbsp;6.1 of
491 [RFC5213]</a>, need to be extended to store the information elements
492 related to the LCMP option that are defined below.
493
494 o LCMPReregistrationStartTime
495
496 o LCMPInitialRetransmissionTime
497
498
499
500 <span class="grey">Patki, et al. Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc8127">RFC 8127</a> LMA-Controlled MAG Configuration Parameters August 2017</span>
503
504
505 o LCMPMaximumRetransmissionTime
506
507 o LCMPHeartbeatInterval
508
509 o LCMPHeartbeatRetransmissionDelay
510
511 o LCMPHeartbeatMaxRetransmissions
512
513 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Local Mobility Anchor Considerations</span>
514
515 On receiving a PBU message [<a href="./rfc5213" title="&quot;Proxy Mobile IPv6&quot;">RFC5213</a>] from a MAG, the LMA MUST check
516 if the variable EnableLCMPSubOptReregControl is configured and set to
517 (1). If yes, and if LCMPReregistrationStartTime,
518 LCMPInitialRetransmissionTime, and LCMPMaximumRetransmissionTime are
519 all set to NON_ZERO values, then it MUST include the Binding
520 Re-registration Control Sub-Option in the LCMP mobility option, which
521 is in turn included in the PBA message. If the variable
522 EnableLCMPSubOptReregControl is configured and set to (1), and if any
523 of LCMPReregistrationStartTime, LCMPInitialRetransmissionTime, and
524 LCMPMaximumRetransmissionTime is set to ZERO value, then the LMA MUST
525 report a configuration error and reject the binding request by
526 sending a PBA message with status code '128 - Reason Unspecified'
527 [<a href="./rfc5213" title="&quot;Proxy Mobile IPv6&quot;">RFC5213</a>].
528
529 The LMA MUST also check if variable EnableLCMPSubOptHeartbeatControl
530 is configured and set to (1). If yes, and if LCMPHeartbeatInterval,
531 LCMPHeartbeatRetransmissionDelay, and LCMPHeartbeatMaxRetransmissions
532 are all set to NON_ZERO values, then it MUST include the Heartbeat
533 Control Sub-Option in the LCMP mobility option, which is in turn
534 included in the PBA message. If the variable
535 EnableLCMPSubOptHeartbeatControl is set to (1), and if any of
536 LCMPHeartbeatInterval, LCMPHeartbeatRetransmissionDelay, and
537 LCMPHeartbeatMaxRetransmissions is set to ZERO value, then the LMA
538 MUST report a configuration error and reject the binding request by
539 sending a PBA message with status code '128 - Reason Unspecified'
540 [<a href="./rfc5213" title="&quot;Proxy Mobile IPv6&quot;">RFC5213</a>].
541
542 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Mobile Access Gateway Considerations</span>
543
544 If the PBA message [<a href="./rfc5213" title="&quot;Proxy Mobile IPv6&quot;">RFC5213</a>] received from the LMA contains the LCMP
545 mobility option and the Binding Re-registration Control Sub-Option,
546 then the MAG MUST overwrite the timer parameters related to binding
547 re-registration that are configured locally on the MAG with the
548 parameters received in the Binding Re-registration Control Sub-
549 Option. If any of the parameters in the Binding Re-registration
550 Control Sub-Option are ZERO, then the PBA message MUST be ignored and
551 an error message SHOULD be logged.
552
553
554
555
556 <span class="grey">Patki, et al. Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc8127">RFC 8127</a> LMA-Controlled MAG Configuration Parameters August 2017</span>
559
560
561 Similarly, if the LCMP mobility option contains the Heartbeat Control
562 Sub-Option, then the MAG MUST overwrite the heartbeat-related timer
563 parameters configured locally on the MAG with the parameters received
564 in the Heartbeat Control Sub-Option. If any of the parameters in the
565 Heartbeat Control Sub-Option, except HB-Retransmission-Delay, are
566 ZERO, then the PBA message MUST be ignored and an error message
567 SHOULD be logged.
568
569 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
570
571 IANA has updated the "Mobile IPv6 parameters" registry as described
572 here.
573
574 o Action 1: This specification defines a new mobility header option,
575 "LMA-Controlled MAG Parameters". This mobility option is
576 described in <a href="#section-3">Section 3</a>. The type value 62 has been assigned for
577 this option in the "Mobility Options" registry, as defined in
578 [<a href="./rfc6275" title="&quot;Mobility Support in IPv6&quot;">RFC6275</a>].
579
580 o Action 2: This specification defines a new mobility sub-option
581 format, the LCMP sub-option. The format of this mobility sub-
582 option is described in <a href="#section-3.1">Section 3.1</a>. This sub-option can be
583 carried in the LCMP option. The type values for this sub-option
584 are managed by IANA, under the "LMA-Controlled MAG Parameters Sub-
585 Option Type Values" registry. Per this document, IANA has
586 reserved the following type values. Approval of new LCMP sub-
587 option type values are to be made through Expert Review [<a href="./rfc8126" title="">RFC8126</a>].
588
589 +---+-----------------------------------------------------+
590 | 0 | Reserved |
591 +---+-----------------------------------------------------+
592 | 1 | Binding Re-registration Control Sub-Option |
593 +---+-----------------------------------------------------+
594 | 2 | Heartbeat Control Sub-Option |
595 +---+-----------------------------------------------------+
596
597 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
598
599 The LCMP option defined in this specification allows the
600 configuration of re-registration and heartbeat frequencies. This
601 option is defined for carrying it in Proxy Binding Update and Proxy
602 Binding Acknowledgement messages. This option is carried like any
603 other mobility header option as specified and does not require any
604 special security considerations.
605
606
607
608
609
610
611
612 <span class="grey">Patki, et al. Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc8127">RFC 8127</a> LMA-Controlled MAG Configuration Parameters August 2017</span>
615
616
617 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
618
619 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
620
621 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
622 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
623 DOI 10.17487/RFC2119, March 1997,
624 &lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;.
625
626 [<a id="ref-RFC5213">RFC5213</a>] Gundavelli, S., Ed., Leung, K., Devarapalli, V.,
627 Chowdhury, K., and B. Patil, "Proxy Mobile IPv6",
628 <a href="./rfc5213">RFC 5213</a>, DOI 10.17487/RFC5213, August 2008,
629 &lt;<a href="https://www.rfc-editor.org/info/rfc5213">https://www.rfc-editor.org/info/rfc5213</a>&gt;.
630
631 [<a id="ref-RFC5847">RFC5847</a>] Devarapalli, V., Ed., Koodli, R., Ed., Lim, H., Kant, N.,
632 Krishnan, S., and J. Laganier, "Heartbeat Mechanism for
633 Proxy Mobile IPv6", <a href="./rfc5847">RFC 5847</a>, DOI 10.17487/RFC5847, June
634 2010, &lt;<a href="https://www.rfc-editor.org/info/rfc5847">https://www.rfc-editor.org/info/rfc5847</a>&gt;.
635
636 [<a id="ref-RFC7563">RFC7563</a>] Pazhyannur, R., Speicher, S., Gundavelli, S., Korhonen,
637 J., and J. Kaippallimalil, "Extensions to the Proxy Mobile
638 IPv6 (PMIPv6) Access Network Identifier Option", <a href="./rfc7563">RFC 7563</a>,
639 DOI 10.17487/RFC7563, June 2015,
640 &lt;<a href="https://www.rfc-editor.org/info/rfc7563">https://www.rfc-editor.org/info/rfc7563</a>&gt;.
641
642 [<a id="ref-RFC8174">RFC8174</a>] Leiba, B., "Ambiguity of Uppercase vs Lowercase in <a href="./rfc2119">RFC</a>
643 <a href="./rfc2119">2119</a> Key Words", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc8174">RFC 8174</a>, DOI 10.17487/RFC8174,
644 May 2017, &lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;.
645
646 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
647
648 [<a id="ref-RFC6275">RFC6275</a>] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility
649 Support in IPv6", <a href="./rfc6275">RFC 6275</a>, DOI 10.17487/RFC6275, July
650 2011, &lt;<a href="https://www.rfc-editor.org/info/rfc6275">https://www.rfc-editor.org/info/rfc6275</a>&gt;.
651
652 [<a id="ref-RFC8126">RFC8126</a>] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
653 Writing an IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>,
654 <a href="./rfc8126">RFC 8126</a>, DOI 10.17487/RFC8126, June 2017,
655 &lt;<a href="https://www.rfc-editor.org/info/rfc8126">https://www.rfc-editor.org/info/rfc8126</a>&gt;.
656
657 [<a id="ref-RFC8200">RFC8200</a>] Deering, S. and R. Hinden, "Internet Protocol, Version 6
658 (IPv6) Specification", STD 86, <a href="./rfc8200">RFC 8200</a>,
659 DOI 10.17487/RFC8200, July 2017,
660 &lt;<a href="https://www.rfc-editor.org/info/rfc8200">https://www.rfc-editor.org/info/rfc8200</a>&gt;.
661
662
663
664
665
666
667
668 <span class="grey">Patki, et al. Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc8127">RFC 8127</a> LMA-Controlled MAG Configuration Parameters August 2017</span>
671
672
673 Acknowledgements
674
675 The authors would like to thank the DMM Working Group for all the
676 comments and discussions on this document. The authors would also
677 like to thank Suresh Krishnan, Ralph Droms, Mirja Kuhlewind, Alexey
678 Melnikov, and Ben Campbell for their review feedback.
679
680 The work of Jong-Hyouk Lee was supported by 'The Cross-Ministry Giga
681 KOREA Project' grant from the Ministry of Science, ICT and Future
682 Planning, Korea.
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724 <span class="grey">Patki, et al. Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc8127">RFC 8127</a> LMA-Controlled MAG Configuration Parameters August 2017</span>
727
728
729 Authors' Addresses
730
731 Dhananjay Patki
732 Cisco
733 Cessna Business Park SEZ, Kadubeesanahalli
734 Bangalore, Karnataka 560087
735 India
736
737 Email: [email protected]
738
739
740 Sri Gundavelli
741 Cisco
742 170 West Tasman Drive
743 San Jose, CA 95134
744 United States of America
745
746 Email: [email protected]
747
748
749 Jong-Hyouk Lee
750 Sangmyung University
751 31, Sangmyeongdae-gil, Dongnam-gu
752 Cheonan 31066
753 Republic of Korea
754
755 Email: [email protected]
756
757
758 Qiao Fu
759 China Mobile
760 Xuanwumenxi Ave. No.32
761 Beijing
762 China
763
764 Email: [email protected]
765
766
767 Lyle T. Bertz
768 Sprint
769 Kansas
770 United States of America
771
772 Email: [email protected]
773
774
775
776
777
778
779
780 Patki, et al. Standards Track [Page 14]
781 </pre>