Skip to main content

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

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
Authors Richard Barnes , Matt Lepinski
Last updated 2011-03-29 (Latest revision 2010-08-16)
Replaces draft-barnes-ecrit-rough-loc
RFC stream Internet Engineering Task Force (IETF)
Formats
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
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

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 descibe how emergency services and non-emergency services can be invoked by an endpoint that does not have access to its precise location.

Authors

Richard Barnes
Matt Lepinski

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