Re: [rtcweb] Congratuiations on the Cisco announcement - but we still prefer VP8

Adam Roach <adam@nostrum.com> Fri, 01 November 2013 19:44 UTC

Return-Path: <adam@nostrum.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 B2F3A11E817A for <rtcweb@ietfa.amsl.com>; Fri, 1 Nov 2013 12:44:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.459
X-Spam-Level:
X-Spam-Status: No, score=-102.459 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001, 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 2ZisfZ4h0SjJ for <rtcweb@ietfa.amsl.com>; Fri, 1 Nov 2013 12:44:06 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5FF2711E8146 for <rtcweb@ietf.org>; Fri, 1 Nov 2013 12:44:02 -0700 (PDT)
Received: from orochi-2.roach.at (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id rA1Jhvra081479 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 1 Nov 2013 14:43:58 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <52740478.6030109@nostrum.com>
Date: Fri, 01 Nov 2013 14:43:52 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Harald Alvestrand <hta@google.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
References: <CAOqqYVEER_HprgauRawO+_gGdLdMY1MUY8jrMhhi3yVDL31bFg@mail.gmail.com>
In-Reply-To: <CAOqqYVEER_HprgauRawO+_gGdLdMY1MUY8jrMhhi3yVDL31bFg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------050209070102030801040605"
Received-SPF: pass (shaman.nostrum.com: 99.152.145.110 is authenticated by a trusted mechanism)
Subject: Re: [rtcweb] Congratuiations on the Cisco announcement - but we still prefer VP8
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, 01 Nov 2013 19:44:06 -0000

On 10/31/13 13:47, Harald Alvestrand wrote:
>
> We congratulate Cisco on their intention to make an open source H.264 
> codec available and usable by the community. We look forward to seeing 
> the result of this effort.
>
>
> Google still believes that VP8 - a freely available, fully open, 
> high-quality video codec that you can download, compile for your 
> platform, include in your binary, distribute and put into production 
> today - is the best choice of a Mandatory to Implement video codec for 
> the WebRTC effort.
>

I agree with Harald that VP8 is a better codec than H.264 baseline in a 
number of important ways.

But I also want to reiterate that having an MTI codec has never been 
about choosing the best codec or even a good codec. It's about choosing 
an emergency backup codec-of-last-resort. It's about having one single 
mandated codec that everyone has in their back pocket in case nothing 
else works.

The core of RTCWEB is about session *negotiation*. Endpoints will 
negotiate the best codec they have in common. Once the next generation 
of codecs come out, this "best codec in common" will only be the MTI if 
they were about to fail anyway.

So it doesn't have to be good.

It just has to be better than failure.

/a