Re: [codec] consensus call: guidelines and requirements
Gregory Lebovitz <gregory.ietf@gmail.com> Sun, 28 February 2010 07:21 UTC
Return-Path: <gregory.ietf@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 33C783A8741 for <codec@core3.amsl.com>; Sat, 27 Feb 2010 23:21:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.855
X-Spam-Level:
X-Spam-Status: No, score=-101.855 tagged_above=-999 required=5 tests=[AWL=0.743, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 jjVQyqJ0yPiq for <codec@core3.amsl.com>; Sat, 27 Feb 2010 23:21:18 -0800 (PST)
Received: from mail-bw0-f211.google.com (mail-bw0-f211.google.com [209.85.218.211]) by core3.amsl.com (Postfix) with ESMTP id 143E93A8136 for <codec@ietf.org>; Sat, 27 Feb 2010 23:20:55 -0800 (PST)
Received: by bwz3 with SMTP id 3so1023256bwz.29 for <codec@ietf.org>; Sat, 27 Feb 2010 23:20:52 -0800 (PST)
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:content-type; bh=vz95TmQeexwKCKOTMDj33DlXIt/4g43XhlQtdiN4wMc=; b=cDXlZxWLJgB6p9JpSai9y7PFDQFBwfRNcETeyaHnQVv8pI4sA02ZaBii4n54vvchmM hNolGx4ZeUUevVYJ1s4IU7oNxrsgZCtQslHwrKVL4PRd9AqziGhGHzJ/z7189i6TbJgB G+08Kf6gMi6ktZCVLcUacraYT6xlAXO/vYYMc=
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 :content-type; b=M8DmJZDL0mAXpgHUEiSqr++bPFuQwHsSEXas8gMAq8EinsX9fLU33xNnBKyBkfgZ/r gAGX/dVxB3Z8+MKwH6SIMtw8bnVN3D9KzRVknEg5mvoH/O+7k75aJylADeqeGNLwncuQ kwlVE6sy4nrStK2btlX8B4wODxXxrCrDyklAA=
MIME-Version: 1.0
Received: by 10.204.26.198 with SMTP id f6mr1939049bkc.13.1267341652313; Sat, 27 Feb 2010 23:20:52 -0800 (PST)
In-Reply-To: <9b58f4551002241610n15d78941ufcea4558dc0272ff@mail.gmail.com>
References: <4B84574A.5070204@stpeter.im> <9b58f4551002241610n15d78941ufcea4558dc0272ff@mail.gmail.com>
Date: Sat, 27 Feb 2010 23:20:52 -0800
Message-ID: <f1548841002272320s3eae7bafj980d78e80cb852a0@mail.gmail.com>
From: Gregory Lebovitz <gregory.ietf@gmail.com>
To: Peter Saint-Andre <stpeter@stpeter.im>, Michael Knappe <mknappe@juniper.net>, Codec WG <codec@ietf.org>
Content-Type: multipart/alternative; boundary="000325554b2efec8130480a3f8fa"
Subject: Re: [codec] consensus call: guidelines and requirements
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: Sun, 28 Feb 2010 07:21:19 -0000
On Wed, Feb 24, 2010 at 4:10 PM, Jack Moffitt <jack@collecta.com> wrote: > > 1. Accepting draft-valin-codec-guidelines-02 [3] as the initial version > > of the Codec Standardization Guidelines. > > > > 2. Accepting draft-valin-codec-requirements-02 [4] as the initial > > version of the Technical Requirements. > > +1 to both of these from me. > ++1. This is not to say that I think either of these drafts are perfect and ready for WG last call. On the contrary, as many others have pointed out on this thread, there are still several contentious parts and tuning to be done, especially to make the documents align more fully with the charter. But, that said, these documents are (a) the clear and obvious efforts of focus of the WG, with no contending documents, and (b) well along the right path toward fulfilling the charter. For these reasons, I support adopting them as WG documents, and continuing our efforts and tune and align them. Hth, Gregory. > > jack. > _______________________________________________ > codec mailing list > codec@ietf.org > https://www.ietf.org/mailman/listinfo/codec > -- ---- IETF related email from Gregory M. Lebovitz Juniper Networks
- [codec] consensus call: guidelines and requiremen… Peter Saint-Andre
- Re: [codec] consensus call: guidelines and requir… Jack Moffitt
- Re: [codec] consensus call: guidelines and requir… Jean-Marc Valin
- Re: [codec] consensus call: guidelines and requir… Stephan Wenger
- Re: [codec] consensus call: guidelines and requir… Koen Vos
- Re: [codec] consensus call: guidelines and requir… Roni Even
- Re: [codec] consensus call: guidelines and requir… Kevin P. Fleming
- Re: [codec] consensus call: guidelines and requir… Brian West
- Re: [codec] consensus call: guidelines and requir… Gregory Maxwell
- Re: [codec] consensus call: guidelines and requir… Ron
- Re: [codec] consensus call: guidelines and requir… Finta Tartaruga
- Re: [codec] consensus call: guidelines and requir… Jonas Svedberg
- Re: [codec] consensus call: guidelines and requir… Gregory Lebovitz
- Re: [codec] consensus call: guidelines and requir… Monty Montgomery
- Re: [codec] consensus call: guidelines and requir… Peter Saint-Andre
- Re: [codec] consensus call: guidelines and requir… Erik Norvell
- Re: [codec] consensus call: guidelines and requir… Michael Knappe