Re: [rtcweb] Google statement on codecs

Maire Reavy <mdr@reavy.org> Mon, 30 July 2012 01:44 UTC

Return-Path: <mdr@reavy.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 D393111E80F9 for <rtcweb@ietfa.amsl.com>; Sun, 29 Jul 2012 18:44:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=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 nRvhiYEsTz4p for <rtcweb@ietfa.amsl.com>; Sun, 29 Jul 2012 18:44:33 -0700 (PDT)
Received: from r2-chicago.webserversystems.com (r2-chicago.webserversystems.com [173.236.101.58]) by ietfa.amsl.com (Postfix) with ESMTP id 2C03511E80F6 for <rtcweb@ietf.org>; Sun, 29 Jul 2012 18:44:33 -0700 (PDT)
Received: from static-68-179-67-73.ptr.terago.net ([68.179.67.73] helo=[10.244.29.137]) by r2-chicago.webserversystems.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <mdr@reavy.org>) id 1Svf29-0005Ux-3M for rtcweb@ietf.org; Sun, 29 Jul 2012 20:44:33 -0500
Message-ID: <5015E6FF.2000804@reavy.org>
Date: Sun, 29 Jul 2012 18:44:31 -0700
From: Maire Reavy <mdr@reavy.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CAOJ7v-2nghk6HcFv_6xAs+hrK=Uqm+oTsvqLFtxm4oDBY9oDgA@mail.gmail.com> <5015D506.5010201@mozilla.com>
In-Reply-To: <5015D506.5010201@mozilla.com>
Content-Type: multipart/alternative; boundary="------------050101040509030506060201"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - r2-chicago.webserversystems.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - reavy.org
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: Re: [rtcweb] Google statement on codecs
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: Mon, 30 Jul 2012 01:44:33 -0000

On 7/29/2012 5:27 PM, Timothy B. Terriberry wrote:
> Justin Uberti wrote:
>> Given the ability to deliver a royalty-free platform with no compromises
>> on quality, we see no reason to include mandatory royalty-bearing 
>> codecs.
>
> +1
>
> As Brendan Eich, Mozilla's CTO, outlined in his article 
> https://hacks.mozilla.org/2012/03/video-mobile-and-the-open-web/ back 
> in March, we believe very strongly in keeping WebRTC unencumbered.

Absolutely!  And that stance hasn't changed.

Mandating encumbered codecswould force open-source projects to violate 
the spec (by not implementing a mandatory codec).  For this reason and 
the reasons Justin cites, we believe Opus, G.711 and VP8 are the best 
mandatory-to-implement choices for the spec.

-- 
Maire Reavy <mreavy@mozilla.com>om>, _<mdr@reavy.org> _
Mozilla