idnits 2.17.1 draft-pazhyannur-netext-civic-location-ani-subopt-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC6757]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 3, 2014) is 3705 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC5415' is defined on line 423, but no explicit reference was found in the text Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 NETEXT WG R. Pazhyannur 3 Internet-Draft S. Speicher 4 Intended status: Standards Track S. Gundavelli 5 Expires: September 4, 2014 Cisco 6 J. Korhonen 7 Broadcom 8 J. Kaippallimalil 9 Huawei 10 March 3, 2014 12 Extensions to the PMIPv6 Access Network Identifier Option 13 draft-pazhyannur-netext-civic-location-ani-subopt-02.txt 15 Abstract 17 Access Network Identifier (ANI) Mobility option was introduced in 18 [RFC6757] enabling a MAG to convey information like network 19 identifier, geo-location, operator-identifier. This specification 20 extends Access Network Identifier mobility option with sub-options to 21 carry Civic Location and MAG Group Identifer This specificaton also 22 defines a ANI update timer sub-option that informs the the LMA when 23 (and how often) the ANI will be updated. 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on September 4, 2014. 42 Copyright Notice 44 Copyright (c) 2014 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 60 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 3 61 2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3 62 2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 63 3. Protocol Extension . . . . . . . . . . . . . . . . . . . . . 4 64 3.1. Civic-Location Sub-Option . . . . . . . . . . . . . . . . 4 65 3.2. MAG Group-Id Sub-Option . . . . . . . . . . . . . . . . . 5 66 3.3. ANI Update-Timer Sub-Option . . . . . . . . . . . . . . . 5 67 4. Protocol Considerations . . . . . . . . . . . . . . . . . . . 6 68 4.1. MAG Considerations . . . . . . . . . . . . . . . . . . . 6 69 4.2. LMA Considerations . . . . . . . . . . . . . . . . . . . 7 70 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 71 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 72 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 73 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 74 8.1. Normative References . . . . . . . . . . . . . . . . . . 9 75 8.2. Informative References . . . . . . . . . . . . . . . . . 10 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 78 1. Introduction 80 [RFC6757] introduced the Access Network Identifier (ANI) mobility 81 Option. This enabled a MAG to provide the Network Identifier, Geo- 82 Location, and Operator-Identifier sub options. When the access 83 network is WLAN, the Network Identiifer sub option may contain SSID, 84 and BSSID of the Access Point (AP), the Geo-Location may contain the 85 latitude/longitude of the AP, and the Operator-Identifier may contain 86 the realm of the operator managing the WLAN. The MAG sends the above 87 information is sent to the LMA. The LMA may use this information to 88 determine access network specific policies (in terms of QoS, DPI, 89 etc). Further, the LMA may make this information available to 90 location based applications. 92 While the above mentioned sub-options provide a rich set of 93 information, in this document we describe the need for extending the 94 ANI sub options, especially relevant for WLAN deployments. In many 95 deployments (especially indoor AP deployments), it is difficult to 96 provide Geo-spatial coordinates of APs. However, for many location 97 based applications the civic location is sufficient. This motivates 98 the need for a ANI civic-location sub-option. In many deployments, 99 operators tend to create groups of APs into "AP-Groups". These 100 groups have a group identifier. The group-identifier is used a proxy 101 for coarse location (such as floor of a building, or a small 102 building). The group identifier may also be used to provide a common 103 policy (e.g., QoS, charging, DPI) for all APs in that group. This 104 specification provides a sub-option for the MAG to convey a group- 105 identifier to the LMA. (The provisioning of the group-identifier is 106 outside the scope of this specification and is typically done via a 107 configuration mechanism such as CLI (Command line Interface), CAPWAP 108 [RFC5416], etc. This document also provides a new sub-option that 109 determines how often the MAG will update the ANI. In typical 110 deployments, it is expected that the MAG will update the ANI as soon 111 as it changes. This is certainly true when the MAG is co-located 112 with the AP. When a client roams from one AP to another AP, the MAG 113 on the roamed AP will provide the new ANI (for example the network 114 identifier and Geo-location of the new AP). However, if the MAG is 115 co-located with an Access Controller (also known as Wireless LAN 116 Controller), then a client roaming from one AP to another AP may not 117 neceesarily require an ANI update. This leads to stale ANI 118 information at the LMA. To cover both cases, ANI is always fresh, 119 ANI may be stale, we introduce a new ANI Update Timer option. This 120 enables the MAG to inform the LMA when and how often the MAG will 121 update the ANI. The MAG sends an ANI update only if the ANI Update 122 Timer has expired and the ANI values have changed since the last ANI 123 update. Consequently, this enables the LMA to determine whether i 124 the ANI is stale or not and when to expect an update. The LMA can 125 use ANI update Timer option to set the maximum frequency at which it 126 wants to receive ANI updates. This may be particularly useful in 127 environments where a MAG covers a large number of Wi-Fi APs and there 128 is high client mobility between the APs (for example in a stadium Wi- 129 Fi deployment). 131 [RFC6757] provides ANI sub-options to carry geo-location information. 132 In this document we provide additional sub-options to carry civic- 133 location, and AP-Group identifer. This documents also defines an ANI 134 sub-option to enable a MAG to communicate how often the MAG will 135 update the ANI information. 137 2. Conventions and Terminology 139 2.1. Conventions 141 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 142 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 143 document are to be interpreted as described in RFC 2119 [RFC2119]. 145 2.2. Terminology 147 All the mobility related terms used in this document are to be 148 interpreted as defined in [RFC5213] and [RFC5844]. 150 3. Protocol Extension 152 3.1. Civic-Location Sub-Option 154 The Civic-Location is a mobility sub-option carried in the Access 155 Network Identifier option defined in [RFC6757]. This sub-option 156 carries the Civic Location information of the mobile node as known to 157 the MAG. The format of this option is defined below. 159 0 1 2 3 160 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 161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 162 | ANI Type=IANA | ANI Length | Format | Reserved | 163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 164 | Civic Location ~ 165 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 167 Figure 1: Network-Identifier Sub-option 169 ANI Type: 171 ANI Length: Total length of this sub option in octets, excluding the 172 ANI Type and ANI length fields. 174 Format: This specifies the encoding format of the Civic location. 175 Two values are defined in this specification. 177 0: This value denotes Binary Encoding. The location format is 178 based on the encoding format defined in Section 3.1 of 179 [RFC4776], whereby the first 3 octets are not put into the 180 Civic Location field (i.e., the code for the DHCP option, the 181 length of the DHCP option, and the 'what' element are not 182 included). 184 1: This value denotes XML Encoding. This is specified in the 185 Presence Information Data Format Location Object [RFC5139]. 187 Civic Location: This field will contain the Civic Location. The 188 format (encoding) type is specified in the format field of this 189 sub option. Note that the length shall not exceed 252 bytes. 191 3.2. MAG Group-Id Sub-Option 193 The MAG Group Identifier is a mobility sub-option carried in the 194 Access Network Identifier option defined in [RFC6757]. The MAG Group 195 Identifier identifies the group affiliation of the MAG within that 196 Proxy Mobile IPv6 domain. When the MAG is configured with a group 197 identifier, the MAG may send its group-id in the PBU. (The 198 configuration of this group identifier is outside the scope of this 199 specification. The usage of the group identifier by the LMA is left 200 to implementation. ) The format of this option is defined below. 202 0 1 2 3 203 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 204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 205 | ANI Type=IANA | ANI Length | Reserved | 206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 207 | Group Identifier | 208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 210 Figure 2: MAG Group-Identifier Sub-option 212 ANI Type: 214 ANI Length: Total length of this sub option in octets, excluding the 215 ANI Type and ANI length fields. The value is always 6. 217 Reserved: MUST be set to zero when sending and ignored when 218 received. 220 Group Identifier: 222 3.3. ANI Update-Timer Sub-Option 224 The ANI Update Timer is a mobility sub-option carried in the ANI 225 option defined in [RFC6757]. Section 4 describes how the MAG and LMA 226 may use this sub option. 228 0 1 2 3 229 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 230 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 231 | ANI Type=IANA | ANI Length | Reserved | 232 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 233 | Update-Timer | 234 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 236 Figure 3: Network-Identifier Sub-option 238 ANI Type: 240 ANI Length: Total length of this sub option in octets, excluding the 241 ANI Type and ANI length fields is always 6. 243 Reserved: MUST be set to zero when sending and ignored when 244 received. 246 Update-Timer: Update-Timer is a 16 bit unsigned integer. It 247 indicates the time in seconds before the MAG sends an update value 248 of ANI mobility options. A value of 0 indicates that the MAG will 249 send an updated ANI mobility option as soon as it discovers a 250 change in ANI values. 252 4. Protocol Considerations 254 The following considerations apply to the LMA and the MAG. 256 4.1. MAG Considerations 258 o The conceptual Binding Update List entry data structure maintained 259 by the mobile access gateway, described in Section 6.1 of 260 [RFC5213], MUST be extended to store the access-network-related 261 information elements associated with the current session. 262 Specifically, the following parameters MUST be defined: 264 * Civic Location 266 * MAG Group-Id 268 * ANI Update-Timer 270 o ANI Update Timer Considerations: The MAG sets the update timer 271 when it sends a PBU with the ANI Update Timer sub option. When 272 the update-timer expires, if the ANI options have changed, the MAG 273 sends an PBU with update ANI. if the ANI options have not 274 changed, the MAG does not send a PBU. It sends an PBU with 275 updated ANI values only when the ANI changes. The Update timer is 276 reset when the PBU is sent. When the Update-Timer Sub option is 277 carried in a PBU, it is considered as a proposed value for the 278 update-timer. When the Update-Timer sub option is carried in a 279 PBA, then it is considered as an accepted value for the update- 280 timer. If the MAG does not receive a update-timer sub option in 281 PBA (in response to sending the sub-option in the PBU), then MAG 282 behavior with respect to updating the ANI values is left to 283 implementation choices. 285 4.2. LMA Considerations 287 o The conceptual Binding Cache entry data structure maintained by 288 the local mobility anchor, described in Section 5.1 of [RFC5213], 289 MUST be extended to store the access-network-related information 290 elements associated with the current session. Specifically, the 291 following parameters MUST be defined: 293 * Civic Location 295 * MAG Group-Id 297 * ANI Update-Timer 299 o On receiving a Proxy Binding Update message [RFC5213] from a 300 mobile access gateway with the Access Network Information option, 301 the local mobility anchor must process the option and update the 302 corresponding fields in the Binding Cache entry. If the option is 303 not understood by that LMA implementation, it will skip the 304 option. 306 o If the local mobility anchor understands/supports the Access 307 Network Identifier mobility sub-options defined in this 308 specification, then the local mobility anchor MUST echo the Access 309 Network Identifier mobility option with the specific sub-option(s) 310 that it accepted back to the mobile access gateway in a Proxy 311 Binding Acknowledgement. The Access Network Identifier sub- 312 options defined in this specification MUST NOT be altered by the 313 local mobility anchor with the exception of the ANI Update Timer 314 sub-option. 316 o ANI Update Timer Considerations: When the LMA receives this sub 317 option, it may choose to change the value of this sub-option in 318 the PBA. For example, if the LMA does not want to receive 319 frequent updates (as indicated by the timer value) it may choose 320 to increase the value. Similarly, if the LMA needs to receive ANI 321 updates as soon as possible then it may set the value to zero (0) 322 in the PBA. 324 5. IANA Considerations 326 This document requires the following IANA action. 328 o Action-1: This specification defines a new Access Network 329 Identifier sub-option called Civic Location Sub-option. This 330 mobility sub-option is described in Section 3.1 and this sub- 331 option can be carried in Access Network Identifier mobility 332 option. The type value for this sub-option needs to be 333 allocated from the registry "Access Network Information (ANI) Sub- 334 Option Type Values". RFC Editor: Please replace in 335 Section 3.1 with the assigned value, and update this section 336 accordingly. 338 o Action-2: This specification defines a new Access Network 339 Identifier sub-option called MAG Group Identifier Sub-option. 340 This mobility sub-option is described in Section 3.2 and this sub- 341 option can be carried in Access Network Identifier mobility 342 option. The type value for this sub-option needs to be 343 allocated from the registry "Access Network Information (ANI) Sub- 344 Option Type Values". RFC Editor: Please replace in 345 Section 3.2 with the assigned value, and update this section 346 accordingly. 348 o Action-3: This specification defines a new Access Network 349 Identifier sub-option called ANI-Update-Timer Sub-option. This 350 sub-option is described in Section 3.3 and this sub-option can be 351 carried in Access Network Identifier mobility option. The type 352 value for this sub-option needs to be allocated from the 353 registry "Access Network Information (ANI) Sub-Option Type 354 Values". RFC Editor: Please replace in Section 3.3 with 355 the assigned value, and update this section accordingly. 357 6. Security Considerations 359 The Civic Location and the ANI-Update-Frequency sub-Options defined 360 in this specification are to be carried in the Access Network 361 Identifier option defined in [RFC6757]. This sub-option is carried 362 in Proxy Binding Update and Proxy Binding Acknowledgement messages. 363 This sub-option is carried like any other Access Network Identifier 364 sub-option as defined in [RFC6757]. Therefore, it inherits from 365 [RFC5213] and [RFC6757], its security guidelines and does not require 366 any additional security considerations. 368 The Civic Location sub-option carried in the Access Network 369 Information option exposes the civic location of the network to which 370 the mobile node is attached. This information is considered to be 371 very sensitive, so care must be taken to secure the Proxy Mobile IPv6 372 signaling messages when carrying this sub-option. The base Proxy 373 Mobile IPv6 specification [RFC5213] specifies the use of IPsec for 374 securing the signaling messages, and those mechanisms can be enabled 375 for protecting this information. Operators can potentially apply 376 IPsec Encapsulating Security Payload (ESP) with confidentiality and 377 integrity protection for protecting the location information. 379 Access-network-specific information elements that the mobile access 380 gateway sends may have been dynamically learned over DHCP or using 381 other protocols. If proper security mechanisms are not in place, the 382 exchanged information may be potentially compromised with the mobile 383 access gateway sending incorrect access network parameters to the 384 local mobility anchor. This situation may potentially result in 385 incorrect service policy enforcement at the local mobility anchor and 386 impact to other services that depend on this access network 387 information. This threat can be mitigated by ensuring the 388 communication path between the mobile access gateway and the access 389 points is properly secured by the use of IPsec, Transport Layer 390 Security (TLS), or other security protocols. 392 7. Acknowledgements 394 TBD 396 8. References 398 8.1. Normative References 400 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 401 Requirement Levels", BCP 14, RFC 2119, March 1997. 403 [RFC4776] Schulzrinne, H., "Dynamic Host Configuration Protocol 404 (DHCPv4 and DHCPv6) Option for Civic Addresses 405 Configuration Information", RFC 4776, November 2006. 407 [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location 408 Format for Presence Information Data Format Location 409 Object (PIDF-LO)", RFC 5139, February 2008. 411 [RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K., 412 and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008. 414 [RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy 415 Mobile IPv6", RFC 5844, May 2010. 417 [RFC6757] Gundavelli, S., Korhonen, J., Grayson, M., Leung, K., and 418 R. Pazhyannur, "Access Network Identifier (ANI) Option for 419 Proxy Mobile IPv6", RFC 6757, October 2012. 421 8.2. Informative References 423 [RFC5415] Calhoun, P., Montemurro, M., and D. Stanley, "Control And 424 Provisioning of Wireless Access Points (CAPWAP) Protocol 425 Specification", RFC 5415, March 2009. 427 [RFC5416] Calhoun, P., Montemurro, M., and D. Stanley, "Control and 428 Provisioning of Wireless Access Points (CAPWAP) Protocol 429 Binding for IEEE 802.11", RFC 5416, March 2009. 431 Authors' Addresses 433 Rajesh S. Pazhyannur 434 Cisco 435 170 West Tasman Drive 436 San Jose, CA 95134 437 USA 439 Email: rpazhyan@cisco.com 441 Sebastian Speicher 442 Cisco 443 Richtistrasse 7 444 Wallisellen, Zurich 8304 445 Switzerland 447 Email: sespeich@cisco.com 449 Sri Gundavelli 450 Cisco 451 170 West Tasman Drive 452 San Jose, CA 95134 453 USA 455 Email: sgundave@cisco.com 456 Jouni Korhonen 457 Broadcom 458 Porkkalankatu 24 459 Helsinki FIN-00180 460 Finland 462 Email: jouni.nospam@gmail.com 464 John Kaippallimalil 465 Huawei 466 5340 Legacy Drive, Suite 175 467 Plano, Texas 75024 468 USA 470 Email: john.kaippallimalil@huawei.com