Skip to main content

IPv6 Moving Object Networking (ipmon)

Document Type Declined BOF request
Title IPv6 Moving Object Networking (ipmon)
Last updated 2022-09-29
State Declined
Editor Jaehoon Paul Jeong
Responsible leadership Erik Kline
Send notices to (None)

Name: IPv6 Moving Object Networking (ipmon)


Moving objects of terrestrial vehicles (e.g., automobiles, motorcycles, and electric scooters), aircrafts (e.g., unmanned aerial vehicle (UAV) like drones, airplanes, and helicopters), watercrafts (e.g., boats, ships, and submarines), and mobile robots for smart buildings are increasingly connected to the Internet through various wireless communications. Comfort-enhancing entertainment applications, driving/flying/sailing safety applications using bidirectional data flows, and connected automated maneuvering are some of the new features expected in moving objects (denoted as vehicle in this charter) to hit the movement spaces (e.g., roadway, street, sky, river, and sea) from now to year 2022. Especially, aerial vehicles for Urban Air Mobility (UAM) are actively developed by the Industry (e.g., Honeywell and Hyundai Motor Group).

Today, there is Vehicle-to-Everything (V2X) communications that makes use of embedded Internet modules, or an occupant's cellular smartphone in vehicular networks. Vehicle-to-Infrastructure (V2I) communications is used for wireless exchange of critical safety and operational data between vehicles and infrastructure nodes (e.g., road-side units and edge computing devices), intended primarily to avoid vehicle crashes and road hazards. Similarly, Vehicle-to-Vehicle (V2V) communications is used for short-range communications between vehicles to exchange vehicle information such as vehicle speed, heading, braking status, and collision situations.
Also, Vehicle-to-Pedestrian (V2P) communications is used for short-range communications between vehicles and pedestrians' mobile devices (e.g., smartphone and smart watch) to exchange street context information such as the existence of moving objects (e.g., cars, trucks, pedestrians, bikes, motorcycles, and electric scooters) and collision situations.

This group will work on use cases of V2X (e.g., V2V, V2I, and V2P) where IPv6 is well-suited as a networking technology and will develop IPv6-based solutions to establish direct and secure connectivity among moving objects or among moving objects and stationary systems. These vehicular networks are characterized by dynamically changing network topologies and connectivity.

V2V and V2I communications may involve various kinds of link layers: IEEE 802.11-OCB (Outside the Context of a Basic Service Set), 802.11bd, 802.11ad, 802.15.4 with 6lowpan, VLC (Visible Light Communications), IrDA, LTE-D, LP-WAN, UWB, and 5G V2X. One of the most used link layers for vehicular networks is IEEE 802.11-OCB, as a basis for Dedicated short-range communications (DSRC). Several of these link-layers already provide support for IPv6. IPv6 on 802.11-OCB has been standardized as RFC 8691 by IPWAVE WG since 2019. However, IPv6 on 5G V2X needs to be fully defined by this working group. Some aspects of the IPv6 over 5G V2X have been already defined at 3GPP specification and the specification produced by this working group is expected be compatible with these aspects. Also, if IPv6 over IEEE 802.11bd needs some modification from RFC 8691, this group will work on a work item for it.

This group's primary deliverable (and the only Standards track item) will include documents that will specify the mechanisms for transmission of IPv6 datagrams over either 3GPP 5G V2X or IEEE 802.11bd V2X. Once these documents are completed, they will also be reviewed by the 6man working group. Along with these work items, the following key technologies, which are identified by IPWAVE WG's problem statement and use cases document, need to be standardized for moving objects as follows.

Program of Work

The IPMON working group's deliverables include:

  1. Basic Support for IPv6 over 3GPP 5G V2X
  2. Basic Support for IPv6 over IEEE 802.11bd V2X
  3. Vehicular Neighbor Discovery
  4. Vehicular Mobility Management
  5. Vehicular Security and Privacy
  6. Context-Aware Navigation Protocol for Physical Collision Avoidance in Vehicular Networks
  7. Data Aggregation for Vehicular Networks
  8. DNS Naming for Moving Objects
  9. Service Discovery for Moving Objects

Required Details

Information for IAB/IESG

To allow evaluation of your proposal, please include the following items:

  • Any protocols or practices that already exist in this space:

o IPv6 Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases

o Vehicular Neighbor Discovery for IP-Based Vehicular Networks

o Vehicular Mobility Management for IP-Based Vehicular Networks

o Basic Support for Security and Privacy in IP-Based Vehicular Networks

o Context-Aware Navigation Protocol for IP-Based Vehicular Networks

o Service and Neighbor Vehicle Discovery in IPv6-Based Vehicular Networks

o DNS Name Autoconfiguration for Internet-of-Things Devices in IP-Based Vehicular Networks

  • Open source projects (if any) implementing this work:

o IPWAVE Basic Protocols Project