Next-Generation Pan-European eCall
draft-ietf-ecrit-ecall-21

The information below is for an old version of the document
Document Type Active Internet-Draft (ecrit WG)
Last updated 2017-01-06 (latest revision 2016-12-15)
Replaces draft-gellens-ecrit-ecall
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication (wg milestone: Nov 2016 - Submit ‘Next-Generat... )
Document shepherd Allison Mankin
Shepherd write-up Show (last changed 2016-11-13)
IESG IESG state Waiting for AD Go-Ahead
Consensus Boilerplate Yes
Telechat date
Responsible AD Alissa Cooper
Send notices to "Allison Mankin" <allison.mankin@gmail.com>
IANA IANA review state IANA - Not OK
IANA action state None
ECRIT                                                         R. Gellens
Internet-Draft                                Core Technology Consulting
Intended status: Standards Track                           H. Tschofenig
Expires: June 18, 2017                                        Individual
                                                       December 15, 2016

                   Next-Generation Pan-European eCall
                     draft-ietf-ecrit-ecall-21.txt

Abstract

   This document describes how to use IP-based emergency services
   mechanisms to support the next generation of the pan European in-
   vehicle emergency call service defined under the eSafety initiative
   of the European Commission (generally referred to as "eCall"). eCall
   is a standardized and mandated system for a special form of emergency
   calls placed by vehicles, providing real-time communications and an
   integrated set of related data.

   This document also registers MIME media types and an Emergency Call
   Additional Data Block for the eCall vehicle data and metadata/control
   data, and an INFO package to enable carrying this data in SIP INFO
   requests.

   Although this specification is designed to meet the requirements of
   European next-generation eCall, it is specified generically such that
   the technology can be re-used or extended to suit requirements across
   jurisdictions.

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 June 18, 2017.

Gellens & Tschofenig      Expires June 18, 2017                 [Page 1]
Internet-Draft            Next-Generation eCall            December 2016

Copyright Notice

   Copyright (c) 2016 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 . . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Document Scope  . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  eCall Requirements  . . . . . . . . . . . . . . . . . . . . .   7
   5.  Vehicle Data  . . . . . . . . . . . . . . . . . . . . . . . .   7
   6.  Data Transport  . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Call Setup  . . . . . . . . . . . . . . . . . . . . . . . . .  10
   8.  Test Calls  . . . . . . . . . . . . . . . . . . . . . . . . .  11
   9.  The Metadata/Control Object . . . . . . . . . . . . . . . . .  11
     9.1.  The Control Block . . . . . . . . . . . . . . . . . . . .  13
       9.1.1.  The <ack> element . . . . . . . . . . . . . . . . . .  13
         9.1.1.1.  Attributes of the <ack> element . . . . . . . . .  14
         9.1.1.2.  Child Element of the <ack> element  . . . . . . .  14
         9.1.1.3.  Ack Examples  . . . . . . . . . . . . . . . . . .  15
       9.1.2.  The <capabilities> element  . . . . . . . . . . . . .  15
         9.1.2.1.  Child Elements of the <capabilities> element  . .  15
         9.1.2.2.  Capabilities Example  . . . . . . . . . . . . . .  16
       9.1.3.  The <request> element . . . . . . . . . . . . . . . .  16
         9.1.3.1.  Attributes of the <request> element . . . . . . .  16
         9.1.3.2.  Request Example . . . . . . . . . . . . . . . . .  18
   10. Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  18
   11. Security Considerations . . . . . . . . . . . . . . . . . . .  24
   12. Privacy Considerations  . . . . . . . . . . . . . . . . . . .  25
   13. XML Schema  . . . . . . . . . . . . . . . . . . . . . . . . .  26
   14. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  28
Show full document text