Working group

The 'Distributed Resource Management Application API (DRMAA)' working group develops and maintains a set of API specifications for tightly coupled and portable programmatic access to cluster, grid, and cloud systems. The DRMAA working group deliverables are intended to facilitate the development of portable application programs and high-level libraries such as SAGA or OGSA-BES. DRM system vendors can provide a standardized access to their product through a DRMAA implementation. High-level API designers, meta-scheduler architects and end users can rely on such DRMAA implementations for a unified access to execution resources. The scope of the API standardization is focused on job submission, job control, reservation management, and retrieval of job and machine monitoring information.

• Project-Homepage: http://www.drmaa.org/
• Subprojects: DRMAAv1, DRMAAv2 C Binding, DRMAAv2 Go Binding, DRMAAv2 OCCI Binding, DRMAAv2 Root Specification
• GridForge Project (historical): https://forge.ogf.org/sf/projects/drmaa-wg

The goal of the GRAAP Working Group is to produce a set of specifications and supporting documents which describe methods and means to establish Service Level Agreements between different entities in a distributed environment. The WS-Agreement Specification V1.0, a Web Services protocol to establish agreements between two services, has been published May 2007 as an OGF Proposed Recommendation: Just recently an errata version has been published fixin a few typos in the non-normative part. The new version supercedes the version of 2007 (see GFD.192). Along with this document the group has published the specification for extended negotiation and renegotiation on top of WS-Agreement as WS-Agreement Negotiation (see GFD.193).

• Projekt-Homepage: http://www.ogf.org/
• GridForge Project (historical): https://forge.ogf.org/sf/projects/graap-wg

The OASIS CAMP TC advances an interoperable protocol that cloud implementers can use to package and deploy their applications. CAMP defines interfaces for self-service provisioning, monitoring, and control. Based on REST, CAMP is expected to foster an ecosystem of common tools, plugins, libraries and frameworks, which will allow vendors to offer greater value-add.
 
Common CAMP use cases include:

• moving on-premise applications to the cloud (private or public)
• redeploying applications across cloud platforms from multiple vendors

For more information on CAMP, see the TC Charter.

Standardization in the field of banking, securities and other financial services.

The scope of the committee includes the definition and standardisation of digital long-term archive formats for cinematographic works. In addition methods for ensuring data integrity and quality shall be specified. The standard is applicable for digitized analogue films as well as digital born content. 2 Reference software to guarantee interoperability amongst vendors and heritage institutions shall be developed. The scope does not include the standardization of distribution formats

The SNIA Cloud Storage Technologies Initiative (CSTI) is committed to the adoption, growth and standardization of storage in cloud infrastructures, including its data services, orchestration and management, and the promotion of portability of data in multi-cloud environments.  

The HDBaseT standard defines a protocol for communicating 5Play over a single long distance Local Area Network (LAN) cable. Building on the adopted HDBaseT specifications 1 and 2, this standard further enhances HDBaseT 5Play by broadening the variety of cables that the protocol can transfer over, expanding wireless compatibility, increasing power throughput over the HDBaseT link, harmonizing with Internet Protocol (IP), and adding security features.

This document specifies broadcast authentication protocols, which are protocols that provide data integrity and entity authentication in a broadcast setting, i.e. a setting with one sender transmitting messages to many receivers. To provide entity authentication, there needs to be a pre-existing infrastructure which links the sender to a cryptographic secret. The establishment of such an infrastructure is beyond the scope of this document.

This document specifies MAC algorithms suitable for applications requiring lightweight cryptographic mechanisms. These mechanisms can be used as data integrity mechanisms to verify that data has not been altered in an unauthorized manner. They can also be used as message authentication mechanisms to provide assurance that a message has been originated by an entity in possession of the secret key.

The following MAC algorithms are specified in this document:

a) LightMAC;

b) Tsudik's keymode;

c) Chaskey-12.

CEN/TC 434 Subcommittees and Working Groups

CEN/TC 434/WG 1 Core semantic data model

CEN/TC 434/WG 3 Syntax bindings

CEN/TC 434/WG 4 Guidelines at transmission level

CEN/TC 434/WG 5 Extension methodology

CEN/TC 434/WG 6 Test methodology and test results

CEN/TC 434/WG 7 Registry Services

Standardization in the field of e-procurement to support the electronic public procurement processes and their accompanying information flows in the physical and financial supply chain.

The work of CEN/PC 440 will be developed from the deliverables of CEN/BII (2)3 in alignment with the deliverables of CEN/PC 434. Other initiatives such as ISO/IEC/JTC 1/SC 32, OpenPEPPOL and eSENS will be taken into consideration as appropriate.

CEN/TC 224 multi-sectorial environment involves sectors such as Government/Citizen, Transport, Banking, e-Health, as well as Consumers and providers from the supply side such as card manufacturers, security technology, conformity assessment body, software manufacturers.