Session Date/Time: 21 Sep 2023 13:00

ROLL

Summary

The ROLL Working Group meeting reviewed the status of several drafts, discussed proposed milestone dates, and outlined next steps for progressing documents towards IESG submission. Key technical discussions included clarifying state transitions in RNFT, the "should" vs. "must" dilemma for MaxPlusCost in NSA Extension, and the interpretation of MOP values in MOPEX. The group decided to hold a session at IETF 118 in Prague and agreed on establishing a cadence for regular interim meetings. During open floor, Co-chair Dominique Barthel announced his intention to step down within the next six months, inviting volunteers to consider the role.

Key Discussion Points

Introduction and Agenda: The chairs opened the meeting, reviewed the Note Well, and confirmed the agenda.
Draft Status Update:
- Ripple (RFC 6550): Submitted to IESG.
- DAO Projection: Version 33 submitted, addressing initial issues. A GitHub ticket was created for further review.
- NSA Extension: Some issues addressed; one open issue remains.
- Enrollment Priority: Work in progress, a new version is expected soon.
- MOPEX: A new version was submitted, and Raul is addressing comments from Alvaro.
- RNFT: A new version is available; Michael is expected to provide feedback for integration.
- Capabilities & Storing Root: Not discussed in detail; to be addressed in future meetings.
Milestone Review:
- DAO Projection: Milestone marked as completed.
- Source Root Multicast for Ripple to IESG: Proposed November 2024.
- YANG Model for MPL: Discussion on whether to continue; a mail list discussion to decide in November.
- Fast Border Router Transportation in Ripple: Proposed March 2024 (corrected from an earlier "drop" indication).
- Proposal for Augmenting DoDAG Flags: Proposed December 2024.
- Capabilities: Proposed June 2024.
- Modes of Operations: Proposed February 2024.
- In-network AI Enrollment in Ripple Networks: Proposed January 2024.
- A sense of those present indicated no objections to the proposed milestone dates. The chairs will proceed with updating them.
RNFT (Fast Border Router Detection in Ripple):
- Michael indicated that previously offered English proofreading edits would not be completed.
- Discussion ensued regarding clarifying state transitions (data plane vs. control plane initiation) in the document. Conrad agreed to integrate clarifications into the text.
- A comment was raised about Section 5.5, concerning the normative language around activating/deactivating the protocol "once per DoDAG version," suggesting it needs clarification or stronger normative phrasing.
- Michael confirmed his role as the document shepherd.
DAO Projection (NSA Extension):
- Remus was commended for addressing review comments and closing GitHub tickets.
- Discussion focused on Issue 25 (previously misidentified as 28), specifically the use of "should" vs. "must" when setting the cost to MaxPlusCost if a candidate neighbor does not meet requirements, referencing RFC 6719. For alternative parents in NSA Extension, the working group leans towards a "must."
- Pascal offered to revisit the original RFC text for context on the "should" recommendation.
- Chairs noted that requests for Routing and Security Directorate reviews for this document had not yet received responses. The document was returned to the working group by the IESG.
- Alvaro volunteered to perform the Routing Directorate review for this document.
MOPEX:
- Raul provided an update on addressing Alvaro's review comments, expecting a response within approximately two weeks.
- A question was raised regarding the reuse of values in the mopex field from the original mob field and how augmented semantics should be handled, particularly concerning IANA assignments and clarity in the text. Raul will clarify this and revisit references to the capabilities draft.
Enrollment Priority:
- The status of open GitHub issues was discussed. Michael will review and close those that have been addressed.
- Discussion about the option's name (currently "this option" for ticket 4), which also includes the DoDAG size parameter.
- A technical comment concerned the explicit reset of the trickle timer (via a T-flag in the option vs. a bit in the DIO base object), revisiting a prior discussion. Pascal will revive this discussion on the mailing list.
- A suggestion was made to reduce the DoDAG size mantissa from 12 bits to 4 bits to save space, given its approximate nature. This will be discussed further on the mailing list.
Upcoming ROLL Meetings:
- IETF 118 (Prague): There was general agreement to schedule a working group meeting at IETF 118.
- Regular Interim Meetings: General agreement was reached to hold regular interim meetings. A cadence of every two months was suggested, with Thursday at 1PM UTC as a tentative time. The chairs will organize this, with the next possible interim meeting in mid-December or early January.
Open Floor:
- Co-chair Dominique Barthel announced his intention to step down from the co-chair role within the next six months (between IETF 118 in Prague and IETF 119 in Brisbane). He invited interested individuals to consider volunteering for the position.
- The time commitment for a co-chair was discussed, estimated at a minimum of 2-3 hours every other week, with more time required for deeper technical involvement. The distinction between a participant and a chair role (technical contribution vs. oversight) was highlighted.
- Pascal also shared that he anticipates a similar change in his professional situation by the end of the year.
- Aris expressed interest in considering the co-chair role.

Decisions and Action Items

Decision: Proposed milestone dates were tentatively accepted, pending final updates after the meeting.
Decision (NSA Extension): The text in the NSA Extension draft will use "must be set to MaxPlusCost" for alternative parents when requirements are not met.
Decision: A ROLL WG meeting will be scheduled for IETF 118 in Prague.
Decision: Regular ROLL interim meetings will be established, tentatively every two months, likely starting mid-December/early January, on Thursdays at 1PM UTC.
Action (Chairs): Update the ROLL WG milestones as discussed.
Action (RNFT authors): Integrate clarifications regarding data plane/control plane initiation for state transitions.
Action (RNFT authors): Clarify the normative language in Section 5.5 regarding activating/deactivating the protocol once per DoDAG version.
Action (RNFT authors): Prepare the document for internal reviews.
Action (Chairs): Request Routing Directorate and Security Directorate reviews for RNFT.
Action (Michael): Shepherd the RNFT document, starting preparations for the write-up before WG Last Call.
Action (Pascal): Revisit the original RFC text regarding the "should" recommendation for setting MaxPlusCost to provide context for the NSA Extension discussion.
Action (Chairs): Assign Alvaro to perform the Routing Directorate review for the DAO Projection (NSA Extension) draft.
Action (Chairs): Ping the Routing and Security Directorates again for reviews of the DAO Projection (NSA Extension) draft.
Action (Chairs): Issue another working group last call for the DAO Projection (NSA Extension) document, as it was returned to the WG.
Action (Raul): Clarify the interpretation of old MOP values when reused in the mopex field, especially concerning augmented semantics and IANA assignment; revisit references to the capabilities draft.
Action (MOPEX authors): Prepare the document for internal reviews.
Action (Chairs): Request Routing Directorate and Security Directorate reviews for MOPEX.
Action (Michael): Review open GitHub issues for Enrollment Priority and close those that have been addressed.
Action (Pascal): Revive the discussion on the mailing list about the trickle timer reset mechanism in Enrollment Priority (T-flag vs. DIO base object bit).
Action (Enrollment Priority authors): Continue discussion on the mailing list about the DoDAG size mantissa resolution (12 bits vs. 4 bits).
Action (Enrollment Priority authors): Update the draft to address open issues.
Action (Chairs): Organize the upcoming interim meetings, setting a firm schedule.
Action (Interested individuals): Consider volunteering for the ROLL Co-chair position and reach out to the current chairs for more information.

Next Steps

The working group will continue to advance its active drafts towards IESG submission. This includes integrating feedback, conducting internal reviews, and obtaining reviews from the Routing and Security Directorates. Working group last calls will be initiated as documents mature, followed by shepherd write-ups and submission to the IESG. The chairs will finalize the schedule for regular interim meetings and prepare for the IETF 118 session. Discussions regarding the future leadership of the working group will also proceed.