Joe, Authors, Contributors (which includes everyone in the working group who has commented on the document or contributed in any other way),
Thank you for bringing the discussion to a close. At this point, our plan is to move forward with the publication request. WG, If you believe you have a comment that has not previously been addressed now is the time to re-raise. Thank you all, Lou ________________________________ On March 16, 2025 12:49:01 PM "Joe Clarke (jclarke)" <jclarke=40cisco....@dmarc.ietf.org> wrote: Hello, NETMOD! The authors of the three YANG Versioning drafts would like to provide a consolidated summary of the last WGLC feedback for these documents. This will save some time in the meeting since we won’t need a presentation slot. The authors received comments from Andy and Jürgen, and we addressed those comments, replying to both as to what we did. Below is a summary: YANG Module Versioning (draft-ietf-netmod-yang-module-versioning) * Comment thread https://mailarchive.ietf.org/arch/msg/netmod/iiHWLodAPVwW0Ztqdap_DSZYcOg/ * Module ietf-yang-status-conformance (prefix ys-conf) has been renamed to ietf-yang-library-status (prefix yls) * Added text in 3.1.1 to clarify that changes in imported modules do not impact a module’s backwards compatibility (non-transitive) * Instead of defining our own pattern, we now use date-no-zone from 6991-bis for the revision-date type * In Appendix A we clarified an example for changing the type of a node and added a reference to section 11 of RFC7950. YANG Semver (draft-ietf-netmod-yang-semver) * Comment threads: https://mailarchive.ietf.org/arch/msg/netmod/VC6_z42N0oReGJxGsqETBFqD_Uw/ and https://mailarchive.ietf.org/arch/msg/netmod/zku6Utcisf7t7jDGS7p5tYQovPQ/ * Changed prefix from “ys” to “ysv” * Created an appendix to show examples of _COMPAT modifier use * Clarify how import by YANG Semver works with respect to comparing versions * Simplify the pre-release metadata requirements for modules in adopted I-Ds * Add a range limit to the version string (max 128 characters) YANG Filename Changes (draft-ietf-netmod-yang-module-filename) * Comment thread: https://mailarchive.ietf.org/arch/msg/netmod/gsEKtI-Cs-Kjv69lxFxPjGgVtaM/ * Allow current schema * mod...@2025-03-19.yang * Allow new schema * Use YANG semantic version (ysv:version) * Use hash sign (#) as delimiter * module#1.2.3.yang * Cleared most WG comments in -01 * Did not update text on multiple YANG module files. Why? * Authors believe multiple filenames are allowed * So, guidance is given, but it is not a MUST: * Typically, only one file name SHOULD exist for the same module (or submodule) revision. Two file names, one with the revision date and another with the YANG semantic version, MAY exist for the same module (or submodule) revision, e.g., when migrating from one scheme to the other. At this point, the authors feel we are done, and we’d like these documents to move forward for publication. Joe (on behalf of the authors/editors)
_______________________________________________ netmod mailing list -- netmod@ietf.org To unsubscribe send an email to netmod-le...@ietf.org
