Non-Interactive Emergency Calls
draft-ietf-ecrit-data-only-ea-22

Document Type Active Internet-Draft (ecrit WG)
Last updated 2020-04-08 (latest revision 2020-03-09)
Replaces draft-rosen-ecrit-data-only-ea
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Aug 2017 - Submit 'Common Alert... )
Document shepherd Allison Mankin
Shepherd write-up Show (last changed 2019-04-16)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Adam Roach
Send notices to "Allison Mankin" <allison.mankin@gmail.com>, <draft-ietf-ecrit-data-only-ea@ietf.org>
IANA IANA review state Version Changed - Review Needed
IANA action state No IANA Actions
IANA expert review state Expert Reviews OK
IANA expert review comments I reviewed Section 10.2 and it meets the requirements of RFC 7852. I approve.
RFC Editor RFC Editor state RFC-EDITOR
ECRIT                                                           B. Rosen
Internet-Draft
Intended status: Standards Track                          H. Schulzrinne
Expires: September 10, 2020                                  Columbia U.
                                                           H. Tschofenig
                                                             ARM Limited
                                                              R. Gellens
                                              Core Technology Consulting
                                                           March 9, 2020

                    Non-Interactive Emergency Calls
                    draft-ietf-ecrit-data-only-ea-22

Abstract

   Use of the Internet for emergency calling is described in RFC 6443,
   'Framework for Emergency Calling Using Internet Multimedia'.  In some
   cases of emergency calls, the transmission of application data is all
   that is needed and no interactive media channel is established: a
   situation referred to as 'non-interactive emergency calls', where,
   unlike most emergency calls, there is no two way interactive media
   such as voice or video or text.  This document describes use of a SIP
   MESSAGE transaction that includes a container for the data based on
   the Common Alerting Protocol (CAP).  That type of emergency request
   does not establish a session, distinguishing it from SIP INVITE,
   which does.  Any device that needs to initiate a request for
   emergency services without an interactive media channel would use the
   mechanisms in this document.

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 https://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 September 10, 2020.

Rosen, et al.          Expires September 10, 2020               [Page 1]
Internet-Draft       Non-Interactive Emergency Calls          March 2020

Copyright Notice

   Copyright (c) 2020 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
   (https://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 . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Architectural Overview  . . . . . . . . . . . . . . . . . . .   4
   4.  Protocol Specification  . . . . . . . . . . . . . . . . . . .   6
     4.1.  CAP Transport . . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Profiling of the CAP Document Content . . . . . . . . . .   7
     4.3.  Sending a non-interactive Emergency Call  . . . . . . . .   8
   5.  Error Handling  . . . . . . . . . . . . . . . . . . . . . . .   9
     5.1.  425 (Bad Alert Message) Response Code . . . . . . . . . .   9
     5.2.  The AlertMsg-Error Header Field . . . . . . . . . . . . .   9
   6.  Call Backs  . . . . . . . . . . . . . . . . . . . . . . . . .  11
   7.  Handling Large Amounts of Data  . . . . . . . . . . . . . . .  11
   8.  Example . . . . . . . . . . . . . . . . . . . . . . . . . . .  12
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
     10.1.  Registration of the
            'application/EmergencyCallData.cap+xml' media type . . .  18
     10.2.  IANA Registration of 'cap' Additional Data Block . . . .  19
     10.3.  IANA Registration for 425 Response Code  . . . . . . . .  19
     10.4.  IANA Registration of New AlertMsg-Error Header Field . .  20
     10.5.  IANA Registration for the SIP AlertMsg-Error Codes . . .  20
   11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  21
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  21
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  21
     12.2.  Informative References . . . . . . . . . . . . . . . . .  23
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  23
Show full document text