On Thu, Jun 16, 2011 at 4:42 PM, Christian Hoene <hoene@xxxxxxxxxxxxxxxx> 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@xxxxxxxx [mailto:codec-bounces@xxxxxxxx] On Behalf >> Of The IESG >> Sent: Thursday, June 16, 2011 9:24 PM >> To: IETF-Announce >> Cc: codec@xxxxxxxx >> 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@xxxxxxxx mailing lists by 2011-06-30. Exceptionally, comments may be >> sent to iesg@xxxxxxxx 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@xxxxxxxx >> https://www.ietf.org/mailman/listinfo/codec > > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf > _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf