[yang-doctors] draft-ietf-opsawg-rfc5706bis-01 early Yangdoctors review

Martin Björklund via Datatracker <noreply@ietf.org> Mon, 02 February 2026 09:21 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: yang-doctors@ietf.org
Delivered-To: yang-doctors@mail2.ietf.org
Received: from [10.244.6.51] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id C4DE8B086C71; Mon, 2 Feb 2026 01:21:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Martin Björklund via Datatracker <noreply@ietf.org>
To: yang-doctors@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <177002406159.2359654.6725980526806889828@dt-datatracker-77f8b84995-z4hzn>
Date: Mon, 02 Feb 2026 01:21:01 -0800
Message-ID-Hash: 66PYRDVH47KTATZP2A3QHR7DP3TKVL5W
X-Message-ID-Hash: 66PYRDVH47KTATZP2A3QHR7DP3TKVL5W
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-yang-doctors.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-opsawg-rfc5706bis.all@ietf.org, opsawg@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Martin Björklund <mbj+ietf@4668.se>
Subject: [yang-doctors] draft-ietf-opsawg-rfc5706bis-01 early Yangdoctors review
List-Id: Email list of the yang-doctors directorate <yang-doctors.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/wTwd0YN4SLctgRBXU9DRrB44Qng>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Owner: <mailto:yang-doctors-owner@ietf.org>
List-Post: <mailto:yang-doctors@ietf.org>
List-Subscribe: <mailto:yang-doctors-join@ietf.org>
List-Unsubscribe: <mailto:yang-doctors-leave@ietf.org>

Document: draft-ietf-opsawg-rfc5706bis
Title: Guidelines for Considering Operations and Management in IETF Specifications
Reviewer: Martin Björklund
Review result: Ready with Nits

Hi,

This is my YANG doctors review of draft-ietf-opsawg-rfc5706bis-01.

This document contains general guidelines for operational
considerations in IETF documents.  From a YANG point of view, it
doesn't contain any YANG models, but provides some guidelines on when
and how to use YANG.

I have just one question and it is regarding the recommendations for
Information Models (IM).  The draft has an implicit recommendation in
section 5.3:

  Although this document recommends using English text (the official
  language for IETF specifications) to describe an Information Model,
  including a complementary YANG module helps translate abstract
  concepts into implementation-specific Data Models.

It later says in 5.3.1:

  When defining an Information Model using YANG Data Structure
  Extensions [...]

It is not clear to me what you mean here.  In section 5.3 it seems you
recommend including a Data Model YANG module (not an IM, since the IM
is in english text).  But then in 5.3.1 you mention a YANG module
for the IM as well, but there is no other discussion about using YANG
for the IM.

Also, I think it would be clearer to have an explicit recommendation
in section 5.3:

  This document recommends using English text...


/martin