[Webkit-unassigned] [Bug 163202] New: WebRTC: Make MediaEndpointPeerConnection handle remotely assigned mids correctly

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Oct 10 02:09:59 PDT 2016


https://bugs.webkit.org/show_bug.cgi?id=163202

            Bug ID: 163202
           Summary: WebRTC: Make MediaEndpointPeerConnection handle
                    remotely assigned mids correctly
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: adam.bergkvist at ericsson.com

An RTCRtpTransceiver has a null mid until it's been associated with a media description (with a mid) [1]. During that time, it's identified by a provisional mid that might become its real mid, but the transceiver can also get its mid assigned by a remote media description. In the second case, the mid value is initially unknown. A transceiver's RTCRtpSender must directly (synchronously in the script) provide a muted remote source that is playable by, for example, media element. This source is initially registered in the MediaEndpoint (WebRTC backend) with the transceiver's provisional mid. So, if the real mid is set by a remote description, the registered mid must be updated to preserve the association between the registered source and the transceiver.

[1] https://w3c.github.io/webrtc-pc/archives/20160913/webrtc.html#dom-rtcrtptransceiver-mid

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20161010/55ce6990/attachment.html>


More information about the webkit-unassigned mailing list