Internet-Draft draft-ietf-opsawg-rfc5706bis-03.txt is now available. It is a
work item of the Operations and Management Area Working Group (OPSAWG) WG of
the IETF.

   Title:   Guidelines for Considering Operations and Management in IETF 
Specifications
   Authors: Benoit Claise
            Joe Clarke
            Adrian Farrel
            Samier Barguil
            Carlos Pignataro
            Ran Chen
   Name:    draft-ietf-opsawg-rfc5706bis-03.txt
   Pages:   49
   Dates:   2026-03-02

Abstract:

   New Protocols and Protocol Extensions are best designed with due
   consideration of the functionality needed to operate and manage them.
   Retrofitting operations and management considerations is suboptimal.
   The purpose of this document is to provide guidance to authors and
   reviewers on what operational and management aspects should be
   addressed when writing documents in the IETF Stream that define New
   Protocols or Protocol Extensions.

   This document obsoletes RFC 5706, replacing it completely and
   updating it with new operational and management techniques and
   mechanisms.  It also updates RFC 2360 to obsolete mandatory MIB
   creation.  Finally, it introduces a requirement to include an
   "Operational Considerations" section in new RFCs in the IETF Stream
   that define New Protocols or Protocol Extensions or describe their
   use (including relevant YANG Models), while providing an escape
   clause if no new considerations are identified.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-rfc5706bis/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-opsawg-rfc5706bis-03.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-rfc5706bis-03

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


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

Reply via email to