Re: [xml2rfc] Multiple authors in reference

Joel Jaeggli <joelja@bogus.com> Tue, 09 August 2011 08:07 UTC

Return-Path: <joelja@bogus.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C000921F8713; Tue, 9 Aug 2011 01:07:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level:
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Ta8-+Jh2HAr; Tue, 9 Aug 2011 01:07:07 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 2103221F8438; Tue, 9 Aug 2011 01:07:07 -0700 (PDT)
Received: from [192.168.1.170] (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7987VYH081277 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 9 Aug 2011 08:07:33 GMT (envelope-from joelja@bogus.com)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <m2ipq73ypj.wl%randy@psg.com>
Date: Tue, 09 Aug 2011 01:07:30 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <FC3BAAFB-626D-4937-8304-BBA327917ECF@bogus.com>
References: <4E3F9E70.6080204@250bpm.com> <m2liv46zs5.wl%randy@psg.com> <4E40CE36.2000806@net-zen.net> <m2ipq73ypj.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 09 Aug 2011 08:07:35 +0000 (UTC)
X-Mailman-Approved-At: Tue, 09 Aug 2011 07:32:06 -0700
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>, IETF Discussion <ietf@ietf.org>
Subject: Re: [xml2rfc] Multiple authors in reference
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xml2rfc>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 08:07:07 -0000

On Aug 8, 2011, at 11:07 PM, Randy Bush wrote:

>>> above five, the rfced's deal with the iesg is that the masthead lists
>>> an editor and all the rest are in a Contributors or Authors section
>> I see.  So the author limit isn't really a "guideline" (as advertised)
>> or even a rule, just a backroom "deal".
> 
> have you taken your meds today?

http://tools.ietf.org/html/draft-rfc-editor-rfc2223bis-08

 2.12 Authors Listed on RFC


      The IESG and IETF have ratified a policy of limiting the number of
      authors listed in the first page header of an RFC.  The specific
      policy is as follows:


      (1)  A small set of author names, with affiliations, may appear on
           the front page header.  These should be the lead author(s)
           who are most responsible for the actual text.  When there are
           many contributors, the best choice will be to list the person
           or (few) persons who acted as document editor(s) (e.g.,"Tom
           Smith, Editor").


           There is no rigid limit on the size of this set, but there is
           likely to be a discussion if the set exceeds five authors, in
           which case the right answer is probably to list one editor.


           The RFC Editor will hold all the people listed on the front





RFC Editor                   Informational                     [Page 13]
 
Internet-Draft        Instructions to RFC Authors          1 August 2004




           page equally responsible for the final form and content of
           the published RFC.  In particular, the "Author's 48 Hours"
           final approval period will require signoff from all listed
           authors.


      (2)  An RFC may include a Contributors section, listing those
           contributors who deserve significant credit for the document
           contents.  The Contributors section is intended to provide a
           level of recognition greater than an acknowledgment and
           nearly equal to listing on the front page.  The choice of
           either, both, or none of Contributor and Acknowledgment
           sections in a particular RFC depends upon the circumstance.


      (3)  The body of an RFC may include an Acknowledgements section,
           in addition to or instead of a Contributors section.  An
           Acknowledgments section may be lengthy, and it may explain
           scope and nature of contributions.  It may also specify
           affiliations.


      (4)  The Author's Address section at the end of the RFC must
           include the authors listed in the front page header.  The
           purpose of this section is to (1) unambiguously define
           author/contributor identity (e.g., the John Smith who works
           for FooBar Systems) and to (2) provide contact information
           for future readers who have questions or comments.


           At the discretion of the author(s), contact addresses may
           also be included in the Contributors section for those
           contributors whose knowledge makes them useful future
           contacts for information about the RFC.


      (5)  The RFC Editor may grant exceptions to these guidelines upon
           specific IESG request or in other exceptional circumstances.


      Finally, it is important to note that the copyright rules
      governing RFC publication [IPC04] require that an RFC must:


           "[acknowledge] all major Contributors.  A major Contributor
           is any person who has materially or substantially contributed
           to the [RFC]."


      The Contributors and Acknowledgment sections fulfill this
      objective.

> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>