IETF Logo Mail Archive

Re: [Ieprep] Comment for WG Last Call on draft-ietf-ieprep-sip-reqs-01.txt

Henning Schulzrinne <hgs@cs.columbia.edu> Wed, 06 November 2002 22:00 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 RAA14544 for <ieprep-archive@odin.ietf.org>; Wed, 6 Nov 2002 17:00:25 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gA6M2To15658 for ieprep-archive@odin.ietf.org; Wed, 6 Nov 2002 17:02:29 -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 gA6M2Tv15655 for <ieprep-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 17:02:29 -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 QAA14514 for <ieprep-web-archive@ietf.org>; Wed, 6 Nov 2002 16:59:54 -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 gA6M1Gv15551; Wed, 6 Nov 2002 17:01:16 -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 gA6M0sv15379 for <ieprep@optimus.ietf.org>; Wed, 6 Nov 2002 17:00:54 -0500
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14457 for <ieprep@ietf.org>; Wed, 6 Nov 2002 16:58:19 -0500 (EST)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100]) by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gA6M0cm6015645; Wed, 6 Nov 2002 17:00:38 -0500 (EST)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66]) (authenticated bits=0) by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id gA6M0aH9007821 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 6 Nov 2002 17:00:37 -0500 (EST)
Message-ID: <3DC9915B.5000706@cs.columbia.edu>
Date: Wed, 06 Nov 2002 17:02:03 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ottensmeyer Joerg <joerg.ottensmeyer@siemens.com>
CC: "Ieprep (E-mail)" <ieprep@ietf.org>
Subject: Re: [Ieprep] Comment for WG Last Call on draft-ietf-ieprep-sip-reqs-01.txt
References: <47D438A0510BD611B9470002A58EDAE7AD2B9B@mchh2a6e.mchh.siemens.de>
In-Reply-To: <47D438A0510BD611B9470002A58EDAE7AD2B9B@mchh2a6e.mchh.siemens.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Since charter discussions seem all the rage these days, it might be 
worth noting that we have, I believe, several times reached the 
conclusion that 911/112-style calls are out of scope. However, I've been 
working on this very topic for a while. You can find a detailed 
description of the issues in the draft draft-schulzrinne-sipping-sos-02 
and draft-ietf-sip-emergency-00. (If they are expired, you can find them 
at http://www.cs.columbia.edu/sip/drafts/).

We have been building a system locally that solves the first of the 
problem you list below. The second and third appear to be operational 
ones that does not seem to require any additional protocol capabilities. 
With the *sos* draft, a proxy can detect that the call is destined for a 
PSAP and thus modify normal AAA procedures and elevate call priority 
should local operating procedures call for that.

A number of BOFs have been held under the auspices of the SIP(PING) 
working group, but not enough people seem to care about this topic, so 
it seems to always be displaced by more urgent things like ISUP 
interworking :-)

I'll be glad to get into more details, but my interpretation is that at 
least the first two issues are considered out of scope of IEPREP.

Ottensmeyer Joerg wrote:

> Dear all,
>
>
> - for this service, the SIP server needs be able to resolve the dialed 
> URI (e.g. sip:ambulance@closest) to the address of the nearest 
> Emergency Response Center.
> - it must be possible to place this call must from all SIP phones and 
> the user does not need to be authenticated or even not registered.
> - then, the call must be able to receive the same priority levels as 
> the other emergency calls to ensure that the call is processed in the 
> SIP proxies and servers when a "catastrophe level" is activated, i.e. 
> the overall service has to be restricted.
>
> I feel, that those requirements have to be reflected somehow in the 
> document under last call.
>
> best regards
> -Jörg
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep

v2.23.0 | Report a Bug | By Email