Service and Neighbor Vehicle Discovery in IPv6-Based Vehicular Networks
draft-yan-ipwave-nd-06
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2020-05-17
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
htmlized (tools)
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. Weng
Expires: November 18, 2020 G. Geng
Jinan University
J. Lee
Sangmyung University
J. Jeong
Sungkyunkwan University
May 17, 2020
Service and Neighbor Vehicle Discovery in IPv6-Based Vehicular Networks
draft-yan-ipwave-nd-06.txt
Abstract
For Cooperative Adaptive Cruise Control (C-ACC), platooning and other
typical use cases in Intelligent Transportation System (ITS), IPv6
communication between neighbor vehicles and between vehicle and
server pose the following two issues: 1) how to discover a neighbor
vehicle and the demanded service; and 2) how to discover the link-
layer address and other metadata 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 November 18, 2020.
Yan, et al. Expires November 18, 2020 [Page 1]
Internet-Draft ITS SeNeDis May 2020
Copyright Notice
Copyright (c) 2020 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. Name and address configurations . . . . . . . . . . . . . . . 3
3. Service and neighbor vehicle discovery . . . . . . . . . . . 3
4. Mobility support . . . . . . . . . . . . . . . . . . . . . . 5
5. Signaling messages . . . . . . . . . . . . . . . . . . . . . 5
6. Security considerations . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . 6
7.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 communication 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 at least one temporary name which may
be related with its geo-location or provided services. This name
is related with the service or identifier of the particular
vehicle.
o Address: A vehicle SHOULD have at least one global IP address
which is routable for the IPv6 communications. This address acts
as the Home Address (HoA) of vehicle to facilitate its mobility.
Yan, et al. Expires November 18, 2020 [Page 2]
Show full document text