Meeting Note - 2025-10-01

[lgecse]

Participant	Join/Leave Time
László Puskás (Cisco)	17:07 / 18:00
Sándor Magyari (Cisco)	17:06 / 18:00
Laszlo Gecse (Cisco)	17:07 / 18:00
Cheng Li (Huawei)	17:22 / 18:00
Luca Muscariello (Cisco)	17:06 / 18:00
Luigi Iannone (Huawei)	17:06 / 18:00
Sam Betts (Cisco)	17:06 / 18:00
János Sarusi-Kis (Cisco)	17:06 / 18:00
Antoine F (Huawei)	17:06 / 18:00
Mauro Sardara (Cisco)	17:06 / 18:00
Michele Papalini (Cisco)	17:06 / 18:00
Bing Liu (Huawei)	17:40 / 18:00

The meeting focused on upcoming changes to the control plane, API updates, documentation improvements, and plans for future language bindings while emphasizing clarity and repository management.

• Next release introduces a control plane with a reconciliation mechanism for node connections.
• New deployment templates facilitate testing between the control plane and Slim nodes.
• Major changes in the Python API for the data plane require a migration guide.
• API naming conventions simplified for clarity, replacing terms like "anycast" and "unicast."
• Documentation updates will clarify interaction patterns and expected behaviors.
• Ongoing improvements focus on enhancing clarity in communication patterns and terminology.
• Future language bindings, including Ruby, are considered to support user requirements.
• Discussed the need to externalize language bindings and maintain a Rust-focused repository.
• Emphasized the importance of separating repositories for different programming languages to streamline maintenance.

Action items:

• Ensure that the documentation is updated to clarify the differences between unicast, anycast, and multicast, particularly regarding their interaction patterns and expected behaviors.
• Track the tasks that need to be completed for the upcoming v0.7.0 release in a GitHub project.
• Consider creating a draft release candidate for testing purposes once most work has been merged for v0.6.0.
• Investigate the possibility of adding Ruby bindings for the API as per Sam’s request.
• Prepare the v0.7.0 plan to externalize Python and Ruby bindings from the slim repo.
• Start planning for JavaScript bindings in a future release (potentially v0.8.0).
• Discuss the ongoing authentication issues related to non-HDP transports and ensure code compliance with standards.