Problem Statements of IPv6-based Geographical Forwarding for ITS
draft-ahn-its-geo-problem-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Sanghyun Ahn | ||
| Last updated | 2017-06-22 (Latest revision 2016-12-19) | ||
| 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
For the support of IPv6-based ITS applications, ITS data packets are required to be delivered based on the geographical location (longitude and latitude) information of the destination ITS node or area. Therefore, geographical forwarding mechanisms are preferred in the ITS environment. In this draft, we define the issues to be considered in delivering IPv6 ITS data based on geographical location.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)