Additional Data related to an Emergency Call
draft-ietf-ecrit-additional-data-15
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (ecrit WG)
|
|
Last updated |
|
2013-11-04
|
|
Replaces |
|
draft-rosen-ecrit-additional-data
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized
bibtex
|
|
Reviews |
|
|
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: May 07, 2014 Nokia Solutions and Networks
R. Marshall
TeleCommunication Systems, Inc.
R. Gellens
Qualcomm Technologies, Inc.
J. Winterbottom
November 03, 2013
Additional Data related to an Emergency Call
draft-ietf-ecrit-additional-data-15.txt
Abstract
When an emergency call is sent to a Public Safety Answering Point
(PSAP), the device that sends it, as well as any application service
provider in the path of the call, or access network provider through
which the call originated may have information about the call, the
caller or the location which the PSAP may be able to use. This
document describes data structures and a mechanism to convey such
data to the PSAP. The mechanism uses a Uniform Resource Identifier
(URI), which may point to either an external resource or an object in
the body of the SIP message. The mechanism thus allows the data to
be passed by reference (when the URI points to an external resource)
or by value (when it points into the body of the message). This
follows the tradition of prior emergency services standardization
work where data can be conveyed by value within the call signaling
(i.e., in body of the SIP message) and also 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."
Rosen, et al. Expires May 07, 2014 [Page 1]
Internet-Draft Additional Call Data November 2013
This Internet-Draft will expire on May 07, 2014.
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
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. Data Structures . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Data Provider Information . . . . . . . . . . . . . . . . 7
3.1.1. Data Provider String . . . . . . . . . . . . . . . . 7
3.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . 8
3.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 8
3.1.4. Type of Data Provider . . . . . . . . . . . . . . . . 9
3.1.5. Data Provider Contact URI . . . . . . . . . . . . . . 10
3.1.6. Data Provider Languages(s) Supported . . . . . . . . 11
3.1.7. xCard of Data Provider . . . . . . . . . . . . . . . 11
3.1.8. Subcontractor Principal . . . . . . . . . . . . . . . 12
3.1.9. Subcontractor Priority . . . . . . . . . . . . . . . 12
3.1.10. ProviderInfo Example . . . . . . . . . . . . . . . . 13
3.2. Service Information . . . . . . . . . . . . . . . . . . . 15
3.2.1. Service Environment . . . . . . . . . . . . . . . . . 15
3.2.2. Service Delivered by Provider to End User . . . . . . 15
3.2.3. Service Mobility Environment . . . . . . . . . . . . 18
3.2.4. emergencyCallData.SvcInfo Example . . . . . . . . . . 18
3.3. Device Information . . . . . . . . . . . . . . . . . . . 19
3.3.1. Device Classification . . . . . . . . . . . . . . . . 19
3.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 20
Show full document text