Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

New Working Groups

One working group has been chartered since IETF 125.

  • ART: JSON Schema(JSONSCHEMA) was chartered 30 April 2026 The JavaScript Object Notation (JSON) is a widely popular data format to store and exchange data in a program language independent and human-readable way. JSON Schema is a language to describe data structures of JSON document (with JSON Schema being JSON documents itself). This Schema language has never been standardized, even though it is in wide use. This working group will attempt to document the language in a standards track RFC.

    We do not recognize any public policy issues in this work.

The following groups are in the process of being (initially) chartered.

  • OPS: SEcure access To Tls Local rEsources(SETTLE)(charter).

    TLS secures most of our web traffic. The availability of provisioning protocols like the Automatic Certificate Management Environment (ACME)(RFC8555) has made prolific deployment of TLS a possibility. However, in local networks it is almost prohibitively difficult to configure the certificates needed for connections secured with TLS. The result is that in local environment will get warnings from e.g. their browsers when they try to connect to servers in the local network–that while users getting used to warnings is generally bad for cyber-hygiene. This working group intends to give operational guidance on how to configure these secure context on local networks. Eventually this work improves the usability of (existing) encryption technology in local domains such as homes or enterprise networks.

    We do not recognize any public policy issues in this work, specifically because this work looks at technologies that are applicable on local networks like enterprise networks.

  • OPS: Operationalizing Network & SErvice abstractioNs(ONSEN) (charter).

    A recent IAB report on the NEMOPS workshop captures complaints and suggestions of network operators—those that run complex networks. This working group, which results from a BOF at IETF 125, uses that report as a starting point develop service abstractions.

    Service abstractions can be used to simplify complexities in the network and make them easier to manage by hiding the complicated details and showing only the important parts.

    This group will look at the operational workflows for deploying, monitoring, troubleshooting, and evolving service abstractions. This work is purely operation in nature; we do not recognize any public policy relation.

  • RTG: Fast Network Notifications(FANN) (charter).

    The work in this group is inspired by the high demands that modern applications–the charter mentions AI and LLMs–put on (e.g. and mainly) datacenter networks. The group will work on notification mechanism that nodes in the network that detect variations in quality can use to signal these promptly so that corrective action can be taken elsewhere in the network. W

    We do not recognize any public policy issues in this work as it is also purely operational

See the IETF datatracker for a full overview of chartering or re-chartering groups