idnits 2.17.1 draft-delcarpio-6lo-wlanah-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 17, 2015) is 3208 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) == Missing Reference: 'TBD' is mentioned on line 530, but not defined == Unused Reference: 'RFC4193' is defined on line 610, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE802.11ah' == Outdated reference: A later version (-17) exists of draft-ietf-6lo-btle-11 == Outdated reference: A later version (-16) exists of draft-ietf-6man-default-iids-03 == Outdated reference: A later version (-11) exists of draft-vanderstok-core-comi-06 -- Obsolete informational reference (is this intentional?): RFC 4941 (Obsoleted by RFC 8981) Summary: 0 errors (**), 0 flaws (~~), 6 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 6Lo Working Group L.F. Del Carpio Vega 3 Internet-Draft M.I. Robles 4 Intended status: Standards Track R. Morabito 5 Expires: December 19, 2015 Ericsson 6 June 17, 2015 8 IPv6 over 802.11ah 9 draft-delcarpio-6lo-wlanah-00 11 Abstract 13 IEEE 802.11 is an established Wireless LAN (WLAN) technology which 14 provides radio connectivity to a wide range of devices. The IEEE 15 802.11ah amendment defines a WLAN system operating at sub 1 GHz 16 license-exempt bands designed to operate with low-rate/low-power 17 consumption. This amendment supports large number of stations and 18 extends the radio coverage to several hundreds of meters. This 19 document describes how IPv6 is transported over 802.11ah using 20 6LoWPAN techniques. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on December 19, 2015. 39 Copyright Notice 41 Copyright (c) 2015 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Terminology and Language Requirements . . . . . . . . . . . . 3 58 3. Overview of 802.11ah . . . . . . . . . . . . . . . . . . . . 3 59 3.1. Link layer topology of 802.11ah . . . . . . . . . . . . . 4 60 3.2. Device Addressing and Frame Structure . . . . . . . . . . 5 61 3.3. Protocol Version 0 . . . . . . . . . . . . . . . . . . . 5 62 3.4. Protocol Version 1 . . . . . . . . . . . . . . . . . . . 6 63 3.5. Link Layer Control . . . . . . . . . . . . . . . . . . . 7 64 4. Uses Cases . . . . . . . . . . . . . . . . . . . . . . . . . 7 65 5. 6LoWPAN over 802.11ah . . . . . . . . . . . . . . . . . . . . 8 66 6. Stateless address autoconfiguration . . . . . . . . . . . . . 9 67 7. Neighbour Discovery in 802.11ah . . . . . . . . . . . . . . . 10 68 8. Header compression . . . . . . . . . . . . . . . . . . . . . 10 69 9. Fragmentation . . . . . . . . . . . . . . . . . . . . . . . . 11 70 10. Multicast at IP level . . . . . . . . . . . . . . . . . . . . 11 71 11. Internet Connection . . . . . . . . . . . . . . . . . . . . . 11 72 12. Management of the Network . . . . . . . . . . . . . . . . . . 11 73 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 74 14. Security Considerations . . . . . . . . . . . . . . . . . . . 12 75 15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 76 16. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 77 16.1. Normative References . . . . . . . . . . . . . . . . . . 12 78 16.2. Informative References . . . . . . . . . . . . . . . . . 13 79 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 81 1. Introduction 83 IEEE 802.11 [IEEE802.11], also known as Wi-Fi, is an established 84 Wireless LAN (WLAN) technology operating in unlicensed Industrial, 85 Scientific and Medical (ISM) bands. Its IEEE 802.11ah [IEEE802.11ah] 86 amendment is tailored for Internet of Things (IoT) use-cases and at 87 the moment of writing this draft it is in the final stages of IEEE 88 standardization. 90 IEEE 802.11ah operates in the Sub-1 GHz spectrum which helps reducing 91 the power consumption. It also supports a larger number of stations 92 on a single Basic Service Set (BSS) and it provides power-saving 93 mechanisms that allow radio stations to sleep in order to save power. 94 However, the system achieves lower throughput compared to 802.11n/ac 95 amendments. 97 IEEE 802.11 specifies only the MAC and PHY layers of the radio 98 technology. In other words, 802.11 does not specify a networking 99 layer but it is compatible with commonly used internet protocol such 100 as IPv4 and IPv6. As 802.11ah is a low-rate/low-power technology, 101 the communication protocols used above MAC should also take power- 102 efficiency into consideration. This motivates the introduction of 103 6LoWPAN techniques [RFC4944] [RFC6282] for efficient transport of 104 IPv6 packets over IEEE 802.11ah radio networks. 106 This document specifies how to use 6LoWPAN techniques for 802.11ah. 107 Similar work has been carried out for Bluetooth Low Energy in 108 [I-D.ietf-6lo-btle]. 110 2. Terminology and Language Requirements 112 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 113 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 114 document are to be interpreted as described in RFC 2119 [RFC2119]. 116 Terminology from 802.11ah: 118 Station (STA): defined in 802.11-2012 [IEEE802.11-2012] as a wireless 119 station which is an addressable unit. 121 Sensor-STA: defined in 802.11ah as a device having low-power 122 consumption requirements. This device might be a battery operated 123 device. 125 Non-sensor STA: defined in 802.11ah as device which usually does not 126 have low-power consumption requirements. 128 In this document, any type STA (sensor STA/non-sensor STA) is 129 associated with a 6LoWPAN Nodes(6LN). 131 Access Point (AP): entity maintaining the WLAN Basic Service Set 132 (BSS) and is associated with the 6LoWPAN Border Router (6LBR). It is 133 assumed that APs are connected to the power-line. 135 The terms 6LoWPAN Router (6LR) and 6LoWPAN Border Router (6LBR) are 136 defined as in [RFC6775] and in this context 6LoWPAN Nodes (6LN) do 137 not refer to a router (Access Point), just to a host (STA). 139 3. Overview of 802.11ah 141 The IEEE 802.11 technology uses the unlicensed spectrum in different 142 ISM bands, using CSMA/CA techniques. Specifically 802.11ah is 143 designed to operate in ISM band below Sub-1 Ghz with a bandwidth of 144 1Mhz/2Mhz (depending of configuration). The system is formed by an 145 Access Point (AP) which maintains a Basic Service Set (BSS) and 146 stations (STAs). STAs are connected to the AP in a star topology. 148 The 802.11ah is more energy efficient compared to other conventional 149 802.11 technologies because of the lower operating frequency and the 150 use of mechanisms which allow STAs to doze periodically and request 151 downlink data when switching to active mode i.e. Traffic Indication 152 Map (TIM) operation, non-TIM operation, Target Wakeup Time (TWT) 154 An exemplary deployment of a 802.11ah BSS may include a large number 155 of STAs associated to a BSS where STAs are sleeping (dozing) most of 156 the time and they may monitor periodic beacon-frame transmissions 157 containing Traffic Indication Maps (TIM). Data packets intended to 158 STAs cannot be delivered when STAs sleep, thus the TIM indicates 159 which STAs have downlink data buffered at the AP. After reading the 160 TIM, STAs request their buffered data by transmitting a Power-Saving 161 Poll (PS-Poll) frame to the AP. After the downlink data is 162 delivered, STAs enter into sleep mode again. For uplink data 163 delivery, STAs might transmit as soon as it has data available. 165 There might be STAs that do not monitor constantly the TIM and 166 request downlink data sporadically after waking up. 168 3.1. Link layer topology of 802.11ah 170 The 802.11ah defines a star topology at L2 link connectivity, where 171 the STAs are connected to the AP and any communication between STAs 172 passes through the AP. The mesh topology at L2 level is not defined 173 in 802.11ah. In addition, the wireless communication between Access 174 Points is not supported directly in 802.11ah. However, it is 175 possible to set-up a mesh of APs with the IEEE 802.11s amendment 176 which is out of scope of this document. Finally, the 802.11 standard 177 does not define its own networking layer but is compatible with 178 commonly used protocols e.g. IPv4, IPv6. 180 +---+ 181 |STA| 182 +-+-+ 183 +---+ | 184 |STA+------+ | 185 +---+ | | 186 +---+---+ +---+ 187 | AP +----+STA| 188 ++-----++ +---+ 189 +----+ | | 190 |STA +-----+ | 191 +----+ +-+--+ 192 |STA | 193 +----+ 195 Figure 1: Link Layer Topology 197 It is important to note that the communication link is unidirectional 198 at any given point in time and that the medium is shared by CSMA/CA 199 techniques which avoid that two or more STAs utilize the medium 200 simultaneously. 202 3.2. Device Addressing and Frame Structure 204 The 802.11 physical transmission is composed by a preamble which is 205 used to prepare a receiver for frame decoding, basic physical layer 206 information, and the physical layer payload which encapsulates the 207 MAC Protocol Data Unit (MPDU). 209 There can be different classes of MAC frames in 802.11, the MAC data 210 frame is the only one carrying higher layer data. Other frames are 211 control and management frames which are used to maintain MAC layer 212 functions. The 802.11/802.11ah MAC addresses use the EUI-48 bit 213 address space. 215 A MAC Data frame in 802.11 is composed by a MAC header, a MAC payload 216 and a Frame Check Sequence (FCS) which are encoded in an MPDU. The 217 MAC payload carries Link Layer Control PDUs which encapsulates for 218 example IP packets. There are two protocol versions for MAC frame 219 formats, the Protocol Version 0 (PV0) is used in systems existing 220 before 802.11ah such as 802.11n/ac and the Protocol Version 1 (PV1) 221 has less overhead that PV0 specified in 802.11ah. 223 Segmentation at MAC layer is possible if required. 225 3.3. Protocol Version 0 227 The elements of the MAC data frame with PV0 is depicted in the 228 picture below. 230 +-------+--------+----+----+----+------+----+-----+----+-------+---+ 231 +Frame +Dura + A1 + A2 + A3 + Seq. + A4 + QoS + HT + Frame +FCS+ 232 +Control+tion/ID + + + + Ctrl + + Crl +Crl + Body + + 233 +-------+--------+----+----+----+------+----+-----+----+-------+---+ 234 2 2 6 6 6 2 6 2 4 0-7951 4 236 Figure 2: MAC frame PV0 238 Frame Control: contains information relevant in link layer such as 239 the Protocol Version, frame type and subtype, Power Management, 240 Fragmentation Information, among others. 242 A1: indicates the recipient of the frame and it contains the 6-bytes 243 MAC address or the Short ID (2-bytes) provided by the AP after 244 association in a given BSS. TBD: further definition of Short ID. 246 A2: indicates the transmitter of the frame and it contains the 247 6-bytes MAC address or the Short ID (2-bytes) provided by the AP 248 after association in a given BSS. 250 Frame Body: is of variable-length field and contains the MAC payload 251 for example L3 packets. 253 FCS: The Frame Check Sequence field is a 32-bit field containing a 254 32-bit CRC which is calculated over all the fields of the MAC header 255 and the Frame Body field 257 Missing descriptions to be completed later. 259 3.4. Protocol Version 1 261 With a 802.11ah basic feature set and following the PV1, the maximum 262 MPDU size is 511 bytes. The MAC header for the PV1 format is at 263 least formed by a Frame Control field and the address fields. Other 264 fields are optional. 266 +---------------+-------+--------+---------------------+ 267 + Frame Control + A1 + A2 + Frame Body + FCS + 268 +---------------+-------+--------+---------------------+ 269 Bytes: 2 6/2 2/6 0 to 497 4 271 Figure 3: MAC frame PV1 of 802.11ah 273 Frame control: see above. 275 A1: indicates the recipient of the frame and it contains the 6-bytes 276 MAC address or the Short ID (2-bytes) provided by the AP after 277 association in a given BSS. 279 A2: indicates the transmitter of the frame and it contains the 280 6-bytes MAC address or the Short ID (2-bytes) provided by the AP 281 after association in a given BSS. 283 Frame Body: The minimum length for non-data frames is 0 bytes. The 284 maximum length depends for example of the MAC header overhead and 285 among other things. For the a basic PV1 data frame with A1/A2 fields 286 carrying MAC addresses and no other optional MAC header fields, the 287 maximum frame body length is 497-bytes. 289 3.5. Link Layer Control 291 The Logical Link Control (LLC) layers works as the interface between 292 higher layers, for example IP, and the 802.11 MAC. It supports 293 higher layer protocol discrimination via the EtherType value 294 utilizing the EtherType protocol discrimination method (EPD) defined 295 in IEEE 802-2014 [IEEE802-2014]. Examples of EtherTypes are 0x0800 296 and 0x8DD, which are used to identify IPv4 and IPv6, respectively. 298 LLC Header Format: TBD. 300 +-----------------------+ 301 | 802 LLC | 302 +-----------------------+ 303 | MAC Layer (802.11ah) | 304 +-----------------------+ 305 | PHY Layer (802.11ah) | 306 +-----------------------+ 308 Figure 4: WLAN Protocol Stack 310 4. Uses Cases 312 [RFC7548] define use cases for the management of constrained 313 networks, these uses cases are apply as well to 802.11ah 315 As a starting point in 802.11ah specification work, the Task Group AH 316 proposed the following use-case categories 317 [ReferenceUseCase802.11ah]: 319 - Sensor and Meters, where large number of sensor deliver data 320 through 802.11ah connectivity 322 - Backhaul Sensor and meter data, where 802.11ah STA can be either 323 directly integrated with a sensor or it will aggregate data from 324 other tree of wireless sensors and then deliver 802.11ah connectivity 326 - Extended Range Wi-Fi, where the typical range of the Wi-Fi 327 connection will extended due to the use of lower frequencies and 328 other techniques. 330 5. 6LoWPAN over 802.11ah 332 IPv4 and IPv6 are compatible with 802.11ah via the LLC. However, 333 this technology presents a trade-off between energy savings and bit 334 rate of the link. Consequently, 6LoWPAN techniques are beneficial to 335 reduce the overhead of transmissions, save energy and get a better 336 throughput. With 6LoWPAN, the nodes, i.e. 6LN, 6LBR, are co-located 337 on the same devices with 802.11 features. The typical 802.11ah 338 network uses a star topology where the 6LBR functionally is co- 339 located with the AP. 6LNs are co-located with STAs and are connected 340 to the 6LBR through a 802.11ah link. The mesh topology at MAC level 341 is not defined by the 802.11ah standard implying that the 6LBR is the 342 only router present in the network. Thus, there is no presence of 343 6LowPAN Routers (6LR). 345 +---------+ 346 |+-------+| +---------+ 347 || 6LN || 802.11ah |+-------+| 348 |+-------+| || 6LN || 349 |+-------++------------+---------|+-------+| 350 || STA || | |+-------+| 351 |+-------+| | || STA || 352 +---------+ | |+-------+| 353 6LN-STA | +---------+ 354 +-----+-----+ 355 |+----+----+| 356 || 6LBR || 357 |+---------+| 358 +---------+ | | +---------+ 359 |+-------+| |+---------++ ++-------+| 360 || 6LN || || AP || || 6LN || 361 |+-------+| |+---------+| |+-------+| 362 |+-------++---+----+------+ | | 363 || STA || | 6LBR-AP |+-------+| 364 |+-------+| | || STA || 365 +--------+| | |+-------+| 366 +---------+ +-----------+---------+ 368 Figure 5: Network Topology 370 There exists the possibility to have a 802.11ah relay node at L2 to 371 extend the range of an AP. This however is experienced as a single 372 hop by the 6LoWPAN network. In case there is need to connect 373 wirelessly several APs in a mesh topology, the 802.11s might be 374 considered as a possibility. However, the 802.11s is not directly 375 compatible with 802.11ah and should be considered as a different 376 radio technology based on 802.11 integrated to the system. 378 The devices in this kind of networks, not necessarily have 379 constrained resources (memory, CPU, etc), but the radio link capacity 380 is limited. It might be that APs are connected to mains power and 381 STAs might be for example battery operated sensors. Therefore 382 6LoWPAN techniques might be good to support transmission of IPv6 383 packets over 802.11ah battery operated devices. Related to 384 performance gain, a reduction in air-time is achieved if the stack is 385 compressed. The communication 6LN-6LN is not supported directly 386 using link-local addresses, it is done through the 6LBR using the 387 shared prefix used on the subnet. This specification requires IPv6 388 header compression format specified in [RFC6282]. 390 In Figure below is showed the stack for PHY and IPv6 including 391 6LoWPAN 393 +---------------------+ 394 | Upper Layers | 395 +---------------------+ 396 | IPv6 | 397 +---------------------+ 398 | 6LoWPAN | 399 +---------------------+ 400 | 802 LLC | 401 +---------------------+ 402 | MAC Layer(802.11ah) | 403 +---------------------+ 404 | PHY Layer(802.11ah) | 405 +---------------------+ 407 Figure 6: Protocol Stack with 6LoWPAN 409 6. Stateless address autoconfiguration 411 The IPv6 link local address follows Section 5.3 of [RFC4862] based on 412 the 48-bit MAC device address. 414 To get the 64-bit Interface Identifier (IID) RFC 7136 [RFC7136] MUST 415 be followed. Section 5 of this RFC states: 417 "For all unicast addresses, except those that start with the binary 418 value 000, Interface IDs are required to be 64 bits long. If derived 419 from an IEEE MAC-layer address, they must be constructed in Modified 420 EUI-64 format." 421 10 bits 54 bits 64 bits 422 +----------+-----------------+----------------------+ 423 |1111111010| 0 | Interface Identifier | 424 +----------+-----------------+----------------------+ 426 Figure 7: IPv6 link local address 428 Following Appendix-A of RFC 4291 [RFC4291] the IID is formed 429 inserting two octets, with hexadecimal values of 0xFF and 0xFE in the 430 middle of the 48-bit MAC. The IID would be as follow where "a" is a 431 bit of the 48 MAC address. 433 |0 1|1 3|3 4|4 6| 434 |0 5|6 1|2 7|8 3| 435 +----------------+----------------+----------------+----------------+ 436 |aaaaaaaaaaaaaaaa|aaaaaaaa11111111|11111110aaaaaaaa|aaaaaaaaaaaaaaaa| 437 +----------------+----------------+----------------+----------------+ 439 Figure 8: Modified EUI-64 format 441 For non-link-local addresses a 64-bit IID MAY be formed by utilizing 442 the 48-bit MAC device address. Random IID can be generated for 6LN 443 using alternative methods such as [I-D.ietf-6man-default-iids]. 445 7. Neighbour Discovery in 802.11ah 447 Neighbour Discovery approach for 6LoWPAN [RFC6775] is applicable to 448 802.11ah topologies. Related to Host-initiated process, use of 449 Address Registration Option (ARO), through the Neighbour Solicitation 450 (NS) and Neighbour Advertisement (NA). Router Solicitation and 451 Router Advertisement are applicable as well following [RFC6775]. 453 As the topology is star, Multihop Distribution of prefix and 6LoWPAN 454 header compression; and Multihop Duplicated Address Detection (DAD) 455 mechanism are not applicable, since this technology does not cover 456 multihop topology. 458 8. Header compression 460 For header compression are applicable the rules proposed in 461 [RFC6282]. Section 3.1.1 mentions the base Encoding in principle 462 apply to 802.11ah. 464 0 1 465 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 466 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ 467 | 0 | 1 | 1 | TF |NH | HLIM |CID|SAC| SAM | M |DAC| DAM | 468 +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ 469 Figure 9: LOWPAN_IPHC base Encoding 471 As specified in [RFC6282]. TF: Traffic Class; Flow Label; NH: Next 472 Header; HLIM: Hop Limit; CID: Context Identifier Extension (TBD: How 473 it would work in 802.11ah); SAC: Source Address Compression. (TBD 474 whether the source address would be eliminated in link-local address 475 ); SAM: Source Address Mode; M: Multicast Compression (TBD: How it 476 would work with 802.11ah); DAC: Destination Address Compression; DAM: 477 Destination Address Mode. 479 9. Fragmentation 481 802.11ah perform fragmentation at L2, thus the fragmentation at L3 482 would be not necessary. 484 10. Multicast at IP level 486 802.11ah supports broadcast and multicast at link layer level, both 487 can be used to carry multicast IP transmission depending on the 488 system's configuration. TBD: add an example. 490 11. Internet Connection 492 For Internet connection, the 6LBR acts as router and forwarding 493 packets between 6LNs to and from Internet. 495 +-----+ 496 | 6LN +--------+ 497 +-----+ | 498 | +-----------+ 499 +----+----+ | | 500 | | | Internet | 501 +------+ 6LBR +----+ | 502 +--+--+ | | | | 503 | 6LN | +----+----+ +-----------+ 504 +-----+ | 505 +--+--+ 506 | 6LN | 507 +-----+ 509 Figure 10: Internet connection of 6Lo network 511 12. Management of the Network 512 TBD: how LightWeight Machine to Machine (LWM2M) or CoAP Management 513 Interface (COMI) [I-D.vanderstok-core-comi] aspects can be applied to 514 this technology, considering [RFC7547] 516 13. IANA Considerations 518 There are no IANA considerations related to this document. 520 14. Security Considerations 522 The security considerations defined in [RFC4944] and its update 523 [RFC6282] can be assumed valid for the 802.11ah case as well. 524 Indeed, the transmission of IPv6 over 802.11ah links meets all the 525 requirements for security as for IEEE 802.15.4. The standard IEEE 526 802.11ah defines all those aspects related with Link Layer security. 527 As well as for other existing WiFi solutions, 802.11ah Link Layer 528 supports security mechanism such as WPA, WPS, 802.1X. To have a 529 deeper understanding on how the Key Management processes are handled 530 in 802.11ah, please refer to [TBD] 532 Implementations defined in [I-D.ietf-6man-default-iids], [RFC3972], 533 [RFC4941], or [RFC5535], can be considered, for example, as methods 534 to support non-link local addresses. 536 Privacy - TBD. 538 15. Acknowledgements 540 This work is partially funded by the FP7 Marie Curie Initial Training 541 Network (ITN) METRICS project (grant agreement No. 607728) 543 16. References 545 16.1. Normative References 547 [IEEE802.11ah] 548 Institute of Electrical and Electronics Engineers (IEEE), 549 "Wireless LAN Medium Access Control (MAC) and Physical 550 Layer (PHY) Specifications: Amendment- Sub 1 GHz License- 551 Exempt Operation", January 2015. 553 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 554 Requirement Levels", BCP 14, RFC 2119, March 1997. 556 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 557 Architecture", RFC 4291, February 2006. 559 [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless 560 Address Autoconfiguration", RFC 4862, September 2007. 562 [RFC6282] Hui, J. and P. Thubert, "Compression Format for IPv6 563 Datagrams over IEEE 802.15.4-Based Networks", RFC 6282, 564 September 2011. 566 [RFC6775] Shelby, Z., Chakrabarti, S., Nordmark, E., and C. Bormann, 567 "Neighbor Discovery Optimization for IPv6 over Low-Power 568 Wireless Personal Area Networks (6LoWPANs)", RFC 6775, 569 November 2012. 571 [RFC7136] Carpenter, B. and S. Jiang, "Significance of IPv6 572 Interface Identifiers", RFC 7136, February 2014. 574 16.2. Informative References 576 [I-D.ietf-6lo-btle] 577 Nieminen, J., Savolainen, T., Isomaki, M., Patil, B., 578 Shelby, Z., and C. Gomez, "IPv6 over BLUETOOTH(R) Low 579 Energy", draft-ietf-6lo-btle-11 (work in progress), April 580 2015. 582 [I-D.ietf-6man-default-iids] 583 Gont, F., Cooper, A., Thaler, D., and W. Will, 584 "Recommendation on Stable IPv6 Interface Identifiers", 585 draft-ietf-6man-default-iids-03 (work in progress), May 586 2015. 588 [I-D.vanderstok-core-comi] 589 Stok, P., Greevenbosch, B., Bierman, A., Schoenwaelder, 590 J., and A. Sehgal, "CoAP Management Interface", draft- 591 vanderstok-core-comi-06 (work in progress), February 2015. 593 [IEEE802-2014] 594 Institute of Electrical and Electronics Engineers (IEEE), 595 "IEEE Standard for Local and Metropolitan Area Networks: 596 Overview and Architecture", 2014. 598 [IEEE802.11-2012] 599 Institute of Electrical and Electronics Engineers (IEEE), 600 "Wireless LAN Medium Access Control (MAC) and Physical 601 Layer (PHY) Specifications", 2012. 603 [IEEE802.11] 604 Institute of Electrical and Electronics Engineers (IEEE), 605 "Wireless LAN ", 2011. 607 [RFC3972] Aura, T., "Cryptographically Generated Addresses (CGA)", 608 RFC 3972, March 2005. 610 [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast 611 Addresses", RFC 4193, October 2005. 613 [RFC4941] Narten, T., Draves, R., and S. Krishnan, "Privacy 614 Extensions for Stateless Address Autoconfiguration in 615 IPv6", RFC 4941, September 2007. 617 [RFC4944] Montenegro, G., Kushalnagar, N., Hui, J., and D. Culler, 618 "Transmission of IPv6 Packets over IEEE 802.15.4 619 Networks", RFC 4944, September 2007. 621 [RFC5535] Bagnulo, M., "Hash-Based Addresses (HBA)", RFC 5535, June 622 2009. 624 [RFC7547] Ersue, M., Romascanu, D., Schoenwaelder, J., and U. 625 Herberg, "Management of Networks with Constrained Devices: 626 Problem Statement and Requirements", RFC 7547, May 2015. 628 [RFC7548] Ersue, M., Romascanu, D., Schoenwaelder, J., and A. 629 Sehgal, "Management of Networks with Constrained Devices: 630 Use Cases", RFC 7548, May 2015. 632 [ReferenceUseCase802.11ah] 633 Institute of Electrical and Electronics Engineers (IEEE), 634 "Potential compromise of 80211ah use case", 2012. 636 Authors' Addresses 638 Luis Felipe Del Carpio Vega 639 Ericsson 640 Hirsalantie 11 641 Jorvas 02420 642 Finland 644 Email: felipe.del.carpio@ericsson.com 646 Maria Ines Robles 647 Ericsson 648 Hirsalantie 11 649 Jorvas 02420 650 Finland 652 Email: maria.ines.robles@ericsson.com 653 Roberto Morabito 654 Ericsson 655 Hirsalantie 11 656 Jorvas 02420 657 Finland 659 Email: roberto.morabito@ericsson.com