Re: [clouds] __答复:_scope_of_the_cloud

"Krishna Sankar (ksankar)" <ksankar@cisco.com> Wed, 14 April 2010 12:55 UTC

Return-Path: <ksankar@cisco.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 0C3923A67FD for <clouds@core3.amsl.com>; Wed, 14 Apr 2010 05:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.146
X-Spam-Level:
X-Spam-Status: No, score=-10.146 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, SARE_SUB_ENC_UTF8=0.152]
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 TEsiq85fr6pJ for <clouds@core3.amsl.com>; Wed, 14 Apr 2010 05:55:43 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 06F5F3A6829 for <clouds@ietf.org>; Wed, 14 Apr 2010 05:53:52 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiQFAJVXxUurR7Ht/2dsb2JhbACBP4FVl21XcaMkiF6RD4JfgUBuBIMp
X-IronPort-AV: E=Sophos; i="4.52,204,1270425600"; d="scan'208,217"; a="115047706"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-4.cisco.com with ESMTP; 14 Apr 2010 12:53:46 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o3ECrkr7012065; Wed, 14 Apr 2010 12:53:46 GMT
Received: from xmb-sjc-219.amer.cisco.com ([171.70.151.188]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 14 Apr 2010 05:53:46 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CADBD1.84C7FB27"
Date: Wed, 14 Apr 2010 05:53:22 -0700
Message-ID: <9FA16888AD1BF64ABCE6C2532CCEB98A0A0785B8@xmb-sjc-219.amer.cisco.com>
In-Reply-To: <p2i460b71b91004140542w362755fdz90200ddafd8b7151@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [clouds] __答复:_scope_of_the_cloud
Thread-Index: Acrb0KJUf4PYGOUdQASLeteElhagsAAAIHMw
References: <201004091421281408197@chinamobile.com><OF97A02D2D.F12C57AA-ON48257700.0025B7E9-48257700.00267C69@zte.com.cn><i2kda8464b11004090045scff74af9qd5a43fde4cc2df31@mail.gmail.com><201004091607326563002@chinamobile.com><w2o460b71b91004090146te13e3415y72f3d870b3de408b@mail.gmail.com><92648F46-12F1-4CF8-BFD1-77E3E2DE4C15@cisco.com> <p2i460b71b91004140542w362755fdz90200ddafd8b7151@mail.gmail.com>
From: "Krishna Sankar (ksankar)" <ksankar@cisco.com>
To: Sam Johnston <sjj@google.com>, "Mark Webb (mwebb)" <mwebb@cisco.com>
X-OriginalArrivalTime: 14 Apr 2010 12:53:46.0193 (UTC) FILETIME=[85251C10:01CADBD1]
Cc: clouds@ietf.org
Subject: Re: [clouds] __答复:_scope_of_the_cloud
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: Wed, 14 Apr 2010 12:55:44 -0000

Eh ? Is there someplace a statement or an intention which says IETF will work only on “service like EC2” ? 

 

From: clouds-bounces@ietf.org [mailto:clouds-bounces@ietf.org] On Behalf Of Sam Johnston
Sent: Wednesday, April 14, 2010 5:43 AM
To: Mark Webb (mwebb)
Cc: clouds@ietf.org
Subject: Re: [clouds] __答复:_scope_of_the_cloud

 

On 13 April 2010 22:38, Mark Webb <mwebb@cisco.com> wrote:

	 

	On Apr 9, 2010, at 4:46 AM, Sam Johnston wrote:

		We're also missing a way of describing containers (e.g. hypervisors, platforms, etc.) and workloads (e.g. applications, virtual machines).

	I really think this is the realm of DMTF. They have a good start with OVF. There is more to do, (network, security and policy abstraction to name a couple) but it would be good for the industry if those container issues were mostly handled in this same place.

 

That may be true, but what IETF is renowned for is creating relatively tight, interoperable specifications for well defined/constrained problems. Others tend to want to boil oceans (e.g. OVF's normative reference to CIM), which may well be necessary to solve their problems (e.g. "private" cloud) but not ours (e.g. services like EC2).

 

Sam