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

"James M. Polk" <jmpolk@cisco.com> Wed, 03 July 2002 20: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 QAA05318 for <ieprep-archive@odin.ietf.org>; Wed, 3 Jul 2002 16:31:41 -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 QAA12237; Wed, 3 Jul 2002 16:32:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA12207 for <ieprep@ns.ietf.org>; Wed, 3 Jul 2002 16:32:13 -0400 (EDT)
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05312 for <ieprep@ietf.org>; Wed, 3 Jul 2002 16:31:25 -0400 (EDT)
Received: from JMPOLK-W2K (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id NAA14782; Wed, 3 Jul 2002 13:31:08 -0700 (PDT)
Message-Id: <4.1.20020703152642.09f0b698@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Wed, 03 Jul 2002 15:31:02 -0500
To: goldmans@agcs.com, Ken Carlberg <K.Carlberg@cs.ucl.ac.uk>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Ieprep] comments on draft-schulzrinne-ieprep-resource-req
Cc: ieprep@ietf.org
In-Reply-To: <3D1F6B26.35EE57E9@agcs.com>
References: <13214.1025432944@cs.ucl.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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

At 01:33 PM 6/30/2002 -0700, Stuart (Stu) Goldman wrote:
>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.

I believe this can easily be referenced in the next rev of this ID, as well
the text separating the motivation for the RP Header mechanism (the
original request of the Chair and AD for this ID) from the requirement of
its usage within IEPREP - if this effort passes through the meat-grinder of
our upcoming Yokohama meeting on enough of a positive note     :-/

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


*************************************
"People generally demand more respect for their own rights than they are
willing to allow for others"

James M. Polk
Senior Consulting Engineer
Office of the CTO

Cisco Systems
2200 East President George Bush Turnpike 
Richardson, TX  75082 USA
w) 972.813.5208
f)  972.813.5280
www.cisco.com

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep