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

Leon Geyser <lgeyser@gmail.com> Wed, 30 October 2013 16:44 UTC

Return-Path: <lgeyser@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 1675021E8146 for <rtcweb@ietfa.amsl.com>; Wed, 30 Oct 2013 09:44:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level:
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 qdp2FVr9PpCM for <rtcweb@ietfa.amsl.com>; Wed, 30 Oct 2013 09:44:03 -0700 (PDT)
Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 1190821E812A for <rtcweb@ietf.org>; Wed, 30 Oct 2013 09:42:46 -0700 (PDT)
Received: by mail-lb0-f173.google.com with SMTP id w7so1430181lbi.18 for <rtcweb@ietf.org>; Wed, 30 Oct 2013 09:42:46 -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=E5fPaLhmUHKjNAJZZOstSOmz5xMNDdtjoV37z4+Kbho=; b=n5xhR9nPdfMMsHolgfyITIjC/QapEyxtZvt+WNNEzfGlFOZ2eUeXYOxp2fn9qr1E// HztjhOg6E2xLP1jkJUmRtawiFVxr+uu9zv9ryatLLgfFRnR8OZGdOf5Q7/PY4aomLP/R m5TARk7PS/FSzZf3q2aknyqgsU/gBbNXywCsBnAzwLWqTY/eAlHeIs4b55SSa2a9U/m6 E/UNLhBUPneKb3g/YWlI9EP/fvR/2bhetqvxo3VUUD9q+iHWyrHbnEdpCuKVYzPYGe5B Gle91uXSK2HxJCVqtFbgm9BGjBxJBLLdTFxJjn0GJNgeOblc1gDdvSsrrEuCq7JmwAGu YPAw==
MIME-Version: 1.0
X-Received: by 10.112.146.200 with SMTP id te8mr3990287lbb.32.1383151365999; Wed, 30 Oct 2013 09:42:45 -0700 (PDT)
Received: by 10.114.168.70 with HTTP; Wed, 30 Oct 2013 09:42:45 -0700 (PDT)
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB123CF835F@xmb-aln-x02.cisco.com>
References: <186CE8D65BA3A741A81A543F936DD0D10A5803D8@xmb-rcd-x07.cisco.com> <527107e5.0201430a.0aa1.ffff9b09SMTPIN_ADDED_BROKEN@mx.google.com> <CAGgHUiSOFGxuNmqoa9BS2+_yjT2hb20KDut5WL264x5tdpTU-g@mail.gmail.com> <CA+23+fHdKBwezhtsES1w_qDJgvVC=ChaBcaF1x0_N65aKv-9yQ@mail.gmail.com> <CAHZ_z=wsQFB=SoH5zq-p-J7KkqrAx4gWJFkPLyAoFtZ8b2zP+w@mail.gmail.com> <527128A7.3050101@nostrum.com> <20131030164716.3d3be136@lminiero> <CALQ_quj6LyjhV1JocAH-aY7o4ppLNZFmYfe9kLVsddzTZA2U6g@mail.gmail.com> <CAHZ_z=xAviWcmpEhp-JHgzzCG-zMF5itqtvs8tyuK0YPTq8GoQ@mail.gmail.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123CF835F@xmb-aln-x02.cisco.com>
Date: Wed, 30 Oct 2013 18:42:45 +0200
Message-ID: <CAGgHUiRNeM0LtsZgTec9ZX-b50VWQdVKyy0_rhG4Uknh72pzig@mail.gmail.com>
From: Leon Geyser <lgeyser@gmail.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="047d7b3a83d4d7577e04e9f80546"
Cc: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, "Jonathan Rosenberg (jdrosen)" <jdrosen@cisco.com>
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.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: Wed, 30 Oct 2013 16:44:11 -0000

It is all great, but how do we solve the problem to support current or
future platforms that don't support downloading a BLOB onto the device and
then using it?


On 30 October 2013 18:17, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote:

>
> On Oct 30, 2013, at 9:55 AM, Matt Fredrickson <creslin@digium.com> wrote:
>
> > That is only as long as the binary versions don't have any additions or
> changes for such things.  Nothing says that the binary modules cannot be
> built in this way.
>
> The binary module will be build that way.
>
> All the build scripts etc that Cisco uses will be part of the open source
> project so that anyone can build it them selves and check that their build
> matches the Cisco binary and check the code does not have backdoors to send
> all your video to the NSA.
>
>
> >
> > Matthew Fredrickson
> >
> >
> > On Wed, Oct 30, 2013 at 10:52 AM, Ethan Hugg <ethanhugg@gmail.com>
> wrote:
> >
> > Lorenzo,
> >
> > You will be able to inspect the source yourself for nefarious things
> like tracking as the code will be freely available.
> >
> > -EH
> >
> >
> >
> > On Wed, Oct 30, 2013 at 8:47 AM, Lorenzo Miniero <lorenzo@meetecho.com>
> wrote:
> > Il giorno Wed, 30 Oct 2013 10:41:27 -0500
> > Adam Roach <adam@nostrum.com> ha scritto:
> >
> > > On 10/30/13 10:20, Matt Fredrickson wrote:
> > > > Does this mean that system information (for systems that this is
> > > > installed on) may be tracked and sent back to the Cisco servers for
> > > > accurate license usage count?  (ethernet MAC address, or some other
> > > > system specific info) so that redownloads of modules on the same
> > > > system are not counted towards your license usage accounting?
> > >
> > > My understanding is that MPEG-LA has a per-organization royalty cap
> > > for H.264 (13 MUSD, if my memory serves), and that Cisco reaches that
> > > cap quite easily with their own products.
> > >
> > > /a
> >
> >
> > Which doesn't preclude the fact the module may do tracking anyway.
> >
> > Lorenzo
> >
> >
> > > _______________________________________________
> > > rtcweb mailing list
> > > rtcweb@ietf.org
> > > https://www.ietf.org/mailman/listinfo/rtcweb
> >
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtcweb
> >
> >
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtcweb
> >
> >
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtcweb
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>