Skip to main content

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

Document Type Expired Internet-Draft (ecrit WG)
Expired & archived
Authors Richard Barnes , Matt Lepinski
Last updated 2013-01-17 (Latest revision 2012-07-16)
Replaces draft-barnes-ecrit-rough-loc
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
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 describe additional rules for networks and endpoints to enable emergency calling by endpoints that do not have access to 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.)