Re: [codec] consensus call: guidelines and requirements
Jonas Svedberg <jonas.svedberg@ericsson.com> Sat, 27 February 2010 21:00 UTC
Return-Path: <jonas.svedberg@ericsson.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 A407E28C202 for <codec@core3.amsl.com>; Sat, 27 Feb 2010 13:00:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 aKVgO0d3mY-2 for <codec@core3.amsl.com>; Sat, 27 Feb 2010 13:00:46 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 04F2B28C2E2 for <codec@ietf.org>; Sat, 27 Feb 2010 13:00:45 -0800 (PST)
X-AuditID: c1b4fb39-b7c2dae000007b99-61-4b8988885bc5
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 9E.2D.31641.888898B4; Sat, 27 Feb 2010 22:03:04 +0100 (CET)
Received: from ESESSCMS0361.eemea.ericsson.se ([169.254.1.202]) by esessmw0256.eemea.ericsson.se ([10.2.3.125]) with mapi; Sat, 27 Feb 2010 22:03:03 +0100
From: Jonas Svedberg <jonas.svedberg@ericsson.com>
To: Codec WG <codec@ietf.org>
Date: Sat, 27 Feb 2010 22:03:03 +0100
Thread-Topic: [codec] consensus call: guidelines and requirements
Thread-Index: Acq02C7bX1i6roo1RRWknr7VXQRjvwC/DyIg
Message-ID: <70605C7F7303F24DA29681D7F6AB952801A4E836@ESESSCMS0361.eemea.ericsson.se>
References: <4B84574A.5070204@stpeter.im>
In-Reply-To: <4B84574A.5070204@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
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: Sat, 27 Feb 2010 21:00:47 -0000
Hi all, With respect to the standardization guidelines I see that more work is needed to bring it inline with the spirit of the charter, before adopting as a WG draft document e.g. *The charter is much clearer on the goal of having one standardized codec compared to the the <draft-valin-codec-guidelines-02> where in sections 1 and 2 the guidelines target can still be seen as the standardization of several codecs. *Regarding the IPR section 5, (if this section is to be maintained in the process guidelines at all), it needs be aligned with the charter and then further discussion is desired especially around the listed subguidelines within section 5. *Also in general the WG draft guidelines should be limited to the process description of the codec standardization work, and not include motivational/promotional parts. e.g. in section 1, section 5. The preferred way forward would be to develop the draft-guidelines a bit further and then check for consensus at IETF 77. -- With respect to the requirements draft it is fine as a *starting point*, (I do see that the definition of the main application and the various design constraints/references for the various points in the "Operating Space" still need further input/discussion. ) //BR Jonas Svedberg PS As I am new to this list: For those who do not know me I am working at Ericsson. DS -----Original Message----- From: codec-bounces@ietf.org [mailto:codec-bounces@ietf.org] On Behalf Of Peter Saint-Andre Sent: den 23 februari 2010 23:32 To: Codec WG Subject: [codec] consensus call: guidelines and requirements Our charter [1] specifies that our first two deliverables shall be: 1. A set of Codec Standardization Guidelines that define the work processes of the working group. This document shall be Informational. 2. A set of technical Requirements. This document shall be Informational. The submission deadline [2] for -00 drafts before IETF 77 is fast approaching. Because it is desirable for these documents to be official WG items before our session at IETF 77, as Chairs we hereby issue a consensus call for: 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. We emphasize that these will be *initial* versions and that the existing Internet-Drafts will be used as *starting points* for discussion and consensus-building within the WG. (In fact, the Chairs have some list feedback to incorporate before submitting these documents to the Secretariat, so the versions referenced above are not *exactly* what would be submitted, but they are close.) We also emphasize that if accepted as WG items these documents will initially be under the editorship of the Chairs (not the current document authors) until the Chairs have an opportunity to select official Document Editors for these Internet-Drafts as described in Section 6.3 of RFC 2418. The Chairs envision that Document Editors can be selected close in time to IETF 77. Please provide your feedback to this consensus call by the end of the day on Sunday, 2010-02-28, so that if accepted the Chairs can submit -00 versions of the relevant Internet-Drafts before the cut-off date (Monday, 2010-03-01 at 17:00 PST). Thank you. Peter Saint-Andre & Michael Knappe Co-chairs, Codec WG [1] http://tools.ietf.org/wg/codec/charters [2] http://www.ietf.org/meeting/cutoff-dates-2010.html#IETF77 [3] http://tools.ietf.org/html/draft-valin-codec-guidelines-02 [4]http://tools.ietf.org/html/draft-valin-codec-requirements-02
- [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