Re: [rtcweb] H.261

Maik Merten <maikmerten@googlemail.com> Fri, 22 November 2013 18:09 UTC

Return-Path: <maikmerten@googlemail.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 14BFE1AD959 for <rtcweb@ietfa.amsl.com>; Fri, 22 Nov 2013 10:09:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 2SUz34TQ_LE0 for <rtcweb@ietfa.amsl.com>; Fri, 22 Nov 2013 10:08:57 -0800 (PST)
Received: from mail-ea0-x230.google.com (mail-ea0-x230.google.com [IPv6:2a00:1450:4013:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 4F9361ADFCE for <rtcweb@ietf.org>; Fri, 22 Nov 2013 10:08:57 -0800 (PST)
Received: by mail-ea0-f176.google.com with SMTP id h14so668840eaj.21 for <rtcweb@ietf.org>; Fri, 22 Nov 2013 10:08:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=fXAkyUYQdG/BOZOO1ql+LRlyszZtbZxxGl/1k9ZpijQ=; b=RTzC6YFk1/3Z2lKM7q2pd+MReRZSh3ux5N2GFjqklQCijaUrXwhRz4hQ84uhpm4c8j w8yzd8p9M2ajoRaH2i+BM01KpMC/F4K8VfUzJ4zycGAcsdL2gJUWxWuqn/7ZFUFshmqd 2F8363suH7kjU4PbPCGwDej9wG4WtzRwruCjsWtvY7zL88cf8YppQVvVc1KkVfgDQGIt 1cGdLNOuNQqvcu+P2744GVzQgb0NA0Arvl0z4qP8+IS3uZm1Qvg+7hq4wX7nV7QkLrM5 PCPXd6eah2v0D4FoHmXmWO2Veq9Td8Cavx+dpdJzCxmd2BgeGPUO7RKiFxs7wLe3ois/ HuxQ==
X-Received: by 10.14.47.130 with SMTP id t2mr8904526eeb.12.1385143729770; Fri, 22 Nov 2013 10:08:49 -0800 (PST)
Received: from [192.168.2.109] (port-92-201-19-228.dynamic.qsc.de. [92.201.19.228]) by mx.google.com with ESMTPSA id e43sm640849eep.7.2013.11.22.10.08.47 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 22 Nov 2013 10:08:48 -0800 (PST)
Message-ID: <528F9DAD.3030300@googlemail.com>
Date: Fri, 22 Nov 2013 19:08:45 +0100
From: Maik Merten <maikmerten@googlemail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CEB4350B.1E7B2%mzanaty@cisco.com> <20131122171020.GY3245@audi.shelbyville.oz> <7949EED078736C4881C92F656DC6F6C130EA9E66AF@ausmsex00.austin.kmvtechnologies.com>
In-Reply-To: <7949EED078736C4881C92F656DC6F6C130EA9E66AF@ausmsex00.austin.kmvtechnologies.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] H.261
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, 22 Nov 2013 18:09:00 -0000

Disclaimer: IANAL

You can get *sued* for anything from anyone at any time. Trolls are not 
in the business of making sound claims on technology, they're in the 
business of getting paid to leave you alone.

However, you will have as good a defense as you can get if you can point 
to a 25 years old reference implementation. Such an old reference 
implementation (including an encoder) exists for H.261, meaning a set of 
encoder techniques should be identifiable that is "as safe as it can 
be". Of course, if your encoder introduces encoding techniques beyond 
that you're not automatically "safe" anymore. However, the existence of 
spec-compliant H.261 encoders in the late 1980ies clearly means that old 
techniques exist that are useful for creating valid H.261 streams.

In a nutshell: Doing really old stuff *should* actually improve your 
standing regarding IPR claims.

Of course, a troll might have a nice patent like "Method and apparatus 
for doing real-time bible lessons over a digital network in the context 
of hypertext-enabled applications" which might or might not read on any 
WebRTC implementation, no matter what the codec. The fix for that: Don't 
implement anything, ever.


Maik


Am 22.11.2013 18:23, schrieb Stefan Slivinski:
> You are not going to avoid patent issues with H.261.  Even if all patents associated with the H.261 specification have expired you are going to run into generic video patents around motion estimation or rate distortion and many, many other areas that have not.  At the end of the day, if a patent troll sees you have money, they are going to find a way to sue you.
>
> -----Original Message-----
> From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Ron
> Sent: Friday, November 22, 2013 9:10 AM
> To: rtcweb@ietf.org
> Subject: Re: [rtcweb] H.261
>
> On Fri, Nov 22, 2013 at 05:17:45AM +0000, Mo Zanaty (mzanaty) wrote:
>> On 11/21/13 12:48, Basil Mohamed Gohar <basilgohar@librevideo.org<mailto:basilgohar@librevideo.org>> wrote:
>> Has anyone actually objected to H.261 being the one MTI codec [...] ?
>>
>> Assume this wins and all obey. Chrome does H.261+VP8, Firefox does
>> H.261+H.264+VP8, IE does H.261+H.264, Safari does H.261+H.264.
>> According to various (incredibly extrapolated, possibly inaccurate and
>> sometimes
>> conflicting) sources [1] on who uses what browser, the chance of H.261
>> fallback is a whopping 30% [2]. Not the minor insignificant case some
>> had assumed.
>>
>> How will these users react to H.261 QCIF/CIF compared to what they use today ...
>
> You seem to be forgetting that WebRTC is a communication protocol for PEOPLE, not some one-sided push technology that gives them take it or leave it choices decided by self-interested vendors.
>
> So I would assume they'll react the same way they already do.
> Something along the lines of:
>
>    "D00d!!  Y U use that crap browser!??!111"
>
> And then they'll use the amazing text capabilities to paste a download link for firefox or something.
>
>    2 minutes later, problem solved.
>
> And they'll be watching each other's cats do fun things in full hi-res glory.
>
>
> It's not some accident of fate that the vendor browsers have the poor level of mindshare that they do, even given the solid advantage of incumbency they should otherwise enjoy.
>
> If the only way they think they can compete is via lock in and exclusivity using codec patents, then that alone speaks for the irrelevancy of those opinions about what is best for making this standard become ubiquitous.
>
>
> We need to guarantee interoperability between things that claim to implement the standard.  Quality of implementation is something that users will judge for themselves, and their mindshare will again gravitate accordingly between the available options.
>
> I'd still much prefer a better codec than H.261 as our baseline, but if the proprietary patent holders refuse to let us have that, then we need to work with the technology that is available to us.
>
> It doesn't take a doctorate in formal logic to connect those dots.
>
>
> This is our next best option for "making the patents evaporate", are people really now saying they didn't really want that to actually happen after all, despite what they said previously?
>
>    Ron
>
>
> _______________________________________________
> 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
>