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

Mark Carlson <> Tue, 25 May 2010 16:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7C1833A6A92 for <>; Tue, 25 May 2010 09:46:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.497
X-Spam-Status: No, score=-4.497 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id dclaHIj7Iozo for <>; Tue, 25 May 2010 09:46:31 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id E02F73A6BCE for <>; Tue, 25 May 2010 09:46:30 -0700 (PDT)
Received: from ( []) by (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4PGkJpc028102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <>; Tue, 25 May 2010 16:46:21 GMT
Received: from ( []) by (Switch-3.4.2/Switch-3.4.1) with ESMTP id o4PB4fsW010792 for <>; Tue, 25 May 2010 16:46:18 GMT
Received: from by with ESMTP id 266698171274805947; Tue, 25 May 2010 09:45:47 -0700
Received: from (/ by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 25 May 2010 09:45:46 -0700
Message-ID: <>
Date: Tue, 25 May 2010 10:45:45 -0600
From: Mark Carlson <>
Organization: Oracle
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv: Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4
MIME-Version: 1.0
References: <>
In-Reply-To: <>
Content-Type: multipart/alternative; boundary="------------060400030606080507090207"
X-Auth-Type: Internal IP
X-Source-IP: []
X-CT-RefId: str=0001.0A090203.4BFBFEDD.0190:SCFMA922111,ss=1,fgs=0
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 16:46:33 -0000


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 English


*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 Storage)

*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 taxonomy: *

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
> 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