Re: [Sipping-emergency] Re: Emergency-req: 8-12

Henning Schulzrinne <hgs@cs.columbia.edu> Mon, 24 February 2003 14:47 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15551 for <sipping-emergency-archive@odin.ietf.org>; Mon, 24 Feb 2003 09:47:30 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1OEu4c29987 for sipping-emergency-archive@odin.ietf.org; Mon, 24 Feb 2003 09:56:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OEu4p29984 for <sipping-emergency-web-archive@optimus.ietf.org>; Mon, 24 Feb 2003 09:56:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15542 for <sipping-emergency-web-archive@ietf.org>; Mon, 24 Feb 2003 09:46:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OEu3p29976 for <sipping-emergency-web-archive@ietf.org>; Mon, 24 Feb 2003 09:56:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1OEsxp29832 for <sipping-emergency@optimus.ietf.org>; Mon, 24 Feb 2003 09:54:59 -0500
Received: from dewberry.cc.columbia.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15524 for <sipping-emergency@ietf.org>; Mon, 24 Feb 2003 09:45:54 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66]) (user=hgs10 mech=PLAIN bits=0) by dewberry.cc.columbia.edu (8.12.3/8.12.3) with ESMTP id h1OEnixw022663 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 24 Feb 2003 09:49:46 -0500 (EST)
Message-ID: <3E5A3123.3070502@cs.columbia.edu>
Date: Mon, 24 Feb 2003 09:50:11 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "King, Kimberly S." <KIMBERLY.S.KING@saic.com>
CC: sipping-emergency@ietf.org
Subject: Re: [Sipping-emergency] Re: Emergency-req: 8-12
References: <B8030EB94AF1D51196D70002A589D64207E77CD3@mcl-its-exs01.mail.saic.com>
In-Reply-To: <B8030EB94AF1D51196D70002A589D64207E77CD3@mcl-its-exs01.mail.saic.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-emergency-admin@ietf.org
Errors-To: sipping-emergency-admin@ietf.org
X-BeenThere: sipping-emergency@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>, <mailto:sipping-emergency-request@ietf.org?subject=unsubscribe>
List-Id: <sipping-emergency.ietf.org>
List-Post: <mailto:sipping-emergency@ietf.org>
List-Help: <mailto:sipping-emergency-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping-emergency>, <mailto:sipping-emergency-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> I'm getting lost in what is the context.  It looks to me like there are
> three cases.
> 
> a) someone uses IP-based phone or IM to call for help (sos/911) and this
> hits a gateway (either regular IP-PSTN gateway or IP to text messaging
> (e.g., SMS).  What is required in this case?

I was trying to avoid getting into the details of how the current system 
works and (more importantly) the properties it has, but maybe that's a 
bad idea.

The case you describe has two important sub-cases:

(1) The gateway is in the same town as the caller. (I'll say 'town' for 
simplicity; I mean 'same ECC serving area', but that's much longer...). 
In that case, the call reaches the right ECC. A problem arises if the 
phone has no E.164 phone number in the ECC calling area.

As an example, if I take my Vonage/Denwa phone from New York to 
Lexington, I might configure the right local Lexington, KY gateway, but 
the poor PSAP will see a 212 phone number and have no clue where I am or 
who I am.

(2) The gateway is in a different town. Since there are 5000 PSAPs in 
the US and it is unlikely that most service providers would use nearly 
that many gateways, this is a likely scenario. In addition to the 
problems in case (1), you are now connected to a gateway in the wrong 
city. Thus, if the Vonage gateway is in New York, my Lexington emergency 
call will reach the NYPD, which isn't going to be too helpful. I suspect 
that the New York 911 call taker things that I'm nuts if I tell them 
that the accident is a 1000 miles away.

This is described without example and more tersely in the section 
'Identifying the Appropriate Emergency Call Center'.

Would it be helpful to write it up at this level?


> b) someone uses IP-based phone or IM to call for help (sos/911) and this
> goes end-to-end IP.  (It appears to me that it might not be detectable to
> the caller whether a gateway will intervene so perhaps what is required
> should be the same as case a).)

This is indeed somewhat similar. The location problem is easier, since 
the caller could route the call to the right ECC.

> c) the receiving center is IP-based but calls come in from the PSTN.
> 
> Have I got this correct?
> 
> Now, if so, isn't this simple?  What is needed?  location information?
> time-stamps? some assuredness that the message is authentic?  ?

The primary problem, as alluded to in the beginning of the end-to-end 
section, is getting the call to the right PSAP/ECC. That's a fundamental 
requirement - you're not going to get useful emergency service 
otherwise. A secondary requirement is that the ECC gets location and 
other information (hazardous materials at your place, etc.). That's a 
longer-term issue, since *current* wireless systems don't deliver that, 
either. (They will, in the next few years.)

> 
> When I try to read the draft, I don't get it in clear language what is
> needed but my feelings are that it shouldn't be that complicated.  What am I
> missing?

In my view, this isn't complicated once you get down to the details.

Henning



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