Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface

Silvia Pfeiffer <silviapfeiffer1@gmail.com> Wed, 17 July 2013 00:27 UTC

Return-Path: <silviapfeiffer1@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC82F21F9D87 for <rtcweb@ietfa.amsl.com>; Tue, 16 Jul 2013 17:27:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HniBlqWg+++N for <rtcweb@ietfa.amsl.com>; Tue, 16 Jul 2013 17:27:06 -0700 (PDT)
Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 4989C21F9D7E for <rtcweb@ietf.org>; Tue, 16 Jul 2013 17:27:06 -0700 (PDT)
Received: by mail-oa0-f44.google.com with SMTP id l10so1688424oag.17 for <rtcweb@ietf.org>; Tue, 16 Jul 2013 17:27:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=gS1Nv3cLQ9kbuztOGhTG9CT9A/WVrw2poFz2Q6FOC0g=; b=LfZoHeRMTEs3NKH1xPzeRO80BQV/liXtfWcfxsFiyCeWSJnx3CXbL7lweCyoa301zX S69bnEDpXVRfl8ooM0lClxwPlNdR4RG24ziPrfJII5WhyiTvLHHXzlMf0nxOzP/AoZEC dXXm63K1M1ltWeb5Qd6IV3lL6OVySi2RKuG/9HEIrf8OIt/TMdu+D7NIwNuhRsUAQ7MB 3DSvjmuaYiMY1VNvZyB9KfH10IcnrhsQoQZizIndJXLR0Qb1UsRvJJtnCoFdqkokQ+zw uczDNmqSzYqchhbqiJrDsOh7ETHoje+f/XTuAgxJ0KZDuZY1HPyK8H2Va5eUZPJVmE/n xK3w==
X-Received: by 10.60.95.198 with SMTP id dm6mr5172837oeb.44.1374020825390; Tue, 16 Jul 2013 17:27:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.173.106 with HTTP; Tue, 16 Jul 2013 17:26:45 -0700 (PDT)
In-Reply-To: <BLU401-EAS386F88B3FE140492B39B59693610@phx.gbl>
References: <CAJrXDUGMohpBdi-ft-o_uE7ewFkw7wRY9x7gYEncjov7qi-Bew@mail.gmail.com> <CABcZeBPa4wBS8pYq=0wesMOfL6TkeC7QGAZ8pWwOcnkhkJqWfA@mail.gmail.com> <CAJrXDUFxo8P8wxh8jX3019yPQOuwQ0eVdsFmRXsbWdWinnc5oA@mail.gmail.com> <CABcZeBOTKpmFC34waqZ4kA-P8t+E6yY9gX1JFCHhsBH0+CF-Qw@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30BC0F@ESESSMB209.ericsson.se> <CAD5OKxtKLMf_d=8GSMrqfNhDHPe9MFP2ZTKzZHFn9CyMr-gSVQ@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30C833@ESESSMB209.ericsson.se> <CAD5OKxvGfkgRp6tXwbOu_kVteHiBBqsyR5ixH18FMKjCNGO8VQ@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30CD1E@ESESSMB209.ericsson.se> <BLU401-EAS386F88B3FE140492B39B59693610@phx.gbl>
From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Wed, 17 Jul 2013 10:26:45 +1000
Message-ID: <CAHp8n2kNnNoRBQYmEF-5=2NebCBsbTSWxHt0ZndAvq7zU8sKUg@mail.gmail.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jul 2013 00:27:08 -0000

The whole point of standardisation at the W3C is for browser to agree
on the knobs. So, I do think it's a valuable effort.
Cheers,
Silvia.


On Wed, Jul 17, 2013 at 10:15 AM, Bernard Aboba
<bernard_aboba@hotmail.com>; wrote:
> The problem was that we never defined what mangling browsers had to support. Given all the SDP specs that is actually a huge work item. And creating APIs to avoid mangling isn't actually that much simpler. What knobs do you provide and which ones do you ignore? Browsers might not agree on those either.
>
> On Jul 8, 2013, at 1:37 PM, "Stefan Håkansson LK" <stefan.lk.hakansson@ericsson.com>; wrote:
>
>> On 7/8/13 5:22 PM, Roman Shpount wrote:
>>
>>> So, was there ever a consensus that "developers MUST NOT
>>> touch SDP"?
>>
>> No, developers are free to touch the SDP (and probably must in certain
>> cases).
>>
>>>
>>> _____________
>>> Roman Shpount
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb