Operations and Management Area Working Group (opsawg)
| WG | Name | Operations and Management Area Working Group | |
|---|---|---|---|
| Acronym | opsawg | ||
| Area | Operations and Management Area (ops) | ||
| State | Active | ||
| Charter | charter-ietf-opsawg-05 Approved | ||
| Document dependencies | |||
| Additional resources |
GitHub organization Issue tracker Wiki Zulip stream |
||
| Personnel | Chairs | Benoît Claise, Joe Clarke | |
| Area Director | Mahesh Jethanandani | ||
| Mailing list | Address | opsawg@ietf.org | |
| To subscribe | https://www.ietf.org/mailman/listinfo/opsawg | ||
| Archive | https://mailarchive.ietf.org/arch/browse/opsawg/ | ||
| Chat | Room address | https://zulip.ietf.org/#narrow/stream/opsawg |
Charter for Working Group
The Operations and Management Area receives occasional proposals for the development and publication of RFCs dealing with operational and management topics. The OPSAWG will serve as the forum to:
- Develop such work items that are not in the scope of an existing OPS WG and do not justify the formation of a new WG or belong to a WG that has already concluded. The OPSAWG mailing list will serve as a discussion forum for such work items when they arise, and the WG will meet to discuss if there are active proposals.
- Find a more appropriate WG in the IETF for the work if OPSAWG is not the right forum.
- Help collect work items and gauge interest to determine whether a new WG should be chartered.
Examples include the advancement of documents on the standards track, application statements, maintenance, and minor extensions of documents that were developed in working groups that have concluded, e.g., IPFIX, network or service level YANG modules, and tools for the Operations and Management Area.
The OPSAWG will undertake only work items that have been proven to have at least a reasonable level of interest from the operators, vendor and user community and have a committed number of editors and reviewers. It is not within the scope of the OPSAWG to pick up any failed work of other OPS WG.
Milestones
| Date | Milestone | Associated documents |
|---|---|---|
| Apr 2026 | Submit IM and DM for Packet Discard Reporting as Proposed Standard |
draft-ietf-opsawg-discardmodel
|
| Dec 2025 | Submit End-Site Prefix Lengths as Proposed Standard |
draft-ietf-opsawg-prefix-lengths
|
| Dec 2025 | Submit Guidelines for Characterizing "OAM" as a BCP |
draft-ietf-opsawg-oam-characterization
|
| Dec 2025 | Submit Alternate-Marking IE for IPFIX as Proposed Standard |
draft-ietf-opsawg-ipfix-alt-mark
|
| Dec 2025 | Submit YANG Data Model and RADIUS Extension for Policy-based Network Access Control as Proposed Standard |
draft-ietf-opsawg-ucl-acl
|
| Dec 2025 | Submit PCAP and PCAPng Link Type as Informational |
draft-ietf-opsawg-pcaplinktype
|
| Dec 2025 | Submit PCAPng File Format as Informational |
draft-ietf-opsawg-pcapng
|
| Dec 2025 | Submit PCAP Capture File Format as Historic |
draft-ietf-opsawg-pcap
|
| Sep 2025 | Submit Contextualized Telemetry Data as Proposed Standard |
draft-ietf-opsawg-collected-data-manifest
|
| Sep 2025 | Submit On Path Telemetry in IPFIX as Proposed Standard |
draft-ietf-opsawg-ipfix-on-path-telemetry
|
| Sep 2025 | Submit GTP-U in IPFIX as Proposed Standard |
draft-ietf-opsawg-ipfix-gtpu
|
| Sep 2025 | Submit TACACS+ YANG Model as Proposed Standard |
draft-ietf-opsawg-secure-tacacs-yang
|
| Jul 2025 | Submit TACACS+ TLS as Proposed Standard |
draft-ietf-opsawg-tacacs-tls13
|