Re: [clouds] Clouds SDO gap analysis template (a Table)

"Carl Williams" <> Tue, 25 May 2010 17:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BB0273A63D3 for <>; Tue, 25 May 2010 10:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.289
X-Spam-Status: No, score=-2.289 tagged_above=-999 required=5 tests=[AWL=0.309, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ji-wnBSNhy6l for <>; Tue, 25 May 2010 10:28:11 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 055943A681F for <>; Tue, 25 May 2010 10:28:10 -0700 (PDT)
Received: from [] (helo=carlwPC) by with esmtpa (Exim 4.67) (envelope-from <>) id 1OGxv8-0000bt-AU; Tue, 25 May 2010 10:28:02 -0700
From: "Carl Williams" <>
To: "'Mark Webb'" <>, <>
References: <> <> <>
In-Reply-To: <>
Date: Tue, 25 May 2010 13:28:07 -0400
Organization: MCSR Labs
Message-ID: <008b01cafc2f$a497e180$edc7a480$@org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_008C_01CAFC0E.1D864180"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acr8LKkk4x7BouK2SmG77p0MKucONgAAukAA
Content-Language: en-us
X-ELNK-Trace: 43c6fb6bcad0e12d8fb8d53de325e257a94dbb672ca097f4cd8a6537e1e116d64c29f44aa89573bf350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
Subject: Re: [clouds] Clouds SDO gap analysis template (a Table)
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Clouds pre-BOF discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 25 May 2010 17:28:22 -0000

Hi Mark,


  I agree with you and support a “Gap Analysis” that should be published in
internet-draft form.





From: [] On Behalf Of
Mark Webb
Sent: Tuesday, May 25, 2010 1:06 PM
Subject: Re: [clouds] Clouds SDO gap analysis template (a Table)




I think the wiki is a fine effort.  Ad-hoc and informal,
but with fine goals.


However, it doesn't capture the full picture or all significant SDO and
forum working on cloud related standards and profiles.  TMF (very important
IMO) and ITU-T cloud working group, (less significant now but carries
weight) are two that are not on this site.


There is work to be done IMO.


Mark Webb


On May 25, 2010, at 12:45 PM, Mark Carlson wrote:


Not sure why you are doing this. The information you need is largely already
available on wiki. Each SDO has already created 
an entry describing their cloud work, and they use a standard template
to describe each standard.

For example, here is one for an already finalized standard:

Cloud Standard

1. The name of the specification 

SNIA Cloud Data Management Interface

2. A short statement (<100 words) of the purpose and function of the
specification The SNIA Cloud Data Management Interface (CDMI) is the
functional interface that applications will use to create, retrieve, update
and delete data elements from the cloud. As part of this interface the
client will be able to discover the capabilities of the cloud storage
offering and use this interface to manage containers and the data that is
placed in them. In addition, metadata can be set on containers and their
contained data elements through this interface. 

3. The version number (or other distinct identifier) and date of the most
recently approved version of the specification. 

SNIA Architecture - 1.0 standard 

4. If the specification is part of a group of explicitly related
specifications from the same source, the name of the group of
specifications. Not applicable 

5. URI for the normative text of the specification 


6. The name of the SDO that generated/authored/hosted the specification.
Storage Networking Industry Association 

7. URI for the SDO 

8. The level of approval that the SDO has conferred on the specification as
described by the SDO's process. SNIA Architecture (Final Standard) 

9. The language or languages in which the specification is available. US


10. Which of the categories of Cloud services does the standard address?
(Infrastructure as a Service - IaaS, Data Storage as a Service - DaaS,
Platform as a Service - PaaS, Software as a Service - SaaS) DaaS (Cloud

11. Does the standard address both functional and management aspects of the
service? Yes. Management is done by setting metadata on containers of data
and individual data elements. The functional interface allows CRUD semantics
for storage of data via HTTP. 


12. The level of approval of the specification in this generic lifecycle

Final standard 

13. URI for the applicable SDO's patent and copyright rules, if any,
applicable to development and use of the specification. SNIA IP Policy

14. URI for the SDO's posting location, (if any) for notices from
participants or individuals regarding claims under the rules stated under
number 15. SNIA IP Policy

15. Interoperability, conformance, or certification test activity for the
specification (by owner name or URI). 


16. Known implementations of the specification (by owner name or URI). 

The SNIA Cloud Storage TWG is producing an open source reference

17. A list (or URI pointer to same) of the other specifications* that are
normatively referenced in the specification. 

[ISO-8601] International Standards Organization, "Data elements and
interchange formats -- Information interchange -- Representation of dates
and times", ISO 8601:20044 -

[ITU-T509] International Telecommunications Union Telecommunication
Standardization Sector (ITU-T), Recommendation X.509: Information technology
- Open Systems Interconnection - The Directory: Public-key and attribute
certificate frameworks, May 2000. Specification and technical corrigenda - 

[RFC2119] IETF RFC 2119 <> . Key words for
use in RFCs to Indicate Requirement Levels - 

[RFC2045] IETF RFC 2045 <> . Multipurpose
Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies

[RFC2578] IETF RFC 2578 <> . Structure of
Management Information Version 2 (SMIv2) - 

[RFC2616] IETF RFC 2616 <> . Hypertext
Transfer Protocol -- HTTP/1.1 - 

[RFC3280] IETF RFC 3280 <> . Internet
X.509 Public Key Infrastructure Certificate and Certificate Revocation List
(CRL) Profile - 

[RFC3530] IETF RFC 3530 <> . Network File
System (NFS) version 4 Protocol - 

[RFC3986] IETF RFC 3986 <> . Uniform
Resource Identifier (URI): Generic Syntax -

[RFC4346] IETF RFC 4346 <> . The Transport
Layer Security (TLS) Protocol Version 1.1 - 

[RFC4627] IETF RFC 4627 <> . The
application/json Media Type for JavaScript Object Notation (JSON) - 

[RFC5246] IETF RFC 5246 <> . The Transport
Layer Security (TLS) Protocol Version 1.2 - 


18. A list (or URI pointer to same) of the other specifications* that are
referenced in the specification (except the ones listed under number 17). 

[CRC] Williams, Ross, "A Painless Guide to CRC Error Detection Algorithms",
Chapter 16, August 1993, 

[PKS12] RSA Laboratories, PKCS #12: Personal Information Exchange Syntax,
Version 1.0, June 1999. Specification and Technical Corrigendum - 

[REST] "Representational State Transfer" -

[RESTful Web] Richardson, Leonard and Sam Ruby, RESTful Web Services,
O'Reilly, 2007. 

[SIRDM] Storage Industry Resource Domain Model - 

19. A list (or URI pointer to same) of other specifications* with which the
specification may (speculatively) interoperate or act in complementary,
compatible fashion. 

OCCI - see OGF entry. 

20. A list (or URI pointer to same) of other specifications* similar to this
specification. (Whether or not substitutable.) 



The template can be found here:

-- mark

On 5/25/10 10:33 AM, Bhumip Khasnabish wrote: 

Dear All,


Attached please find a template (a Table) that can be utilized for Clouds
SDO gap analysis.


Very much appreciate your comments, inputs, suggestions for updating it.


The plan is to populate this template with SDOs' information, 

once this template is finalized through email discussion.


Thanks a lot for your support and contributions


Best Regards.




Bhumip Khasnabish (Mobile:+001-781-752-8003,

© 2010 Bhumip Khasnabish. Do not view, print, forward, and save the content
of this email if you are not the intended recipient of the communiqué.

clouds mailing list

clouds mailing list