Re: [codec] 3 week WGLC on draft-ietf-codec-requirements-02
Cullen Jennings <fluffy@cisco.com> Tue, 25 January 2011 21:01 UTC
Return-Path: <fluffy@cisco.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 6FB613A689F for <codec@core3.amsl.com>; Tue, 25 Jan 2011 13:01:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.581
X-Spam-Level:
X-Spam-Status: No, score=-110.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 nyPsTanZd29N for <codec@core3.amsl.com>; Tue, 25 Jan 2011 13:01:57 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id A81A53A689E for <codec@ietf.org>; Tue, 25 Jan 2011 13:01:57 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAFPJPk2rR7H+/2dsb2JhbACkcXOhWZs7hU8EhReHEYNG
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-4.cisco.com with ESMTP; 25 Jan 2011 21:04:56 +0000
Received: from [192.168.4.2] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p0PL4thK006379; Tue, 25 Jan 2011 21:04:55 GMT
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <000001cbbad6$4f44aea0$edce0be0$@uni-tuebingen.de>
Date: Tue, 25 Jan 2011 14:06:45 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B1562DB-979F-495F-933F-7B18B6D379FB@cisco.com>
References: <4D3AD6EA.5020607@jdrosen.net> <000001cbbad6$4f44aea0$edce0be0$@uni-tuebingen.de>
To: Christian Hoene <hoene@uni-tuebingen.de>
X-Mailer: Apple Mail (2.1082)
Cc: codec@ietf.org
Subject: Re: [codec] 3 week WGLC on draft-ietf-codec-requirements-02
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: Tue, 25 Jan 2011 21:01:58 -0000
I followed up with Christian on a separate thread and I hope we will sort out whatever is needed to fix this document. I just want to say the chairs certainly want this document to reflect rough consensus of the WG. Please, help us get there - review this document and provide suggested text for any technical changes that you think need to be made to the draft. Thanks, Cullen <CODEC co-chair> On Jan 23, 2011, at 1:19 AM, Christian Hoene wrote: >> The authors believe that the requirements document is complete. > > [Christian Hoene] Which authors? So far this document has only two selected > editors. > >> The chairs >> would like to now issue a 3 week working group last call for > draft-ietf-codec- >> requirements-02. At the end of 3 weeks, if no comments have been >> received, we will pass the document to the IESG for approval. > > [Christian Hoene] Despite hundreds of emails, what were exchanged on this > mailing list on issues regarding requirements, the editors have been > reluctant to update the requirements document according to the consensus > process on this mailing list. > > If I compare draft-ietf-codec-requirement-02 with > draft-valin-codec-requirements-02, I only see editorial changes. > https://tools.ietf.org/rfcdiff?url1=draft-ietf-codec-requirements-02&difftyp > e=--html&submit=Go!&url2=draft-valin-codec-requirements-02 > > Sorry guys, if I see this I become very cynical on the standardization > process at the IETF. The editors have not done their job and the chairs do > not care. At the end, it all looks like rubberstamping with a little bit of > theater. > > Christian > > > _______________________________________________ > codec mailing list > codec@ietf.org > https://www.ietf.org/mailman/listinfo/codec
- [codec] 3 week WGLC on draft-ietf-codec-requireme… Jonathan Rosenberg
- Re: [codec] 3 week WGLC on draft-ietf-codec-requi… Christian Hoene
- Re: [codec] 3 week WGLC on draft-ietf-codec-requi… Stephen Botzko
- Re: [codec] 3 week WGLC on draft-ietf-codec-requi… Christian Hoene
- Re: [codec] 3 week WGLC on draft-ietf-codec-requi… Stephan Wenger
- Re: [codec] 3 week WGLC on draft-ietf-codec-requi… Jean-Marc Valin
- Re: [codec] 3 week WGLC on draft-ietf-codec-requi… Mary Barnes
- Re: [codec] 3 week WGLC on draft-ietf-codec-requi… Peter Saint-Andre
- Re: [codec] 3 week WGLC on draft-ietf-codec-requi… Jean-Marc Valin
- Re: [codec] 3 week WGLC on draft-ietf-codec-requi… Elwell, John
- Re: [codec] 3 week WGLC on draft-ietf-codec-requi… Christian Hoene
- Re: [codec] 3 week WGLC on draft-ietf-codec-requi… Cullen Jennings
- Re: [codec] 3 week WGLC on draft-ietf-codec-requi… Mary Barnes