Re: [urn] Authorship Re: I-D Action: draft-ietf-urnbis-rfc3406bis-urn-ns-reg-02.txt
Alfred Hönes <ah@TR-Sys.de> Sun, 25 March 2012 23:25 UTC
Return-Path: <A.Hoenes@TR-Sys.de>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B54621E804C for <urn@ietfa.amsl.com>; Sun, 25 Mar 2012 16:25:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.627
X-Spam-Level:
X-Spam-Status: No, score=-98.627 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, 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 Qtn-Gj6IbFfQ for <urn@ietfa.amsl.com>; Sun, 25 Mar 2012 16:25:47 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by ietfa.amsl.com (Postfix) with ESMTP id C266A21E801C for <urn@ietf.org>; Sun, 25 Mar 2012 16:25:45 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA258577877; Mon, 26 Mar 2012 01:24:37 +0200
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id BAA21248; Mon, 26 Mar 2012 01:24:35 +0200 (MESZ)
From: Alfred Hönes <ah@TR-Sys.de>
Message-Id: <201203252324.BAA21248@TR-Sys.de>
To: leslie@thinkingcat.com
Date: Mon, 26 Mar 2012 01:24:35 +0200
In-Reply-To: <4F6F16E5.8060909@thinkingcat.com> from Leslie Daigle at Mar "25, " 2012 "09:00:21" am
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset="hp-roman8"
Content-Transfer-Encoding: 7bit
Cc: urn@ietf.org
Subject: Re: [urn] Authorship Re: I-D Action: draft-ietf-urnbis-rfc3406bis-urn-ns-reg-02.txt
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Mar 2012 23:25:47 -0000
Leslie Daigle wrote: > Hi, > > This document says: > >> IETF URNbis WG A. Hoenes >> Internet-Draft TR-Sys >> Obsoletes: 3406 (if approved) March 12, 2012 >> Intended status: BCP >> Expires: September 13, 2012 > > and > >> 7. Acknowledgements >> >> This document is heavily based on RFC 3406, the authors of which are >> cordially acknowledged. >> > > I don't think this is appropriate. The bulk of the work was done by > the original authors/editors/WG, this is not a complete rewrite. > > I believe the appropriate thing is to list the original authors > (unless they don't want to be!), and add the new author. > > This is also true for the syntax document, but I'm mentioning it here > because I'm clearly more implicated, as lead author on both previous > iterations of this RFC. > > Leslie. Leslie, I'm a bit surprised that you raise this argument now (and haven't done so much earlier). The delineation of who should appear as an "Author" or be listed in the "Contributors" or Acknowledgements" section of an RFC, and -- by induction -- of an I-D, seems to be a subject of recurring debate. Here is the background I'm aware of: RFC 5378 and its predecessors admit -- notwithstanding specifically indicating-so exceptions -- the unlimited right to prepare derived work within the IETF. Section 5.6 (a) of BCP 78 is rather terse on what "properly acknowledge[ing] all Contributors" means in detail. >From the perspective of the RFC Editor, being listed on the front page of an RFC means active participation during the final RFC Editor processing stages; according to my limited experience, the IESG also expects listed authors to be available for interaction during their evaluation process of a draft (once publication is requested). The RFC Style and Policy documents indicate that people not listed on the front page can be acknowledged in Contributors and/or Acknowledgements sections, which are seen as almost equivalent -- the practical difference being that people listed in a Contributors section optionally can be shown with full contact information like in the Authors' Address section. Working Groups in the IETF at present seem to have divergent policies on whom to list on the front page of their WG documents that revise previous work. Some seem to be very strict in only listing active authors/editors, and that also seems to be the essence of the RFC Editor's policy. The (vaguely) related elaborations in the "Tao" of the IETF also seem to be compatible with this policy (in particular the Tao points out that WG chairs decide who is going to be listed on the front page of WG documents). Until the advent of a related recent thread on the wgchairs list I haven't even been aware of successful diverging practice in other WGs of the IETF. The first version of the rfc2141bis draft was submitted im March 2010 and the first version of the rfc3406bis draft in November 2010. IIRC, you have been engaged in the process leading to the formation of the URNbis WG (but haven't been able to attend the BoF in person) and you have attended the WG's meeting at IETF 80. If you had indicated interest in working on the documents, I would have been honored to work with you and have your name listed on the front page of the rfc3406bis draft, but absent such indication, I simply followed the examples I've seen in the past in other WGs I've been active in, where only individuals working actively on the documents were being listed on the front page of "bis" documents. I also do not recall participation of the author of RFC 2141 in URNbis-related activities or any indication of desire to participate in the work on the rfc2141bis draft -- which of course would have been honored as well. As long as the work distribution remains the same as up to now, I'd like to defer the decision on the front page listing to the RFC Editor or eventually emerging new consensus in the IETF that might in fact invalidate the aforementioned strict practice. If you can commit time to actually perform work on the rfc3406bis draft, I'll readily agree, and you'll of course be listed on the front page of the next draft version. Otherwise, if you would prefer being listed in a distinct "Contributors" section -- maybe including contact information, then please let me know. Kind regards, Alfred. -- +------------------------+--------------------------------------------+ | TR-Sys Alfred Hoenes | Alfred Hoenes Dipl.-Math., Dipl.-Phys. | | Gerlinger Strasse 12 | Phone: (+49)7156/9635-0, Fax: -18 | | D-71254 Ditzingen | E-Mail: ah@TR-Sys.de | +------------------------+--------------------------------------------+ > ... [snip] > > -- > > ------------------------------------------------------------------- > "Reality: > Yours to discover." > -- ThinkingCat > Leslie Daigle > leslie@thinkingcat.com > -------------------------------------------------------------------
- [urn] I-D Action: draft-ietf-urnbis-rfc3406bis-ur… internet-drafts
- [urn] Namespace and Community Considerations Re: … Leslie Daigle
- [urn] Review period Re: I-D Action: draft-ietf-ur… Leslie Daigle
- [urn] Authorship Re: I-D Action: draft-ietf-urnbi… Leslie Daigle
- Re: [urn] Namespace and Community Considerations … Alfred Hönes
- Re: [urn] Review period ... draft-ietf-urnbis-rfc… Alfred Hönes
- Re: [urn] Authorship Re: I-D Action: draft-ietf-u… Alfred Hönes
- Re: [urn] Authorship Re: I-D Action: draft-ietf-u… Peter Saint-Andre
- Re: [urn] Review period ... draft-ietf-urnbis-rfc… Peter Saint-Andre
- Re: [urn] Namespace and Community Considerations … Peter Saint-Andre
- Re: [urn] Review period Re: I-D Action: draft-iet… Juha Hakala