Skip to main content

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

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Henning Schulzrinne , Stephen McCann , Gabor Bajko , Hannes Tschofenig , Dirk Kroeselberg
Last updated 2011-01-10 (Latest revision 2010-07-12)
Replaced by draft-ietf-ecrit-unauthenticated-access
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-ecrit-unauthenticated-access
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

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, the device does not have credentials for network access, does not have a VoIP provider or application service provider (ASP), 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.

Authors

Henning Schulzrinne
Stephen McCann
Gabor Bajko
Hannes Tschofenig
Dirk Kroeselberg

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)