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

"cb.list6" <cb.list6@gmail.com> Fri, 25 October 2013 16:36 UTC

Return-Path: <cb.list6@gmail.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 11BF211E836D for <rtcweb@ietfa.amsl.com>; Fri, 25 Oct 2013 09:36:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level:
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, 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 TIVcV5EomNJU for <rtcweb@ietfa.amsl.com>; Fri, 25 Oct 2013 09:36:01 -0700 (PDT)
Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE6B11E8363 for <rtcweb@ietf.org>; Fri, 25 Oct 2013 09:36:01 -0700 (PDT)
Received: by mail-we0-f171.google.com with SMTP id t60so4127146wes.30 for <rtcweb@ietf.org>; Fri, 25 Oct 2013 09:36:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8gFeSOeJrK2nNbXiMH568iOG9QbKQ/QSDBhHceftD28=; b=GZr27l2SR8Ph5RSPHT9OSfpTqnF45oRNORXhdAcVyhCGOqh8yzUGFCL4q7KNjXf+9T oRMoSRaeDKm2cXPU4+5e67KLWv11hHLLknbu5tBeaeXL/1zD5xBcdjcSgC1Yvndiah2W xihwlObf3fXhUe0xr6MktFNLNubMLlGDiX8p8wn8fiOK7NDkFLOBr/l3hc0boc+nw3w0 xXYt6EYkcfZClA0PzztAr+qCTEyPHLM9uU6dR1aGOa5vJ4GoVhgQGejlWXyLa4SSkD0Q 6kcFTu18dGz0NRI94xai0Fx80+646dtHib7kfr65W1Bt2F/Igqw9+GwrVwjGYKIkpZFV lIbw==
MIME-Version: 1.0
X-Received: by 10.194.20.170 with SMTP id o10mr8124820wje.4.1382718960136; Fri, 25 Oct 2013 09:36:00 -0700 (PDT)
Received: by 10.217.114.137 with HTTP; Fri, 25 Oct 2013 09:35:59 -0700 (PDT)
In-Reply-To: <5269F098.2020904@alvestrand.no>
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>
Date: Fri, 25 Oct 2013 09:35:59 -0700
Message-ID: <CAD6AjGQTSeVYjP0V--sbbMUYvTJuzqqh3r+K-pwve7KkS4dSgg@mail.gmail.com>
From: "cb.list6" <cb.list6@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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 16:36:19 -0000

On Thu, Oct 24, 2013 at 9:16 PM, Harald Alvestrand <harald@alvestrand.no> 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.
>

Yes. I should have done a better job of advocating no MTI in a timely manner.

I am happy to post an I-D when the tool comes back up, or i can email
it.  But, i respect the chairs need for a deadline and that i have
missed it.

I am happy to present the salient points in Vancouver if asked to.

That said, here they are in email:

1.  There are 2 camps H264 and VP8

2.  H264 and VP8 are both high quality and efficient video codecs,
there is no dispute

3.  H264 camp claims there is no IPR liability-free path.  Thus they
claim H264 has a more mature IPR model via MPEG than VP8.

4.  The IETF does not adjudicate on validity of any IPR claim, the
IETF only distributes information that is volunteered to the IETF.

5.  The 2 camps have irreconcilable legal and business assumptions,
thus the ideal of MTI cannot be achieved.

6.  Having both H264 and VP8 as MTI is not viable, because we know it
would cannot be true that both would be implemented.

7.  Voice-only WebRTC does have an MTI.  In the event that a common
video codec cannot be negotiated during video session setup, the
session SHOULD fall-back to voice-only session negotiation where there
is a MTI .

CB




> 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.
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb