**Session Date/Time:** 18 Mar 2025 06:00

# netconf

## Summary
The NETCONF working group session covered a variety of topics, including updates on drafts related to NETCONF over Quick, list pagination, augmented by addition to the YANG library, external transaction ID for configuration tracing, adaptive subscription for YANG notifications, UDP-based transport for configured descriptions, YANG groupings for UDP clients and servers, subscriptions for distributed notifications, YANG notification transport capabilities, extensible YANG model for YANG Push notifications, YANG Push operational data observability enhancements, and an implementation of HTTPs notive draft with Kafka integration and related performance analysis. Decisions were made on several drafts, and action items were assigned for further development and review.

## Key Discussion Points

*   **Netconf Over Quick:** Discussions focused on stream usage, authentication, and security considerations. The importance of utilizing the mailing list for design discussions was emphasized.
*   **Yang Groupings for Quick Clients and Servers:** The group discussed and adopted the draft, addressing transport parameters like version, initial RTT, congestion control algorithm, max idle timeout, initial max streams, and keep-alive interval.
*   **List Pagination:** The working group discussed comments from the last call and agreed to move forward with the revised draft.
*   **Augmented By Addition to the Yang Library:** The scope of augmented by was discussed, focusing on direct augmentations.
*   **External Transaction ID for Configuration Tracing:** Minor changes were made, and the draft was deemed ready for last call.
*   **Adaptive Subscription for Yang Notifications:**  Minor updates based on reviews were discussed, including augmentation of the modification capabilities module and refining use cases, with request for last call.
*   **UDP-based transport for configured descriptions:** The group discussed the removal of private encoding options, DTLS encryption requirements, and adherence to NMDA architecture.
*   **Yang groupings for UDP clients and servers:** The group discussed whether a server should support multiple local ports on a single IP address and voted to maintain the current model with a single port per IP address.
*   **Subscription to distributed notifications:** Review comments were addressed, and the draft was deemed ready for IESG review.
*   **Yang notification transport capabilities:** TLS version support was discussed, and minor adjustments were made based on implementation feedback.
*   **Extensible Yang model for Yang Push Notifications:** Global enabling of the envelope and the addition of the observation timestamp extension were discussed.
*   **Yang Push operational data observability enhancements:** The group discussed simplifying Yang Push and potentially replacing XPaths with a more JSON-friendly YPath.
*   **HTTPs Notive Draft Implementation:** Student researchers presented their implementation, and integration with Kafka.  The group was asked for review.

## Decisions and Action Items

*   **Netconf over Quick:** Polish the draft based on feedback. Continue discussions on the mailing list. (Action: David Dai)
*   **Yang Groupings for Quick Clients and Servers:** Adopted by the working group. Version should potentially be a leaf-list to allow for supporting multiple versions of Quick (Action: Per Anderson).
*   **List Pagination:** Proceed with revised ID, remove delete operation in restconf draft (Action: Mahash Talili)
*   **Augmented By Addition to the Yang Library:** Follow the format of the deviation in the module states for augmented by (Action: Author)
*   **External Transaction ID for Configuration Tracing:** Ready for working group last call. Update security considerations using RFC 8407 bis. (Action: Jean)
*   **Adaptive Subscription for Yang Notifications:** Move to working group last call. (Action: Kent Watson)
*   **UDP-based transport for configured descriptions:** A volunteer will be located for Shepard (Action: Kent Watson)
*   **Yang groupings for UDP clients and servers:** Maintain the current model; the current version is ready to be progressed. A shepherd is needed (Action: Kent Watson)
*   **Subscription to distributed notifications:** Ready for IESG review; find a shepherd. (Action: Kent Watson)
*   **Yang notification transport capabilities:** Update the draft to reflect that TLS 1.2 is not obsolete. (Action: Benoit)
*   **Extensible Yang model for Yang Push Notifications:** Seek feedback on the updated text and implementation. (Action: Alex)
*   **Yang Push operational data observability enhancements:** Plan bi-monthly meetings with co-authors to resolve key points and issues, then request a virtual interim. (Action: Rob Wilson)

## Next Steps

*   Authors to incorporate feedback from the session into revised drafts.
*   Chairs to initiate working group last calls on drafts ready for progression.
*   Working group members to review and provide feedback on drafts via the mailing list.
*   Authors to engage in implementation and interoperability testing.
*   Shepherds to be assigned to drafts progressing to the IESG.
*   Plan virtual interim to discuss Yang Push (Action: Rob Wilson, Kent Watson)