Re: [codec] A concrete proposal for requirements and testing
Ron <ron@debian.org> Sat, 09 April 2011 23:07 UTC
Return-Path: <ron@debian.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 3A46A3A6982 for <codec@core3.amsl.com>; Sat, 9 Apr 2011 16:07:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.488
X-Spam-Level:
X-Spam-Status: No, score=-2.488 tagged_above=-999 required=5 tests=[AWL=0.111, 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 Y7oMMnZ49FXy for <codec@core3.amsl.com>; Sat, 9 Apr 2011 16:07:16 -0700 (PDT)
Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [150.101.137.131]) by core3.amsl.com (Postfix) with ESMTP id 181923A6977 for <codec@ietf.org>; Sat, 9 Apr 2011 16:07:15 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAA3loE120qsf/2dsb2JhbACmIHiIerV4hW4EhVmHfw
Received: from ppp118-210-171-31.lns20.adl6.internode.on.net (HELO audi.shelbyville.oz) ([118.210.171.31]) by ipmail07.adl2.internode.on.net with ESMTP; 10 Apr 2011 08:39:01 +0930
Received: from localhost (localhost [127.0.0.1]) by audi.shelbyville.oz (Postfix) with ESMTP id BBF124F8F3 for <codec@ietf.org>; Sun, 10 Apr 2011 08:38:59 +0930 (CST)
X-Virus-Scanned: Debian amavisd-new at audi.shelbyville.oz
Received: from audi.shelbyville.oz ([127.0.0.1]) by localhost (audi.shelbyville.oz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id O0t6WS330LRC for <codec@ietf.org>; Sun, 10 Apr 2011 08:38:57 +0930 (CST)
Received: by audi.shelbyville.oz (Postfix, from userid 1000) id E93114F8FE; Sun, 10 Apr 2011 08:38:57 +0930 (CST)
Date: Sun, 10 Apr 2011 08:38:57 +0930
From: Ron <ron@debian.org>
To: codec@ietf.org
Message-ID: <20110409230857.GL30415@audi.shelbyville.oz>
References: <BANLkTi=K82JrPCtOcodGePcTx0phs7p1eQ@mail.gmail.com> <C9C608E7.2A56A%stewe@stewe.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <C9C608E7.2A56A%stewe@stewe.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
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 23:07:17 -0000
On Sat, Apr 09, 2011 at 01:36:37PM -0700, Stephan Wenger wrote: > On 4.9.2011 10:56 , "Kat Walsh" <kat@mindspillage.org> wrote: > > >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"? > > The official job title was something like "Advisor to IESG re IPR matters > related to Codec WG". Which part of your advise here was directed to the IESG? > Note, though, that I was talking about "licensing deals", and that the > context of this discussion has been that someone was arguing about > knowledge (or lack thereof) of royalty-bearing licensing deals. This has > nothing to do with disclosures received. (I don't have the exact > quotation readily available, and I'm too lazy to look it up.) That would have been Roni, repeating your query about whether Opus was royalty-free, I guess. After we'd already agreed, by your request and hatted advice, that we not talk about that on this list. But FTR, the answer is quite clearly still, yes it is. You don't seriously think that Xiph would have kept it a secret if some party had triggered the termination clause in their own IPR grant, do you? In the absence of news about that (not to mention other assurances given directly to you on this list and at the Prague meeting), I think we can safely conclude that there has been no such claim to date and Opus remains as RF as any thing that royalties have never been collected on can be. We don't have to pry into people's backroom deals at all to see that. So let's drop the FUD about Scary Claims, and the bizarre claims about transitive, questionable IPR states obligating us to test against codecs that are clearly unsuitable for meeting the WG charter, and just get on with the tedious task of trying to find out if any of the people currently wasting our time with spurious circular arguments, actually have a point that this group really needs to consider. Because so far, we have a flood of vague handwavy claims about supposed 'alternative codecs', which aren't backed up by even the most rudimentary standards of proof, and cries that the WG documents aren't satisfactory - which aren't backed up by even pointing at the parts that are considered unsatisfactory, let alone an explanation of what is actually supposed to be unsatisfactory about them. Which try as I might, I don't seem to be able to glean even a single, simple, contribution to the advancement of this group's charter from. No matter how many times they are repeated by the same people to the point of going "oh, uh, nevermind". Again. The last call is rolling. If you have something of substance to add to the work we have, please detail it precisely. If you can't, the only logical conclusion is that we have consensus from the non-obstructing people on the current documents in their present form and nobody knows how to improve them further yet. I sincerely hope this isn't actually representative of the way that some of these people work within the other SDO's they are a part of, because that would be acutely embarrassing for both them, and their organisations. When the supposed amateurs appear more professional than you do, making sure you have the right hat on is the least of your problems. It's too late to pretend that Opus hasn't wiped the floor with pretty much every other codec, and that the achievement of its developers isn't distinctly remarkable. It may not be too late to suck up your initial disdain and disbelief in this group and salvage some self respect for both yourselves and the organisations you inevitably represent to the world. Remember all this is becoming a part of your permanent record, and part of the internet history even. So who wants to look like an engineer in that story, and who wants to look like a cheap, inept saboteur? It's your last call to make that decision too. :> Choose wisely, Ron
- [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