Working group

IETF develops standards for automated network management which, as the name implies, aims to improve and make more efficient management of networks as they continue to increase in size and complexity.

IETF Autonomic Networking Integrated Model and Approach (ANIMA) working group develops and maintains specifications and documentation for interoperable protocols and procedures for automated network management and control of professionally-managed networks.

• ANIMA work will rely on the framework described in draft-ietf-anima-reference-model already approved for publication. Work not related to this framework is welcome for review, but WG adoption of such work requires explicit rechartering. The two concrete areas of the reference model are (1) the Autonomic Networking Infrastructure (ANI), and (2) Autonomic Functions (AF) built from software modules called Autonomic Service Agents (ASA).
• ANIMA will start to define Autonomic Functions (AF) to enable service automation in networks; it will also work on generic aspects of ASA including design guidelines and lifecycle management, coordination and dependency management.
• The life span of this WG is from 2019 with Information distribution over GRASP to the IESG submission in November to Jul 2020, when the WG will recharter or close.

The OASIS LegalRuleML TC defines a rule interchange language for the legal domain. The work enables modeling and reasoning that allows implementers to structure, evaluate, and compare legal arguments constructed using the rule representation tools provided.
 
The TC is affiliated with the OASIS LegalXML Member Section. For more information on LegalRuleML, see the TC Charter.

The Dynamic Host Configuration Working Group (DHC WG) has developed DHCP for automated allocation, configuration and management of IP addresses, IPv6 prefixes, IP protocol stack and other parameters. DHCPv4 is currently a Draft Standard and is documented in RFC 2131 and RFC 2132.
DHCPv6 is currently a Proposed Standard and is being updated. The WG plans to advance the DHCPv6 protocol to Internet standard. The DHC WG is responsible for defining DHCP protocol extensions. Definitions of new DHCP options that are delivered using standard mechanisms with documented semantics are not considered a protocol extension and thus are generally outside of scope for the DHC WG.

The Real-time Transport Protocol (RTP) is an Internet Standard. RTP and its associated profiles and payload formats provides for real-time transmission of audio and video over unicast and multicast transports.

The Audio/Video Transport Core Maintenance (avtcore) Working Group in IETF is chartered to:

• Maintain the core RTP/RTCP specifications and the AVP, SAVP, AVPF, and SAVPF profiles.
• Develop application-specific guidelines for the use of RTP/RTCP protocols with the AVP, SAVP, AVPF, and SAVPF profiles, and extensions to those protocols that are driven by application-specific needs.
• Specify and maintain payload formats for use with RTP, developing RTP payload formats for new media codecs, review and revise existing payload formats to advance those that are especially
  useful to Internet Standard, and declare others Historic.
• Evaluate and process proposals for RTP eXtended Report Block (XRBLOCK) definitions containing new metrics.

The WG's milestones span early 2019 to Mar 2020.

The Dynamic Host Configuration Working Group (DHC WG) has developed DHCP for automated allocation, configuration and management of IP addresses, IPv6 prefixes, IP protocol stack and other parameters. DHCPv4 is currently a Draft Standard and is documented in RFC 2131 and RFC 2132.
DHCPv6 is currently a Proposed Standard and is being updated. The WG plans to advance the DHCPv6 protocol to Internet standard. The DHC WG is responsible for defining DHCP protocol extensions. Definitions of new DHCP options that are delivered using standard mechanisms with documented semantics are not considered a protocol extension and thus are generally outside of scope for the DHC WG.

The OASIS Electronic Court Filing TC will develop specifications for the use of XML to create legal documents and to transmit legal documents from an attorney, party or self-represented litigant to a court, from a court to an attorney, party or self-represented litigant or to another court, and from an attorney or other user to another attorney or other user of legal documents.
 
The TC is affiliated with the OASIS LegalXML Member Section. For more information, see the TC Charter and FAQ

The IETF Binary Floor Control Protocol Bis (BFCPBIS) working group is chartered to specify a revision of BFCP (RFC 4582) to support both TCP and UDP as transports.

• The revision adds optional support for UDP to BFCP. The security when using UDP will be based on DTLS. The updated protocol will use an existing approach (e.g., stop and wait with a single outstanding transaction) to provide a reliable, congestion safe, and TCP friendly transport.
• The updated protocol will also be able to deliver server-initiated transactions reliably when needed. The WG will research the size of messages used and decide if fragmenting a request or response over multiple UDP packets is required. The new protocol will be backwards compatible with RFC 4582 when used in TCP mode.
• The BFCPBIS WG coordinates closely with the MMUSIC WG to create a revision of RFC 4583 specifying how BFCP is signaled in SDP so that it supports UDP as well as TCP transports.

Most of the WG's milestones for applications and real-time area have been achieved.

The OASIS Litigant Portal (LP) Technical Committee is chartered to produce specifications for data interoperation between Litigant Portal Modules. The technical specifications are collectively referred to as the Litigant Portal Exchange (LPX) Specifications. Portal modules are designed to provide assististance to self-represented litigants. The modules will (a) define structured interactions between related modules in the portal, (b) facilitate navigation between modules in the portal, (c) define interfaces with external partners and resources. Specifications for information exchange will initially support XML data formats. Members of the LP TC may also produce non-Standards Track content such as tutorials, usage guides, quick start guides and other documents that will assist the broader community in adopting the LPX specifications.
 
The TC is affiliated with the OASIS LegalXML Member Section. For more information on the LP TC, see the TC Charter.

Standardization of coded representation of audio, picture, multimedia and hypermedia information - and sets of compression and control functions for use with such information - such as:

• Audio information
• Bi-level and Limited Bits-per-pixel Still Pictures
• Digital Continuous-tone Still Pictures
• Computer Graphic Images
• Moving Pictures and Associated Audio
• Multimedia and Hypermedia Information for Real-time Final Form Interchange
• Audio Visual Interactive Script ware

Excluded: Character Coding

Standardization of microprocessor systems; and of interfaces, protocols, architectures and associated interconnecting media for information technology equipment and networks, generally for commercial and residential environments, to support embedded and distributed computing environments, storage systems, other input/output components, home and building electronic systems including customer premises smart grid applications for electricity, gas, water and heat.

NOTE: This scope includes requirements for components, assemblies and subsystems. However, standardization of cables, waveguides and connectors remains within the relevant product technical committees and subcommittees of IEC. The scope includes the development of network interfaces, in liaison with committees for external utility networks, to support smart grid applications at the customer premises.

The current area of work for JTC 1/SC 24 consists of:

• standardization of interfaces for information technology based applications relating to computer graphics and virtual reality,
• image processing,
• environmental data representation,
• support for Mixed and Augmented Reality (MAR), and
• interaction with, and visual presentation of, information

CACAO TC members are developing a standard to implement the course of action playbook model for cybersecurity operations.
 
In order to defend against cyber threats, organizations must manually identify, create, and document the prevention, mitigation, and remediation steps that, together, form a course of action playbook. However, today, there is is no standardized way to document and share these playbooks across organizational boundaries and technology solutions. CACAO addresses this problem by defining a sequence of cyber defense actions that can be executed for each type of playbook. It will specifically enable organizations to:

1. create course of action playbooks in a structured machine-readable format,
2. digitally sign course of action playbooks,
3. securely share course of action playbooks across organizational boundaries and technological solutions, and
4. document processing instructions for course of action playbooks in a machine readable format.