Restricting front page authors with xml2rfc
Ben Niven-Jenkins <ben@niven-jenkins.co.uk> Wed, 07 December 2011 01:26 UTC
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A0B811E8082 for <l3vpn@ietfa.amsl.com>; Tue, 6 Dec 2011 17:26:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.166
X-Spam-Level:
X-Spam-Status: No, score=-103.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 pcFAqbDi02GB for <l3vpn@ietfa.amsl.com>; Tue, 6 Dec 2011 17:26:33 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfa.amsl.com (Postfix) with ESMTP id 3D45611E8080 for <l3vpn@ietf.org>; Tue, 6 Dec 2011 17:26:33 -0800 (PST)
Received: from cpc10-cmbg15-2-0-cust121.5-4.cable.virginmedia.com ([86.30.246.122] helo=[192.168.0.3]) by mail6.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1RY6HI-0002jE-2G; Wed, 07 Dec 2011 01:26:32 +0000
Subject: Restricting front page authors with xml2rfc
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <4EDEBB7E.6090007@raszuk.net>
Date: Wed, 07 Dec 2011 01:26:30 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <A6684F4C-6508-4AD3-8756-0CE8DE4CF24B@niven-jenkins.co.uk>
References: <1BFE7EAB-8CB7-4AC3-87EC-74F3EC54AC15@niven-jenkins.co.uk> <4EDEAFA7.9080803@raszuk.net> <B1B1D5E4-BB08-499F-BA8B-819AA312120C@niven-jenkins.co.uk> <4EDEBB7E.6090007@raszuk.net>
To: robert@raszuk.net
X-Mailer: Apple Mail (2.1084)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: "l3vpn@ietf.org mailing list" <l3vpn@ietf.org>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 01:26:34 -0000
Robert, On 7 Dec 2011, at 01:03, Robert Raszuk wrote: > Hello Ben, > > I am not aware about any former draft/rfc where there are "zombie authors". > > In most documents I have authored section 8 is directly populated from the xml header. So even technically I am keen on better understanding how xml2rfc conversion tool can list 4 authors in the header and 8 in the section 8. There is no way to do it with the standard xml2rfc package. The following e-mail contains a patch to xml2rfc which adds a new role of "notfirstpage" to achieve the effect. http://www.ietf.org/mail-archive/web/xml2rfc/current/msg02994.html Ben > > And that is very different from contributors section or separate section listing the authors or co-authors of the document. > > Best regards, > R. > > PS. The common convention during the merge if sigma of authors is greater then 5 is to just leave editors of the documents undergoing merge - here we are observing a bit different phenomenon. > > >> Robert, >> >> On 7 Dec 2011, at 00:13, Robert Raszuk wrote: >> >>> Support. >>> >>> However for clarity and future reference perhaps it would be good >>> to document the process of removing 4 authors from the header of >>> the draft and only leaving them in section 8. In particular Yiqun >>> and IJsbrand being original co-authors and contributors to the >>> idea. >>> >>> Even if this is a result of merge with >>> draft-rekhter-mvpn-wildcard-spmsi-04.txt removing original authors >>> of the idea seems odd. >> >> I don't know the specifics for this particular draft as I wasn't >> involved in writing it or any of the drafts that were merged together >> to form it but as I'm sure you know >> >> http://www.rfc-editor.org/policy.html#policy.authlist >> >> states the policy of no more than 5 authors on the front page and >> that they "should be the lead author(s) who are most responsible for >> the actual text" so my assumption is that the authors listed on the >> front page of draft-ietf-l3vpn-mvpn-wildcards-00 are those "most >> responsible" for the text of the combined draft rather than >> necessarily those "most responsible" for the original idea(s). >> >> If anyone feels strongly about only being credited in the "Authors" >> section and not on the front page itself they should bring it up with >> me privately offline. >> >> Regards Ben >> >> >>> >>> Thx, R. >>> >>>> Colleagues, >>>> >>>> This e-mail is the start of a 2 week WG Last Call for >>>> draft-ietf-l3vpn-mvpn-wildcards-00. >>>> >>>> Please read the draft and provide any comments you may have. >>>> >>>> Feedback should be provided to the mailing list and/or the >>>> authors. >>>> >>>> Last Call ends at midnight PST on the 20th December. >>>> >>>> Thanks Ben >>>> >>> >> >> >> >
- WG Last Call: draft-ietf-l3vpn-mvpn-wildcards-00 Ben Niven-Jenkins
- Re: WG Last Call: draft-ietf-l3vpn-mvpn-wildcards… Robert Raszuk
- Re: WG Last Call: draft-ietf-l3vpn-mvpn-wildcards… Ben Niven-Jenkins
- Re: WG Last Call: draft-ietf-l3vpn-mvpn-wildcards… Robert Raszuk
- Restricting front page authors with xml2rfc Ben Niven-Jenkins
- Re: WG Last Call: draft-ietf-l3vpn-mvpn-wildcards… Jeff Tantsura
- Re: WG Last Call: draft-ietf-l3vpn-mvpn-wildcards… Ben Niven-Jenkins
- Re: WG Last Call: draft-ietf-l3vpn-mvpn-wildcards… Ben Niven-Jenkins