RE: [Ecrit] draft review <draft-schulzrinne-sipping-emergency-req -01.txt>
"Abbott, Nadine B." <nabbott@telcordia.com> Mon, 07 March 2005 12:20 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06242; Mon, 7 Mar 2005 07:20:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D8HGG-0001CF-9K; Mon, 07 Mar 2005 07:23:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D8HDA-0003s0-1O; Mon, 07 Mar 2005 07:19:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D8HD8-0003rv-Cx for ecrit@megatron.ietf.org; Mon, 07 Mar 2005 07:19:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06091 for <ecrit@ietf.org>; Mon, 7 Mar 2005 07:19:43 -0500 (EST)
Received: from dnsmx1rrc.telcordia.com ([128.96.20.41]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D8HFJ-00019a-LG for ecrit@ietf.org; Mon, 07 Mar 2005 07:22:01 -0500
Received: from rrc-its-ieg01.cc.telcordia.com (rrc-its-ieg01.cc.telcordia.com [128.96.109.78]) by dnsmx1rrc.telcordia.com (8.11.7+Sun/8.9.3) with SMTP id j27CIn401384; Mon, 7 Mar 2005 07:18:49 -0500 (EST)
Received: from rrc-its-exbh01.mail.saic.com ([128.96.109.61]) by rrc-its-ieg01.cc.telcordia.com (SMSSMTP 4.0.5.66) with SMTP id M2005030707184615941 ; Mon, 07 Mar 2005 07:18:46 -0500
Received: by rrc-its-exbh01.mail.saic.com with Internet Mail Service (5.5.2657.72) id <FGDHPC4S>; Mon, 7 Mar 2005 07:18:46 -0500
Message-ID: <F0CB7F62D783BF40AD93882BB817F245023584BA@nvc-its-exs01.cc.telcordia.com>
From: "Abbott, Nadine B." <nabbott@telcordia.com>
To: 'Henning Schulzrinne' <hgs@cs.columbia.edu>, Tschofenig Hannes <hannes.tschofenig@siemens.com>
Subject: RE: [Ecrit] draft review <draft-schulzrinne-sipping-emergency-req -01.txt>
Date: Mon, 07 Mar 2005 07:18:46 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: "'ecrit@ietf.org'" <ecrit@ietf.org>
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ecrit.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
Sender: ecrit-bounces@ietf.org
Errors-To: ecrit-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
In addition, in North America, the term "Enhanced" is used to indicate that the emergency call is routed to an appropriate answering point based on the caller's location. Nadine -----Original Message----- From: ecrit-bounces@ietf.org [mailto:ecrit-bounces@ietf.org] On Behalf Of Henning Schulzrinne Sent: Saturday, March 05, 2005 8:25 PM To: Tschofenig Hannes Cc: 'ecrit@ietf.org' Subject: Re: [Ecrit] draft review <draft-schulzrinne-sipping-emergency-req-01.txt> Thanks for your comments. Some quick responses below: Enhanced emergency service: Enhanced emergency services add the ability to identify the caller identity and/or caller location to basic emergency services. (Sometimes, only the caller location may be known, e.g., from a public access point that is not owned by an individual.) [hannes] why is this differentiation necessary? Tschofenig Hannes wrote: > hi henning, > > i quickly read through your draft and here are a few high level comments: > * good document with an impressive list of requirements > (also addresses security specific requirements) > * i wonder whether the other draft authors have read this document. > it would be good to know how their requirements relate to the > requirements raised in this document. > > things to improve with this document: > * a few sections address topics that are outside the scope of ecrit Those will be deleted. > * terminology needs to be enhanced and fixed > * a number of security related requirements have been addressed in > the document but the > security consideration section requires more work > * some people might argue that the language in the document is a bit > too sip focused Well, this started as a SIPPING document... One high-level decision to be made is whether we assume that calls reach PSAPs via SIP, even if after translation. Clearly, some parts will be independent of the signaling protocol, but I don't think there's much point in having PSAPs support some smorgasbord of signaling protocols since that would only work if everybody supported everything. > > some some very minor comments at : > http://www.ietf-ecrit.org/comments/draft-schulzrinne-sipping-emergency > -req-0 > 1_hannes.txt > > ciao > hannes > > _______________________________________________ > Ecrit mailing list > Ecrit@ietf.org > https://www1.ietf.org/mailman/listinfo/ecrit _______________________________________________ Ecrit mailing list Ecrit@ietf.org https://www1.ietf.org/mailman/listinfo/ecrit _______________________________________________ Ecrit mailing list Ecrit@ietf.org https://www1.ietf.org/mailman/listinfo/ecrit
- RE: [Ecrit] draft review <draft-schulzrinne-sippiā¦ Abbott, Nadine B.