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

The information below is for an old version of the document
Document Type Active Internet-Draft (ecrit WG)
Last updated 2011-10-27 (latest revision 2010-11-08)
Replaces draft-schulzrinne-ecrit-psap-callback
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
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                                                     H. Schulzrinne
Internet-Draft                                       Columbia University
Intended status: Standards Track                           H. Tschofenig
Expires: April 29, 2012                           Nokia Siemens Networks
                                                             C. Holmberg
                                                                Ericsson
                                                                M. Patel
                                             InterDigital Communications
                                                        October 27, 2011

             Public Safety Answering Point (PSAP) Callback
                 draft-ietf-ecrit-psap-callback-03.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 offers capabilities to allow
   callbask to bypass authorization policies to reach the caller without
   unnecessary delays.  However, the mechanism specified prior to this
   document supports only limited scenarios.  This document discusses
   some shortcomings, presents additional scenarios where better-than-
   normal call treatment behavior would be desirable, and specifies a
   protocol solution.

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

Schulzrinne, et al.      Expires April 29, 2012                 [Page 1]
Internet-Draft                PSAP Callback                 October 2011

   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 April 29, 2012.

Copyright Notice

   Copyright (c) 2011 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  . . . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  Callback Scenarios . . . . . . . . . . . . . . . . . . . . . .  6
     3.1.  Routing Asymmetry  . . . . . . . . . . . . . . . . . . . .  6
     3.2.  Multi-Stage Routing  . . . . . . . . . . . . . . . . . . .  7
     3.3.  Call Forwarding  . . . . . . . . . . . . . . . . . . . . .  8
     3.4.  Network-based Service URN Resolution . . . . . . . . . . . 10
     3.5.  PSTN Interworking  . . . . . . . . . . . . . . . . . . . . 11
   4.  Specification  . . . . . . . . . . . . . . . . . . . . . . . . 12
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . . 13
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 14
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 16
     8.2.  Informative References . . . . . . . . . . . . . . . . . . 17
   Appendix A.  Alternative Solutions Considered  . . . . . . . . . . 19
     A.1.  Identity-based Authorization . . . . . . . . . . . . . . . 19
     A.2.  Trait-based Authorization  . . . . . . . . . . . . . . . . 20
     A.3.  Call Marking . . . . . . . . . . . . . . . . . . . . . . . 21

Schulzrinne, et al.      Expires April 29, 2012                 [Page 2]
Show full document text