Session Date/Time: 22 Jul 2024 20:00

netmod

Summary

The NetMod working group session at IETF 120 in Vancouver covered a range of topics, including document updates, post-last call discussions, and new draft proposals. Key discussions revolved around Yang module versioning, system-defined configuration updates, common Yang data models for scheduling, and approaches to managing device configurations. The session also addressed the future of Yang, including potential versions 1.2 and 2.0.

Key Discussion Points

Common Yang Data Types: The working group sought a volunteer editor to finalize the "6991 bis" document, which has been delayed in the publication process.
Common Interface Extension & Sub-interface: The status of these expired drafts was discussed, with a plan to get them resubmitted for last call after addressing final edits.
Yang Module Versioning: Updates on two drafts related to Yang module versioning and semantic versioning were presented. Authors requested a new working group last call.
Yang File Naming Convention: Per presented an experimental draft to standardize file naming with YANG semantic versioning, there was a discussion about whether it should be proposed standard instead.
System-Defined Configuration Update: The working group reviewed updates to the draft, focusing on issues raised during the last call, including what needs to be copied from system to running and merge behavior. Another last call was decided.
Common Scheduling Yang Model: The authors presented updates to the common scheduling data model and requested working group review, along with an early review by the Yang doctors.
Immutable Flag: The group discussed clarifications on the immutable flag and its impact on NetConf and RESTCONF specifications. A potential liaison with 3GPP was considered.
Yang Full Embed: A proposal for reusing device-level modules at the network level was presented. Concerns were raised about complexity and potential conflicts with existing Yang mechanisms.
Device Configuration as a Service: An approach to managing device configurations as a service through the SDM controller was presented, sparking discussion on conflict management and inventory alignment.
Yang Next: Ken Watsen presented his work on Yang next, including refactoring the existing Yang specification. The discussion focused on whether to pursue Yang 1.2 and/or Yang 2.0, the approach, and the benefits to the community.
Large Scale Management: The BBF presented a Liaison letter on scaling issues of YANG modules with the suggestion that certain data nodes can be moved deeper into the YANG tree.

Decisions and Action Items

Common Yang Data Types: The working group will seek a volunteer editor to finalize the "6991 bis" document.
Yang File Naming Convention: This document will be considered for adoption as a working group document and proceed toward a proposed standard rather than experimental RFC.
System-Defined Configuration Update: Another working group last call will be initiated.
Immutable Flag: Rob Wilson volunteered to draft a liaison statement to 3GPP regarding the document's status.
Yang Full Embed: The authors will work offline with the authors of packages to see whether or not they can leverage the same mechanism or a slight modification of it
Yang Next: Kent Watsen will prepare a document outlining the motivation and objectives for Yang next to facilitate further discussion.

Next Steps

Authors of the discussed drafts will incorporate feedback from the meeting and submit updated versions.
The working group will continue discussions on the mailing list, particularly regarding the device configuration service approach.
The Chairs will send out information on the various action items discussed.