URNbis                                                        J. Klensin
Internet-Draft
Obsoletes: 3044, 3187 (if approved)                            J. Hakala
Intended status: Standards Track         The National Library of Finland
Expires: August November 10, 2016                                February 7, 2016 2017                                   May 9, 2017

     Uniform Resource Name (URN) Namespace Registration Transition
                 draft-ietf-urnbis-ns-reg-transition-06
                 draft-ietf-urnbis-ns-reg-transition-07

Abstract

   The original registration procedure for formal Uniform Resource Name
   (URN) namespaces required IETF Consensus.  That requirement
   discouraged some registrations and increased the risk for problems
   that could occur as a result.  The requirements have now been changed
   in [[RFC 2141bis]].  That document
   by RFC 8141, which adopts a different model. model, focusing on encouraging
   registration and publication of information for all appropriate
   namespaces.  This document specifies IANA instructions to adapt selected existing
   registrations to the new model.  It also obsoletes some previous RFCs
   to eliminate any ambiguity about the clarifies that status of new templates relevant older
   RFCs and
   updated advises IANA about selected existing registrations.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August November 10, 2016. 2017.

Copyright Notice

   Copyright (c) 2016 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Obsoleting Older Registration RFCs for ISSNs and ISBNs  . . .   3
     2.1.  ISBN URN Changes  . . . . . . . . . . . . . . . . . . . .   4
     2.2.  ISSN URN Changes  . . . . . . . . . . . . . . . . . . . .   4
   3.  Obsoleting older registration RFC for NBNs  . . . . . . . . .   4
   4.  Other existing URN registrations and RFCs . . . . . . . . . .   4
   4.   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   5.
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   7.   6
   8.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   5
   8.   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .   7   8
     A.1.  Changes from version -00 to -01 . . . . . . . . . . . . .   7   8
     A.2.  Changes from version -01 to -02 . . . . . . . . . . . . .   7   8
     A.3.  Changes from version -02 to -03 . . . . . . . . . . . . .   7   9
     A.4.  Changes from version -03 to -04 . . . . . . . . . . . . .   7   9
     A.5.  Changes from version -04 to -05 . . . . . . . . . . . . .   8   9
     A.6.  Changes from version -05 to -06 . . . . . . . . . . . . .   8   9
     A.7.  Changes from version -06 (2016-02-07) to -07 (2017-05-09)   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8  10

1.  Introduction

   [[CREF1: RFC Editor: Please note that mentions of "[[RFC 2141bis]]"
   in this I-D are defined as an Entity in the XML with the brackets
   providing extra emphasis.  Before publication, they should be
   corrected, and the brackets removed, to show the actual RFC number.]]

   [[CREF2: Note in draft: This document has been written in RFC form,
   i.e., assuming that it and 2141bis have been approved.  That style of
   writing assumes that RFC 3406 and the rules it specified are already
   obsolete.  It may be a bit awkward while the I-D is being evaluated
   by the WG and the IETF, but lowers the risk for errors or other
   surprises during the RFC editing process.]]

   As a part of the initial development of the Uniform Resource Name
   (URN) system in the late 1990s, the IETF URN working group agreed
   that it was important to demonstrate that the URN syntax can
   accommodate existing identifier systems.  RFC 2288 [RFC2288]
   investigated proved
   the feasibility of using three identifiers (ISBN, ISSN International Standard Book Number (ISBN),
   International Standard Serial Number (ISSN), and Serial Item and SICI)
   Contribution Identifier (SICI) [ANSI-SICI]) as URNs, with positive results; URNs; however, it did
   not formally register corresponding URN namespaces.  This was in part
   due to the still evolving process to formalize criteria for namespace
   definition documents and registration, consolidated later in the IETF
   into successive Namespace Definition Mechanism documents [RFC2611]
   [RFC3406].

   URN Namespaces have subsequently been registered for NBN (National
   Bibliography Number) [RFC3188], ISBN (International Standard Book
   Number) [RFC3187], and ISSN (International Standard Serial Number)
   [RFC3044] as
   well as for a fairly large collection of other
   namespaces [IANA-Namespace-Registry]. identifiers including
   National Bibliography Number (NBN) [RFC3188].  The comprehensive list
   can be found in the IANA registry [IANA-Namespace-Registry] (see also
   Section 4).

   While a URN namespace for SICI could be registered at any time, the
   standard has not gained broad international acceptance and has not
   had a namespace defined to date.

   The predecessor registration procedure for Uniform Resource Name
   (URN) namespaces [RFC3406] required IETF Consensus for formal
   namespaces.  That requirement discouraged some registrations and
   increased the risk for problems, including use of names without
   registration ("squatting"), that could occur as a result.  Those
   potential problems included the possibility of the same name being
   used to identify different namespaces with different rules.  The
   requirements have now been changed [RFC2141bis] in RFC 8141 [RFC8141] to adopt a
   different model that focuses more on encouraging registration of all
   namespaces that follow the formal namespace syntax, with as much
   information collected as possible consistent with that goal.  This

   Therefore this document
   specifies does the following:

   o  Specifies IANA instructions to adapt selected existing
      registrations to the new model and obsoletes model.

   o  Obsoletes the separate RFCs that specify the namespaces for International Standard Serial Numbers (ISSNs)
   [RFC3044] ISSNs
      and International Standard Book Numbers (ISBNs) [RFC3187] ISBNs to eliminate any ambiguity about the status of new
      templates and updated registrations.

   An updated version of the specification for the namespace for
   National Bibliography Numbers (NBNs) [RFC3188] will be issued
   separately.  NBN is not a formal international standard and RFC 3188
   is the only formal document which specifies its scope.  The intention
   is to modernize the existing namespace registration so that it
   specifies

   o  Provides information about the identifier and provides examples status of its use, while NBNs under the
   actual namespace registration will be done according
      definitions.

   o  Provides suggestions to IANA about the new
   practice. handling of other existing
      registrations not explicitly mentioned herein.

2.  Obsoleting Older Registration RFCs for ISSNs and ISBNs

   The existing RFCs that describe URN namespaces for ISSNs (RFC 3044)
   and ISBNs (RFC 3187) should be identified as "Historic" after this
   document is approved and immediately after the new registration
   templates for those namespaces are submitted and incorporated into
   the URN Namespace registry by IANA.

   [[CREF3: Note in draft: The more information that can be supplied in
   the template or references from it, the better.  But, if there is
   information in the now-expired Internet-Drafts (draft-ietf-urnbis-
   rfc3187bis-isbn-urn, draft-ietf-urnbis-rfc3044bis-issn-urn) that
   should be captured somewhere and that doesn't fit naturally in the
   template, the discussion below is probably a reasonable place to put
   it.]]
   [[CREF4: Similarly, if special transition discussions are needed for
   other URN namespaces registered prior to the intended transition,
   this document might be a place to discuss them if they are not too
   complicated (if they are complicated, they probably deserve their own
   documents).]]

   The updated templates reflect not only new template formats but
   substantive changes to the definitions of the namespaces.  The
   changes are summarized in the subsections that follow.

   For both ISSN and ISBN URNs, it is intended that the registrations
   track the evolution of ISO standardization without requiring
   resubmission of the templates or other formal IETF or IANA
   registration update approval procedures.  The subsections that follow
   clarify the relationship between the original URN namespace
   registrations for ISBN and ISSN and new templates being registered
   that follow the principles of RFC 8141.  Approval and registration of
   those new templates makes the older templates obsolete and RFCs 3044
   and 3187 Historic.

2.1.  ISBN URN Changes

   The revised ISBN namespace reflects the updated latest version of the ISO
   Standard for ISBNs,
   ISBN Standard, ISO 2108:2005 2108:2017 [ISO-ISBN-b].  The namespace allows for
   the use of both the old ten character ISBN numbers described in RFC
   3187 and the earlier ISO 2108:1992 [ISO-ISBN-a] (known as ISBN-10), as
   well (formerly known as ISBN-10) and
   the expanded ones specified 13 character identifiers introduced in the revised and updated
   standard (known ISO 2108:2005 [ISO-ISBN-c]
   (formerly known as ISBN-13).

   For information and help in understanding other parts of this
   document, review the new ISBN registration template [ISBN-Template].

2.2.  ISSN URN Changes

   The updated ISSN namespace is also updated to reflect reflects the changes between the current
   ISSN Standard when standard [ISO-ISSN] and its predecessor on which RFC 3044 was written and
   based.  ISO 3297:2007 introduced the newest, 2007 linking ISSN (ISSN-L), which is
   designated for all media of a serial publication, irrespective of how
   many there are.  Traditional ISSN applies to single media only, such
   as printed version
   [ISO-ISSN]. of a serial.

   For information and help in understanding other parts of this
   document, review the new ISSN registration template [ISSN-Template].

3.  Obsoleting older registration RFC for NBNs

   NBN is not a formal international standard or even a single
   identifier system, but an umbrella concept which covers all
   identifier systems the national libraries and their partners use to
   identify resources which do not have other identifier.  For instance,
   if a book received via legal deposit does not have an ISBN, the
   national library gives it a local identifier.  NBN specification
   provides simple means of expressing these local identifiers so that
   they become globally unique URNs, such as urn:nbn:fi-fe19981001.

   In addition to the namespace registration itself, RFC 3188 provides
   some generic information about NBNs and their use, and specifies the
   syntax of URN:NBNs which guarantees uniqueness by requiring the usage
   of country codes and institutional identifiers as a part of the NSS.

   When RFC 3188 is revised, it should be accompanied with a template
   which revises the registration of the URN:NBN namespace.

4.  Other existing URN registrations and RFCs

   The RFC Series and IANA Registry contain many URN definitions namespace
   registrations in addition to those for which this document calls out
   explicit actions.  In general, those existing registrations are still
   appropriate but omit some information called for in [[RFC 2141bis]]. RFC 8141
   [RFC8141].  Reregistration with new templates is recommended, but not
   required.  Until and unless those registrations are updated as
   provided for in [[RFC
   2141bis]], RFC 8141, the existing registration templates should
   be read as not requiring or allowing any features that were not
   allowed and specified by the earlier URN [RFC2141] and registration
   [RFC3406] specifications.

4.

5.  IANA Considerations

   IANA is requested to update the registry entries for URN ISSN, ISBN,
   and NRN NBN namespaces to reflect the new, [[RFC 2141bis]]-complaint RFC 8141-compliant templates
   as soon as they are available and to no longer reference the now-historic now-
   historic RFCs.  With respect to namespaces other than those listed
   above, registrations and templates conforming to the newer rules may
   be substituted for the older ones when they are available.  However,
   neither this document nor [[RFC 2141bis]] supercedes RFC 8141 supersedes existing registrations
   other than those listed above.  Therefore, IANA needs to be prepared
   to maintain a registry whose contents reflect old-style templates for
   some namespaces (including, temporarily, those for ISBN and ISSN
   ones) and the newer ones for others.

   IANA should also note that the portions of the registrations that
   point to ISO Standards are intended to identify current versions
   (which may change) rather than only the versions that are active at
   the time this document is approved (see Section 2).

5.

6.  Security Considerations

   While particular URN namespaces and their registrations might
   conceivably have security implications, this specification merely
   specifies a transition of a set of namespace registrations and does
   not have such implications.  The security implications associated
   with particular namespaces are expected to be listed in registration
   templates as specified in [[RFC 2141bis]].

6. RFC 8141.

7.  Acknowledgements

   This document draws heavily on discussions in the IETF URNbis Working
   Group in the second and third quarters of 2013, particularly during
   IETF 87 in August 2013, and on informal discussions during the
   plenary meeting of ISO TC 46 in June 2013.  The efforts of those who
   participated in those discussions are greatly appreciated.  It also
   draws on internet-drafts that were developed to update the older
   registrations before that approach was replaced by the new extended
   template model.  Those drafts were prepared by Pierre Godefroy, Juha
   Hakala, Alfred Hoenes, and Maarit Huttunen.

   The current draft benefits significantly from a careful reading and
   suggestions
   suggestions for editorial changes by Peter Saint-Andre and from
   considerable work by Stella Griffiths of the ISBN international
   Centre to refine the ISBN discussion and from Pierre Godefroy and
   Clement Oury of the ISSN International Centre for similar refinements
   of the ISSN discussion.
   [[CREF1: RFC Editor and IANA: Please note that "Centre" is the
   correct spelling of the names of those bodies.  If you want to spell
   out the names, use "International Standard Book Number" and
   "International Standard Series Number" although the abbreviations are
   well-known internationally.  And M.  Oury's first name is properly
   spelled with an acute accent over the initial "e", i.e., with U+00E9
   should things be far enough along for editorial changes by Peter Saint-Andre.

7. you to use that information.]]

8.  Contributors

   Alfred Hoenes was the editor and co-author of two of the documents
   from which this one is, in part, derived.  This document would not
   have been possible without his contributions.

8.

9.  References

8.1.

9.1.  Normative References

   [RFC2141bis]

   [RFC8141]  Saint-Andre, P. and J. Klensin, "Uniform Resource Name
              (URN) Syntax", February 2016,
              <https://datatracker.ietf.org/doc/draft-ietf-urnbis-
              rfc2141bis-urn/>.

8.2. Names
              (URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017,
              <http://www.rfc-editor.org/info/rfc8141>.

9.2.  Informative References

   [ANSI-SICI]
              ANSI/NISO, "Serial Item and Contribution Identifier, ANSI/
              NISO Z39.56-1996 (Version 2)", 1996.

   [IANA-Namespace-Registry]
              IANA, "Uniform Resource Names (URN) Namespaces", 2016,
              <http://www.iana.org/assignments/urn-namespaces/
              urn-namespaces.xhtml>.

   [ISBN-Template]
              ISBN International Centre, "... to be supplied ...", 2017,
              <http://www.iana.org/???>.

              RFC Editor: please be sure the correct IANA links are
              filled in for this and the ISSN one.  Also, if you would
              like addresses and other contact information for these,
              that information is easily provided.

   [ISO-ISBN-a]
              ISO, "Information and documentation - The International
              Standard Book Number (ISBN)", ISO 2180:1992, 2108:1992, 1992.

   [ISO-ISBN-b]
              ISO, "Information and documentation - The International
              Standard Book Number (ISBN)", ISO 2180:2005, 2108:2017, 2017.

              Note to RFC Editor: As of early March, the 2017 version is
              awaiting publication, but the ISBN International Center
              strongly prefers that we reference it and not some earlier
              version.  If this note is still present when the document
              is otherwise ready for AUTH48, please see
              https://www.iso.org/standard/65483.html and discuss status
              with the authors.

   [ISO-ISBN-c]
              ISO, "Information and documentation - The International
              Standard Book Number (ISBN)", ISO 2108:2005, 2005.

   [ISO-ISSN]
              ISO, "Information and documentation - International
              standard serial number (ISSN)", ISO 3297:2007, 2007.

   [ISSN-Template]
              ISSN International Centre, "Namespace Registration for
              International Standard Serial Number (ISSN) and Linking
              ISSN (ISSN-L)ISO 3297:2007", 2017,
              <http://www.iana.org/???>.

   [RFC2141]  Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141,
              May 1997, <http://www.rfc-editor.org/info/rfc2141>.

   [RFC2288]  Lynch, C., Preston, C., and R. Daniel, "Using Existing
              Bibliographic Identifiers as Uniform Resource Names",
              RFC 2288, DOI 10.17487/RFC2288, February 1998,
              <http://www.rfc-editor.org/info/rfc2288>.

   [RFC2611]  Daigle, L., van Gulik, D., Iannella, R., and P. Falstrom, Faltstrom,
              "URN Namespace Definition Mechanisms", BCP 33, RFC 2611,
              DOI 10.17487/RFC2611, June 1999,
              <http://www.rfc-editor.org/info/rfc2611>.

   [RFC3044]  Rozenfeld, S., "Using The ISSN (International Serial
              Standard Number) as URN (Uniform Resource Names) within an
              ISSN-URN Namespace", RFC 3044, DOI 10.17487/RFC3044,
              January 2001, <http://www.rfc-editor.org/info/rfc3044>.

   [RFC3187]  Hakala, J. and H. Walravens, "Using International Standard
              Book Numbers as Uniform Resource Names", RFC 3187,
              DOI 10.17487/RFC3187, October 2001,
              <http://www.rfc-editor.org/info/rfc3187>.

   [RFC3188]  Hakala, J., "Using National Bibliography Numbers as
              Uniform Resource Names", RFC 3188, DOI 10.17487/RFC3188,
              October 2001, <http://www.rfc-editor.org/info/rfc3188>.

   [RFC3406]  Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
              "Uniform Resource Names (URN) Namespace Definition
              Mechanisms", BCP 66, RFC 3406, DOI 10.17487/RFC3406, October 2002,
              <http://www.rfc-editor.org/info/rfc3406>.

Appendix A.  Change Log

   RFC Editor: Please remove this appendix.

A.1.  Changes from version -00 to -01

   o  Modified the introduction to Section 2 and Section 4 5 to make it
      clear that registry update procedures should not be required to
      keep the registrations current with ISO Standard reaffirmations or
      replacments.

   o  Many editorial changes to improve readability and clarity.

A.2.  Changes from version -01 to -02

   o  Several small editorial changes and clarifications suggested by
      Peter Saint-Andre.

   o  Updated acknowledgments.

A.3.  Changes from version -02 to -03

   o  Updated to prevent expiration

   o  New text to allow for other already-registered namespaces and to
      better explain relationships.

   o  Some small editorial changes.

A.4.  Changes from version -03 to -04

   o  Updated references and, where needed, discussion to point to the
      new, consolidated, 2141bis rather than to the formerly separate
      and now obsolete 3406bis.

   o  Some small editorial changes.

A.5.  Changes from version -04 to -05

   o  Reissued to keep draft alive; no substantive changes.

   o  Updated references.

A.6.  Changes from version -05 to -06

   o  Reissued to keep draft alive; some editorial updates but no
      substantive changes.

   o  Updated references.

A.7.  Changes from version -06 (2016-02-07) to -07 (2017-05-09)

   o  Removed old CREFs.  Added a new one, but only as a forward-looking
      note to the RFC Editor.

   o  Moved expansions of ISBN, ISSN, SICI, and NBN to the first uses of
      those terms, after which the abbreviations are used exclusively.

   o  Removed text that made promises about the content and schedule for
      RFC 3188bis.

   o  Rewrote or removed several paragraphs that seemed to confuse the
      status of various documents and registrations.

   o  Added a cross-reference and additional detail for existing
      registrations not specifically discussed in this document.

   o  Modified the IANA Considerations section to improve clarity and
      remove references to the expected template appendices.  Because
      RFC 8141 (2141bis) has been published and the new registration
      procedures are in effect, there is presumably no reason to add
      length and confusion to this document by including preliminary
      versions of those templates.

   o  Updated references, including the reference to the recently-
      published RFC 8141 (aka 2141bis).

   o  Added placeholder references for the registrations of the new IANA
      templates.

   o  Corrected minor typographical errors.

Authors' Addresses

   John C Klensin
   1770 Massachusetts Ave, Ste 322
   Cambridge, MA  02140
   USA

   Phone: +1 617 245 1457
   Email: john-ietf@jck.com

   Juha Hakala
   The National Library of Finland
   P.O. Box 15, Helsinki University
   Helsinki, MA  FIN-00014
   Finland

   Email: juha.hakala@helsinki.fi