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

"Spencer Dawkins" <spencer@wonderhamster.org> Sat, 09 January 2010 00:33 UTC

Return-Path: <spencer@wonderhamster.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 EF2083A6812; Fri, 8 Jan 2010 16:33:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.135
X-Spam-Level:
X-Spam-Status: No, score=-2.135 tagged_above=-999 required=5 tests=[AWL=0.464, 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 DYu-gHROCGRX; Fri, 8 Jan 2010 16:33:45 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id D5C1E3A67FA; Fri, 8 Jan 2010 16:33:44 -0800 (PST)
Received: from S73602b (cpe-76-182-230-135.tx.res.rr.com [76.182.230.135]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0LzuTT-1NxDtq143n-014gLq; Fri, 08 Jan 2010 19:33:11 -0500
Message-ID: <F13E12C08A7540E38779D89BA993ADCB@china.huawei.com>
From: Spencer Dawkins <spencer@wonderhamster.org>
To: Adrian Farrel <Adrian.Farrel@huawei.com>, Russ Housley <housley@vigilsec.com>
References: <C76B79FC.1E959%stewe@stewe.org> <4B46404C.4030903@octasic.com><4B47BC66.3090006@vigilsec.com> <5F16477173FD48939F1DAD69CBD6A61B@your029b8cecfe>
Date: Fri, 08 Jan 2010 18:32:50 -0600
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="response"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX1+pOx84KF+6p8IYL9kz0eS7//EcAwrPZ3tDF10 j9BJvn5bYMlHCcpC8AOJblaBK1stv+IhF4aoQQXZLiupdi/BWD VVSpTeivZ66wcmttYc/UZ5/J3X/KYEkx4BB27067io=
X-Mailman-Approved-At: Fri, 08 Jan 2010 16:39:49 -0800
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: Sat, 09 Jan 2010 00:33:46 -0000

I would have guessed "adopting" (nice catch. I missed it completely). but 
other than this, I wanted to say that Russ's new formula seemed more in 
synch with what I've been seeing on this list - much stronger than "will 
try" (would be nice).

Thanks,

Spencer

----- Original Message ----- 
From: "Adrian Farrel" <Adrian.Farrel@huawei.com>
To: "Russ Housley" <housley@vigilsec.com>
Cc: <codec@ietf.org>; <ietf@ietf.org>; <iesg@ietf.org>
Sent: Friday, January 08, 2010 6:20 PM
Subject: Re: [codec] WG Review: Internet Wideband Audio Codec (codec)


> "adapting" or "adopting"?
> ----- Original Message ----- 
> From: "Russ Housley" <housley@vigilsec.com>
> Cc: <codec@ietf.org>; <ietf@ietf.org>; <iesg@ietf.org>
> Sent: Friday, January 08, 2010 11:14 PM
> Subject: Re: [codec] WG Review: Internet Wideband Audio Codec (codec)
>
>
>> Good improvement.  I'd go a slide bit further:
>>
>>    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 would hinder free
>>    redistribution in any way.
>>
>> Russ
>>
>> On 1/7/2010 3:13 PM, Jean-Marc Valin wrote:
>>> Hi,
>>>
>>> I'm not sure royalties are the *least* of out problems, but I certainly
>>> agree with Stephan that annoyances go further than just royalties. I
>>> understand that BCP79 restricts what we can say about that in the 
>>> charter,
>>> but at least mentioning the problem as Stephan suggests is a good idea 
>>> IMO.
>>> In some sense, this is again part of the "making it easy to 
>>> redistribute".
>>>
>>> Jean-Marc
>>>
>>> Stephan Wenger wrote:
>>>> 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
>>>>
>>>>
>>>> _______________________________________________
>>>> codec mailing list
>>>> codec@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/codec
>>>
>>>
>>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf