Dear Jürgen,

Thanks for the comment.

Just to give the full picture here and put netmod in the loop as well.  
Revision is part of YANG as defined in Section 7.1.9 in RFC 6020 
(https://www.rfc-editor.org/rfc/rfc6020.html#section-7.1.9) already. Its use 
when importing other modules are being described in Section 5.1.1 
(https://www.rfc-editor.org/rfc/rfc6020.html#section-5.1.1). 

YANG push has the same requirements that in order to describe the semantic 
properly, a reference to revision is needed since the semantics can evolve over 
time.

However, where you specifically point at is that draft-ietf-netmod-yang-semver 
(https://datatracker.ietf.org/doc/html/draft-ietf-netmod-yang-semver) and 
draft-ietf-netmod-yang-module-versioning 
(https://datatracker.ietf.org/doc/html/draft-ietf-netmod-yang-module-versioning)
 adding the capability that newer revision doesn't have to be backward 
compatible or not which is being reflected in 
draft-tgraf-netconf-yang-notifications-versioning as well.

Best wishes
Thomas

-----Original Message-----
From: netconf <[email protected]> On Behalf Of Jürgen Schönwälder
Sent: Tuesday, May 16, 2023 8:17 AM
To: Mahesh Jethanandani <[email protected]>
Cc: netconf <[email protected]>; netconf-chairs <[email protected]>
Subject: Re: [netconf] Adoption poll for 
draft-tgraf-netconf-yang-notifications-versioning

So here we go. The change from (module, path) names to (module, path,
version) names will trigger a series of followup works, like this one.
Adding version numbers to how we name things is a fundamental change of YANG 
and its protocols (and people still pretend this change can be done without 
even changing the YANG version number).

I doubt that fixing things piecewise is the right strategy but I fear this is 
where the IETF is heading. The result will likely look like some patchwork 
glued together by some implementation specific bits and pieces.

/js

On Mon, May 15, 2023 at 01:42:14PM -0700, Mahesh Jethanandani wrote:
> 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)
> 
> 
> 
> 
> 

> _______________________________________________
> netconf mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/netconf


-- 
Jürgen Schönwälder              Constructor University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <https://constructor.university/>

_______________________________________________
netconf mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netconf

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to