Service and Neighbor Discovery in ITS
draft-yan-ipwave-nd-03

Document Type Active Internet-Draft (individual)
Last updated 2018-10-15
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
Network Working Group                                             Z. Yan
Internet-Draft                                                     CNNIC
Intended status: Standards Track                                  J. Lee
Expires: April 18, 2019                             Sangmyung University
                                                        October 15, 2018

                 Service and Neighbor Discovery in ITS
                       draft-yan-ipwave-nd-03.txt

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].

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 April 18, 2019.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Yan & Lee                Expires April 18, 2019                 [Page 1]
Internet-Draft                   ITS ND                     October 2018

   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  . . . . . . . . . . . . . . . . . . . . .   5
   8.  Security considerations . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   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 ITS.  Based on the naming scheme like this and the
   widely-used DNS-SD/mDNS protocol, this draft illustrates how to
   discover the neighbor vehicle or services with DNS resolution logic.
   Before this, we make the following assumptions:

   o  Name: vehicle SHOULD have a temporary name which is related to its
      geo-location.

   o  Address: vehicle SHOULD have a global IP address which is
      routeable for the IP communications.

   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 extended NDP messages (e.g., RA and RS messages) can
   also be used to exchange some required information (e.g., mobile

Yan & Lee                Expires April 18, 2019                 [Page 2]
Internet-Draft                   ITS ND                     October 2018

   network prefixes, link-local address) in ITS in combination with DNS-
   SD/mDNS [MNPP].

2.  Prefix management

   The network architecture which illustrates the prefix management of
Show full document text