Re: [rtcweb] Proposed Video Selection Process

Maik Merten <maikmerten@googlemail.com> Fri, 22 November 2013 21:19 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 97ED31AE265 for <rtcweb@ietfa.amsl.com>; Fri, 22 Nov 2013 13:19:49 -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 o9FEqrpnGrEx for <rtcweb@ietfa.amsl.com>; Fri, 22 Nov 2013 13:19:48 -0800 (PST)
Received: from mail-ee0-x233.google.com (mail-ee0-x233.google.com [IPv6:2a00:1450:4013:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id EECA11AE23A for <rtcweb@ietf.org>; Fri, 22 Nov 2013 13:19:47 -0800 (PST)
Received: by mail-ee0-f51.google.com with SMTP id b15so769349eek.10 for <rtcweb@ietf.org>; Fri, 22 Nov 2013 13:19:40 -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=oSqc4GyqJaiGzGRiAj6VSM0K9ey6NAvayl5o7uwcV0Y=; b=WDT8UkfV0oqxg/jlVVRunL5WoPrYn++uBaaF5nCPa4Ro9J8kWl2A0SwVAH0qWyMYUM 183kJL1YGOPH4X/I/xNWcVY3S0WssFDHJOC/ReXbQH1teXapOptjAc0QoNjy9vbLcbnG MJK7htD1C4Awrd+6N+ntzfhzrIshyQJ3oynR4p+hX3AVs+rh0Z9uQIfDer+KMLzroVPu IRuvEtEyO1eTKgVlDfGOckLGgfuGekzElonCMYzbanosIHpiymUwQ9pHosuCKaMGdTm9 aVgPV1jJrNA97VtSX/ScakWFFEeUZnNHoyBe01z6dbUE5fldWySCHVyZao/ZoQcdad3k RLJA==
X-Received: by 10.14.212.72 with SMTP id x48mr19336629eeo.0.1385155180413; Fri, 22 Nov 2013 13:19:40 -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 1sm80274403eeg.4.2013.11.22.13.19.38 for <rtcweb@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 22 Nov 2013 13:19:39 -0800 (PST)
Message-ID: <528FCA68.2070309@googlemail.com>
Date: Fri, 22 Nov 2013 22:19:36 +0100
From: Maik Merten <maikmerten@googlemail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <7949EED078736C4881C92F656DC6F6C130EA8AD7ED@ausmsex00.austin.kmvtechnologies.com> <E62E1CAF-546D-4A0E-9339-D03D6C0BC1AE@apple.com> <528EBAB0.2010906@librevideo.org> <D125BF97-73BE-4591-8C70-30C03974CC78@apple.com> <528EBD4C.8070504@librevideo.org> <CAOJ7v-2zCZk4cMh1MbpXGHCELJMJppLVEX9CwPG3VNtDfDv4qw@mail.gmail.com> <02B96CE8-A6D9-4288-B052-FB54B07447FB@apple.com>
In-Reply-To: <02B96CE8-A6D9-4288-B052-FB54B07447FB@apple.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] Proposed Video Selection Process
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 21:19:49 -0000

Am 22.11.2013 21:01, schrieb David Singer:
> I am not knocking his opinion, you understand, just questioning whether we should discard H.263 based on just this one opinion.

The overall notion of H.261 being implementable without restrictions is 
easy to grasp: The technology is over 25 years old, which puts it into 
the "comfy zone" of patent expiration. It is hard to come up with a 
scenario where patents covering the original standard and original 
reference implementation would still be enforceable.

H.263 would be vastly preferable in terms of technology level and 
deployment, but it isn't yet old enough to *automatically* be in the 
same "comfy zone". It is quite old, but not *that* old.

This doesn't mean there actually *are* unavoidable H.263 patents. 
However, the IPR and licensing situation surrounding H.263 would need to 
be analyzed thoroughly by professionals and the findings would need to 
be shared.

Does anybody here have the resources to conduct such an analysis? If a 
credible analysis reveals that H.263 (or MPEG-1 Part 2, that one is also 
clearly superior to H.261) is actually carrying low risk this would be 
quite something.


Maik