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

cowwoc <cowwoc@bbs.darktech.org> Fri, 25 October 2013 08:03 UTC

Return-Path: <cowwoc@bbs.darktech.org>
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 ECFE911E8158 for <rtcweb@ietfa.amsl.com>; Fri, 25 Oct 2013 01:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.099
X-Spam-Level:
X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5 tests=[AWL=-2.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 GMXXwvppwdoX for <rtcweb@ietfa.amsl.com>; Fri, 25 Oct 2013 01:03:21 -0700 (PDT)
Received: from mail-qc0-f176.google.com (mail-qc0-f176.google.com [209.85.216.176]) by ietfa.amsl.com (Postfix) with ESMTP id B7F0C11E82C3 for <rtcweb@ietf.org>; Fri, 25 Oct 2013 01:03:15 -0700 (PDT)
Received: by mail-qc0-f176.google.com with SMTP id s19so2001302qcw.7 for <rtcweb@ietf.org>; Fri, 25 Oct 2013 01:03:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=pYuA8IbzNd2/RCJUBZXYR2QMDs3OXycnptcVLD4Ucsw=; b=ZQawtYQ0j5IiUa7TnCOuAmB9DDR7NKd7+tJbgJWudrsSvgdowgCF9cKouVuHBkNh3A TwZN/Xa2gYsspasLh3GXYKnT+6YbCbKICLRR0oHKfbSQbepDRhfmhspJlljwAKjOiJIF Jp24Kl5oKjjMLRTNGFk/UFMh6eFUraxLjc+TqCLoNJYGHhRN52speEhl2tDs7WJzRxNN Rhxk6N9DWKy+7IK4CVyMEoUqDAcyb82pPPP2fV4oRLLIpeDQPNV4DKHoY7t8YPLWSRNF F5wvtZR/QiXzfdNiyXf3zQYeIVO3X/x1PhwdDtnW48oQ833b8lWWwARAF4VRVU+Xxpof 7spw==
X-Gm-Message-State: ALoCoQmLNcs6rMQDzJHekT0JilZTrgYjFTdsdeHi5KG4JNBK8f110Xt4qiu1VHKS7/OJ93xppfEJ
X-Received: by 10.224.57.77 with SMTP id b13mr9562425qah.63.1382688195167; Fri, 25 Oct 2013 01:03:15 -0700 (PDT)
Received: from [192.168.1.100] (206-248-171-209.dsl.teksavvy.com. [206.248.171.209]) by mx.google.com with ESMTPSA id k4sm16898919qaa.8.2013.10.25.01.03.13 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Oct 2013 01:03:14 -0700 (PDT)
Message-ID: <526A25C0.6080406@bbs.darktech.org>
Date: Fri, 25 Oct 2013 04:03:12 -0400
From: cowwoc <cowwoc@bbs.darktech.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
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>
In-Reply-To: <5269F098.2020904@alvestrand.no>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Fri, 25 Oct 2013 08:03:27 -0000

On 25/10/2013 12:16 AM, Harald Alvestrand wrote:
> On 10/25/2013 01:13 AM, cb.list6 wrote:
>>
>> There is no holding back vp8, it can always be negotiated.
>>
>> My guidance is no mti.
>>
>> I, for one, am tired of the gang-land ipr turf wars and posturing. 
>> This argument is all about ipr, and ietf is explicitly setup to punt 
>> on all ipr issue because they are hard.
>>
>> Any layperson can see there is no concensus to be found. That's why 
>> we designed for codec negotiating and negotiating away from failure 
>> is left for implementation
>>
> Formalistically, the people who argue for abandoning an MTI, like the 
> people who argue for adapting an antiquated codec, have not put in a 
> draft by the chairs' deadline of October 6, so have not made a proposal.
>
> But I'm not the one who argued for this to be put on the agenda for 2 
> hours.
> The people who pushed for this to be on the agenda for 2 hours need to 
> come forward and say why they believe this is a good use of our time. 
> I haven't yet heard a VP8 proponent saying so.
>
> So far, apart from learning a bit more about configuring x264, I 
> haven't seen much new information.

     I think the real elephant in the room is whether Apple and 
Microsoft (who are on the H264 bandwagon) will decide to implement VP8 
just because you mandate it or whether they will side-step WebRTC 
altogether. FireFox's market-share is decline so more and more this is 
becoming a story of Chrome vs IE (on desktop) + Safari (on mobile).

     The real question we should be asking is how to get Apple and 
Microsoft on board. If we could get everyone on board, the question of 
what codec should be used would melt away (hint: there is no objective 
answer to this question).

Gili