Neighbor discovery to support direct communication in ITS
draft-yan-its-nd-01

Document Type Active Internet-Draft (individual)
Last updated 2016-10-25
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 28, 2017                             Sangmyung University
                                                        October 25, 2016

       Neighbor discovery to support direct communication in ITS
                        draft-yan-its-nd-01.txt

Abstract

   For C-ACC, Platooning and other typical use cases in ITS, how to
   establish direct IP communication paths between neighbor vehicles
   poses two issues : how to discover the neighbor vehicle and the
   nearby service (from the upper layer); how to discover the link-layer
   address of the selected vehicle (from the lower layer).  This draft
   aims to solve these problems based on mDNS.

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 http://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 28, 2017.

Copyright Notice

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

Yan & Lee                Expires April 28, 2017                 [Page 1]
Internet-Draft               ITS Vehicle ND                 October 2016

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://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 configuration  . . . . . . . . . . . . . . . . . . . . .   3
   3.  Address configuration . . . . . . . . . . . . . . . . . . . .   3
   4.  Neighbor discovery  . . . . . . . . . . . . . . . . . . . . .   3
   5.  Handover  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Signaling messages  . . . . . . . . . . . . . . . . . . . . .   4
   7.  Security considerations . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   As illustrated in [DNS-Autoconf] draft, a naming scheme is proposed
   for the vehicle devices to support the unique name auto-
   configuration.  This can be used to support the location based
   communicaton and scalable information organization in ITS.  Based on
   the naming scheme like this and the mature mDNS protocol, this draft
   illustrates how to discover the neighbor vehicle or services with the
   infrastructure-less DNS resolution.  Before this, we have the
   following assumptions:

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

   o  Address: vehicle SHOULD have a global IP address which is stable.

   In this way, a standardized and efficient scheme can be used to
   retrieve the necessary information of the neighbor vehicles (domain
   name, IP address, goe-location and so on) for the further direct
   communications based on the mDNS function.

Yan & Lee                Expires April 28, 2017                 [Page 2]
Internet-Draft               ITS Vehicle ND                 October 2016

2.  Name configuration

   The RSU acts as an access router for the static and moving vehicles
Show full document text