[netconf] Current status of draft-ietf-netconf-distributed-notif draft.

[Mahesh Jethanandani <[e-mail]>]

Hi Authors,

I've been going through the Last Call review record for draft-ietf-netconf-distributed-notif (currently at -21). Thanks for the thorough back-and-forth with Schönwälder, Qu, Halpern, Westerlund, Obser, and Björklund — most of it is cleanly closed with explicit reviewer sign-off. One thing still needs attention, plus a few smaller loose ends worth a look:

1. YANG validation error in -21 (not caught by any directorate review)
   The datatracker validation for -21 reports a real error: the "message-publisher-ids"
   grouping's leaf-list `message-publisher-id` has `min-elements 1` (i.e., it's mandatory),
   and it's introduced via `augment "/sn:subscriptions/sn:subscription" { uses
   message-publisher-ids; }` into ietf-subscribed-notifications with no `when` guard. Per
   RFC 7950 §7.17, a mandatory node can't be added into another module's data tree this way
   without a conditional. There's also a minor canonical-ordering issue in the same
   leaf-list (`config` should precede `min-elements`). Could you take a look and post a fix?

A few smaller items from the GenArt review (Joel Halpern) that came up in discussion but
didn't make it into the text — worth a quick look:

  - Section 7 still has the two consecutive MUST statements about subscription state
    change notifications that Joel found redundant/confusing; the clarifying sentence
    discussed in the thread doesn't appear to have been added.
  - Whether the document should say explicitly that only a single level of delegation
    is supported (Joel's ask), since the current text only implies it architecturally.

Thanks again for the work on this one

Mahesh Jethanandani
[e-mail]