IETF Logo Mail Archive

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

Donald Eastlake <d3e3e3@gmail.com> Fri, 17 June 2011 20:31 UTC

Return-Path: <d3e3e3@gmail.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 F319821F8496; Fri, 17 Jun 2011 13:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 iFXci2nnfQIx; Fri, 17 Jun 2011 13:31:51 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1C50121F8498; Fri, 17 Jun 2011 13:31:51 -0700 (PDT)
Received: by ywp31 with SMTP id 31so2036247ywp.31 for <multiple recipients>; Fri, 17 Jun 2011 13:31:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=XgrnMs6M2OQPcSmwbDB+RYC1ptdKIN/NBOEUnlLRkW4=; b=VeI/Yp04vcFseqGRUB8dS/tjzpPKV/GzxdeK/lMQsfGml8DODE0txfOVkWdUaaF6fz agKjvgFh5aP4V3/fOGXO+RTqoIqQZ0KzNYQ12AK29L2nguMTDSw22hnf1jlOI+6CtgDM XMMHOYgPPMC6HOTTIjCsuA3wTJoNGg8OVyqzM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=oydJC33TnsU+gz0TTLS6ezdVwHDsxYJNhJ0eLS95f+Cbs8a7sLnzeqEN48EEdf49FQ Mh2nWGRuLWCzaRL4NlWul28lBud0vXENt0JMgGdvUiqzSkPsUqzkpyOMmDCMIhvRD7PB 2nIS4HbQn0JTSTdqYaBUpqE/QE+SEbU+lJQL0=
Received: by 10.150.136.2 with SMTP id j2mr2942837ybd.125.1308342709130; Fri, 17 Jun 2011 13:31:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.14.8 with HTTP; Fri, 17 Jun 2011 13:31:29 -0700 (PDT)
In-Reply-To: <003e01cc2c65$ea831540$bf893fc0$@uni-tuebingen.de>
References: <003e01cc2c65$ea831540$bf893fc0$@uni-tuebingen.de>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 17 Jun 2011 16:31:29 -0400
Message-ID: <BANLkTimLCvhnWp6D_6ZYmK9N_s_yGHr+XQ@mail.gmail.com>
To: Christian Hoene <hoene@uni-tuebingen.de>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Fri, 24 Jun 2011 08:50:51 -0700
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: Fri, 17 Jun 2011 20:31:52 -0000

On Thu, Jun 16, 2011 at 4:42 PM, Christian Hoene <hoene@uni-tuebingen.de> 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.

If everyone listed at the upper right of the first page is going to be
an Editor, then adding "Ed." after their name is completely
superfluous and adds only clutter.

Traditionally, those listed at the upper right of the first page of an
RFC have been called "authors" in most cases, regardless of their
actual role, and those listed in an Acknowledgements section have
frequently been called "contributors" or the like. So I think it s
perfectly fine the way it is in regards to this non-issue.

Donald

> 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
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

v2.23.0 | Report a Bug | By Email