Re: [AVT] Draft charter revision
"Michael A. Ramalho" <mramalho@cisco.com> Mon, 14 July 2003 02:25 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11613 for <avt-archive@odin.ietf.org>; Sun, 13 Jul 2003 22:25:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19bt1Z-0005gs-Pd for avt-archive@odin.ietf.org; Sun, 13 Jul 2003 22:25:10 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6E2P9Ve021868 for avt-archive@odin.ietf.org; Sun, 13 Jul 2003 22:25:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19bt1S-0005eJ-6U; Sun, 13 Jul 2003 22:25:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19bt0n-0005dE-72 for avt@optimus.ietf.org; Sun, 13 Jul 2003 22:24:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11561 for <avt@ietf.org>; Sun, 13 Jul 2003 22:24:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19bt0k-0000i1-00 for avt@ietf.org; Sun, 13 Jul 2003 22:24:18 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 19bt0j-0000hw-00 for avt@ietf.org; Sun, 13 Jul 2003 22:24:17 -0400
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h6E2NjuJ027230; Sun, 13 Jul 2003 19:23:45 -0700 (PDT)
Received: from MRAMALHO-W2K1.cisco.com (sjc-vpn2-806.cisco.com [10.21.115.38]) by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AFZ60176; Sun, 13 Jul 2003 19:23:44 -0700 (PDT)
Message-Id: <4.3.2.7.2.20030713220122.01742a28@mira-sjc5-9.cisco.com>
X-Sender: mramalho@mira-sjc5-9.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sun, 13 Jul 2003 22:23:43 -0400
To: Colin Perkins <csp@csperkins.org>, avt@ietf.org
From: "Michael A. Ramalho" <mramalho@cisco.com>
Subject: Re: [AVT] Draft charter revision
Cc: casner@acm.org, magnus.westerlund@ericsson.com, mankin@psg.com
In-Reply-To: <20030714002309.377f68da.csp@csperkins.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
At 12:23 AM 7/14/2003 +0200, Colin Perkins wrote: >Attached is a draft for the revised AVT charter. This will be discussed in >the session tomorrow morning; comments are welcome. > >-- >Colin Perkins >csp@csperkins.org Colin/Magnus/Steve, I've got two questions regarding the following snippet from the re-charter: "The group continues to be precluded from work on codecs themselves because of overlap with the other standards bodies, and because the IETF does not have the ability to effectively review new codecs. An exception was made for the freeware iLBC codec on a highly experimental basis, but acceptance of new codec work is unexpected and subject to rechartering." 1) With regard to iLBC, while I understood that the issue was not fully resolved, I thought AVT was to be the "primary repository" for iLBC's definition (that is, not the ITU-T or other standards defining bodies). I more or less understand what "experimental" means in the IETF - but what does "highly experimental" mean? Is it even less probable that iLBC will eventually attain standards status by the additional adjective? 2) With regard to RGL (for people unfamiliar to RGL, see www.vovida.org for details), RGL is really a "lossless data compression technique" applied to (A or mu-law) G.711. Steve had requested that "avt" be included in the titles of RGL revisions - so I assumed it was a working group item. Is RGL covered in the "re-chartering statement" (above)? Or is RGL, by virtue of it having more in common with a data compression algorithm than a (lossy) signal processing codec, exempt (no codec expertise needed - a rational noted above)? If this is unclear, could you obtain further guidance from the ADs (Allison) or the IESG? Thanks, Michael Ramalho Michael A. Ramalho, Ph.D. Office email: mramalho@cisco.com Personal email: mar42@cornell.edu Office: +1.941.708.4650 Cell: +1.941.544.2844 _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] Draft charter revision Colin Perkins
- Re: [AVT] Draft charter revision Michael A. Ramalho
- Re: [AVT] Draft charter revision Colin Perkins