Re: [codec] comparitive quality testing

Stephan Wenger <> Wed, 20 April 2011 00:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F1CFBE076E for <>; Tue, 19 Apr 2011 17:45:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.329
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 7rvywJQo+H-9 for <>; Tue, 19 Apr 2011 17:45:53 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 99B7AE069C for <>; Tue, 19 Apr 2011 17:45:52 -0700 (PDT)
Received: from [] (unverified []) by (SurgeMail 3.9e) with ESMTP id 11108-1743317 for multiple; Wed, 20 Apr 2011 02:45:51 +0200
User-Agent: Microsoft-MacOutlook/
Date: Tue, 19 Apr 2011 17:45:40 -0700
From: Stephan Wenger <>
To: Roman Shpount <>, Alan Duric <>
Message-ID: <>
Thread-Topic: [codec] comparitive quality testing
In-Reply-To: <>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3386079950_4968155"
X-ORBS-Stamp: Your IP ( was found in the spamhaus database.
Cc: "" <>
Subject: Re: [codec] comparitive quality testing
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Codec WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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).

From:  Roman Shpount <>
Date:  Tue, 19 Apr 2011 19:08:33 -0400
To:  Alan Duric <>
Cc:  "" <>
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

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.