Cloud Standard

SNIA Cloud Data Management Interface

_______________________________________________
clouds mailing list
clouds@ietf.org
https://www.ietf.org/mailman/listinfo/clouds

SNIA Cloud Data Management Interface

_______________________________________________
clouds mailing list
clouds@ietf.org
https://www.ietf.org=
/mailman/listinfo/clouds

SNIA Cloud Data Managem=
ent Interface

_______________________________________________
clouds mailing list
clouds@ietf.org
=
https://www.ietf.org/mailman/listinfo/clouds

SNIA Cloud Data Managem=
ent Interface

_______________________________________________
clouds mailing list
clouds@ietf.org
=
https://www.ietf.org/mailman/listinfo/clouds

SNIA Cloud Data Management Interface

________________________________________=
_______
clouds mailing list
clouds@ietf.org
=
https://www.ietf.or=
g/mailman/listinfo/clouds
=A0 =

SNIA Cloud Data Management Interface

_______________________________________________
clouds mailing list
clouds@ietf.org
https://www.ietf.org/mailman/listinfo/clouds

SNIA Cloud Data Management Interface

_______________________________________________
clouds mailing list
clouds@ietf.org
=
https://www.ietf.org/mailman/listinfo/clouds

SNIA Cloud Data Management =
Interface
=A0=A0=A0 

______________________________________________=
_
clouds mailing =
list
clouds@ietf.org
https://www.ietf.org/mailman/listinfo/clouds
=A0 =

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 =
standard4. If the specification is part of a group of =
explicitly related specifications from the same source, the name of the =
group of specifications. Not =
applicable5. URI for the normative text of the =
specification 6. The name of the SDO that =
generated/authored/hosted the specification. Storage =
Networking Industry Association7. 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 =
English10. Which of the =
categories of Cloud services does the standard address? (Infrastruc=
ture 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 =
Policy14. 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).None16. Known implementations of the =
specification (by owner name or URI).
The SNIA Cloud Storage TWG is =
producing an open source reference =
implementation.
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 -http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?c=
snumber=3D40874
[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.)
None.

clouds mailing list

SNIA Cloud Dat=
a Management Interface
    =

___________________=
____________________________
clouds mailing list=

clouds@ietf.org<=
/o:p>
htt=
ps://www.ietf.org/mailman/listinfo/clouds
  <=
/span>
SNIA Cloud Data Management Interface

_______________________________________________
clouds mailing list
clouds@ietf.org
https://www.ietf.org/mailman/listinfo/clouds

_______________________________________________
clouds mailing list
clouds@ietf.org
https://www.ietf.org/mailman/listinfo/clouds

Cloud Standard<= o:p>

SOURCE

SUBJECT

OPTIONAL

Cloud Standard

SOURCE

SUBJECT

OPTIONAL

Cloud Standard

SOURCE

SUBJECT

OPTIONAL

Cloud Standard

SOURCE

SUBJECT

OPTIONAL

Cloud Standard

SOURCE

SUBJECT

OPTIONAL

Cloud Standard

SOURCE =

SUBJECT =

OPTIONAL

Cloud Standard

SOURCE

SUBJECT

OPTIONAL

Cloud Standard

SOURCE

SUBJECT

OPTIONAL

Cloud = Standard

SOURCE

SUBJECT

OPTIONAL

Cloud Standard

SOURCE

SUBJECT

OPTIONAL