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

cowwoc <cowwoc@bbs.darktech.org> Thu, 31 October 2013 09:32 UTC

Return-Path: <cowwoc@bbs.darktech.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 A44C511E820B for <rtcweb@ietfa.amsl.com>; Thu, 31 Oct 2013 02:32:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.121
X-Spam-Level:
X-Spam-Status: No, score=-5.121 tagged_above=-999 required=5 tests=[AWL=-1.522, BAYES_00=-2.599, 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 4hV4iw2+Wfvm for <rtcweb@ietfa.amsl.com>; Thu, 31 Oct 2013 02:32:38 -0700 (PDT)
Received: from mail-qe0-f49.google.com (mail-qe0-f49.google.com [209.85.128.49]) by ietfa.amsl.com (Postfix) with ESMTP id C340311E8211 for <rtcweb@ietf.org>; Thu, 31 Oct 2013 02:32:37 -0700 (PDT)
Received: by mail-qe0-f49.google.com with SMTP id a11so1550670qen.8 for <rtcweb@ietf.org>; Thu, 31 Oct 2013 02:32:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=G0qJmBpaiQzBZ4bRvlBFRTLjxXfCfL9Iq25Nenh/QLM=; b=SRyO+poSUD3+jKh5RMgTJcZnWCGfoOxK+ek5Q/BVko/UT3G5K2/7SvXSxnebHqjHB9 Wm8WEg4Ta9cFVJ24R4fu/QrlBp9WaGI9k4sh/zuwG7+7IsStiog0fVFDCf3KjUyMrUrc NJGI8kCkFW/4D/rBnSxCUI75jOp6Z5Z0Mx2Dv0RSy8nQuTxSFD5FO4dzxipmnPNra1Q0 46aNu+w4Lnhy+GKQ2Z2qsajqPiESIq5gA57BrWhEtd46XIu5OSK+AOoeYRkK+14SoYMW NA3r1GOovaaQ+txWPGut6pM0dds4WHxkL0cbim2p8sYcC7eIIpwRtgqm/I1psKs8DHpD mhJw==
X-Gm-Message-State: ALoCoQmPfuhOlVcFbVFdDRb1C/U15FX/EZKDC9/HK684ujnJ3zqWruuKTu5/tMwt4ceGx3cMyqHD
X-Received: by 10.49.116.66 with SMTP id ju2mr1117803qeb.94.1383211957237; Thu, 31 Oct 2013 02:32:37 -0700 (PDT)
Received: from [192.168.1.100] (206-248-171-209.dsl.teksavvy.com. [206.248.171.209]) by mx.google.com with ESMTPSA id r5sm7258153qaj.13.2013.10.31.02.32.35 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 31 Oct 2013 02:32:36 -0700 (PDT)
Message-ID: <527223B0.5060204@bbs.darktech.org>
Date: Thu, 31 Oct 2013 05:32:32 -0400
From: cowwoc <cowwoc@bbs.darktech.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: David Singer <singer@apple.com>
References: <186CE8D65BA3A741A81A543F936DD0D10A5803D8@xmb-rcd-x07.cisco.com> <20131030201651.79401531@lminiero> <949EF20990823C4C85C18D59AA11AD8B0C4743@FR712WXCHMBA11.zeu.alcatel-lucent.com> <52716D29.6050403@bbs.darktech.org> <59056F16-7501-40B3-8799-47CA7EBAE99C@apple.com>
In-Reply-To: <59056F16-7501-40B3-8799-47CA7EBAE99C@apple.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
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.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, 31 Oct 2013 09:32:45 -0000

On 31/10/2013 5:14 AM, David Singer wrote:
> On Oct 30, 2013, at 21:33 , cowwoc <cowwoc@bbs.darktech.org> wrote:
>
>>      While I appreciate Cisco's huge contribution in this area, Lorenzo and Keith bring up some good points.
>>
>>      How about this approach?
>> 	• Mandate both codecs as MTI
>> 	• If either codec becomes problematic (requiring us to pay royalties) we simply drop that codec as MTI (implementation becomes optional) and searching for a replacement to add as MTI. In the meantime, we have that other codec to fall back on.
> That is, alas, not the only way a codec becomes problematic.  One can also get sued.
>
>>      With this approach we no longer have to depend on the generosity of Cisco or Google, and it reduces the incentive of patent trolls (it's harder to squeeze us for royalties when we have a fallback).

     I'm no lawyer but, my understanding is that this could happen no 
matter what codec we choose. Our goal should be to minimize the 
probability of infringement, reduce the profitability of suing, and 
provide a backup plan if we're forced to move off a codec.

     At least with this approach our liability is limited to past 
infringement. They can't blackmail us with unreasonable licensing fees 
because we can switch to the other codec without losing our business. 
This lowers the profitability of suing which reduces the chance that 
they'll sue in the first place. At least, that's my reasoning :)

Gili