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

Matt Fredrickson <creslin@digium.com> Wed, 30 October 2013 15:49 UTC

Return-Path: <creslin@digium.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 8167A21F9CAD for <rtcweb@ietfa.amsl.com>; Wed, 30 Oct 2013 08:49:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.826
X-Spam-Level:
X-Spam-Status: No, score=-2.826 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 Vt92ygzTbWSu for <rtcweb@ietfa.amsl.com>; Wed, 30 Oct 2013 08:49:04 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5BD0D11E8173 for <rtcweb@ietf.org>; Wed, 30 Oct 2013 08:48:18 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id ep20so1278580lab.3 for <rtcweb@ietf.org>; Wed, 30 Oct 2013 08:48:18 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=abNDCypa0pbwmCp9oe6BopWwUFqsySlANK8yWzjAj5c=; b=GcP1kOucUD9WyJn+Bkrsr8V39Gd7cNHgLfSDYTbTZvGA1YQ24MQO+scFaKf861wJGi /5dO9sqOrjvYLm6POw7N2OaPYTdJeel+8ytn8grZsLxRjicbtlU7CiZ3GjQE+Lbl7WLU RIPytwZeL5zHFpoByHRvXfsMedhNq8MPocihD1YatiGHsXtqY8d7VFAsEtr3Cbna2O0t wWiNYmTJTvZaXcvGmqSA/ppbozJuJ38R4WVBcSfFbnsNBd2BVkgyntFiF11xNIKQjpWl cT25IdppwnVS4ZbX2ziBeth+KjVE9VdE8itm9YBHDBRS/U+yrk+a+dbsb3r7ylUh9w3A xPLQ==
X-Gm-Message-State: ALoCoQl/KNmZvq1RjlWcntCgmFz6Dc59u2sw1sdQkjs3PLhrFy5U2nb7sb14pf4QpMxPY4UoV3Ce
MIME-Version: 1.0
X-Received: by 10.112.167.3 with SMTP id zk3mr3834363lbb.23.1383148098016; Wed, 30 Oct 2013 08:48:18 -0700 (PDT)
Received: by 10.112.132.102 with HTTP; Wed, 30 Oct 2013 08:48:17 -0700 (PDT)
In-Reply-To: <CA+9kkMDhYk894XMCxo9gYQjo_+AOheZiZuFCPH2x13UZodb7+Q@mail.gmail.com>
References: <186CE8D65BA3A741A81A543F936DD0D10A5803D8@xmb-rcd-x07.cisco.com> <CA+9kkMDhYk894XMCxo9gYQjo_+AOheZiZuFCPH2x13UZodb7+Q@mail.gmail.com>
Date: Wed, 30 Oct 2013 10:48:17 -0500
Message-ID: <CAHZ_z=zkLPCEsjjhAm+r1=kD4_SUfjyVfwdKOT2g20uyvTY5Pg@mail.gmail.com>
From: Matt Fredrickson <creslin@digium.com>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="001a11c264a40de98504e9f74336"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, "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 15:49:10 -0000

On Wed, Oct 30, 2013 at 10:44 AM, Ted Hardie <ted.ietf@gmail.com> wrote:

> Dr. Rosenberg, it's always good to have your contributions.
>
> Thanks for today's announcement; I have a couple of questions.
>
> In March, Cullen announced that Cisco would open source an H.264
> implementation if the working group selected H.264 as the MTI.  I assume
> that today's announcement is a follow-on to that intention, removing the
> requirement for H.264 to be the MTI for this generous gift, since there is
> no similar requirement in your statement.  Is that correct?  This will
> remain available even in the case some other codec is selected as MTI?
>
> The web site and your announcement say H.264, without naming specific
> profiles.  Will the details of which will be included come when the source
> code is available?  Do you have a timeline for when the source code might
> become available?  Since the board will also name supported platforms, can
> you give a timeline for when they might be disclosed?
>

I think the FAQ said the baseline profile will be initially included.

Matthew Fredrickson