W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2013

[Bug 20807] New: End-to-end stream configuration unspecified

From: <bugzilla@jessica.w3.org>
Date: Tue, 29 Jan 2013 18:08:49 +0000
To: public-webrtc@w3.org
Message-ID: <bug-20807-4991@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20807

            Bug ID: 20807
           Summary: End-to-end stream configuration unspecified
    Classification: Unclassified
           Product: WebRTC Working Group
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebRTC API
          Assignee: public-webrtc@w3.org
          Reporter: matthew.kaufman@skype.net
                CC: public-webrtc@w3.org

In the WebRTC draft, Section 4.3.2.2, there is a method addStream() on the
RTCPeerConnection object. It is expected that this will add a stream to the
local peer connection.  At the receiving end the onaddstream event is expected
to fire when the SDP is passed into setRemoteDescription(). It is critical that
it be possible to describe streams in such a way that the receiver can
construct a MediaStream that consists of tracks in the same configuration as
the stream added by the sender.  There is no specification within this document
and its normative references defining how the labels used on MediaStream and
MediaStreamTrack correspond to RTP constructs or how information about streams
is conveyed between peers such that a receiver can successfully reconstruct a
MediaStream in the same configuration that a sender used.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Tuesday, 29 January 2013 18:08:54 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:32 UTC