Re: [webrtc-pc] [Question] Is it guaranteed that the mid property value of transceiver is the same for setLocalDescription()(sender) and ontrack(receiver)? (#2527) from Harald Alvestrand via GitHub on 2020-05-07 (public-webrtc-logs@w3.org from May 2020)

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Thu, 07 May 2020 09:59:38 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-625155248-1588845577-sysbot+gh@w3.org>

If they are not, file a bug on the relevant browser.
Chrome allocates MIDs as 0, 1, 2 in the order of creation of the transceiver - but this is something that may change at any time; what MID values are assigned is not part of the standard.
Note - mids are allocated on the offerer at createOffer() time, not at transceiver creation time, and are made visible at the answerer after setRemoteDescription(). This may confuse.


-- 
GitHub Notification of comment by alvestrand
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2527#issuecomment-625155248 using your GitHub account

Received on Thursday, 7 May 2020 09:59:39 UTC