Re: [clouds] IETF-78 Cloud Standards BOF

"Monique Morrow (mmorrow)" <mmorrow@cisco.com> Wed, 28 July 2010 20:53 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 EB8A43A685F for <clouds@core3.amsl.com>; Wed, 28 Jul 2010 13:53:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.505
X-Spam-Level:
X-Spam-Status: No, score=-10.505 tagged_above=-999 required=5 tests=[AWL=0.093, 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 3+NPFN2RyAiv for <clouds@core3.amsl.com>; Wed, 28 Jul 2010 13:53:36 -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 4A52C3A67F8 for <clouds@ietf.org>; Wed, 28 Jul 2010 13:53:36 -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: AvsEAMc1UExAZnwN/2dsb2JhbACgCHGncZsKgm+CRwSLLA
X-IronPort-AV: E=Sophos; i="4.55,275,1278288000"; d="scan'208,217"; a="140431112"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 28 Jul 2010 20:53:59 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o6SKrvj9026865; Wed, 28 Jul 2010 20:53:58 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 22:53:57 +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_01CB2E96.FEDEBFDE"
Date: Wed, 28 Jul 2010 22:49:52 +0200
Message-ID: <317616CE96204D49B5A1811098BA895002787709@XMB-AMS-110.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [clouds] IETF-78 Cloud Standards BOF
Thread-Index: AcsuhMPEDRu1MA2LQ+qlgLBT7UQZTQAEanSh
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><317616CE96204D49B5A1811098BA8950027876FF@XMB-AMS-110.cisco.com><17969D855F28964C88D177D45B6CDF1104D3B75810@IMCMBX2.MITRE.ORG> <AANLkTik=4mtkqS86HwcS9qNBw8ZgVRo0cSo6hrcP=mfQ@mail.gmail.com>
From: "Monique Morrow (mmorrow)" <mmorrow@cisco.com>
To: "Sam Johnston" <sj@google.com>, "Natale, Bob" <RNATALE@mitre.org>
X-OriginalArrivalTime: 28 Jul 2010 20:53:57.0249 (UTC) FILETIME=[FF3F1F10:01CB2E96]
Cc: k.mcewen@verizon.net, 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 20:53:39 -0000

Sam,

Concur.

I would like to focus the discussion from ├╝eber"coordination to what we can do in the IETF [my own concrete case study of issues included - draft in process]  in terms of what we can do moving forward,

See you tomorrow -

MM


-----Original Message-----
From: Sam Johnston [mailto:sj@google.com]
Sent: Wed 7/28/2010 11:43 AM
To: Natale, Bob
Cc: Monique Morrow (mmorrow); Linda Dunbar; Chris Fenton (Iridescent); k.mcewen@verizon.net; clouds@ietf.org; Mark Carlson
Subject: Re: [clouds] IETF-78 Cloud Standards BOF
 
Bob/Monique/Linda,

I personally am very sceptical of (and would vigorously oppose) any attempt
to *coordinate* standards in the cloud space and echo Andy Edmonds in
pointing at cloud-standards.org (which already purports to do so). I am
however fully supportive of *collaboration* between standards orgs and
believe cloud-standards.org is as good a (neutral) venue as any, having
participated in a number of their calls. I also don't believe a group exists
(or even could exist) which would be able to objectively assess the cloud
space as each views the problem from a completely different perspective - in
this case the underlying telecommunications infrastructure while one could
argue cloud is more user-centric. Nevertheless the activity may prove useful
for ITU-T's internal use.

What was abundantly clear at today's bar bof is that there are a number of
areas where the IETF can deliver significant value now and we should focus
on these rather than participating in the landrush going on around us - as I
said in my presentation, there are currently no standards in cloud, only
specifications.

Getting back to Chris's original question, I don't think there's much point
in spending any time creating yet another model for cloud, however
enumerating specific potential work areas (e.g. CloudAudit, CloudLog, HTTP
enhancements, ARP222, etc.) would be time well spent... particularly if it
were to result in drafts as is the case for these examples.

Cheers,

Sam

On 28 July 2010 19:11, Natale, Bob <RNATALE@mitre.org> wrote:

>  Hi Monique,
>
>
>
> I fully agree.  In fact, I meant my first sentence below to read ".of
> having a single SDO **coordinate** efforts.." . did **not** mean to imply
> that there should be only a single SDO in the cloud space, for sure!  Not
> meant to stifle individual SDO initiative, innovation, or momentum . just
> introduce some rational division of labor and coordination of
> effort/deliverables at the collective SDO level.
>
>
>
> Cheers,
>
> BobN
>
>
>
> *From:* Monique Morrow (mmorrow) [mailto:mmorrow@cisco.com]
> *Sent:* Wednesday, July 28, 2010 1:03 PM
> *To:* Natale, Bob; Linda Dunbar; Chris Fenton (Iridescent);
> k.mcewen@verizon.net
>
> *Cc:* clouds@ietf.org
> *Subject:* RE: [clouds] IETF-78 Cloud Standards BOF
>
>
>
> Bob,
>
> With ITU-T Focus Group Cloud Computing Vice Chair hat on, this suggestion
> is pragmatic.
>
> In the meantime, as IETF contributor, want to additionally focus on
> centering in on our use cases-scenarios- applicability of IETF-developed
> protocols and/or identification of protocols that should be developed within
> the IETF accordingly.
>
> With warm regards
>
> Monique
>
> PS BoF continues tomorrow!
>
> -----Original Message-----
> From: Natale, Bob [mailto:RNATALE@mitre.org <RNATALE@mitre.org>]
> Sent: Wed 7/28/2010 9:13 AM
> 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<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 <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<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<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 mailing list
> clouds@ietf.org
> https://www.ietf.org/mailman/listinfo/clouds
>
>