SNIA Draft Technical Work available for Public Review

During the development of technical work, the SNIA may make available a Work-in-Progress DRAFT version for public review & feedback.  Work-in-Progress DRAFTS are not endorsed by the SNIA for commercial shipping product implementation, but rather for review/feedback and prototyping work to ensure the work, when completed, will meet the needs of the Industry.
Work-in-Progress DRAFTS are subject to change. The Work-in-Progress DRAFT  may be updated, replaced, or made obsolete at any time. Some of the Intellectual Property protections for users of SNIA software and specifications are not applicable to users of Work-in-Progress DRAFTs.

To provide feedback, please use the SNIA Feedback Portal.

TLS Specification for Storage Systems v0.5r1 DRAFT

This document specifies the requirements for use of the Transport Layer Security (TLS) protocol in conjunction with data storage technologies. The requirements are intended to facilitate secure interoperability of storage clients and servers as well as non-storage technologies that may have similar interoperability needs. This document was developed with the expectation that future versions of SMI-S and CDMI could leverage these requirements to ensure consistency between these standards as well as to more rapidly adjust the security functionality in these standards.

• TLS Specification for Storage Systems v0.5r1 DRAFT

Storage Management Initiative Specification (SMI-S) v2.0r1 DRAFT

The Storage Management Initiative Specification defines a method for the interoperable management of heterogeneous networked storage.

• SMI-S v2 Summary (Important Overview of V2)
• Storage Management Initiative Specification (SMI-S) v2.0r1 DRAFT (13MB)

Cloud Data Management Interface (CDMI) v1.1.0a DRAFT

The Cloud Data Management Interface defines 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.

This interface is also used by administrative and management applications to manage containers, accounts, security access and monitoring/billing information, even for storage that is accessible by other protocols. The capabilities of the underlying storage and data services are exposed so that clients can understand the offering.

• Cloud Data Management Interface (CDMI) v1.1.0a DRAFT

Linear Tape File System (LTFS) Format Specification v2.1 DRAFT

The Linear Tape File System format is an open description of the layout of data-structures stored on a sequential-access media design to address tape archive requirements. These data-structures hold the file content data and associated file metadata.  This specification is being developed by the SNIA LTFS Technical Work Group.

Publication of this Working Draft for review and comment has been approved by the LTFS TWG.  This draft represents a “best effort” attempt by the LTFS TWG to reach preliminary consensus, and it may be updated, replaced, or made obsolete at any time.  This document should not be used as reference material or cited as other than a “work in progress.  Suggestion for revision should be directed to http://www.snia.org/feedback/.

• Linear Tape File System (LTFS) Format Specification v2.1 DRAFT

CDMI Reference Implementation v1.0d DRAFT

The CDMI Reference Implementation is a SNIA Software development project that implements the Cloud Data Management Interface.

• CDMI Reference Implementation v1.0d DRAFT

SMI-S v1.6.1 rev 2 DRAFT Addenda Books

Implementation draft of the Architecture, Common Profiles and Host Addenda books as extension of the SMI-S 1.6 Addenda books.

• SMI-S v1.6.1 rev 2 DRAFT Addenda Books

DRAFT CDMI Extensions and Profiles

The Cloud Storage Technical Work Group is adding new functionality to CDMI by publishing individual extensions the the CDMI standard. These can be implemented as needed in conjunction with a CDMI implementation to add new functionality before the next release of CDMI. As implementation experience is gained and interoperable implementations are tested, these extensions will be made part of the next release of CDMI.

The Cloud Storage TWG will also be publishing profiles of CDMI that scope it down to specific use cases based on different types of clouds.

See the dedicated web page DRAFT CDMI Extensions and Profiles for additional information.

Self-contained Information Retention Format (SIRF) Use Cases and Functional Requirements v0.5a DRAFT

We propose an approach to digital content preservation that leverages the knowledge of the archival profession and helps archivists remain comfortable with the digital domain. One of the major needs to make this strategy possible is a digital equivalent to the physical container - the archival box or file folder - that defines a series, and that can be labeled with standard information in a defined format to allow retrieval when needed. The Self-contained Information Retention Format (SIRF) is defined to be that equivalent - a logical container for a set of (digital) preservation objects that also contains catalogs and metadata related to the entire contents of the container as well as to the individual objects. This logical container makes it easier and more efficient to provide many of the processes needed to address threats to digital content.

This document describes SIRF and the motivation for it along with its use cases and requirements. The use case model is used to derive the desired functional requirements of the SIRF format and the system that implements and uses it.  The model uses graphical symbols and text to specify how users or applications in specific roles use SIRF. The document describes the use cases from a usage point of view: it doesn't describe how systems implement SIRF internally, nor does it describe SIRF internal structures or mechanisms.

• Self-contained Information Retention Format (SIRF) Use Cases and Functional Requirements v0.5a DRAFT

Common Trace Semantics Specification v1.0 rev 11 DRAFT

The Common Trace Semantics Specification defines common, recommended semantics for data in I/O traces. Standardized I/O trace semantics will enable the development and use of common I/O trace collection and analysis tools as well as facilitate the sharing of the I/O traces themselves.

• Block I/O Trace Common Semantics Book v1.0 rev 11 DRAFT