Hi Reshad, Thanks again for your detailed review and comments. Sorry for the late revert. I was traveling and away from work.
I have addressed all your comments and uploaded version -03 to the datatracker. Datatracker link: https://datatracker.ietf.org/doc/draft-rtv-netmod-yang-subtree-replacement/ Changes in draft-rtv-netmod-yang-subtree-replacement-03: - Previously (in -01) you had This extension MUST be used only with 'status deprecated'. But you don't have text anymore, is that on purpose? I thought it was useful. That was an oversight on my part. I have restored the constraint in the extension description. ``` This extension MUST be used only with nodes that have 'status deprecated'. The parent node containing this extension MUST include a 'status deprecated' statement. ``` - In the extension descriptions, you should also add text such as "The statement MUST only be a sub-statement of a leaf, container, etc” ADDRESSED: Added explicit substatement restrictions per your suggestion: ``` This statement MAY be used as a substatement of container, list, leaf, leaf-list, choice, case, anydata, and anyxml statements. It MUST NOT be used as a substatement of rpc, action, or notification statements. ``` I have used MAY instead of MUST since the extension is optional and we could have deprecated nodes without a deprecation-info. - And also Zero or one 'deprecated-info' statement per parent statement is allowed. Same for obsoletion-info. I have added cardinality specification to the extension description. However, I specified "zero or more" rather than "zero or one" to support scenarios where a deprecated node has multiple valid migration paths. Also on more detailed analysis I felt obsoletion-info is better removed. We had agreed in IETF 123 that keeping this information post obsoletion may bloat up the YANG unnecessarily. The extension is now focused solely on deprecated nodes. - Nit: you've removed names from the Acknowledgement section and replaced them with NTEMOD WG. I believe it's good form to keep names of people who have provided comments. Have restored them all. Thanks again Reshad Rahman, Kent Watsen, Lou Berger, Balazs Lengyel, Deepak Rajaram, and Rob Wilton for your inputs on the draft. Rgds, Rajesh From: Reshad Rahman <[email protected]> Date: Thursday, January 15, 2026 at 8:48 AM To: NETMOD WG <[email protected]>, Rajesh Tarakkad Venkateswaran (rtv) <[email protected]> Cc: Veena Ramamoorthy (vemoorth) <[email protected]>, Sarthak Jain (sarthakj) <[email protected]>, Venkata Harish Nagamangalam (vnagaman) <[email protected]>, Sai Venkata Giri Karnati (saikarna) <[email protected]>, Rob Wilton (rwilton) <[email protected]> Subject: Re: [netmod] Re: Updated draft: draft-rtv-netmod-yang-subtree-replacement-01 Hi Rajesh, Thanks for making the changes. I went through the diff quickly and here are some comments: - Previously (in -01) you had This extension MUST be used only with 'status deprecated'. But you don't have text anymore, is that on purpose? I thought it was useful. - In the extension descriptions, you should also add text such as "The statement MUST only be a sub-statement of a leaf, container, etc" - And also Zero or one 'deprecated-info' statement per parent statement is allowed. Same for obsoletion-info. - Nit: you've removed names from the Acknowledgement section and replaced them with NTEMOD WG. I believe it's good form to keep names of people who have provided comments. Regards, Reshad. On Wednesday, January 14, 2026 at 06:49:30 PM EST, Rajesh Tarakkad Venkateswaran (rtv) <[email protected]> wrote: Hi Reshad, Thank you for your valuable feedback on the draft. I have addressed both of your observations and uploaded version -02 to the datatracker. Datatracker link: https://datatracker.ietf.org/doc/draft-rtv-netmod-yang-subtree-replacement/ Changes in draft-rtv-netmod-yang-subtree-replacement-02: ISSUE 1: Missing <CODE BEGINS> Markers - ADDRESSED Your observation: "the module containing the deprecated-info extension doesn't have the <CODE BEGINS> marker" Fixed: * Added <CODE BEGINS> and <CODE ENDS> markers to the ietf-lifecycle-ext module per RFC 8407bis requirements * Module filename: [email protected] * The datatracker now successfully extracts the YANG module (confirmed via xym tool output) * YANG validation is now operational and passes cleanly ISSUE 2: Incorrect Section Structure - ADDRESSED Your observation: "module ietf-deprecated-info is in section 5.1 which is under 'Section 5 - Example implementation'" Fixed: * Created new normative Section 4: "YANG Module" * Moved ietf-lifecycle-ext module to Section 4.1 (normative placement) * Section 5: "Implementation of Lifecycle Tuples Across Various Scenarios" * Section 6: "Example Implementation" (now contains only test/example modules) * Clear separation between normative YANG module and example implementations Additional Improvements: * Added complete RFC 8407-compliant copyright boilerplate to the YANG module * Added proper revision statement with reference to this draft * Fixed all YANG validation warnings (pyang shows 0 warnings) * Module now includes proper contact information and BCP 14 keywords notice Validation Status: * YANG module extraction: Successful * pyang validation: 0 warnings (previously 2) * yanglint validation: Pass * idnits: 1 minor warning (non-ASCII typography, cosmetic only) The draft is now properly structured with the normative YANG module in its own section, and all YANG validation checks pass successfully. Please let me know if you have any additional feedback or concerns. Best regards, Rajesh From: Reshad Rahman <[email protected]> Date: Thursday, January 15, 2026 at 1:21 AM To: NETMOD WG <[email protected]>, Rajesh Tarakkad Venkateswaran (rtv) <[email protected]> Cc: Veena Ramamoorthy (vemoorth) <[email protected]>, Sarthak Jain (sarthakj) <[email protected]>, Venkata Harish Nagamangalam (vnagaman) <[email protected]>, Sai Venkata Giri Karnati (saikarna) <[email protected]>, Rob Wilton (rwilton) <[email protected]> Subject: Re: [netmod] Re: Updated draft: draft-rtv-netmod-yang-subtree-replacement-01 Hi Rajesh, authors, On the datatracker page, there is no YANG validation for this document. I think this is because the module containing the deprecated-info extension doesn't have the <CODE BEGINS> marker, see https://www.ietf.org/archive/id/draft-ietf-netmod-rfc8407bis-28.html#name-code-components And module ietf-deprecated-info is in section 5.1 which is under "Section 5 - Example implementation", I'm assuming that it's a mistake in that 5.1 is normative and not an example? Regards, Reshad. On Wednesday, January 14, 2026 at 01:11:20 PM EST, Rajesh Tarakkad Venkateswaran (rtv) <[email protected]> wrote: Hello all, Happy new year !!! Gentle reminder that we have a new version that incorporates the comments we discussed at IETF123. Thanks in advance for your review and feedback. Rgds, Rajesh From: Rajesh Tarakkad Venkateswaran (rtv) <[email protected]> Date: Tuesday, December 30, 2025 at 11:22 PM To: NETMOD WG <[email protected]> Cc: Veena Ramamoorthy (vemoorth) <[email protected]>, Sarthak Jain (sarthakj) <[email protected]>, Venkata Harish Nagamangalam (vnagaman) <[email protected]>, Sai Venkata Giri Karnati (saikarna) <[email protected]>, Rob Wilton (rwilton) <[email protected]> Subject: Updated draft: draft-rtv-netmod-yang-subtree-replacement-01 Dear NETMOD Working Group, We've submitted draft-rtv-netmod-yang-subtree-replacement-01, which incorporates the feedback from the IETF 123 discussion. Key changes from -00: • Renamed extension to deprecated-info • Extension must be removed when node becomes obsolete • Added formal ABNF grammar for lifecycle tuples • Enhanced one-to-many migration support with per-path type prefixes • Added design rationale sections addressing working group feedback Full details in the Change Log (Appendix A). Datatracker: https://datatracker.ietf.org/doc/draft-rtv-netmod-yang-subtree-replacement/ <https://datatracker.ietf.org/doc/draft-rtv-netmod-yang-subtree-replacement/> We welcome continued feedback from the working group. Best regards, Rajesh T V _______________________________________________ netmod mailing list -- [email protected]<mailto:[email protected]> To unsubscribe send an email to [email protected]<mailto:[email protected]>
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
