[netconf] Roman Danyliw's Discuss on draft-ietf-netconf-netconf-event-notifications-20: (with DISCUSS)

[Roman Danyliw via Datatracker <[e-mail]>]

Roman Danyliw has entered the following ballot position for
draft-ietf-netconf-netconf-event-notifications-20: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-netconf-netconf-event-notifications/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

An easy to fix issue.

Section 8.  I agree with the brevity of this section as the more detailed
considerations can be found in [draft-ietf-netconf-subscribed-notifications].
[draft-ietf-netconf-subscribed-notifications] has a similar statement about
buggy subscribers, but also makes a SHOULD statement about operators monitoring
for odd behavior.  This text doesn’t include this monitoring recommendation but
does explicitly discuss terminating sessions.  Could the text in these two
sections please be reconciled. Perhaps with a reference such as:

“This document does not introduce additional Security Considerations for
dynamic subscriptions beyond those discussed in
[draft-ietf-netconf-subscribed-notifications].  In particular for NETCONF
subscribers …<use the current text> ”