Next-Generation Vehicle-Initiated Emergency Calls
draft-ietf-ecrit-car-crash-03

The information below is for an old version of the document
Document Type Active Internet-Draft (ecrit WG)
Last updated 2015-07-06
Replaces draft-gellens-ecrit-car-crash
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Nov 2016 - Submit ‘Internet Pro... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
ECRIT                                                         R. Gellens
Internet-Draft                                Qualcomm Technologies, Inc
Intended status: Informational                                  B. Rosen
Expires: January 3, 2016                                   NeuStar, Inc.
                                                           H. Tschofenig

                                                            July 4, 2015

           Next-Generation Vehicle-Initiated Emergency Calls
                   draft-ietf-ecrit-car-crash-03.txt

Abstract

   This document describes how to use IP-based emergency services
   mechanisms to support the next generation of emergency calls placed
   by vehicles (automatically in the event of a crash or serious
   incident, or manually invoked by a vehicle occupant) and conveying
   vehicle, sensor, and location data related to the crash or incident.
   Such calls are often referred to as "Automatic Crash Notification"
   (ACN), or "Advanced Automatic Crash Notification" (AACN), even in the
   case of manual trigger.  The "Advanced" qualifier refers to the
   ability to carry a richer set of data.

   This document also registers a MIME Content Type and an Emergency
   Call Additional Data Block for the vehicle, sensor, and location data
   (often referred to as "crash data" even though there is not
   necessarily a crash).  An external specification for the data format,
   contents, and structure are referenced in this document.

   Profiling and simplifications of the general emergency call
   mechanism, as described in [RFC6443] and [RFC6881], are possible due
   to the nature of the functionality that is provided in vehicles such
   as the usage of Global Satellite Navigation System (GNSS).

   This document reuses the technical aspects of next-generation pan-
   European eCall (a mandated and standardized system for emergency
   calls by in-vehicle systems within Europe and other regions), as
   described in [I-D.ietf-ecrit-ecall].  However, this document
   specifies a different set of vehicle (crash) data, specifically, the
   Vehicle Emergency Data Set (VEDS) rather than the eCall Minimum Set
   of Data (MSD).

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

Gellens, et al.          Expires January 3, 2016                [Page 1]
Internet-Draft      Vehicle-Initiated Emergency Calls          July 2015

   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 January 3, 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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Overview of Current Deployment Models . . . . . . . . . . . .   7
   4.  Document Scope  . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  Migration to Next-Generation  . . . . . . . . . . . . . . . .   9
   6.  Profile . . . . . . . . . . . . . . . . . . . . . . . . . . .  11
   7.  Call Setup  . . . . . . . . . . . . . . . . . . . . . . . . .  11
   8.  Call Routing  . . . . . . . . . . . . . . . . . . . . . . . .  14
   9.  Test Calls  . . . . . . . . . . . . . . . . . . . . . . . . .  15
   10. Example . . . . . . . . . . . . . . . . . . . . . . . . . . .  15
   11. Security Considerations . . . . . . . . . . . . . . . . . . .  17
   12. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
     12.1.  MIME Content-type Registration for
            'application/EmergencyCall.VEDS+xml' . . . . . . . . . .  18
     12.2.  Registration of the 'VEDS' entry in the Emergency Call
Show full document text