idnits 2.17.1 draft-ietf-ipwave-ipv6-over-80211ocb-08.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 : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 19, 2017) is 2411 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '1' on line 685 -- Looks like a reference, but probably isn't: '16' on line 695 -- Looks like a reference, but probably isn't: '13' on line 693 -- Looks like a reference, but probably isn't: '14' on line 693 -- Looks like a reference, but probably isn't: '15' on line 695 == Unused Reference: 'RFC3963' is defined on line 879, but no explicit reference was found in the text == Unused Reference: 'RFC4429' is defined on line 912, but no explicit reference was found in the text == Unused Reference: 'RFC6775' is defined on line 940, but no explicit reference was found in the text == Outdated reference: A later version (-11) exists of draft-ietf-tsvwg-ieee-802-11-09 ** Obsolete normative reference: RFC 2818 (Obsoleted by RFC 9110) ** Downref: Normative reference to an Informational RFC: RFC 3753 ** Downref: Normative reference to an Informational RFC: RFC 5889 ** Downref: Normative reference to an Informational RFC: RFC 7721 Summary: 5 errors (**), 0 flaws (~~), 5 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Petrescu 3 Internet-Draft CEA, LIST 4 Intended status: Standards Track N. Benamar 5 Expires: March 23, 2018 Moulay Ismail University 6 J. Haerri 7 Eurecom 8 C. Huitema 9 Private Octopus Inc. 10 J. Lee 11 Sangmyung University 12 T. Ernst 13 YoGoKo 14 T. Li 15 Peloton Technology 16 September 19, 2017 18 Transmission of IPv6 Packets over IEEE 802.11 Networks operating in mode 19 Outside the Context of a Basic Service Set (IPv6-over-80211-OCB) 20 draft-ietf-ipwave-ipv6-over-80211ocb-08.txt 22 Abstract 24 In order to transmit IPv6 packets on IEEE 802.11 networks running 25 outside the context of a basic service set (OCB, earlier "802.11p") 26 there is a need to define a few parameters such as the supported 27 Maximum Transmission Unit size on the 802.11-OCB link, the header 28 format preceding the IPv6 header, the Type value within it, and 29 others. This document describes these parameters for IPv6 and IEEE 30 802.11-OCB networks; it portrays the layering of IPv6 on 802.11-OCB 31 similarly to other known 802.11 and Ethernet layers - by using an 32 Ethernet Adaptation Layer. 34 In addition, the document lists what is different in 802.11-OCB 35 (802.11p) links compared to more 'traditional' 802.11a/b/g/n links, 36 where IPv6 protocols operate without issues. Most notably, the 37 operation outside the context of a BSS (OCB) impacts IPv6 handover 38 behaviour and IPv6 security. 40 Status of This Memo 42 This Internet-Draft is submitted in full conformance with the 43 provisions of BCP 78 and BCP 79. 45 Internet-Drafts are working documents of the Internet Engineering 46 Task Force (IETF). Note that other groups may also distribute 47 working documents as Internet-Drafts. The list of current Internet- 48 Drafts is at https://datatracker.ietf.org/drafts/current/. 50 Internet-Drafts are draft documents valid for a maximum of six months 51 and may be updated, replaced, or obsoleted by other documents at any 52 time. It is inappropriate to use Internet-Drafts as reference 53 material or to cite them other than as "work in progress." 55 This Internet-Draft will expire on March 23, 2018. 57 Copyright Notice 59 Copyright (c) 2017 IETF Trust and the persons identified as the 60 document authors. All rights reserved. 62 This document is subject to BCP 78 and the IETF Trust's Legal 63 Provisions Relating to IETF Documents 64 (https://trustee.ietf.org/license-info) in effect on the date of 65 publication of this document. Please review these documents 66 carefully, as they describe your rights and restrictions with respect 67 to this document. Code Components extracted from this document must 68 include Simplified BSD License text as described in Section 4.e of 69 the Trust Legal Provisions and are provided without warranty as 70 described in the Simplified BSD License. 72 Table of Contents 74 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 75 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 76 3. Communication Scenarios where IEEE 802.11-OCB Links are Used 7 77 4. Aspects introduced by the OCB mode to 802.11 . . . . . . . . 7 78 5. Layering of IPv6 over 802.11-OCB as over Ethernet . . . . . . 11 79 5.1. Maximum Transmission Unit (MTU) . . . . . . . . . . . . . 11 80 5.2. Frame Format . . . . . . . . . . . . . . . . . . . . . . 11 81 5.2.1. Ethernet Adaptation Layer . . . . . . . . . . . . . . 12 82 5.3. Link-Local Addresses . . . . . . . . . . . . . . . . . . 14 83 5.4. Address Mapping . . . . . . . . . . . . . . . . . . . . . 14 84 5.4.1. Address Mapping -- Unicast . . . . . . . . . . . . . 14 85 5.4.2. Address Mapping -- Multicast . . . . . . . . . . . . 15 86 5.5. Stateless Autoconfiguration . . . . . . . . . . . . . . . 16 87 5.6. Subnet Structure . . . . . . . . . . . . . . . . . . . . 17 88 6. Security Considerations . . . . . . . . . . . . . . . . . . . 17 89 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 90 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 18 91 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 92 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 93 10.1. Normative References . . . . . . . . . . . . . . . . . . 19 94 10.2. Informative References . . . . . . . . . . . . . . . . . 22 95 Appendix A. ChangeLog . . . . . . . . . . . . . . . . . . . . . 23 96 Appendix B. Changes Needed on a software driver 802.11a to 97 become a 802.11-OCB driver . . . 28 99 Appendix C. Design Considerations . . . . . . . . . . . . . . . 29 100 C.1. Vehicle ID . . . . . . . . . . . . . . . . . . . . . . . 29 101 C.2. Reliability Requirements . . . . . . . . . . . . . . . . 30 102 C.3. Multiple interfaces . . . . . . . . . . . . . . . . . . . 30 103 C.4. MAC Address Generation . . . . . . . . . . . . . . . . . 31 104 Appendix D. IEEE 802.11 Messages Transmitted in OCB mode . . . . 32 105 Appendix E. Implementation Status . . . . . . . . . . . . . . . 32 106 E.1. Capture in Monitor Mode . . . . . . . . . . . . . . . . . 33 107 E.2. Capture in Normal Mode . . . . . . . . . . . . . . . . . 35 108 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37 110 1. Introduction 112 This document describes the transmission of IPv6 packets on IEEE Std 113 802.11-OCB networks (a.k.a 802.11p) [IEEE-802.11-2016]. This 114 involves the layering of IPv6 networking on top of the IEEE 802.11 115 MAC layer (with an LLC layer). Compared to running IPv6 over the 116 Ethernet MAC layer, there is no modification expected to IEEE Std 117 802.11 MAC and Logical Link sublayers: IPv6 works fine directly over 118 802.11-OCB too (with an LLC layer). 120 The term "802.11p" is an earlier definition. The behaviour of 121 "802.11p" networks is rolled in the document IEEE Std 802.11-2016. 122 In that document the term 802.11p disappears. Instead, each 802.11p 123 feature is conditioned by the Management Information Base (MIB) 124 attribute "OCBActivated". Whenever OCBActivated is set to true the 125 IEEE Std 802.11 OCB state is activated. For example, an 802.11 126 STAtion operating outside the context of a basic service set has the 127 OCBActivated flag set. Such a station, when it has the flag set, 128 uses a BSS identifier equal to ff:ff:ff:ff:ff:ff. 130 The IPv6 network layer operates on 802.11-OCB in the same manner as 131 it operates on 802.11 WiFi, with a few particular exceptions. The 132 IPv6 network layer operates on WiFi by involving an Ethernet 133 Adaptation Layer; this Ethernet Adaptation Layer maps 802.11 headers 134 to Ethernet II headers. The operation of IP on Ethernet is described 135 in [RFC1042], [RFC2464] and [I-D.hinden-6man-rfc2464bis]. The 136 situation of IPv6 networking layer on Ethernet Adaptation Layer is 137 illustrated below: 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 140 | IPv6 | 141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 142 | Ethernet Adaptation Layer | 143 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 144 | 802.11 WiFi MAC | 145 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 146 | 802.11 WiFi PHY | 147 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 149 (in the above figure, a WiFi profile is represented; this is used 150 also for OCB profile.) 152 A more theoretical and detailed view of layer stacking, and 153 interfaces between the IP layer and 802.11-OCB layers, is illustrated 154 below. The IP layer operates on top of the EtherType Protocol 155 Discrimination (EPD); this Discrimination layer is described in IEEE 156 Std 802.3-2012; the interface between IPv6 and EPD is the LLC_SAP 157 (Link Layer Control Service Access Point). 159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 | IPv6 | 161 +-+-+-+-+-+-{ }+-+-+-+-+-+-+-+ 162 { LLC_SAP } 802.11-OCB 163 +-+-+-+-+-+-{ }+-+-+-+-+-+-+-+ Boundary 164 | EPD | | | 165 | | MLME | | 166 +-+-+-{ MAC_SAP }+-+-+-| MLME_SAP | 167 | MAC Sublayer | | | 802.11-OCB 168 | and ch. coord. | | SME | Services 169 +-+-+-{ PHY_SAP }+-+-+-+-+-+-+-| | 170 | | PLME | | 171 | PHY Layer | PLME_SAP | 172 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 174 In addition to the description of interface between IP and MAC using 175 "Ethernet Adaptation Layer" and "Ethernet Protocol Discrimination 176 (EPD)" it is worth mentioning that SNAP [RFC1042] is used to carry 177 the IPv6 Ethertype. 179 However, there may be some deployment considerations helping optimize 180 the performances of running IPv6 over 802.11-OCB (e.g. in the case of 181 handovers between 802.11-OCB-enabled access routers, or the 182 consideration of using the IP security architecture [RFC4301]). 184 There are currently no specifications for handover between OCB links 185 since these are currently specified as LLC-1 links (i.e. 186 connectionless). Any handovers must be performed above the Data Link 187 Layer. To realize handovers between OCB links there is a need for 188 specific indicators to assist in the handover process. The 189 indicators may be IP Router Advertisements, or 802.11-OCB's Time 190 Advertisements, or application-layer data. However, this document 191 does not describe handover behaviour. 193 The OCB operation is stripped off of all existing 802.11 link-layer 194 security mechanisms. There is no encryption applied below the 195 network layer running on 802.11-OCB. At application layer, the IEEE 196 1609.2 document [IEEE-1609.2] does provide security services for 197 certain applications to use; application-layer mechanisms are out-of- 198 scope of this document. On another hand, a security mechanism 199 provided at networking layer, such as IPsec [RFC4301], may provide 200 data security protection to a wider range of applications. See the 201 section Security Considerations of this document, Section 6 203 We briefly introduce the vehicular communication scenarios where IEEE 204 802.11-OCB links are used. This is followed by a description of 205 differences in specification terms, between 802.11-OCB and 206 802.11a/b/g/n - we answer the question of what are the aspects 207 introduced by OCB mode to 802.11; the same aspects, but expressed in 208 terms of requirements to implementation, are listed in Appendix B.) 210 The document then concentrates on the parameters of layering IP over 211 802.11-OCB as over Ethernet: value of MTU, the Frame Format which 212 includes a description of an Ethernet Adaptation Layer, the forming 213 of Link-Local Addresses the rules for forming Interface Identifiers 214 for Stateless Autoconfiguration, the mechanisms for Address Mapping. 215 These are precisely the same as IPv6 over Ethernet [RFC2464]. A 216 reference is made to ad-hoc networking characteristics of the subnet 217 structure in OCB mode. 219 As an example, these characteristics of layering IPv6 straight over 220 LLC over 802.11-OCB MAC are illustrated by dissecting an IPv6 packet 221 captured over a 802.11-OCB link; this is described in the section 222 Appendix E. 224 In the published literature, many documents describe aspects related 225 to running IPv6 over 802.11-OCB: 226 [I-D.jeong-ipwave-vehicular-networking-survey]. 228 2. Terminology 230 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 231 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 232 document are to be interpreted as described in RFC 2119 [RFC2119]. 234 OBRU (On-Board Router Unit): an OBRU is almost always situated in a 235 vehicle; it is a computer with at least two IP interfaces; at least 236 one IP interface runs in OCB mode of 802.11. It MAY be an IP Router. 238 RSRU (Road-Side Router Unit): an RSRU is almost always situated in a 239 box fixed along the road. An RSRU has at least two distinct IP- 240 enabled interfaces; at least one interface is operated in mode OCB of 241 IEEE 802.11 and is IP-enabled. An RSRU is similar to a Wireless 242 Termination Point (WTP), as defined in [RFC5415], or an Access Point 243 (AP), as defined in IEEE documents, or an Access Network Router (ANR) 244 defined in [RFC3753], with one key particularity: the wireless PHY/ 245 MAC layer of at least one of its IP-enabled interfaces is configured 246 to operate in 802.11-OCB mode. The RSRU communicates with the On 247 board Unit (OBRU) in the vehicle over 802.11 wireless link operating 248 in OCB mode. An RSRU MAY be connected to the Internet, and MAY be an 249 IP Router. When it is connected to the Internet, the term V2I 250 (Vehicle to Internet) is relevant. 252 RSU (Road-Side Unit): an RSU operates in 802.11-OCB mode. A RSU 253 broadcasts data to OBUs or exchanges data with OBUs in its 254 communications zone. An RSU may provides channel assignments and 255 operating instructions to OBUs in its communications zone, when 256 required. The basic functional blocks of an RSU are: internal 257 computer processing, permanent storage capability, an integrated GPS 258 receiver for positioning and timing and an interface that supports 259 both IPv4 and IPv6 connectivity, compliant with 802.3at. An OCB 260 interface of an RSU MAY be IP-enabled simultaneously to being WAVE- 261 enabled or GeoNetworking-enabled (MAY support simultaneously 262 EtherTypes 0x86DD for IPv6 _and_ 0x88DC for WAVE and 0x8947 for 263 GeoNetworking). 265 OCB (outside the context of a basic service set - BSS): A mode of 266 operation in which a STA is not a member of a BSS and does not 267 utilize IEEE Std 802.11 authentication, association, or data 268 confidentiality. 270 802.11-OCB: mode specified in IEEE Std 802.11-2016 when the MIB 271 attribute dot11OCBActivited is true. The OCB mode requires 272 transmission of QoS data frames (IEEE Std 802.11e), half-clocked 273 operation (IEEE Std 802.11j), and use of 5.9 GHz frequency band. 275 3. Communication Scenarios where IEEE 802.11-OCB Links are Used 277 The IEEE 802.11-OCB Networks are used for vehicular communications, 278 as 'Wireless Access in Vehicular Environments'. The IP communication 279 scenarios for these environments have been described in several 280 documents; in particular, we refer the reader to 281 [I-D.petrescu-its-scenarios-reqs], about scenarios and requirements 282 for IP in Intelligent Transportation Systems. 284 The link model is the following: STA --- 802.11-OCB --- STA. In 285 vehicular networks, STAs can be RSRUs and/or OBRUs. While 802.11-OCB 286 is clearly specified, and the use of IPv6 over such link is not 287 radically new, the operating environment (vehicular networks) brings 288 in new perspectives. 290 The 802.11-OCB links form and terminate; nodes connected to these 291 links peer, and discover each other; the nodes are mobile. However, 292 the precise description of how links discover each other, peer and 293 manage mobility is not given in this document. 295 4. Aspects introduced by the OCB mode to 802.11 297 In the IEEE 802.11-OCB mode, all nodes in the wireless range can 298 directly communicate with each other without involving authentication 299 or association procedures. At link layer, it is necessary to set the 300 same channel number (or frequency) on two stations that need to 301 communicate with each other. Stations STA1 and STA2 can exchange IP 302 packets if they are set on the same channel. At IP layer, they then 303 discover each other by using the IPv6 Neighbor Discovery protocol. 305 Briefly, the IEEE 802.11-OCB mode has the following properties: 307 o The use by each node of a 'wildcard' BSSID (i.e., each bit of the 308 BSSID is set to 1) 310 o No IEEE 802.11 Beacon frames are transmitted 312 o No authentication is required in order to be able to communicate 314 o No association is needed in order to be able to communicate 316 o No encryption is provided in order to be able to communicate 318 o Flag dot11OCBActivated is set to true 320 All the nodes in the radio communication range (OBRU and RSRU) 321 receive all the messages transmitted (OBRU and RSRU) within the radio 322 communications range. The eventual conflict(s) are resolved by the 323 MAC CDMA function. 325 The following message exchange diagram illustrates a comparison 326 between traditional 802.11 and 802.11 in OCB mode. The 'Data' 327 messages can be IP packets such as HTTP or others. Other 802.11 328 management and control frames (non IP) may be transmitted, as 329 specified in the 802.11 standard. For information, the names of 330 these messages as currently specified by the 802.11 standard are 331 listed in Appendix D. 333 STA AP STA1 STA2 334 | | | | 335 |<------ Beacon -------| |<------ Data -------->| 336 | | | | 337 |---- Probe Req. ----->| |<------ Data -------->| 338 |<--- Probe Res. ------| | | 339 | | |<------ Data -------->| 340 |---- Auth Req. ------>| | | 341 |<--- Auth Res. -------| |<------ Data -------->| 342 | | | | 343 |---- Asso Req. ------>| |<------ Data -------->| 344 |<--- Asso Res. -------| | | 345 | | |<------ Data -------->| 346 |<------ Data -------->| | | 347 |<------ Data -------->| |<------ Data -------->| 349 (a) 802.11 Infrastructure mode (b) 802.11-OCB mode 351 The interface 802.11-OCB was specified in IEEE Std 802.11p (TM) -2010 352 [IEEE-802.11p-2010] as an amendment to IEEE Std 802.11 (TM) -2007, 353 titled "Amendment 6: Wireless Access in Vehicular Environments". 354 Since then, this amendment has been included in IEEE 802.11(TM) -2012 355 and -2016 [IEEE-802.11-2016]. 357 In document 802.11-2016, anything qualified specifically as 358 "OCBActivated", or "outside the context of a basic service" set to be 359 true, then it is actually referring to OCB aspects introduced to 360 802.11. 362 In order to delineate the aspects introduced by 802.11-OCB to 802.11, 363 we refer to the earlier [IEEE-802.11p-2010]. The amendment is 364 concerned with vehicular communications, where the wireless link is 365 similar to that of Wireless LAN (using a PHY layer specified by 366 802.11a/b/g/n), but which needs to cope with the high mobility factor 367 inherent in scenarios of communications between moving vehicles, and 368 between vehicles and fixed infrastructure deployed along roads. 369 While 'p' is a letter just like 'a, b, g' and 'n' are, 'p' is 370 concerned more with MAC modifications, and a little with PHY 371 modifications; the others are mainly about PHY modifications. It is 372 possible in practice to combine a 'p' MAC with an 'a' PHY by 373 operating outside the context of a BSS with OFDM at 5.4GHz and 374 5.9GHz. 376 The 802.11-OCB links are specified to be compatible as much as 377 possible with the behaviour of 802.11a/b/g/n and future generation 378 IEEE WLAN links. From the IP perspective, an 802.11-OCB MAC layer 379 offers practically the same interface to IP as the WiFi and Ethernet 380 layers do (802.11a/b/g/n and 802.3). A packet sent by an OBRU may be 381 received by one or multiple RSRUs. The link-layer resolution is 382 performed by using the IPv6 Neighbor Discovery protocol. 384 To support this similarity statement (IPv6 is layered on top of LLC 385 on top of 802.11-OCB, in the same way that IPv6 is layered on top of 386 LLC on top of 802.11a/b/g/n (for WLAN) or layered on top of LLC on 387 top of 802.3 (for Ethernet)) it is useful to analyze the differences 388 between 802.11-OCB and 802.11 specifications. During this analysis, 389 we note that whereas 802.11-OCB lists relatively complex and numerous 390 changes to the MAC layer (and very little to the PHY layer), there 391 are only a few characteristics which may be important for an 392 implementation transmitting IPv6 packets on 802.11-OCB links. 394 The most important 802.11-OCB point which influences the IPv6 395 functioning is the OCB characteristic; an additional, less direct 396 influence, is the maximum bandwidth afforded by the PHY modulation/ 397 demodulation methods and channel access specified by 802.11-OCB. The 398 maximum bandwidth theoretically possible in 802.11-OCB is 54 Mbit/s 399 (when using, for example, the following parameters: 20 MHz channel; 400 modulation 64-QAM; codint rate R is 3/4); in practice of IP-over- 401 802.11-OCB a commonly observed figure is 12Mbit/s; this bandwidth 402 allows the operation of a wide range of protocols relying on IPv6. 404 o Operation Outside the Context of a BSS (OCB): the (earlier 405 802.11p) 802.11-OCB links are operated without a Basic Service Set 406 (BSS). This means that the frames IEEE 802.11 Beacon, Association 407 Request/Response, Authentication Request/Response, and similar, 408 are not used. The used identifier of BSS (BSSID) has a 409 hexadecimal value always 0xffffffffffff (48 '1' bits, represented 410 as MAC address ff:ff:ff:ff:ff:ff, or otherwise the 'wildcard' 411 BSSID), as opposed to an arbitrary BSSID value set by 412 administrator (e.g. 'My-Home-AccessPoint'). The OCB operation - 413 namely the lack of beacon-based scanning and lack of 414 authentication - should be taken into account when the Mobile IPv6 415 protocol [RFC6275] and the protocols for IP layer security 417 [RFC4301] are used. The way these protocols adapt to OCB is not 418 described in this document. 420 o Timing Advertisement: is a new message defined in 802.11-OCB, 421 which does not exist in 802.11a/b/g/n. This message is used by 422 stations to inform other stations about the value of time. It is 423 similar to the time as delivered by a GNSS system (Galileo, GPS, 424 ...) or by a cellular system. This message is optional for 425 implementation. 427 o Frequency range: this is a characteristic of the PHY layer, with 428 almost no impact on the interface between MAC and IP. However, it 429 is worth considering that the frequency range is regulated by a 430 regional authority (ARCEP, ETSI, FCC, etc.); as part of the 431 regulation process, specific applications are associated with 432 specific frequency ranges. In the case of 802.11-OCB, the 433 regulator associates a set of frequency ranges, or slots within a 434 band, to the use of applications of vehicular communications, in a 435 band known as "5.9GHz". The 5.9GHz band is different from the 436 2.4GHz and 5GHz bands used by Wireless LAN. However, as with 437 Wireless LAN, the operation of 802.11-OCB in "5.9GHz" bands is 438 exempt from owning a license in EU (in US the 5.9GHz is a licensed 439 band of spectrum; for the fixed infrastructure an explicit FCC 440 autorization is required; for an onboard device a 'licensed-by- 441 rule' concept applies: rule certification conformity is required); 442 however technical conditions are different than those of the bands 443 "2.4GHz" or "5GHz". On one hand, the allowed power levels, and 444 implicitly the maximum allowed distance between vehicles, is of 445 33dBm for 802.11-OCB (in Europe), compared to 20 dBm for Wireless 446 LAN 802.11a/b/g/n; this leads to a maximum distance of 447 approximately 1km, compared to approximately 50m. On the other 448 hand, specific conditions related to congestion avoidance, jamming 449 avoidance, and radar detection are imposed on the use of DSRC (in 450 US) and on the use of frequencies for Intelligent Transportation 451 Systems (in EU), compared to Wireless LAN (802.11a/b/g/n). 453 o 'Half-rate' encoding: as the frequency range, this parameter is 454 related to PHY, and thus has not much impact on the interface 455 between the IP layer and the MAC layer. 457 o In vehicular communications using 802.11-OCB links, there are 458 strong privacy requirements with respect to addressing. While the 459 802.11-OCB standard does not specify anything in particular with 460 respect to MAC addresses, in these settings there exists a strong 461 need for dynamic change of these addresses (as opposed to the non- 462 vehicular settings - real wall protection - where fixed MAC 463 addresses do not currently pose some privacy risks). This is 464 further described in section Section 6. A relevant function is 465 described in IEEE 1609.3-2016 [IEEE-1609.3], clause 5.5.1 and IEEE 466 1609.4-2016 [IEEE-1609.4], clause 6.7. 468 Other aspects particular to 802.11-OCB, which are also particular to 469 802.11 (e.g. the 'hidden node' operation), may have an influence on 470 the use of transmission of IPv6 packets on 802.11-OCB networks. The 471 OCB subnet structure is described in section Section 5.6. 473 5. Layering of IPv6 over 802.11-OCB as over Ethernet 475 5.1. Maximum Transmission Unit (MTU) 477 The default MTU for IP packets on 802.11-OCB is 1500 octets. It is 478 the same value as IPv6 packets on Ethernet links, as specified in 479 [RFC2464]. This value of the MTU respects the recommendation that 480 every link in the Internet must have a minimum MTU of 1280 octets 481 (stated in [RFC8200], and the recommendations therein, especially 482 with respect to fragmentation). If IPv6 packets of size larger than 483 1500 bytes are sent on an 802.11-OCB interface card then the IP stack 484 will fragment. In case there are IP fragments, the field "Sequence 485 number" of the 802.11 Data header containing the IP fragment field is 486 increased. 488 Non-IP packets such as WAVE Short Message Protocol (WSMP) can be 489 delivered on 802.11-OCB links. Specifications of these packets are 490 out of scope of this document, and do not impose any limit on the MTU 491 size, allowing an arbitrary number of 'containers'. Non-IP packets 492 such as ETSI GeoNetworking packets have an MTU of 1492 bytes. The 493 operation of IPv6 over GeoNetworking is specified at 494 [ETSI-IPv6-GeoNetworking]. 496 5.2. Frame Format 498 IP packets are transmitted over 802.11-OCB as standard Ethernet 499 packets. As with all 802.11 frames, an Ethernet adaptation layer is 500 used with 802.11-OCB as well. This Ethernet Adaptation Layer 501 performing 802.11-to-Ethernet is described in Section 5.2.1. The 502 Ethernet Type code (EtherType) for IPv6 is 0x86DD (hexadecimal 86DD, 503 or otherwise #86DD). 505 The Frame format for transmitting IPv6 on 802.11-OCB networks is the 506 same as transmitting IPv6 on Ethernet networks, and is described in 507 section 3 of [RFC2464]. The frame format for transmitting IPv6 508 packets over Ethernet is illustrated below: 510 0 1 511 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 512 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 513 | Destination | 514 +- -+ 515 | Ethernet | 516 +- -+ 517 | Address | 518 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 519 | Source | 520 +- -+ 521 | Ethernet | 522 +- -+ 523 | Address | 524 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 525 |1 0 0 0 0 1 1 0 1 1 0 1 1 1 0 1| 526 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 527 | IPv6 | 528 +- -+ 529 | header | 530 +- -+ 531 | and | 532 +- -+ 533 / payload ... / 534 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 535 (Each tic mark represents one bit.) 537 Ethernet II Fields: 539 Destination Ethernet Address 540 the MAC destination address. 542 Source Ethernet Address 543 the MAC source address. 545 1 0 0 0 0 1 1 0 1 1 0 1 1 1 0 1 546 binary representation of the EtherType value 0x86DD. 548 IPv6 header and payload 549 the IPv6 packet containing IPv6 header and payload. 551 5.2.1. Ethernet Adaptation Layer 553 In general, an 'adaptation' layer is inserted between a MAC layer and 554 the Networking layer. This is used to transform some parameters 555 between their form expected by the IP stack and the form provided by 556 the MAC layer. For example, an 802.15.4 adaptation layer may perform 557 fragmentation and reassembly operations on a MAC whose maximum Packet 558 Data Unit size is smaller than the minimum MTU recognized by the IPv6 559 Networking layer. Other examples involve link-layer address 560 transformation, packet header insertion/removal, and so on. 562 An Ethernet Adaptation Layer makes an 802.11 MAC look to IP 563 Networking layer as a more traditional Ethernet layer. At reception, 564 this layer takes as input the IEEE 802.11 Data Header and the 565 Logical-Link Layer Control Header and produces an Ethernet II Header. 566 At sending, the reverse operation is performed. 568 +--------------------+------------+-------------+---------+-----------+ 569 | 802.11 Data Header | LLC Header | IPv6 Header | Payload |.11 Trailer| 570 +--------------------+------------+-------------+---------+-----------+ 571 \ / \ / 572 ----------------------------- -------- 573 ^---------------------------------------------/ 574 | 575 802.11-to-Ethernet Adaptation Layer 576 | 577 v 578 +---------------------+-------------+---------+ 579 | Ethernet II Header | IPv6 Header | Payload | 580 +---------------------+-------------+---------+ 582 The Receiver and Transmitter Address fields in the 802.11 Data Header 583 contain the same values as the Destination and the Source Address 584 fields in the Ethernet II Header, respectively. The value of the 585 Type field in the LLC Header is the same as the value of the Type 586 field in the Ethernet II Header. 588 The ".11 Trailer" contains solely a 4-byte Frame Check Sequence. 590 The Ethernet Adaptation Layer performs operations in relation to IP 591 fragmentation and MTU. One of these operations is briefly described 592 in section Section 5.1. 594 In OCB mode, IPv6 packets can be transmitted either as "IEEE 802.11 595 Data" or alternatively as "IEEE 802.11 QoS Data", as illustrated in 596 the figure below. Some commercial OCB products use 802.11 Data, and 597 others 802.11 QoS data. In the future, both could be used. 599 +--------------------+-------------+-------------+---------+-----------+ 600 | 802.11 Data Header | LLC Header | IPv6 Header | Payload |.11 Trailer| 601 +--------------------+-------------+-------------+---------+-----------+ 603 or 605 +--------------------+-------------+-------------+---------+-----------+ 606 | 802.11 QoS Data Hdr| LLC Header | IPv6 Header | Payload |.11 Trailer| 607 +--------------------+-------------+-------------+---------+-----------+ 609 The distinction between the two formats is given by the value of the 610 field "Type/Subtype". The value of the field "Type/Subtype" in the 611 802.11 Data header is 0x0020. The value of the field "Type/Subtype" 612 in the 802.11 QoS header is 0x0028. 614 The mapping between qos-related fields in the IPv6 header (e.g. 615 "Traffic Class", "Flow label") and fields in the "802.11 QoS Data 616 Header" (e.g. "QoS Control") are not specified in this document. 617 Guidance for a potential mapping is provided in 618 [I-D.ietf-tsvwg-ieee-802-11], although it is not specific to OCB 619 mode. 621 5.3. Link-Local Addresses 623 The link-local address of an 802.11-OCB interface is formed in the 624 same manner as on an Ethernet interface. This manner is described in 625 section 5 of [RFC2464]. Additionally, if stable identifiers are 626 needed, it is recommended to follow the Recommendation on Stable IPv6 627 Interface Identifiers [RFC8064]. Additionally, if semantically 628 opaque Interface Identifiers are needed, a potential method for 629 generating semantically opaque Interface Identifiers with IPv6 630 Stateless Address Autoconfiguration is given in [RFC7217]. 632 5.4. Address Mapping 634 For unicast as for multicast, there is no change from the unicast and 635 multicast address mapping format of Ethernet interfaces, as defined 636 by sections 6 and 7 of [RFC2464]. 638 5.4.1. Address Mapping -- Unicast 640 The procedure for mapping IPv6 unicast addresses into Ethernet link- 641 layer addresses is described in [RFC4861]. The Source/Target Link- 642 layer Address option has the following form when the link-layer is 643 Ethernet. 645 0 1 646 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 647 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 648 | Type | Length | 649 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 650 | | 651 +- Ethernet -+ 652 | | 653 +- Address -+ 654 | | 655 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 657 Option fields: 659 Type 660 1 for Source Link-layer address. 661 2 for Target Link-layer address. 663 Length 664 1 (in units of 8 octets). 666 Ethernet Address 667 The 48 bit Ethernet IEEE 802 address, in canonical bit order. 669 5.4.2. Address Mapping -- Multicast 671 IPv6 protocols often make use of IPv6 multicast addresses in the 672 destination field of IPv6 headers. For example, an ICMPv6 link- 673 scoped Neighbor Advertisement is sent to the IPv6 address ff02::1 674 denoted "all-nodes" address. When transmitting these packets on 675 802.11-OCB links it is necessary to map the IPv6 address to a MAC 676 address. 678 The same mapping requirement applies to the link-scoped multicast 679 addresses of other IPv6 protocols as well. In DHCPv6, the 680 "All_DHCP_Servers" IPv6 multicast address ff02::1:2, and in OSPF the 681 "All_SPF_Routers" IPv6 multicast address ff02::5, need to be mapped 682 on a multicast MAC address. 684 An IPv6 packet with a multicast destination address DST, consisting 685 of the sixteen octets DST[1] through DST[16], is transmitted to the 686 IEEE 802.11-OCB MAC multicast address whose first two octets are the 687 value 0x3333 and whose last four octets are the last four octets of 688 DST. 690 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 691 |0 0 1 1 0 0 1 1|0 0 1 1 0 0 1 1| 692 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 693 | DST[13] | DST[14] | 694 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 695 | DST[15] | DST[16] | 696 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 698 A Group ID named TBD, of length 112bits is requested to IANA; this 699 Group ID signifies "All 80211OCB Interfaces Address". Only the least 700 32 significant bits of this "All 80211OCB Interfaces Address" will be 701 mapped to and from a MAC multicast address. 703 Transmitting IPv6 packets to multicast destinations over 802.11 links 704 proved to have some performance issues 705 [I-D.perkins-intarea-multicast-ieee802]. These issues may be 706 exacerbated in OCB mode. Solutions for these problems should 707 consider the OCB mode of operation. 709 5.5. Stateless Autoconfiguration 711 The Interface Identifier for an 802.11-OCB interface is formed using 712 the same rules as the Interface Identifier for an Ethernet interface; 713 this is described in section 4 of [RFC2464]. No changes are needed, 714 but some care must be taken when considering the use of the SLAAC 715 procedure. 717 The bits in the the interface identifier have no generic meaning and 718 the identifier should be treated as an opaque value. The bits 719 'Universal' and 'Group' in the identifier of an 802.11-OCB interface 720 are significant, as this is an IEEE link-layer address. The details 721 of this significance are described in [RFC7136]. 723 As with all Ethernet and 802.11 interface identifiers ([RFC7721]), 724 the identifier of an 802.11-OCB interface may involve privacy, MAC 725 address spoofing and IP address hijacking risks. A vehicle embarking 726 an On-Board Unit whose egress interface is 802.11-OCB may expose 727 itself to eavesdropping and subsequent correlation of data; this may 728 reveal data considered private by the vehicle owner; there is a risk 729 of being tracked; see the privacy considerations described in 730 Appendix C. 732 If stable Interface Identifiers are needed in order to form IPv6 733 addresses on 802.11-OCB links, it is recommended to follow the 734 recommendation in [RFC8064]. Additionally, if semantically opaque 735 Interface Identifiers are needed, a potential method for generating 736 semantically opaque Interface Identifiers with IPv6 Stateless Address 737 Autoconfiguration is given in [RFC7217]. 739 5.6. Subnet Structure 741 A subnet is formed by the external 802.11-OCB interfaces of vehicles 742 that are in close range (not their on-board interfaces). This 743 ephemeral subnet structure is strongly influenced by the mobility of 744 vehicles: the 802.11 hidden node effects appear. On another hand, 745 the structure of the internal subnets in each car is relatively 746 stable. 748 For routing purposes, a prefix exchange mechanism could be needed 749 between neighboring vehicles. 751 The 802.11 networks in OCB mode may be considered as 'ad-hoc' 752 networks. The addressing model for such networks is described in 753 [RFC5889]. 755 An addressing model involves several types of addresses, like 756 Globally-unique Addresses (GUA), Link-Local Addresses (LL) and Unique 757 Local Addresses (ULA). The subnet structure in 'ad-hoc' networks may 758 have characteristics that lead to difficulty of using GUAs derived 759 from a received prefix, but the LL addresses may be easier to use 760 since the prefix is constant. 762 6. Security Considerations 764 Any security mechanism at the IP layer or above that may be carried 765 out for the general case of IPv6 may also be carried out for IPv6 766 operating over 802.11-OCB. 768 802.11-OCB does not provide any cryptographic protection, because it 769 operates outside the context of a BSS (no Association Request/ 770 Response, no Challenge messages). Any attacker can therefore just 771 sit in the near range of vehicles, sniff the network (just set the 772 interface card's frequency to the proper range) and perform attacks 773 without needing to physically break any wall. Such a link is less 774 protected than commonly used links (wired link or protected 802.11). 776 The potential attack vectors are: MAC address spoofing, IP address 777 and session hijacking and privacy violation. 779 Within the IPsec Security Architecture [RFC4301], the IPsec AH and 780 ESP headers [RFC4302] and [RFC4303] respectively, its multicast 781 extensions [RFC5374], HTTPS [RFC2818] and SeND [RFC3971] protocols 782 can be used to protect communications. Further, the assistance of 783 proper Public Key Infrastructure (PKI) protocols [RFC4210] is 784 necessary to establish credentials. More IETF protocols are 785 available in the toolbox of the IP security protocol designer. 786 Certain ETSI protocols related to security protocols in Intelligent 787 Transportation Systems are described in [ETSI-sec-archi]. 789 As with all Ethernet and 802.11 interface identifiers, there may 790 exist privacy risks in the use of 802.11-OCB interface identifiers. 791 Moreover, in outdoors vehicular settings, the privacy risks are more 792 important than in indoors settings. New risks are induced by the 793 possibility of attacker sniffers deployed along routes which listen 794 for IP packets of vehicles passing by. For this reason, in the 795 802.11-OCB deployments, there is a strong necessity to use protection 796 tools such as dynamically changing MAC addresses. This may help 797 mitigate privacy risks to a certain level. On another hand, it may 798 have an impact in the way typical IPv6 address auto-configuration is 799 performed for vehicles (SLAAC would rely on MAC addresses amd would 800 hence dynamically change the affected IP address), in the way the 801 IPv6 Privacy addresses were used, and other effects. 803 7. IANA Considerations 805 A Group ID named TBD, of length 112bits is requested to IANA; this 806 Group ID signifies "All 80211OCB Interfaces Address". 808 8. Contributors 810 Romain Kuntz contributed extensively about IPv6 handovers between 811 links running outside the context of a BSS (802.11-OCB links). 813 Tim Leinmueller contributed the idea of the use of IPv6 over 814 802.11-OCB for distribution of certificates. 816 Marios Makassikis, Jose Santa Lozano, Albin Severinson and Alexey 817 Voronov provided significant feedback on the experience of using IP 818 messages over 802.11-OCB in initial trials. 820 Michelle Wetterwald contributed extensively the MTU discussion, 821 offered the ETSI ITS perspective, and reviewed other parts of the 822 document. 824 9. Acknowledgements 826 The authors would like to thank Witold Klaudel, Ryuji Wakikawa, 827 Emmanuel Baccelli, John Kenney, John Moring, Francois Simon, Dan 828 Romascanu, Konstantin Khait, Ralph Droms, Richard 'Dick' Roy, Ray 829 Hunter, Tom Kurihara, Michal Sojka, Jan de Jongh, Suresh Krishnan, 830 Dino Farinacci, Vincent Park, Jaehoon Paul Jeong, Gloria Gwynne, 831 Hans-Joachim Fischer, Russ Housley, Rex Buddenberg, Erik Nordmark, 832 Bob Moskowitz, Andrew (Dryden?), Georg Mayer, Dorothy Stanley, Sandra 833 Cespedes, Mariano Falcitelli, Sri Gundavelli and William Whyte. 834 Their valuable comments clarified particular issues and generally 835 helped to improve the document. 837 Pierre Pfister, Rostislav Lisovy, and others, wrote 802.11-OCB 838 drivers for linux and described how. 840 For the multicast discussion, the authors would like to thank Owen 841 DeLong, Joe Touch, Jen Linkova, Erik Kline, Brian Haberman and 842 participants to discussions in network working groups. 844 The authours would like to thank participants to the Birds-of- 845 a-Feather "Intelligent Transportation Systems" meetings held at IETF 846 in 2016. 848 10. References 850 10.1. Normative References 852 [I-D.ietf-tsvwg-ieee-802-11] 853 Szigeti, T., Henry, J., and F. Baker, "Diffserv to IEEE 854 802.11 Mapping", draft-ietf-tsvwg-ieee-802-11-09 (work in 855 progress), September 2017. 857 [RFC1042] Postel, J. and J. Reynolds, "Standard for the transmission 858 of IP datagrams over IEEE 802 networks", STD 43, RFC 1042, 859 DOI 10.17487/RFC1042, February 1988, 860 . 862 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 863 Requirement Levels", BCP 14, RFC 2119, 864 DOI 10.17487/RFC2119, March 1997, 865 . 867 [RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet 868 Networks", RFC 2464, DOI 10.17487/RFC2464, December 1998, 869 . 871 [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, 872 DOI 10.17487/RFC2818, May 2000, 873 . 875 [RFC3753] Manner, J., Ed. and M. Kojo, Ed., "Mobility Related 876 Terminology", RFC 3753, DOI 10.17487/RFC3753, June 2004, 877 . 879 [RFC3963] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. 880 Thubert, "Network Mobility (NEMO) Basic Support Protocol", 881 RFC 3963, DOI 10.17487/RFC3963, January 2005, 882 . 884 [RFC3971] Arkko, J., Ed., Kempf, J., Zill, B., and P. Nikander, 885 "SEcure Neighbor Discovery (SEND)", RFC 3971, 886 DOI 10.17487/RFC3971, March 2005, 887 . 889 [RFC4086] Eastlake 3rd, D., Schiller, J., and S. Crocker, 890 "Randomness Requirements for Security", BCP 106, RFC 4086, 891 DOI 10.17487/RFC4086, June 2005, 892 . 894 [RFC4210] Adams, C., Farrell, S., Kause, T., and T. Mononen, 895 "Internet X.509 Public Key Infrastructure Certificate 896 Management Protocol (CMP)", RFC 4210, 897 DOI 10.17487/RFC4210, September 2005, 898 . 900 [RFC4301] Kent, S. and K. Seo, "Security Architecture for the 901 Internet Protocol", RFC 4301, DOI 10.17487/RFC4301, 902 December 2005, . 904 [RFC4302] Kent, S., "IP Authentication Header", RFC 4302, 905 DOI 10.17487/RFC4302, December 2005, 906 . 908 [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", 909 RFC 4303, DOI 10.17487/RFC4303, December 2005, 910 . 912 [RFC4429] Moore, N., "Optimistic Duplicate Address Detection (DAD) 913 for IPv6", RFC 4429, DOI 10.17487/RFC4429, April 2006, 914 . 916 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 917 "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, 918 DOI 10.17487/RFC4861, September 2007, 919 . 921 [RFC5374] Weis, B., Gross, G., and D. Ignjatic, "Multicast 922 Extensions to the Security Architecture for the Internet 923 Protocol", RFC 5374, DOI 10.17487/RFC5374, November 2008, 924 . 926 [RFC5415] Calhoun, P., Ed., Montemurro, M., Ed., and D. Stanley, 927 Ed., "Control And Provisioning of Wireless Access Points 928 (CAPWAP) Protocol Specification", RFC 5415, 929 DOI 10.17487/RFC5415, March 2009, 930 . 932 [RFC5889] Baccelli, E., Ed. and M. Townsley, Ed., "IP Addressing 933 Model in Ad Hoc Networks", RFC 5889, DOI 10.17487/RFC5889, 934 September 2010, . 936 [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility 937 Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July 938 2011, . 940 [RFC6775] Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C. 941 Bormann, "Neighbor Discovery Optimization for IPv6 over 942 Low-Power Wireless Personal Area Networks (6LoWPANs)", 943 RFC 6775, DOI 10.17487/RFC6775, November 2012, 944 . 946 [RFC7136] Carpenter, B. and S. Jiang, "Significance of IPv6 947 Interface Identifiers", RFC 7136, DOI 10.17487/RFC7136, 948 February 2014, . 950 [RFC7217] Gont, F., "A Method for Generating Semantically Opaque 951 Interface Identifiers with IPv6 Stateless Address 952 Autoconfiguration (SLAAC)", RFC 7217, 953 DOI 10.17487/RFC7217, April 2014, 954 . 956 [RFC7721] Cooper, A., Gont, F., and D. Thaler, "Security and Privacy 957 Considerations for IPv6 Address Generation Mechanisms", 958 RFC 7721, DOI 10.17487/RFC7721, March 2016, 959 . 961 [RFC8064] Gont, F., Cooper, A., Thaler, D., and W. Liu, 962 "Recommendation on Stable IPv6 Interface Identifiers", 963 RFC 8064, DOI 10.17487/RFC8064, February 2017, 964 . 966 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 967 (IPv6) Specification", STD 86, RFC 8200, 968 DOI 10.17487/RFC8200, July 2017, 969 . 971 10.2. Informative References 973 [ETSI-IPv6-GeoNetworking] 974 "ETSI EN 302 636-6-1 v1.2.1 (2014-05), ETSI, European 975 Standard, Intelligent Transportation Systems (ITS); 976 Vehicular Communications; Geonetworking; Part 6: Internet 977 Integration; Sub-part 1: Transmission of IPv6 Packets over 978 Geonetworking Protocols. Downloaded on September 9th, 979 2017, freely available from ETSI website at URL 980 http://www.etsi.org/deliver/ 981 etsi_en/302600_302699/30263601/01.02.01_60/ 982 en_30263601v010201p.pdf". 984 [ETSI-sec-archi] 985 "ETSI TS 102 940 V1.2.1 (2016-11), ETSI Technical 986 Specification, Intelligent Transport Systems (ITS); 987 Security; ITS communications security architecture and 988 security management, November 2016. Dowloaded on 989 September 9th, 2017, freely available from ETSI website at 990 URL http://www.etsi.org/deliver/ 991 etsi_ts/102900_102999/102940/01.02.01_60/ 992 ts_102940v010201p.pdf". 994 [I-D.hinden-6man-rfc2464bis] 995 Crawford, M. and R. Hinden, "Transmission of IPv6 Packets 996 over Ethernet Networks", draft-hinden-6man-rfc2464bis-02 997 (work in progress), March 2017. 999 [I-D.jeong-ipwave-vehicular-networking-survey] 1000 Jeong, J., Cespedes, S., Benamar, N., Haerri, J., and M. 1001 Wetterwald, "Survey on IP-based Vehicular Networking for 1002 Intelligent Transportation Systems", draft-jeong-ipwave- 1003 vehicular-networking-survey-03 (work in progress), June 1004 2017. 1006 [I-D.perkins-intarea-multicast-ieee802] 1007 Perkins, C., Stanley, D., Kumari, W., and J. Zuniga, 1008 "Multicast Considerations over IEEE 802 Wireless Media", 1009 draft-perkins-intarea-multicast-ieee802-03 (work in 1010 progress), July 2017. 1012 [I-D.petrescu-its-scenarios-reqs] 1013 Petrescu, A., Janneteau, C., Boc, M., and W. Klaudel, 1014 "Scenarios and Requirements for IP in Intelligent 1015 Transportation Systems", draft-petrescu-its-scenarios- 1016 reqs-03 (work in progress), October 2013. 1018 [IEEE-1609.2] 1019 "IEEE SA - 1609.2-2016 - IEEE Standard for Wireless Access 1020 in Vehicular Environments (WAVE) -- Security Services for 1021 Applications and Management Messages. Example URL 1022 http://ieeexplore.ieee.org/document/7426684/ accessed on 1023 August 17th, 2017.". 1025 [IEEE-1609.3] 1026 "IEEE SA - 1609.3-2016 - IEEE Standard for Wireless Access 1027 in Vehicular Environments (WAVE) -- Networking Services. 1028 Example URL http://ieeexplore.ieee.org/document/7458115/ 1029 accessed on August 17th, 2017.". 1031 [IEEE-1609.4] 1032 "IEEE SA - 1609.4-2016 - IEEE Standard for Wireless Access 1033 in Vehicular Environments (WAVE) -- Multi-Channel 1034 Operation. Example URL 1035 http://ieeexplore.ieee.org/document/7435228/ accessed on 1036 August 17th, 2017.". 1038 [IEEE-802.11-2016] 1039 "IEEE Standard 802.11-2016 - IEEE Standard for Information 1040 Technology - Telecommunications and information exchange 1041 between systems Local and metropolitan area networks - 1042 Specific requirements - Part 11: Wireless LAN Medium 1043 Access Control (MAC) and Physical Layer (PHY) 1044 Specifications. Status - Active Standard. Description 1045 retrieved freely on September 12th, 2017, at URL 1046 https://standards.ieee.org/findstds/ 1047 standard/802.11-2016.html". 1049 [IEEE-802.11p-2010] 1050 "IEEE Std 802.11p (TM)-2010, IEEE Standard for Information 1051 Technology - Telecommunications and information exchange 1052 between systems - Local and metropolitan area networks - 1053 Specific requirements, Part 11: Wireless LAN Medium Access 1054 Control (MAC) and Physical Layer (PHY) Specifications, 1055 Amendment 6: Wireless Access in Vehicular Environments; 1056 document freely available at URL 1057 http://standards.ieee.org/getieee802/ 1058 download/802.11p-2010.pdf retrieved on September 20th, 1059 2013.". 1061 Appendix A. ChangeLog 1063 The changes are listed in reverse chronological order, most recent 1064 changes appearing at the top of the list. 1066 From draft-ietf-ipwave-ipv6-over-80211ocb-07 to draft-ietf-ipwave- 1067 ipv6-over-80211ocb-08 1069 o Removed the per-channel IPv6 prohibition text. 1071 o Corrected typographical errors. 1073 From draft-ietf-ipwave-ipv6-over-80211ocb-06 to draft-ietf-ipwave- 1074 ipv6-over-80211ocb-07 1076 o Added new terms: OBRU and RSRU ('R' for Router). Refined the 1077 existing terms RSU and OBU, which are no longer used throughout 1078 the document. 1080 o Improved definition of term "802.11-OCB". 1082 o Clarified that OCB does not "strip" security, but that the 1083 operation in OCB mode is "stripped off of all .11 security". 1085 o Clarified that theoretical OCB bandwidth speed is 54mbits, but 1086 that a commonly observed bandwidth in IP-over-OCB is 12mbit/s. 1088 o Corrected typographical errors, and improved some phrasing. 1090 From draft-ietf-ipwave-ipv6-over-80211ocb-05 to draft-ietf-ipwave- 1091 ipv6-over-80211ocb-06 1093 o Updated references of 802.11-OCB document from -2012 to the IEEE 1094 802.11-2016. 1096 o In the LL address section, and in SLAAC section, added references 1097 to 7217 opaque IIDs and 8064 stable IIDs. 1099 From draft-ietf-ipwave-ipv6-over-80211ocb-04 to draft-ietf-ipwave- 1100 ipv6-over-80211ocb-05 1102 o Lengthened the title and cleanded the abstract. 1104 o Added text suggesting LLs may be easy to use on OCB, rather than 1105 GUAs based on received prefix. 1107 o Added the risks of spoofing and hijacking. 1109 o Removed the text speculation on adoption of the TSA message. 1111 o Clarified that the ND protocol is used. 1113 o Clarified what it means "No association needed". 1115 o Added some text about how two STAs discover each other. 1117 o Added mention of external (OCB) and internal network (stable), in 1118 the subnet structure section. 1120 o Added phrase explaining that both .11 Data and .11 QoS Data 1121 headers are currently being used, and may be used in the future. 1123 o Moved the packet capture example into an Appendix Implementation 1124 Status. 1126 o Suggested moving the reliability requirements appendix out into 1127 another document. 1129 o Added a IANA Consiserations section, with content, requesting for 1130 a new multicast group "all OCB interfaces". 1132 o Added new OBU term, improved the RSU term definition, removed the 1133 ETTC term, replaced more occurences of 802.11p, 802.11 OCB with 1134 802.11-OCB. 1136 o References: 1138 * Added an informational reference to ETSI's IPv6-over- 1139 GeoNetworking. 1141 * Added more references to IETF and ETSI security protocols. 1143 * Updated some references from I-D to RFC, and from old RFC to 1144 new RFC numbers. 1146 * Added reference to multicast extensions to IPsec architecture 1147 RFC. 1149 * Added a reference to 2464-bis. 1151 * Removed FCC informative references, because not used. 1153 o Updated the affiliation of one author. 1155 o Reformulation of some phrases for better readability, and 1156 correction of typographical errors. 1158 From draft-ietf-ipwave-ipv6-over-80211ocb-03 to draft-ietf-ipwave- 1159 ipv6-over-80211ocb-04 1161 o Removed a few informative references pointing to Dx draft IEEE 1162 1609 documents. 1164 o Removed outdated informative references to ETSI documents. 1166 o Added citations to IEEE 1609.2, .3 and .4-2016. 1168 o Minor textual issues. 1170 From draft-ietf-ipwave-ipv6-over-80211ocb-02 to draft-ietf-ipwave- 1171 ipv6-over-80211ocb-03 1173 o Keep the previous text on multiple addresses, so remove talk about 1174 MIP6, NEMOv6 and MCoA. 1176 o Clarified that a 'Beacon' is an IEEE 802.11 frame Beacon. 1178 o Clarified the figure showing Infrastructure mode and OCB mode side 1179 by side. 1181 o Added a reference to the IP Security Architecture RFC. 1183 o Detailed the IPv6-per-channel prohibition paragraph which reflects 1184 the discussion at the last IETF IPWAVE WG meeting. 1186 o Added section "Address Mapping -- Unicast". 1188 o Added the ".11 Trailer" to pictures of 802.11 frames. 1190 o Added text about SNAP carrying the Ethertype. 1192 o New RSU definition allowing for it be both a Router and not 1193 necessarily a Router some times. 1195 o Minor textual issues. 1197 From draft-ietf-ipwave-ipv6-over-80211ocb-01 to draft-ietf-ipwave- 1198 ipv6-over-80211ocb-02 1200 o Replaced almost all occurences of 802.11p with 802.11-OCB, leaving 1201 only when explanation of evolution was necessary. 1203 o Shortened by removing parameter details from a paragraph in the 1204 Introduction. 1206 o Moved a reference from Normative to Informative. 1208 o Added text in intro clarifying there is no handover spec at IEEE, 1209 and that 1609.2 does provide security services. 1211 o Named the contents the fields of the EthernetII header (including 1212 the Ethertype bitstring). 1214 o Improved relationship between two paragraphs describing the 1215 increase of the Sequence Number in 802.11 header upon IP 1216 fragmentation. 1218 o Added brief clarification of "tracking". 1220 From draft-ietf-ipwave-ipv6-over-80211ocb-00 to draft-ietf-ipwave- 1221 ipv6-over-80211ocb-01 1223 o Introduced message exchange diagram illustrating differences 1224 between 802.11 and 802.11 in OCB mode. 1226 o Introduced an appendix listing for information the set of 802.11 1227 messages that may be transmitted in OCB mode. 1229 o Removed appendix sections "Privacy Requirements", "Authentication 1230 Requirements" and "Security Certificate Generation". 1232 o Removed appendix section "Non IP Communications". 1234 o Introductory phrase in the Security Considerations section. 1236 o Improved the definition of "OCB". 1238 o Introduced theoretical stacked layers about IPv6 and IEEE layers 1239 including EPD. 1241 o Removed the appendix describing the details of prohibiting IPv6 on 1242 certain channels relevant to 802.11-OCB. 1244 o Added a brief reference in the privacy text about a precise clause 1245 in IEEE 1609.3 and .4. 1247 o Clarified the definition of a Road Side Unit. 1249 o Removed the discussion about security of WSA (because is non-IP). 1251 o Removed mentioning of the GeoNetworking discussion. 1253 o Moved references to scientific articles to a separate 'overview' 1254 draft, and referred to it. 1256 Appendix B. Changes Needed on a software driver 802.11a to become a 1257 802.11-OCB driver 1259 The 802.11p amendment modifies both the 802.11 stack's physical and 1260 MAC layers but all the induced modifications can be quite easily 1261 obtained by modifying an existing 802.11a ad-hoc stack. 1263 Conditions for a 802.11a hardware to be 802.11-OCB compliant: 1265 o The PHY entity shall be an orthogonal frequency division 1266 multiplexing (OFDM) system. It must support the frequency bands 1267 on which the regulator recommends the use of ITS communications, 1268 for example using IEEE 802.11-OCB layer, in France: 5875MHz to 1269 5925MHz. 1271 o The OFDM system must provide a "half-clocked" operation using 10 1272 MHz channel spacings. 1274 o The chip transmit spectrum mask must be compliant to the "Transmit 1275 spectrum mask" from the IEEE 802.11p amendment (but experimental 1276 environments tolerate otherwise). 1278 o The chip should be able to transmit up to 44.8 dBm when used by 1279 the US government in the United States, and up to 33 dBm in 1280 Europe; other regional conditions apply. 1282 Changes needed on the network stack in OCB mode: 1284 o Physical layer: 1286 * The chip must use the Orthogonal Frequency Multiple Access 1287 (OFDM) encoding mode. 1289 * The chip must be set in half-mode rate mode (the internal clock 1290 frequency is divided by two). 1292 * The chip must use dedicated channels and should allow the use 1293 of higher emission powers. This may require modifications to 1294 the local computer file that describes regulatory domains 1295 rules, if used by the kernel to enforce local specific 1296 restrictions. Such modifications to the local computer file 1297 must respect the location-specific regulatory rules. 1299 MAC layer: 1301 * All management frames (beacons, join, leave, and others) 1302 emission and reception must be disabled except for frames of 1303 subtype Action and Timing Advertisement (defined below). 1305 * No encryption key or method must be used. 1307 * Packet emission and reception must be performed as in ad-hoc 1308 mode, using the wildcard BSSID (ff:ff:ff:ff:ff:ff). 1310 * The functions related to joining a BSS (Association Request/ 1311 Response) and for authentication (Authentication Request/Reply, 1312 Challenge) are not called. 1314 * The beacon interval is always set to 0 (zero). 1316 * Timing Advertisement frames, defined in the amendment, should 1317 be supported. The upper layer should be able to trigger such 1318 frames emission and to retrieve information contained in 1319 received Timing Advertisements. 1321 Appendix C. Design Considerations 1323 The networks defined by 802.11-OCB are in many ways similar to other 1324 networks of the 802.11 family. In theory, the encapsulation of IPv6 1325 over 802.11-OCB could be very similar to the operation of IPv6 over 1326 other networks of the 802.11 family. However, the high mobility, 1327 strong link asymmetry and very short connection makes the 802.11-OCB 1328 link significantly different from other 802.11 networks. Also, the 1329 automotive applications have specific requirements for reliability, 1330 security and privacy, which further add to the particularity of the 1331 802.11-OCB link. 1333 C.1. Vehicle ID 1335 In automotive networks it is required that each node is represented 1336 uniquely. Accordingly, a vehicle must be identified by at least one 1337 unique identifier. The current specification at ETSI and at IEEE 1338 1609 identifies a vehicle by its MAC address, which is obtained from 1339 the 802.11-OCB Network Interface Card (NIC). 1341 In case multiple 802.11-OCB NICs are present in one car, implicitely 1342 multiple vehicle IDs will be generated. Additionally, some software 1343 generates a random MAC address each time the computer boots; this 1344 constitutes an additional difficulty. 1346 A mechanim to uniquely identify a vehicle irrespectively to the 1347 multiplicity of NICs, or frequent MAC address generation, is 1348 necessary. 1350 C.2. Reliability Requirements 1352 This section may need to be moved out into a separate requirements 1353 document. 1355 The dynamically changing topology, short connectivity, mobile 1356 transmitter and receivers, different antenna heights, and many-to- 1357 many communication types, make IEEE 802.11-OCB links significantly 1358 different from other IEEE 802.11 links. Any IPv6 mechanism operating 1359 on IEEE 802.11-OCB link MUST support strong link asymmetry, spatio- 1360 temporal link quality, fast address resolution and transmission. 1362 IEEE 802.11-OCB strongly differs from other 802.11 systems to operate 1363 outside of the context of a Basic Service Set. This means in 1364 practice that IEEE 802.11-OCB does not rely on a Base Station for all 1365 Basic Service Set management. In particular, IEEE 802.11-OCB SHALL 1366 NOT use beacons. Any IPv6 mechanism requiring L2 services from IEEE 1367 802.11 beacons MUST support an alternative service. 1369 Channel scanning being disabled, IPv6 over IEEE 802.11-OCB MUST 1370 implement a mechanism for transmitter and receiver to converge to a 1371 common channel. 1373 Authentication not being possible, IPv6 over IEEE 802.11-OCB MUST 1374 implement an distributed mechanism to authenticate transmitters and 1375 receivers without the support of a DHCP server. 1377 Time synchronization not being available, IPv6 over IEEE 802.11-OCB 1378 MUST implement a higher layer mechanism for time synchronization 1379 between transmitters and receivers without the support of a NTP 1380 server. 1382 The IEEE 802.11-OCB link being asymmetric, IPv6 over IEEE 802.11-OCB 1383 MUST disable management mechanisms requesting acknowledgements or 1384 replies. 1386 The IEEE 802.11-OCB link having a short duration time, IPv6 over IEEE 1387 802.11-OCB SHOULD implement fast IPv6 mobility management mechanisms. 1389 C.3. Multiple interfaces 1391 There are considerations for 2 or more IEEE 802.11-OCB interface 1392 cards per vehicle. For each vehicle taking part in road traffic, one 1393 IEEE 802.11-OCB interface card could be fully allocated for Non IP 1394 safety-critical communication. Any other IEEE 802.11-OCB may be used 1395 for other type of traffic. 1397 The mode of operation of these other wireless interfaces is not 1398 clearly defined yet. One possibility is to consider each card as an 1399 independent network interface, with a specific MAC Address and a set 1400 of IPv6 addresses. Another possibility is to consider the set of 1401 these wireless interfaces as a single network interface (not 1402 including the IEEE 802.11-OCB interface used by Non IP safety 1403 critical communications). This will require specific logic to 1404 ensure, for example, that packets meant for a vehicle in front are 1405 actually sent by the radio in the front, or that multiple copies of 1406 the same packet received by multiple interfaces are treated as a 1407 single packet. Treating each wireless interface as a separate 1408 network interface pushes such issues to the application layer. 1410 Certain privacy requirements imply that if these multiple interfaces 1411 are represented by many network interface, a single renumbering event 1412 SHALL cause renumbering of all these interfaces. If one MAC changed 1413 and another stayed constant, external observers would be able to 1414 correlate old and new values, and the privacy benefits of 1415 randomization would be lost. 1417 The privacy requirements of Non IP safety-critical communications 1418 imply that if a change of pseudonyme occurs, renumbering of all other 1419 interfaces SHALL also occur. 1421 C.4. MAC Address Generation 1423 When designing the IPv6 over 802.11-OCB address mapping, we will 1424 assume that the MAC Addresses will change during well defined 1425 "renumbering events". The 48 bits randomized MAC addresses will have 1426 the following characteristics: 1428 o Bit "Local/Global" set to "locally admninistered". 1430 o Bit "Unicast/Multicast" set to "Unicast". 1432 o 46 remaining bits set to a random value, using a random number 1433 generator that meets the requirements of [RFC4086]. 1435 The way to meet the randomization requirements is to retain 46 bits 1436 from the output of a strong hash function, such as SHA256, taking as 1437 input a 256 bit local secret, the "nominal" MAC Address of the 1438 interface, and a representation of the date and time of the 1439 renumbering event. 1441 Appendix D. IEEE 802.11 Messages Transmitted in OCB mode 1443 For information, at the time of writing, this is the list of IEEE 1444 802.11 messages that may be transmitted in OCB mode, i.e. when 1445 dot11OCBActivated is true in a STA: 1447 o The STA may send management frames of subtype Action and, if the 1448 STA maintains a TSF Timer, subtype Timing Advertisement; 1450 o The STA may send control frames, except those of subtype PS-Poll, 1451 CF-End, and CF-End plus CFAck; 1453 o The STA may send data frames of subtype Data, Null, QoS Data, and 1454 QoS Null. 1456 Appendix E. Implementation Status 1458 This section describes an example of an IPv6 Packet captured over a 1459 IEEE 802.11-OCB link. 1461 By way of example we show that there is no modification in the 1462 headers when transmitted over 802.11-OCB networks - they are 1463 transmitted like any other 802.11 and Ethernet packets. 1465 We describe an experiment of capturing an IPv6 packet on an 1466 802.11-OCB link. In this experiment, the packet is an IPv6 Router 1467 Advertisement. This packet is emitted by a Router on its 802.11-OCB 1468 interface. The packet is captured on the Host, using a network 1469 protocol analyzer (e.g. Wireshark); the capture is performed in two 1470 different modes: direct mode and 'monitor' mode. The topology used 1471 during the capture is depicted below. 1473 +--------+ +-------+ 1474 | | 802.11-OCB Link | | 1475 ---| Router |--------------------------------| Host | 1476 | | | | 1477 +--------+ +-------+ 1479 During several capture operations running from a few moments to 1480 several hours, no message relevant to the BSSID contexts were 1481 captured (no Association Request/Response, Authentication Req/Resp, 1482 Beacon). This shows that the operation of 802.11-OCB is outside the 1483 context of a BSSID. 1485 Overall, the captured message is identical with a capture of an IPv6 1486 packet emitted on a 802.11b interface. The contents are precisely 1487 similar. 1489 E.1. Capture in Monitor Mode 1491 The IPv6 RA packet captured in monitor mode is illustrated below. 1492 The radio tap header provides more flexibility for reporting the 1493 characteristics of frames. The Radiotap Header is prepended by this 1494 particular stack and operating system on the Host machine to the RA 1495 packet received from the network (the Radiotap Header is not present 1496 on the air). The implementation-dependent Radiotap Header is useful 1497 for piggybacking PHY information from the chip's registers as data in 1498 a packet understandable by userland applications using Socket 1499 interfaces (the PHY interface can be, for example: power levels, data 1500 rate, ratio of signal to noise). 1502 The packet present on the air is formed by IEEE 802.11 Data Header, 1503 Logical Link Control Header, IPv6 Base Header and ICMPv6 Header. 1505 Radiotap Header v0 1506 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1507 |Header Revision| Header Pad | Header length | 1508 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1509 | Present flags | 1510 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1511 | Data Rate | Pad | 1512 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1514 IEEE 802.11 Data Header 1515 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1516 | Type/Subtype and Frame Ctrl | Duration | 1517 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1518 | Receiver Address... 1519 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1520 ... Receiver Address | Transmitter Address... 1521 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1522 ... Transmitter Address | 1523 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1524 | BSS Id... 1525 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1526 ... BSS Id | Frag Number and Seq Number | 1527 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1529 Logical-Link Control Header 1530 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1531 | DSAP |I| SSAP |C| Control field | Org. code... 1532 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1533 ... Organizational Code | Type | 1534 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1536 IPv6 Base Header 1537 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1538 |Version| Traffic Class | Flow Label | 1539 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1540 | Payload Length | Next Header | Hop Limit | 1541 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1542 | | 1543 + + 1544 | | 1545 + Source Address + 1546 | | 1547 + + 1548 | | 1549 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1550 | | 1551 + + 1552 | | 1553 + Destination Address + 1554 | | 1555 + + 1556 | | 1557 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1559 Router Advertisement 1560 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1561 | Type | Code | Checksum | 1562 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1563 | Cur Hop Limit |M|O| Reserved | Router Lifetime | 1564 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1565 | Reachable Time | 1566 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1567 | Retrans Timer | 1568 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1569 | Options ... 1570 +-+-+-+-+-+-+-+-+-+-+-+- 1572 The value of the Data Rate field in the Radiotap header is set to 6 1573 Mb/s. This indicates the rate at which this RA was received. 1575 The value of the Transmitter address in the IEEE 802.11 Data Header 1576 is set to a 48bit value. The value of the destination address is 1577 33:33:00:00:00:1 (all-nodes multicast address). The value of the BSS 1578 Id field is ff:ff:ff:ff:ff:ff, which is recognized by the network 1579 protocol analyzer as being "broadcast". The Fragment number and 1580 sequence number fields are together set to 0x90C6. 1582 The value of the Organization Code field in the Logical-Link Control 1583 Header is set to 0x0, recognized as "Encapsulated Ethernet". The 1584 value of the Type field is 0x86DD (hexadecimal 86DD, or otherwise 1585 #86DD), recognized as "IPv6". 1587 A Router Advertisement is periodically sent by the router to 1588 multicast group address ff02::1. It is an icmp packet type 134. The 1589 IPv6 Neighbor Discovery's Router Advertisement message contains an 1590 8-bit field reserved for single-bit flags, as described in [RFC4861]. 1592 The IPv6 header contains the link local address of the router 1593 (source) configured via EUI-64 algorithm, and destination address set 1594 to ff02::1. Recent versions of network protocol analyzers (e.g. 1595 Wireshark) provide additional informations for an IP address, if a 1596 geolocalization database is present. In this example, the 1597 geolocalization database is absent, and the "GeoIP" information is 1598 set to unknown for both source and destination addresses (although 1599 the IPv6 source and destination addresses are set to useful values). 1600 This "GeoIP" can be a useful information to look up the city, 1601 country, AS number, and other information for an IP address. 1603 The Ethernet Type field in the logical-link control header is set to 1604 0x86dd which indicates that the frame transports an IPv6 packet. In 1605 the IEEE 802.11 data, the destination address is 33:33:00:00:00:01 1606 which is the corresponding multicast MAC address. The BSS id is a 1607 broadcast address of ff:ff:ff:ff:ff:ff. Due to the short link 1608 duration between vehicles and the roadside infrastructure, there is 1609 no need in IEEE 802.11-OCB to wait for the completion of association 1610 and authentication procedures before exchanging data. IEEE 1611 802.11-OCB enabled nodes use the wildcard BSSID (a value of all 1s) 1612 and may start communicating as soon as they arrive on the 1613 communication channel. 1615 E.2. Capture in Normal Mode 1617 The same IPv6 Router Advertisement packet described above (monitor 1618 mode) is captured on the Host, in the Normal mode, and depicted 1619 below. 1621 Ethernet II Header 1622 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1623 | Destination... 1624 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1625 ...Destination | Source... 1626 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1627 ...Source | 1628 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1629 | Type | 1630 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1632 IPv6 Base Header 1633 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1634 |Version| Traffic Class | Flow Label | 1635 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1636 | Payload Length | Next Header | Hop Limit | 1637 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1638 | | 1639 + + 1640 | | 1641 + Source Address + 1642 | | 1643 + + 1644 | | 1645 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1646 | | 1647 + + 1648 | | 1649 + Destination Address + 1650 | | 1651 + + 1652 | | 1653 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1655 Router Advertisement 1656 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1657 | Type | Code | Checksum | 1658 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1659 | Cur Hop Limit |M|O| Reserved | Router Lifetime | 1660 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1661 | Reachable Time | 1662 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1663 | Retrans Timer | 1664 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1665 | Options ... 1666 +-+-+-+-+-+-+-+-+-+-+-+- 1668 One notices that the Radiotap Header, the IEEE 802.11 Data Header and 1669 the Logical-Link Control Headers are not present. On the other hand, 1670 a new header named Ethernet II Header is present. 1672 The Destination and Source addresses in the Ethernet II header 1673 contain the same values as the fields Receiver Address and 1674 Transmitter Address present in the IEEE 802.11 Data Header in the 1675 "monitor" mode capture. 1677 The value of the Type field in the Ethernet II header is 0x86DD 1678 (recognized as "IPv6"); this value is the same value as the value of 1679 the field Type in the Logical-Link Control Header in the "monitor" 1680 mode capture. 1682 The knowledgeable experimenter will no doubt notice the similarity of 1683 this Ethernet II Header with a capture in normal mode on a pure 1684 Ethernet cable interface. 1686 An Adaptation layer is inserted on top of a pure IEEE 802.11 MAC 1687 layer, in order to adapt packets, before delivering the payload data 1688 to the applications. It adapts 802.11 LLC/MAC headers to Ethernet II 1689 headers. In further detail, this adaptation consists in the 1690 elimination of the Radiotap, 802.11 and LLC headers, and in the 1691 insertion of the Ethernet II header. In this way, IPv6 runs straight 1692 over LLC over the 802.11-OCB MAC layer; this is further confirmed by 1693 the use of the unique Type 0x86DD. 1695 Authors' Addresses 1697 Alexandre Petrescu 1698 CEA, LIST 1699 CEA Saclay 1700 Gif-sur-Yvette , Ile-de-France 91190 1701 France 1703 Phone: +33169089223 1704 Email: Alexandre.Petrescu@cea.fr 1706 Nabil Benamar 1707 Moulay Ismail University 1708 Morocco 1710 Phone: +212670832236 1711 Email: benamar73@gmail.com 1712 Jerome Haerri 1713 Eurecom 1714 Sophia-Antipolis 06904 1715 France 1717 Phone: +33493008134 1718 Email: Jerome.Haerri@eurecom.fr 1720 Christian Huitema 1721 Private Octopus Inc. 1722 Friday Harbor, WA 98250 1723 U.S.A. 1725 Email: huitema@huitema.net 1727 Jong-Hyouk Lee 1728 Sangmyung University 1729 31, Sangmyeongdae-gil, Dongnam-gu 1730 Cheonan 31066 1731 Republic of Korea 1733 Email: jonghyouk@smu.ac.kr 1735 Thierry Ernst 1736 YoGoKo 1737 France 1739 Email: thierry.ernst@yogoko.fr 1741 Tony Li 1742 Peloton Technology 1743 1060 La Avenida St. 1744 Mountain View, California 94043 1745 United States 1747 Phone: +16503957356 1748 Email: tony.li@tony.li