SSSC PROJECTS

SISWG: See http://siswg.org

SSSWG:

1244 - Guide to Storage System Design (Dormant)

1244.6 - The Media Manager Interchange Protocol (MMIP) (Withdrawn)

defines a protocol to allow interchange of information between autonomous Media Managers.

1244.7 - The Media Manager Control Interface Protocol (MMCIP) (Withdrawn)

defines a protocol which permits interfacing the data management component of the MMS with existing library management systems.

1244.8 - The C Language Procedural Interface (Withdrawn)

defines a set of standard programming interfaces which facilitate construction of components of the MMS, particularly client, administrative, and operational applications, library managers, and drive managers. The initial definition will be for the C programming language. The interface will be designed so that implementation in languages such as C++ or Java could be easily accomplished.

1244.9 - MMS User Mount Commands (Withdrawn)

defines a set of standard commands to allow a user to mount, unmount, acquire, and release media. These commands are specified as a part of a command line interface for systems that offer such interfaces, such as the UNIX shell or NT command line interface. Commands may be embedded in scripts to produce more complex or custom functions, or to allow an application program that is not written for MMS to be adapted for use with MMS.

1244.10 - MMS Standard Administrative and Operational Commands (Withdrawn)

defines a set of standard administration and operation commands of an MMS. The standard defines a command- line, minimally interactive interface for basic interaction with the MMS; these commands could be used to construct interactive interfaces using scripting-based systems such as web CGI scripting or tcl/tk.

1244.11 - MOVER (Withdrawn)

provides a standard storage system data mover architecture and interfaces for use by the IEEE Media Management System and other storage system software. MOVER transfers data between two endpoints in a distributed storage system. Deceptively simple to state, but much more difficult too describe as a standard.

1563.1 - Recommended Practice for Portable Tape Driver Architecture (Withdrawn)
Provides a reference model for tape driver architectures that
is portable across multiple operating system environments, fully featured, and high performance.

A fully realized architecture that industry can base their implementations on that will reduce the effort required to support a new tape device on a given platform and thereby increase the available choice of drives on any given platform.  This will benefit the application vendor and the end customer.

1563.2 - Common Tape Driver Semantics (Withdrawn)
Defines a common set of operations and semantics for access to tape drives across multiple operating systems platforms.

Eases the task of porting and supporting applications that use tape storage across multiple operating system environments.  This will enable application vendors to port to more platforms and thereby increase the end customer's available choices.

1563.3 - Common Format For Data On Tape (Withdrawn)
Defines a self-identifying format and record structure for the storage of data and meta-data on tapes, a structure that contains the key to understanding the format of the data stream as well the data itself.  An analogue from the networking world would be the Document Type Definition (DTD) structure used to describe documents in XML (eXtended Markup Language).

Enables data written by one application to be accessible by other applications without those applications having to know how each other encodes data written to tape.

Page Updated 20080328