Neighbor Vehicle Discovery and Service in IP-Based Vehicular Networks
draft-yan-ipwave-nd-05
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-11-17
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
IPWAVE Working Group Z. Yan
Internet-Draft CNNIC
Intended status: Standards Track J. Lee
Expires: May 20, 2020 Sangmyung University
J. Jeong
Sungkyunkwan University
November 17, 2019
Neighbor Vehicle Discovery and Service in IP-Based Vehicular Networks
draft-yan-ipwave-nd-05.txt
Abstract
For Cooperative Adaptive Cruise Control (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 a
neighbor vehicle and the demanded service; and 2) how to discover the
link-layer address of the neighbor vehicle and selected server. This
document presents a solution to these problems based on DNS-SD/mDNS
[RFC6762][RFC6763].
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 20, 2020.
Yan, et al. Expires May 20, 2020 [Page 1]
Internet-Draft ITS ND November 2019
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Prefix management . . . . . . . . . . . . . . . . . . . . . . 3
3. Name configuration . . . . . . . . . . . . . . . . . . . . . 3
4. Address configuration . . . . . . . . . . . . . . . . . . . . 4
5. Neighbor vehicle and service discovery . . . . . . . . . . . 4
6. Mobility support . . . . . . . . . . . . . . . . . . . . . . 5
7. Signaling messages . . . . . . . . . . . . . . . . . . . . . 6
8. Security considerations . . . . . . . . . . . . . . . . . . . 6
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
9.1. Normative References . . . . . . . . . . . . . . . . . . 6
9.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
As illustrated in [DNS-Autoconf], a naming scheme is needed for the
vehicle devices to support the unique name auto-configuration. This
can support the location based communicaton and scalable information
organization in Intelligent Transportation Systems (ITS). Based on
the naming scheme like this and the widely-used DNS-SD/mDNS protocol,
this document illustrates how to discover a neighbor vehicle or the
required services with DNS resolution logic. Before this, we make
the following assumptions:
o Name: A vehicle SHOULD have a temporary name which is related to
its geo-location.
o Address: A vehicle SHOULD have a global IP address which is
routeable for the IP communications.
Yan, et al. Expires May 20, 2020 [Page 2]
Internet-Draft ITS ND November 2019
In this way, a standardized, efficient and scalable scheme can be
used to retrieve the necessary information of the corresponding node
(domain name, IP address, goe-location, link-local address and so on)
for the further communications based on the DNS-SD/mDNS function. In
addition, the IPv6 Neighbor Discovery (ND)'s messages (e.g., RA and
Show full document text