RFC Series Editor statement on authorship

RFC Series Editor <rse@rfc-editor.org> Fri, 15 May 2015 00:32 UTC

Return-Path: <rse@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 293411B29C0 for <ietf-announce@ietfa.amsl.com>; Thu, 14 May 2015 17:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 9Zboj-6BwIsO; Thu, 14 May 2015 17:32:46 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DFB2D1AD259; Thu, 14 May 2015 17:32:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: RFC Series Editor <rse@rfc-editor.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: RFC Series Editor statement on authorship
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150515003246.23210.64861.idtracker@ietfa.amsl.com>
Date: Thu, 14 May 2015 17:32:46 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/qJsmeWN-e1c85_bvlICdsUOQjdk>
Cc: rfc-interest@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org, rfc-interest@rfc-editor.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 May 2015 00:32:48 -0000

The intent of the author list in the document header and the Authors
Addresses space in an RFC is to indicate who is responsible for the
technical content of the document. Listing as an author indicates active
technical contribution to the text either by personally writing a
substantial part of it or by detailed and close technical collaboration
with the person(s) doing so. If the development of a document has been
delegated or subcontracted, the authors are the person(s) doing the
actual writing, not the person(s) delegating or subcontracting the work.
The RFC Series provides for acknowledgement and contributor section to
recognize other parties that support the document but who are not
authors by the definition above.

In keeping with the history of the RFC Series, if there are more than
five authors for a single document, one or two editors should be chosen
and listed, and all contributors to the text should be listed in the
contributor section (see Section 4.1.1. of the RFC Style Guide [RFC7322]).
Exceptions should be discussed with the relevant stream approving body
(IESG, IRSG, IAB, or ISE) and the RFC Editor.

All contributors are expected to review the intellectual property rules
governing their contributions, as described in the IETF Trust Legal
Provisions <http://trustee.ietf.org/trust-legal-provisions.html>.
These rules provide guidance applicable to all document streams.

This guidance will be added to the RFC Style Guide