Re: [Ieprep] SIP requirements draft after WG last call
Allison Mankin <mankin@psg.com> Sat, 11 January 2003 02:06 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 VAA22514 for <ieprep-archive@odin.ietf.org>; Fri, 10 Jan 2003 21:06:41 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0B2J8x13648 for ieprep-archive@odin.ietf.org; Fri, 10 Jan 2003 21:19:08 -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 h0B2J8J13645 for <ieprep-web-archive@optimus.ietf.org>; Fri, 10 Jan 2003 21:19:08 -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 VAA22502 for <ieprep-web-archive@ietf.org>; Fri, 10 Jan 2003 21:06:10 -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 h0B2HUJ13600; Fri, 10 Jan 2003 21:17:30 -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 h0ALaYJ30625 for <ieprep@optimus.ietf.org>; Fri, 10 Jan 2003 16:36:34 -0500
Received: from psg.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16771 for <ieprep@ietf.org>; Fri, 10 Jan 2003 16:23:41 -0500 (EST)
Received: from localhost ([127.0.0.1] helo=psg.com ident=mankin) by psg.com with esmtp (Exim 3.36 #2) id 18X6g3-0008CN-00; Fri, 10 Jan 2003 13:26:55 -0800
To: "King, Kimberly S." <KIMBERLY.S.KING@saic.com>
cc: "'ieprep@ietf.org'" <ieprep@ietf.org>
Subject: Re: [Ieprep] SIP requirements draft after WG last call
In-Reply-To: Message from "King, Kimberly S." <KIMBERLY.S.KING@saic.com> of "Mon, 02 Dec 2002 17:34:12 EST." <B8030EB94AF1D51196D70002A589D64207E779DA@mcl-its-exs01.mail.saic.com>
Date: Fri, 10 Jan 2003 13:26:55 -0800
From: Allison Mankin <mankin@psg.com>
Message-Id: <E18X6g3-0008CN-00@psg.com>
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>
Hi, Folks, We on the IESG approved draft-ietf-ietf-sip-reqs-03 during the IESG call on Thursday. I had some review issues with it that did not require holding it up, but which did result in the following RFC Editor note. You'll see this note in the announcement Monday: RFC Editor Note: Before REQ-1 insert the following paragraph: Note: not all the following requirements are possible to meet at once. They may represent in some cases tradeoffs that must be considered by the designer. I'm fairly confident that folks should be ok with the above. It was stimulated by conflict between the the requirement for proxy visibility (REQ-17) and confidentiality etc. (SEC-8 and SEC-9), one of the two issues I recorded in the id-tracker and passed on to the author but did not block the draft about. The other issue goes to the future work with the doc. The issue is realism about common expression of the emergency namespace/routing etc. Three requirements presented expectations of high understanding across heterogeneous domains (REQ-4, 5 and 7), and this struck me as a very high expectation, but now SIPPING can consider what technology supports the requirements. Anyway, good news, and thanks for the hard work! Allison _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep
- [Ieprep] SIP requirements draft after WG last call Henning Schulzrinne
- [Ieprep] SIP requirements draft after WG last call King, Kimberly S.
- Re: [Ieprep] SIP requirements draft after WG last… Allison Mankin