Hi, Yes, I support working on YANG v2, and this document and the underlying github repository to back it are a good approach.
I do have concerns that the scope and goal of YANG v2 is not well defined - I think that we, as a community, need to understand and agree what the goal is of the next version of YANG and which of the 150+ proposed enhancements tracked by github we plan to fix and included in YANG v2. I don't think that an approach that just relies on individual contributors working on the issues they have most interest in is the best or right approach. To that end, I published a doc during the last IETF meeting (https://www.ietf.org/archive/id/draft-wilton-netmod-yang-next-agreement-00.html), with a goal of trying to further the discussion about both what specific issues tracked on the github issue tracker could/should go into the next version of YANG and also which changes should not end up in the next revision of YANG, and which changes we probably don't want in any version of YANG currently being considered. A comparison could be drawn to XPath. XPath v1, whilst it has some flaws, is still a small language. The subsequent versions of XPath are all significantly larger languages, with presumably a much greater implementation cost. Care is required, I think, that YANG v2 doesn't immediately follow this same path. Kind regards, Rob From: Lou Berger <[email protected]> Date: Monday, 27 April 2026 at 22:43 To: NetMod WG <[email protected]> Cc: NetMod WG Chairs <[email protected]> Subject: [netmod] WG adoption call: draft-yn-netmod-yang2-02 Hello, This email begins a 2-week adoption poll for: https://datatracker.ietf.org/doc/draft-yn-netmod-yang2/ Please voice your support or technical objections to adoption on the list by the end of the day (any time zone) May 11. Thank you, Lou (as Co-chair)
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
