<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-opsawg-rfc5706bis" target="https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-rfc5706bis-04">
   <front>
      <title>Guidelines for Considering Operations and Management in IETF Specifications</title>
      <author initials="B." surname="Claise" fullname="Benoît Claise">
         <organization>Everything OPS</organization>
      </author>
      <author initials="J." surname="Clarke" fullname="Joe Clarke">
         <organization>Cisco</organization>
      </author>
      <author initials="A." surname="Farrel" fullname="Adrian Farrel">
         <organization>Old Dog Consulting</organization>
      </author>
      <author initials="S." surname="Barguil" fullname="Samier Barguil">
         <organization>Nokia</organization>
      </author>
      <author initials="C." surname="Pignataro" fullname="Carlos Pignataro">
         <organization>Blue Fern Consulting</organization>
      </author>
      <author initials="R." surname="Chen" fullname="Ran Chen">
         <organization>ZTE</organization>
      </author>
      <date month="March" day="15" year="2026" />
      <abstract>
	 <t>   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 document a
   specification for New Protocols or Protocol Extensions or describe
   their use.

   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
   &quot;Operational Considerations&quot; 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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-opsawg-rfc5706bis-04" />
   
</reference>
