Re: [clouds] IETF-78 Cloud Standards BOF

"Monique Morrow (mmorrow)" <mmorrow@cisco.com> Wed, 28 July 2010 14:41 UTC

Return-Path: <mmorrow@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 D789628C105 for <clouds@core3.amsl.com>; Wed, 28 Jul 2010 07:41:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.482
X-Spam-Level:
X-Spam-Status: No, score=-10.482 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 1ypU6l9GugXG for <clouds@core3.amsl.com>; Wed, 28 Jul 2010 07:40:59 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 9BD073A6949 for <clouds@ietf.org>; Wed, 28 Jul 2010 07:40:58 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAOPdT0xAZnwM/2dsb2JhbACfbXGmG5scgm+CRwSLLA
X-IronPort-AV: E=Sophos; i="4.55,274,1278288000"; d="scan'208,217"; a="140268176"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 28 Jul 2010 14:41:21 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o6SEfI42012963; Wed, 28 Jul 2010 14:41:21 GMT
Received: from xmb-ams-110.cisco.com ([144.254.74.85]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 28 Jul 2010 16:41:19 +0200
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_01CB2E62.F0A3436A"
Date: Wed, 28 Jul 2010 16:37:07 +0200
Message-ID: <317616CE96204D49B5A1811098BA8950027876FC@XMB-AMS-110.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [clouds] IETF-78 Cloud Standards BOF
Thread-Index: AcsuTL9mj8JJKN//Q4q9BVXc3kn9gAABABdyAAFdd5AAAwlLrQ==
References: <024501cb2e4c$c17f78e0$447e6aa0$@com> <317616CE96204D49B5A1811098BA8950027876F5@XMB-AMS-110.cisco.com> <011501cb2e57$9ab0c6a0$e9818182@china.huawei.com>
From: "Monique Morrow (mmorrow)" <mmorrow@cisco.com>
To: "Linda Dunbar" <ldunbar@huawei.com>, "Chris Fenton (Iridescent)" <cfenton@iridescentnetworks.com>, <clouds@ietf.org>
X-OriginalArrivalTime: 28 Jul 2010 14:41:19.0518 (UTC) FILETIME=[F1001BE0:01CB2E62]
Cc: k.mcewen@verizon.net
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 14:41:00 -0000

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