moq

Summary

This was the first official meeting of the moq working group at an IETF plenary. The agenda included reports from the interim meeting, presentations on the combined rush/warp/quickR proposal and relays, and a discussion about a potential interim meeting. Key discussions revolved around media encoding, congestion control, prioritization, relay functionality, and security considerations.

Key Discussion Points

Media Encoding & Dependencies: Discussion on different encoding schemes (I-frames, P-frames, B-frames) and their impact on latency and prioritization. The importance of respecting encoding dependencies over the network was emphasized.
Congestion Control & Prioritization: The interplay between congestion control and rate control was discussed. The need for application-level prioritization to inform packet dropping decisions during congestion was a recurring theme. Discussion on differentiating local queue prioritization from marking packets for network prioritization.
Rush/Warp/QuickR Combined Proposal: Luke presented the combined draft, highlighting the concept of segments (any number of frames per stream), delivery order, and dependencies written on the wire for relay support. Different approaches to segmenting media were explored.
Relays: Colin presented on relay functionality, focusing on the need to provide relays with sufficient information (envelope data) to make intelligent forwarding and dropping decisions without inspecting the payload. Discussions on priority, dependency indication, caching, security, and privacy aspects of relays. Multicast Quick was brought up as potentially helpful.
Use Cases and Requirements: A discussion on the progress of the use cases and requirements document.

Decisions and Action Items

GitHub for Document Management: Confirmed usage of GitHub for document management.
Slack Bridge: Working on setting up a bridge for Slack to retain messages. WG discussions should not occur on Slack until that happens.
Interim Meeting: The working group will investigate the feasibility of an in-person interim meeting in late January 2023 on the U.S. West Coast. Chairs will come up with a suggestion to the list.
Call for Adoption: A call for adoption on the use cases and requirements document will be issued after further discussion on the mailing list.

Next Steps

Luke to review chat transcript for additional issues raised.
Continue discussions on the mailing list regarding prioritization schemes, dependency handling, relay functionality, media formats, and congestion control algorithms.
Define the agenda for the potential interim meeting based on mailing list discussions and available drafts.
Further develop the combined rush/warp/quickR draft, focusing on wire format definition and CDN support.
Explore potential synergies with the Quick, WebTransport, and other relevant working groups (IETF and W3C).