Re: [codec] WG Review: Internet Wideband Audio Codec (codec)

Stephan Wenger <stewe@stewe.org> Thu, 07 January 2010 19:46 UTC

Return-Path: <stewe@stewe.org>
X-Original-To: codec@core3.amsl.com
Delivered-To: codec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E0C928C0EB; Thu, 7 Jan 2010 11:46:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9dy-IuSQThxZ; Thu, 7 Jan 2010 11:46:31 -0800 (PST)
Received: from stewe.org (stewe.org [85.214.122.234]) by core3.amsl.com (Postfix) with ESMTP id 223B53A68FF; Thu, 7 Jan 2010 11:46:28 -0800 (PST)
Received: from [192.168.1.111] (unverified [71.202.146.15]) by stewe.org (SurgeMail 3.9e) with ESMTP id 545279-1743317 for multiple; Thu, 07 Jan 2010 20:46:26 +0100
User-Agent: Microsoft-Entourage/12.23.0.091001
Date: Thu, 07 Jan 2010 11:46:04 -0800
From: Stephan Wenger <stewe@stewe.org>
To: Peter Saint-Andre <stpeter@stpeter.im>, Russ Housley <housley@vigilsec.com>
Message-ID: <C76B79FC.1E959%stewe@stewe.org>
Thread-Topic: [codec] WG Review: Internet Wideband Audio Codec (codec)
Thread-Index: AcqP0gv1iBRD6vF+6UKNUup/hXikbg==
In-Reply-To: <4B463120.1030504@stpeter.im>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Originating-IP: 71.202.146.15
X-Authenticated-User: stewe@stewe.org
X-ORBS-Stamp: Your IP (71.202.146.15) was found in the spamhaus database. http://www.spamhaus.net
Cc: codec@ietf.org, ietf@ietf.org, iesg@ietf.org
Subject: Re: [codec] WG Review: Internet Wideband Audio Codec (codec)
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Should the IETF standardize wideband Internet codec\(s\)? " <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 07 Jan 2010 19:46:32 -0000

Hi,

Russ' language is an improvement.  But let's not forget that there are
encumbrances that have nothing to do with paying royalties, but are equally
problematic from an adoption viewpoint.  Examples:

1. Co-marketing requirement: need to put a logo of the rightholder company
on one's products acknowledging using the protected technology.
2. Unreasonable (from the viewpoint of the adopter) reciprocity
requirements: one of many examples would be "if you use this technology, you
agree not to assert, against me or my customers, any of your patents.
Otherwise your license terminates.".
3. Requirement for a "postcard license".  Such a requirement may rule out
open source implementations under certain open source licenses.

I believe strongly that a charter that discusses IPR issues should mention
at least those three aspects, and/or provide sufficiently vague language to
allow for an appropriate reaction to those and other encumbrances that may
show up.  

Royalties are the least of our problems.

Regards,
Stephan

Disclaimer: I have clients that would have problems with all three
encumbrances mentioned above.





On 1/7/10 11:08 AM, "Peter Saint-Andre" <stpeter@stpeter.im> wrote:

> On 1/7/10 9:46 AM, Russ Housley wrote:
>> Andy:
>> 
>>>> Although this preference cannot guarantee that the working
>>>> group will produce an unencumbered codec, the working group shall
>>>> attempt to adhere to the spirit of BCP 79.  This preference does not
>>>> explicitly rule out the possibility of adapting encumbered technologies;
>>>> such decisions will be made in accordance with the rough consensus of
>>>> the working group.
>>> 
>>> I appreciate the potential difficulty of guaranteeing the unencumbered
>>> status of any output of this group. However, I would like this
>>> statement to
>>> be stronger, saying that this group will only produce a new codec if
>>> it is
>>> strongly believed by WG rough consensus to either be unencumbered,
>>> or freely licensed by the IPR holder(s), if any.
>> 
>> I do not think that anyone wants the outcome to be yet another
>> encumbered codec.  I think these words are trying to say what you want,
>> but they are also trying to be realistic.
>> 
>> Does the following text strike a better balance?
>> 
>>   Although this preference cannot guarantee that the working
>>   group will produce an unencumbered codec, the working group shall
>>   follow BCP 79, and adhere to the spirit of BCP 79.  The working
>>   group cannot explicitly rule out the possibility of adapting
>>   encumbered technologies; however, the working group will try to
>>   avoid encumbered technologies that require royalties.
> 
> That seems reasonable. Although I was only the BoF co-chair, I'll
> volunteer to hold the pen on edits to the proposed charter.
> 
> Peter