ECRIT B. Rosen
Internet-Draft NeuStar, Inc.
Intended status: Standards Track H. Schulzrinne
Expires: August 29, 2013 Columbia U.
H. Tschofenig
Nokia Siemens Networks
February 25, 2013
Data-Only Emergency Calls
draft-ietf-ecrit-data-only-ea-05.txt
Abstract
RFC 6443 'Framework for Emergency Calling Using Internet Multimedia'
describes how devices use the Internet to place emergency calls and
how Public Safety Answering Points (PSAPs) can handle Internet
multimedia emergency calls natively. The exchange of multimedia
traffic typically involves a SIP session establishment starting with
a SIP INVITE that negotiates various parameters for that session.
In some cases, however, the transmission of application data is
everything that is needed. Examples of such environments include a
temperature sensors issuing alerts, or vehicles sending crash data.
Often these alerts are conveyed as one-shot data transmissions.
These type of interactions are called 'data-only emergency calls'.
This document describes a container for the data based on the Common
Alerting Protocol (CAP) and its transmission using the SIP MESSAGE
transaction.
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 29, 2013.
Copyright Notice
Rosen, et al. Expires August 29, 2013 [Page 1]
Internet-Draft Data-Only Emergency Calls February 2013
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Architectural Overview . . . . . . . . . . . . . . . . . . . . 5
4. Protocol Specification . . . . . . . . . . . . . . . . . . . . 8
4.1. CAP Transport . . . . . . . . . . . . . . . . . . . . . . 8
4.2. Profiling of the CAP Document Content . . . . . . . . . . 8
4.3. Sending a Data-Only Emergency Call . . . . . . . . . . . . 9
5. Error Handling . . . . . . . . . . . . . . . . . . . . . . . . 10
5.1. 425 (Bad Alert Message) Response Code . . . . . . . . . . 10
5.2. The AlertMsg-Error Header Field . . . . . . . . . . . . . 10
6. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
7. Security Considerations . . . . . . . . . . . . . . . . . . . 17
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
8.1. Registration of the 'application/cap+xml' MIME type . . . 19
8.2. IANA Registration for 425 Response Code . . . . . . . . . 20
8.3. IANA Registration of New AlertMsg-Error Header Field . . . 20
8.4. IANA Registration for the SIP AlertMsg-Error Codes . . . . 21
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23
10.1. Normative References . . . . . . . . . . . . . . . . . . . 23
10.2. Informative References . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25
Rosen, et al. Expires August 29, 2013 [Page 2]
datatracker.ietf.org