Re: [codec] possible issues to track
stephen botzko <stephen.botzko@gmail.com> Thu, 25 March 2010 22:04 UTC
Return-Path: <stephen.botzko@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 176F43A6B5C for <codec@core3.amsl.com>; Thu, 25 Mar 2010 15:04:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.261
X-Spam-Level:
X-Spam-Status: No, score=-0.261 tagged_above=-999 required=5 tests=[AWL=1.207, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001]
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 oPhFtCol1uBM for <codec@core3.amsl.com>; Thu, 25 Mar 2010 15:04:03 -0700 (PDT)
Received: from mail-pz0-f204.google.com (mail-pz0-f204.google.com [209.85.222.204]) by core3.amsl.com (Postfix) with ESMTP id 03B2E3A6CD7 for <codec@ietf.org>; Thu, 25 Mar 2010 15:04:01 -0700 (PDT)
Received: by pzk42 with SMTP id 42so951894pzk.32 for <codec@ietf.org>; Thu, 25 Mar 2010 15:04:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=U/6x7mKDdcrcWMX2L5HIzhoxSJDXV9FFdI1B5weA1G8=; b=P/Pt4yYvRvVrDSe3IzfZzQv0vXAgs1lY1gluV9sp9SZGEOmUjRUY9A1B++SB5uwcdg 7v5rxVyokGsX5d10RPZiYHdnLP3fnYp9Y2zWt4QcPgiEav+VVIiUYeEglhW2NvYIVrem FWAGKP/WZWYY7g5gQJLkfBdnhT/7J0UwbUHSI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Ghs+Di2X9Dwc7Xa6tHo5zPJYQFaPaVqHfDT0Gn0GzI66+gssPzpV/jmKvQe9aZKFyG +5HZmF08gGgsCvR/T3UDUReNApIrjqFIGlgvAnaNppVvSFHQCm/Y+Qt9UgBZy5IKDfuu 0/LQiuFKr+OT3+4mpW8LCDT80d7zaUA1WYwjM=
MIME-Version: 1.0
Received: by 10.141.187.14 with SMTP id o14mr2867037rvp.244.1269554661610; Thu, 25 Mar 2010 15:04:21 -0700 (PDT)
In-Reply-To: <C7D12868.207B0%stewe@stewe.org>
References: <4BABD9C2.6070108@octasic.com> <C7D12868.207B0%stewe@stewe.org>
Date: Thu, 25 Mar 2010 15:04:21 -0700
Message-ID: <6e9223711003251504l195e0218qc0e27b598ea99b8a@mail.gmail.com>
From: stephen botzko <stephen.botzko@gmail.com>
To: Stephan Wenger <stewe@stewe.org>
Content-Type: multipart/alternative; boundary="000e0cd1ad1ca0d7ce0482a73af8"
Cc: Codec WG <codec@ietf.org>
Subject: Re: [codec] possible issues to track
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: Thu, 25 Mar 2010 22:04:04 -0000
Perhaps something as simple as saying "not worse" instead of "better". Stephen Bozko On Thu, Mar 25, 2010 at 2:49 PM, Stephan Wenger <stewe@stewe.org> wrote: > No, I just suggest to attempt being just a little bit diplomatic. > Stephan > > > > On 3.25.2010 14:46 , "Jean-Marc Valin" <jean-marc.valin@octasic.com> > wrote: > > > Stephan Wenger wrote: > >> The comment was from me, and it was addressed towards the sensitivities > of > >> cross-SDO relationships. It is one thing if the ITU states that > something > >> is better than ITU-Rec xxx, but it is another thing if another body > states > >> this. Certainly without having received appropriate input from the ITU > >> after requesting it through a liaison. > > > > So do you suggest we drop the ITU codecs from the list? I don't really > > mind, considering that I would not expect that part of the requirement to > > be a limiting factor. > > > > Jean-Marc > > > >> Stephan > >> > >> > >> > >> On 3.25.2010 14:32 , "Jean-Marc Valin" <jean-marc.valin@octasic.com> > wrote: > >> > >>> Peter Saint-Andre wrote: > >>>> - avoid phrasing subjective comparision in relation to ITU codecs > >>> I was actually surprised to see that one come up. As far as I know, > most > >>> ITU terms of reference include comparisons like "better than G.722 at > rate > >>> X". Does the ITU phrase this differently then we did? > >>> > >>> As for the way of discussing the issues, it seems to me like the > mailing > >>> list is just simpler. Most people so far have commented on the list > anyway. > >>> > >>> Cheers, > >>> > >>> Jean-Marc > >>> _______________________________________________ > >>> codec mailing list > >>> codec@ietf.org > >>> https://www.ietf.org/mailman/listinfo/codec > >> > >> > > > > > _______________________________________________ > codec mailing list > codec@ietf.org > https://www.ietf.org/mailman/listinfo/codec >
- Re: [codec] possible issues to track Michael Knappe
- [codec] possible issues to track Peter Saint-Andre
- Re: [codec] possible issues to track Jean-Marc Valin
- Re: [codec] possible issues to track Stephan Wenger
- Re: [codec] possible issues to track Jean-Marc Valin
- Re: [codec] possible issues to track Stephan Wenger
- Re: [codec] possible issues to track Michael Knappe
- Re: [codec] possible issues to track Benjamin M. Schwartz
- Re: [codec] possible issues to track Michael Knappe
- Re: [codec] possible issues to track stephen botzko
- Re: [codec] possible issues to track Jean-Marc Valin
- Re: [codec] possible issues to track Peter Saint-Andre
- Re: [codec] possible issues to track Jean-Marc Valin
- Re: [codec] possible issues to track Michael Knappe
- Re: [codec] possible issues to track stephen botzko
- Re: [codec] possible issues to track Benjamin M. Schwartz
- Re: [codec] possible issues to track Christian Hoene
- Re: [codec] possible issues to track Michael Knappe
- Re: [codec] possible issues to track stephen botzko
- Re: [codec] possible issues to track Jean-Marc Valin
- Re: [codec] possible issues to track Benjamin M. Schwartz
- Re: [codec] possible issues to track Benjamin M. Schwartz