Re: [clouds] IETF-78 Cloud Standards BOF

"Edmonds, AndrewX" <andrewx.edmonds@intel.com> Wed, 28 July 2010 16:26 UTC

Return-Path: <andrewx.edmonds@intel.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 D0D0728C15E for <clouds@core3.amsl.com>; Wed, 28 Jul 2010 09:26:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 3HzU-fhg251Q for <clouds@core3.amsl.com>; Wed, 28 Jul 2010 09:25:53 -0700 (PDT)
Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by core3.amsl.com (Postfix) with ESMTP id 64F2F28C0CF for <clouds@ietf.org>; Wed, 28 Jul 2010 09:25:53 -0700 (PDT)
Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP; 28 Jul 2010 09:24:11 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos; i="4.55,275,1278313200"; d="scan'208,217"; a="590554577"
Received: from irsmsx601.ger.corp.intel.com ([163.33.7.164]) by fmsmga002.fm.intel.com with ESMTP; 28 Jul 2010 09:25:27 -0700
Received: from irsmsx501.ger.corp.intel.com (163.33.7.70) by irsmsx601.ger.corp.intel.com (163.33.7.164) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 28 Jul 2010 17:26:00 +0100
Received: from irsmsx502.ger.corp.intel.com ([163.33.7.249]) by irsmsx501.ger.corp.intel.com ([163.33.7.70]) with mapi; Wed, 28 Jul 2010 17:26:00 +0100
From: "Edmonds, AndrewX" <andrewx.edmonds@intel.com>
To: "Natale, Bob" <RNATALE@mitre.org>, "Monique Morrow (mmorrow)" <mmorrow@cisco.com>, Linda Dunbar <ldunbar@huawei.com>, "Chris Fenton (Iridescent)" <cfenton@iridescentnetworks.com>, "k.mcewen@verizon.net" <k.mcewen@verizon.net>
Date: Wed, 28 Jul 2010 17:23:38 +0100
Thread-Topic: [clouds] IETF-78 Cloud Standards BOF
Thread-Index: AcsuTL9mj8JJKN//Q4q9BVXc3kn9gAABABdyAAFdd5AAAwlLrQADCmFAAACJOFA=
Message-ID: <DAFA889EB3BE6243AEF55CFEE82D68A401BE3F3D4A@irsmsx502.ger.corp.intel.com>
References: <024501cb2e4c$c17f78e0$447e6aa0$@com> <317616CE96204D49B5A1811098BA8950027876F5@XMB-AMS-110.cisco.com> <011501cb2e57$9ab0c6a0$e9818182@china.huawei.com> <317616CE96204D49B5A1811098BA8950027876FC@XMB-AMS-110.cisco.com> <17969D855F28964C88D177D45B6CDF1104D3B7579D@IMCMBX2.MITRE.ORG>
In-Reply-To: <17969D855F28964C88D177D45B6CDF1104D3B7579D@IMCMBX2.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_DAFA889EB3BE6243AEF55CFEE82D68A401BE3F3D4Airsmsx502gerc_"
MIME-Version: 1.0
Cc: "clouds@ietf.org" <clouds@ietf.org>, "Craig.A.Lee@aero.org" <Craig.A.Lee@aero.org>
Subject: Re: [clouds] IETF-78 Cloud Standards BOF
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, 28 Jul 2010 16:26:02 -0000

Perhaps the cloud-standards.org forum could be a useful "rally" point and compliment this idea? I believe they hold bi-weekly co-ordination-type confcalls.

Andy

From: clouds-bounces@ietf.org [mailto:clouds-bounces@ietf.org] On Behalf Of Natale, Bob
Sent: Wednesday, July 28, 2010 7:13 PM
To: Monique Morrow (mmorrow); Linda Dunbar; Chris Fenton (Iridescent); k.mcewen@verizon.net
Cc: clouds@ietf.org
Subject: Re: [clouds] IETF-78 Cloud Standards BOF

Hi,

I think Linda's idea of having a single SDO - and the ITU-T works fine for me in this case - is a good one.

If the IETF endorses it, I could convey that message to the TM Forum Cloud Services Initiative as well.

Each such SDO that agrees with the approach would send a liaison message to the ITU-T Cloud group expressing agreement, stating the focus area(s) best assigned to that SDO (e.g., the IETF-based protocols mentioned by Monique below), identifying any scheduled near-term (1 yr or less?) deliverables in those areas, and soliciting future "assignments" (to be negotiated via open collaboration) from the ITU-T.  With the stipulation that the ITU-T Cloud effort must be open in terms of meetings, documents, and inputs at a minimum.  Or something like that...?

Cheers,
BobN

From: clouds-bounces@ietf.org [mailto:clouds-bounces@ietf.org] On Behalf Of Monique Morrow (mmorrow)
Sent: Wednesday, July 28, 2010 10:37 AM
To: Linda Dunbar; Chris Fenton (Iridescent); clouds@ietf.org
Cc: k.mcewen@verizon.net
Subject: Re: [clouds] IETF-78 Cloud Standards BOF


Linda

That is certainly an approach -- in addition to leveraging and developing IETF-based protocols as discussed today in some of the use cases presented.

Best -monique



-----Original Message-----
From: Linda Dunbar [mailto:ldunbar@huawei.com]
Sent: Wed 7/28/2010 6:20 AM
To: Monique Morrow (mmorrow); 'Chris Fenton (Iridescent)'; clouds@ietf.org
Cc: k.mcewen@verizon.net; 'Bhumip Khasnabish'
Subject: RE: [clouds] IETF-78 Cloud Standards BOF

It is very nice that Bhumip to create a bar BOF for interested parties to
present different aspects of Cloud.  As we can see that API and Cloud log
are very different from dynamic resource management, which is also different
from Private VPN. They need different expertise. People in Service layer may
think the network wiring too detail and trivial. People worrying about
network details view API as software features which can be application
specific.

Since ITU-T already starts the Cloud initiative, why not let ITU-T defines
the general framework for Cloud and come to IETF for specific problems?



Linda Dunbar



  _____

From: clouds-bounces@ietf.org [mailto:clouds-bounces@ietf.org] On Behalf Of
Monique Morrow (mmorrow)
Sent: Wednesday, July 28, 2010 7:31 AM
To: Chris Fenton (Iridescent); clouds@ietf.org
Cc: k.mcewen@verizon.net
Subject: Re: [clouds] IETF-78 Cloud Standards BOF



Chris

Do you proposed perhaps a framework draft as a starting point?

Monique





-----Original Message-----
From: Chris Fenton (Iridescent) [mailto:cfenton@iridescentnetworks.com]
Sent: Wed 7/28/2010 5:02 AM
To: clouds@ietf.org
Cc: k.mcewen@verizon.net
Subject: [clouds] IETF-78 Cloud Standards BOF

Hi all,

Thanks for interesting presentations.  To me the cloud without common or
option for a standardised interface/api is not a cloud its a set of service
platforms. We need to move forwards define the topic areas for
standardisation but essentially its all the elements you have for
subscribers to access a data platform from identity thru transport. Then
there are the service management aspects and the service provider
capabilities who want logs session or usage records and finally the platform
owner would need some or at least be able to support the above....

So possible topic areas for definition are :

Service user
- access
- transport
- service discovery maybe

Service provider
- Service management (also VM management - movement etc...)
- Subscription management
- charging billing etc...
- basically these are all FCAPS aspects Fault, Configuration, Accounting,
Performance, Security

Platform provider - not so sure what standards apply so long as the platform
itself provides the APis the boxes can be anything
- Management
- also FCAPS

CJ

Mr Chris Fenton
+44 7802 221 541
cfenton@iridescentnetworks.com
Skype: chrisfentouk
http://www.iridescentnetworks.com





-------------------------------------------------------------
Intel Ireland Limited (Branch)
Collinstown Industrial Park, Leixlip, County Kildare, Ireland
Registered Number: E902934

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.