Re: [Ieprep] comments on draft-schulzrinne-ieprep-resource-req
Ken Carlberg <K.Carlberg@cs.ucl.ac.uk> Sun, 30 June 2002 10:31 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27546 for <ieprep-archive@odin.ietf.org>; Sun, 30 Jun 2002 06:31:20 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA19266; Sun, 30 Jun 2002 06:29:20 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA19234 for <ieprep@optimus.ietf.org>; Sun, 30 Jun 2002 06:29:19 -0400 (EDT)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA27476 for <ieprep@ietf.org>; Sun, 30 Jun 2002 06:28:31 -0400 (EDT)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id <g.08343-0@bells.cs.ucl.ac.uk>; Sun, 30 Jun 2002 11:29:06 +0100
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #25[UCI]
To: Rohan Mahy <rohan@cisco.com>
cc: ieprep@ietf.org, hgs@cs.columbia.edu
Subject: Re: [Ieprep] comments on draft-schulzrinne-ieprep-resource-req
In-reply-to: Your message of "Fri, 28 Jun 2002 12:23:10 PDT." <7B97EE5E-8ACC-11D6-BA11-0003938AF740@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Sun, 30 Jun 2002 11:29:04 +0100
Message-ID: <13214.1025432944@cs.ucl.ac.uk>
From: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
Sender: ieprep-admin@ietf.org
Errors-To: ieprep-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
X-BeenThere: ieprep@ietf.org
> -Also, I think that the requirement implied in number 3 is cumbersome > and poorly stated. > what is the requirement here? is this a requirement that session setup > via SIP may need appropriate QoS marked or requested? if it is, say so > directly. as I read the draft, items 1 through 4 of the Introduction seemed more aimed at providing motivation for the R-P mechanism, as opposed to requirements. after points 1-4, actual requirements are stated. one thing that may help is to divide the Intro section into two parts: 1. Introduction, and 2. Requirements > - the security requirements are WAY underspecified. would it be possible to simply point to Ian Brown's draft <draft-ietf-ieprep-security-01.txt> and expand it if necessary to address the security concerns you may have? my personal view is that I would be a bit weary of placing a lot of security work in a requirements doc for a labeling mechanism. mind you, I'm not saying that security is a non-issue (actually, its quite critical). but I think because we have a number of drafts that need to address the subject, it would be easier to have consensus on a single document as opposed to trying to replicate in detail security requirements/issues in each and every document. my 2 cents, -ken _______________________________________________ Ieprep mailing list Ieprep@ietf.org https://www1.ietf.org/mailman/listinfo/ieprep
- [Ieprep] comments on draft-schulzrinne-ieprep-res… Rohan Mahy
- Re: [Ieprep] comments on draft-schulzrinne-ieprep… Ken Carlberg
- Re: [Ieprep] comments on draft-schulzrinne-ieprep… Stuart (Stu) Goldman
- Re: [Ieprep] comments on draft-schulzrinne-ieprep… James M. Polk