Re: [clouds] IETF-78 Cloud Standards BOF
"Natale, Bob" <RNATALE@mitre.org> Wed, 28 July 2010 16:13 UTC
Return-Path: <RNATALE@mitre.org>
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 4BFC93A67D0 for <clouds@core3.amsl.com>; Wed, 28 Jul 2010 09:13:15 -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 LXjBVDAjNIAf for <clouds@core3.amsl.com>; Wed, 28 Jul 2010 09:13:07 -0700 (PDT)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id 9DA203A6768 for <clouds@ietf.org>; Wed, 28 Jul 2010 09:13:06 -0700 (PDT)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id o6SGDSRe002566 for <clouds@ietf.org>; Wed, 28 Jul 2010 12:13:28 -0400
Received: from imchub2.MITRE.ORG (imchub2.mitre.org [129.83.29.74]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id o6SGDS2K002558; Wed, 28 Jul 2010 12:13:28 -0400
Received: from IMCMBX2.MITRE.ORG ([129.83.29.205]) by imchub2.MITRE.ORG ([129.83.29.74]) with mapi; Wed, 28 Jul 2010 12:13:28 -0400
From: "Natale, Bob" <RNATALE@mitre.org>
To: "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 12:13:27 -0400
Thread-Topic: [clouds] IETF-78 Cloud Standards BOF
Thread-Index: AcsuTL9mj8JJKN//Q4q9BVXc3kn9gAABABdyAAFdd5AAAwlLrQADCmFA
Message-ID: <17969D855F28964C88D177D45B6CDF1104D3B7579D@IMCMBX2.MITRE.ORG>
References: <024501cb2e4c$c17f78e0$447e6aa0$@com> <317616CE96204D49B5A1811098BA8950027876F5@XMB-AMS-110.cisco.com> <011501cb2e57$9ab0c6a0$e9818182@china.huawei.com> <317616CE96204D49B5A1811098BA8950027876FC@XMB-AMS-110.cisco.com>
In-Reply-To: <317616CE96204D49B5A1811098BA8950027876FC@XMB-AMS-110.cisco.com>
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_17969D855F28964C88D177D45B6CDF1104D3B7579DIMCMBX2MITREO_"
MIME-Version: 1.0
Cc: "clouds@ietf.org" <clouds@ietf.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:13:15 -0000
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
- [clouds] IETF-78 Cloud Standards BOF Chris Fenton (Iridescent)
- Re: [clouds] IETF-78 Cloud Standards BOF Monique Morrow (mmorrow)
- Re: [clouds] IETF-78 Cloud Standards BOF Linda Dunbar
- Re: [clouds] IETF-78 Cloud Standards BOF Monique Morrow (mmorrow)
- Re: [clouds] IETF-78 Cloud Standards BOF Natale, Bob
- Re: [clouds] IETF-78 Cloud Standards BOF Edmonds, AndrewX
- Re: [clouds] IETF-78 Cloud Standards BOF Monique Morrow (mmorrow)
- Re: [clouds] IETF-78 Cloud Standards BOF Natale, Bob
- Re: [clouds] IETF-78 Cloud Standards BOF Sam Johnston
- Re: [clouds] IETF-78 Cloud Standards BOF Monique Morrow (mmorrow)
- Re: [clouds] IETF-78 Cloud Standards BOF Monique Morrow (mmorrow)
- [clouds] Where is today's cloud bar bof? guyingjie 00107907