Re: [clouds] __答复:_scope_of_the_cloud

Sam Johnston <sjj@google.com> Fri, 09 April 2010 12:23 UTC

Return-Path: <sjj@google.com>
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 EE0843A6A2B for <clouds@core3.amsl.com>; Fri, 9 Apr 2010 05:23:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.654
X-Spam-Level:
X-Spam-Status: No, score=-101.654 tagged_above=-999 required=5 tests=[AWL=2.870, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_BACKHAIR_54=1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_UTF8=0.152, USER_IN_WHITELIST=-100]
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 U+D8FZYIblNz for <clouds@core3.amsl.com>; Fri, 9 Apr 2010 05:23:48 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 6B97C3A6A2D for <clouds@ietf.org>; Fri, 9 Apr 2010 05:23:42 -0700 (PDT)
Received: from wpaz13.hot.corp.google.com (wpaz13.hot.corp.google.com [172.24.198.77]) by smtp-out.google.com with ESMTP id o39CNawb022146 for <clouds@ietf.org>; Fri, 9 Apr 2010 05:23:36 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1270815816; bh=SaLmY5YfCt5Q/Mf0EY7Erk7OYqU=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=Nmp9UAZVuJbEnA3CFSAla/2pm7WmbcpHzI90MFeO+UvpZeZpFTbhJvzRRcz+RICkz rIPTXeyhweBfzANIF/zrg==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=tgRMINvQeX8ElcH7pf+6i4X0YBBZKdsesBkQCHvBoM8Nx/ynxzUgECpJLF5w8sfVH fAECxiwPf/c/N2OjhwKhA==
Received: from bwz1 (bwz1.prod.google.com [10.188.26.1]) by wpaz13.hot.corp.google.com with ESMTP id o39CNFBD022722 for <clouds@ietf.org>; Fri, 9 Apr 2010 05:23:35 -0700
Received: by bwz1 with SMTP id 1so2462897bwz.1 for <clouds@ietf.org>; Fri, 09 Apr 2010 05:23:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.204.150.67 with HTTP; Fri, 9 Apr 2010 05:23:34 -0700 (PDT)
In-Reply-To: <t2wa065968d1004090516m6a7326e2xac25d6397ca55c38@mail.gmail.com>
References: <201004091421281408197@chinamobile.com> <OF97A02D2D.F12C57AA-ON48257700.0025B7E9-48257700.00267C69@zte.com.cn> <i2kda8464b11004090045scff74af9qd5a43fde4cc2df31@mail.gmail.com> <201004091607326563002@chinamobile.com> <w2o460b71b91004090146te13e3415y72f3d870b3de408b@mail.gmail.com> <C6A1D07CACFDBD4D9422C7D7ED288D410418B5B080@34093-MBX-C01.mex07a.mlsrvr.com> <t2wa065968d1004090516m6a7326e2xac25d6397ca55c38@mail.gmail.com>
Date: Fri, 9 Apr 2010 14:23:34 +0200
Received: by 10.204.19.137 with SMTP id a9mr20745bkb.24.1270815814564; Fri, 09 Apr 2010 05:23:34 -0700 (PDT)
Message-ID: <j2w460b71b91004090523s16f14092kb77fba9213394fb5@mail.gmail.com>
From: Sam Johnston <sjj@google.com>
To: Bhumip Khasnabish <vumip1@gmail.com>
Content-Type: multipart/alternative; boundary=0003255549fa33bc080483ccddb5
X-System-Of-Record: true
Cc: "clouds@ietf.org" <clouds@ietf.org>
Subject: Re: [clouds] =?utf-8?b?X1/nrZTlpI06X3Njb3BlX29mX3RoZV9jbG91ZA==?=
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: Fri, 09 Apr 2010 12:23:51 -0000

On 9 April 2010 14:16, Bhumip Khasnabish <vumip1@gmail.com> wrote:

> Yes, in progress, and doing this. Plan to publish this soon (may wait a few
> more days just to see whether we see any more new comments and/or
> suggestions). Thanks.
>

Let me add another to the list then - AAA. Examples include OAuth Web
Resource Authorization Profiles
(draft-hardt-oauth<http://tools.ietf.org/html/draft-hardt-oauth>)h>),
which is already in the IETF pipeline even if OAuth itself is not, and our
new IMAP and SMTP authentication using
OAuth<http://code.google.com/apis/gmail/oauth/>spect;spec, which is not.

Sam

2010/4/9 Gene Golovinsky <gene@alertlogic.com>
>
>>   We're also missing a way of describing containers (e.g. hypervisors,
>> platforms, etc.) and workloads (e.g. applications, virtual machines).
>> CloudAudit provides a technical solution to the former (but it's out of
>> scope) and Cisco's James Urquhart has been working on a descriptor format
>> for the latter[2]. Both of these areas seem appropriate for IETF
>> involvement, and indeed CloudAudit could be worked into a generic catalog
>> service (e.g. the legal name of the provider, its location, logo, services,
>> SLAs, etc.).
>>
>> *[Gene>] I fully agree with that*
>>
>>
>>
>> I think the best next step would be for to work torwards formalising the
>> "clouds" effort somewhat, which will necessarily involve enumerating the
>> opportunities for standards development and prioritising them. IETF-78 would
>> presumably be a good forum for this activity (assuming it can't be done more
>> inclusively on this mailing list).
>>
>> *[Gene>] In one of the previous e-mails to the list Bhumip has outlined
>> areas of Cloud related interests. Then we had a discussion on the list where
>> people expressed their preferences, suggestions and disagreements. Bhumip,
>> since you were already doing this, would you please recap the list taking
>> all that into account?*
>>
>> * *
>>
>> *Cheers.*
>>
>> *--Gene*
>>
>>
>>
>>
>>
>> _______________________________________________
>> clouds mailing list
>> clouds@ietf.org
>> https://www.ietf.org/mailman/listinfo/clouds
>>
>>
>
>
> --
> Best Regards.
>
> Bhumip Khasnabish (Mobile:+001-781-752-8003, bhumip@acm.org)
>
> © 2010 Bhumip Khasnabish. Do not view, print, forward, and save the content
> of this email if you are not the intended recipient of the communiqué.
>