Session Date/Time: 02 Jul 2025 21:00

SCONE

Summary

The SCONE working group held an interim meeting focused on planning for the IETF123 hackathon in Madrid and providing status updates on the workstreams. Key discussions included the hackathon's scope, an update on the applicability and manageability draft (shifting focus and addressing initial comments), and the status of the core SCONE protocol document, which has seen low activity but will be updated with recent merges. A need for more focus on semantics and clearer definitions within the protocol was also highlighted.

Key Discussion Points

Working Group Status Update:
- Four interims have been held since the Bangkok meeting, driving progress on two workstreams.
- Good progress has been made, including establishing a GitHub repository, consolidating two protocol proposals into one, and tracking open issues.
- One milestone achieved with the adoption of a SCONE-based protocol as the working group charter.
- Applicability and manageability workstream noted as lagging; more effort needed.
IETF123 Hackathon Planning (Wesley):
- A hackathon session is planned for July 19-20 at IETF123 in Madrid, with remote participation support available.
- A Slack channel has been created on the quickdev Slack for coordination.
- Planned activities include running SCONE network elements and QUICK end stacks, with coordination on version numbers via Slack.
- Results will be shared with hackathon participants and potentially the SCONE WG meeting.
- A suggestion was made to invite QUICK experts to the hackathon.
Applicability and Manageability Update (Sanjay):
- The draft's focus is shifting from "use case and requirements" to "applicability and manageability."
- Response to comments:
  - RFC2119 language: Proposed to keep the reference for now, as "must" and "should" terms will likely remain.
  - Removing requirements: Agreed to remove specific requirements from the next version, as the protocol document addresses them. The scope will be adjusted.
  - Structure/organization: Agreed to improve structure following RFC9317 and RFC7603.
- Planned content for the next version: Expansion on the SCONE hint, network actions, application actions, and addressing GitHub issue #35 (advised bit rate per flow or aggregate).
- Plan to submit a broader outline and structure of the document within the next 5 days.
SCONE Protocol Status (Marcus):
- Low activity since the last meeting.
- A non-controversial pull request, clarifying "throughput device" over "rate limits" to broaden the mechanism's description, has been merged.
- No updates on issue #5 (the most debated issue previously).
- No substantial discussion yet on issue #35 (aggregate or per-flow measurement).
- Anticipation that interop testing and the applicability document will lead to more informed discussions and potentially new issues.
Semantics and Terminology (Dan):
- Proposed adding labels to GitHub issues to distinguish between "semantics" and "protocol" related items.
- Expressed concern about a lack of progress on semantics, particularly regarding a clear understanding of what "throughput advice" is supposed to be.
- Emphasized the need for clarity in the document on terminology, semantics, and what is being transported, ensuring it is well-understood and measurable by both Content Service Providers (CSPs) and Client Application Providers (CAPs).
- Mentioned the "video session data rate" draft as relevant context.
- Marcus agreed that this is a critical area and suggested translating previous discussions (e.g., Anoop's presentation on averaging window times) into specific issues or pull requests.
Next Draft Version: The chairs confirmed plans to roll up recent merges into a draft-scone-01 version before the upcoming IETF document deadline.
Interim Schedule: The chairs noted that the aggressive interim schedule has not necessarily driven work forward as expected and suggested discussing a potentially less frequent schedule in Madrid or on the mailing list.

Decisions and Action Items

Decision: The SCONE hackathon for IETF123 Madrid is confirmed with planned activities focusing on SCONE network elements and QUICK end stacks.
Decision: The focus of the applicability and manageability draft (draft-sanjay-scone-req) will shift from "use cases and requirements" to "applicability and manageability."
Decision: The RFC2119 reference will be retained in the applicability and manageability draft for now.
Decision: Requirements content will be removed from the applicability and manageability draft in future versions.
Decision: The structure of the applicability and manageability draft will be aligned with RFC9317 and RFC7603.
Decision: Merged pull requests for the core SCONE protocol will be rolled into draft-scone-01 before the upcoming IETF document deadline.
Action Item: Wesley to extend an invitation to QUICK experts to participate in the SCONE hackathon at IETF123.
Action Item: Sanjay to share the broader outline and structure of the updated applicability and manageability draft on the mailing list.
Action Item: The chairs/editors will investigate adding labels (e.g., "semantics") to GitHub issues for better organization.
Action Item: The working group will discuss the future interim meeting schedule at IETF123 or on the mailing list.

Next Steps

IETF123 Hackathon: Participants will collaborate on SCONE implementations and interop testing in Madrid (July 19-20).
Applicability and Manageability Document: Continued development and refinement, with an outline expected to be shared soon.
Protocol Semantics: Further discussion and clarification on "throughput advice" and other semantic aspects of the SCONE protocol, potentially leading to new GitHub issues or pull requests.
IETF123 Working Group Meeting: Further technical discussions and review of progress.
Working Group Management: Discuss and potentially revise the interim meeting schedule for the working group.