Re: [codec] Conformance with unusual sample rates

Gregory Maxwell <gmaxwell@juniper.net> Fri, 18 November 2011 23:09 UTC

Return-Path: <gmaxwell@juniper.net>
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 6FEDF21F8509 for <codec@ietfa.amsl.com>; Fri, 18 Nov 2011 15:09:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.599
X-Spam-Level:
X-Spam-Status: No, score=-7.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_INVITATION=-2, RCVD_IN_DNSWL_MED=-4]
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 sTsfSlaf1tGE for <codec@ietfa.amsl.com>; Fri, 18 Nov 2011 15:09:35 -0800 (PST)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id 6C9E921F8500 for <codec@ietf.org>; Fri, 18 Nov 2011 15:09:35 -0800 (PST)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKTsblrRtRwxGPFBqWMZBbPPCGZxwt0z3L@postini.com; Fri, 18 Nov 2011 15:09:35 PST
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Fri, 18 Nov 2011 15:06:42 -0800
From: Gregory Maxwell <gmaxwell@juniper.net>
To: John Ridges <jridges@masque.com>
Date: Fri, 18 Nov 2011 15:06:41 -0800
Thread-Topic: [codec] Conformance with unusual sample rates
Thread-Index: AcymQ7bdyInuyNLTQyKESvYnS3g3cgAAA2Ra
Message-ID: <BCB3F026FAC4C145A4A3330806FEFDA93D19F6B50D@EMBX01-HQ.jnpr.net>
References: <CAECFA53.34065%stewe@stewe.org>,<4EC6DFE6.3080006@masque.com>
In-Reply-To: <4EC6DFE6.3080006@masque.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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:09:36 -0000

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…)