Re: crypto delay (Notes from Non-meeting)

A

>Perhaps this is a mistake? I think that emergency calling is complex,
>and I'm far more concerned about my non-emergency privacy.

Until its you that has the heart attack.

>I'm also interested in trying, and would like to throw out the
>suggestion that we might specify a level of crypto which is secure,
>and offer nothing on slower processors. That would make sense if we
>worry about roll-back attacks, and the ongoing cost of having weak
>crypto in the system.

I'm more concerned that the needs of the emergency response system are not
impeded in any form I'm having the heart attack thank you very much
..adding complexity to the task of getting a location object from Point A
to Point B is a "bad thing" tm. KISS strikes me as a more interesting
foundation for protocol design.

Now on to other things..

What is the location object be are all talking about ? XML? ASN.1 <just
kidding>

What is the semantical expression of location object the PSAP needs?
Typically it keys a database look up based on TN to address. PSAP address
databases are simply subsets of LIDB or DA information supplied by the
LEC's this is now complicated by the mobile environment where formal
Lattitude and Longitude are used ..again keyed to address.

So in those environments where E.164 addressing is uesd that is a
requirement...not we have the problem of sip URI's

Now what other paramaters does it need to transmit?

TTL?

Confidence Factor ? By this I mean ..whatever system generates the
location information may be able to transmit its Confidence in the
reliability of the data. This might be useful in those cases where L/L
triangulation is difficult or is unable to reach pinpoint accuracy.

I'm just thinking out loud about what could or should not be included in
the object.

>Adam

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Manager, Strategic Technology Initiatives
NeuStar Inc.
45980 Center Oak Plaza Bldg 8 Sterling, VA 20166
1120 Vermont Ave NW Suite 400 Washington DC 20005
Voice +1 571.434.5651 Cell : +1 314.503.0640, Fax: +1 815.333.1237
<mailto: rshockey@ix.netcom.com> or
<mailto: rich.shockey@neustar.biz>
<http://www.neustar.biz>
<http://www.enum.org>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Received on Sat Apr 6 19:36:39 2002