Working group

The OASIS PKCS 11 Technical Committee develops enhancements to improve the PKCS #11 standard for ease of use in code libraries, open source applications, wrappers, and enterprise/COTS products: implementation guidelines, usage tutorials, test scenarios and test suites, interoperability testing, coordination of functional testing, development of conformance profiles, and providing reference implementations.
 
The updated standard provides additional support for mobile and cloud computing use cases: for distributed/federated applications involving key management functions (key generation, distribution, translation, escrow, re-keying); session-based models; virtual devices and virtual keystores; evolving wireless/sensor applications using near field communication (NFC), RFID, Bluetooth, and Wi-Fi.
 
TC members are also designing new mechanisms for API instrumentation, suitable for use in prototyping, profiling, and testing in resource-constrained application environments. These updates enable support for easy integration of PKCS #11 with other cryptographic key management system (CKMS) standards, including a broader range of cryptographic algorithms and CKMS cryptographic service models.

The OSLC PROMCODE TC defines technical elements and guidelines for project management of Software Supply Chains. The OSLC PROMCODE TC will examine the work done by the PROMCODE consortium on exchanging project management information, and will modify/extend the work so that it fits the needs of the global community.
 
The OSLC PROMCODE TC will work to:

1. Define a model of project management information for SSC. A model should describe a minimum set of information and relationships commonly used by carriers and suppliers to manage software delivery.
2. Define a set of resources and their relationships following the OSLC framework as defined by the OSLC Core TC.
3. Create additional technical elements as required to support current and future scenarios for OSLC User Groups, OSLC MS-affiliated TCs, Subcommittees and the OSLC Member Section Steering Committee.
4. Leverage existing work, such as existing OSLC specifications, as much as possible. If gaps are identified, the OSLC PROMCODE TC will attempt to resolve them with other affiliated TCs prior to defining new concepts within PROMCODE.

The PROMCODE (Project Management of Contracted Delivery for Software Supply Chains) specifications advance a standard for exchanging project management information across organizational boundaries in support of Software Supply Chain (SSC) delivery. PROMCODE leverages other OSLC specifications which apply World Wide Web and Linked Data principles to enable products, services and other distributed network resources to interoperate successfully. TC members intend to request affiliation with the OASIS OSLC Member Section.
 
This TC is part of the OASIS OSLC Member Section. For more information on the OSLC PROMCODE TC, see the TC Charter.

The OpenDocument Format (ODF) is an open XML-based document file format for office applications to be used for documents containing text, spreadsheets, charts, and graphical elements. The file format makes transformations to other formats simple by leveraging and reusing existing standards wherever possible. As an open standard under the stewardship of OASIS, OpenDocument also creates the possibility for new types of applications and solutions to be developed other than traditional office productivity applications.
 
The OpenDocument TC works closely together with the OASIS ODF Adoption Technical Committee which provide expertise and resources to educate the marketplace on the value of the OpenDocument OASIS Standard.
 
For more information, see the TC Charter and FAQ
 

The OASIS OData TC works to simplify the querying and sharing of data across disparate applications and multiple stakeholders for re-use in the enterprise, Cloud, and mobile devices. A REST-based protocol, OData builds on HTTP and JSON using URIs to address and access data feed resources. It enables information to be accessed from a variety of sources including (but not limited to) relational databases, file systems, content management systems, and traditional Web sites. OData provides a way to break down data silos and increase the shared value of data by creating an ecosystem in which data consumers can interoperate with data producers in a way that is far more powerful than currently possible, enabling more applications to make sense of a broader set of data. Every producer and consumer of data that participates in this ecosystem increases its overall value.

CoRE provides a framework for resource-oriented applications intended to run on constrained IP networks. Such networks have limited packet sizes, may exhibit a high degree of packet loss, and may have a substantial number of devices that may be powered off at any point in time but periodically "wake up" for brief periods of time.

• The CoRE working group will define a framework for a limited class of applications: those that deal with the manipulation of simple resources on constrained networks.
• This includes applications to monitor simple sensors (e.g. temperature sensors, light switches, and power meters), to control actuators (e.g. light switches, heating controllers, and door locks), and to manage devices.

A major factor limiting the interoperability of telepresence systems is the lack of a standardised way to describe and negotiate the use of the multiple streams of audio and video comprising the media flows.

The CLUE WG will create specifications for SIP-based conferencing systems to enable communication of information about media streams so that a sending system, receiving system, or intermediate system can make
reasonable decisions about transmitting, selecting, and rendering media streams. This enables systems to make choices that optimise user experience.

In the context of this WG, telepresence is used in a general manner to describe systems that provide high definition, high quality audio/video enabling a "being-there" experience.

Using existing work done by the development communities of Matroska, FFV1, and FLAC, the IETF Working Group on Codec for LossLess Archiving and Realtime Transmission (CELLAR) will formalise specifications for these open and lossless formats. In order to provide authoritative, standardised specifications for users and developers, the Working Group will seek consensus throughout the process of refining and formalising these standards.

This WG fills gaps in terms of standardising open, transparent, self-descriptive, lossless formats as an important mission to be undertaken by the open source community. Work addresses concerns about the sustainability and credibility of existing specifications for the long-term use of these formats through a broader review and formalisation encourage widespread adoption.

The Working Group will seek consensus and refinements for specifications for both FFV1 and Matroska in order to provide authoritative, standardized specifications for users and developers. Backward compatibility with existing versions 0-3 of the FFV1 and Matroska specifications will be an important goal, while also reviewing and refining the current version 4 under active development.

The OpenC2 TC was chartered to draft documents, specifications, lexicons or other artifacts to fulfill the needs of cyber security command and control in a standardized manner. The Technical Committee will leverage pre-existing standards to the greatest extent practical, identifying gaps pertaining to the command and control of technologies that provide or support cyber defenses. The TC will base its initial efforts on artifacts generated by the OpenC2 Forum, a community of cyber-security stakeholders that was facilitated by the National Security Agency; the Forum has published a language description document (RC4), actuator profiles, and open source prototype implementations.
 
For more information on the OpenC2 TC, see the TC Charter.
 
OpenC2 TC standing rules can be found under Additional Information.

The significant growth in content delivered over IP networks, existing CDN providers are scaling up their infrastructure and many Network Service Providers and Enterprise Service Providers are deploying their own CDNs. Work in IETF focuses on meeting the need to interconnect (previously) standalone CDNs to that can interoperate and collectively behave as a single delivery infrastructure.

The goal of the Content Delivery Networks Interconnection (CDNI) WG is to allow the interconnection of separately administered CDNs in support of the end-to-end delivery of content from CSPs through multiple CDNs and ultimately to end users (via their respective User Agents). The CDNI WG aims at delivering a  targeted, deployable solution in a short timeframe as needed by the industry. It is expected that the CDNI interfaces will be realised using existing IETF protocols for transport and message exchange, and using existing object notation grammars/languages for the definition of CDNI objects and semantics.

In the event that protocol extensions or new protocols are deemed necessary by the WG, the WG will recharter in mid-June 2020.
 

Concise Binary Object Representation (CBOR, RFC 7049) extends the JavaScript Object Notation (JSON, RFC 8259) data interchange format to include binary data and an extensibility model, using a binary representation format that is easy to parse correctly. It has been picked up by a number of IETF efforts (e.g., CORE, ANIMA GRASP) as a message format.

• The IETF CBOR working group will update RFC 7049 to deal with existing errata. Security issues and clarifications may be addressed, but changes to the document will ensure backward compatibility for widespread deployed codebases. The resulting document will be targeted at becoming an Internet Standard.
• This WG falls under the IETF applications and real-time area.

The SSM TWG is a technical work group of the SNIA Technical Committee defining the Swordfish specification that extends the Distributed Management Task Force (DMTF)'s Redfish specification (API) to handle the emanagement of storage equipment and storage services found in modern data centers.

The target market for this interface is Cloud and Web-based IT professionals for scalable storage management and related data services. Within this community, the focus is on usability by non-computing science degree personnel. The interface should be simple to use, accessible, and compatible with the existing tool chains and with modern transports.

The purpose of the OASIS Production Planning and Scheduling TC is to develop common object models and corresponding XML schemas for production planning and scheduling software, which can communicate with each other in order to establish collaborative planning and scheduling on intra and/or inter enterprises in manufacturing industries.