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

RE: FW: [Bug 20810] SDP inadequately defined

From: Matthew Kaufman (SKYPE) <matthew.kaufman@skype.net>
Date: Wed, 29 Oct 2014 18:54:08 +0000
To: Harald Alvestrand <harald@alvestrand.no>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <AE1A6B5FD507DC4FB3C5166F3A05A484505F3149@TK5EX14MBXC299.redmond.corp.microsoft.com>

Matthew Kaufman

> -----Original Message-----
> From: Harald Alvestrand [mailto:harald@alvestrand.no]
> Sent: Tuesday, October 28, 2014 8:35 PM
> To: public-webrtc@w3.org
> Subject: Re: FW: [Bug 20810] SDP inadequately defined
> On 10/28/2014 01:07 PM, Matthew Kaufman (SKYPE) wrote:
> > I'm not entirely thrilled about all the bugs being closed as "this is the IETF's
> problem", but this one in particular is an issue. There is currently NO chain of
> normative references, RFC or otherwise, which when used as a specification
> results in SDP that is compatible with any SDP generated or consumed by any
> WEBRTC implementation. This is a bug *with the W3C specification* until
> such time as we reach the point where the normative references are
> sufficient to create an interoperable implementation without reference to
> third party source code.
> I disagree with your interpretation of the state of play.
> The current reference to how SDP should be generated and parsed is JSEP.


> I agree that JSEP is not specifying the generation and parsing that browsers
> do today. 

It isn't adequately specifying anything that can possibly work.

This is a) a problem with JSEP (it wasn't complete last time I looked
> at it), and b) a problem with the browsers (they have not been updated to
> follow the parts of the spec that *are* complete).
> But the WEBRTC (W3C) bugtracker is about tracking issues that can be solved
> by *modifying W3C specifications*. There is nothing here that can be fixed
> by modifying a W3C specification.

Sure it can. The W3C specification could specifically call out the existing specs explicitly in such a way that one would know what to implement.

The W3C specification could more explicitly define the specific SDP that is to be generated and understood.

The W3C specification could *not use SDP as an API* and then this problem goes away entirely.

> My conclusion is that keeping a bug in the W3C bugtracker that says "JSEP is
> not complete" makes no sense. Therefore, I closed this bug.

That's not what the bug says. The bug says that the W3C specification in its current state cannot be used to create interoperable implementations of the standard. That is a *blocking* bug, and until *actually fixed* (and not simply closed for convenience) should prevent the specification from becoming a standard.

Leave the bug open until this critical flaw is repaired, please.

Matthew Kaufman

Received on Wednesday, 29 October 2014 18:55:21 UTC

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