datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

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

Document type: Expired Internet-Draft (ecrit WG)
Document stream: IETF
Last updated: 2013-01-17 (latest revision 2012-07-16)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-ecrit-rough-loc

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)