Public Safety Answering Point (PSAP) Callback
draft-ietf-ecrit-psap-callback-10

The information below is for an old version of the document
Document Type Active Internet-Draft (ecrit WG)
Last updated 2013-09-17 (latest revision 2013-07-13)
Replaces draft-schulzrinne-ecrit-psap-callback
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd Roger Marshall
Shepherd write-up Show (last changed 2013-07-29)
IESG IESG state In Last Call (ends 2013-09-27)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Richard Barnes
Send notices to ecrit-chairs@tools.ietf.org, draft-ietf-ecrit-psap-callback@tools.ietf.org
IANA IANA review state IANA OK - Actions Needed
ECRIT                                                     H. Schulzrinne
Internet-Draft                                       Columbia University
Intended status: Standards Track                           H. Tschofenig
Expires: January 14, 2014                         Nokia Siemens Networks
                                                             C. Holmberg
                                                                Ericsson
                                                                M. Patel
                                             InterDigital Communications
                                                           July 13, 2013

             Public Safety Answering Point (PSAP) Callback
                 draft-ietf-ecrit-psap-callback-10.txt

Abstract

   After an emergency call is completed (either prematurely terminated
   by the emergency caller or normally by the call taker) it is possible
   that the call taker feels the need for further communication.  For
   example, the call may have been dropped by accident without the call
   taker having sufficient information about the current situation of a
   wounded person.  A call taker may trigger a callback towards the
   emergency caller using the contact information provided with the
   initial emergency call.  This callback could, under certain
   circumstances, be treated like any other call and as a consequence it
   may get blocked by authorization policies or may get forwarded to an
   answering machine.

   The IETF emergency services architecture specification already offers
   a solution approach for allowing PSAP callbacks to bypass
   authorization policies to reach the caller without unnecessary
   delays.  Unfortunately, the specified mechanism only supports limited
   scenarios.  This document discusses shortcomings of the current
   mechanisms and illustrates additional scenarios where better-than-
   normal call treatment behavior would be desirable.  A solution based
   on a new header field value, called "psap-callback", for the SIP
   Priority header field is specified to accomplish the PSAP callback
   marking.

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/.

Schulzrinne, et al.     Expires January 14, 2014                [Page 1]
Internet-Draft                PSAP Callback                    July 2013

   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 January 14, 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Callback Scenarios  . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Routing Asymmetry . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Multi-Stage Routing . . . . . . . . . . . . . . . . . . .   6
     3.3.  Call Forwarding . . . . . . . . . . . . . . . . . . . . .   7
     3.4.  Network-based Service URN Resolution  . . . . . . . . . .   8
     3.5.  PSTN Interworking . . . . . . . . . . . . . . . . . . . .   9
   4.  SIP PSAP Callback Indicator . . . . . . . . . . . . . . . . .  10
     4.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .  10
     4.2.  Usage . . . . . . . . . . . . . . . . . . . . . . . . . .  10
     4.3.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . .  11
       4.3.1.  General . . . . . . . . . . . . . . . . . . . . . . .  11
       4.3.2.  ABNF  . . . . . . . . . . . . . . . . . . . . . . . .  11
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
     5.1.  Security Threat . . . . . . . . . . . . . . . . . . . . .  11
     5.2.  Security Requirements . . . . . . . . . . . . . . . . . .  11
     5.3.  Security Solution . . . . . . . . . . . . . . . . . . . .  12
Show full document text