Re: [codec] A concrete proposal for requirements and testing
Kat Walsh <kat@mindspillage.org> Sat, 09 April 2011 17:54 UTC
Return-Path: <mindspillage@gmail.com>
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 38B8C3A68EC for <codec@core3.amsl.com>; Sat, 9 Apr 2011 10:54:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 dPCgEO4Nrw9X for <codec@core3.amsl.com>; Sat, 9 Apr 2011 10:54:52 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 23EC03A6889 for <codec@ietf.org>; Sat, 9 Apr 2011 10:54:51 -0700 (PDT)
Received: by ewy19 with SMTP id 19so1616518ewy.31 for <codec@ietf.org>; Sat, 09 Apr 2011 10:56:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=90J7x8ycSlNwMkwKuvPQd//P0qZRsFhNe7Fr6w75VMg=; b=vl/GcmtXxYx0yHJ3POSHqYDTUEkV5SAvPjNDT2jkKdTLlwXU5NdACfUgxCvAw9dPXG 4HlWJmMoVr/bHMJ2Bz736j01As9ZJz46kS+34+/+ay3H2TkDr50Nlfh2aq62YQKe4ZiU NmXj4pxT97Gxh4e46Lm8MbAfFWz4gPx/qDDs4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=aJ8MPm+u78u+N3ULeE6SNRQtGhFXPyKe5Pn+PehgNmydlPyDDgx04PdQXopnLXiexp 5aIeno4ilJBN3cxhJ97xRH/RKRpDcrvlKS5KUxAVFYe9OTnF6nTkA7xlKOCpP2K4Q+zB h0FK1pPjRmfGyMieh4rpNvoUdObdHF+UYxl9k=
MIME-Version: 1.0
Received: by 10.14.18.100 with SMTP id k76mr1515841eek.125.1302371797684; Sat, 09 Apr 2011 10:56:37 -0700 (PDT)
Sender: mindspillage@gmail.com
Received: by 10.14.119.130 with HTTP; Sat, 9 Apr 2011 10:56:36 -0700 (PDT)
In-Reply-To: <C9C5C8B9.2A54E%stewe@stewe.org>
References: <20110409152146.GK30415@audi.shelbyville.oz> <C9C5C8B9.2A54E%stewe@stewe.org>
Date: Sat, 09 Apr 2011 13:56:36 -0400
X-Google-Sender-Auth: Ejh4iNC7_4nepajorpYPZFIXatw
Message-ID: <BANLkTi=K82JrPCtOcodGePcTx0phs7p1eQ@mail.gmail.com>
From: Kat Walsh <kat@mindspillage.org>
To: Stephan Wenger <stewe@stewe.org>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: codec@ietf.org
Subject: Re: [codec] A concrete proposal for requirements and testing
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Codec WG <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 Apr 2011 17:55:21 -0000
On Sat, Apr 9, 2011 at 11:35 AM, Stephan Wenger <stewe@stewe.org> wrote: > With hat: The same hat we're all wearing, the one that indicates "simply speaking your own opinion"? > In the IETF, as a group, we look at information made available by the > rightholders (to the IETF, or, when there are other SDOs involved, at > their disclosure system and/or their patent policy). Those of us who feel > qualified can also look at objectively verifiable (by anyone!) data such > as patent expiration dates. > > We do not look at known, rumored, or unknown licensing deals. We do not > solicit such information. In fact, per BCP 79, it seems the opposite is true. We do look at licensing: "Although the IETF can make no actual determination of validity, enforceability or applicability of any particular IPR claim, it is reasonable that a working group will take into account on their own opinions of the validity, enforceability or applicability of Intellectual Property Rights in their evaluation of alternative technologies." And we do solicit such information: "Since IPR disclosures will be used by IETF working groups during their evaluation of alternative technical solutions, it is helpful if an IPR disclosure includes information about licensing of the IPR in case Implementing Technologies require a license." Not only is this information explicitly asked for, but I've never seen limitations on what we're all allowed to look at and consider, even if we have to dance around public discussion of some things that some participants or their employers misguidedly believe there is more safety in ignoring. I can't see any justification for discouraging individuals from looking at as much information as is necessary to make their own informed decisions, even if the information is of no official interest to the process. If people are broadly unwilling to deploy the technology, regardless of their reasons, then the goals of the charter are not met. > Let's stay out of antitrust trouble. What kind of antitrust trouble are you thinking of? (You can't possibly be suggesting that choosing to use or not use a technology based on its patent licensing status has antitrust implications.) Cheers, Kat Walsh
- [codec] A concrete proposal for requirements and … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Roman Shpount
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Roman Shpount
- Re: [codec] A concrete proposal for requirements … Benjamin M. Schwartz
- Re: [codec] A concrete proposal for requirements … Roni Even
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Jan Skoglund
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- Re: [codec] A concrete proposal for requirements … Erik Norvell
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Benjamin M. Schwartz
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Peter Saint-Andre
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Benjamin M. Schwartz
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Peter Saint-Andre
- Re: [codec] A concrete proposal for requirements … Timothy B. Terriberry
- Re: [codec] A concrete proposal for requirements … Stephan Wenger
- Re: [codec] A concrete proposal for requirements … Monty Montgomery
- Re: [codec] A concrete proposal for requirements … Timothy B. Terriberry
- Re: [codec] A concrete proposal for requirements … Stephan Wenger
- Re: [codec] A concrete proposal for requirements … Gregory Maxwell
- Re: [codec] A concrete proposal for requirements … Monty Montgomery
- Re: [codec] A concrete proposal for requirements … Koen Vos
- Re: [codec] A concrete proposal for requirements … Roman Shpount
- Re: [codec] A concrete proposal for requirements … Koen Vos
- Re: [codec] A concrete proposal for requirements … Stephan Wenger
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Gregory Maxwell
- Re: [codec] A concrete proposal for requirements … Roman Shpount
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Koen Vos
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Roni Even
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Kavan Seggie
- Re: [codec] A concrete proposal for requirements … Roni Even
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Roni Even
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Roni Even
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Stephan Wenger
- Re: [codec] A concrete proposal for requirements … Kat Walsh
- Re: [codec] A concrete proposal for requirements … Stefan Hacker
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Paul Coverdale
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Serge Smirnoff
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Jean-Marc Valin
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Ron
- Re: [codec] A concrete proposal for requirements … Stephen Botzko
- Re: [codec] A concrete proposal for requirements … Anisse Taleb
- [codec] Chairs and consensus Cullen Jennings