Using Imprecise Location for Emergency Context Resolution
draft-ietf-ecrit-rough-loc-05

Document Type Expired Internet-Draft (ecrit WG)
Last updated 2013-01-17 (latest revision 2012-07-16)
Replaces draft-barnes-ecrit-rough-loc
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream WG state WG Document
Document shepherd No shepherd assigned
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-ietf-ecrit-rough-loc-05.txt

Abstract

Emergency calling works best when precise location is available for emergency call routing. However, there are situations in which a location provider is unable or unwilling to provide precise location, yet still wishes to enable subscribers to make emergency calls. This document describes the level of location accuracy that providers must provide to enable emergency call routing. In addition, we describe additional rules for networks and endpoints to enable emergency calling by endpoints that do not have access to precise location.

Authors

Richard Barnes (rbarnes@bbn.com)
Matt Lepinski (mlepinski@bbn.com)

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