Re: [Ecrit] draft review <draft-schulzrinne-sipping-emergency-req-01.txt>
Henning Schulzrinne <hgs@cs.columbia.edu> Sun, 06 March 2005 01:26 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 UAA04334; Sat, 5 Mar 2005 20:26:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D7kZ8-0000gJ-Kj; Sat, 05 Mar 2005 20:28:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D7kWJ-0006sz-De; Sat, 05 Mar 2005 20:25:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D7kWI-0006su-Gv for ecrit@megatron.ietf.org; Sat, 05 Mar 2005 20:25:22 -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 UAA04295 for <ecrit@ietf.org>; Sat, 5 Mar 2005 20:25:20 -0500 (EST)
Received: from opus.cs.columbia.edu ([128.59.20.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D7kYB-0000fp-27 for ecrit@ietf.org; Sat, 05 Mar 2005 20:27:19 -0500
Received: from [127.0.0.1] (IDENT:U2FsdGVkX1+pkpqbzyb+WjOXB8bHTT6i/g55r3MDAkY@razor.cs.columbia.edu [128.59.16.8]) (authenticated bits=0) by opus.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id j261PHh3018737 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 5 Mar 2005 20:25:18 -0500 (EST)
Message-ID: <422A5BF1.9090809@cs.columbia.edu>
Date: Sat, 05 Mar 2005 20:25:05 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tschofenig Hannes <hannes.tschofenig@siemens.com>
Subject: Re: [Ecrit] draft review <draft-schulzrinne-sipping-emergency-req-01.txt>
References: <D2E490BD3F24C24598C4605E40024D15188E1C@mchp9gma.mch.sbs.de>
In-Reply-To: <D2E490BD3F24C24598C4605E40024D15188E1C@mchp9gma.mch.sbs.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: 7bit
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: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
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] draft review <draft-schulzrinne-sipping-e… Tschofenig Hannes
- Re: [Ecrit] draft review <draft-schulzrinne-sippi… Henning Schulzrinne