Re: [rtcweb] Cisco to open source its H.264 implementation and absorb MPEG-LA licensing fees

Jack Moffitt <jack@metajack.im> Fri, 13 December 2013 01:12 UTC

Return-Path: <metajack@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F9B91AE05D for <rtcweb@ietfa.amsl.com>; Thu, 12 Dec 2013 17:12:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MNYOsOvOdZ0h for <rtcweb@ietfa.amsl.com>; Thu, 12 Dec 2013 17:12:10 -0800 (PST)
Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 45AE31AE193 for <rtcweb@ietf.org>; Thu, 12 Dec 2013 17:12:10 -0800 (PST)
Received: by mail-oa0-f49.google.com with SMTP id i4so1381455oah.36 for <rtcweb@ietf.org>; Thu, 12 Dec 2013 17:12:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=wq3bIeN4Gmp7f3FcArdNi+b4fp3S9K5zz0j6fLhs7dk=; b=ln4YU9O1qcltXawtaqBWhhHk0AipO+Sb3QmmtYIOIqmVObEor+wCRsh0O9oOckm0SB sQBLgy3HHSmpxmJdDX4RrPEMLlq9aPpHGVgpo3xcWOmdXelOpQNuFubS+n8U8U2IH15q bW7zsfXqhrTvu91kBX6rDp/hpoIOexV/kwmkiIEFKPOzauuU0w1pmMzsgE1FeaT+gGvm X5G8RFQ/NHKZeAWs12Byc81bg0M5PkglEJHZZ8azZneAkCZm8zC9TCVSAv2MkxG1gqvM AbFaLlX6FquOGu3GS2qsaGGu6qV8bvNn271aZVjG6TFFK0Vp/y/bMed4WbvN4+9BXa4w UdFg==
MIME-Version: 1.0
X-Received: by 10.60.144.228 with SMTP id sp4mr7621028oeb.29.1386897123926; Thu, 12 Dec 2013 17:12:03 -0800 (PST)
Sender: metajack@gmail.com
Received: by 10.60.17.70 with HTTP; Thu, 12 Dec 2013 17:12:03 -0800 (PST)
In-Reply-To: <28230E1E-A834-4C49-AC46-DBCC9818CEF5@iii.ca>
References: <186CE8D65BA3A741A81A543F936DD0D10A5803D8@xmb-rcd-x07.cisco.com> <A672E2AB-827D-46E8-9EB1-D7ED82B10B94@cisco.com> <20131211193239.GK3245@audi.shelbyville.oz> <558F8D49-4024-4DF1-9A9E-AF422F1292C2@iii.ca> <20131212011550.GM3245@audi.shelbyville.oz> <E8882BCE-4795-4CF5-B785-18C2141A5DE2@iii.ca> <20131212183852.GN3245@audi.shelbyville.oz> <9B19C671-4356-4918-B271-D95B7AA84BBA@iii.ca> <20131212213234.GQ3245@audi.shelbyville.oz> <52AA37E2.1070202@gmail.com> <20131212234430.GT3245@audi.shelbyville.oz> <28230E1E-A834-4C49-AC46-DBCC9818CEF5@iii.ca>
Date: Thu, 12 Dec 2013 18:12:03 -0700
X-Google-Sender-Auth: vwU3br98l9b5KNYEcudCdc39gJE
Message-ID: <CAP7VpsU3Kab9pFENanO_uecr6BOKxtLPc37mnTx3C-tjKpbP=g@mail.gmail.com>
From: Jack Moffitt <jack@metajack.im>
To: Cullen Jennings <fluffy@iii.ca>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Cisco to open source its H.264 implementation and absorb MPEG-LA licensing fees
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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, 13 Dec 2013 01:12:11 -0000

> The thing that is hard is making a compile match an existing binary when you don't really know how the original binary was compiled. The plan here is to exactly describe the process that Cisco uses to compile (which linux distro, which version, which compiler version etc, all the build scripts etc). Then any external group, such as Mozilla, can replicate theses instructions and get the same binary. I do realize that if you build the same code on even very similar systems, you may get a different binary. I realize it is not trivial to get this to all happen but we are confident it can be done.

This sounds very fragile. Why not just create a public EC2 image that
can build the code, and then everyone will have the same setup and it
will be easy to replicate. Or even better, just a standard chef or
puppet script that uses a well known stock public EC2 AMI.

jack.