1437980 - RTCRtpReceiver track msid not respected

Status: RESOLVED INVALID

(Core :: WebRTC: Networking, defect, P2)

Description

[Alex Artushin]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce:

Set up a new WebRTC connection

const pc = new RTCPeerConnection;
... webrtc negotiation with offer sdp line including msids `a=msid:recv-stream-67981174 consumer-audio-67981174`...
const rtpReceivers = pc.getReceivers()


Actual results:

rtpReceivers did not contain tracks with any of the offer msids.


Expected results:

MSID should be respected as per https://tools.ietf.org/html/draft-ietf-mmusic-msid-16

Firefox 58 did this correctly and used the second msid as the mediastreamtrack id.

Comment 1

[Nils Ohlmeier [:drno]]

I think this is a known side effect of implementing the Transceiver model in Firefox 59. AFAIR MSID's are pretty much meaningless in the new Transceiver world.

Byron, do I remember this correct or what do you say about this bug?

Comment 2

[Byron Campen [:bwc]]

Correct. Under the latest webrtc spec, remote track ids are not consistent with what happens on the other end. We may even end up removing the track ids from a=msid entirely.

Comment 3

[Alex Artushin]

Got it. Thanks guys.

Comment 4

[Iñaki Baz Castillo]

Thanks. And yes, I totally agree with removing msid stuff at all.