W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2018

[webrtc-pc] Pull Request: Describing which media description is offerer tagged.

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Thu, 04 Oct 2018 11:24:45 +0000
To: public-webrtc-logs@w3.org
Message-ID: <pull_request.opened-220340561-1538652284-sysbot+gh@w3.org>
henbos has just submitted a new pull request for https://github.com/w3c/webrtc-pc:

== Describing which media description is offerer tagged. ==
Fixes #1919.

This PR...
- Makes sure that rejected transceivers are marked as stopped in setLocalDescription, as is necessary because the offerer tagged m= section might have been rejected between setRemoteDescription(offer) and setLocalDescription(answer).
- Mandates that the first non-stopped transceiver is picked as the "offerer tagged" m= section. (The BUNDLE spec does not say which one you should pick, it just suggests that you pick one that you think is unlikely be rejected.)
- Clarifies the existing NOTE in RTCRtpTransceiver.stop() that rejected m= sections causes their transceivers to be stopped when applying the answer at setLocalDescription and that this can be avoided by predicting which transceiver is offerer tagged per how it must have been picked.

See https://github.com/w3c/webrtc-pc/pull/2001
Received on Thursday, 4 October 2018 11:24:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:07 UTC