Session Date/Time: 27 Mar 2023 04:00

netconf

Summary

The netconf working group meeting at IETF 116 covered a variety of topics, including updates on chartered work group items like HTTP Notify, client server suites, UDP Notify, disputed Notify, tailor-one-dot-three, transaction ID, and tracing mechanisms. The meeting also discussed non-chartered items like Netconf private candidates, young model for netconf event notifications, support provisioning, hostname sequencing, and incident management for phonetic services. Several polls were conducted to gauge working group interest in specific proposals. A key theme was the need for alignment and a coherent framework for transaction ID and tracing related drafts.

Key Discussion Points

Netconf Next: Discussion on initiating work on Netconf Next and associated Github issues, including banner encoding and binary notifications. The need for volunteers to drive this work forward was emphasized.
UDP Notify Draft: Clarification of observation domain ID and message ID sequence. Discussion of adding a Udp client/server grouping similar to the TCP client/server suite draft. A request was made for a working group last call after addressing these points.
Disputed Notify Draft: Primarily editorial changes. A request was made for a working group last call, concurrent with UDP Notify.
List Pagination: Discussion on snapshot recognition and cursor-based sorting. A poll indicated a lack of strong interest in locale-based sorting, but more concrete examples were requested for the mailing list.
Netconf with TLS: Discussion of changes made to update RC7589 for TLS 1.3. A shorter last call was suggested due to the scope of the changes, especially the title change. The upcoming TLS working group discussion on deprecating TLS 1.2 was mentioned.
External Transaction ID: Presenting the external collection Id for configuration increasing and there was another proposition to do configuration testing from young. Discussion on converging with the test context extension draft, potentially switching from transaction IDs to case IDs. Open questions remain on how to pass client IDs.
Transaction ID, Trace Context, and Private Candidates: An overview of five related drafts, including the adopted transaction ID draft, configuration trace, W3C trace, private candidates, and existing context drafts. A key focus was on defining a coherent framework for these drafts, ensuring optionality and independent implementability. Aligning terminology and behavior across documents was deemed crucial. Opinions diverged on whether a separate "framework" document was needed, with suggestions ranging from incorporating relationships into existing drafts to creating an architecture document.
Private Candidates: Discussion on whether the private candidates draft should support RESTCONF. A poll showed a split in the working group. The authors are focusing on definitions and proposed solutions, with examples of conflict resolution.
Netconf Event Notifications and Yang Push Headers: discussion to move forward with a young model, add network device metrics for identification from the new device as well as revision of module for notification sequencing.
Incident Management for Nano Services: Presentation of a new draft proposing incident management technology for network services. Discussion on its relationship to alarm information, KPI information, and maintenance information. Feedback was requested, including comparison to the SAM Tetra framework and alignment with the D-MIMO draft in OPS.

Decisions and Action Items

UDP Notify Draft: Action: Alexa to revise the draft to include a Udp client/server grouping and address Rob Wilson's comments.
List Pagination: Action: Per to formulate concrete examples of use cases for locale-based sorting and take them to the mailing list.
Netconf with TLS: Decision: A shorter (two-week) working group last call will be conducted.
External Transaction ID: Action: Jean to work on the next version of the draft, incorporating the case ID concept and addressing how to pass client IDs.
Transaction ID and Related Drafts: Action: Authors of the transaction ID, trace context, and private candidates drafts to collaborate on aligning terminology, use cases, and behavior to create a coherent framework.
Netconf Event Notifications and Yang Push Headers: The draft is to be progressed with a young model, the working group to participate with a discussion on the list.
Clients server Suite of draft:
- Rob Wilson to send in comments from reviews completed.

Next Steps

Mailing list discussions on various topics, including locale-based sorting for list pagination and potential adoption of the Thomas' YANG module and a call for adoption vote.
Continued implementation experience and feedback gathering for the transaction ID drafts.
Collaboration among authors to align terminology and behavior across transaction ID and related drafts.
Publication of the zero-one version of the private candidates draft.
Progress and revisions to drafts will be continued with the working group.