- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Sun, 10 Mar 2019 07:00:29 +0000
- To: public-webrtc-logs@w3.org
When we defined a=msid the first time (in the context of plan B), changing the track ID (aka "appdata") was the way to say "the old track has gone away, you're now seeing a new one". Now that tracks are identified by their tie to a media section, it's possible to make a change of appdata mean something else - but we also took away the requirement to send it, and the requirement to show it on the receiving side; we no longer require the track's "id" attribute to be derived from a=msid. So appdata is largely useless - it's not even surfaced reliably. So that leaves the stream ID (when present). This can change, and should be interpreted as a change in the list of streams carrying the track. My $0.02. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2115#issuecomment-471252888 using your GitHub account
Received on Sunday, 10 March 2019 07:00:31 UTC