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