Extensions to the Emergency Services Architecture for dealing with Unauthenticated and Unauthorized Devices
draft-ietf-ecrit-unauthenticated-access-07

The information below is for an old version of the document
Document Type Active Internet-Draft (ecrit WG)
Last updated 2013-10-02 (latest revision 2013-07-13)
Replaces draft-schulzrinne-ecrit-unauthenticated-access
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd Roger Marshall
Shepherd write-up Show (last changed 2013-07-29)
IESG IESG state Waiting for AD Go-Ahead
Consensus Boilerplate Unknown
Telechat date
Responsible AD Richard Barnes
Send notices to ecrit-chairs@tools.ietf.org, draft-ietf-ecrit-unauthenticated-access@tools.ietf.org
IANA IANA review state IANA OK - No Actions Needed
ECRIT                                                     H. Schulzrinne
Internet-Draft                                       Columbia University
Intended status: Standards Track                               S. McCann
Expires: January 14, 2014                      Research in Motion UK Ltd
                                                                G. Bajko
                                                                   Nokia
                                                           H. Tschofenig
                                                  Nokia Siemens Networks
                                                          D. Kroeselberg
                                                                 Siemens
                                                           July 13, 2013

   Extensions to the Emergency Services Architecture for dealing with
                Unauthenticated and Unauthorized Devices
             draft-ietf-ecrit-unauthenticated-access-07.txt

Abstract

   The IETF emergency services architecture assumes that the calling
   device has acquired rights to use the access network or that no
   authentication is required for the access network, such as for public
   wireless access points.  Subsequent protocol interactions, such as
   obtaining location information, learning the address of the Public
   Safety Answering Point (PSAP) and the emergency call itself are
   largely decoupled from the underlying network access procedures.

   In some cases, however, the device does not have these credentials
   for network access, does not have a VoIP service provider, or the
   credentials have become invalid, e.g., because the user has exhausted
   their prepaid balance or the account has expired.

   This document provides a problem statement, introduces terminology
   and describes an extension for the base IETF emergency services
   architecture to address these scenarios.

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 January 14, 2014                [Page 1]
Internet-Draft      Unauthenticated Emergency Service          July 2013

   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 . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Use Case Categories . . . . . . . . . . . . . . . . . . . . .   5
   4.  ZBP Considerations  . . . . . . . . . . . . . . . . . . . . .   7
   5.  NASP Considerations . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  End Host Profile  . . . . . . . . . . . . . . . . . . . .  10
       5.1.1.  LoST Server Discovery . . . . . . . . . . . . . . . .  10
       5.1.2.  ESRP Discovery  . . . . . . . . . . . . . . . . . . .  10
       5.1.3.  Location Determination and Location Configuration . .  10
       5.1.4.  Emergency Call Identification . . . . . . . . . . . .  10
       5.1.5.  SIP Emergency Call Signaling  . . . . . . . . . . . .  10
       5.1.6.  Media . . . . . . . . . . . . . . . . . . . . . . . .  11
       5.1.7.  Testing . . . . . . . . . . . . . . . . . . . . . . .  11
     5.2.  IAP/ISP Profile . . . . . . . . . . . . . . . . . . . . .  11
       5.2.1.  ESRP Discovery  . . . . . . . . . . . . . . . . . . .  11
       5.2.2.  Location Determination and Location Configuration . .  11
     5.3.  ESRP Profile  . . . . . . . . . . . . . . . . . . . . . .  11
       5.3.1.  Emergency Call Routing  . . . . . . . . . . . . . . .  11
       5.3.2.  Emergency Call Identification . . . . . . . . . . . .  12
       5.3.3.  SIP Emergency Call Signaling  . . . . . . . . . . . .  12
   6.  Lower Layer Considerations for NAA Case . . . . . . . . . . .  12
Show full document text