Varun Singh

@balazskreith is taking responsibility for this. When it is ready, we will need someone from W3C to vet the licenses on the dependency libs

@pallab-gain and @karthikbr82 put together an interactive graph: https://webrtc-stats.callstats.io/graph/ @henbos @alvestrand @jan-ivar comments and feedback appreceiated.

@MoeRT09 Thanks for producing this. This is good stuff. For this issue, What we need for the spec should show the interlinking of the objects.

This was fixed by @dontcallmedom with the summary table, closing

we are discussing the first scenario, not about receiving simulcast

The issue is about what the receiver knows about the source stream at the SFU. There are SSRCs received by the SFU, which it may swap and send downstream to...

> The question is -- can the receiver know (via getStats) which stream is being downstreamed to it A_low or A_high? > > visually, you could plot metrics (frameHeight, bitrates,...

One proposal: I have not thought of this enough, and my first thought was why not use CSRC to indicate which source stream is being carried, at any given time...

@murillo128 Since for all practical purposes the RTP Session terminates at the SFU -- we cannot use SSRCs across RTP Sessions (I should check the taxonomy draft for the proper...