**Session Date/Time:** 22 Jul 2025 07:30 # moq ## Summary The meeting covered several important topics, including a discussion on whether to rename the "media over quick" protocol, updates to the moq-transport draft, the introduction of Privacy Pass tokens for enhanced security, a proposal for distributing Open Cybersecurity Framework (OCSF) events over MoQ, and an update on secure objects. Key technical discussions and decisions revolved around the handling of header extensions in secure objects, the possibility of self-subscription, and error handling for fetch requests. ## Key Discussion Points * **Protocol Naming:** A vote was held regarding renaming the "media over quick" protocol. The majority favored keeping the current name, but the topic will be revisited on the mailing list. * **moq-transport Updates:** Alan presented updates to the moq-transport draft since IETF 122, focusing on new features, wire changes, and compression schemes. Changes included request IDs, authentication info structure, forward flags, and joining fetch. * **Privacy Pass Tokens:** Cullen introduced Privacy Pass tokens as an alternative to CAT tokens, designed to provide privacy-preserving authorization. The discussion covered the scope of authorization and the need for consistency with CAT tokens. * **OCSF over MoQ:** Suhas proposed using MoQ to distribute Open Cybersecurity Framework (OCSF) events for cybersecurity applications, emphasizing its potential to reduce latency and improve scalability compared to traditional systems. The discussion revolved around use cases and the applicability of MoQ's charter. * **Secure Objects:** Cullen updated the group on secure objects, focusing on the handling of header extensions. The proposal involves categories of header extensions that relays can modify, see but not modify, or cannot see (encrypted). There was debate on mutability and placement of the integrity marker. * **Self-Subscription:** A debate occurred about allowing a publisher to subscribe to its own track. Concerns revolved around potential loop issues. The preliminary conclusion was to allow it, enabling multi-publisher scenarios. * **Fetch Range Errors:** The group discussed how to handle fetch requests for ranges that are too large. The initial idea of providing an explicit fetch error for too-large requests was favored over more complex approaches like subsetting the fetch. ## Decisions and Action Items * **Protocol Naming:** Stick with the current name "media over quick" but revisit the discussion on the mailing list. * **Privacy Pass Tokens:** Further discussion of Privacy Pass tokens on the mailing list, followed by potential adoption call. * **Secure Objects:** Take the discussion of header extensions and integrity markers to the mailing list for further consideration. * **Fetch Range Errors:** Add an explicit fetch error for requests with a range that is too large. ## Next Steps * Magnus and the chairs will coordinate on adoption calls for Privacy Pass tokens and CAT tokens after mailing list discussion. * Further discussions will take place on the mailing list regarding header extensions in secure objects, including mutability and integrity marker placement. * A PR will be written to add an explicit fetch error code. * The implementation of a PR that allows the feature of self-subscription in moq should include clarification about whether the publisher also receives their own objects when subscribed to the same namespace and track. --- **Session Date/Time:** 24 Jul 2025 07:30 ```markdown # moq ## Summary This moq session covered several important topics, including the naming of the protocol, interop results, updates on the Warp draft, authentication and access control, open issues in the moq transport draft, and discussions around ABR and synchronization. The meeting involved a mix of presentations, discussions, and decisions regarding the direction of the moq protocol. ## Key Discussion Points * **Naming:** The group discussed the possibility of repurposing the "MOQ" acronym, but decided to stick with "Media Over Quick". * **Interop:** Mike presented interop results and raised the question of the best timing for cutting interop target drafts. There was a call for clearer communication about changes between drafts and mechanisms to announce bugs that impact interoperability. Also, ALPN is still blocking some functionality. * **Warp:** Will Law provided an update on the Warp draft, focusing on changes related to group numbering, track roles, catalog generation, and live broadcast termination. A major point of discussion was the URL syntax for Warp, particularly how to separate connection information from namespace and name information. There was feedback regarding tokenization and concerns about including credentials in the URL path. * **Authentication (CAT for MOQ):** Authentication and access control for MOQ using Common Access Tokens (CAT) was discussed, including updates to the MOQ claim, supported actions, and composite claims. The "moq revalidate claim" and its relationship to token expiration was discussed. There was an open question about the types of matches needed (exact, prefix, suffix, contains). A request for working group adoption was made, along with a discussion about whether the working group adopting the scheme precludes additional work on others with significantly different properties. * **MOQT Open Issues:** Ali reviewed open issues, including issues related to varn format, and the `announce` verb. Discussions were held about modularity and what is mandatory for relays to implement, also empty object returns on fetch. There was an issue on Should vs Must for multi-publisher relay handling and various use cases around those, that could be implemented. * **ABR and Synchronization:** Ian presented on issues related to ABR and synchronization. Topics covered included bandwidth estimation, discovery, padding streams, probing, the priority of less than best effort and reserving congestion control. There was also talk about grouping, in order to sync multiple sources like Audio and Video. ## Decisions and Action Items * **Naming:** Stick with "Media Over Quick" for the MOQ acronym. * **Warp URL Syntax:** Will to review chat logs and continue discussion on the mailing list. * **CAT for MOQ Adoption:** Conduct a confirmation poll on the working group mailing list. * **MOQT: Feature Modularity:** Relays must implement everything, and applications are allowed to implement a subset of features. Discussion will continue on the PR. * **MOQT: Multi-Publisher:** Create a PR that makes forwarding for Multi-publishers a MUST and then separately can propose a way to make it must when the publisher identifies that it is absolutely critical and should otherwise. * **ABR and Synchronization:** Explore whether it can implement in a way to probe with duplicates as a kind of poor man's FEC just to have some way of implementing such a thing and discussion about the reserving capacity in the Lincoln not fully utilizing the congestion controller for a certain prioritization use cases. ## Next Steps * Magnus to take naming decision to the mailing list. * Will to review the chat logs and create an issue on Github to track follow up discussions about warp url syntax. * Ali to send the summarization of the discussion, with a link, to the mailing list. * Ali to create PR for Multi-Publisher and then separately can propose a way to make it must when the publisher identifies that it is absolutely critical and should otherwise. * Ian to provide links to the github issues on mailing list. * Continue discussions asynchronously on GitHub and the mailing list. * Present new drafts and updates at the next interim meeting in Toronto.