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

Peter Thatcher <pthatcher@google.com> Wed, 03 July 2013 22:28 UTC

Return-Path: <pthatcher@google.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 2FF3E21F9BF1 for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2013 15:28:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 sz+-1LtJKGVU for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2013 15:28:48 -0700 (PDT)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 5788A21F9BCA for <rtcweb@ietf.org>; Wed, 3 Jul 2013 15:28:48 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id fa11so679035pad.33 for <rtcweb@ietf.org>; Wed, 03 Jul 2013 15:28:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=JkiPGc3uD8GhCS4OxyugJdbgQ2gYtBW6z0VKJBI/zzI=; b=nkSEmSrwwaurCeNlejo1j6SYg0URRUs7bRKTeutvymfEgwAsA1gsHk7wTFWz0yH5nL N0fYM5puif3QaXBzh8aC9ndzFv1Tqr7D79Pv5WV6/ciwtgcGqBpbJQOc76fr2ym3LGhM /PCR4cJtVGfvgpNE0v6m9E7AQavpyiELa+CxEfncI++6sLTaiAODbbKRHAnTRl9nIMUD GkP9sO76bph8hNxX8FD9ZCjDs6sbaetmA6C61ZxuF5Gw57U0wCsZudCKgpiYC7uki5hD VS/Xb2oINgc8QXJuMmUyxqRUyLqPPKAxP0w1fVvFn9KbOwny7xRRINKfvn3gJfdff24H KpAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=JkiPGc3uD8GhCS4OxyugJdbgQ2gYtBW6z0VKJBI/zzI=; b=dAE9H+n+1mMSCASGscr3V9papylL0oN0s63huVGu36EX2TmkXmXBVboM3U1aFLkYGU GTrLyMB2/GjMQWX8rkz93DInphoKnMOLi1H4BEH2ODdKQPJjNUOKwtGsyyzq7tqYSUIX iOqFtfyIjSydzvUFMYJhYdvImvw2BC8J3Bbwl6CMMymBa0avfB06EM2oS4Gqq25Jlpwh fvanBToQLoPCVy2iZzc3dtGmbBPEp9vQVBkO/YN87GQoTJJX5/3nZXtV8amUsWnAoMp/ Eunoup2CxjlGgMwM0YUcnUvp1VzhBD9VQl1s/4oq/nIycqZ03nYyQUoDJf3182WJeW41 VCxg==
X-Received: by 10.68.213.5 with SMTP id no5mr2708004pbc.185.1372890528057; Wed, 03 Jul 2013 15:28:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.78.169 with HTTP; Wed, 3 Jul 2013 15:28:07 -0700 (PDT)
In-Reply-To: <CABcZeBP_r=3krG=Seb+jYj0VJyR-yOzH8EU9Vp8p83kMZAx6jw@mail.gmail.com>
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> <CALiegfnDD8PAxZMfczV=cZtwx49XDT2+XiRhe5t88cT+xayz5g@mail.gmail.com> <CABcZeBMCGdY=LS0OG22aFdhwU2m_-H4_sHb15SAYBT7e2_4RLQ@mail.gmail.com> <CAJrXDUH9q6zbjQ_xFRuWXmkb_aqnmv+Pn8SSQwrXzUV17d3t9Q@mail.gmail.com> <CABcZeBP_r=3krG=Seb+jYj0VJyR-yOzH8EU9Vp8p83kMZAx6jw@mail.gmail.com>
From: Peter Thatcher <pthatcher@google.com>
Date: Wed, 3 Jul 2013 15:28:07 -0700
Message-ID: <CAJrXDUE1XNiNzwVPt+hdqmqqDGQECb80KoB1mjFebr-HMxwE+Q@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Content-Type: multipart/alternative; boundary=e89a8fb208343dbc9c04e0a2fc14
X-Gm-Message-State: ALoCoQlSyvVxJJGlLTqWVCClLz2Xsk9e9by23nxSJiv+1GvVkU4hMMaJutZfUTFSEHrWZulMyZ5JYuABbU9XI2skKqoBW5BTj9WoUgzAGlOAXCKgohEkzz1wyz3ORUShG71KpNGz2/CkBEAQ+2zacfpNTfqyH9vXegoh2/Zc3MOyJSMtlRiQIRqEUz+LBgsygD6cAfGkdRWv
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, 03 Jul 2013 22:28:49 -0000

On Wed, Jul 3, 2013 at 3:20 PM, Eric Rescorla <ekr@rtfm.com>; wrote:

>
>
>
> On Wed, Jul 3, 2013 at 3:16 PM, Peter Thatcher <pthatcher@google.com>wrote:
>
>>
>>
>>
>> On Wed, Jul 3, 2013 at 3:04 PM, Eric Rescorla <ekr@rtfm.com>; wrote:
>>
>>> On Wed, Jul 3, 2013 at 2:42 PM, Iñaki Baz Castillo <ibc@aliax.net>wrote:
>>>
>>>> So compatibility with SIP is important but compatibility with Jingle is
>>>> just impossible. And this is supposed to be the API proposed to W3C...
>>>>
>>> Who said anything about impossible? It's a mechanical transformation
>>> (see: http://xmpp.org/extensions/xep-0167.html).
>>>
>>> Anyway, it's not like this feature is a surprise to anyone--well at
>>> least anyone who was paying attention--it's been a feature of the
>>> specification since before the WG was even formed. As I said
>>> earlier, it was in the original WHATWG spec that Ian Hickson
>>> wrote.
>>>
>>>
>
>>  There are lots of application developers who weren't around back then,
>> so it's not reasonable to expect them to have been paying attention back
>> then.  Many are very new to this, and there are lots of surprises for them.
>>
>
> The person I was responding to has posts on this mailing list going back
> as far as September 2011.
>
> -Ekr
>

You said "it's not like this feature is a surprise to anyone",  and I
thought "anyone" was a bit broader than that.  Sorry for the
misunderstanding.