RE: [Ecrit] Emergency Context Routing of Internet Technologies -Architecture Considerations

James and Andy,

I appreciate your contribution to additional discussion of architectural
considerations that provide a context for the focus of on requirements
for location-based mapping protocols in the ECRIT discussions.  I think
this is very helpful.

I have a few observations and suggestions:

In section 1, a suggested definition for
Location Information Server (LIS) -- Provides a mapping function to
relate unique identifiers for IP devices at physical network access
points and the geographic descriptions of their location (e.g., civic
location/street addresses or geographic coordinates).  Responds to
queries for location information.

In Section 2, the list of methods for delivering configuration and
location information to the client does not include  the proposed HELD
method for IP clients to acquire location information from an Internet
access provider (described in HTTP Enabled Location Delivery [HELD],
draft-winterbottom-http-location-delivery-01).  This should be to be
added to the list to address the needs of a number of potential Internet
access providers that would be called upon to provide location
information in North America.

In Section 4, I suggest the addition of a paragraph with wording
something like the following to include an example of an ESRP concept
previously described in Section 6.1 of I-D: "Emergency Services for
Internet Telephony Systems," Henning Schulzrinne, October 18, 2004,
draft-schulzrinne-sipping-emergency-arch-02.

      At the option of the PSAP, more than one ESRP function may be
implemented in series, 
      to provide increasingly precise routing to the appropriate PSAP. 
      This allows for simplification of emergency call routing at the
originating network, 
      and for decision-making at local jurisdictional or at aggregate
levels for 
      real-time control of call routing.  This might also allow for some
additional jurisdictional 
      control of the visibility of emergency call routing information.

Thanks again,

Nadine Abbott  

-----Original Message-----
From: ecrit-bounces@ietf.org [mailto:ecrit-bounces@ietf.org] On Behalf
Of Tschofenig, Hannes
Sent: Tuesday, September 06, 2005 1:59 PM
To: ecrit@ietf.org
Subject: [Ecrit] Emergency Context Routing of Internet Technologies
-Architecture Considerations

hi all, 

james and andy just submitted a draft with the following content:

"
   This document discusses architectural considerations for emergency 
   context routing of Internet technologies.  The purpose of this 
   document is to provide a systemic view of emergency context routing,
   discuss unresolved issues, and explain the relationship of some of 
   the proposals to these issues, while discussing potential directions 
   that might be still be necessary for the working group to 
   investigate.  
"

i have copied the draft to
http://www.ietf-ecrit.org/cache/draft-polk-newton-ecrit-arch-considerati
ons-00.txt

thanks to both of them for touching a number of interesting discussion
topics. 

ciao
hannes

_______________________________________________
Ecrit mailing list
Ecrit@ietf.org
https://www1.ietf.org/mailman/listinfo/ecrit

_______________________________________________
Ecrit mailing list
Ecrit@ietf.org
https://www1.ietf.org/mailman/listinfo/ecrit