[urn] Authorship Re: I-D Action: draft-ietf-urnbis-rfc3406bis-urn-ns-reg-02.txt

[Leslie Daigle <[e-mail]>]

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.



On 3/12/12 4:20 PM, [e-mail] wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Uniform Resource Names, Revised Working Group of the IETF.
>
> 	Title           : Uniform Resource Name (URN) Namespace Definition Mechanisms
> 	Author(s)       : Alfred Hoenes
> 	Filename        : draft-ietf-urnbis-rfc3406bis-urn-ns-reg-02.txt
> 	Pages           : 30
> 	Date            : 2012-03-12
>
>     Uniform Resource Names (URNs) are intended to serve as persistent,
>     location-independent, resource identifiers.  To structure and
>     organize their usage, the URN syntax (RFC 2141bis) specifies a
>     hierarchy that divides the set of possible URNs into "URN Namespaces"
>     that can be individually defined and managed.  URN Namespaces in
>     particular serve to map existing identifier systems into the URN
>     system and thereby make available generic, network-based resolution
>     services for the identified documents, artifacts, and other objects
>     (and metadata related to them).
>
>     To achive these goals, URN Namespaces need to be specified in a
>     comparable manner, and their Namespace Identifiers (NIDs) need to be
>     registered with IANA, so that naming conflicts are avoided and
>     implementers of services can follow a structured approach in support
>     of various namespaces, guided by the registry to the related
>     documents and the particularities of specific namespaces, as
>     described in these Namespace registration documents.
>
>     This RFC serves as a guideline for authors of URN Namespace
>     definition and registration documents and the process to be followed
>     to register a URN Namespace with IANA.  It describes the essential
>     content of such documents and how they shall be structured to allow
>     readers familar with the scheme to quickly assess the properties of a
>     specific URN Namespace.
>
>     This document is a companion document to the revised URN Syntax
>     specification, RFC 2141bis; it supersedes and replaces RFC 3406.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-urnbis-rfc3406bis-urn-ns-reg-02.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-urnbis-rfc3406bis-urn-ns-reg-02.txt
>
> _______________________________________________
> urn mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/urn

-- 

-------------------------------------------------------------------
"Reality:
      Yours to discover."
                                 -- ThinkingCat
Leslie Daigle
[e-mail]
-------------------------------------------------------------------