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

Re: FW: [Bug 20810] SDP inadequately defined

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Thu, 30 Oct 2014 13:22:54 +0000
To: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>, Harald Alvestrand <harald@alvestrand.no>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B1D0AF15B@ESESSMB209.ericsson.se>
On 29/10/14 23:33, Matthew Kaufman (SKYPE) wrote:
> 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

>> 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.

Is that really the case? In the W3C document, as far as I can see, the 
actual SDP (or RTCSessionDescription) is never dealt with in any other 
way than applying to the PeerConnection or sending off to a remote peer.

Received on Thursday, 30 October 2014 13:23:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:01 UTC