Internet Protocol-based In-Vehicle Emergency Calls
draft-gellens-ecrit-car-crash-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Authors Randall Gellens  , Brian Rosen  , Hannes Tschofenig 
Last updated 2013-11-04
Replaced by RFC 8148, RFC 8148
Stream (None)
Intended RFC status (None)
Formats 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)
ECRIT                                                         R. Gellens
Internet-Draft                                QUALCOMM Technologies, Inc
Intended status: Informational                                  B. Rosen
Expires: May 06, 2014                                      NeuStar, Inc.
                                                           H. Tschofenig
                                                  Nokia Siemens Networks
                                                       November 04, 2013

           Internet Protocol-based In-Vehicle Emergency Calls
                  draft-gellens-ecrit-car-crash-00.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).

   Profiling and simplifications are possible due to the nature of the
   functionality that is provided in vehicles with the usage of Global
   Satellite Navigation System (GNSS).

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-

Gellens, Rosen & TschofeniExpires May 06, 2014                  [Page 1]
Internet-Draft Next-Generation In-Vehicle Emergency Calls  November 2013

   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 May 06, 2014.

Copyright Notice

   Copyright (c) 2013 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  . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Overview of Current Deployment Models  . . . . . . . . . . . .  6
   4.  Document Scope . . . . . . . . . . . . . . . . . . . . . . . .  7
   5.  Migration to Next-Generation . . . . . . . . . . . . . . . . .  8
   6.  Profile  . . . . . . . . . . . . . . . . . . . . . . . . . . .  9
   7.  Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . . 10
   8.  Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . 12
   9.  Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . . 13
   10. Example  . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
   11. Security Considerations  . . . . . . . . . . . . . . . . . . . 16
   12. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 16
     12.1.  Service URN Registration  . . . . . . . . . . . . . . . . 16
     12.2.  MIME Content-type Registration for
            'application/emergencyCall.VEDS+xml'  . . . . . . . . . . 16
     12.3.  Registration of the 'VEDS' entry in the Emergency Call
            Additional Data registry  . . . . . . . . . . . . . . . . 17
   13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 17
   14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18
   15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
     15.1.  Normative References  . . . . . . . . . . . . . . . . . . 18
     15.2.  Informative references  . . . . . . . . . . . . . . . . . 19
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19

Show full document text