Additional Data related to an Emergency Call
draft-ietf-ecrit-additional-data-07

The information below is for an old version of the document
Document Type Active Internet-Draft (ecrit WG)
Last updated 2013-02-25
Replaces draft-rosen-ecrit-additional-data
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
ECRIT                                                           B. Rosen
Internet-Draft                                                   NeuStar
Intended status: Standards Track                           H. Tschofenig
Expires: August 30, 2013                          Nokia Siemens Networks
                                                             R. Marshall
                                         TeleCommunication Systems, Inc.
                                                              R. Gellens
                                             Qualcomm Technologies, Inc.
                                                       February 26, 2013

              Additional Data related to an Emergency Call
                draft-ietf-ecrit-additional-data-07.txt

Abstract

   When an emergency call is sent to a Public Safety Answering Point
   (PSAP), the device that sends it, as well as any service provider in
   the path of the call, or access network through which the call
   originated may have information about the call which the PSAP may be
   able to use.  This document describes an XML data structure to
   contains such data and a Uniform Resource Identifier (URI) for
   conveying the data to the PSAP.  The URI may point to either an
   external resource, or the body of the SIP message.

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 August 30, 2013.

Copyright Notice

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

   This document is subject to BCP 78 and the IETF Trust's Legal

Rosen, et al.            Expires August 30, 2013                [Page 1]
Internet-Draft            Additional Call Data             February 2013

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  5
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  8
   3.  Block Overview . . . . . . . . . . . . . . . . . . . . . . . .  9
   4.  Transmitting Blocks of Additional Data . . . . . . . . . . . . 10
     4.1.  Transmitting blocks using Call-Info  . . . . . . . . . . . 10
     4.2.  Transmitting blocks by reference using Provided-By . . . . 11
     4.3.  Transmitting blocks by value using Provided-By . . . . . . 12
   5.  Data Provider Information  . . . . . . . . . . . . . . . . . . 13
     5.1.  Data Provider String . . . . . . . . . . . . . . . . . . . 13
     5.2.  Data Provider ID . . . . . . . . . . . . . . . . . . . . . 13
     5.3.  Data Provider ID Series  . . . . . . . . . . . . . . . . . 14
     5.4.  Type of Data Provider  . . . . . . . . . . . . . . . . . . 14
     5.5.  Data Provider Contact URI  . . . . . . . . . . . . . . . . 15
     5.6.  Data Provider Languages(s) Supported . . . . . . . . . . . 16
     5.7.  xCard of Data Provider . . . . . . . . . . . . . . . . . . 16
     5.8.  Subcontractor Principal  . . . . . . . . . . . . . . . . . 17
     5.9.  Subcontractor Priority . . . . . . . . . . . . . . . . . . 18
     5.10. emergencyCall.ProviderInfo XML Schema  . . . . . . . . . . 19
   6.  Service Information  . . . . . . . . . . . . . . . . . . . . . 20
     6.1.  Service Environment  . . . . . . . . . . . . . . . . . . . 20
     6.2.  Service Delivered by Provider to End User  . . . . . . . . 20
     6.3.  Service Mobility Environment . . . . . . . . . . . . . . . 22
     6.4.  emergencyCall.SvcInfo XML Schema . . . . . . . . . . . . . 23
   7.  Device Information . . . . . . . . . . . . . . . . . . . . . . 24
     7.1.  Device Classification  . . . . . . . . . . . . . . . . . . 24
     7.2.  Device Manufacturer  . . . . . . . . . . . . . . . . . . . 26
     7.3.  Device Model Number  . . . . . . . . . . . . . . . . . . . 26
     7.4.  Unique Device Identifier . . . . . . . . . . . . . . . . . 27
     7.5.  Type of Device Identifier  . . . . . . . . . . . . . . . . 27
Show full document text