The Operations and Management Area Working Group (opsawg) WG in the
Operations and Management Area of the IETF is undergoing rechartering. The
IESG has not made any determination yet. The following draft charter was
submitted, and is provided for informational purposes only. Please send your
comments to the IESG mailing list ([email protected]) by 2025-05-01.

Operations and Management Area Working Group (opsawg)
-----------------------------------------------------------------------
Current status: Active WG

Chairs:
  Joe Clarke <[email protected]>
  BenoĆ®t Claise <[email protected]>

Assigned Area Director:
  Mahesh Jethanandani <[email protected]>

Operations and Management Area Directors:
  Mahesh Jethanandani <[email protected]>
  Mohamed Boucadair <[email protected]>

Mailing list:
  Address: [email protected]
  To subscribe: https://www.ietf.org/mailman/listinfo/opsawg
  Archive: https://mailarchive.ietf.org/arch/browse/opsawg/

Group page: https://datatracker.ietf.org/group/opsawg/

Charter: https://datatracker.ietf.org/doc/charter-ietf-opsawg/

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 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 WG.

Milestones:

  Jul 2025 - Submit TACACS+ TLS as Proposed Standards

  Sep 2025 - Submit TACACS+ YANG Model as Proposed Standard

  Sep 2025 - Submit GTP-U in IPFIX as Proposed Standard

  Sep 2025 - Submit On Path Telemetry in IPFIX as Proposed Standard

  Sep 2025 - Submit Contextualized Telemetry Data as Proposed Standard

  Dec 2025 - Submit PCAP Capture File Format as Historic

  Dec 2025 - Submit PCAPng File Format as Informational

  Dec 2025 - Submit PCAP and PCAPng Link Type as Informational

  Dec 2025 - Submit YANG Data Model and RADIUS Extension for Policy-based
  Network Access Control as Proposed Standard

  Dec 2025 - Submit Alternate-Marking IE for IPFIX as Proposed Standard

  Dec 2025 - Submit Guidelines for Characterizing "OAM" as a BCP

  Dec 2025 - Submit End-Site Prefix Lengths as Proposed Standard

  Apr 2026 - Submit IM and DM for Packet Discard Reporting as Proposed
  Standard



_______________________________________________
OPSAWG mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to