Re: [rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)

Peter Thatcher <pthatcher@google.com> Sat, 20 July 2013 01:01 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 D4BB621E8064 for <rtcweb@ietfa.amsl.com>; Fri, 19 Jul 2013 18:01:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.761
X-Spam-Level:
X-Spam-Status: No, score=-1.761 tagged_above=-999 required=5 tests=[AWL=0.216, 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 Bry0QDa6n+HU for <rtcweb@ietfa.amsl.com>; Fri, 19 Jul 2013 18:01:31 -0700 (PDT)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 5D8B121E8056 for <rtcweb@ietf.org>; Fri, 19 Jul 2013 18:01:31 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id 4so4776676pdd.20 for <rtcweb@ietf.org>; Fri, 19 Jul 2013 18:01:31 -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=Y0QnFsKASv6QijmBLKrqTRv/JjnHohFNGsvwXxw6jcY=; b=Ccy804TKbNwyuBU8q/uB0XMojGY4PXMNO7D0FE/I+dOlncBgbv8x2VHImqljK3JdhL mzKT1HGz0My2EXGK9iQ+L8n2+N0Mj9k1hbhRhQBNVMi3VczrAZb+PPA2qHJsF47e1q4l ZGzq2SO9DGJwYJ66n691nJzA/PEX7GdEzXshLB1HPhkf8D7PdMQ535p4lwcYoa8cUc2Z HVyK/y6NXHlFAdNjB8pjH9FLuprig1k9bg26CTZ/PbK9kYI8fGTTb55+/yxPrmkns9Yc 7DQieTXjnEGtARH3xY8IPN7SYynF62SyPC4nIANpDGtjlzgbPaeHquvkmfg2tQhAs5yB WY7Q==
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=Y0QnFsKASv6QijmBLKrqTRv/JjnHohFNGsvwXxw6jcY=; b=GDMK2vMqAw7CCSn9VRcvz+DC5Mi0PdmSH+toCPAnQhjFwDdcAjQIKd7CenjavCNCpp I7QP7RSK7RXf3LTswsX3yy3/K3ueM4yj8+K0gB6UzWE0ouWCx1nlDxx32EhU7vB/QH3q bxGGDm1Trn1JpL2PSiMqM7nMoxStEtD3f4c/z/qUWCK4l5XxF1kT4HjDEWBXsea6zw3e h4gA85s8E2lwQrwXBYCffOW7ZNTtDuCNypzbJlFsGsZECl8IOuvWjNdAJZpd9YYyNpHH OJFRA1BP5fOBlsH2xTkIerXovwyagdGbpljVhMjJ5jDSL9BRDh2ZrnTmf1hw0d2pIbpS GosQ==
X-Received: by 10.68.217.7 with SMTP id ou7mr19861519pbc.8.1374282091011; Fri, 19 Jul 2013 18:01:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.78.195 with HTTP; Fri, 19 Jul 2013 18:00:49 -0700 (PDT)
In-Reply-To: <644AB0EE-8889-4940-BA88-33EA653D44DC@iii.ca>
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> <AE1A6B5FD507DC4FB3C5166F3A05A484213E41E7@TK5EX14MBXC265.redmond.corp.microsoft.com> <C50FDAD5-492C-4A83-AD6D-464242FB4A05@iii.ca> <CALiegfneUj=kzDjR_E1=S-bqAajaPUE3f_A2g8oGriFyPhamPA@mail.gmail.com> <51E96B5B.2050302@nostrum.com> <CABkgnnXa-eTzRHcLMnHam4c+1D9kkvRwi9=V-9P43+p+pKE_sw@mail.gmail.com> <644AB0EE-8889-4940-BA88-33EA653D44DC@iii.ca>
From: Peter Thatcher <pthatcher@google.com>
Date: Fri, 19 Jul 2013 18:00:49 -0700
Message-ID: <CAJrXDUGwpi2xZ1U3W0HX9SQ=VhuCB52ngfaSrPqO4_5SXQ=cYQ@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Content-Type: multipart/alternative; boundary=e89a8ff24319db461b04e1e6fbfd
X-Gm-Message-State: ALoCoQk8BIDD6jdUAVJLHBisdIDgphNee6QVTfhnIbrnmc6MD9SxHcxUCO5GlU8z+BN5/kYQBVGzu7jAGeQoGecOX6OasWbEHIeqNlWOgxFdlDRBAva3dGPJbn9F9xHPRPJzQ21c0HPH7+DV9ZTFcDCDQePrGiMbg47jOLq8rB5u/mf/RxcZhaxp/Y1+stxGdPBFupnjr8Z0
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Subject: Re: [rtcweb] On babies and bathwater (was Re: 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: Sat, 20 Jul 2013 01:01:31 -0000

The logic of how to talk to the video conferencing system doesn't need to
be backed into the browser.  If the API provides enough control the JS, the
web app can contain the logic to talk to the video conferencing system.

I know I'm going to start sounding like a broken record, but you brought up
video conferencing systems as an example, so I will say it again: there are
are video conferencing systems that don't use SDP for signalling.  For
example, there are video conferencing systems that use Jingle for
signalling.  Would I expect the logic of how to speak to that video
conferencing system to be baked into the browser?  No, I think I'd prefer
it to be built into a web app built on top of a good API.  Why should
SDP-based video conferencing systems be treated special?


On Fri, Jul 19, 2013 at 5:52 PM, Cullen Jennings <fluffy@iii.ca>; wrote:

>
> On Jul 19, 2013, at 9:54 AM, Martin Thomson <martin.thomson@gmail.com>;
> wrote:
>
> > Negotiation is a hole.  A vast, soul-sucking, waste of time.
>
> That's might be closer to true when you control both ends, like Skype.
>
> It's not true when a browser from one vendor running an application from a
> scone vendor needs to talk to video conferencing system from a third vendor.
>
>
>
>