ECRIT Direct Emergency Calling
draft-winterbottom-ecrit-direct-02

Document Type Expired Internet-Draft (individual)
Last updated 2010-03-07
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-winterbottom-ecrit-direct-02.txt

Abstract

The specified IETF emergency services architecture puts a strong emphasis on emergency call and emergency messaging via the Voice Service Provider (VSP) / Application Service Provider (ASP). There are two reasons for this design decision: The call routing via the VSP/ASP is more natural as it follows the standard communication pattern and transition deployments assume non-updated end hosts. As the deployment of the Location-to-Service Translation protocol progresses there are possibilities for upgraded end devices to directly communicate with the IP-based emergency services network without the need to interact with a VSP/ASP, which simplifies the task of regulators as the involved parties are within the same jurisdiction. This memo describes the procedures and operations of a generic emergency calling client utilizing the available building blocks.

Authors

James Winterbottom (james.winterbottom@andrew.com)
Martin Thomson (martin.thomson@andrew.com)
Hannes Tschofenig (Hannes.Tschofenig@gmx.net)
Henning Schulzrinne (hgs+ecrit@cs.columbia.edu)

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