Re: [netconf] Adoption poll for draft-tgraf-netconf-yang-notifications-versioning

[[e-mail]]

Dear Zhenqiang,

Thanks a lot for the review and feedback. These are exactly the challenges we are addressing with this document.


  *   Since network elements only support one revision, I wonder the behavio and result when a network element receives a subsription with an old revision which it doesn't support?

In Section 2 (https://datatracker.ietf.org/doc/html/draft-tgraf-netconf-yang-notifications-versioning-03#name-extend-the-datastore-select) we give the network operator the ability to subscribe to a xpath/sub-tree filter regardless its revision, to a specific revision or to a revision which needs to be backward compatible to a revision-label (semantic revision). If a specific revision or backward compatible to revision-label is chosen and such a subscription can't be established, no messages are being published on the network node.


  *   What should the receiver such as NMS do when it receives yang push notification with revision that is not the one the receiver subscribes?

In case of not specifying a specific revision or the revision changes but is still backward compatible to the prevision revision, the YANG push receiver (NMS) would now have the capability with the described enhancements described in Section 3 (https://datatracker.ietf.org/doc/html/draft-tgraf-netconf-yang-notifications-versioning-03#section-3) to learn that semantics have changed and being capable to obtain through netconf <get-schema> the new semantics and adjust its data transformation accordingly.

Best wishes
Thomas

From: netconf <[e-mail]> On Behalf Of [e-mail]
Sent: Thursday, June 8, 2023 8:59 AM
To: Mahesh Jethanandani <[e-mail]>; Netconf <[e-mail]>
Cc: netconf-chairs <[e-mail]>
Subject: Re: [netconf] Adoption poll for draft-tgraf-netconf-yang-notifications-versioning

Hello All,

I have read the doc and I support its adoption. Please consider the concern as below.

Since network elements only support one revision, I wonder the behavio and result when a network element receives a subsription with an old revision which it doesn't support?

What should the receiver such as NMS do when it receives yang push notification with revision that is not the one the receiver subscribes?

________________________________
Best Regards,
Zhenqiang Li

[e-mail]<mailto:[e-mail]>

From: Mahesh Jethanandani<mailto:[e-mail]>
Date: 2023-05-16 04:42
To: netconf<mailto:[e-mail]>
CC: netconf-chairs<mailto:[e-mail]>
Subject: [netconf] Adoption poll for draft-tgraf-netconf-yang-notifications-versioning
All,

This is start of a two week poll on making draft-tgraf-netconf-yang-notifications-versioning-03 a working group
document. Please send email to the list indicating "yes/support” or "no/do not support".  If indicating no, please state your reservations
with the document.  If yes, please also feel free to provide comments you'd like to see addressed once the document is a WG document.

The poll ends May 31.

Mahesh and Kent (as co-chairs)