[yang-doctors] draft-ietf-netconf-distributed-notif-17 ietf last call Yangdoctors review

Martin Björklund via Datatracker <noreply@ietf.org> Wed, 25 February 2026 13:30 UTC

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
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <177202622983.2538513.16223609857971033741@dt-datatracker-6ff7c68975-7k42g>
Date: Wed, 25 Feb 2026 05:30:29 -0800
Message-ID-Hash: INAIN4LJO5EK4VQAFGE3UF2NAU6S5SWB
CC: draft-ietf-netconf-distributed-notif.all@ietf.org, last-call@ietf.org, netconf@ietf.org
Reply-To: Martin Björklund <mbj+ietf@4668.se>
Subject: [yang-doctors] draft-ietf-netconf-distributed-notif-17 ietf last call Yangdoctors review
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/79azUCQBDUPBuymjTtI9v61ccXg>

Document: draft-ietf-netconf-distributed-notif
Title: Subscription to Notifications in a Distributed Architecture
Reviewer: Martin Björklund
Review result: Ready with Nits

This is my second YANG doctor's review of this document.

My only comment is about the terminology.  This document claims that it imports
the term "Capability" from RFC 9196, but RFC 9196 doesn't define this term. 
That RFC defines a generic capability model and then defines some specific
capabilities, so it is unclear what this term is supposed to refer to.

The term Global Capability is defined as "The overall subscription
capability..."  What is a "subscription capability"?

It would perhaps help if there was an example that clearly mapped these terms
to specifics.

/martin

[yang-doctors] draft-ietf-netconf-distributed-not… Martin Björklund via Datatracker
[yang-doctors] Re: draft-ietf-netconf-distributed… Thomas.Graf
[yang-doctors] Re: draft-ietf-netconf-distributed… Thomas.Graf
[yang-doctors] Re: draft-ietf-netconf-distributed… Martin Björklund