175x Filetype PPTX File size 0.06 MB Source: www.itu.int
Contents • What is IPWAVE Working Group • Main WG item: IPv6 over 802.11 OCB • Additional WG item: Problem Statement and Use Cases • Perspectives IPWAVE Working Group • IP Wireless Access in Vehicular Environments (IPWAVE) is a Working Group at the Internet Engineering Task Force (IETF). • Works on “V2V and V2I use-cases where IP is well-suited as a networking technology”. • Liaisons with ISO TC 204, SAE, ETSI ITS, IEEE, ITU CITS, ITU-R WP 5A. • Group formed in year 2016, after successful Birds-of-a-Feather (BoF) www.ietfjournal.org/intelligent-transportation-systems-and-the-ietf/ • Email list, roughly 340 subscribers www.ietf.org/mailman/listinfo/its Main Work Item: IPv6 over 802.11- OCB • draft-ietf-ipwave-ipv6-over-80211ocb-52 publicly accessible • IEEE 802.11p is a MAC and PHY layer for vehicular wireless networks: • Operates Outside the Context of a BSSID (802.11-OCB). • Works at 5.9GHz bands channels with a short 10MHz width. • Requires the use of 802.11 “QoS Data” headers. • Higher power levels are allowed (33 dBm, 40 dBm, country-specific). • Future evolutions: 802.11bd. • Running an IP layer on 802.11-OCB requires the definition of a few parameters: • EtherType is 0x86DD • Default MTU is 1500 bytes, minimum MTU size is 1280 bytes • Priority (TID) is 1, i.e. ‘Background’, also known as ‘AC_BK’ • Interface Identifiers are: • based on EUI-64, or are ‘Stable’ or ‘Opaque’ IIDs; • of length 64 bit. • Use IPv6-over-Ethernet [RFC2464], and a simple “frame translation from 802.3 to 802.11 in order to minimize the code changes.” • Subnet structure: recommendations on the use of Neighbor Discovery and Mobile IPv6 protocols in vehicular settings. • Security considerations, privacy. Status • RFC 8691 “Basic Support for IPv6 Networks Operating Outside the Context of a Basic Service Set over IEEE Std 802.11” • issued in December 2019 • Implementation of RFC 8691 is straightforward: • Available as a patch to linux kernels (some parts fully integrated in mainline) See an OCB patch for 16mbit/s and less, at e.g. https://github.com/jfpastrana/ath9k_ocb_linux_4.2.8 • Not yet available on BSD systems • Advancements towards the use of IPv6 with ath10k drivers • For a higher bandwidth OCB (more than 16mbit/s for vehicle networks, e.g. 1Gbit/s) • See the OCB patch at: https://gitlab.com/hpi-potsdam/osm/g5-on-linux/11p-on-linux/-/tree/ath10k (important note: contrary to github, one can browse that gitlab URL on IPv6 as well, without a need of having IPv4 on the computer) Topologies for using IPv6 for Vehicle Networks • Disconnected from the • Vehicle-to-Vehicle IP network topology: Internet • Scales well very large IPv6 IPv6 IPv6 (more than what ITS-G5 Vehicle over OCB Vehicle over OCB over OCB Vehicle can do on 5 channels) at 5.9GHz at 5.9GHz at 5.9GHz • subnet1 subnet2 subnetn Demonstrated in camera- less and driver-less convoy (platoon) • Vehicle-to-Internet IP network topology: • Connected to the Internet IPv6 • Offers access to Internet over OCB at 5.9GHz without going to cellular subnet Internet network Vehicle RSU • Works simultaneously with non-IP CAMs or BSMs, on same channels • Other variations
no reviews yet
Please Login to review.