Additional Data Related to an Emergency Call
draft-ietf-ecrit-additional-data-33

Document Type Active Internet-Draft (ecrit WG)
Last updated 2015-07-20
Replaces draft-rosen-ecrit-additional-data
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html
Stream WG state Submitted to IESG for Publication
Document shepherd Marc Linsner
Shepherd write-up Show (last changed 2015-05-08)
IESG IESG state AD Evaluation
Telechat date
Responsible AD Alissa Cooper
Send notices to draft-ietf-ecrit-additional-data.ad@ietf.org, draft-ietf-ecrit-additional-data@ietf.org, ecrit-chairs@ietf.org, draft-ietf-ecrit-additional-data.shepherd@ietf.org, "Marc Linsner" <mlinsner@cisco.com>
ECRIT                                                         R. Gellens
Internet-Draft                               Qualcomm Technologies, Inc.
Intended status: Standards Track                                B. Rosen
Expires: January 20, 2016                                        NeuStar
                                                           H. Tschofenig

                                                             R. Marshall
                                         TeleCommunication Systems, Inc.
                                                         J. Winterbottom

                                                           July 19, 2015

              Additional Data Related to an Emergency Call
                draft-ietf-ecrit-additional-data-33.txt

Abstract

   When an emergency call is sent to a Public Safety Answering Point
   (PSAP), the originating device, the access network provider to which
   the device is connected, and all service providers in the path of the
   call have information about the call, the caller or the location
   which is helpful for the PSAP to have in handling the emergency.
   This document describes data structures and mechanisms to convey such
   data to the PSAP.  The intent is that every emergency call carry the
   information described here using the mechanisms described here.

   The mechanisms permit the data to be conveyed by reference (as an
   external resource) or by value (within the body of a SIP message or a
   location object).  This follows the tradition of prior emergency
   services standardization work where data can be conveyed by value
   within the call signaling (i.e., in the body of the SIP message) or
   by reference.

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."

Gellens, et al.         Expires January 20, 2016                [Page 1]
Internet-Draft            Additional Call Data                 July 2015

   This Internet-Draft will expire on January 20, 2016.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   6
   3.  Document Scope  . . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Data Structures . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Data Provider Information . . . . . . . . . . . . . . . .   9
       4.1.1.  Data Provider String  . . . . . . . . . . . . . . . .   9
       4.1.2.  Data Provider ID  . . . . . . . . . . . . . . . . . .   9
       4.1.3.  Data Provider ID Series . . . . . . . . . . . . . . .  10
       4.1.4.  Type of Data Provider . . . . . . . . . . . . . . . .  11
       4.1.5.  Data Provider Contact URI . . . . . . . . . . . . . .  12
       4.1.6.  Data Provider Languages(s) Supported  . . . . . . . .  13
       4.1.7.  xCard of Data Provider  . . . . . . . . . . . . . . .  13
       4.1.8.  Subcontractor Principal . . . . . . . . . . . . . . .  14
       4.1.9.  Subcontractor Priority  . . . . . . . . . . . . . . .  15
       4.1.10. ProviderInfo Example  . . . . . . . . . . . . . . . .  15
     4.2.  Service Information . . . . . . . . . . . . . . . . . . .  17
       4.2.1.  Service Environment . . . . . . . . . . . . . . . . .  17
       4.2.2.  Service Type  . . . . . . . . . . . . . . . . . . . .  18
       4.2.3.  Service Mobility Environment  . . . . . . . . . . . .  20
       4.2.4.  EmergencyCallData.ServiceInfo Example . . . . . . . .  21
     4.3.  Device Information  . . . . . . . . . . . . . . . . . . .  22
       4.3.1.  Device Classification . . . . . . . . . . . . . . . .  22
Show full document text