W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > July 2017

Re: [webrtc-pc] does MSID still work? (was: example 13: getReceivers semantics)

From: Mark Roberts via GitHub <sysbot+gh@w3.org>
Date: Thu, 13 Jul 2017 18:32:49 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-315164141-1499970767-sysbot+gh@w3.org>
Thanks, @jan-ivar.

> The track ids in the SDP won't match those in the menu.

AFAICT, this is true if

* The remote end calls [`addTransceiver(kind)`](http://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-addtransceiver), in which case its `direction` defaults to "sendrecv", its `sender.track` is `null`, and therefore JSEP says it should generate `a=msid:- random`. (If I'm reading [5.2.1](https://tools.ietf.org/html/draft-ietf-rtcweb-jsep-21#section-5.2.1) correctly...)
* The remote end calls `replaceTrack` in some subsequent round of negotiation.

-- 
GitHub Notification of comment by markandrus
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1128#issuecomment-315164141 using your GitHub account
Received on Thursday, 13 July 2017 18:32:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:21:40 UTC