RE: crypto delay (Notes from Non-meeting)

Absolutely correct! Time to answer the call is very important. As the
Wireless Phase II implementations are unfolding, it is very typical for the
call to be completed (people talking) for 20+ seconds before the location
information is displayed on the PSAP's screen. This time lag has nothing to
do with authentication/crypto, it's simply the time it takes to triangluate
and derive a reasonably accurate location.

Taking time to authenticate and/or intiate crypto may be doable if it all
works. Can we complete the call if something fails?

-Marc Linsner-

-----Original Message-----
From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
Sent: Tuesday, April 02, 2002 9:12 AM
To: Andrew Daviel
Cc: Rosen, Brian; geopriv@mail.apps.ietf.org
Subject: Re: crypto delay (Notes from Non-meeting)

I don't see how caller authentication has anything to do with geo-priv.
Authenticating a location is going to be almost impossible unless you
rely on a trusted intermediary to provide the location. For PDAs with
GPS, that doesn't work. The best you can do is have the originator sign
the request and then later prosecute them. That is, if you can
realistically track random.name@hotmail.com.

Also, while dispatch times are important, in many cases the important
delay is time to answer, so that the emergency call center can, for
example, provide instructions on CPR or other first-aid advice.

> that fast, in any case. A few seconds taken to authenticate a location
> and reduce the incidence of false alarms is going to save time and lives
> in the long run.
> There is perhaps an issue if the caller believes the equipment is broken
> and tries to reconnect, or abandons it altogether. This might be obviated
> by some display or audible feedback of call/authentication progress.
>
> --
> Andrew Daviel
Received on Tue Apr 2 09:39:32 2002