[Ieprep] sipping requirements
Scott Bradner <sob@harvard.edu> Mon, 14 October 2002 14: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 KAA20985 for <ieprep-archive@odin.ietf.org>; Mon, 14 Oct 2002 10:06:33 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9EE8E501862 for ieprep-archive@odin.ietf.org; Mon, 14 Oct 2002 10:08:14 -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 g9EE8Ev01859 for <ieprep-web-archive@optimus.ietf.org>; Mon, 14 Oct 2002 10:08:14 -0400
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 KAA20973 for <ieprep-web-archive@ietf.org>; Mon, 14 Oct 2002 10:06:03 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9EE79v01531; Mon, 14 Oct 2002 10:07:09 -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 g9EE6Kv01225 for <ieprep@optimus.ietf.org>; Mon, 14 Oct 2002 10:06:20 -0400
Received: from newdev.harvard.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20926 for <ieprep@ietf.org>; Mon, 14 Oct 2002 10:04:09 -0400 (EDT)
Received: (from sob@localhost) by newdev.harvard.edu (8.12.2/8.12.2) id g9EE5VxX013732 for ieprep@ietf.org; Mon, 14 Oct 2002 10:05:31 -0400 (EDT)
From: Scott Bradner <sob@harvard.edu>
Message-Id: <200210141405.g9EE5VxX013732@newdev.harvard.edu>
To: ieprep@ietf.org
Subject: [Ieprep] sipping requirements
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>
List-Archive: <https://www1.ietf.org/pipermail/ieprep/>
Date: Mon, 14 Oct 2002 10:05:31 -0400
Henning sez: > Just for clarification: the document that triggered this discussion was > the requirements document authored by myself, which is specifically > meant to be handed to the SIPPING WG and thus addresses SIP > specifically. (helping my co-chair focus discussion on this document) draft-ietf-ieprep-sip-reqs-00.txt lists quite a few REQs and SECs (security requirements) - Kimberly started a REQ-by-REQ discussion of them and the discussion has been generally useful but I'd also like to ask if *all* of the requiremnents (both REQ & SEC) are needed - requirements documents should have only the minimum set of requirements to ensure that the protocol does what it needs to do to support the desired functions and no more. in addition - there should be a discussion to see if there is WG consensus on sec 5 (network models) Scott _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep
- [Ieprep] sipping requirements Scott Bradner