IPv6 Mobile Object Networking (IPMON): Problem Statement and Use Cases
draft-jeong-6man-ipmon-problem-statement-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jaehoon Paul Jeong , Yiwen Shen , Sri Gundavelli | ||
| Last updated | 2023-09-27 (Latest revision 2023-03-26) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document discusses the problem statement and use cases of IPv6 Mobile Object Networking (IPMON). A moving object is a physically movable networked device with 5G communication capability, such as a terrestrial vehicle (e.g., car and motorcycle), a user's smart device (e.g., smartphone, smart watch, and tablet), an aerial vehicle (e.g., drone and helicopter), and a marine vehicle (e.g., boat and ship). These mobile objects are called vehicles in this document. The main scenarios of vehicular communications are vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X) communications. First, this document explains use cases using V2V, V2I, and V2X networking over 5G. Next, for IPv6-over-5G vehicular networks, it makes a gap analysis of current IPv6 protocols (e.g., IPv6 Neighbor Discovery).
Authors
Jaehoon Paul Jeong
Yiwen Shen
Sri Gundavelli
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)