Re: [Ieprep] comments on draft-schulzrinne-ieprep-resource-req

"Stuart (Stu) Goldman" <goldmans@agcs.com> Sun, 30 June 2002 20:33 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 QAA10807 for <ieprep-archive@odin.ietf.org>; Sun, 30 Jun 2002 16:33:26 -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 QAA11371; Sun, 30 Jun 2002 16:33:33 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA11339 for <ieprep@optimus.ietf.org>; Sun, 30 Jun 2002 16:33:32 -0400 (EDT)
Received: from bootstrap.agcs.com (bootstrap.agcs.com [130.131.48.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10783 for <ieprep@ietf.org>; Sun, 30 Jun 2002 16:32:44 -0400 (EDT)
Received: from pxmail2.agcs.com (pxmail2.agcs.com [130.131.52.2]) by bootstrap.agcs.com (Pro-8.9.3/8.9.3) with ESMTP id NAA01682 for <ieprep@ietf.org>; Sun, 30 Jun 2002 13:33:30 -0700 (MST)
Received: from mkultra ([130.131.166.68]) by pxmail2.agcs.com (Netscape Messaging Server 4.15 pxmail2 Mar 5 2002 15:11:07) with SMTP id GYJD3T00.5JY for <ieprep@ietf.org>; Sun, 30 Jun 2002 13:33:29 -0700
Received: FROM agcs.com BY mkultra ; Sun Jun 30 13:33:26 2002 -0700
Message-ID: <3D1F6B26.35EE57E9@agcs.com>
Date: Sun, 30 Jun 2002 13:33:42 -0700
From: "Stuart (Stu) Goldman" <goldmans@agcs.com>
Reply-To: goldmans@agcs.com
Organization: AG Communication Systems
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
CC: ieprep@ietf.org
Subject: Re: [Ieprep] comments on draft-schulzrinne-ieprep-resource-req
References: <13214.1025432944@cs.ucl.ac.uk>
Content-Type: multipart/mixed; boundary="------------BD52BFF13C4F39D230B4AADE"
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

Ken,

You make an excellent point. If we were to attempt to replicate in
detail security requirements/issues in each and every document, it is likely
that the text would be slightly different as the security requirements
evolved. By pointing to a single source one avoids the unintended differences.

Ken Carlberg wrote:

> > -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