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
|
<pre>Internet Engineering Task Force (IETF) R. Pazhyannur
Request for Comments: 7563 S. Speicher
Updates: <a href="./rfc6757">6757</a> S. Gundavelli
Category: Standards Track Cisco Systems
ISSN: 2070-1721 J. Korhonen
Broadcom Corporation
J. Kaippallimalil
Huawei
June 2015
<span class="h1">Extensions to the Proxy Mobile IPv6 (PMIPv6) Access Network Identifier</span>
<span class="h1">Option</span>
Abstract
The Access Network Identifier (ANI) mobility option was introduced in
<a href="./rfc6757">RFC 6757</a>, "Access Network Identifier (ANI) Option for Proxy Mobile
IPv6". This enables a Mobile Access Gateway (MAG) to convey
identifiers like the network identifier, geolocation, and operator
identifier. This specification extends the Access Network Identifier
mobility option with sub-options to carry the civic location and the
MAG group identifier. This specification also defines an ANI Update-
Timer sub-option that determines when and how often the ANI option
will be updated.
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="./rfc5741#section-2">Section 2 of RFC 5741</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/rfc7563">http://www.rfc-editor.org/info/rfc7563</a>.
<span class="grey">Pazhyannur, 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="./rfc7563">RFC 7563</a> Extensions to ANI June 2015</span>
Copyright Notice
Copyright (c) 2015 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-4">4</a>
<a href="#section-2.1">2.1</a>. Conventions . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2.2">2.2</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3">3</a>. Protocol Extension . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.1">3.1</a>. Civic-Location Sub-Option . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3.2">3.2</a>. MAG-Group-Identifier Sub-Option . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3.3">3.3</a>. ANI Update-Timer Sub-Option . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-4">4</a>. Protocol Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-4.1">4.1</a>. MAG Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-4.2">4.2</a>. LMA Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-5">5</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-7">7</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-7.1">7.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-7.2">7.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<span class="grey">Pazhyannur, 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="./rfc7563">RFC 7563</a> Extensions to ANI June 2015</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
"Access Network Identifier (ANI) Option for Proxy Mobile IPv6"
[<a href="./rfc6757" title=""Access Network Identifier (ANI) Option for Proxy Mobile IPv6"">RFC6757</a>] introduced the ANI mobility option. This enabled a Mobile
Access Gateway (MAG) to provide the Network-Identifier, Geo-Location,
and Operator-Identifier sub-options. When the access network is
WLAN, the Network-Identifier sub-option may contain the Service Set
Identifier (SSID) and the Basic Service Set Identifier (BSSID) of the
Access Point (AP) and the geolocation of the AP, and the Operator-
Identifier may contain the realm of the operator managing the WLAN.
The MAG sends the above information to the Local Mobility Anchor
(LMA). The LMA may use this information to determine access-network-
specific policies (in terms of Quality of Service (QoS), Deep Packet
Inspection (DPI), etc.). Further, the LMA may make this information
available to location-based applications.
While the above mentioned sub-options provide a rich set of
information, in this document we describe the need for extending the
ANI sub-options that are particularly useful in WLAN deployments. In
WLAN deployments (especially indoor AP deployments), it is difficult
to provide geospatial coordinates of APs. At the same time, for many
location-based applications the civic location is sufficient. This
motivates the need for an ANI Civic-Location sub-option. In many
deployments, operators tend to create groups of APs into "AP-Groups".
These groups have a group identifier. The group identifier is used
as a proxy for coarse location (such as the floor of a building or a
small building). The group identifier may also be used to provide a
common policy (e.g., QoS, charging, DPI) for all APs in that group.
This specification provides a sub-option for the MAG to convey a
group identifier to the LMA. The provisioning of the group
identifier is outside the scope of this specification and is
typically done via a configuration mechanism such as CLI (Command-
line Interface) or via Control and Provisioning of Wireless Access
Points (CAPWAP) [<a href="./rfc5415" title=""Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification"">RFC5415</a>] [<a href="./rfc5416" title=""Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Binding for IEEE 802.11"">RFC5416</a>].
This document also provides a new sub-option that determines how
often the MAG will update the ANI. In typical deployments, it is
expected that the MAG will update the ANI as soon as it changes.
This is certainly true when the MAG is co-located with the AP. When
a client roams from one AP to another AP, the MAG on the roamed (or
sometimes referred to as the target) AP will provide the new ANI (for
example, the network identifier and geolocation of the new AP).
However, if the MAG is co-located with an Access Controller (also
known as Wireless LAN Controller (WLC)), then a client roaming from
one AP to another AP does not necessarily perform an ANI update. The
WLC handles client mobility between APs and as a result, intra-WLC
mobility is hidden from the LMA.
<span class="grey">Pazhyannur, 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="./rfc7563">RFC 7563</a> Extensions to ANI June 2015</span>
In such deployments, the information conveyed in the ANI sub-options
(e.g., location) becomes stale and is only refreshed at the time of
lifetime expiry. The MAG could deal with this by sending a Proxy
Binding Update (PBU) whenever a client moves between APs just for the
purpose of updating the ANI sub-option. Alternately, this document
allows the LMA to determine how often it wants to know about the
changes in the ANI sub-option; for example, in some cases the LMA may
not care about the ANI sub-option except at the time of initial
binding, or in some cases it may care about every AP transition. The
sub-option allows the LMA to tell the MAG the desired update
frequency. As always, mobility events or re-registration events will
update the ANI sub-options. The LMA can use the ANI Update-Timer
option to set the maximum frequency at which it wants to receive ANI
updates. This is particularly useful in environments where a MAG
covers a large number of Wi-Fi APs and there is high client mobility
between the APs; for example, in a stadium Wi-Fi deployment, if a LMA
does not want ANI updates any more often than 100 seconds, then it
can propose 100 seconds as the value for ANI Update-Timer.
[<a id="ref-RFC6757">RFC6757</a>] provides ANI sub-options to carry geolocation information.
In this document, we provide additional sub-options to carry the
civic location and group identifier. This document also defines an
ANI sub-option to enable a MAG to communicate how often the MAG will
update the ANI information.
<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", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Terminology</span>
All of the mobility-related terms used in this document are to be
interpreted as defined in [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>] and [<a href="./rfc5844" title=""IPv4 Support for Proxy Mobile IPv6"">RFC5844</a>]. In this document,
Civic Location is defined as follows.
Civic Location: There are two common ways to identify the location
of an object, either through geospatial coordinates or by so-
called civic addresses. Geospatial coordinates indicate
longitude, latitude, and altitude, while civic addresses indicate
a street address or sometimes the location within a building (such
as a room number). Civic location refers to the civic address.
<span class="grey">Pazhyannur, 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="./rfc7563">RFC 7563</a> Extensions to ANI June 2015</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Protocol Extension</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Civic-Location Sub-Option</span>
The Civic-Location is a mobility sub-option carried in the Access
Network Identifier option defined in [<a href="./rfc6757" title=""Access Network Identifier (ANI) Option for Proxy Mobile IPv6"">RFC6757</a>]. This sub-option
carries the civic location information of the mobile node as known to
the MAG. The format of this 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|ANI Type=4 | ANI Length | Format | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| civic location ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Civic-Location Sub-Option
ANI Type: 4
ANI Length: Total length of this sub-option in octets, excluding the
ANI Type and ANI Length fields.
Format: This specifies the encoding format of the civic location.
The value 0 is defined in this specification as described below.
The remaining values (1 through 255) are reserved.
0: This value denotes Binary Encoding. The location format
is based on the encoding format defined in <a href="./rfc4776#section-3.1">Section 3.1 of
[RFC4776]</a>, whereby the first 3 octets are not put into the
civic location field (i.e., the code for the DHCP option,
the length of the DHCP option, and the 'what' element are
not included). What is included is the two-octet country
code field, followed by one or more civic address elements.
The country-code is a two-letter ISO 3166 country code in
capital ASCII letters, e.g., US. The structure of the civic
address elements that follow the country code field is as
defined in <a href="./rfc4776#section-3.3">Section 3.3 of [RFC4776]</a>.
Reserved: This MUST be set to zero when sending and ignored when
received.
civic location: This field will contain the civic location. The
format (encoding) type is specified in the format field of this
sub-option. Note that the length SHALL NOT exceed 253 bytes.
<span class="grey">Pazhyannur, 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="./rfc7563">RFC 7563</a> Extensions to ANI June 2015</span>
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. MAG-Group-Identifier Sub-Option</span>
The MAG group identifier is a mobility sub-option carried in the
Access Network Identifier option defined in [<a href="./rfc6757" title=""Access Network Identifier (ANI) Option for Proxy Mobile IPv6"">RFC6757</a>]. The MAG group
identifier identifies the group affiliation of the MAG within that
Proxy Mobile IPv6 domain. The group identifier is not assumed to be
globally unique across different network operators. However, the
group identifier should be unique within an operator network. In
domains spanning multiple operators, it is recommended that the
Operator-Identifier sub-option (defined in [<a href="./rfc6757" title=""Access Network Identifier (ANI) Option for Proxy Mobile IPv6"">RFC6757</a>]) be used in
addition to the MAG-Group-Identifier sub-option to ensure uniqueness.
When the MAG is configured with a group identifier, the MAG should
send its group identifier in the PBU. Note that the configuration of
this identifier is outside the scope of this specification; the usage
of the identifier by the LMA is left to implementation. 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|ANI Type=5 | ANI Length | group identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: MAG-Group-Identifier Sub-Option
ANI Type: 5
ANI Length: Total length of this sub-option in octets, excluding the
ANI Type and ANI Length fields. The value is always 2.
group identifier: This is a 3-octet unsigned integer value assigned
to a group of MAGs.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. ANI Update-Timer Sub-Option</span>
The ANI Update-Timer is a mobility sub-option carried in the ANI
option defined in [<a href="./rfc6757" title=""Access Network Identifier (ANI) Option for Proxy Mobile IPv6"">RFC6757</a>]. <a href="#section-4">Section 4</a> describes how the MAG and LMA
use this sub-option.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|ANI Type=6 | ANI Length | Update-Timer |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: ANI Update-Timer Sub-Option
<span class="grey">Pazhyannur, 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="./rfc7563">RFC 7563</a> Extensions to ANI June 2015</span>
ANI Type: 6
ANI Length: Total length of this sub-option in octets, excluding the
ANI Type and ANI Length fields. The value is always 2.
Update-Timer: Update-Timer is a 16-bit unsigned integer. The unit
of time is 4 seconds (time unit of 4 seconds ensures consistency
with the time units for the binding lifetime). A value of 0
indicates that the MAG will send an updated ANI mobility option as
soon as it discovers a change in ANI values. A non-zero value
indicates that the MAG may not send ANI values immediately after
they have changed but rather send ANI updates when the
Update-Timer expires.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Protocol Considerations</span>
The following considerations apply to the LMA and the MAG.
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. MAG Considerations</span>
o The conceptual Binding Update List entry data structure maintained
by the mobile access gateway, described in <a href="./rfc5213#section-6.1">Section 6.1 of
[RFC5213]</a>, is extended to store the access-network-related
information elements associated with the current session.
Specifically, the following parameters are defined:
* civic location
* MAG group identifier
* ANI Update-Timer
o If the mobile access gateway is configured to support the Access
Network Information sub-options defined in this specification, it
includes this option with the specific sub-options in all PBU
messages (including PBUs for lifetime extension and for
deregistration) that it sends to the LMA. The Access Network
Information option is constructed as specified in <a href="#section-3">Section 3</a>.
o ANI Update-Timer Considerations: The MAG sets the Update-Timer
based on an exchange of timer values with the LMA. When the ANI
Update-Timer sub-option is carried in a PBU, it is considered as a
proposed value for the Update-Timer. The LMA may change the value
of the Update-Timer received in the PBU. When the LMA-provided
value for the Update-Timer is different than what is sent by the
MAG, the MAG should use the LMA-provided value. If the MAG does
not receive an ANI Update-Timer sub-option in the Proxy Binding
Acknowledgement (PBA) (in response to sending the sub-option in
<span class="grey">Pazhyannur, 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="./rfc7563">RFC 7563</a> Extensions to ANI June 2015</span>
the PBU), then MAG behavior is in accordance to [<a href="./rfc6757" title=""Access Network Identifier (ANI) Option for Proxy Mobile IPv6"">RFC6757</a>]. When
ANI parameters of a mobility session change, the MAG checks
whether the Update-Timer has expired. If the Update-Timer has
expired, the MAG sends a PBU with the ANI option. The ANI option
reflects the updated access network parameters for that mobility
session. If the Update-Timer has not expired, the MAG does not
send a PBU. When the Update-Timer for a mobility session expires,
the MAG checks whether the ANI parameters have changed. If the
parameters have changed from the last reported values, the MAG
sends a PBU with an ANI option. If the parameters have not
changed, the MAG does not send a PBU (and the Update-Timer remains
expired). Note that the MAG may send a PBU even before the
Update-Timer expires. This could be, for example, to initiate a
QoS service request to the LMA (see [<a href="./rfc7222" title=""Quality-of-Service Option for Proxy Mobile IPv6"">RFC7222</a>]). In such cases,
the MAG must reset the Update-Timer when it sends a PBU.
o If the mobile access gateway had any of the Access Network
Information mobility options included in the PBU sent to an LMA,
then the PBA received from the LMA should contain the Access
Network Information mobility option with the specific sub-options.
If the mobile access gateway receives a PBA with a successful
Status Value but without an Access Network Information mobility
option, then the mobile access gateway may log the event and,
based on its local policy, even proceed to terminate the mobility
session. In this case, the mobile access gateway knows the LMA
does not understand the Access Network Information mobility
option.
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. LMA Considerations</span>
o 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>, is extended to
store the access-network-related information elements associated
with the current session. Specifically, the following parameters
are defined:
* civic location
* MAG group identifier
* ANI Update-Timer
o On receiving a PBU message from a MAG with the ANI option, the LMA
must process the option and update the corresponding fields in the
Binding Cache entry. If the option is not understood by that LMA
implementation, it will skip the option and process the PBU
without these options.
<span class="grey">Pazhyannur, 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="./rfc7563">RFC 7563</a> Extensions to ANI June 2015</span>
o If the received PBU message does not include the Access Network
Information option, then the mobility session associated with that
PBU is updated to remove any access network information elements.
o If the LMA understands/supports the Access Network Identifier
mobility sub-options defined in this specification, then the LMA
echoes the Access Network Identifier mobility option with the
specific sub-option(s) that it accepted back to the mobile access
gateway in a PBA. The Civic-Location and MAG-Group-Identifier
sub-options defined in this specification should not be altered by
the LMA. The LMA may change the value of the ANI Update-Timer
sub-option. It may choose to either echo the same value or
increase or decrease the timer value. For example, if the LMA
does not want to receive frequent updates (as implied by the timer
value), it may choose to increase the value. Similarly, if the
LMA needs to receive ANI updates as soon as possible, then it may
set the value to zero (0) in the PBA.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
IANA has registered the values described below.
o This specification defines a new Access Network Identifier sub-
option called the Civic-Location sub-option. This mobility sub-
option is described in <a href="#section-3.1">Section 3.1</a> and this sub-option can be
carried in the Access Network Identifier mobility option. The
type value <4> has been allocated from the registry "Access
Network Information (ANI) Sub-Option Type Values".
o This specification defines a new Access Network Identifier sub-
option called the MAG-Group-Identifier sub-option. This mobility
sub-option is described in <a href="#section-3.2">Section 3.2</a> and this sub-option can be
carried in Access Network Identifier mobility option. The type
value <5> has been allocated from the registry "Access Network
Information (ANI) Sub-Option Type Values".
o This specification defines a new Access Network Identifier sub-
option called the ANI Update-Timer sub-option. This sub-option is
described in <a href="#section-3.3">Section 3.3</a> and this sub-option can be carried in the
Access Network Identifier mobility option. The type value <6> has
been allocated from the registry "Access Network Information (ANI)
Sub-Option Type Values".
<span class="grey">Pazhyannur, 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="./rfc7563">RFC 7563</a> Extensions to ANI June 2015</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
The Civic-Location sub-option defined in this specification is
carried in the Access Network Identifier option defined in [<a href="./rfc6757" title=""Access Network Identifier (ANI) Option for Proxy Mobile IPv6"">RFC6757</a>].
This sub-option is carried in PBU and PBA messages. This sub-option
is carried like any other Access Network Identifier sub-option as
defined in [<a href="./rfc6757" title=""Access Network Identifier (ANI) Option for Proxy Mobile IPv6"">RFC6757</a>]. Therefore, it inherits its security guidelines
from [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>] and [<a href="./rfc6757" title=""Access Network Identifier (ANI) Option for Proxy Mobile IPv6"">RFC6757</a>] and does not require any additional
security considerations.
The Civic-Location sub-option exposes the civic location of the
network to which the mobile node is attached. This information is
considered to be very sensitive, so care must be taken to secure the
Proxy Mobile IPv6 signaling messages when carrying this sub-option.
The base Proxy Mobile IPv6 specification [<a href="./rfc5213" title=""Proxy Mobile IPv6"">RFC5213</a>] specifies the use
of IPsec for securing the signaling messages, and those mechanisms
can be enabled for protecting this information. Operators can
potentially apply IPsec Encapsulating Security Payload (ESP) with
confidentiality and integrity protection for protecting the location
information. The other way to protect the sensitive location
information of network users is of course to not send it in the first
place. Users of the Civic-Location sub-option should provision
location values with the highest possible level of granularity, e.g.,
to the province or city level rather than provisioning specific
addresses.
Access-network-specific information elements that the mobile access
gateway sends may have been dynamically learned over DHCP or using
other protocols. If proper security mechanisms are not in place, the
exchanged information between the MAG and LMA may be compromised.
This situation may result in incorrect service policy enforcement at
the LMA and impact other services that depend on this access network
information. This threat can be mitigated by ensuring the
communication path between the mobile access gateway and the access
points is properly secured by the use of IPsec, Transport Layer
Security (TLS), or other security protocols.
<span class="grey">Pazhyannur, 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="./rfc7563">RFC 7563</a> Extensions to ANI June 2015</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.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="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>>.
[<a id="ref-RFC4776">RFC4776</a>] Schulzrinne, H., "Dynamic Host Configuration Protocol
(DHCPv4 and DHCPv6) Option for Civic Addresses
Configuration Information", <a href="./rfc4776">RFC 4776</a>,
DOI 10.17487/RFC4776, November 2006,
<<a href="http://www.rfc-editor.org/info/rfc4776">http://www.rfc-editor.org/info/rfc4776</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="http://www.rfc-editor.org/info/rfc5213">http://www.rfc-editor.org/info/rfc5213</a>>.
[<a id="ref-RFC5844">RFC5844</a>] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy
Mobile IPv6", <a href="./rfc5844">RFC 5844</a>, DOI 10.17487/RFC5844, May 2010,
<<a href="http://www.rfc-editor.org/info/rfc5844">http://www.rfc-editor.org/info/rfc5844</a>>.
[<a id="ref-RFC6757">RFC6757</a>] Gundavelli, S., Ed., Korhonen, J., Ed., Grayson, M.,
Leung, K., and R. Pazhyannur, "Access Network Identifier
(ANI) Option for Proxy Mobile IPv6", <a href="./rfc6757">RFC 6757</a>,
DOI 10.17487/RFC6757, October 2012,
<<a href="http://www.rfc-editor.org/info/rfc6757">http://www.rfc-editor.org/info/rfc6757</a>>.
[<a id="ref-RFC7222">RFC7222</a>] Liebsch, M., Seite, P., Yokota, H., Korhonen, J., and S.
Gundavelli, "Quality-of-Service Option for Proxy Mobile
IPv6", <a href="./rfc7222">RFC 7222</a>, DOI 10.17487/RFC7222, May 2014,
<<a href="http://www.rfc-editor.org/info/rfc7222">http://www.rfc-editor.org/info/rfc7222</a>>.
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
[<a id="ref-RFC5415">RFC5415</a>] Calhoun, P., Ed., Montemurro, M., Ed., and D. Stanley,
Ed., "Control And Provisioning of Wireless Access Points
(CAPWAP) Protocol Specification", <a href="./rfc5415">RFC 5415</a>,
DOI 10.17487/RFC5415, March 2009,
<<a href="http://www.rfc-editor.org/info/rfc5415">http://www.rfc-editor.org/info/rfc5415</a>>.
[<a id="ref-RFC5416">RFC5416</a>] Calhoun, P., Ed., Montemurro, M., Ed., and D. Stanley,
Ed., "Control and Provisioning of Wireless Access Points
(CAPWAP) Protocol Binding for IEEE 802.11", <a href="./rfc5416">RFC 5416</a>,
DOI 10.17487/RFC5416, March 2009,
<<a href="http://www.rfc-editor.org/info/rfc5416">http://www.rfc-editor.org/info/rfc5416</a>>.
<span class="grey">Pazhyannur, 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="./rfc7563">RFC 7563</a> Extensions to ANI June 2015</span>
Acknowledgements
This document benefited considerably from the numerous improvements
proposed by Kent Leung.
Authors' Addresses
Rajesh S. Pazhyannur
Cisco Systems
170 West Tasman Drive
San Jose, California 95134
United States
EMail: rpazhyan@cisco.com
Sebastian Speicher
Cisco Systems
Richtistrasse 7
Wallisellen, Zurich 8304
Switzerland
EMail: sespeich@cisco.com
Sri Gundavelli
Cisco Systems
170 West Tasman Drive
San Jose, California 95134
United States
EMail: sgundave@cisco.com
Jouni Korhonen
Broadcom Corporation
3151 Zanker Road
San Jose, California 95134
United States
EMail: jouni.nospam@gmail.com
John Kaippallimalil
Huawei
5340 Legacy Drive, Suite 175
Plano, Texas 75024
United States
EMail: john.kaippallimalil@huawei.com
Pazhyannur, et al. Standards Track [Page 12]
</pre>
|
