ECRIT                                                         R. Gellens
Internet-Draft                                                Consultant                                Core Technology Consulting
Intended status: Standards Track                                B. Rosen
Expires: January 7, February 2, 2017                                  NeuStar, Inc.
                                                           H. Tschofenig
                                                              Individual
                                                            July 6,
                                                          August 1, 2016

           Next-Generation Vehicle-Initiated Emergency Calls
                   draft-ietf-ecrit-car-crash-08.txt
                   draft-ietf-ecrit-car-crash-09.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.

   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).
   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).  This document is an extension
   of the eCall document, with the primary differences being that this
   document makes the MSD data set optional and VEDS mandatory, and
   extends adds
   attribute values to the eCall metadata/control object to permit
   greater functionality.  This document registers a new INFO package
   (identical to that registered for eCall but with the addition of the
   VEDS MIME type).  This document also describes legacy (circuit-
   switched) ACN systems and their migration to next-generation
   emergency calling, to provide background information and context.

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 January 7, February 2, 2017.

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 . . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Document Scope  . . . . . . . . . . . . . . . . . . . . . . .   8
   4.  Overview of Legacy Deployment Models  . . . . . . . . . . . .   9   8
   5.  Migration to Next-Generation  . . . . . . . . . . . . . . . .  10
   6.  Data Transport  . . . . . . . . . . . . . . . . . . . . . . .  13
   7.  Call Setup  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     6.1.  14
   8.  Call Routing  . . . . . . . . . . . . . . . . . . . . . . . .  15
   7.  eCall
   9.  New Metadata/Control Extensions Values . . . . . . . . . . . . . . . . .  16
     7.1.
     9.1.  New values for the 'action' attribute'  . . . . . . . . .  17
     7.2.
     9.2.  Request Example . . . . . . . . . . . . . . . . . . . . .  18
     9.3.  The <ack> element extensions . . . . . . . . . . . . . . . .  17
     7.3. . . . .  18
     9.4.  The <capabilities> element  . . . . . . . . . . . . . . .  19
     7.4.  <request> element extensions
   10. Test Calls  . . . . . . . . . . . . . . . .  21
   8.  Test Calls . . . . . . . . .  20
   11. The emergencyCallData.eCall.VEDS INFO package . . . . . . . .  21
     11.1.  INFO Package Requirements  . . . . . . . . . .  23
   9. . . . . .  22
   12. Example . . . . . . . . . . . . . . . . . . . . . . . . . . .  24
   10.
   13. Security Considerations . . . . . . . . . . . . . . . . . . .  30
   11.  29
   14. Privacy Considerations  . . . . . . . . . . . . . . . . . . .  30
   12.  29
   15. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  30
     12.1.
     15.1.  MIME Content-type Registration for
            'application/EmergencyCall.VEDS+xml' . . . . . . . . . .  31

     12.2.  30
     15.2.  Registration of the 'VEDS' entry in the Emergency Call
            Additional Data registry . . . . . . . . . . . . . . . .  32
     12.3.  Additions to the eCall Control Extension Registry  31
     15.3.  New Action Values  . . .  32
     12.4.  eCall Action Extensions . . . . . . . . . . . . . . . .  34
     12.5.  eCall  32
     15.4.  Static Message Registry  . . . . . . . . . . . . .  34
     12.6.  eCall Reason Registry  . . . . . . . . . . . . . . . . .  35
     12.7.  eCall  32
     15.5.  Lamp ID Registry . . . . . . . . . . . . . . . . .  36
     12.8.  eCall Camera ID Registry . . . . . . . . . . . . . . . .  37
   13. eCall Control Block Schema  . . . . . . .  33
     15.6.  Camera ID Registry . . . . . . . . . .  38
   14. Contributors . . . . . . . . .  34
   16. Acknowledgements  . . . . . . . . . . . . . . .  41
   15. Acknowledgements . . . . . . .  35
   17. Changes from Previous Versions  . . . . . . . . . . . . . . .  41
   16.  35
     17.1.  Changes from Previous Versions  . . . . . . . . . draft-ietf-08 to draft-ietf-09  . . . . . .  41
     16.1.  35
     17.2.  Changes from draft-ietf-07 to draft-ietf-08  . . . . . .  41
     16.2.  36
     17.3.  Changes from draft-ietf-06 to draft-ietf-07  . . . . . .  42
     16.3.  36
     17.4.  Changes from draft-ietf-05 to draft-ietf-06  . . . . . .  42
     16.4.  36
     17.5.  Changes from draft-ietf-04 to draft-ietf-05  . . . . . .  42
     16.5.  36
     17.6.  Changes from draft-ietf-03 to draft-ietf-04  . . . . . .  42
     16.6.  36
     17.7.  Changes from draft-ietf-02 to draft-ietf-03  . . . . . .  42
     16.7.  36
     17.8.  Changes from draft-ietf-01 to draft-ietf-02  . . . . . .  42
     16.8.  36
     17.9.  Changes from draft-ietf-00 to draft-ietf-01  . . . . . .  42
     16.9.  37
     17.10. Changes from draft-gellens-02 to draft-ietf-00 . . . . .  43
     16.10.  37
     17.11. Changes from draft-gellens-01 to -02 . . . . . . . . . .  43
     16.11.  37
     17.12. Changes from draft-gellens-00 to -01 . . . . . . . . . .  43
   17.  37
   18. References  . . . . . . . . . . . . . . . . . . . . . . . . .  43
     17.1.  37
     18.1.  Normative References . . . . . . . . . . . . . . . . . .  43
     17.2.  37
     18.2.  Informative references . . . . . . . . . . . . . . . . .  44  39
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  45  39

1.  Terminology

   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 [RFC2119].

   This document re-uses terminology defined in Section 3 of [RFC5012].

   Additionally, we use the following abbreviations:

   +--------+----------------------------------------------------------+
   | Term   | Expansion                                                |
   +--------+----------------------------------------------------------+
   | 3GPP   | 3rd Generation Partnership Project                       |
   | AACN   | Advanced Automatic Crash Notification                    |
   | ACN    | Automatic Crash Notification                             |
   | APCO   | Association of Public-Safety Communications Officials    |
   | EENA   | European Emergency Number Association                    |
   | ESInet | Emergency Services IP network                            |
   | GNSS   | Global Navigation Satellite System (which includes       |
   |        | various systems such as the Global Positioning System or |
   |        | GPS)                                                     |
   | IVS    | In-Vehicle System                                        |
   | MNO    | Mobile Network Operator                                  |
   | MSD    | eCall Minimum Set of Data                                |
   | NENA   | National Emergency Number Association                    |
   | POTS   | Plain Old Telephone Service (normal, circuit-switched    |
   |        | voice calls)                                             |
   | PSAP   | Public Safety Answering Point                            |
   | TSP    | Telematics Service Provider                              |
   | VEDS   | Vehicle Emergency Data Set                               |
   +--------+----------------------------------------------------------+

2.  Introduction

   Emergency calls made by in-vehicle systems (e.g., automatically in
   the event of a crash or serious incident or manually by a vehicle
   occupant) assist in significantly reducing road deaths and injuries
   by allowing emergency services to respond quickly and appropriately
   to the specifics of the incident, often with better location
   accuracy.

   Drivers often have a poor location awareness, especially outside of
   major cities, at night and when away from home (especially abroad).
   In the most crucial cases, the victim(s) might not be able to call
   because they have been injured or trapped.

   For more than two decades, some vehicles have been equipped with
   telematics systems that, which, among other features, place an emergency
   call automatically in the event of a crash or manually in response to
   an emergency call button.  Such systems generally have on-board
   location determination systems that make use of satellite-based
   positioning technology, inertial sensors, gyroscopes, etc., which can
   provide an accurate position for the vehicle.  Such built-in systems
   can take advantage of the benefits of being integrated into a
   vehicle, such as more power capacity, ability to have larger or
   specialized antenna, ability to be engineered to avoid or minimise
   degradation by vehicle glass coatings, interference from other
   vehicle systems, etc.  Thus, the PSAP can be provided with a good
   estimate of where the vehicle is during an emergency.  Vehicle
   manufacturers are increasingly adopting such systems, both for the
   safety benefits and for the additional features and services they
   enable (e.g., remote engine diagnostics, remote door unlock, stolen
   vehicle tracking and disabling, etc.).

   The general term for such systems is Automatic Crash Notification
   (ACN) or "Advanced Automatic Crash Notification" (AACN).  "ACN" is
   used in this document as a general term.  ACN systems transmit some
   amount of data specific to the incident, referred to generally as
   "crash data" (the term is commonly used even though there might not
   have been a crash).  While different systems transmit different
   amounts of crash data, standardized formats, structures, and
   mechanisms are needed to provide interoperability among systems and
   PSAPs.

   As of the date of this document, currently deployed in-vehicle
   telematics systems are circuit-switched and lack a standards-based
   ability to convey crash data directly to the PSAP (generally relying
   on either a human advisor or an automated text-to-speech system to
   provide the PSAP call taker with some crash data orally, or in some
   cases via a proprietary mechanism).  In most cases, the PSAP call
   taker needs to first realize that the call is related to a vehicle
   incident, and then listen to the data and transcribe it.  Circuit-
   switched ACN systems are referred to here as CS-ACN.

   The transition to next-generation calling in general, and for
   emergency calling in particular, provides an opportunity to vastly
   improve the scope, breadth, reliability and usefulness of crash data
   during an emergency by allowing it to be transmitted during call set-up, set-
   up, and to be automatically processed by the PSAP and made available
   to the call taker in an integrated, automated way, as well as provide
   the ability for a PSAP call taker to request that a vehicle take
   certain actions, such as flashing lights or unlocking doors.  In
   addition, vehicle manufacturers are provided an opportunity to take
   advantage of the same standardized mechanisms for data transmission
   and request processing for internal use if they wish (such as
   telemetry between the vehicle and a service center for both emergency
   and non-emergency uses, including location-based services, multi-media multi-
   media entertainment systems, remote door unlocking, and road-side
   assistance applications).

   Next-generation ACN provides an opportunity for such calls to be
   recognized and processed as such during call set-up, and routed to an
   equipped PSAP where the vehicle data is available to assist the call
   taker in assessing and responding to the situation.  Next-generation
   (IP-based) ACN systems are referred to here as NG-ACN.

   An ACN call can be initiated by a vehicle occupant or automatically
   initiated by vehicle systems in the event of a serious incident.
   (The "A" in "ACN" does stand for "Automatic," but the term is broadly
   used to refer to the class of calls that are placed by an in-vehicle
   system (IVS) or Telematics Service Providers (TSP) and that carry
   incident-related data as well as voice.)  Automatically triggered
   calls indicate a car crash or some other serious incident (e.g., a
   fire).  Manually triggered calls are often reports of observed
   crashes or serious hazards (such as impaired drivers or roadway
   debris).  Depending on the design,  In some implementations, manually triggered calls might be
   more likely to be accidental.

   This document describes how the IETF mechanisms for IP-based
   emergency calls, including [RFC6443] and
   [I-D.ietf-ecrit-additional-data], [RFC7852], are used to
   provide the realization of next-generation ACN.

   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).  This document is an extension of
   [I-D.ietf-ecrit-ecall], with the differences being that this document
   makes the MSD data set optional and VEDS mandatory, and adds
   extension elements, attributes, and new
   attribute values to the eCall metadata/
   control metadata/control object defined in that
   document.  This document also registers a new INFO package (identical
   to that defined in [I-D.ietf-ecrit-ecall] with the addition of the
   VEDS MIME type).

   The Association of Public-Safety Communications Officials (APCO) and
   the National Emergency Number Association (NENA) have jointly
   developed a standardized set of incident-related vehicle data for ACN
   use, called the Vehicle Emergency Data Set (VEDS) [VEDS].  Such data
   is often referred to as crash data although it is applicable in
   incidents other than crashes.

   VEDS provides a standard data set for the transmission, exchange, and
   interpretation of vehicle-related data.  A standard data format
   allows the data to be generated by an IVS or TSP and interpreted by
   PSAPs, emergency responders, and medical facilities.  It includes
   incident-related information such as airbag deployment, location and
   compass orientation of the vehicle, spatial orientation of the
   vehicle (e.g., upright, on its side or top or a bumper), various
   sensor data that can indicate the potential severity of the crash and
   the likelihood of severe injuries to the vehicle occupants, etc.
   This data better informs the PSAP and emergency responders as to the
   type of response that might be needed.  Some of this information has
   been included in U.S. government guidelines for field triage of
   injured patients [triage-2008] [triage-2011].  These guidelines are
   designed to help responders identify the potential existence of
   severe internal injuries and to make critical decisions about how and
   where a patient needs to be transported.

   This document registers the 'application/EmergencyCallData.VEDS+xml'
   MIME content-type, and registers the 'VEDS' entry in the Emergency
   Call Additional Data registry.

   VEDS is an XML structure (see [VEDS]) transported in SIP using the
   'application/EmergencyCallData.VEDS+xml' MIME content-type.  The
   'VEDS' entry in the Emergency Call Additional Data registry is used
   to construct a 'purpose' parameter value to indicate VEDS data in a
   Call-Info header (as described in [I-D.ietf-ecrit-additional-data]). content-type..

   VEDS is a versatile structure that can accomodate varied needs.
   However, if additional sets of data are determined to be needed
   (e.g., in the future or in different regions), the steps to enable
   each data block are very briefly summarized below:

   o  A standardized format and encoding (such as XML) is defined and
      published by a Standards Development Organization (SDO)

   o  A MIME Content-Type is registered for it (typically under the
      'Application' media type) with a sub-type starting with
      'EmergencyCallData.'

   o  An entry for the block is added to the Emergency Call Additional
      Data Blocks sub-registry (established by
      [I-D.ietf-ecrit-additional-data]); [RFC7852]); the registry
      entry is the root of the MIME sub-type (not including the
      'EmergencyCallData' prefix and any suffix such as '+xml')

   o  A next-generation In-Vehicle System (IVS) or TSP transmits crash data
   by encoding it in a standardized and registered format (such as VEDS)
   and attaching it to a SIP message as a MIME body part.  The body part new INFO package is identified by its MIME content-type (such as 'application/
   EmergencyCallData.VEDS+xml') in registered that permits carrying the Content-Type header field of new
      content type and the
   body part.  The body part is assigned a unique identifier which is
   listed metadata/control object (defined in a Content-ID header field
      [I-D.ietf-ecrit-ecall]) in the body part.  The SIP
   message is marked as containing the crash INFO messages.

   Section 6 describes how VEDA data by adding a Call-Info
   header field at the top level of the message.  This Call-Info header
   field contains a CID URL referencing the body part's unique
   identifier, and a 'purpose' parameter identifying the data as the
   crash data per the registry entry.  The 'purpose' parameter's value
   is 'EmergencyCallData.' plus the value associated with the data type
   in the registry; for VEDS data, "purpose=EmergencyCallData.VEDS". metadata/control are
   transported within NG-ACN calls.  Section 7 describes how such calls
   are places.

   These mechanisms are thus used to place emergency calls that are
   identifiable as ACN calls and that carry one or more standardized crash data objects in
   an interoperable way.

   Calls by in-vehicle systems are placed via cellular networks, which
   might ignore location information sent by an originating device in an
   emergency call INVITE, instead attaching their own location
   information (often determined in cooperation with the originating
   device).  Standardized crash data structures often include location
   as determined by the IVS.  A benefit of this is that it allows the
   PSAP to see both the location as determined by the cellular network
   (often in cooperation with the originating device) and the location
   as determined by the IVS.

   This specification inherits the ability to utilize test call
   functionality from Section 15 of [RFC6881].

3.  Document Scope

   This document is focused on how an ACN emergency call is setup and
   incident-related data (including vehicle, sensor, and location data)
   is transmitted to the PSAP using IETF specifications.  For the direct
   model, this is the end-to-end description (between the vehicle and
   the PSAP).  For the TSP model, this describes the call leg between
   the TSP and the PSAP, leaving the call leg between the vehicle and
   the TSP up to the entities involved (i.e., IVS and TSP vendors) who
   are then free to use the same mechanism as for the right-hand side or
   not.

   Note that Europe has a mandated and standardized system for emergency
   calls by in-vehicle systems.  This pan-European system is known as
   "eCall" and is the subject of a separate document,
   [I-D.ietf-ecrit-ecall], which this document builds on.  Vehicles
   designed to operate in multiple regions might need to support eCall
   as well as the ACN NG-ACN as described here.  In this case, a  A vehicle IVS might determine
   whether to use eCall or ACN by first determining a the region or
   country in which it is located (e.g., from a GNSS location fix and/or
   identity of or information from an MNO).  If other regions adopt
   other data formats, a multi-region vehicle might need to support
   those as well.  This document adopts the call set-up and other
   technical aspects of [I-D.ietf-ecrit-ecall], which uses
   [I-D.ietf-ecrit-additional-data]; [RFC7852];
   this makes it straightforward to use a different data set while
   keeping other technical aspects unchanged.  Hence, both NG-eCall and
   the NG-ACN mechanism described here are compatible, differing
   primarily in the specific data block that is sent (the eCall MSD in
   the case of NG-eCall, and the APCO/
   NENA APCO/NENA VEDS used in this document),
   and some additions to the metadata/
   control metadata/control data block.  If other
   regions adopt their own vehicle data sets, this can be similarly
   accomodated without changing other technical aspects.  Note that any
   additional data blocks require a new INFO package to permit transport
   within INFO messages.

4.  Overview of Legacy Deployment Models

   Legacy (circuit-switched) systems for placing emergency calls by in-
   vehicle systems generally have some ability to convey at least
   location and in some cases telematics data to the PSAP.  Most such
   systems use one of three architectural models, which are described
   here as: "Telematics Service Provider" (TSP), "direct", and "paired".
   These three models are illustrated below.

   In the TSP model, both emergency and non-emergency calls are placed
   to a Telematics Service Provider (TSP); a proprietary technique is
   used for data transfer (such as a proprietary in-band modem) between
   the TSP and the vehicle.

   In an emergency, generally the TSP call taker bridges in the PSAP and
   communicates location, crash data (such as impact severity and trauma
   prediction), and other data (such as the vehicle description) to the
   PSAP call taker verbally (in some cases, a proprietary out-of-band
   interface is used).  Since the TSP knows the location of the vehicle
   (from on-board GNSS and sensors), location-based routing is usually
   used to route to the appropriate PSAP.  In some cases, the TSP is
   able to transmit location automatically, using similar techniques as
   for wireless calls.  Typically, a three-way voice call is established
   between the vehicle, the TSP, and the PSAP, allowing communication
   between the PSAP call taker, the TSP call taker, and the vehicle
   occupants (who might be unconscious).

      ///----\\\  proprietary  +------+ 911 trunk or POTS  +------+
     ||| IVS |||-------------->+ TSP  +------------------->+ PSAP |
      \\\----///  crash data   +------+ location via trunk +------+

                        Figure 1: Legacy TSP Model.

   In the paired model, the IVS uses a Bluetooth link with a previously-
   paired handset to establish an emergency call with the PSAP (by
   dialing a standard emergency number; 9-1-1 in North America), and
   then communicates location data to the PSAP via text-to-speech; crash
   data might or might not be conveyed also using text-to-speech.  Some
   such systems use an automated voice prompt menu for the PSAP call
   taker (e.g., "this is an automatic emergency call from a vehicle;
   press 1 to open a voice path to the vehicle; press 2 to hear the
   location read out") to allow the call taker to request location data
   via text-to-speech.

                   +---+
      ///----\\\   | H |   911/etc voice call via handset   +------+
     ||| IVS |||-->| S +----------------------------------->+ PSAP |
      \\\----///   +---+   location via text-to-speech      +------+

                       Figure 2: Legacy Paired Model

   In the direct model, the IVS directly places an emergency call with
   the PSAP by dialing a standard emergency number (9-1-1 in North
   America).  Such systems might communicate location data to the PSAP
   via text-to-speech; crash data might or might not be conveyed using
   text-to-speech.  Some such systems use an automated voice prompt menu
   (e.g., "this is an automatic emergency call from a vehicle; press 1
   to open a voice path to the vehicle; press 2 to hear the location
   read out") to allow the call taker to request location data via text-
   to-speech.

      ///----\\\      911/etc voice call via IVS          +------+
     ||| IVS  |||---------------------------------------->+ PSAP |
      \\\----///     location via text-to-speech          +------+

                       Figure 3: Legacy Direct Model

5.  Migration to Next-Generation

   Migration of emergency calls placed by in-vehicle systems to next-
   generation (all-IP) technology per this document provides a
   standardized mechanism to identify such calls and to present crash
   data with the call, as well as enabling additional communications
   modalities and enhanced functionality.  This allows ACN calls and
   crash data to be automatically processed by the PSAP and made
   available to the call taker in an integrated, automated way.  Because
   the crash data is carried in the initial SIP INVITE (per
   [I-D.ietf-ecrit-additional-data]) [RFC7852])
   the PSAP can present it to the call taker simultaneously with the
   appearance of the call.  The PSAP can also process the data to take
   other actions (e.g., if multiple calls from the same location arrive
   when the PSAP is busy and a subset of them are NG-ACN calls, a PSAP
   might choose to store the information and reject the calls, since the
   IVS will receive confirmation that the information has been
   successfully received; a PSAP could also choose to include a message
   stating that it is aware of the incident and responders are on the
   way; a PSAP could call the vehicle back when a call taker is
   available).

   Origination devices and networks, PSAPs, emergency services networks,
   and other telephony environments are migrating to next-generation.
   This provides opportunities for significant enhancement to
   interoperability and functionality, especially for emergency calls
   carrying additional data such as vehicle crash data.  (In the U.S., a
   network specifically for emergency responders is being developed.
   This network, FirstNet, will be next-generation from the start,
   enhancing the ability for data exchange between PSAPs and
   responders.)
   Migration to next-generation (NG) provides an opportunity to
   significantly improve the handling and response to vehicle-initiated
   emergency calls.  Such calls can be recognized as originating from a
   vehicle, routed to a PSAP equipped both technically and operationally
   to handle such calls, and the vehicle-determined location and crash
   data can be made available to the call taker simultaneously with the
   call appearance.  The PSAP can take advantage of enhanced
   functionality, including the ability to request the vehicle to take
   an action, such as sending an updated set of data, converying a
   message to the occupants, flashing lights, unlocking doors, etc.

   Vehicle manufacturers using the TSP model can choose to take
   advantage of the same mechanism to carry telematics data and requests
   and responses between the vehicle and the TSP for both emergency and
   non-emergency calls as are used for the interface with the PSAP.

   A next-generation IVS establishes an emergency call using the
   emergency call solution as described in [RFC6443] and [RFC6881], with
   the difference that the Request-URI indicates an ACN type of
   emergency call, the IVS typically does not perform routing or
   location queries but relies on the carrier for this, and uses Call-
   Info header fields to indicates that vehicle crash and capabilities
   data is attached.  When an ESInet is deployed, the MNO only needs to
   recognize the call as an emergency call and route it to an ESInet.
   The ESInet can recognize the call as an ACN with vehicle data and can
   route the call to an NG-ACN capable PSAP.  Such a PSAP can interpret
   the vehicle data sent with the call and make it available to the call
   taker.

   [I-D.ietf-ecrit-ecall] registers new service URN children within the
   "sos" subservice.  These URNs request NG-ACN resources, and
   differentiate between manually and automatically triggered NG-ACN
   calls (which might be subject to different treatment depending on
   policy).  The two service URNs registered in [I-D.ietf-ecrit-ecall]
   are "urn:service:sos.ecall.automatic" and
   "urn:service:sos.ecall.manual".  The same service URNs are used for
   ACN as for eCall since in any region only one of these is supported,
   making a distinction unnecessary.  (Further, PSAP equipment might
   support multiple data formats, allowing a PSAP to handle a vehicle
   that erroneously sent the wrong data object.)

   Note that in North America, routing queries performed by clients
   outside of an ESInet typically treat all sub-services of "sos"
   identically to "sos" with no sub-service.  However, the Request-URI
   header field retains the full sub-service; route and handling
   decisions within an ESInet or PSAP can take the sub-service into
   account.  For example, in a region with multiple cooperating PSAPs,
   an NG-ACN call might be routed to a PSAP that is NG-ACN capable, or
   one that specializes in vehicle-related incidents.

   Migration of the three architectural models to next-generation (all-
   IP) is described below.

   In the TSP model, the IVS transmits crash and location data to the
   TSP either by re-using the mechanisms and data objects described
   here, or using a proprietary mechanism.  In an emergency, the TSP
   bridges in the PSAP and the TSP transmits crash and other data to the
   PSAP using the mechanisms and data objects described here.  There is
   a three-way call between the vehicle, the TSP, and the PSAP, allowing
   communication between the PSAP call taker, the TSP call taker, and
   the vehicle occupants (who might be unconscious).  The TSP relays
   PSAP requests and vehicle responses.

                  proprietary
      ///----\\\  or standard       +------+     standard       +------+
     ||| IVS ||| ------------------->+ TSP +------------------->+ PSAP |
      \\\----/// crash + other data +------+ crash + other data +------+

                    Figure 4: Next-Generation TSP Model

   The vehicle manufacturer and the TSP can choose to use the same
   mechanisms and data objects on the left call leg in Figure 4 as on
   the right.  (Note that the TSP model can be more difficult when the
   vehicle is in a different country than the TSP (e.g., a US resident
   driving in Canada or Mexico) because of the additional complexity in
   choosing the correct PSAP based on vehicle location performed by a
   TSP in a different country.)

   In the direct model, the IVS communicates crash data to the PSAP
   directly using the mechanisms and data objects described here.

     ///----\\\           NG emergency call              +------+
    ||| IVS |||----------------------------------------->+ PSAP |
     \\\----///          crash + other data              +------+

                  Figure 5: Next-Generation Direct Model

   In the paired model, the IVS uses a Bluetooth link to a previously-
   paired handset to establish an emergency call with the PSAP; it is
   undefined what facilities are or will be available for transmitting
   crash data through the Bluetooth link to the handset for inclusion in
   an NG emergency call.  Hence, manufacturers that use the paired model
   for legacy calls might choose to adopt either the direct or TSP
   models for next-generation calls.

                                   +---+
      ///----\\\    (undefined)    | H |     standard       +------+
     ||| IVS |||------------------>| S +------------------->+ PSAP |
      \\\----///    (undefined)    +---+ crash + other data +------+

                  Figure 6: Next-Generation Paired Model

   If the call is routed to a PSAP that is not capable of processing the
   vehicle data, the PSAP ignores (or does not receive) the vehicle
   data.  This is detectable by the IVS or TSP when the status response
   to the INVITE (e.., 200 OK) lacks an eCall control structure
   acknowledging receipt of the data [I-D.ietf-ecrit-ecall].  The IVS or
   TSP then proceeds as it would for a CS-ACN call (e.g., verbal
   conveyance of data)

6.  Call Setup

   A next-generation In-Vehicle System (IVS) initiates an NG-ACN call
   with  Data Transport

   [RFC7852] establishes a SIP INVITE using one of the SOS sub-services
   "SOS.ecall.automatic" or "SOS.ecall.manual" in the Request-URI,
   standard sets general mechanism for attaching blocks of crash data and capabilities
   data encoded in
   standardized and registered formats, to a SIP emergency call.  This mechanism permits certain
   emergency call MIME types to be attached as additional data
   blocks as specified in Section 4.1 to SIP messages.  This
   document makes use of
   [I-D.ietf-ecrit-additional-data].  As described in that document,
   each mechanism.

   An In-Vehicle System (IVS) transmits a VEDS data block (see [VEDS])
   by attaching it to a SIP message as a MIME body part per [RFC7852].
   The body part is identified by its MIME content-type, and pointed
   to by content-type ('application/
   emergencyCallData.eCall.VEDS+xml') in the Content-Type header field
   of the body part.  The body part is assigned a CID URL unique identifier
   which is listed in a Content-ID header field in the body part.  The
   SIP message is marked as containing the VEDS data by adding (or
   appending to) a Call-Info header with field at the top level of the SIP
   message.  This Call-Info header field contains a CID URL referencing
   the body part's unique identifier, and a 'purpose' parameter
   value corresponding to
   identifying the data block.

   Should new as a VEDS data blocks be needed (e.g., in other regions or in block per the
   future), Emergency Call
   Additional Data Blocks registry entry; the steps required during standardization are:

   o 'purpose' parameter's
   value is 'emergencyCallData.VEDS'.

   A set of data PSAP or IVS transmits a metadata/control object (see
   [I-D.ietf-ecrit-ecall]) by attaching it to a SIP message as a MIME
   body part per [RFC7852].  The body part is standardized identified by an SDO or appropriate
      organization

   o  A its MIME Content-Type for
   content-type ('application/emergencyCallData.eCall.control+xml') in
   the crash data set is registered with IANA

      *  If the data is specifically for use in emergency calling, the
         MIME type is normally under the 'application' type with a
         subtype starting with 'EmergencyCallData.'

      *  If the data format is XML, then by convention the name has a
         suffix of '+xml'

   o  The item is registered in the Emergency Call Additional Data
      registry, as defined in Section 9.1.7 of
      [I-D.ietf-ecrit-additional-data]

      *  For emergency-call-specific formats, the registered name is the
         root of the MIME Content-Type (not including the
         'EmergencyCallData' prefix and any suffix such as '+xml') as
         described in Section 4.1 of [I-D.ietf-ecrit-additional-data].

   When placing an emergency call:

   o  The crash data set is created and encoded per its specification

   o  IVS capability data is encoded per the specification in
      [I-D.ietf-ecrit-ecall] as extended in this document

   o  The crash data set and capabilities data are attached to the
      emergency call INVITE as specified in Section 4.1 header field of
      [I-D.ietf-ecrit-additional-data], that is, as MIME body parts
      identified by the MIME Content-Type in the body part's Content-
      Type header field

   o  Each part.  The body part is
   assigned a unique identifier label which is listed in the a Content-ID header
   field of in the body part

   o part.  The SIP message is marked as containing the
   metadata/control block by adding (or appending to) a Call-Info header fields
   field at the top level of the INVITE are added
      that reference SIP message.  This Call-Info header
   field contains a CID URL referencing the crash data body part's unique
   identifier, and capabilities a 'purpose' parameter identifying the data and identify
      each by its MIME root (as registered in as a
   metadata/control block per the Emergency Call Additional Data registry)

      *  The crash and capabilities data are referenced in Call-Info
         header fields by CID URLs that contain Blocks
   registry entry; the unique Content ID
         assigned to the body part

      *  The crash and capabilities data are identified in the Call-Info
         header fields by a 'purpose' parameter whose parameter's value is
         'EmergencyCallData.' concatenated with the specific data
         block's entry
   'emergencyCallData.eCall.control'.

   An In-Vehicle System (IVS) initiating an NG-ACN call includes in the Emergency Call Additional Data registry

      *  A Call-Info header field can be either solely to reference one
         item of data (and hence have only the one URL) or can also
         contain other URLs referencing other data

   o  Any additional
   initial INVITE a VEDS data sets are included by following block and a metadata/control object
   informing the same steps PSAP of its capabilities.  The Vehicle Emergency Data Set (VEDS) is an XML structure defined by
   the Association PSAP creates a metadata/
   control object acknowledging receipt of Public-Safety Communications Officials (APCO) the VEDS data and includes it
   to the National Emergency Number Association (NENA) [VEDS].  The
   'application/EmergencyCallData.VEDS+xml' MIME content-type is used SIP response to
   identify it.  The 'VEDS' entry in the Emergency Call Additional Data
   registry is used INVITE.

   A PSAP can request the vehicle to construct a 'purpose' parameter value for
   conveying send an updated VEDS data in block
   during a Call-Info header. call.  The PSAP creates a metadata/control object requesting
   the VEDS data is attached as and attaches it to a body part with MIME content type
   'application/EmergencyCallData.VEDS+xml' SIP INFO message which is pointed at by a
   Call-Info URL of type CID with a 'purpose' parameter of
   'EmergencyCallData.VEDS'.

   Entities along it sends
   within the path between dialog.  The IVS then attaches an updated VEDS data to a
   SIP INFO message and sends it within the vehicle dialog.  The metadata/
   control object and the PSAP VEDS are able attached to
   identify an INFO message in the call
   same way they are attached to other messages (such as an ACN call the INVITE and handle it appropriately.  The
   PSAP
   the reply to the INVITE as discussed above).  INFO messages are sent
   using an appropriate INFO Package.  See Section 11 for more
   information.

   When data is able being carried in an INFO request message, the body part
   also carries a Content-Disposition header field set to identify "Info-
   Package".

7.  Call Setup

   A next-generation In-Vehicle System (IVS) initiates an NG-ACN call
   with a SIP INVITE using one of the SOS sub-services
   "SOS.ecall.automatic" or "SOS.ecall.manual" in the Request-URI,
   standard sets of crash data and capabilities data encoded in
   standardized and registered formats, attached as well as any other additional data attached
   blocks as specified in Section 4.1 of [RFC7852].  As described in
   that document, each data block is identified by its MIME content-
   type, and pointed to the INVITE by examining the a CID URL in a Call-Info header fields for 'purpose' parameters whose values start with
   'EmergencyCallData.'  The PSAP is able a
   'purpose' parameter value corresponding to access the data it is
   capable of handling and is interested block.

   If new data blocks are needed (e.g., in other regions or in by checking the 'purpose'
   parameter values.

   This document extends [I-D.ietf-ecrit-ecall]
   future), the steps required during standardization are briefly
   summarized below:

   o  A set of data is standardized by reusing an SDO or appropriate
      organization

   o  A MIME Content-Type for the call set-
   up and other normative requirements crash data set is registered with IANA

      *  If the exception that in this
   document, support for the eCall MSD data is OPTIONAL and support specifically for VEDS use in REQUIRED.  This document also extends emergency calling, the metadata/control object
   defined in [I-D.ietf-ecrit-ecall] by adding new elements, attributes,
   and values.

6.1.  Call Routing

   An Emergency Services IP Network (ESInet)
         MIME type is a network operated by or
   on behalf of emergency services authorities.  It handles emergency
   call routing and processing before delivery to a PSAP.  In normally under the
   NG9-1-1 architecture adopted by NENA as well as 'application' type with a
         subtype starting with 'EmergencyCallData.'

      *  If the NG1-1-2
   architecture adopted by EENA, each PSAP is connected to one or more
   ESInets.  Each originating network data format is also connected to one or more
   ESInets.  The ESInets maintain policy-based routing rules which
   control XML, then by convention the routing and processing name has a
         suffix of emergency calls. '+xml'

   o  The
   centralization item is registered in the Emergency Call Additional Data
      registry, as defined in Section 9.1.7 of such rules within ESInets provides for a cleaner
   separation between [RFC7852]

      *  For emergency-call-specific formats, the responsibilities registered name is the
         root of the originating network MIME Content-Type (not including the
         'EmergencyCallData' prefix and that any suffix such as '+xml') as
         described in Section 4.1 of [RFC7852].

   o  A new INFO package is registered that permits carrying the emergency services network, and provides greater
   flexibility the new
      content type, the metadata/control object (defined in
      [I-D.ietf-ecrit-ecall]), and control over processing of emergency calls by for compatibility, the
   emergency services authorities MSD and PSAPs.  This makes it easier to
   react quickly to unusual situations that require changes VEDS
      objects, in how INFO messages.

   When placing an emergency calls call, the crash data set and IVS capability
   data are routed or handled (e.g., a natural disaster
   closes a PSAP), as well transported as ease described in making long-term changes that
   affect such routing (e.g., cooperative agreements to specially handle
   calls requiring translation or relay services).

   In Section 6.

   The Vehicle Emergency Data Set (VEDS) is an environment that uses ESInets, the originating network need
   only detect that XML structure defined by
   the service URN Association of an emergency call Public-Safety Communications Officials (APCO) and
   the National Emergency Number Association (NENA) [VEDS].  It is or starts
   carried in body part with "sos", passing all types of emergency calls to an ESInet.  The
   ESInet is then responsible for routing such calls to an appropriate
   PSAP.  In an environment without an ESInet, MIME content-type 'application/
   EmergencyCallData.VEDS+xml'.

   Entities along the emergency services
   authorities path between the vehicle and the originating carriers determine how such calls PSAP are
   routed.

7.  eCall Metadata/Control Extensions

   This document extends able to
   identify the eCall metadata/control structure defined in
   [I-D.ietf-ecrit-ecall] by adding new elements, attributes, call as an ACN call and
   values. handle it appropriately.  The <ack> element
   PSAP is permitted in a control block sent by the IVS
      to the PSAP, able to acknowledge receipt of a request by identify the PSAP crash and
      indicate if capabilities data attached to
   the request was carried out, when that request would
      not otherwise be acknowledged (if INVITE by examining the Call-Info header fields for 'purpose'
   parameters whose values start with 'EmergencyCallData.'  The PSAP requests the vehicle is
   able to
      send data and the vehicle does so, access the data serves as a success
      acknowledgement).

      A new <capabilities> element it is added; used capable of handling and is interested
   in a control block
      sent from by checking the IVS to 'purpose' parameter values.

   This document extends [I-D.ietf-ecrit-ecall] by reusing the PSAP (e.g., call set-
   up and other normative requirements with the exception that in this
   document, support for the initial INVITE) eCall MSD is OPTIONAL and support for VEDS
   in REQUIRED.  This document also adds new attribute values to
      inform the PSAP of the vehicle capabilities.  Child elements
      contain all actions and data types supported
   metadata/control object defined in [I-D.ietf-ecrit-ecall].

8.  Call Routing

   An Emergency Services IP Network (ESInet) is a network operated by the vehicle and
      all available lamps (lights) or
   on behalf of emergency services authorities.  It handles emergency
   call routing and cameras.

      New request values are added processing before delivery to a PSAP.  In the <request> element to enable
   NG9-1-1 architecture adopted by NENA as well as the NG1-1-2
   architecture adopted by EENA, each PSAP is connected to request the vehicle to perform actions.

   Mandatory Actions (the IVS and the PSAP MUST support):

   o  Transmit data object (VEDS MUST be supported; MSD MAY be
      supported)

   Optional Actions (the IVS and the PSAP MAY support):

   o  Play and/or display static (pre-defined) message
   o  Speak/display dynamic text (text supplied in action)
   o  Flash one or turn on more
   ESInets.  Each originating network is also connected to one or off a lamp (light)
   o  Honk horn
   o  Enable a camera more
   ESInets.  The <ack> element indicates ESInets maintain policy-based routing rules which
   control the object being acknowledged (i.e., a
   data object or a <request> element), routing and reports success or failure. processing of emergency calls.  The <capabilities> element has child <request> elements to indicate
   centralization of such rules within ESInets provides for a cleaner
   separation between the actions supported by responsibilities of the IVS.

   The <request> element contains attributes to indicate originating network
   and that of the request emergency services network, and
   to supply any needed information, provides greater
   flexibility and MAY contain a <text> child
   element to contain the text for a dynamic message.  The 'action'
   attribute is mandatory and indicates control over processing of emergency calls by the specific action.
   [I-D.ietf-ecrit-ecall] established an IANA registry
   emergency services authorities and PSAPs.  This makes it easier to contain the
   allowed values; this document adds new values
   react quickly to unusual situations that registry require changes in
   Table 3.

7.1.  New values for the 'action' attribute'

   The following new "action" values how
   emergency calls are defined:

   'msg-static' displays routed or plays handled (e.g., a predefined message (translated natural disaster
   closes a PSAP), as
   appropriate for well as ease in making long-term changes that
   affect such routing (e.g., cooperative agreements to specially handle
   calls requiring translation or relay services).

   In an environment that uses ESInets, the language of originating network need
   only detect that the vehicle's interface).  A registry service URN of an emergency call is created in Section 12.5 for messages and their IDs.  Vehicles
   include the highest registered message in their <capabilities>
   element or starts
   with "sos", passing all types of emergency calls to indicate support an ESInet.  The
   ESInet is then responsible for all messages up routing such calls to and including the
   indicated value.

   'msg-dynamic' displays or speaks (via text-to-speech) a dynamic
   message included in an appropriate
   PSAP.  In an environment without an ESInet, the request.

   'honk' sounds emergency services
   authorities and the horn.

   'lamp' turns a lamp (light) on, off, or flashes.

   'enable-camera' originating carriers determine how such calls are
   routed.

9.  New Metadata/Control Values

   This document adds a one-way media stream (established via SIP re-
   INVITE sent by new attribute values to the vehicle) metadata/control
   structure defined in [I-D.ietf-ecrit-ecall].

      In addition to enable the base usage from the PSAP call taker to view a
   feed from a camera.

   Note that there is no 'request' action to play dynamic media (such as
   an audio message).  The PSAP can send a SIP re-INVITE the IVS to establish a
   one-way media stream for this purpose.

7.2.  <ack> element extensions

   The
      acknowledge receipt of crash data, the <ack> element is extended to be transmitted also
      contained in a metadata/control block sent by the IVS to the
   PSAP PSAP.
      This is used by the IVS to acknowledge receipt of a <request> element that requested request by the
      PSAP and indicate if the
   IVS to perform an action other than transmitting a data object (e.g.,
   a request to display a message was carried out when that request
      would not otherwise be acknowledged, but a request acknowledged (if the PSAP requests the
      vehicle to transmit a send data object would not result in a separate <ack>
   element being sent, since and the vehicle does so, the data object itself serves as
   acknowledgment.)  An <ack> a
      success acknowledgement).

      The <capabilities> element is used in a metadata/control block
      sent by an from the IVS references to the
   unique ID of PSAP (e.g., in the request being acknowledged, indicates whether initial INVITE) to
      inform the
   request was successfully performed, and if not, optionally includes
   an explanation.

   The <ack> element has PSAP of the following new child elements:

7.2.1.  New vehicle capabilities.  Child Element of elements
      contain all actions and data types supported by the <ack> element

   The <ack> element has vehicle and
      all available lamps (lights) and cameras.

      New request values are added to the following new child element:

   Name:  actionResult
   Usage:  Optional
   Description:  An <actionResult> <request> element indicates to enable
      the result of an
      action (other than a 'send-data' action).  When an <ack> element
      is in response PSAP to a control object with multiple <request>
      elements (that are not 'send-data' actions), request the <ack> element
      contains an <actionResult> element for each.
                 The <actionResult> element has the following
      attributes:

      Name:  action
      Usage: vehicle to perform actions.

   Mandatory
      Type:  token
      Description:  Contains the value of the 'action' attribute of Actions (the IVS and the
         <request> element

      Name:  success
      Usage:  Mandatory
      Type:  Boolean
      Description:  Indicates if PSAP MUST support):

   o  Transmit data object (VEDS MUST be supported; MSD MAY be
      supported)

   Optional Actions (the IVS and the action was successfully
         accomplished

      Name:  reason
      Usage:  Conditional
      Type:  token
      Description:  Used when 'success' is "False", this attribute
         contains PSAP MAY support):

   o  Play and/or display static (pre-defined) message
   o  Speak/display dynamic text (text supplied in action)
   o  Flash or turn on or off a reason code for lamp (light)
   o  Honk horn
   o  Enable a failure.  A registry for reason
         codes is defined in Section 12.6.

      Name:  details
      Usage:  optional
      Type:  string
      Description:  Contains further explanation of camera

   The <ack> element indicates the circumstances of object being acknowledged (i.e., a
   data object or a metadata/control block containing <request>
   elements), and reports success or failure.

   The contents are implementation-specific
         and human-readable.

   Example:  <actionResult action="msg-dynamic" success="true"/>

   Example:  <actionResult action="lamp" success="false" reason="unable"
      details="The requested lamp is inoperable"/>

7.2.2.  Ack Examples

      <?xml version="1.0" encoding="UTF-8"?>
      <EmergencyCallData.eCallControl
          xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:
              eCall:control">

      <ack ref="1234567890@atlanta.example.com">
          <actionResult action="msg-dynamic" success="true"/>
          <actionResult action="lamp" success="false" reason="unable"
                        details="The requested lamp is inoperable"/>
      </ack>

      </EmergencyCallData.eCallControl>

                  Figure 7: Ack Example from IVS to PSAP

7.3.  The <capabilities> element

   The <capabilities> element is transmitted by the IVS to indicate to
   the PSAP its capabilities.  No attributes for this element are
   currently defined.  The following has child <request> elements are defined:

7.3.1.  Child Elements of indicating
   the <capabilities> element

   The <capabilities> element has actions supported by the following child elements:

   Name:  request
   Usage:  Mandatory
   Description: IVS.

   The <capabilities> <request> element contains attributes to indicate the request and
   to supply any needed information, and MAY contain a <request> <text> child
   element per action supported by to contain the vehicle.

      Because support text for a 'send-data' action is REQUIRED, a <request>
      child element with a "send-data" 'action' attribute is also
      REQUIRED. dynamic message.  The 'supported-datatypes' 'action'
   attribute is REQUIRED in this
      <request> element within a <capabilities> element, mandatory and MUST indicates the specific action.
   [I-D.ietf-ecrit-ecall] established an IANA registry to contain at a minimum the 'VEDS' data
   allowed values; this document adds new values to that registry in
   Table 2.

   Per [I-D.ietf-ecrit-ecall], the PSAP sends a control/metadata block value; it SHOULD
      contain all
   in response to the VEDS data blocks supported sent by the IVS.

      All IVS in SIP requests other actions are OPTIONAL.

      If
   than INFO (e.g., the "msg-static" action INVITE).  This metadata/control block is supported, a <request> child element
      with sent in
   the SIP response to the request (e.g., the INVITE response).  When
   the PSAP needs to send a "msg-static" 'action' attribute control block that is sent, with a 'msgid'
      attribute set not an immediate
   response to the highest supported static message supported a VEDS or other data sent by the vehicle.  A registry IVS, the control block
   is created in Section 12.5 to map 'msgid'
      values transmitted from the PSAP to static text messages.  By sending the highest supported
      static message number IVS in its <capabilities> element, a SIP INFO request within
   the vehicle
      indicates its support for all static messages established dialog.  The IVS sends the requested data (e.g., the
   VEDS) or an acknowledgment (for requests other than to send data) in
   a new INFO request.  This mechanism flexibly allows the registry up PSAP to send
   metadata/control data to the IVS and including that value.

      If the "lamp" action is supported, a <request> child element with
      a "lamp" 'action' is sent, with a 'supported-lamps' attribute set IVS to all supported lamp IDs. respond.  If the "enable-camera" action is supported, control
   data sent in a <request> child
      element with an "enable-camera" 'action' is sent, with a
      'supported-cameras' attribute set to all supported camera IDs.

   Examples:
      <request action="send-data" supported-datatypes="VEDS"/>
      <request action="send-data" supported-datatypes="VEDS; eCall.MSD"
      />
      <request action="msg-dynamic"/>
      <request action="msg.static" msgid="17" />

7.3.2.  Capabilities Example

    <?xml version="1.0" encoding="UTF-8"?>
    <EmergencyCallData.eCallControl
        xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:
            eCall:control">

    <capabilities>
        <request action="send-data" supported-datatypes="VEDS"/>
        <request action="lamp"
                 supported-lamps="head;interior;fog-front;fog-rear;brake;
                 position-front;position-rear;turn-left;turn-right;hazard"/>
        <request action="msg-static" msgid="3"/>
        <request action="msg-dynamic"/>
        <request action="honk"/>
        <request action="enable-camera" supported-cameras="backup; interior"/>
    </capabilities>

    </EmergencyCallData.eCallControl>

                      Figure 8: Capabilities Example

7.4.  <request> element extensions

   This document extends response message requests the <request> element IVS to be permitted one or
   more times on its own or as a child elements of send a <capabilities>
   element.  The following new attributes, values, and child elements
   are defined for VEDS
   or other data block, or to perform an action other than sending data,
   the <request> element:

7.4.1. IVS sends the requested data or an acknowledgment regarding the
   action in an INFO message within the dialog.

9.1.  New Attributes of values for the <request> element 'action' attribute'

   The <request> element has the following new attributes:

   Name:  msgid
   Usage:  Conditional
   Type:  int
   Description:  Mandatory with "action" values are defined:

   msg-static:  displays or plays a "msg-static" action.  Indicates the
      identifier of the static predefined message to be displayed and/or spoken (translated as
      appropriate for the vehicle occupants.  This document establishes an IANA language of the vehicle's interface).  A
      registry is created in Section 15.4 for messages and their IDs, IDs.
      Vehicles include the highest registered message in Section 12.5
   Example:  msgid="3"

   Name:  persistance
   Usage:  Optional
   Type:  duration
   Description:  Specifies how long their
      <capabilities> element to carry on the specified action, indicate support for example, how long all messages up to continue honking or flashing.  If absent,
      the default is for the duration of
      and including the ACN call.
   Example:  persistance="PT1H"

   Name:  supported-datatypes
   Usage:  Conditional
   Type:  string
   Description:  Used with indicated value.

   msg-dynamic  displays or speaks (via text-to-speech) a 'send-data' action dynamic
      message included in a <request> element
      that is a child of a <capability> element, this attribute lists
      all data blocks that the vehicle can transmit, using request.

   honk  sounds the same
      identifier as in the 'purpose' attribute in a Call-Info header
      field to point to the data block.  Permitted values are contained
      in the 'Emergency Call Data Types' IANA registry established in
      [I-D.ietf-ecrit-additional-data].  Multiple values are separated
      with a semicolon.
   Example:  supported-datatypes="VEDS; eCall.MSD"

   Name:  lamp-action
   Usage:  Conditional
   Type:  token
   Description:  Used with horn.

   lamp  turns a 'lamp' action, indicates if the lamp is to
      be illuminated, turned (light) on, off, or flashed.  Permitted values are
      'on', 'off', and 'flash'.

   Example:  lamp-action="flash"

   Name:  lamp-ID
   Usage:  Conditional
   Type:  token
   Description:  Used with flashes.

   enable-camera  adds a 'lamp' action, indicates which lamp one-way media stream (established via SIP re-
      INVITE sent by the
      action affects.  Permitted values are contained in vehicle) to enable the registry of
      lamp-ID tokens created in Section 12.7
   Example:  lamp-ID="hazard"

   Name:  supported-lamps
   Usage:  Conditional
   Type:  string
   Description:  Used with PSAP call taker to view
      a 'lamp' action in feed from a <request> element camera.

   Note that there is a child of a <capability> element, this attribute lists all
      supported lamps, using values in the registry of lamp-ID tokens
      created in Section 12.7.  Multiple values are separated with a
      semicolon.
   Example:  supported-lamps="head; interior; fog-front; fog-rear;
      brake; position-front; position-rear; turn-left; turn-right;
      hazard"

   Name:  camera-ID
   Usage:  Conditional
   Type:  token
   Description:  Used with an 'enable-camera' action, indicates which
      camera no 'request' action to enable.  Permitted values are contained in the registry
      of camera-ID tokens created in Section 12.8.  When a vehicle
      camera is enabled, the IVS sends play dynamic media (such as
   an audio message).  The PSAP can send a SIP re-INVITE to negotiate establish a one-
      way
   one-way media stream for this purpose.

9.2.  Request Example

      <?xml version="1.0" encoding="UTF-8"?>
      <EmergencyCallData.eCallControl
          xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:
              eCall:control">

      <request action="send-data" datatype="VEDS"/>
      <request action="lamp" lamp-id="hazard"
               lamp-action="flash" persistance="PT1H"/>
      <request action="msg-static" msgid="1"/>
      <request action="msg-dynamic">
          <text>Remain calm.  Help is on the camera.
   Example:  camera-ID="backup"

   Name:  supported-cameras
   Usage:  Conditional
   Type:  string
   Description:  Used with an 'enable-camera' action in a <request> way.</text>
      </request>

      </EmergencyCallData.eCallControl>

                         Figure 7: Request Example

9.3.  The <ack> element that is a child of a <capability> element, this attribute
      lists all cameras that

   In [I-D.ietf-ecrit-ecall], the vehicle supports (can add as a video
      feed in <ack> element is transmitted by the current dialog), using
   PSAP to acknowledge the same identifiers as are
      used in MSD.  Here, the 'camera-ID' attribute (contained in <ack> element is also
   transmitted by the camera ID
      registry in Section 12.8).  Multiple values are separated with a
      semicolon.
   Example:  supported-cameras="backup; interior"

7.4.2.  New Child Elements of PSAP to acknowledge the <request> element

   The <request> element has VEDS data and by the following new child elements:

   Name:  text
   Usage:  Conditional
   Type:  string
   Description:  Used within IVS
   to acknowledge receipt of a <request action="msg-dynamic"> <request> element to
      contain that requested the text IVS
   to perform an action other than transmitting a data object (e.g., a
   request to display a message would be displayed and/or spoken (via text-to-
      speech) for acknowledged, but a request to
   transmit VEDS data would not result in a separate <ack> element being
   sent, since the vehicle occupants.
   Example:  <text>Emergency authorities are aware data object itself serves as acknowledgment.)  An
   <ack> element sent by an IVS references the unique ID of your incident the
   metadata/control object containing the request(s) and
      location.  Due to a multi-vehicle incident in your area, no one is
      able to speak with you right now.  Please remain calm.  We will
      assist you soon.</text>

7.4.3.  Request Example indicates
   whether the request was successfully performed, and if not,
   optionally includes an explanation.

9.3.1.  Ack Examples

      <?xml version="1.0" encoding="UTF-8"?>
      <EmergencyCallData.eCallControl
          xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:
              eCall:control">

      <request action="send-data" datatype="VEDS"/>
      <request

      <ack ref="1234567890@atlanta.example.com">
          <actionResult action="msg-dynamic" success="true"/>
          <actionResult action="lamp" lamp-id="hazard"
               lamp-action="flash" persistance="PT1H"/>
      <request action="msg-static" msgid="1"/>
      <request action="msg-dynamic">
          <text>Remain calm.  Help success="false" reason="unable"
                        details="The requested lamp is on the way.</text>
      </request> inoperable"/>
      </ack>

      </EmergencyCallData.eCallControl>

                  Figure 9: Request 8: Ack Example

8.  Test Calls

   An NG-ACN test call is a call that is recognized and treated from IVS to some
   extent as an NG-ACN call but not given emergency call treatment and
   not handled by a call taker. PSAP

9.4.  The specific handling of test NG-ACN
   calls <capabilities> element

   The <capabilities> element ([I-D.ietf-ecrit-ecall]) is not itself standardized; transmitted by
   the test call facility is intended IVS to allow the IVS, user, or TSP indicate its capabilities to verify that an NG-ACN call can be
   successfully established with voice and/or other media communication. the PSAP.

   The IVS might also be able to verify that <capabilities> element contains a <request> child element per
   action supported by the crash vehicle.  The vehicle MUST support sending
   the VEDS data was
   successfully received.

   This document builds on [I-D.ietf-ecrit-ecall], which inherits object and so includes at a minimum a <request> child
   element with the
   ability 'action' attribute set to utilize test call functionality from Section 15 of
   [RFC6881].  A service URN starting with "test." indicates a test
   call.  [I-D.ietf-ecrit-ecall] registered "urn:service:test.sos.ecall"
   for test calls.

   MNOs, emergency authorities, ESInets, "send-data" and PSAPs determine how to
   treat a vehicle call requesting the "test" service URN so that
   'supported-values' attribute containing all data blocks supported by
   the
   desired functionality IV, which MUST include 'VEDS'.  All other actions are OPTIONAL.

   If the "msg-static" action is tested, but this supported, a <request> child element
   with the 'action' attribute set to "msg-static" is outside included, with the scope of
   this document.  (One possibility
   'msgid' attribute set to the highest supported static message
   supported by the vehicle.  A registry is that MNOs route such calls as
   non-emergency calls created in Section 15.4 to an ESInet, which routes them
   map 'msgid' values to a PSAP that
   supports NG-ACN calls; static text messages.  By sending the PSAP accepts test calls, sends a crash
   data acknowledgment, highest
   supported static message number in its <capabilities> element, the
   vehicle indicates its support for all static messages in the registry
   up to and plays an audio clip (for example, saying including that value.

   If the call reached an appropriate PSAP and "lamp" action is supported, a <request> child element with the vehicle data was
   successfully processed)
   'action' attribute set to "lamp" is included, with the 'supported-
   values' attribute set to all supported lamp IDs.  A registry is
   created in addition Section 15.5 to supporting media loopback per
   [RFC6881]).

   Note that since test calls are placed using "test" as contain lamp ID values.

   If the parent
   service URN and "sos" as "enable-camera" action is supported, a child, such calls are not <request> child element
   with the 'action' attribute set to "enable-camera" is included, with
   the 'supported-values' attribute set to all supported camera IDs.  A
   registry is created in Section 15.6 to contain camera ID values.

9.4.1.  Capabilities Example

    <?xml version="1.0" encoding="UTF-8"?>
    <EmergencyCallData.eCallControl
        xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:
            eCall:control">

    <capabilities>
        <request action="send-data" supported-values="VEDS"/>
        <request action="lamp"
                 supported-values="head;interior;fog-front;fog-rear;brake;
                 position-front;position-rear;turn-left;turn-right;hazard"/>
        <request action="msg-static" msgid="3"/>
        <request action="msg-dynamic"/>
        <request action="honk"/>
        <request action="enable-camera" supported-values="backup; interior"/>
    </capabilities>

    </EmergencyCallData.eCallControl>

                      Figure 9: Capabilities Example

10.  Test Calls

   An NG-ACN test call is a call that is recognized and treated to some
   extent as an NG-ACN call but not given emergency call treatment and so some functionality might
   not apply (such as
   preemption or service availability for devices lacking service ("non-
   service-initialized" or "NSI" devices) if those are available for
   emergency calls).

9.  Example

   Figure 10 shows an NG-ACN handled by a call routing. taker.  The mobile network operator
   (MNO) routes specific handling of test NG-ACN
   calls is not itself standardized; the test call facility is intended
   to an Emergency services IP Network (ESInet),
   as for any emergency call.  The ESInet routes allow the call IVS, user, or TSP to an
   appropriate NG-ACN-capable PSAP (using location information and the
   fact that verify that it is an NG-ACN call).  The call is processed by the
   Emergency Services Routing Proxy (ESRP), as the entry point to the
   ESInet. can be
   successfully established with voice and/or other media communication.

   The ESRP routes the call IVS might also be able to an appropriate NG-ACN-capable
   PSAP, where the call is received by a call taker.  (In deployments
   where there is no ESInet, verify that the MNO itself routes crash data was
   successfully received.

   This document builds on [I-D.ietf-ecrit-ecall], which inherits the call directly
   ability to
   an appropriate NG-ACN-capable PSAP.)
                               +---------------------------------------+
                               |                                       |
               +------------+  |                  +-------+            |
               |            |  |                  | PSAP2 |            |
               |            |  |                  +-------+            |
               | Originating|  |                                       |
               |   Mobile   |  |  +------+     +-------+               |
     Vehicle-->|  Network   |--+->| ESRP |---->| PSAP1 |--> Call-Taker |
               |            |  |  +------+     +-------+               |
               |            |  |                                       |
               +------------+  |                  +-------+            |
                               |                  | PSAP3 |            |
                               |                  +-------+            |
                               |                                       |
                               |                                       |
                               |                                       |
                               |                ESInet                 |
                               +---------------------------------------+

     Figure 10: Example utilize test call functionality from Section 15 of Vehicle-Placed Emergency Call Message Flow

   The example, shown in Figure 11, illustrates
   [RFC6881].  A service URN starting with "test." indicates a SIP test
   call.  [I-D.ietf-ecrit-ecall] registered "urn:service:test.sos.ecall"
   for test calls.

   MNOs, emergency call
   INVITE with location information (a PIDF-LO), VEDS crash data (a VEDS
   data block), authorities, ESInets, and capabilities data (an eCall metadata/control block
   with extensions defined in this document) attached PSAPs determine how to the SIP INVITE
   message.  The INVITE has
   treat a request URI containing vehicle call requesting the
   'urn:service:sos.ecall.automatic' "test" service URN.

   The example VEDS data structure shows information about about a
   crashed vehicle.  The example communicates URN so that the car
   desired functionality is a model
   year 2015 Saab 9-5 (a car which does not exist).  The front airbag
   deployed tested, but this is outside the scope of
   this document.  (One possibility is that MNOs route such calls as
   non-emergency calls to an ESInet, which routes them to a consequence of the crash.  The
   'VehicleBodyCategoryCode' indicates PSAP that
   supports NG-ACN calls; the crashed vehicle is PSAP accepts test calls, sends a
   passenger car (the code is set to '101') crash
   data acknowledgment, and that it is not a
   convertible (the 'ConvertibleIndicator' value is set to 'false').

   The 'VehicleCrashPulse' element provides further information about
   the crash, namely plays an audio clip (for example, saying
   that the force of impact based on call reached an appropriate PSAP and the change vehicle data was
   successfully processed) in
   velocity over the duration of addition to supporting media loopback per
   [RFC6881]).

   Note that since test calls are placed using "test" as the crash pulse was 100 MPH. parent
   service URN and "sos" as a child, such calls are not treated as an
   emergency call and so some functionality might not apply (such as
   preemption or service availability for devices lacking service ("non-
   service-initialized" or "NSI" devices) if those are available for
   emergency calls).

11.  The
   principal direction of emergencyCallData.eCall.VEDS INFO package

   This document registers the force of 'emergencyCallData.eCall.VEDS' INFO
   package.

   Both endpoints (the IVS and the impact is set to '12' (which
   refers PSAP equipment) include
   'emergencyCallData.eCall.VEDS' in a Recv-Info header field per
   [RFC6086] to 12 O'Clock, corresponding indicate ability to a frontal collision).  This
   value is receive INFO messages carrying data
   as described in here.

   Support for the 'CrashPulsePrincipalDirectionOfForceValue'
   element.

   The 'CrashPulseRolloverQuarterTurnsValue' 'emergencyCallData.eCall.VEDS' INFO package indicates
   the number of
   quarter turns in concert with a rollover expressed as a number; ability to receive the VEDS body part as specified in
   our case 1.

   No roll bar was deployed, [TBD: THIS
   DOCUMENT] and the metadata/control body part as indicated specified in
   'VehicleRollbarDeployedIndicator' being
   [I-D.ietf-ecrit-ecall].

   An INFO request message carrying data related to an emergency call as
   described in [TBD: THIS DOCUMENT] has an Info-Package header field
   set to 'false'.

   Next, there is information indicating seatbelt and seat sensor data
   for individual seat positions 'emergencyCallData.eCall.VEDS' per [RFC6086].

11.1.  INFO Package Requirements

   The requirements of Section 10 of [RFC6086] are addressed in the vehicle.  In our example,
   following sections.

11.1.1.  Overall Description

   This section describes "what type of information from the driver seat is available (value '1' carried in INFO
   requests associated with the
   'VehicleSeatLocationCategoryCode' element), that the seatbelt was
   monitored ('VehicleSeatbeltMonitoredIndicator' element), that the
   seatbelt was fastened ('VehicleSeatbeltFastenedIndicator' element) Info Package, and the seat sensor determined that the seat was occupied
   ('VehicleSeatOccupiedIndicator' element).

   Finally, information about the weight for what types of
   applications and functionalities UAs can use the vehicle, which is 600
   kilogram Info Package."

   INFO requests associated with the emergencyCallData.eCall.VEDS INFO
   package carry data associated with emergency calls as defined in our example.

   In addition
   [TBD: THIS DOCUMENT].  The application is vehicle-initiated emergency
   calls established using SIP.  The functionality is to the carry vehicle
   data and metadata/control information about between vehicles and PSAPs.
   Refer to [TBD: THIS DOCUMENT] for more information.

11.1.2.  Applicability

   This section describes "why the vehicle, further indications
   are provided, namely Info Package mechanism, rather than
   some other mechanism, has been chosen for the presence specific use-case...."

   The use of fuel leakage
   ('FuelLeakingIndicator' element), INFO is based on an indication whether the vehicle
   was subjected to multiple impacts ('MultipleImpactsIndicator'
   element), the orientation analysis of the vehicle at final rest
   ('VehicleFinalRestOrientationCategoryCode' element) requirements against
   the intent and an indication
   that there are no parts effects of INFO versus other approaches (which
   included SIP MESSAGE, SIP OPTIONS, SIP re-INVITE, media plane
   transport, and non-SIP protocols).  In particular, the vehicle on fire (the
   'VehicleFireIndicator' element).

    INVITE urn:service:sos.ecall.automatic SIP/2.0 transport of
   emergency call data blocks occurs within a SIP emergency dialog, per
   Section 6, and is normally carried in the initial INVITE and its
   response; the use of INFO only occurs when emergency-call-related
   data needs to be sent mid-call.  While MESSAGE could be used, it is
   not tied to a SIP dialog as is INFO and thus might not be associated
   with the dialog.  SIP OPTIONS or re-INVITE could also be used, but is
   seen as less clean than INFO.  SUBSCRIBE/NOTIFY could be coerced into
   service, but the semantics are not a good fit, e.g., the subscribe/
   notify mechanism provides one-way communication consisting of (often
   multiple) notifications from notifier to subscriber indicating that
   certain events in notifier have occurred, whereas what's needed here
   is two-way communication of data related to the emergency dialog.
   Use of the media plane mechanisms was discounted because the number
   of messages needing to be exchanged in a dialog is normally zero or
   very few, and the size of the data is likewise very small.  The
   overhead caused by user plane setup (e.g., to use MSRP as transport)
   would be disproportionately large.

   Based on the the analyses, the SIP INFO method was chosen to provide
   for mid-call data transport.

11.1.3.  Info Package Name

   The info package name is emergencyCallData.eCall.VEDS

11.1.4.  Info Package Parameters

   None

11.1.5.  SIP Option-Tags

   None

11.1.6.  INFO Message Body Parts

   The 'application/emergencyCallData.eCall.VEDS+xml' and 'application/
   emergencyCallData.eCall.control+xml' MIME types are associated with
   this INFO package.  See [TBD: THIS DOCUMENT] and
   [I-D.ietf-ecrit-ecall] for more information.

11.1.7.  Info Package Usage Restrictions

   Usage is limited to vehicle-initiated emergency calls as defined in
   [TBD: THIS DOCUMENT].

11.1.8.  Rate of INFO Requests

   The rate of SIP INFO requests associated with the
   emergencyCallData.eCall.VEDS info package is normally quite low (most
   dialogs are likely to contain zero INFO requests, while others can be
   expected to carry an occasional request).

11.1.9.  Info Package Security Considerations

   The MIME content type registations for the data blocks that can be
   carried using this IFO package contains a discussion of the security
   and/or privacy considerations specific to that data block.  The
   "Security Considerations" and "Privacy Considerations" sections of
   [TBD: THIS DOCUMENT] discuss security and privacy considerations of
   the data carried in vehicle-initiated emergency calls as described in
   that document.

11.1.10.  Implementation Details

   See [TBD: THIS DOCUMENT] for protocol details.

11.1.11.  Examples

   See [TBD: THIS DOCUMENT] for protocol examples.

12.  Example

   Figure 10 shows an NG-ACN call routing.  The mobile network operator
   (MNO) routes the call to an Emergency services IP Network (ESInet),
   as for any emergency call.  The ESInet routes the call to an
   appropriate NG-ACN-capable PSAP (using location information and the
   fact that that it is an NG-ACN call).  The call is processed by the
   Emergency Services Routing Proxy (ESRP), as the entry point to the
   ESInet.  The ESRP routes the call to an appropriate NG-ACN-capable
   PSAP, where the call is received by a call taker.  (In deployments
   where there is no ESInet, the MNO itself routes the call directly to
   an appropriate NG-ACN-capable PSAP.)

                               +---------------------------------------+
                               |                                       |
               +------------+  |                  +-------+            |
               |            |  |                  | PSAP2 |            |
               |            |  |                  +-------+            |
               | Originating|  |                                       |
               |   Mobile   |  |  +------+     +-------+               |
     Vehicle-->|  Network   |--+->| ESRP |---->| PSAP1 |--> Call-Taker |
               |            |  |  +------+     +-------+               |
               |            |  |                                       |
               +------------+  |                  +-------+            |
                               |                  | PSAP3 |            |
                               |                  +-------+            |
                               |                                       |
                               |                                       |
                               |                                       |
                               |                ESInet                 |
                               +---------------------------------------+

     Figure 10: Example of Vehicle-Placed Emergency Call Message Flow

   The example, shown in Figure 11, illustrates a SIP emergency call
   INVITE with location information (a PIDF-LO), VEDS crash data (a VEDS
   data block), and capabilities data (an eCall metadata/control block
   with extensions defined in this document) attached to the SIP INVITE
   message.  The INVITE has a request URI containing the
   'urn:service:sos.ecall.automatic' service URN.

   The example VEDS data structure shows information about about a
   crashed vehicle.  The example communicates that the car is a model
   year 2015 Saab 9-5 (a car which does not exist).  The front airbag
   deployed as a consequence of the crash.  The
   'VehicleBodyCategoryCode' indicates that the crashed vehicle is a
   passenger car (the code is set to '101') and that it is not a
   convertible (the 'ConvertibleIndicator' value is set to 'false').

   The 'VehicleCrashPulse' element provides further information about
   the crash, namely that the force of impact based on the change in
   velocity over the duration of the crash pulse was 100 MPH.  The
   principal direction of the force of the impact is set to '12' (which
   refers to 12 O'Clock, corresponding to a frontal collision).  This
   value is described in the 'CrashPulsePrincipalDirectionOfForceValue'
   element.

   The 'CrashPulseRolloverQuarterTurnsValue' indicates the number of
   quarter turns in concert with a rollover expressed as a number; in
   our case 1.

   No roll bar was deployed, as indicated in
   'VehicleRollbarDeployedIndicator' being set to 'false'.

   Next, there is information indicating seatbelt and seat sensor data
   for individual seat positions in the vehicle.  In our example,
   information from the driver seat is available (value '1' in the
   'VehicleSeatLocationCategoryCode' element), that the seatbelt was
   monitored ('VehicleSeatbeltMonitoredIndicator' element), that the
   seatbelt was fastened ('VehicleSeatbeltFastenedIndicator' element)
   and the seat sensor determined that the seat was occupied
   ('VehicleSeatOccupiedIndicator' element).

   Finally, information about the weight of the vehicle, which is 600
   kilogram in our example.

   In addition to the information about the vehicle, further indications
   are provided, namely the presence of fuel leakage
   ('FuelLeakingIndicator' element), an indication whether the vehicle
   was subjected to multiple impacts ('MultipleImpactsIndicator'
   element), the orientation of the vehicle at final rest
   ('VehicleFinalRestOrientationCategoryCode' element) and an indication
   that there are no parts of the vehicle on fire (the
   'VehicleFireIndicator' element).

    INVITE urn:service:sos.ecall.automatic SIP/2.0
    To: urn:service:sos.ecall.automatic
    From: <sip:+13145551111@example.com>;tag=9fxced76sl
    Call-ID: 3848276298220188511@atlanta.example.com
    Geolocation: <cid:target123@example.com>
    Geolocation-Routing: no
    Call-Info: cid:1234567890@atlanta.example.com;
               purpose=EmergencyCallData.VEDS
    Call-Info: cid:1234567892@atlanta.example.com;
               purpose=EmergencyCallData.ecall.control
    Accept: application/sdp, application/pidf+xml,
            application/emergencyCallData.eCall.control+xml
    Recv-Info: emergencyCallData.eCall
    Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE,
           SUBSCRIBE, NOTIFY, UPDATE
    CSeq: 31862 INVITE
    Content-Type: multipart/mixed; boundary=boundary1
    Content-Length: ...

    --boundary1
    Content-Type: application/sdp

    ...Session Description Protocol (SDP) goes here

    --boundary1
     Content-Type: application/pidf+xml
     Content-ID: <target123@atlanta.example.com>

     <?xml version="1.0" encoding="UTF-8"?>
     <presence
        xmlns="urn:ietf:params:xml:ns:pidf"
        xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
        xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
        xmlns:dyn="urn:ietf:params:xml:ns:pidf:geopriv10:dynamic"
        xmlns:gml="http://www.opengis.net/gml"
        xmlns:gs="http://www.opengis.net/pidflo/1.0"
        entity="sip:+13145551111@example.com">
        <dm:device id="123">
            <gp:geopriv>
                <gp:location-info>
                    <gml:Point srsName="urn:ogc:def:crs:EPSG::4326">
                       <gml:pos>-34.407 150.883</gml:pos>
                    </gml:Point>
                     <dyn:Dynamic>
                        <dyn:heading>278</dyn:heading>
                        <dyn:direction><dyn:direction>
                     </dyn:Dynamic>
                </gp:location-info>
                <gp:usage-rules/>
                <method>gps</method>
            </gp:geopriv>
            <timestamp>2012-04-5T10:18:29Z</timestamp>
            <dm:deviceID>1M8GDM9A_KP042788</dm:deviceID>
        </dm:device>
 </presence>
     --boundary1
     Content-Type: application/EmergencyCallData.VEDS+xml
     Content-ID: 1234567890@atlanta.example.com
     Content-Disposition: by-reference;handling=optional

     <?xml version="1.0" encoding="UTF-8"?>
     <AutomatedCrashNotification xmlns="http://www.veds.org/acn/1.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

     <Crash>
         <CrashVehicle>
             <ItemMakeName xmlns="http://niem.gov/niem/niem-core/2.0">
                 Saab
             </ItemMakeName>
             <ItemModelName xmlns="http://niem.gov/niem/niem-core/2.0">
                 9-5
             </ItemModelName>
             <ItemModelYearDate
                 xmlns="http://niem.gov/niem/niem-core/2.0">
                 2015
             </ItemModelYearDate>
             <Airbag>
                 <AirbagCategoryCode>FRONT</AirbagCategoryCode>
                 <AirbagDeployedIndicator>true
                 </AirbagDeployedIndicator>
             </Airbag>
             <ConvertibleIndicator>false</ConvertibleIndicator>
             <PowerSourceCategoryCode>MAIN</PowerSourceCategoryCode>
             <VehicleBodyCategoryCode
                 xmlns="http://niem.gov/niem/domains/jxdm/4.1">
                 101
             </VehicleBodyCategoryCode>
             <VehicleCrashPulse>
                 <CrashPulseChangeInVelocityMeasure>
                     <MeasurePointValue
                         xmlns="http://niem.gov/niem/niem-core/2.0">
                         100
                     </MeasurePointValue>
                     <MeasureUnitText
                         xmlns="http://niem.gov/niem/niem-core/2.0">
                         MPH</MeasureUnitText>
                  </CrashPulseChangeInVelocityMeasure>
                         <CrashPulsePrincipalDirectionOfForceValue>12
                         </CrashPulsePrincipalDirectionOfForceValue>
                 <CrashPulseRolloverQuarterTurnsValue>1
                 </CrashPulseRolloverQuarterTurnsValue>
             </VehicleCrashPulse>
             <VehicleRollbarDeployedIndicator>false
             </VehicleRollbarDeployedIndicator>
             <VehicleSeat>
                 <VehicleSeatLocationCategoryCode>1
                 </VehicleSeatLocationCategoryCode>
                 <VehicleSeatOccupiedIndicator>true
                 </VehicleSeatOccupiedIndicator>
                 <VehicleSeatbeltFastenedIndicator>true
                 </VehicleSeatbeltFastenedIndicator>
                 <VehicleSeatbeltMonitoredIndicator>true
                 </VehicleSeatbeltMonitoredIndicator>
             </VehicleSeat>
             <VehicleUnladenWeightMeasure
                 xmlns="http://niem.gov/niem/niem-core/2.0">
                 <MeasurePointValue
                     xmlns="http://niem.gov/niem/niem-core/2.0">
                     600
                     </MeasurePointValue>
                 <MeasureUnitText
                     xmlns="http://niem.gov/niem/niem-core/2.0">
                     kilogram
                 </MeasureUnitText>
             </VehicleUnladenWeightMeasure>
         </CrashVehicle>
         <FuelLeakingIndicator>true</FuelLeakingIndicator>
         <MultipleImpactsIndicator>false</MultipleImpactsIndicator>
         <SevereInjuryIndicator>true</SevereInjuryIndicator>
         <VehicleFinalRestOrientationCategoryCode>Driver
         </VehicleFinalRestOrientationCategoryCode>
         <VehicleFireIndicator>false</VehicleFireIndicator>
     </Crash>
 </AutomatedCrashNotification>

     --boundary1
     Content-Type: application/EmergencyCallData.ecall.control+xml
     Content-ID: 1234567892@atlanta.example.com
     Content-Disposition: by-reference;handling=optional

     <?xml version="1.0" encoding="UTF-8"?>
     <EmergencyCallData.eCallControl
          xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:
              eCall:control">

      <capabilities>
          <request action="send-data" supported-datatypes="VEDS"/>
          <request action="lamp"
                   supported-lamps="head;interior;fog-front;fog-rear;
                   supported-values="head;interior;fog-front;fog-rear;
                   brake;position-front;position-rear;turn-left;
                   turn-right;hazard"/>
          <request action="msg-static" msgid="3"/>
          <request action="msg-dynamic"/>
          <request action="honk"/>
          <request action="enable-camera"
                   supported-cameras="backup;
                   supported-values="backup; interior"/>
      </capabilities>

     </EmergencyCallData.eCallControl>

     --boundary1--

    Figure 11: SIP INVITE indicating a Vehicule-Initated Emergency Call

10.

13.  Security Considerations

   Since this document relies on [I-D.ietf-ecrit-ecall] and
   [I-D.ietf-ecrit-additional-data], [RFC7852],
   the security considerations described there and in [RFC5069] apply
   here.  Implementors are cautioned to read and understand the
   discussion in those documents.

   As with emergency service systems where location data is supplied or
   determined with the assistance of an end host, there is the
   possibility that that location is incorrect, either intentially
   (e.g., in a denial of service attack against the emergency services
   infrastructure) or due to a malfunctioning device.  The reader is
   referred to [RFC7378] for a discussion of some of these
   vulnerabilities.

   In addition to the security considerations discussion specific to the
   metadata/control object in [I-D.ietf-ecrit-ecall], note that vehicles
   MAY decline to carry out any requested action (e.g., if the vehicle
   requires but is unable to verify the certificate used to sign the
   request).  The vehicle MAY use any value in the reason registry to
   indicate why it did not take an action (e.g., the generic "unable" or
   the more specific "security-failure").

11.

14.  Privacy Considerations

   Since this document builds on [I-D.ietf-ecrit-ecall], which itself
   builds on [I-D.ietf-ecrit-additional-data], [RFC7852], the data structures specified there, and the
   corresponding privacy considerations discussed there, apply here as
   well.  The VEDS data structure contains optional elements that can
   carry identifying and personal information, both about the vehicle and about the owner, as well as
   location information, and so needs to be protected against
   unauthorized disclosure, as discussed in
   [I-D.ietf-ecrit-additional-data].  Local regulations may impose
   additional privacy protection requirements.

12.  IANA Considerations

   This document registers the 'application/EmergencyCall.VEDS+xml' MIME
   content type, and adds "VEDS" to the Emergency Call Additional Data
   registry.  This document adds to and creates new sub-registries in
   the 'eCall Control Data' registry created in [I-D.ietf-ecrit-ecall].

12.1.  MIME Content-type Registration for 'application/
       EmergencyCall.VEDS+xml'

   This specification requests the registration of a new MIME type
   according to the procedures of RFC 4288 [RFC4288] and guidelines in
   RFC 3023 [RFC3023].

      MIME media type name: application

      MIME subtype name: EmergencyCallData.VEDS+xml

      Mandatory parameters: none

      Optional parameters: charset

      Indicates the character encoding of enclosed XML.

      Encoding considerations: Uses XML, which can employ 8-bit
      characters, depending on the character encoding used.  See
      Section 3.2 of RFC 3023 [RFC3023].

      Security considerations:

         This content type is designed to carry vehicle crash data
         during an emergency call.

         This data can contain personal information including vehicle
         VIN, location, direction, etc.  Appropriate precautions need to
         be taken to limit unauthorized access, inappropriate disclosure
         to third parties, and eavesdropping of this information.
         Please refer to Section 7 and Section 8 of
         [I-D.ietf-ecrit-additional-data] for more information.

         When this content type is contained in a signed or encrypted
         body part, the enclosing multipart (e.g., multipart/signed or
         multipart/encrypted) has the same Content-ID as about the data part.
         This allows an entity to identify vehicle
   and access about the data blocks it
         is interested in without having owner, as well as location information, and so needs to dive deeply into the message
         structure or decrypt parts it is not interested in.  (The
         'purpose' parameter
   be protected against unauthorized disclosure, as discussed in

   [RFC7852].  Local regulations may impose additional privacy
   protection requirements.

   The additional functionality enabled by this document, such as access
   to vehicle camera streams, carries a Call-Info header field identifies the
         data, burden of protection and the CID URL points so
   implementations need to be careful that access is only provided
   within the data block in context of an emergency call or to an emergency services
   provider (e.g., by verifying that the body,
         which has a matching Content-ID body part header field).

      Interoperability considerations: None

      Published specification: [VEDS]

      Applications which use this media type: Emergency Services
      Additional information: None

      Magic Number: None

      File Extension: .xml

      Macintosh file type code: 'TEXT'

      Persons and email addresses request for further information: Randall
      Gellensm rg+ietf (at) randy.pensive.org; Hannes Tschofenig,
      Hannes.Tschofenig (at) gmx.net

      Intended usage: LIMITED USE

      Author: This specification camera access is
   signed by a work item of the IETF ECRIT
      working group, with mailing list address <ecrit@ietf.org>.

      Change controller: The IESG <ietf@ietf.org>

12.2.  Registration of the 'VEDS' entry in the Emergency Call Additional
       Data registry

   This specification requests certificate issued by an emergency services registrar).

15.  IANA to add Considerations

   This document registers the 'VEDS' entry 'application/EmergencyCall.VEDS+xml' MIME
   content type, and adds "VEDS" to the Emergency Call Additional Data registry, with a reference to this
   document.  The Emergency Call Additional Data registry has been
   established by [I-D.ietf-ecrit-additional-data].

12.3.  Additions
   registry.  This document adds to and creates sub-registries in the eCall Control Extension Registry
   'Metadata/Control Data' registry created in [I-D.ietf-ecrit-ecall].
   This document uses registers a new INFO package.

15.1.  MIME Content-type Registration for 'application/
       EmergencyCall.VEDS+xml'

   This specification requests the "eCall Control Extension Registry" to add registration of a new
   elements, attributes, and values MIME content
   type according to the eCall metadata/control
   object, as per [I-D.ietf-ecrit-ecall]:

   +-----------+---------------------+---------------------------------+
   |    Type   |         Name        |           Description           |
   +-----------+---------------------+---------------------------------+
   | Attribute |        msgid        |     See Section 7.2 of this     |
   |           |                     |             document            |
   |           |                     |                                 |
   | Attribute |     persistance     |     See Section 7.2 of this     |
   |           |                     |             document            |
   |           |                     |                                 |
   | Attribute | supported-datatypes |     See Section 7.2 of this     |
   |           |                     |             document            |
   |           |                     |                                 |
   | Attribute |     lamp-action     |     See Section 7.2 of this     |
   |           |                     |             document            |
   |           |                     |                                 |
   | Attribute |       lamp-ID       |     See Section 7.2 of this     |
   |           |                     |             document            |
   |           |                     |                                 |
   | Attribute |   supported-lamps   |     See Section 7.2 procedures of this     |
   |           |                     |             document            |
   |           |                     |                                 |
   | Attribute |      camera-ID      |     See Section 7.2 RFC 4288 [RFC4288] and guidelines
   in RFC 3023 [RFC3023].

      MIME media type name: application

      MIME subtype name: EmergencyCallData.VEDS+xml

      Mandatory parameters: none

      Optional parameters: charset

      Indicates the character encoding of this     |
   |           |                     |             document            |
   |           |                     |                                 |
   |  Element  |         text        | enclosed XML.

      Encoding considerations: Uses XML, which can employ 8-bit
      characters, depending on the character encoding used.  See
      Section 7.4.2 3.2 of this    |
   |           |                     |             document            |
   |           |                     |                                 |
   |  Element  |     actionResult    |    See Section 7.2.1 RFC 3023 [RFC3023].

      Security considerations:

         This content type is designed to carry vehicle crash data
         during an emergency call.

         This data can contain personal information including vehicle
         VIN, location, direction, etc.  Appropriate precautions need to
         be taken to limit unauthorized access, inappropriate disclosure
         to third parties, and eavesdropping of this    |
   |           |                     |             document            |
   |           |                     |                                 |
   | Attribute |        action       |    See information.

         Please refer to Section 7.2.1 of this    |
   |           |                     |             document            |
   |           |                     |                                 |
   | Attribute |       success       |    See 7 and Section 7.2.1 8 of [RFC7852] for more
         information.

         When this    |
   |           |                     |             document            |
   |           |                     |                                 |
   | Attribute |        reason       |    See Section 7.2.1 of content type is contained in a signed or encrypted
         body part, the enclosing multipart (e.g., multipart/signed or
         multipart/encrypted) has the same Content-ID as the data part.
         This allows an entity to identify and access the data blocks it
         is interested in without having to dive deeply into the message
         structure or decrypt parts it is not interested in.  (The
         'purpose' parameter in a Call-Info header field identifies the
         data, and the CID URL points to the data block in the body,
         which has a matching Content-ID body part header field).

      Interoperability considerations: None

      Published specification: [VEDS]

      Applications which use this    |
   |           |                     |             document            |
   |           |                     |                                 |
   | Attribute |       details       |    See Section 7.2.1 media type: Emergency Services

      Additional information: None

      Magic Number: None

      File Extension: .xml

      Macintosh file type code: 'TEXT'

      Persons and email addresses for further information: Randall
      Gellensm rg+ietf@randy.pensive.org; Hannes Tschofenig,
      Hannes.Tschofenig@gmx.net

      Intended usage: LIMITED USE

      Author: This specification is a work item of the IETF ECRIT
      working group, with mailing list address <ecrit@ietf.org>.

      Change controller: The IESG <ietf@ietf.org>

15.2.  Registration of the 'VEDS' entry in the Emergency Call Additional
       Data registry

   This specification requests IANA to add the 'VEDS' entry to the
   Emergency Call Additional Data registry, with a reference to this    |
   |           |                     |             document            |
   +-----------+---------------------+---------------------------------+

           Table 2: eCall Control Extension Registry
   document.  The Emergency Call Additional Data registry was
   established by [RFC7852].

15.3.  New Values

12.4.  eCall Action Extensions Values

   This document adds new values for the 'action' attribute of the
   <request> element in the "eCall Control Action "Action Registry" registry created by
   [I-D.ietf-ecrit-ecall].

             +---------------+------------------------------+

          +---------------+-------------------------------------+
          |      Name     |             Description             |
             +---------------+------------------------------+
          +---------------+-------------------------------------+
          |   msg-static  | Section 7.1 9.1 of this document [TBD: THIS DOCUMENT] |
          |               |                                     |
          |  msg-dynamic  | Section 7.1 9.1 of this document [TBD: THIS DOCUMENT] |
          |               |                                     |
          |      honk     | Section 7.1 9.1 of this document [TBD: THIS DOCUMENT] |
          |               |                                     |
          |      lamp     | Section 7.1 9.1 of this document [TBD: THIS DOCUMENT] |
          |               |                                     |
          | enable-camera | Section 7.1 9.1 of this document [TBD: THIS DOCUMENT] |
             +---------------+------------------------------+
          +---------------+-------------------------------------+

                    Table 3: eCall Control 2: Action Registry New Values

12.5.  eCall

15.4.  Static Message Registry

   This document creates a new sub-registry called "eCall Static "Static Message
   Registry" in the "eCall Control "Metadata/Control Data" registry established by
   [I-D.ietf-ecrit-ecall].  Because all compliant vehicles are expected
   to support all static messages translated into all languages
   supported by the vehicle, it is important to limit the number of such
   messages.  As defined in [RFC5226], this registry operates under
   "Publication Required" rules, which require a stable, public document
   and imply implies expert review of the publication.  The expert should
   determine that the document has been published by an appropriate
   emergency services organization (e.g., NENA, EENA, APCO) or by the
   IETF with input from an emergency services organization, and that the
   proposed message is sufficiently distinguishable from other messages.

   The content contents of this registry includes: are:

   ID:  An integer identifier to be used in the 'msgid' attribute of an
      eCall control a
      metadata/control <request> element.

   Message:  The text of the message.  Messages are listed in the
      registry in English; vehicles are expected to implement
      translations into languages supported by the vehicle.

   When new messages are added to the registry, the message text is
   determined by the registrant; IANA assigns the IDs.  Each message is
   assigned a consecutive integer value as its ID.  This allows an IVS
   to indicate by a single integer value that it supports all messages
   with that value or lower.

   The initial set of values is listed in Table 4. 3.

   +----+--------------------------------------------------------------+
   | ID | Message                                                      |
   +----+--------------------------------------------------------------+
   | 1  | Emergency authorities are aware of your incident and         |
   |    | location, but are unable to speak with you right now.  We    |
   |    | will help you as soon as possible.                           |
   +----+--------------------------------------------------------------+

                  Table 4: eCall Static Message Registry

12.6.  eCall Reason Registry

   This document creates a new sub-registry called "eCall Reason
   Registry" in the "eCall Control Data" registry established by
   [I-D.ietf-ecrit-ecall].  This new sub-registry contains values for
   the 'reason' attribute of the <actionResult> element.  As defined in
   [RFC5226], this registry operates under "Expert Review" rules.  The
   expert should determine that the proposed reason is sufficiently
   distinguishable from other reasons and that the proposed description
   is understandable and correctly worded.

   The content of this registry includes:

   ID:  A short string identifying the reason, for use in the 'reason'
      attribute of an <actionResult> element.

   Description:  A description of the reason.

   The initial set of values is listed in Table 5.

   +------------------+------------------------------------------------+
   | ID               | Description                                    |
   +------------------+------------------------------------------------+
   | unsupported      | The 'action' is not supported.                 |
   |                  |                                                |
   | unable           | The 'action' could not be accomplished.        |
   |                  |                                                |
   | data-unsupported | The data item referenced in a 'send-data'      |
   |                  | request is not supported.                      |
   |                  |                                                |
   | security-failure | The authenticity of the request or the are aware of your incident and         |
   |    | authority of the requestor could not be location, but are unable to speak with you right now.  We    |
   |    | verified. will help you as soon as possible.                           |
   +------------------+------------------------------------------------+
   +----+--------------------------------------------------------------+

                     Table 5: eCall Reason 3: Static Message Registry

12.7.  eCall

15.5.  Lamp ID Registry

   This document creates a new sub-registry called "eCall Lamp "Lamp ID Registry" in
   the "eCall Control "Metadata/Control Data" registry established by
   [I-D.ietf-ecrit-ecall].  This new sub-registry standardizes uniquely identifies
   the names of automotive lamps (lights).  As defined in [RFC5226],
   this registry operates under "Expert Review" rules.  The expert
   should determine that the proposed lamp name is clearly
   understandable and is sufficiently distinguishable from other lamp
   names.

   The content contents of this registry includes: are:

   Name:  The identifier to be used in the 'lamp-ID' attribute of an
      eCall control a
      metadata/control <request> element.

   Description:  A description of the lamp (light).

   The initial set of values is listed in Table 6. 4.

     +----------------+---------------------------------------------+
     | Name           | Description                                 |
     +----------------+---------------------------------------------+
     | head           | The main lamps used to light the road ahead |
     |                |                                             |
     | interior       | Interior lamp, often at the top center      |
     |                |                                             |
     | fog-front      | Front fog lamps                             |
     |                |                                             |
     | fog-rear       | Rear fog lamps                              |
     |                |                                             |
     | brake          | Brake indicator lamps                       |
     |                |                                             |
     | brake-center   | Center High Mounted Stop Lamp               |
     |                |                                             |
     | position-front | Front position/parking/standing lamps       |
     |                |                                             |
     | position-rear  | Rear position/parking/standing lamps        |
     |                |                                             |
     | turn-left      | Left turn/directional lamps                 |
     |                |                                             |
     | turn-right     | Right turn/directional lamps                |
     |                |                                             |
     | hazard         | Hazard/four-way lamps                       |
     +----------------+---------------------------------------------+

                 Table 6: eCall 4: Lamp ID Registry Initial Values

12.8.  eCall

15.6.  Camera ID Registry

   This document creates a new sub-registry called "eCall Camera "Camera ID Registry"
   in the "eCall Control "Metadata/Control Data" registry established by
   [I-D.ietf-ecrit-ecall].  This new sub-registry standardizes the names
   of uniquely identifies
   automotive camera. cameras.  As defined in [RFC5226], this registry operates
   under "Expert Review" rules.  The expert should determine that the
   proposed camera name is clearly understandable and is sufficiently
   distinguishable from other camera names.

   The content contents of this registry includes: are:

   Name:  The identifier to be used in the 'camera-ID' attribute of an
      eCall control <request> element.

   Description:  A description of the camera.

   The initial set of values is listed in Table 7. 5.

   +-------------+-----------------------------------------------------+
   | Name        | Description                                         |
   +-------------+-----------------------------------------------------+
   | backup      | Shows what is behind the vehicle, e.g., often used  |
   |             | for driver display when the vehicle is in reverse.  |
   |             | Also known as rearview, reverse, rear visibility,   |
   |             | etc.                                                |
   |             |                                                     |
   | left-rear   | Shows view to the left and behind (e.g., left side  |
   |             | rear-view mirror or blind spot view)                |
   |             |                                                     |
   | right-rear  | Shows view to the right and behind (e.g., right     |
   |             | side rear-view mirror or blind spot view)           |
   |             |                                                     |
   | forward     | Shows what is in front of the vehicle               |
   |             |                                                     |
   | rear-wide   | Shows what is behind vehicle (e.g., used by rear-   |
   |             | collision detection systems), separate from backup  |
   |             | view                                                |
   |             |                                                     |
   | lane        | Used by systems to identify road lane and/or        |
   |             | monitor vehicle's position within lane              |
   |             |                                                     |
   | interior    | Shows the interior (e.g., driver)                   |
   |             |                                                     |
   | night-front | Night-vision view of what is in front of the        |
   |             | vehicle                                             |
   +-------------+-----------------------------------------------------+

                Table 7: eCall 5: Camera ID Registry Initial Values

13.  eCall Control Block Schema

   This section presents an XML schema of the eCall control block after
   applying the extensions defined in this document.  Note that the text
   is normative; this schema is informative.

    <?xml version="1.0"?>
    <xs:schema
        targetNamespace="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
        xmlns:xs="http://www.w3.org/2001/XMLSchema"
        xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control"
        xmlns:xml="http://www.w3.org/XML/1998/namespace"
        elementFormDefault="qualified"
        attributeFormDefault="unqualified">

        <xs:import namespace="http://www.w3.org/XML/1998/namespace"
            schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>

        <xs:element name="EmergencyCallData.eCallControl"
                    type="pi:eCallControlType"/>

        <xs:complexType name="eCallControlType">
            <xs:complexContent>
                <xs:restriction base="xs:anyType">
                    <xs:choice>
                        <xs:element name="capabilities"
                                    type="pi:capabilitiesType"/>
                        <xs:element name="request" type="pi:requestType"/>
                        <xs:element name="ack" type="pi:ackType"/>
                        <xs:any namespace="##other" processContents="lax"
                                minOccurs="0"
                                maxOccurs="unbounded"/>
                    </xs:choice>
                    <xs:anyAttribute/>
                </xs:restriction>
            </xs:complexContent>
        </xs:complexType>

        <xs:complexType name="ackType">
            <xs:complexContent>
                <xs:restriction base="xs:anyType">
                    <xs:sequence minOccurs="1" maxOccurs="unbounded">
                        <xs:element name="actionResult" minOccurs="0"
                                    maxOccurs="unbounded">
                            <xs:complexType>
                                <xs:attribute name="action"
                                              type="xs:token"
                                              use="required"/>
                                <xs:attribute name="success"
                                              type="xs:boolean"
                                              use="required"/>
                                <xs:attribute name="reason"
                                              type="xs:token">
                                    <xs:annotation>
                                        <xs:documentation>conditionally
                                             mandatory when @success='false"
                                            to indicate reason code for a
                                            failure </xs:documentation>
                                    </xs:annotation>
                                </xs:attribute>
                                <xs:attribute name="details"
                                              type="xs:string"/>
                                <xs:anyAttribute processContents="skip"/>
                            </xs:complexType>

                        </xs:element>
                        <xs:any namespace="##other" processContents="lax"
                                minOccurs="0"
                                maxOccurs="unbounded"/>
                    </xs:sequence>
                    <xs:attribute name="ref"
                                  type="xs:anyURI"
                                  use="required"/>
                    <xs:attribute name="received"
                                  type="xs:boolean"/>
                    <xs:anyAttribute/>
                </xs:restriction>
            </xs:complexContent>
        </xs:complexType>

        <xs:complexType name="capabilitiesType">
            <xs:complexContent>
                <xs:restriction base="xs:anyType">
                    <xs:sequence minOccurs="1" maxOccurs="unbounded">
                        <xs:element name="request"
                                    type="pi:requestType"
                                    minOccurs="1"
                            maxOccurs="unbounded"/>
                        <xs:any namespace="##other" processContents="lax"
                                 minOccurs="0"
                            maxOccurs="unbounded"/>
                    </xs:sequence>
                    <xs:anyAttribute/>
                </xs:restriction>
            </xs:complexContent>
        </xs:complexType>

        <xs:complexType name="requestType">
            <xs:complexContent>
                <xs:restriction base="xs:anyType">
                    <xs:choice minOccurs="1" maxOccurs="unbounded">
                        <xs:any namespace="##other" processContents="lax"
                                minOccurs="0"
                                maxOccurs="unbounded"/>
                    </xs:choice>
                    <xs:attribute name="action" type="xs:token" use="required"/>
                    <xs:attribute name="msgid" type="xs:unsignedInt"/>
                    <xs:attribute name="persistence" type="xs:duration"/>
                    <xs:attribute name="datatype" type="xs:token"/>
                    <xs:attribute name="supported-datatypes" type="xs:string"/>
                    <xs:attribute name="lamp-id" type="xs:token"/>
                    <xs:attribute name="lamp-action">
                        <xs:simpleType>
                            <xs:restriction base="xs:string">
                                <xs:pattern value=""/>
                                <xs:pattern value=""/>
                                <xs:enumeration value="on"/>
                                <xs:enumeration value="off"/>
                                <xs:enumeration value="flash"/>
                            </xs:restriction>
                        </xs:simpleType>
                    </xs:attribute>
                    <xs:attribute name="supported-lamps" type="xs:string"/>
                    <xs:attribute name="camera-id" type="xs:token"/>
                    <xs:attribute name="supported-cameras" type="xs:string"/>
                    <xs:anyAttribute/>
                </xs:restriction>
            </xs:complexContent>
        </xs:complexType>

    </xs:schema>

                   Figure 12: eCall Control Block Schema

14.  Contributors

16.  Acknowledgements

   We would like to thank Ulrich Dietz Christer Holmberg for his help with earlier
   versions of the original version of this document.

15.  Acknowledgements

   We would like to thank suggestions; Michael
   Montag, Arnoud van Wijk, Ban Al-Bakri, Wes George, Gunnar Hellstrom,
   and Rex Buddenberg for their feedback.

16. feedback; and Ulrich Dietz for his help
   with earlier versions of the original version of this document.

17.  Changes from Previous Versions

16.1.

17.1.  Changes from draft-ietf-08 to draft-ietf-09

   o  Added INFO package registration for eCall.VEDS
   o  Moved <capabilities> element and other extension points back to
      eCall document so that extension points are in base spec (and also
      to get XML schema to compile)
   o  Text changes for clarification.

17.2.  Changes from draft-ietf-07 to draft-ietf-08

   o  Moved much of the metadata/control object from
      [I-D.ietf-ecrit-ecall] to this document as extensions
   o  Editorial clarifications and simplifications
   o  Moved "Call Routing" to be a subsection of "Call Setup"
   o  Deleted "Profile" section and moved some of its text into
      "Introduction"

16.2.

17.3.  Changes from draft-ietf-06 to draft-ietf-07

   o  Minor editorial changes

16.3.

17.4.  Changes from draft-ietf-05 to draft-ietf-06

   o  Added clarifying text regarding signed and encrypted data
   o  Additional informative text in "Migration to Next-Generation"
      section
   o  Additional clarifying text regarding security and privacy.

16.4.

17.5.  Changes from draft-ietf-04 to draft-ietf-05

   o  Reworded security text in main document and in MIME registration
      for the VEDS object

16.5.

17.6.  Changes from draft-ietf-03 to draft-ietf-04

   o  Added example VEDS object
   o  Additional clarifications and corrections
   o  Removed references from Abstract
   o  Moved Document Scope section to follow Introduction

16.6.

17.7.  Changes from draft-ietf-02 to draft-ietf-03

   o  Additional clarifications and corrections

16.7.

17.8.  Changes from draft-ietf-01 to draft-ietf-02

   o  This document now refers to [I-D.ietf-ecrit-ecall] for technical
      aspects including the service URN; this document no longer
      proposes a unique service URN for non-eCall NG-ACN calls; the same
      service URN is now used for all NG-ACN calls including NG-eCall
      and non-eCall
   o  Added discussion of an NG-ACN call placed to a PSAP that doesn't
      support it
   o  Minor wording improvements and clarifications

16.8.

17.9.  Changes from draft-ietf-00 to draft-ietf-01

   o  Added further discussion of test calls
   o  Added further clarification to the document scope
   o  Mentioned that multi-region vehicles may need to support other
      crash notification specifications such as eCall
   o  Minor wording improvements and clarifications

16.9.

17.10.  Changes from draft-gellens-02 to draft-ietf-00

   o  Renamed from draft-gellens- to draft-ietf-
   o  Added text to Introduction to clarify that during a CS ACN, the
      PSAP call taker usually needs to listen to the data and transcribe
      it

16.10.

17.11.  Changes from draft-gellens-01 to -02

   o  Fixed case of 'EmergencyCallData', in accordance with changes to
      [I-D.ietf-ecrit-additional-data]

16.11.
      [RFC7852]

17.12.  Changes from draft-gellens-00 to -01

   o  Now using 'EmergencyCallData' for purpose parameter values and
      MIME subtypes, in accordance with changes to
      [I-D.ietf-ecrit-additional-data] [RFC7852]
   o  Added reference to RFC 6443
   o  Fixed bug that caused Figure captions to not appear

17.

18.  References

17.1.

18.1.  Normative References

   [I-D.ietf-ecrit-additional-data]
              Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and
              J. Winterbottom, "Additional Data Related to an Emergency
              Call", draft-ietf-ecrit-additional-data-38 (work in
              progress), April 2016.

   [I-D.ietf-ecrit-ecall]
              Gellens, R. and H. Tschofenig, "Next-Generation Pan-
              European eCall", draft-ietf-ecrit-ecall-07 draft-ietf-ecrit-ecall-10 (work in
              progress), February July 2016.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <http://www.rfc-editor.org/info/rfc2119>.

   [RFC3023]  Murata, M., St. Laurent, S., and D. Kohn, "XML Media
              Types", RFC 3023, DOI 10.17487/RFC3023, January 2001,
              <http://www.rfc-editor.org/info/rfc3023>.

   [RFC4119]  Peterson, J., "A Presence-based GEOPRIV Location Object
              Format", RFC 4119, DOI 10.17487/RFC4119, December 2005,
              <http://www.rfc-editor.org/info/rfc4119>.

   [RFC4288]  Freed, N. and J. Klensin, "Media Type Specifications and
              Registration Procedures", RFC 4288, DOI 10.17487/RFC4288,
              December 2005, <http://www.rfc-editor.org/info/rfc4288>.

   [RFC5031]  Schulzrinne, H., "A Uniform Resource Name (URN) for
              Emergency and Other Well-Known Services", RFC 5031,
              DOI 10.17487/RFC5031, January 2008,
              <http://www.rfc-editor.org/info/rfc5031>.

   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", BCP 26, RFC 5226,
              DOI 10.17487/RFC5226, May 2008,
              <http://www.rfc-editor.org/info/rfc5226>.

   [RFC5491]  Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV
              Presence Information Data Format Location Object (PIDF-LO)
              Usage Clarification, Considerations, and Recommendations",
              RFC 5491, DOI 10.17487/RFC5491, March 2009,
              <http://www.rfc-editor.org/info/rfc5491>.

   [RFC5962]  Schulzrinne, H., Singh, V., Tschofenig, H., and M.
              Thomson, "Dynamic Extensions to the Presence Information
              Data Format Location Object (PIDF-LO)", RFC 5962,
              DOI 10.17487/RFC5962, September 2010,
              <http://www.rfc-editor.org/info/rfc5962>.

   [RFC6443]  Rosen, B., Schulzrinne, H., Polk, J., and A. Newton,
              "Framework for Emergency Calling Using Internet
              Multimedia", RFC 6443, DOI 10.17487/RFC6443, December
              2011, <http://www.rfc-editor.org/info/rfc6443>.

   [RFC6881]  Rosen, B. and J. Polk, "Best Current Practice for
              Communications Services in Support of Emergency Calling",
              BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013,
              <http://www.rfc-editor.org/info/rfc6881>.

   [RFC7852]  Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and
              J. Winterbottom, "Additional Data Related to an Emergency
              Call", RFC 7852, DOI 10.17487/RFC7852, July 2016,
              <http://www.rfc-editor.org/info/rfc7852>.

   [VEDS]     Advanced Automatic Crash Notification (AACN) Joint APCO/
              NENA Data Standardization Workgroup, , "Vehicular
              Emergency Data Set (VEDS) version 3", July 2012,
              <https://www.apcointl.org/resources/telematics/aacn-and-
              veds.html>.

17.2.

18.2.  Informative references

   [RFC5012]  Schulzrinne, H. and R. Marshall, Ed., "Requirements for
              Emergency Context Resolution with Internet Technologies",
              RFC 5012, DOI 10.17487/RFC5012, January 2008,
              <http://www.rfc-editor.org/info/rfc5012>.

   [RFC5069]  Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M.
              Shanmugam, "Security Threats and Requirements for
              Emergency Call Marking and Mapping", RFC 5069,
              DOI 10.17487/RFC5069, January 2008,
              <http://www.rfc-editor.org/info/rfc5069>.

   [RFC6086]  Holmberg, C., Burger, E., and H. Kaplan, "Session
              Initiation Protocol (SIP) INFO Method and Package
              Framework", RFC 6086, DOI 10.17487/RFC6086, January 2011,
              <http://www.rfc-editor.org/info/rfc6086>.

   [RFC7378]  Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed.,
              "Trustworthy Location", RFC 7378, DOI 10.17487/RFC7378,
              December 2014, <http://www.rfc-editor.org/info/rfc7378>.

   [triage-2008]
              National Center for Injury Prevention and Control, and
              Centers for Disease Control and Prevention,
              "Recommendations from the Expert Panel: Advanced Automatic
              Collision Notification and Triage of the Injured Patient",
              2008, <https://stacks.cdc.gov/view/cdc/5304/>.

   [triage-2011]
              National Center for Injury Prevention and Control, and
              Centers for Disease Control and Prevention, "Guidelines
              for field triage of injured patients: recommendations of
              the National Expert Panel on Field Triage", January 2012,
              <https://www.researchgate.net/journal/1545-8601_MMWR_Recom
              mendations_and_reports_Morbidity_and_mortality_weekly_repo
              rt_Recommendations_and_reports_Centers_for_Disease_Control
              >.

Authors' Addresses

   Randall Gellens
   Consultant
   6755 Mira Mesa Blvd 123-151
   San Diego  92121
   US
   Core Technology Consulting

   Email: rg+ietf@randy.pensive.org
   Brian Rosen
   NeuStar, Inc.
   470 Conrad Dr
   Mars, PA  16046
   US

   Email: br@brianrosen.net

   Hannes Tschofenig
   Individual

   Email: Hannes.Tschofenig@gmx.net
   URI:   http://www.tschofenig.priv.at