Additional Data related to an Emergency Call
draft-ietf-ecrit-additional-data-06
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (ecrit WG)
|
|
Last updated |
|
2013-02-18
|
|
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.R. Rosen
Internet-Draft NeuStar
Intended status: Standards Track H. Tschofenig
Expires: August 20, 2013 Nokia Siemens Networks
R. Marshall
TeleCommunication Systems, Inc.
R. Gellens
Qualcomm Technologies, Inc.
February 18, 2013
Additional Data related to an Emergency Call
draft-ietf-ecrit-additional-data-06.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 20, 2013.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
Rosen, Tschofenig, MarshExpireseAugust 20, 2013 [Page 1]
Internet-Draft Additional Call Data February 2013
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Block Overview . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Transmitting Blocks of Additional Data . . . . . . . . . . . . 7
4.1. Transmitting blocks using Call-Info . . . . . . . . . . . 7
4.2. Transmitting blocks by reference using Provided-By . . . . 8
4.3. Transmitting blocks by value using Provided-By . . . . . . 9
5. Data Provider Information . . . . . . . . . . . . . . . . . . 9
5.1. Data Provider String . . . . . . . . . . . . . . . . . . . 9
5.2. Data Provider ID . . . . . . . . . . . . . . . . . . . . . 10
5.3. Data Provider ID Series . . . . . . . . . . . . . . . . . 10
5.4. Type of Data Provider . . . . . . . . . . . . . . . . . . 11
5.5. Data Provider Contact URI . . . . . . . . . . . . . . . . 12
5.6. Data Provider Languages(s) Supported . . . . . . . . . . . 12
5.7. xCard of Data Provider . . . . . . . . . . . . . . . . . . 13
5.8. Subcontractor Principal . . . . . . . . . . . . . . . . . 13
5.9. Subcontractor Priority . . . . . . . . . . . . . . . . . . 14
5.10. emergencyCall.ProviderInfo XML Schema . . . . . . . . . . 14
6. Service Information . . . . . . . . . . . . . . . . . . . . . 15
6.1. Service Environment . . . . . . . . . . . . . . . . . . . 15
6.2. Service Delivered by Provider to End User . . . . . . . . 16
6.3. Service Mobility Environment . . . . . . . . . . . . . . . 17
6.4. emergencyCall.SvcInfo XML Schema . . . . . . . . . . . . . 18
7. Device Information . . . . . . . . . . . . . . . . . . . . . . 18
7.1. Device Classification . . . . . . . . . . . . . . . . . . 19
7.2. Device Manufacturer . . . . . . . . . . . . . . . . . . . 20
7.3. Device Model Number . . . . . . . . . . . . . . . . . . . 21
7.4. Unique Device Identifier . . . . . . . . . . . . . . . . . 21
Show full document text