Re: [codec] Conformance with unusual sample rates

John Ridges <jridges@masque.com> Fri, 18 November 2011 23:31 UTC

Return-Path: <jridges@masque.com>
X-Original-To: codec@ietfa.amsl.com
Delivered-To: codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B0F31F0C45 for <codec@ietfa.amsl.com>; Fri, 18 Nov 2011 15:31:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_INVITATION=-2]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A5raCkXBMGgN for <codec@ietfa.amsl.com>; Fri, 18 Nov 2011 15:31:43 -0800 (PST)
Received: from mail.masque.com (mail.masque.com [173.8.226.74]) by ietfa.amsl.com (Postfix) with ESMTP id CB4701F0C40 for <codec@ietf.org>; Fri, 18 Nov 2011 15:31:43 -0800 (PST)
Received: from [127.0.0.1] (unknown [192.168.1.241]) by mail.masque.com (Postfix) with ESMTP id D7EC71602A6; Fri, 18 Nov 2011 16:31:42 -0700 (MST)
Message-ID: <4EC6EADC.1070102@masque.com>
Date: Fri, 18 Nov 2011 16:31:40 -0700
From: John Ridges <jridges@masque.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Gregory Maxwell <gmaxwell@juniper.net>
References: <CAECFA53.34065%stewe@stewe.org>, <4EC6DFE6.3080006@masque.com> <BCB3F026FAC4C145A4A3330806FEFDA93D19F6B50D@EMBX01-HQ.jnpr.net>
In-Reply-To: <BCB3F026FAC4C145A4A3330806FEFDA93D19F6B50D@EMBX01-HQ.jnpr.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: "bens@alum.mit.edu" <bens@alum.mit.edu>, "codec@ietf.org" <codec@ietf.org>
Subject: Re: [codec] Conformance with unusual sample rates
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: Fri, 18 Nov 2011 23:31:44 -0000

Mr. Maxwell,

I apologize for spreading any FUD. Your statement is what I had expected 
(and hoped for). I was thrown a bit by Mr. Wenger's concerns. For my 
part, I consider this matter closed.

John Ridges


On 11/18/2011 4:06 PM, Gregory Maxwell wrote:
> John Ridges [jridges@masque.com]:
>> Well, I'm not a lawyer, but it doesn't seem right that a standard should
>> invite you to use the reference implementation in a way that would
>> violate its own IPR declarations. It makes me wonder if there are ways
>> of inadvertently misusing the codec's API that would do so as well.
> Obviously.
>
> This is the purpose of language like: [warning generic language from an IPR
> statement is contained in the paragraph below]
>
> "Specification means, [...]
> (b) any reference implementation (each, a “Reference Implementation”)
> published by the IETF Codec Working Group in the request for comments
> [...]  . Licensed patents [...] in the case of (b) above, use of the
> reference implementation to the extent it infringes such patent"
>
> My expectation is that the red light / green-light stuff is moot if  you are
> using an IETF published reference implementation as is. This is the
> reasonable and expected thing, and to the best of my knowledge it was
> the intention of the parties that contributed to the process.
>
> Other things are permitted as well, subject to the conformance
> requirements, but if you want to be extra paranoid, and want to take
> the easy way out, using the reference itself will cover you.
>
> If you've found some reason to believe otherwise, please contact me
> and I'll either point you to whatever you're missing or fuss at people
> to get it fixed.  (This is a generic invitation, open to any and all comers,
> if there is too much interest I'll write a FAQ outside of the working
> group or something…)
>
>
>