Re: [codec] Last Call: <draft-ietf-codec-requirements-04.txt> (Codec Requirements) to Informational RFC

Cullen Jennings <fluffy@cisco.com> Mon, 20 June 2011 13:31 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: codec@ietfa.amsl.com
Delivered-To: codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D12A511E80AC; Mon, 20 Jun 2011 06:31:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d6SRJ8QrMyb5; Mon, 20 Jun 2011 06:31:49 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id DCE4211E8082; Mon, 20 Jun 2011 06:31:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=4104; q=dns/txt; s=iport; t=1308576709; x=1309786309; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=YyRCgEeYyo1JyZqyj3JWiMiKU+H2wtqgVnJNAUdFEno=; b=EuPvrcsj8Wz6h+QKKb+wjcv4FDYs1pFhkHaDHq45il9qgJG04aSvCS2+ lYfVtjS+DPIfwlg2dojGsdE9hq3AoMVHrGgx4Up4woqY8au4BM+NEugdw CdbVXXpZKZa7DB50hycPEADKutGewDg3uLFpITn/0EUfelc4lsbZjemAD w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvUAAHJL/02rRDoJ/2dsb2JhbABGDZdRjwt3iHOhGp1jgx6DDASHIIo+hGCLQA
X-IronPort-AV: E=Sophos;i="4.65,394,1304294400"; d="scan'208";a="717282598"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-6.cisco.com with ESMTP; 20 Jun 2011 13:31:48 +0000
Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p5KDVlQx021477; Mon, 20 Jun 2011 13:31:47 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <003e01cc2c65$ea831540$bf893fc0$@uni-tuebingen.de>
Date: Mon, 20 Jun 2011 07:31:47 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <2C1BBE56-DC0A-47A0-9F2C-A622AAB77EAA@cisco.com>
References: <003e01cc2c65$ea831540$bf893fc0$@uni-tuebingen.de>
To: Christian Hoene <hoene@uni-tuebingen.de>
X-Mailer: Apple Mail (2.1084)
Cc: codec@ietf.org, ietf@ietf.org
Subject: Re: [codec] Last Call: <draft-ietf-codec-requirements-04.txt> (Codec Requirements) to Informational RFC
X-BeenThere: codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Codec WG <codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 20 Jun 2011 13:31:50 -0000

This is all a sort of confusing point of many IETF documents and not unique to this one. I think the important points is that for many IETF documents, the people listed on the front page are not the authors. Typically the list of authors is a much longer list. And to clarify what I mean by Author, I mean it in the sense that it would used in copyright law. I do think the Acknowledgements section needs to identity anyone who is a contributor to the document. The limit on number of people on the front pages makes it impossible to even put all the authors on the front page if we wanted to. 

So my main point is, just because someone is listed on front page or not, should not be used to decide if they are an author or not. 

The use of "Ed." has been a bit inconsistent at the IETF and I'm not aware of good guidelines on how and when to use it. Traditionally when we have had a few people producing the drafts and incorporating work from the multiple people in on the mailing list, the people where were actively editing the document have often been listed on the front page. There are many exception to this - I was a bit cheesed to not be listed on the front page of RFC 4244. 

Back to the matter at hand ... This is a pretty classic sort of document where an individual draft got selected as a basis for the WG document, multiple people in the WG contributed text, a final draft was produced. Historically, most IETF docs like this do not put "Ed" after all the people on the front page. However, perhaps we should, I don't really have any strong opinion one way or the other. I can confirm that this document, like many documents coming out of a WG,  includes contribution from people beyond the list of names on the front page. 

Cullen


On Jun 16, 2011, at 2:42 PM, Christian Hoene wrote:

> Hello,
> 
> In this draft, the editors of draft are not named as editors but as authors.
> Thus, I would suggest to follow the example given in
> http://www.rfc-editor.org/rfc/rfc5620.txt and add an ", Ed." behind the
> names. A list of authors is given in the acknowledgement section of the
> draft.
> 
> With best regards,
> 
> Christian Hoene
> 
> 
>> -----Original Message-----
>> From: codec-bounces@ietf.org [mailto:codec-bounces@ietf.org] On Behalf
>> Of The IESG
>> Sent: Thursday, June 16, 2011 9:24 PM
>> To: IETF-Announce
>> Cc: codec@ietf.org
>> Subject: [codec] Last Call: <draft-ietf-codec-requirements-04.txt> (Codec
>> Requirements) to Informational RFC
>> 
>> 
>> The IESG has received a request from the Internet Wideband Audio Codec
>> WG
>> (codec) to consider the following document:
>> - 'Codec Requirements'
>>  <draft-ietf-codec-requirements-04.txt> as an Informational RFC
>> 
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2011-06-30. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>> 
>> Abstract
>> 
>> 
>>   This document provides specific requirements for an Internet audio
>>   codec.  These requirements address quality, sampling rate, bit-rate,
>>   and packet loss robustness, as well as other desirable properties.
>> 
>> 
>> 
>> 
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-codec-requirements/
>> 
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-codec-requirements/
>> 
>> 
>> No IPR declarations have been submitted directly on this I-D.
>> 
>> 
>> _______________________________________________
>> 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