W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2015

Re: Simulcast V1

From: Adam Roach <adam@nostrum.com>
Date: Thu, 20 Aug 2015 09:50:33 -0500
To: docfaraday@gmail.com, Harald Alvestrand <harald@alvestrand.no>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>, Bernard Aboba <Bernard.Aboba@microsoft.com>
Message-ID: <55D5E939.2010402@nostrum.com>
On 8/20/15 09:02, docfaraday@gmail.com wrote:
> [I]t now sounds like we have disagreements on how simulcast should be 
> signaled in SDP.

Let's be clear here.

The way things are encoded and go on the wire is in the purview of the 
IETF, not the W3C. The format of SDP is in the purview of the IETF, not 
the W3C.

MMUSIC has a charter item and an adopted draft that details how 
simulcast works. /It is not in charter for any W3C working group or 
community group to define a competing specification for how simulcast 
works./ If we're doing simulcast, the SDP and media will track whatever 
MMUSIC defines. Anyone who cares about how this is signaled in JSEP or 
how it is encoded in RTP and RTCP needs to have a conversation, in 
MMUSIC, about the contents of the existing adopted simulcast working 
group draft.

What *this* working group can consider is what the JavaScript API looks 
like for controlling the IETF-defined simulcast mechanisms, and that's 
the conversation I was trying to have.

/a
Received on Thursday, 20 August 2015 14:51:05 UTC

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