Re: [rtcweb] revisiting why WebRTC is succeeding everywhere but the Web

Eric Rescorla <ekr@rtfm.com> Wed, 17 December 2014 16:56 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 921161A8F4C for <rtcweb@ietfa.amsl.com>; Wed, 17 Dec 2014 08:56:34 -0800 (PST)
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=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AxDLXp6PU2vd for <rtcweb@ietfa.amsl.com>; Wed, 17 Dec 2014 08:56:31 -0800 (PST)
Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2C681A8F50 for <rtcweb@ietf.org>; Wed, 17 Dec 2014 08:56:30 -0800 (PST)
Received: by mail-wg0-f46.google.com with SMTP id x13so20858808wgg.19 for <rtcweb@ietf.org>; Wed, 17 Dec 2014 08:56:29 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=fZSXhTaMOLy6UJsvqpXnhxV/r0VKFfnEnarUcKIgGjQ=; b=Qbu4cfxtlANJc9078KNLkjqPwLwTYdxXcP1nRZAB9uFzBqFUqEhTV6WOxYDO7e5WSL inpYDV57rtPudseYfA3EOXRCaKTEdzdkMyyxD3t89/fTEVq/w830sx2dpMBZY6hXGFMI ALePrbZUzGRw91s2k5x4MF9WrFlp+UuIHphhbyeI6oBWK3Utv7F/+QRWvyqy7CHwpRHh TxS3UiWMW4ryRNFDP0gI7KGGo6TO0vrEq0WmI+FRT9rvT1R6OHrGDRFUVJ6W0kE0gUDS rlX0R14+P+5xialbDxThqeG9da4/ySzF7eM9JYSuJ8nwDluo7Y2bcqRQW7NbPCOzN51X socA==
X-Gm-Message-State: ALoCoQlcO1GdcwG0fgbHtmZqvdIYnqP7bELI1CELWGa12XDpe8MAHEMBl6pl/6/kFTV3qPOwuZmR
X-Received: by 10.180.19.193 with SMTP id h1mr16277892wie.10.1418835389240; Wed, 17 Dec 2014 08:56:29 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.130.34 with HTTP; Wed, 17 Dec 2014 08:55:49 -0800 (PST)
In-Reply-To: <554C8171-7804-4887-AE19-407C5DF816C8@unina.it>
References: <548F0E28.8040503@andyet.net> <20141215192409.GN47023@verdi> <548F54A5.2060105@andyet.net> <CA+9kkMDNhRdbzCs9vrqDeD4CoWWK1xS5o0z3jL0DvNpDuLfCPw@mail.gmail.com> <548F5E22.2040605@andyet.net> <548F5F0E.4050100@nostrum.com> <548F5FB8.9010300@andyet.net> <548F646C.1050406@nostrum.com> <20141216150303.GT47023@verdi> <CABcZeBOAfuscG28PMAu8JJ4yAAt1-ohnuqCaeoa+jkpDkJhhpw@mail.gmail.com> <20141216152100.GU47023@verdi> <54905132.40105@alvestrand.no> <5B1166AB-A2EA-4F83-ABB2-8947D044B159@apple.com> <54909198.7040409@nostrum.com> <FC77807D-E811-46DE-920C-2019C2E0A563@apple.com> <228CCD7E-143B-4ACA-9730-D3D6BB07694A@gmail.com> <CA+9kkMBjCOnv+b7yNUSKCUscgQOozEcAvuCmymzyCY8+Kudczw@mail.gmail.com> <F7F3EFE2-7258-4AE6-B736-71850692429B@gmail.com> <554C8171-7804-4887-AE19-407C5DF816C8@unina.it>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 17 Dec 2014 08:55:49 -0800
Message-ID: <CABcZeBM8=j=ur0+Lt6pVL7td30_OUzCCtfUcZwP6k1Mnq0QuLg@mail.gmail.com>
To: Simon Pietro Romano <spromano@unina.it>
Content-Type: multipart/alternative; boundary=bcaec53d526f5ef7de050a6c5b52
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/h3MG4QggZSJ2Nunn9yZXWKFhh6c
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] revisiting why WebRTC is succeeding everywhere but the Web
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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 Dec 2014 16:56:34 -0000

It's also worth observing that a lot of the problem with multiple stream
polyfills
isn't a result of the state of standardization but just that Firefox
doesn't do
it yet, so you have to simulate with multiple PCs. We're working on it now,
though.

-Ekr




On Wed, Dec 17, 2014 at 8:39 AM, Simon Pietro Romano <spromano@unina.it>
wrote:
>
> It is possible to write a single stream audio/video app that runs on any
> browser.  But if you include the video features that enable collaborative
> Web apps like Skype for Web, Hangouts, Jitsi Meet, etc. then yes there are
> no polyfills today.  So these Web apps need to be written for a particular
> browser.  By now people are getting used to installing a browser to run
> their favorite WebRTC web app.
>
>
> Based on my experience, if you stick to the Maximum Common Divisor (e.g.,
> by avoiding SSRC multiplexing, on hold, some forms of bundling, etc) you
> can still offer a rich end-user experience on a wide set of browsers
> (Chrome, Firefox, Opera at least). This is indeed what we try and do with
> the 'stable' version of Meetecho (which you probably forgot to mention).
> BTW, I think this is unavoidable as long as the standardization process has
> not yet reached the steady state.
>
> Simon
>
> That's not the IETF's problem really (WebRTC protocols and open source
> SDKs implementing same are in much better shape, and are being widely
> used). But it is indicative of the mountain that WebRTC needs to be climb
> to be a successful Web standard.
>
> On Dec 16, 2014, at 5:43 PM, Ted Hardie <ted.ietf@gmail.com> wrote:
>
> On Tue, Dec 16, 2014 at 2:30 PM, Bernard Aboba <bernard.aboba@gmail.com>
> wrote:
>
>> On Dec 16, 2014, at 3:18 PM, David Singer <singer@apple.com> wrote:
>>
>> However the browser model is very different. The browser app developer
>> typically cannot compile their own browser or fix browser bugs so they have
>> to live with what is there. Today's polyfills typically only work for audio
>> so writing a multi-browser video app that supports multiple video streams
>> is a nightmare even without a codec problem.
>>
>>
> ​So, can I confirm here that you mean polyfill in the same way ​Remy Sharp
> did?  That is, a piece of Javascript that replicates an API and
> functionality that the browser lacks?
>
> And so you are asserting that there are downloadable Javascript bits that
> replicate both the audio functionality and relevant API, but there are no
> downloadable Javascript bits that replicate the video functionality and
> relevant API?
>
> Have I gotten your meaning?
>
> Ted
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>
>                              _\\|//_
>                                   ( O-O )
>    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
>                      Simon Pietro Romano
>                Universita' di Napoli Federico II
>                       Computer Engineering Department
>              Phone: +39 081 7683823 -- Fax: +39 081 7683816
>                                            e-mail: spromano@unina.it
>
>     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
>     idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
>                                      oooO
>   ~~~~~~~~~~~~~~~~~~~~~~~(   )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
>                  \ (            (   )
>                                   \_)          ) /
>                                                                        (_/
>
>
>
>
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>