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

Re: FW: [Bug 20810] SDP inadequately defined

From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Thu, 30 Oct 2014 16:18:40 +0100
Message-ID: <CALiegfnNmFxMi4WsXfNa+1Kng=-0oV3R-ZNVF4FFmPemLpQBhA@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Cc: public-webrtc@w3.org
JSEP is redundant anyhow. Most of it should be included into the W3 spec,
and then rename JSEP to "SDP made easy" or "375 things you need to know
about SDP".

May I know why the RTCPeerConnection signaling plane (which is a set of JS
methods and events) must be defined in a document other than the WebRTC W3
spec?
On 30 Oct 2014 16:00, "Harald Alvestrand" <harald@alvestrand.no> wrote:

> On 10/30/2014 07:00 AM, Iñaki Baz Castillo wrote:
> >
> > If the SDP string is considered part of the API, shouldn't the WebRTC
> > W3 spec instruct on how to generate and parse WebRTC compliant SDPs? I
> > don't understand why there is a separate draft for that in the IETF
> > domain.
> >
> It would be ridiculous to have two docs specifying this.
>
> We might have made JSEP a W3C draft without straining credulity too far,
> but I don't see a great benefit in moving it now.
>
>
> --
> Surveillance is pervasive. Go Dark.
>
>
>
Received on Thursday, 30 October 2014 15:19:10 UTC

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