Session Date/Time: 21 Mar 2024 05:30

rift

Summary

This session focused on two main topics: an update on the rift base specification and a discussion regarding a new charter for the working group. Jordan provided an update on version 20 of the rift base spec, highlighting the editorial and structural improvements made based on AD and reviewer feedback. The chairs then presented a proposed new charter, including additional areas of work like key-value stores, segment routing, and AI/ML applications. The group discussed the scope of the proposed charter and the importance of prioritization.

Key Discussion Points

Rift Base Spec Update (v20):
- Significant improvements made based on AD and reviewer feedback.
- Changes included editorial, structural, formatting, and normative clarifications.
- Addressed issues with PDF rendering in IETF tools by recommending manual upload of locally generated copies.
- Clarified pseudo-code for tide generation, prefix attachment, tie processing, and level determination procedures.
- New acronym "Rain" (rift adjacency in rush notification) introduced.
- IANA considerations addressed and schema version bumped.
- Routing Directorate review received with minor editorial updates.
New Charter Discussion:
- The new charter aims to encompass existing work (base spec, YANG model, applicability statement) and expand into new areas.
- Proposed additions include: key-value store, segment routing, Leafringed topologies, policy-guided prefix, multicast, Dragonflight, zero-touch provisioning, flood reduction/reflection, EVP overlay, and using rift in AI/ML clusters.
- Discussion about the use of multicast for AI/ML and the need for clarity on its specific meaning in this context.
- Concerns raised about the breadth of the proposed charter and the need for prioritization.
- Importance of contributions from operational folks to drive adoption was highlighted.

Decisions and Action Items

Decision: The working group generally supports the new charter. The chairs will initiate a formal approval process, including a call for comments on the mailing list.
Action Item: Chairs to send the new charter text to the mailing list for review and feedback.
Action Item: Authors to publish version 21 of the rift base specification after the upload tools are available.
Action Item: Tony to focus on reviewing and brushing up the YANG document after the base spec is finalized.
Action Item: Individuals interested in specific areas of the new charter (e.g., AI/ML, Dragonflight) should contact Tony to coordinate efforts.

Next Steps

Formal approval process for the new charter via mailing list.
Publication of rift base specification version 21.
Continued work on the YANG model.
Initiation of work on new areas outlined in the proposed charter, based on contributor interest and prioritization.