Code change:
control of packetization and transmission, with addtional support for retransmission as an optional extension. <ins> To provide an overview of interactive use cases, we can consider a conferencing session comprised of: Multiple emitters, publishing on multiple tracks (audio, video tracks and at different qualities) A media switch, sourcing tracks that represent a subset of tracks from across all the emitters.  Such subset may represent tracks representing top 5 speakers at higher qualities and lot of other tracks for rest of the emitters at lower qualities. Multiple receivers, with varied receiving capacity (bandwidth limited), subscribing to subset of the tracks This setup relies on the following functionalities: Media Switches source new tracks but retain the media payload from the original emitters.  This implies publishing new Track IDs sourced from the SFU, with object payload unchanged from the original emitters. Media Switches propagate a subset of tracks as-is from the emitters to the subscribers.  This implies Track IDs to be unchanged between the emitters and the receivers. Subscribers explictly request one or more media tracks in appropriate qualities and dynamically move between the qualtiies during the course of the session. Another topology for the conferencing use-case is to use multiple distribution networks for delivering the media, with media switching functionality running across distribution networks and these media functions as part of the core distribution network as shown below. Such a topology needs to meet all the properties listed in the homogenous topology setup, however having multiple distribution networks, and relying on the distribution networks to carry out the media delivery, brings in further requirements towards a data model that enables tracks to be uniquely identifiable across the distribution networks and not just within a single distribution network. </ins> 3.1.1. In this use case the computation for running a video game (single or

Related discussion:
text: Note - this is a rough draft, although I have done some edits while adding this material. I do have notes for to-dos, and I'm pretty sure I want to figure out how to do the diagrams in some way that will format with straight lines, for starters.
I'm happy to just merge this in now as is just to unblock other work and make progress, and make any adjustments later because there's nothing that stands out as controversial, NAME are you okay with this?
We have a plan on how to resolve our terminology migration for in this PR
Based on review comments from NAME on the mailing list .
Draft is in suhasHere/moq-drafts.
NAME - NAME and I are starting with the scenarios from URL
NAME - I think it would be good to close this issue when we have a reasonable plan for where the material from the scenarios draft goes, and then handle further changes via issues and PRs as usual. Does that make sense? NAME NAME and NAME - I wanted to let you know that NAME and I are (finally, finally!) merging text from the scenarios draft in the requirements draft, as NAME suggested. I think I have homes for almost all of the text from the requirements draft, but I do have some work to do, so that the material is in the right place, and that it flows with text from the previous version of the requirements draft. I am, of course, always interested in comments. And thank you each for the work you did on this material.
Awesome - let me know if something I can do to help
Thanks NAME .. look forward to the updates. +1 to NAME , please let me know if we can be of any help Here is my review. Firstly, I'd like to say that this document is badly needed. The requirements document doesn't get into the level of detail that this document does, and I think that this level of detail is important to make progress on the design. Terminology I think it would be useful to define some of the terminology, including terms like "track" and "media switch". Section 2.2 A few questions: Are the trackIDs "t1, t2, t3" separate MediaStreamTracks, or are they just multiple encodings of the same track?