[Ecrit] [Fwd: New Version Notification for draft-barnes-ecrit-rough-loc-02]

[Richard Barnes <rbarnes at bbn.com>]

In anticipation of the virtual interim, here's a new draft of rough-loc.

-- Added a requirement that the rough location MUST contain the precise 
location of the endpoint (when known)

-- Added considerations for civic addresses

-- Extended security considerations to note the necessity of URIs that 
allow PSAPs to access precise location

-- Fixed several editorial nits





-------- Original Message --------
Subject: New Version Notification for draft-barnes-ecrit-rough-loc-02
Date: Mon, 23 Feb 2009 19:22:51 -0800 (PST)
From: IETF I-D Submission Tool <idsubmission at ietf.org>
To: rbarnes at bbn.com
CC: mlepinski at bbn.com


A new version of I-D, draft-barnes-ecrit-rough-loc-02.txt has been 
successfuly submitted by Richard Barnes and posted to the IETF repository.

Filename:	 draft-barnes-ecrit-rough-loc
Revision:	 02
Title:		 Using Imprecise Location for Emergency Context Resolution
Creation_date:	 2009-02-24
WG ID:		 Independent Submission
Number_of_pages: 14

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.




The IETF Secretariat.