Re: [Sipping-emergency] proposed charter, new wg on emergency calling and routing

I'm glad to see some progress on this issue.

My concern is that the charter already specifies or biases the solution. 
I know Ted has a particular solution in mind, possibly influenced by his 
experience at his day job, but this is far from what most people who 
have been actively working in this area have been discussing. Thus, my 
concerns are primarily with the paragraphs below:

> Standards Track RFC describing a query protocol for Emergency Service
> Context
> lookup  by physical location.  Update, insert, and modification of the data
> associated
> with ERC's is out of scope for this work item.
>     (IRIS might be a candidate protocol here--it is a query only protocol
> for registry data,
>      which is one way to model the back end store mapping location to ERC).
> 
> BCP describing the call routing strategies for ip911.
>     (e.g.:  does an ERC have a sip: URI to talk to, or do we need to last
> mile via PSTN?)
> 
> BCP describing how to discover ERC capabilities.
>     (can a deaf person IM this center or can we route through a relay?)
> 
> Threats and security documentation
>     (mainly pointers, but the pointers need to be gathered).

I believe that the description misses a core requirement, namely the 
ability to administer the system in a fully decentralized manner that 
reflects the current administrative boundaries and delebation of 
responsibilities. It also must be international, i.e., it cannot just 
work for the US (or pick any other country) or require a US entity to 
manage the system.

It would have been nice to recognize that there has been work going on 
this area for several years, but maybe that's too much to ask.

Henning

_______________________________________________
Sipping-emergency mailing list
Sipping-emergency@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-emergency