[Sipping-emergency] The Real Emergency Calling Scenarios To Look At
Tom Taylor <taylor@nortelnetworks.com> Fri, 13 June 2003 16:58 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 MAA12446
for <sipping-emergency-archive@odin.ietf.org>;
Fri, 13 Jun 2003 12:58:31 -0400 (EDT)
Received: (from mailnull@localhost)
by www1.ietf.org (8.11.6/8.11.6) id h5DGw4302131
for sipping-emergency-archive@odin.ietf.org; Fri, 13 Jun 2003 12:58:04 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DGw3m02091
for <sipping-emergency-web-archive@optimus.ietf.org>;
Fri, 13 Jun 2003 12:58:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12230
for <sipping-emergency-web-archive@ietf.org>;
Fri, 13 Jun 2003 12:57:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 19QrqC-0006kn-00
for sipping-emergency-web-archive@ietf.org; Fri, 13 Jun 2003 12:55:52 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
by ietf-mx with esmtp (Exim 4.12) id 19QrqB-0006kk-00
for sipping-emergency-web-archive@ietf.org; Fri, 13 Jun 2003 12:55:51 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DDc0a11601
for <sipping-emergency-web-archive@ietf.org>; Fri, 13 Jun 2003 09:38:00 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DDb1m10664
for <sipping-emergency@optimus.ietf.org>; Fri, 13 Jun 2003 09:37:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04366
for <sipping-emergency@ietf.org>; Fri, 13 Jun 2003 09:36:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 19Qohe-0005A7-00
for sipping-emergency@ietf.org; Fri, 13 Jun 2003 09:34:50 -0400
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
by ietf-mx with esmtp (Exim 4.12) id 19Qohd-00059S-00
for sipping-emergency@ietf.org; Fri, 13 Jun 2003 09:34:50 -0400
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
ESMTP id h5DDaKU18450; Fri, 13 Jun 2003 09:36:20 -0400 (EDT)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by
zcard309.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service
Version 5.5.2653.13) id KRLG1K22; Fri, 13 Jun 2003 09:36:20 -0400
Received: from nortelnetworks.com (acart1d8.ca.nortel.com [47.129.129.84]) by
zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service
Version 5.5.2653.13) id JQNA0TMM; Fri, 13 Jun 2003 09:36:20 -0400
Message-ID: <3EE9D34F.7020608@nortelnetworks.com>
Date: Fri, 13 Jun 2003 09:36:15 -0400
X-Sybari-Space: 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:1.4b) Gecko/20030507
X-Accept-Language: en-ca, en-us, en, fr
MIME-Version: 1.0
To: sipping-emergency@ietf.org, Patrick.Emery@aca.gov.au,
dick.rr.knight@bt.com, steve.norreys@bt.com
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping-emergency] The Real Emergency Calling Scenarios To Look At
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 dealt too lightly with Henning's remark on the optionality of proxies in my previous message. Obviously I had to follow through and consider the effect on each scenario. This got me thinking about the real variables of interest, which is probably the point of the whole exercise. It seems to me the key variables are these: (1) Whether the SIP phone is being used in stationary, nomadic, or mobile mode (with the latter still being out of scope?). Stationary usage implies that information on location and call-back addressing can be lodged in a network database in advance of the emergency call. (2) Whether there is a proxy in the signalling path, or the SIP phone signals directly to a PSTN gateway. A proxy provides the opportunity for gateway selection if location information is available. (3) Whether the SIP phone can reach a PSTN gateway which in turn can reach the ECC in jurisdiction. (4) Whether there is an opportunity to pull together information about the SIP phone's physical location (in the case of Wi-Fi or LAN access) or at least the calling number (for dial-up access), correlate it with the caller's contact information, and use the results to provide necessary data to the PSTN gateway. People can think about this list and consider whether I have it right. My problem now is what this does to the scenarios document. I'll have to think through how many independent scenarios we really have taking account of the above variables, and whether they are close enough to the ones already in the document. In any event, a list like the one above should appear in a Conclusions section, along with the implications for possible solutions. Tom _______________________________________________ Sipping-emergency mailing list Sipping-emergency@ietf.org https://www1.ietf.org/mailman/listinfo/sipping-emergency