- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Jan 2018 11:31:24 +0000
- To: public-webrtc-logs@w3.org
Caveat: I'm no expert on SDP, but... I'm talking about a=msid "track IDs", but considering replaceTrack(), these IDs no longer necessarily correspond to the remote endpoint's MediaStreamTrack.id, and it's possible to send the same track multiple times - the announced IDs have to be unique to the sender. As of now, it makes more sense to think of these as sender IDs, and it does not make sense to use the ID of whatever track was used when the sender was first announced, as this may lead to multiple "tracks" having the same ID even within a single blob of SDP. But perhaps I'm speaking out of turn, care to weigh in @taylor-b? -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1562#issuecomment-354991273 using your GitHub account
Received on Wednesday, 3 January 2018 11:31:25 UTC