[clouds] What are we doing here?

Nathaniel Borenstein <nsb@guppylake.com> Mon, 02 August 2010 01:00 UTC

Return-Path: <nsb@guppylake.com>
X-Original-To: clouds@core3.amsl.com
Delivered-To: clouds@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 2FA483A68F8 for <clouds@core3.amsl.com>; Sun, 1 Aug 2010 18:00:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id JdxfzXEXvLgk for <clouds@core3.amsl.com>; Sun, 1 Aug 2010 18:00:56 -0700 (PDT)
Received: from server1.netnutz.com (server1.netnutz.com []) by core3.amsl.com (Postfix) with ESMTP id 3BAA33A68F1 for <clouds@ietf.org>; Sun, 1 Aug 2010 18:00:56 -0700 (PDT)
Received: from c-67-173-1-117.hsd1.il.comcast.net ([] helo=[]) by server1.netnutz.com with esmtpa (Exim 4.69) (envelope-from <nsb@guppylake.com>) id 1Ofjaq-0003Wv-Hy; Sun, 01 Aug 2010 21:13:28 -0400
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <FEB225C5-6C8C-4ACC-9589-8A5F2505706B@unbehagen.net>
Date: Sun, 1 Aug 2010 20:01:18 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <37FB9B36-E555-46C4-8B66-BD635B3445B4@guppylake.com>
References: <AANLkTinvqsPzwBDxrj74RXpys21x2BRmJFBcoc8vbRhW@mail.gmail.com> <294030129BF751408412C35312657D974E7991B241@qtdenexmbm21.AD.QINTRA.COM> <AANLkTinW9dXdbArLGp2oKRt3QbzHhLL+zm=TdaQK-cCE@mail.gmail.com> <25C3B27C-5DF8-4855-A272-BD10591F6B6F@unbehagen.net> <AANLkTi=ap4AbXYKq_3ZDqyKR7JOzcx8j9EoLpRqoNxnG@mail.gmail.com> <FEB225C5-6C8C-4ACC-9589-8A5F2505706B@unbehagen.net>
To: Paul Unbehagen <paul@unbehagen.net>
X-Mailer: Apple Mail (2.1081)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server1.netnutz.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - guppylake.com
Cc: Sam Johnston <sj@google.com>, "clouds@ietf.org" <clouds@ietf.org>, "Fargano, Michael" <Michael.Fargano@qwest.com>
Subject: [clouds] What are we doing here?
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, 02 Aug 2010 01:00:57 -0000

I missed the BoF, so please excuse me if this is clear to everyone but me, however...

What are we trying to accomplish?

Standards efforts tend to be most successful if there are clear goals in mind.  What I'm seeing is a bunch of people who are excited about the general idea of cloud standards, each with a few particular ideas in mind.  Things like reference architectures can be very useful in the context of a well-developed set of technologies and goals -- Dave Crocker's email architecture document comes to mind.  But they don't do much to help focus on goals in the way that is  almost a prerequisite to a successful WG.

So, I suggest that in the interest of getting somewhere, we might think about the kind of goals suitable for WG creation.  Examples of such goals might be:

-- Making X portable across cloud vendors, where X might be virtual machines, storage grids, email archives, etc.

-- Enhancing security of cloud services by doing Y, where Y might be enhancements to authentication, specification of best practices, etc.  

-- Standardizing interface Z,  where Z might be video streaming, VPN extensions, etc.

I think there are enough goals here for a dozen WG's, but probably not enough people.  Is there a goal or two that enough of us share to give us critical mass?

For my part, I'm most enthused about the first category of goals -- standards to ensure that users aren't locked in to a single vendor.   What are other folks enthused about?  -- Nathaniel