IETF Logo Mail Archive

Re: [clouds] CloudApps BoF (IETF-80) proposal for your review andcomments

"Natale, Bob" <RNATALE@mitre.org> Mon, 31 January 2011 22:22 UTC

Return-Path: <RNATALE@mitre.org>
X-Original-To: clouds@core3.amsl.com
Delivered-To: clouds@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB5103A688A for <clouds@core3.amsl.com>; Mon, 31 Jan 2011 14:22:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level:
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bk4hzZLGoYhz for <clouds@core3.amsl.com>; Mon, 31 Jan 2011 14:22:31 -0800 (PST)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by core3.amsl.com (Postfix) with ESMTP id 367803A67F7 for <clouds@ietf.org>; Mon, 31 Jan 2011 14:22:31 -0800 (PST)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id BEE8321B0BD1; Mon, 31 Jan 2011 17:25:45 -0500 (EST)
Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtpksrv1.mitre.org (Postfix) with ESMTP id BA0C021B0BD7; Mon, 31 Jan 2011 17:25:45 -0500 (EST)
Received: from IMCMBX2.MITRE.ORG ([129.83.29.209]) by imchub1.MITRE.ORG ([129.83.29.73]) with mapi; Mon, 31 Jan 2011 17:22:55 -0500
From: "Natale, Bob" <RNATALE@mitre.org>
To: Spencer Dawkins <spencer@wonderhamster.org>
Date: Mon, 31 Jan 2011 17:22:54 -0500
Thread-Topic: [clouds] CloudApps BoF (IETF-80) proposal for your review andcomments
Thread-Index: AcvBj1PeUEfc019RRfGh/Ucb5HJjvwABOPBA
Message-ID: <17969D855F28964C88D177D45B6CDF1105093E3A05@IMCMBX2.MITRE.ORG>
References: <AANLkTi=Qm3rSzkx4uoNt7XL2999DotMpC0+LAaKoDpZi@mail.gmail.com><4D47015E.1010905@stpeter.im> <AANLkTikgt5Mw1d-b2Eo5LEq7sS54L3vn-Ahx3gsUijRo@mail.gmail.com> <09EAD7529B674CEFB193CFCF0D738A66@china.huawei.com>
In-Reply-To: <09EAD7529B674CEFB193CFCF0D738A66@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "clouds@ietf.org" <clouds@ietf.org>
Subject: Re: [clouds] CloudApps BoF (IETF-80) proposal for your review andcomments
X-BeenThere: clouds@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Clouds pre-BOF discussion list <clouds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/clouds>, <mailto:clouds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clouds>
List-Post: <mailto:clouds@ietf.org>
List-Help: <mailto:clouds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clouds>, <mailto:clouds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jan 2011 22:22:32 -0000

Hi Spencer,

I'd like to think that the intent of your last phrase -- "but do as little as possible" -- was actually "but do only as much as necessary" ...? and I have no problem with pointers to other sources who have already specified use cases, requirements, test cases, etc. ... no need for duplicate text (verbatim or generally) ... but any development effort should document cognizance of the requirements it intends to satisfy (IMHO).

Cheers,
BobN

-----Original Message-----
From: clouds-bounces@ietf.org [mailto:clouds-bounces@ietf.org] On Behalf Of Spencer Dawkins
Sent: Monday, January 31, 2011 4:39 PM
To: Vishwas Manral; Peter Saint-Andre
Cc: clouds@ietf.org
Subject: Re: [clouds] CloudApps BoF (IETF-80) proposal for your review andcomments

Vishwas,

> Hi Peter,
>
> I would not totally agree. For nearly every new protocol developed,
> that I have worked on there has been seperate  requirement documents,
> use cases as well as protocol extension documents

While I would not dream of identifying the person who said it, I was told at 
IETF 51 in London that the reason so many groups were being chartered to 
produce use cases and requirements documents was to slow groups of new IETF 
participants down long enough for leadership to figure out what on earth 
they were talking about :p

I agree with Peter that IETF does less use cases/requirements work than most 
SDOs. My suggestion is that you may need to do this work, in this specific 
case, but do as little as possible.

Thanks,

Spencer 

_______________________________________________
clouds mailing list
clouds@ietf.org
https://www.ietf.org/mailman/listinfo/clouds

v2.23.0 | Report a Bug | By Email