Re: [rtcweb] VP8 vs H.264 - the core issue

Harald Alvestrand <harald@alvestrand.no> Sat, 26 October 2013 22:19 UTC

Return-Path: <harald@alvestrand.no>
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 714A621E8098 for <rtcweb@ietfa.amsl.com>; Sat, 26 Oct 2013 15:19:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level:
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 lE9-hufkYcYP for <rtcweb@ietfa.amsl.com>; Sat, 26 Oct 2013 15:19:28 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 475C711E8108 for <rtcweb@ietf.org>; Sat, 26 Oct 2013 15:19:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 49E2239E2B4 for <rtcweb@ietf.org>; Sun, 27 Oct 2013 00:19:19 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aXib3lNU9n7E for <rtcweb@ietf.org>; Sun, 27 Oct 2013 00:19:17 +0200 (CEST)
Received: from [10.1.218.3] (unknown [62.192.18.162]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 2E03539E2A9 for <rtcweb@ietf.org>; Sun, 27 Oct 2013 00:19:17 +0200 (CEST)
Message-ID: <526C3FE4.2040301@alvestrand.no>
Date: Sun, 27 Oct 2013 00:19:16 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <52681A96.2020904@alvestrand.no> <526826AF.5030308@librevideo.org> <52690090.2050609@alvestrand.no> <BBE9739C2C302046BD34B42713A1E2A22DFCD683@ESESSMB105.ericsson.se> <AE1A6B5FD507DC4FB3C5166F3A05A4843D45DC08@TK5EX14MBXC266.redmond.corp.microsoft.com> <5269764C.4030801@librevideo.org> <52698758.5040404@bbs.darktech.org> <CAD6AjGSb5syh0HO+89fH8cGZ0zqM6gYLPj3aeTRQLN0u8W4cSg@mail.gmail.com> <5269F098.2020904@alvestrand.no> <E44893DD4E290745BB608EB23FDDB7620A0F272E@008-AM1MPN1-043.mgdnok.nokia.com> <949EF20990823C4C85C18D59AA11AD8B0BF358@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CAGgHUiRtXUAJTotAFX7YwQ6cS_OD-MpAb+898c6OYxm7D5xXKw@mail.gmail.com> <FCBEDCB500188C488DA30C874B94F80E1C01158C@xmb-rcd-x03.cisco.com> <CAOJ7v-1iV4_SvToRYYtDZszxkSDF0qmrS4YN8w7OFQ3p29CaDw@mail.gmail.com> <526AE703.8000409@bbs.darktech.org> <CA+9kkMC=RrmAEyd0uWjpPhvCGuUnj5ATmuZrA7FnAxXhqMJXrg@mail.gmail.com> <526C15CD.5020601@bbs.darktech.org>
In-Reply-To: <526C15CD.5020601@bbs.darktech.org>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/alternative; boundary="------------070709010605070803020904"
Subject: Re: [rtcweb] VP8 vs H.264 - the core issue
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, 26 Oct 2013 22:19:34 -0000

On 10/26/2013 09:19 PM, cowwoc wrote:
> On 25/10/2013 7:23 PM, Ted Hardie wrote:
>> On Fri, Oct 25, 2013 at 2:47 PM, cowwoc <cowwoc@bbs.darktech.org
>> <mailto:cowwoc@bbs.darktech.org>> wrote:
>>
>>
>>         From an end-user point of view, the only thing I really care
>>     about is getting WebRTC support from Microsoft and Apple. Because
>>     I view everything through that prism, my primary concern is how
>>     this decision affects them jumping on board.
>>
>>
>> Do you mean "getting WebRTC support from Microsoft and Apple." or
>> "adding WebRTC support from Microsoft and  Apple to that available
>> from Firefox and Chrome?"
>>
>> regards,
>>
>> Ted Hardie
>
> Hi Ted,
>
>     I'm not sure whether I understood your question correctly. Is this
> what you meant?
>
>  1. Getting Microsoft and Apple to implement and bundle WebRTC as part
>     of IE and Safari, versus
>  2. Having outsiders (e.g. Firefox or Chrome) offer free plugins for
>     IE and Safari without Microsoft and Apple's support
>
>     If that's what you meant, then I'm asking for #1. As we've seen
> before (e.g. Chrome refusing to carry H264) just because a plugin is
> available does not mean that a vendor will agree to bundle it as part
> of the browser. As Monty pointed out, this has more to do with market
> control than licensing fees.
>
>     I think we will all suffer unless Microsoft and Apple genuinely
> want to jump on board the WebRTC train. I disagree with the assessment
> that they are sitting around waiting for us to make up our mind.
> Microsoft put out some feelers in the form of CU-RTC-Web and,
> regardless of the merits of that proposal, was clobbered from all
> directions. A more appropriate response would have been to sit down
> with their representatives and say "Listen. We value your feedback. We
> won't be able to integrate all of it in version 1.0 but here is a
> compromise that integrates part of what you said... Can we use this as
> a basis for an ongoing relationship?" Instead, the representative from
> Microsoft is sounding very defensive and I can't say I blame them.
>

I actually think Martin Thomson and Travis Leithead have been giving
great input and been positive contributors. Not to belittle the
contributions of others, but those two especially have made many
positive contributions.

>     An open process has to feel genuine, not just in words, but also
> in actions.
>
>

I think we may have some differing perspectives.

-- 
Surveillance is pervasive. Go Dark.