draft-ietf-urnbis-ns-reg-transition-08.txt   rfc8254.txt 
URNbis J. Klensin Internet Engineering Task Force (IETF) J. Klensin
Internet-Draft Request for Comments: 8254
Obsoletes: 3044, 3187 (if approved) J. Hakala Obsoletes: 3044, 3187 J. Hakala
Intended status: Standards Track The National Library of Finland Category: Standards Track The National Library of Finland
Expires: January 2, 2018 July 1, 2017 ISSN: 2070-1721 October 2017
Uniform Resource Name (URN) Namespace Registration Transition Uniform Resource Name (URN) Namespace Registration Transition
draft-ietf-urnbis-ns-reg-transition-08
Abstract Abstract
The original registration procedure for formal Uniform Resource Name The original registration procedure for formal Uniform Resource Name
(URN) namespaces required IETF Consensus. That requirement (URN) namespaces required IETF Consensus. That requirement
discouraged some registrations and increased the risk for problems discouraged some registrations and increased the risk for problems
that could occur as a result. The requirements have now been changed that could occur as a result. The requirements have now been changed
by RFC 8141, which adopts a different model, focusing on encouraging by RFC 8141, which adopts a different model, focusing on encouraging
registration and publication of information for all appropriate registration and publication of information for all appropriate
namespaces. This document clarifies the status of relevant older namespaces. This document clarifies the status of relevant older
RFCs and confirms and documents advice to IANA about selected RFCs and confirms and documents advice to IANA about selected
existing registrations. existing registrations. This document also obsoletes RFCs 3044 and
3187 and moves them to Historic status. These RFCs describe the ISSN
and ISBN namespaces, which are now outdated because the descriptions
reside in registration templates.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on January 2, 2018. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8254.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Obsoleting Older Registration RFCs for ISSNs and ISBNs . . . 3 2. Obsoleting Older Registration RFCs for ISSNs and ISBNs . . . 4
2.1. ISBN URN Changes . . . . . . . . . . . . . . . . . . . . 4 2.1. ISBN URN Changes . . . . . . . . . . . . . . . . . . . . 4
2.2. ISSN URN Changes . . . . . . . . . . . . . . . . . . . . 4 2.2. ISSN URN Changes . . . . . . . . . . . . . . . . . . . . 4
3. The Older Registration RFC for NBNs . . . . . . . . . . . . . 4 3. The Older Registration RFC for NBNs . . . . . . . . . . . . . 5
4. Other Existing URN Registrations and RFCs . . . . . . . . . . 5 4. Other Existing URN Registrations and RFCs . . . . . . . . . . 5
5. Registration Examples . . . . . . . . . . . . . . . . . . . . 5 5. Registration Examples . . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . 6 7. Security Considerations . . . . . . . . . . . . . . . . . . . 6
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . 6
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 8.2. Informative References . . . . . . . . . . . . . . . . . 6
10.1. Normative References . . . . . . . . . . . . . . . . . . 6 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 8
10.2. Informative References . . . . . . . . . . . . . . . . . 6 Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
A.1. Changes from version -00 to -01 . . . . . . . . . . . . . 8
A.2. Changes from version -01 to -02 . . . . . . . . . . . . . 8
A.3. Changes from version -02 to -03 . . . . . . . . . . . . . 9
A.4. Changes from version -03 to -04 . . . . . . . . . . . . . 9
A.5. Changes from version -04 to -05 . . . . . . . . . . . . . 9
A.6. Changes from version -05 to -06 . . . . . . . . . . . . . 9
A.7. Changes from version -06 (2016-02-07) to -07 . . . . . . 9
A.8. Changes from version -07 (2017-05-09) to -08 . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
As a part of the initial development of the Uniform Resource Name As a part of the initial development of the Uniform Resource Name
(URN) system in the late 1990s, the IETF URN working group agreed (URN) system in the late 1990s, the IETF URN Working Group agreed
that it was important to demonstrate that the URN syntax could that it was important to demonstrate that the URN syntax could
accommodate existing identifier systems. RFC 2288 [RFC2288] showed accommodate existing identifier systems. RFC 2288 [RFC2288] showed
the feasibility of using International Standard Book Number (ISBN), the feasibility of using International Standard Book Number (ISBN),
International Standard Serial Number (ISSN), and Serial Item and International Standard Serial Number (ISSN), and Serial Item and
Contribution Identifier (SICI) [ANSI-SICI]) as URNs; however, it did Contribution Identifier (SICI) [ANSI-SICI] as URNs; however, it did
not formally register corresponding URN namespaces. This was in part not formally register corresponding URN namespaces. This was in part
due to the still evolving process to formalize criteria for namespace due to the still-evolving process to formalize criteria for namespace
definition documents and registration, consolidated later by the IETF definition documents and registration, consolidated later by the IETF
into successive Namespace Definition Mechanism documents [RFC2611] into successive Namespace Definition Mechanism documents [RFC2611]
[RFC3406]. [RFC3406].
URN Namespaces were subsequently registered for ISBN [RFC3187] and URN namespaces were subsequently registered for ISBN [RFC3187] and
ISSN [RFC3044] as well as for a fairly large collection of other ISSN [RFC3044] as well as for a fairly large collection of other
identifiers including National Bibliography Number (NBN) [RFC3188]. identifiers including National Bibliography Number (NBN) [RFC3188].
The comprehensive list can be found in the IANA registry The comprehensive list can be found in the IANA Uniform Resource
[IANA-Namespace-Registry] (see also Section 4). Names (URN) Namespaces registry [IANA-URN] (see also Section 4).
While a URN namespace for SICI could be registered at any time, the While a URN namespace for SICI could be registered at any time, the
SICI Standard has not gained broad international acceptance and has SICI standard has not gained broad international acceptance and has
not had a namespace defined to date. not had a namespace defined to date.
The predecessor registration procedure for Uniform Resource Name The predecessor registration procedure for URN namespaces [RFC3406]
(URN) namespaces [RFC3406] required IETF Consensus for formal required IETF Consensus for formal namespaces. That requirement
namespaces. That requirement discouraged some registrations and discouraged some registrations and increased the risk for problems,
increased the risk for problems, including use of names without including use of names without registration ("squatting"). If names
registration ("squatting"). Those potential problems included the are not registered in a consistent way, there is a possibility of the
possibility of the same name being used to identify different same name being used to identify different namespaces with different
namespaces with different rules. The requirements have now been rules, resulting in considerable confusion. The requirements have
changed in RFC 8141 [RFC8141] to adopt a different model that focuses now been changed in RFC 8141 [RFC8141] to adopt a different model
more on encouraging registration of all namespaces that follow the that focuses more on encouraging registration of all namespaces that
formal namespace syntax, with as much information collected as follow the formal namespace syntax, with as much information
possible consistent with that goal. collected as possible consistent with that goal.
Therefore this document does the following: Therefore, this document does the following:
o Describes the instructions developed with IANA to adapt selected o Describes the instructions developed with IANA to adapt selected
existing registrations to the new model. Those registration existing registrations to the new model. Those registration
updates have been completed for ISBN and ISSN NIDs and URN updates have been completed for ISBN and ISSN Namespace
namespaces. Identifiers (NIDs) and URN namespaces.
o Obsoletes the separate RFCs that specify the namespaces for ISSNs o Obsoletes the separate RFCs that specify the namespaces for ISSNs
and ISBNs to eliminate any ambiguity about the status of new and ISBNs to eliminate any ambiguity about the status of new
templates and updated registrations. templates and updated registrations.
o Provides information about the status of NBNs under the new o Provides information about the status of NBNs under the new
definitions. definitions.
o Provides suggestions to IANA about the handling of other existing o Provides suggestions to IANA about the handling of other existing
registrations not explicitly discussed in this document. registrations not explicitly discussed in this document.
2. Obsoleting Older Registration RFCs for ISSNs and ISBNs 2. Obsoleting Older Registration RFCs for ISSNs and ISBNs
The existing RFCs that describe URN namespaces for ISSNs [RFC3044] The existing RFCs that describe URN namespaces for ISSNs [RFC3044]
and ISBNs [RFC3187] should be identified as "Historic" after this and ISBNs [RFC3187] have been identified as "Historic" concurrent
document is approved. The new registration templates for those with publication of this document. The new registration templates
namespaces have already been submitted and incorporated into the URN for those namespaces have already been submitted and incorporated
Namespace registry by IANA. into the URN Namespaces registry by IANA.
Those updated templates reflect not only the new template formats but Those updated templates reflect not only the new template formats but
substantive changes to the definitions of the namespaces. The substantive changes to the definitions of the namespaces. The
significant changes are summarized in the subsections that follow. significant changes are summarized in the subsections that follow.
For both ISSN and ISBN URNs, it is intended that the registrations For both ISSN and ISBN namespaces, URN registration practices within
track the evolution of ISO standardization without requiring them are expected to evolve along with the ISO ISBN and ISSN
resubmission of the templates or other formal IETF or IANA standards without requiring resubmission of the templates or other
registration update approval procedures. The subsections that follow formal IETF or IANA URN namespace registration update approval
clarify the relationship between the original URN namespace procedures. The subsections that follow clarify the relationship
registrations for ISBN and ISSN and the newly-registered templates between the original URN namespace registrations for ISBN and ISSN
that follow the principles of RFC 8141. Approval and registration of and the recently registered templates that follow the principles of
those new templates makes the older templates obsolete. RFC 8141. Approval and registration of those new templates made the
older templates obsolete.
2.1. ISBN URN Changes 2.1. ISBN URN Changes
The revised ISBN namespace reflects the latest version of the ISO The revised ISBN namespace reflects the latest version of the ISO
ISBN Standard, ISO 2108:2017 [ISO-ISBN-b]. The namespace allows for ISBN standard, ISO 2108:2017 [ISO-ISBN-b]. The namespace allows for
the use of both the old ten character ISBN numbers described in RFC the use of both the old ten-character ISBN numbers described in RFC
3187 and ISO 2108:1992 [ISO-ISBN-a] (formerly known as ISBN-10) and 3187 and ISO 2108:1992 [ISO-ISBN-a] (formerly known as ISBN-10) and
the 13 character identifiers introduced in ISO 2108:2005 [ISO-ISBN-c] the thirteen-character identifiers introduced in ISO 2108:2005
(formerly known as ISBN-13). [ISO-ISBN-c] (formerly known as ISBN-13).
For more details, review the new ISBN registration template and For more details, review the new ISBN registration template and
associated documentation [ISBN-Template]. associated documentation [ISBN-Template].
2.2. ISSN URN Changes 2.2. ISSN URN Changes
The updated ISSN namespace reflects the changes between the current The updated ISSN namespace reflects the changes between the current
ISSN standard [ISO-ISSN] and its predecessor on which RFC 3044 was ISSN standard [ISO-ISSN] and its predecessor on which RFC 3044 was
based. ISO 3297:2007 introduced the linking ISSN (ISSN-L), which is based. ISO 3297:2007 introduced the linking ISSN (ISSN-L), which is
designated for all media of a serial publication, irrespective of how designated for all media of a serial publication, irrespective of how
many there are. Traditional ISSN applies to single media only, such many there are. Traditional ISSN applies to a single medium only,
as printed version of a serial. such as the printed version of a serial.
For more details, review the new ISSN registration template and For more details, review the new ISSN registration template and
associated documentation [ISSN-Template]. associated documentation [ISSN-Template].
3. The Older Registration RFC for NBNs 3. The Older Registration RFC for NBNs
NBN is not a formal international standard or even a single NBN is not a formal international standard or even a single
identifier system, but an umbrella concept which covers all of the identifier system but an umbrella concept that covers all of the
identifier systems the adopting national libraries and their partners identifier systems the adopting national libraries and their partners
use to identify resources that do not have other identifiers. For use to identify resources that do not have other identifiers. For
instance, if a book received via legal deposit does not have an ISBN, instance, if a book received via legal deposit does not have an ISBN,
the national library gives it a local identifier. The NBN the national library gives it a local identifier. The NBN
specification provides simple means of expressing these local specification provides a simple means of expressing these local
identifiers so that they become globally unique URNs, such as identifiers so that they become globally unique URNs, such as
urn:nbn:fi-fe19981001. urn:nbn:fi-fe19981001.
In addition to the namespace registration itself, RFC 3188 provides In addition to the namespace registration itself, RFC 3188 provides
some generic information about NBNs and their use, and specifies the some generic information about NBNs and their use and specifies the
syntax of URN:NBNs. That syntax guarantees uniqueness by requiring syntax of URN:NBNs. That syntax guarantees uniqueness by requiring
the usage of country codes and institutional identifiers as a part of 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 the Namespace Specific String (NSS). When RFC 3188 is revised, it
template which revises the registration of the URN:NBN namespace. should be accompanied with a template that revises the registration
of the URN:NBN namespace.
4. Other Existing URN Registrations and RFCs 4. Other Existing URN Registrations and RFCs
The RFC Series and IANA Registry contain many URN namespace The RFC Series and the IANA URN Namespaces registry contain many URN
registrations in addition to those for which this document calls out namespace registrations in addition to those for which this document
explicit actions. In general, those existing registrations are still calls out explicit actions. In general, those existing registrations
appropriate but omit some information called for in RFC 8141 are still appropriate but omit some information called for in RFC
[RFC8141]. Reregistration with new templates is recommended, but not 8141 [RFC8141]. Reregistration with new templates is recommended but
required. Until and unless those registrations are updated as not required. Until and unless those registrations are updated as
provided for in RFC 8141, the existing registration templates should provided for in RFC 8141, the existing registration templates should
be read as not requiring or allowing any features that were not be read as not requiring or allowing any features that were not
allowed and specified by the earlier URN [RFC2141] and registration allowed and specified by the earlier URN [RFC2141] and registration
[RFC3406] specifications. [RFC3406] specifications.
5. Registration Examples 5. Registration Examples
For examples of registrations using the new model and for information For examples of registrations using the new model and for information
and help in understanding other parts of this document, review the and help in understanding other parts of this document, review the
new ISBN and ISSN registration templates and associated documentation new ISBN and ISSN registration templates [ISBN-Template]
in the IANA registry [ISBN-Template] [ISSN-Template]. [ISSN-Template] and associated documentation in the IANA URN
Namespaces registry.
6. IANA Considerations 6. IANA Considerations
IANA has completed updates for the registry entries for URN ISSN and IANA has completed updates for the registry entries for URN ISSN and
ISBN namespaces to reflect the new, RFC 8141-compliant, templates. ISBN namespaces to reflect the new templates that are compliant with
With respect to namespaces other than those listed above, when RFC 8141. With respect to namespaces other than those listed above,
registrations and templates are available that conform to the newer when registrations and templates are available that conform to the
rules, they may be substituted for the older ones. However, neither newer rules, they may be substituted for the older ones. However,
this document nor RFC 8141 supersedes any existing registrations neither this document nor RFC 8141 supersedes any existing
(those for ISBN and ISSN are superceded by the newly-registered registrations (those for ISBN and ISSN are superseded by the recently
templates). Therefore, IANA needs to be prepared to maintain a registered templates). Therefore, IANA needs to be prepared to
registry whose contents reflect old-style templates for some maintain a registry whose contents reflect old-style templates for
namespaces and the newer ones for others. some namespaces and the newer ones for others.
IANA should also note that the portions of the ISBN and ISSN IANA should also note that the portions of the ISBN and ISSN
registrations that point to ISO Standards are intended to identify registrations that point to ISO Standards are intended to identify
current versions (which may change) rather than only the versions current versions (which may change) rather than only the versions
that are active at the time this document is approved (see that are active at the time this document is approved (see
Section 2). That provision relies on ISO and the ISBN and ISSN Section 2). That provision relies on ISO TC 46 and its respective
Centres to maintain stability of URN references. registration authorities to maintain stability of URN references
discussed in this document.
7. Security Considerations 7. Security Considerations
While particular URN namespaces and their registrations might While particular URN namespaces and their registrations might
conceivably have security implications, this specification merely conceivably have security implications, this specification merely
specifies a transition of a set of namespace registrations and does specifies a transition of a set of namespace registrations and does
not have such implications. The security implications associated not have such implications. The security implications associated
with particular namespaces are expected to be listed in registration with particular namespaces are expected to be listed in registration
templates as specified in RFC 8141. templates as specified in RFC 8141.
8. Acknowledgements 8. References
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 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 develop the corresponding
template and from Gaelle Bequet, Pierre Godefroy, and Clement Oury of
the ISSN International Centre for similar refinements of the ISSN
discussion and template.
9. 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.
10. References
10.1. Normative References 8.1. Normative References
[RFC8141] Saint-Andre, P. and J. Klensin, "Uniform Resource Names [RFC8141] Saint-Andre, P. and J. Klensin, "Uniform Resource Names
(URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017, (URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017,
<http://www.rfc-editor.org/info/rfc8141>. <https://www.rfc-editor.org/info/rfc8141>.
10.2. Informative References 8.2. Informative References
[ANSI-SICI] [ANSI-SICI]
ANSI/NISO, "Serial Item and Contribution Identifier, ANSI/ ANSI/NISO, "Serial Item and Contribution Identifier
NISO Z39.56-1996 (Version 2)", 1996. (SICI)", ANSI/NISO Z39.56-1996 (Version 2), August 1996.
[IANA-Namespace-Registry] [IANA-URN] IANA, "Uniform Resource Names (URN) Namespaces",
IANA, "Uniform Resource Names (URN) Namespaces", 2017, <http://www.iana.org/assignments/urn-namespaces>.
<http://www.iana.org/assignments/urn-namespaces/
urn-namespaces.xhtml>.
[ISBN-Template] [ISBN-Template]
ISBN International Centre, "Namespace Registration for ISBN International Agency, "Namespace Registration for
International Standard Book Number (ISBN) ISO 2108:2017", International Standard Book Number (ISBN) ISO 2108:2017",
June 2017, <https://www.iana.org/assignments/urn-formal/ June 2017,
isbn>. <https://www.iana.org/assignments/urn-formal/isbn>.
[ISO-ISBN-a] [ISO-ISBN-a]
ISO, "Information and documentation - The International ISO, "Information and documentation - International
Standard Book Number (ISBN)", ISO 2108:1992, 1992. Standard Book Number (ISBN)", ISO 2108:1992, 1992.
[ISO-ISBN-b] [ISO-ISBN-b]
ISO, "Information and documentation - The International ISO, "Information and documentation - International
Standard Book Number (ISBN)", ISO 2108:2017, 2017. Standard Book Number (ISBN)", ISO 2108:2017, 2017.
Note to RFC Editor: As of early July 2017, the 2017
version is awaiting publication, but the ISBN
International Centre 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-ISBN-c]
ISO, "Information and documentation - The International ISO, "Information and documentation - International
Standard Book Number (ISBN)", ISO 2108:2005, 2005. Standard Book Number (ISBN)", ISO 2108:2005, 2005.
[ISO-ISSN] [ISO-ISSN] ISO, "Information and documentation - International
ISO, "Information and documentation - International Standard Serial Number (ISSN)", ISO 3297:2007, 2007.
standard serial number (ISSN)", ISO 3297:2007, 2007.
[ISSN-Template] [ISSN-Template]
ISSN International Centre, "Namespace Registration for ISSN International Centre, "Namespace Registration for
International Standard Serial Number (ISSN) and Linking International Standard Serial Number (ISSN) and Linking
ISSN (ISSN-L) based on ISO 3297:2007", June 2017, ISSN (ISSN-L) based on ISO 3297:2007", June 2017,
<https://www.iana.org/assignments/urn-formal/issn>. <https://www.iana.org/assignments/urn-formal/issn>.
[RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141, [RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141,
May 1997, <http://www.rfc-editor.org/info/rfc2141>. May 1997, <https://www.rfc-editor.org/info/rfc2141>.
[RFC2288] Lynch, C., Preston, C., and R. Daniel, "Using Existing [RFC2288] Lynch, C., Preston, C., and R. Daniel, "Using Existing
Bibliographic Identifiers as Uniform Resource Names", Bibliographic Identifiers as Uniform Resource Names",
RFC 2288, DOI 10.17487/RFC2288, February 1998, RFC 2288, DOI 10.17487/RFC2288, February 1998,
<http://www.rfc-editor.org/info/rfc2288>. <https://www.rfc-editor.org/info/rfc2288>.
[RFC2611] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, [RFC2611] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
"URN Namespace Definition Mechanisms", BCP 33, RFC 2611, "URN Namespace Definition Mechanisms", BCP 33, RFC 2611,
DOI 10.17487/RFC2611, June 1999, DOI 10.17487/RFC2611, June 1999,
<http://www.rfc-editor.org/info/rfc2611>. <https://www.rfc-editor.org/info/rfc2611>.
[RFC3044] Rozenfeld, S., "Using The ISSN (International Serial [RFC3044] Rozenfeld, S., "Using The ISSN (International Serial
Standard Number) as URN (Uniform Resource Names) within an Standard Number) as URN (Uniform Resource Names) within an
ISSN-URN Namespace", RFC 3044, DOI 10.17487/RFC3044, ISSN-URN Namespace", RFC 3044, DOI 10.17487/RFC3044,
January 2001, <http://www.rfc-editor.org/info/rfc3044>. January 2001, <https://www.rfc-editor.org/info/rfc3044>.
[RFC3187] Hakala, J. and H. Walravens, "Using International Standard [RFC3187] Hakala, J. and H. Walravens, "Using International Standard
Book Numbers as Uniform Resource Names", RFC 3187, Book Numbers as Uniform Resource Names", RFC 3187,
DOI 10.17487/RFC3187, October 2001, DOI 10.17487/RFC3187, October 2001,
<http://www.rfc-editor.org/info/rfc3187>. <https://www.rfc-editor.org/info/rfc3187>.
[RFC3188] Hakala, J., "Using National Bibliography Numbers as [RFC3188] Hakala, J., "Using National Bibliography Numbers as
Uniform Resource Names", RFC 3188, DOI 10.17487/RFC3188, Uniform Resource Names", RFC 3188, DOI 10.17487/RFC3188,
October 2001, <http://www.rfc-editor.org/info/rfc3188>. October 2001, <https://www.rfc-editor.org/info/rfc3188>.
[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
"Uniform Resource Names (URN) Namespace Definition "Uniform Resource Names (URN) Namespace Definition
Mechanisms", RFC 3406, DOI 10.17487/RFC3406, October 2002, Mechanisms", RFC 3406, DOI 10.17487/RFC3406, October 2002,
<http://www.rfc-editor.org/info/rfc3406>. <https://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 6 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
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.
A.8. Changes from version -07 (2017-05-09) to -08 Acknowledgements
o Inserted references for the new, updated, registrations for ISBN This document draws heavily on discussions in the IETF URNbis Working
and ISSN. 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 documents were prepared by Pierre Godefroy,
Juha Hakala, Alfred Hoenes, and Maarit Huttunen.
o Corrected or completed several references. The current specification benefits significantly from a careful
reading and suggestions for editorial changes by Peter Saint-Andre;
from considerable work by Stella Griffiths of the ISBN International
Agency to refine the ISBN discussion and develop the corresponding
template; and from Gaelle Bequet, Pierre Godefroy, and Clement Oury
of the ISSN International Centre for similar refinements of the ISSN
discussion and template.
o Many editorial changes, including being clear about actions Contributors
already completed (including removing various temporary notes) and
better alignment of the I-D with RFC Series stylistic conventions.
o With the exception of the one at the beginning of this appendix, Alfred Hoenes was the editor and co-author of two of the documents
remaining instructions and advice to the RFC Editor have been from which this one is, in part, derived. This document would not
converted to notes in the XML source. have been possible without his contributions.
Authors' Addresses Authors' Addresses
John C Klensin John C. Klensin
1770 Massachusetts Ave, Ste 322 1770 Massachusetts Ave, Ste 322
Cambridge, MA 02140 Cambridge, MA 02140
USA United States of America
Phone: +1 617 245 1457 Phone: +1 617 245 1457
Email: john-ietf@jck.com Email: john-ietf@jck.com
Juha Hakala Juha Hakala
The National Library of Finland The National Library of Finland
P.O. Box 15, Helsinki University P.O. Box 15, Helsinki University
Helsinki, MA FIN-00014 Helsinki, MA FIN-00014
Finland Finland
 End of changes. 60 change blocks. 
256 lines changed or deleted 142 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/