Cooperative Adaptive Cruise Control and Platooning at SDOs and Gap Analysis
draft-petrescu-its-cacc-sdo-04

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-10-19
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                                   A. Petrescu, Ed.
Internet-Draft                                                 CEA, LIST
Intended status: Informational                                  J. Huang
Expires: April 21, 2016                              Huawei Technologies
                                                                T. Ernst
                                                         Mines ParisTech
                                                           R. Buddenberg
                                                                     " "
                                                              C. Perkins
                                                               Futurewei
                                                        October 19, 2015

   Cooperative Adaptive Cruise Control and Platooning at SDOs and Gap
                                Analysis
                   draft-petrescu-its-cacc-sdo-04.txt

Abstract

   This document describes the use-cases of Cooperative Adaptive Cruise
   Control, and Platooning, as defined by several Standards Development
   Organizations such as ETSI, IEEE P1609, SAE, 3GPP, ISO and FirstNet.

   C-ACC and Platooning involve concepts of direct vehicle-to-vehicle,
   and device-to-device communications, which are developed by 3GPP
   following on work done within the METIS EU project.  They are
   illustrated very clearly in emergency settings such as FirstNet.

   IP packets - instead of link-layer frames - are pertinent for C-ACC
   and Platooning use-cases because applications for road safety such as
   WAZE, iRezQ and Coyote (currently involving infrastructure) make use
   of IP messages, and have proved successful in deployments.
   Applications such as Sentinel operate directly between vehicles, but
   currently use messages not carried over IP.

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

Petrescu, et al.         Expires April 21, 2016                 [Page 1]
Internet-Draft      C-ACC at SDOs and IP Gap Analysis       October 2015

   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 21, 2016.

Copyright Notice

   Copyright (c) 2015 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
   (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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  ETSI ITS C-ACC and Platooning use-case and reqs . . . . . . .   7
   4.  The C-ACC Use of Protocols specified by IEEE 1609 Standards .   7
   5.  SAE perspective on C-ACC and Platooning . . . . . . . . . . .   8
   6.  3GPP and EU projects using LTE Device-to-Device concepts  . .   8
     6.1.  3GPP  . . . . . . . . . . . . . . . . . . . . . . . . . .   8
     6.2.  METIS . . . . . . . . . . . . . . . . . . . . . . . . . .  10
   7.  ISO perspective on V2V  . . . . . . . . . . . . . . . . . . .  10
   8.  ISO-IEEE Harmonization  . . . . . . . . . . . . . . . . . . .  11
   9.  V2V communications at ITU . . . . . . . . . . . . . . . . . .  12
   10. ARIB and ITS Info-comm use of CACC and V2V concepts . . . . .  13
   11. FirstNet EMS use of LTE and IP in V2I2V . . . . . . . . . . .  13
   12. Internet apps: WAZE, iRezQ, Coyote, Sentinel  . . . . . . . .  14
   13. Car manufacturer labels with V2V features . . . . . . . . . .  14
   14. Gap Analysis  . . . . . . . . . . . . . . . . . . . . . . . .  15
     14.1.  Neighbor Discovery protocol  . . . . . . . . . . . . . .  15
     14.2.  Mobile IP protocol . . . . . . . . . . . . . . . . . . .  15
     14.3.  AODVv2 protocol  . . . . . . . . . . . . . . . . . . . .  16
   15. Security Considerations . . . . . . . . . . . . . . . . . . .  16
   16. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
   17. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  17
Show full document text