Additional Data Related to an Emergency Call
RFC 7852

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions

Internet Engineering Task Force (IETF)                        R. Gellens
Request for Comments: 7852
Updates: 6443, 6881                                             B. Rosen
Category: Standards Track                                        NeuStar
ISSN: 2070-1721                                            H. Tschofenig

                                                             R. Marshall
                                         TeleCommunication Systems, Inc.
                                                         J. Winterbottom
                                             Winterb Consulting Services
                                                               July 2016

              Additional Data Related to an Emergency Call

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 as
   much of the information described here as possible 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 is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7852.

Gellens, et al.              Standards Track                    [Page 1]
RFC 7852                  Additional Call Data                 July 2016

Copyright Notice

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

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

Table of Contents

   1.  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 Language(s) Supported . . . . . . . . . .  13
     4.1.7.  xCard of Data Provider  . . . . . . . . . . . . . . . .  14
     4.1.8.  Subcontractor Principal . . . . . . . . . . . . . . . .  14
     4.1.9.  Subcontractor Priority  . . . . . . . . . . . . . . . .  15
     4.1.10. ProviderInfo Example  . . . . . . . . . . . . . . . . .  15
    4.2.  Service Information  . . . . . . . . . . . . . . . . . . .  18
     4.2.1.  Service Environment . . . . . . . . . . . . . . . . . .  18
     4.2.2.  Service Type  . . . . . . . . . . . . . . . . . . . . .  19
     4.2.3.  Service Mobility Environment .  . . . . . . . . . . . .  21
     4.2.4.  EmergencyCallData.ServiceInfo Example . . . . . . . . .  22
    4.3.  Device Information . . . . . . . . . . . . . . . . . . . .  22
     4.3.1.  Device Classification . . . . . . . . . . . . . . . . .  22
     4.3.2.  Device Manufacturer . . . . . . . . . . . . . . . . . .  23
     4.3.3.  Device Model Number . . . . . . . . . . . . . . . . . .  24
     4.3.4.  Unique Device Identifier  . . . . . . . . . . . . . . .  24
     4.3.5.  Device/Service-Specific Additional Data Structure . . .  25