Re: [rtcweb] A different perspective on the video codec MTI discussion

David Singer <singer@apple.com> Thu, 14 March 2013 16:44 UTC

Return-Path: <singer@apple.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 C494411E80E7 for <rtcweb@ietfa.amsl.com>; Thu, 14 Mar 2013 09:44:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 uBd78YRrF-K4 for <rtcweb@ietfa.amsl.com>; Thu, 14 Mar 2013 09:44:15 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 3E3C521F8545 for <rtcweb@ietf.org>; Thu, 14 Mar 2013 09:44:15 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay2.apple.com ([17.128.113.67]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MJN00BOPT5MKRA0@mail-out.apple.com> for rtcweb@ietf.org; Thu, 14 Mar 2013 09:44:14 -0700 (PDT)
X-AuditID: 11807143-b7f896d000006d55-82-5141fe5ea550
Received: from cardamom.apple.com (cardamom.apple.com [17.128.115.94]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate) by relay2.apple.com (Apple SCV relay) with SMTP id 07.CF.27989.E5EF1415; Thu, 14 Mar 2013 09:44:14 -0700 (PDT)
Received: from singda.apple.com ([17.197.32.11]) by cardamom.apple.com (Oracle Communications Messaging Server 7u4-24.01 (7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTPSA id <0MJN0062MT5QN250@cardamom.apple.com> for rtcweb@ietf.org; Thu, 14 Mar 2013 09:44:14 -0700 (PDT)
From: David Singer <singer@apple.com>
In-reply-to: <CAEWS6TJPKXdf7i140wKMZFHBcSVBtCxwzViWYYFgL01D=LdmEg@mail.gmail.com>
Date: Thu, 14 Mar 2013 09:44:14 -0700
Message-id: <F0FCD7D0-969E-46D9-9681-3A64D36F59DF@apple.com>
References: <CA+23+fE3WRs5SxAUcsjWbxcjzQKxCtW7sdfHtAsbd7MbPyHAtQ@mail.gmail.com> <CAEWS6TJPKXdf7i140wKMZFHBcSVBtCxwzViWYYFgL01D=LdmEg@mail.gmail.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
X-Mailer: Apple Mail (2.1499)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCLMWRmVeSWpSXmKPExsUi2FAcpxv3zzHQoOeascXaf+3sDoweS5b8 ZApgjOKySUnNySxLLdK3S+DKmNT1iLngPHfFyW/vmBsYV3B2MXJySAiYSKzd0cMOYYtJXLi3 ng3EFhKYyCRx9nxQFyMXkD2TSeLd5heMXYwcHMwCehL3L2qBmLxA5qT9QSDlwgL+Epv3LWQC sdkEVCUezDkGVs0pECxx5k4iiMkCFP49IwakgllAW+LJuwusIDavgI1E27crrFCLGCUmXNkH NkZEQF3i8sMLUJfJSqyY2ss0gZF/FsINsxBumIVk6gJG5lWMAkWpOYmVRnqJBQU5qXrJ+bmb GMFhVei8g/HYMqtDjAIcjEo8vA4PHQOFWBPLiitzDzFKcDArifDu+gsU4k1JrKxKLcqPLyrN SS0+xCjNwaIkzru+wz5QSCA9sSQ1OzW1ILUIJsvEwSnVwMjbe5BXszI8/cX9twxrmeewnNRK 3njfI6KzOqM7SrngcNwy+3vp+ceyJsjI79XW3fm3u9tt1y6zKjdmVfmskoS999o28GsdERbl 9GGWFlDXfdb+keHl/TPPK42sbjNuO71Gumm7abnp6xvl9Tknpk8xdl/l9uG5xQL59U42F1RL q+TZChsllFiKMxINtZiLihMB+oCayCcCAAA=
Subject: Re: [rtcweb] A different perspective on the video codec MTI discussion
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: Thu, 14 Mar 2013 16:44:15 -0000

On Mar 14, 2013, at 9:24 , Ben Strong <ben@vline.com> wrote:

> However, I fail to see how either one of those points has any bearing on the MTI decision. The whole point of MTI is guaranteed interoperability across all WebRTC implementations, which is absolutely critical to WebRTC adoption. The only criteria should be the best quality codec which can be supported by all implementations. And because some implementations are open source, it absolutely must be royalty free.

I think you make a key point here; making a mandate that doesn't have consensus is empty, as if (for example) companies are forced to choose between formally complying with the mandate, or taking on excessive risk, they'll probably be risk-averse. Or a mandate that carries a license fee will be ignored by those who don't pay such fees on principle.

We all need a decision we can all stand behind, and we're making progress to that goal, and I appreciate all the data and efforts.  There is some very important data (notably, the names of the 11 and the resulting license) which is promised to be available in only a few weeks. Let's not decide in haste (and possibly repent at leisure).


By the way, open-source and license fees are not in direct conflict; it's the principles that are.  To pick a directly-relevant example, there are open-source implementations of H.264 (AVC).

David Singer
Multimedia and Software Standards, Apple Inc.