Re: [codec] comparitive quality testing
Stephan Wenger <stewe@stewe.org> Wed, 20 April 2011 00:45 UTC
Return-Path: <stewe@stewe.org>
X-Original-To: codec@ietfc.amsl.com
Delivered-To: codec@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id F1CFBE076E for <codec@ietfc.amsl.com>; Tue, 19 Apr 2011 17:45:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.329
X-Spam-Level:
X-Spam-Status: No, score=-1.329 tagged_above=-999 required=5 tests=[AWL=-0.127, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7rvywJQo+H-9 for <codec@ietfc.amsl.com>; Tue, 19 Apr 2011 17:45:53 -0700 (PDT)
Received: from stewe.org (stewe.org [85.214.122.234]) by ietfc.amsl.com (Postfix) with ESMTP id 99B7AE069C for <codec@ietf.org>; Tue, 19 Apr 2011 17:45:52 -0700 (PDT)
Received: from [192.168.1.108] (unverified [24.5.184.151]) by stewe.org (SurgeMail 3.9e) with ESMTP id 11108-1743317 for multiple; Wed, 20 Apr 2011 02:45:51 +0200
User-Agent: Microsoft-MacOutlook/14.2.0.101115
Date: Tue, 19 Apr 2011 17:45:40 -0700
From: Stephan Wenger <stewe@stewe.org>
To: Roman Shpount <roman@telurix.com>, Alan Duric <Alan.Duric@telio.no>
Message-ID: <C9D37557.2AC4A%stewe@stewe.org>
Thread-Topic: [codec] comparitive quality testing
In-Reply-To: <BANLkTik1DhJjUPYFtNL08gbSjqUB0KkLbQ@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3386079950_4968155"
X-Originating-IP: 24.5.184.151
X-Authenticated-User: stewe@stewe.org
X-ORBS-Stamp: Your IP (24.5.184.151) was found in the spamhaus database. http://www.spamhaus.net
Cc: "codec@ietf.org" <codec@ietf.org>
Subject: Re: [codec] comparitive quality testing
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codec>, <mailto:codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/codec>
List-Post: <mailto:codec@ietf.org>
List-Help: <mailto:codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codec>, <mailto:codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Apr 2011 00:45:56 -0000
Interesting information. Two comments inline (after having removed a lot of valuable info). Stephan From: Roman Shpount <roman@telurix.com> Date: Tue, 19 Apr 2011 19:08:33 -0400 To: Alan Duric <Alan.Duric@telio.no> Cc: "codec@ietf.org" <codec@ietf.org> Subject: Re: [codec] comparitive quality testing [] There is also a question of ILBC Freeware license. Based on IETF rules, all the code released as a part of IETF RFC should be covered by BSD license. The reasoning and applicability of iLBC Freeware license in this context is unclear. iLBC, and the drafts leading to the RFC, pre-date the requirement for code in RFCs to use the BSD style license. Therefore, the authors had the right to license their code even in the RFC text under any license compliant with the then in force IPR documents, which were 2026 (overall procedures), 3667 (for copyright), and 3688 (for patent rights). I believe the RFC is in compliance with these documents. Further, no one requires an author to provide the IETF trust with an exclusive license for code portions of an RFC. Therefore, anyone is free to make available code contributed to an I-D or RFC (and, thereby and for the purpose of this discussion, BSD-style licensed) also under licenses other than the BSD style license. They just have to use a different medium than the RFC text. IPR disclosure for iLBC RFC was not updated when RFC was finalized and only has provisional patent applications, not the final granted patent numbers. I'm not aware of the nature of the patent rights, or their numbers, that were disclosed by GlobalIPSound. I can't find such information in the disclosure. That said, those with a bit of patent experience, access to the right tools, and and a few hours of time, can find the relevant patents covered by the disclosure with limited effort and reasonable certainty. Even today the IETF does not require "updates" of IPR disclosures beyond what is mandated in the rather generic language of the policy documents. Some rightholders go at great length in keeping their disclosures updated, others don't. The really interesting question in this context is whether google finds itself bound to the promises made by GIPS at the time. The policy documents provide no guidance on this topic, and this area of law is currently litigated in several venues, with (so far) rather inconclusive results. [] Stephan
- [codec] comparitive quality testing Gregory Maxwell
- Re: [codec] comparitive quality testing Roman Shpount
- Re: [codec] comparitive quality testing Cullen Jennings
- Re: [codec] comparitive quality testing Roman Shpount
- Re: [codec] comparitive quality testing David Virette
- Re: [codec] comparitive quality testing Roman Shpount
- Re: [codec] comparitive quality testing Steve Underwood
- Re: [codec] comparitive quality testing Roman Shpount
- Re: [codec] comparitive quality testing Cullen Jennings
- Re: [codec] comparitive quality testing Alan Duric
- Re: [codec] comparitive quality testing Anisse Taleb
- Re: [codec] comparitive quality testing Monty Montgomery
- Re: [codec] comparitive quality testing Roman Shpount
- Re: [codec] comparitive quality testing Stephan Wenger
- Re: [codec] comparitive quality testing Steve Underwood
- Re: [codec] comparitive quality testing Roman Shpount
- Re: [codec] comparitive quality testing Roman Shpount
- Re: [codec] comparitive quality testing Cullen Jennings
- Re: [codec] comparitive quality testing Alan Duric
- Re: [codec] comparitive quality testing Roman Shpount
- Re: [codec] comparitive quality testing Roman Shpount
- [codec] iLBC deployment statistics (Re: compariti… Harald Alvestrand
- [codec] Deployment of iLBC Re: comparitive qualit… Cullen Jennings
- Re: [codec] comparitive quality testing: vote to … Jean-Francois Mule
- Re: [codec] comparitive quality testing: vote to … Roman Shpount