Non-Interactive Emergency Calls
draft-rosen-stir-emergency-calls-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-09
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
stir                                                            B. Rosen
Internet-Draft                                             March 9, 2020
Intended status: Standards Track
Expires: September 10, 2020

                    Non-Interactive Emergency Calls
                  draft-rosen-stir-emergency-calls-00

Abstract

   Emergency calls from citizens to authorities, and call back of such
   emergency calls by authorities to citizens need assurances that
   headers intended to get appropriate priority from the networks they
   traverse, and in some cases, appropriate routing.  Protection of the
   SIP Resource Priority Header and the SIP Priority header is needed
   for such calls.  This document describes the environment for placing
   emergency calls and call backs which motivate the need and use of the
   mechanisms described in other documents

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.

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

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

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Emergency Calls . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Emergency Call-backs  . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   [RFC6643] describes how devices use the Internet to place emergency
   calls and how Public Safety Answering Points (PSAPs) handle Internet
   emergency calls.  In traditional telephone networks, emergency calls
   are not afforded any priority in the network.  Emergency calls are
   marked with a Service URN, [RFC5031].

   Sometimes, the emergency services need to call the person that placed
   an emergency call after the original emergency call was terminated.
   This is a case of "call-back".  [RFC7090] discusses using SIP
   Priority to mark a call as a call back.  The Resource Priority
   Header, [RFC4412] defines a way to request the network afford
   priority in resources: The 'Priority' header field describes the
   importance that the SIP request should have for the receiving human
   or its agent.  For example, that header may be factored into
   decisions about call routing to mobile devices and assistants and
   about call acceptance when the call destination is busy.  The
   'Priority' header field does not affect the usage of PSTN gateway or
   proxy resources, for example.  In addition, any User Agent Client
   (UAC) can assert any 'Priority' value, and usage of 'Resource-
   Priority' header field values is subject to authorization.

   This document describes the environment for placing emergency calls
   on the Internet, which has different capabilities than the PSTN, as
   well as call backs across the Internet and describes the requirements
   for protecting them with the "stir" mechanism.

Rosen                  Expires September 10, 2020               [Page 2]
Internet-Draft       Non-Interactive Emergency Calls          March 2020

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text