[trill] IESG Statement on authorship

"Susan Hares" <shares@ndzh.com> Fri, 12 June 2015 16:17 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id EB3801A1B3F for <trill@ietfa.amsl.com>; Fri, 12 Jun 2015 09:17:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.054
X-Spam-Status: No, score=-99.054 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id FcrgR6xn_k_k for <trill@ietfa.amsl.com>; Fri, 12 Jun 2015 09:17:46 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com []) by ietfa.amsl.com (Postfix) with ESMTP id 234101A88B3 for <trill@ietf.org>; Fri, 12 Jun 2015 09:17:23 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=;
From: Susan Hares <shares@ndzh.com>
To: trill@ietf.org
Date: Fri, 12 Jun 2015 12:17:04 -0400
Message-ID: <017e01d0a52b$3939a400$abacec00$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_017F_01D0A509.B22B1140"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdClKxLFY3PdQavsRaeBE87FLRTTJg==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/M6sn8upqQOWs2cIfZuRuj6HtQKk>
Cc: 'Donald Eastlake' <d3e3e3@gmail.com>, 'Jon Hudson' <jon.hudson@gmail.com>, trill-chairs@tools.ietf.org, 'Alia Atlas' <akatlas@gmail.com>
Subject: [trill] IESG Statement on authorship
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jun 2015 16:17:49 -0000

TRILL WG members: 


You may want to know about the IESG statement on Internet draft authorship.  My thanks to Deborah Brungard  (our Routing AD) who forwarded this to me. 


Sue Hares


-----Original Message-----
From: BRUNGARD, DEBORAH A [mailto:db3546@att.com] 
Sent: Friday, June 12, 2015 10:36 AM
To: rtg-chairs@ietf.org
Subject: FW: IESG Statement on Internet Draft Authorship


Not everyone pays attention to the ietf-list, you may want to distribute on your wg lists-



-----Original Message-----

From: IETF-Announce [ <mailto:ietf-announce-bounces@ietf.org> mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG

Sent: Thursday, June 11, 2015 2:32 PM

To: IETF Announcement List

Subject: IESG Statement on Internet Draft Authorship


The IESG has received some reports of IETF participants having been listed as document authors on drafts without their consent ("surprised authorship"). In some cases, the surprised authors had never seen the draft that surprised them. It appears that some draft authors think that including other participants as authors is a way to show support for the concepts in the document and gain acceptance for those concepts. This may be thought of as especially useful if the additional authors are established IETF participants.


Adding names of IETF participants who did not actually work on a proposal might seem to be a low-risk way of demonstrating "support", but this is very clearly not an acceptable practice: no one should ever be added to the list of authors on a draft unless that person has consented to it and has contributed significantly to the development of the draft.


The practice of adding surprised authors is


  - not in line with the IETF culture, where it's the technical issues 

    that matter, not who the authors or supporters are;

  - unethical, as it is wrong to claim support from someone who has not 

    consented to it;

  - misleading in terms of support; and

  - problematic in terms of IPR disclosures (BCPs 78 and 79). 


To emphasize this last point, the person submitting an Internet-Draft is asserting that "This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79". A submitter who has not discussed this with all the listed authors cannot make that claim, and this can cause procedural and legal problems later.


All authors need to be aware of the ​RFC Editor's statement on authorship [1], especially as it relates to responsibility for the document's contents. The IESG strongly recommends that all drafts have explicit permission from all authors to have their names listed before the draft is submitted.


If you feel that you are impacted by the above issues, please talk to your Area Director or contact the IESG by ​sending email to < <mailto:iesg@ietf.org> iesg@ietf.org>. As the administrator of the I-D repository (regardless of the source or intended stream for the draft), the IESG will handle each case of disputed authorship on a case-by-base basis. All reports will be investigated, and substantiated claims will be met with corrective actions.


The default corrective action will be the replacement of the offending draft with a "disputed authorship" tombstone. Such a tombstone would:


  - Be published as a successor to the offending draft,

  - Have the offended IETF participant listed as the only author,

  - Will state "The author listed on this tombstone Internet-Draft has 

    stated that he/she should not have been listed as an author on the 

    previous version. The IETF considers being added as an author 

    without one's permission as unethical. The default behaviour of the 

    IESG in such cases is to approve replacement of the offending draft 

    with this tombstone. Please direct any queries to the author listed 



[1]  <http://www.rfc-editor.org/pipermail/rfc-interest/2015-May/008869.html> http://www.rfc-editor.org/pipermail/rfc-interest/2015-May/008869.html