[clouds] IETF-78 Cloud Standards BOF

"Chris Fenton \(Iridescent\)" <cfenton@iridescentnetworks.com> Wed, 28 July 2010 12:02 UTC

Return-Path: <cfenton@iridescentnetworks.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 845FA3A6A1D for <clouds@core3.amsl.com>; Wed, 28 Jul 2010 05:02:27 -0700 (PDT)
X-Quarantine-ID: <pYPMQbSZU9D1>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BANNED, message contains part: multipart/mixed | application/ms-tnef, .tnef, winmail.dat
X-Spam-Flag: NO
X-Spam-Score: 0.289
X-Spam-Level:
X-Spam-Status: No, score=0.289 tagged_above=-999 required=5 tests=[AWL=0.287, BAYES_50=0.001, UNPARSEABLE_RELAY=0.001]
X-Amavis-Modified: Mail body modified (defanged) by core3.amsl.com
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 pYPMQbSZU9D1 for <clouds@core3.amsl.com>; Wed, 28 Jul 2010 05:02:26 -0700 (PDT)
Content-Type: multipart/mixed; boundary="----------=_1280318547-1272-1"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
Received: from smtp114.biz.mail.re2.yahoo.com (smtp114.biz.mail.re2.yahoo.com [66.196.116.99]) by core3.amsl.com (Postfix) with SMTP id C36F93A67EF for <clouds@ietf.org>; Wed, 28 Jul 2010 05:02:25 -0700 (PDT)
Received: (qmail 1916 invoked from network); 28 Jul 2010 12:02:45 -0000
Received: from ChrisPC (cfenton@130.129.113.95 with login) by smtp114.biz.mail.re2.yahoo.com with SMTP; 28 Jul 2010 05:02:44 -0700 PDT
From: "Chris Fenton \(Iridescent\)" <cfenton@iridescentnetworks.com>
To: <clouds@ietf.org>
Date: Wed, 28 Jul 2010 13:02:27 +0100
Message-ID: <024501cb2e4c$c17f78e0$447e6aa0$@com>
X-Mailer: Microsoft Office Outlook 12.0
Cc: k.mcewen@verizon.net
Subject: [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 12:02:27 -0000

WARNING: contains banned part
--- Begin Message ---
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 




--- End Message ---