Service and Neighbor Discovery in ITS
draft-yan-ipwave-nd-03
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Zhiwei Yan , Jong-Hyouk Lee | ||
| Last updated | 2019-04-18 (Latest revision 2018-10-15) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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 C-ACC, platooning and other typical use cases in ITS, direct IP communication between neighbor vehicles poses the following two issues: 1) how to discover the neighbor vehicle and the demanded service; and 2) how to discover the link-layer address of the neighbor vehicle and selected server. This draft presents a solution to these problems based on DNS-SD/mDNS [RFC6762][RFC6763].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)