draft-ietf-urnbis-ns-reg-transition-07.txt   draft-ietf-urnbis-ns-reg-transition-08.txt 
URNbis J. Klensin URNbis J. Klensin
Internet-Draft Internet-Draft
Obsoletes: 3044, 3187 (if approved) J. Hakala Obsoletes: 3044, 3187 (if approved) J. Hakala
Intended status: Standards Track The National Library of Finland Intended status: Standards Track The National Library of Finland
Expires: November 10, 2017 May 9, 2017 Expires: January 2, 2018 July 1, 2017
Uniform Resource Name (URN) Namespace Registration Transition Uniform Resource Name (URN) Namespace Registration Transition
draft-ietf-urnbis-ns-reg-transition-07 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 that status of relevant older namespaces. This document clarifies the status of relevant older
RFCs and advises IANA about selected existing registrations. RFCs and confirms and documents advice to IANA about selected
existing registrations.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 10, 2017. This Internet-Draft will expire on January 2, 2018.
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 (http://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
skipping to change at page 2, line 15 skipping to change at page 2, line 16
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Obsoleting Older Registration RFCs for ISSNs and ISBNs . . . 3 2. Obsoleting Older Registration RFCs for ISSNs and ISBNs . . . 3
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. Obsoleting older registration RFC for NBNs . . . . . . . . . 4 3. The Older Registration RFC for NBNs . . . . . . . . . . . . . 4
4. Other existing URN registrations and RFCs . . . . . . . . . . 5 4. Other Existing URN Registrations and RFCs . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 5. Registration Examples . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 7. Security Considerations . . . . . . . . . . . . . . . . . . . 6
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6
9.1. Normative References . . . . . . . . . . . . . . . . . . 6 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
9.2. Informative References . . . . . . . . . . . . . . . . . 6 10.1. Normative References . . . . . . . . . . . . . . . . . . 6
10.2. Informative References . . . . . . . . . . . . . . . . . 6
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 8 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 8
A.1. Changes from version -00 to -01 . . . . . . . . . . . . . 8 A.1. Changes from version -00 to -01 . . . . . . . . . . . . . 8
A.2. Changes from version -01 to -02 . . . . . . . . . . . . . 8 A.2. Changes from version -01 to -02 . . . . . . . . . . . . . 8
A.3. Changes from version -02 to -03 . . . . . . . . . . . . . 9 A.3. Changes from version -02 to -03 . . . . . . . . . . . . . 9
A.4. Changes from version -03 to -04 . . . . . . . . . . . . . 9 A.4. Changes from version -03 to -04 . . . . . . . . . . . . . 9
A.5. Changes from version -04 to -05 . . . . . . . . . . . . . 9 A.5. Changes from version -04 to -05 . . . . . . . . . . . . . 9
A.6. Changes from version -05 to -06 . . . . . . . . . . . . . 9 A.6. Changes from version -05 to -06 . . . . . . . . . . . . . 9
A.7. Changes from version -06 (2016-02-07) to -07 (2017-05-09) 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 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 can that it was important to demonstrate that the URN syntax could
accommodate existing identifier systems. RFC 2288 [RFC2288] proved 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 in 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 have subsequently been registered for ISBN and ISSN as URN Namespaces were subsequently registered for ISBN [RFC3187] and
well as for a fairly large collection of other identifiers including ISSN [RFC3044] as well as for a fairly large collection of other
National Bibliography Number (NBN) [RFC3188]. The comprehensive list identifiers including National Bibliography Number (NBN) [RFC3188].
can be found in the IANA registry [IANA-Namespace-Registry] (see also The comprehensive list can be found in the IANA registry
Section 4). [IANA-Namespace-Registry] (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
standard has not gained broad international acceptance and has not SICI Standard has not gained broad international acceptance and has
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 Uniform Resource Name
(URN) namespaces [RFC3406] required IETF Consensus for formal (URN) namespaces [RFC3406] required IETF Consensus for formal
namespaces. That requirement discouraged some registrations and namespaces. That requirement discouraged some registrations and
increased the risk for problems, including use of names without increased the risk for problems, including use of names without
registration ("squatting"), that could occur as a result. Those registration ("squatting"). Those potential problems included the
potential problems included the possibility of the same name being possibility of the same name being used to identify different
used to identify different namespaces with different rules. The namespaces with different rules. The requirements have now been
requirements have now been changed in RFC 8141 [RFC8141] to adopt a changed in RFC 8141 [RFC8141] to adopt a different model that focuses
different model that focuses more on encouraging registration of all more on encouraging registration of all namespaces that follow the
namespaces that follow the formal namespace syntax, with as much formal namespace syntax, with as much information collected as
information collected as possible consistent with that goal. possible consistent with that goal.
Therefore this document does the following: Therefore this document does the following:
o Specifies IANA instructions to adapt selected existing o Describes the instructions developed with IANA to adapt selected
registrations to the new model. existing registrations to the new model. Those registration
updates have been completed for ISBN and ISSN 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 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 mentioned herein. 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 (RFC 3044) The existing RFCs that describe URN namespaces for ISSNs [RFC3044]
and ISBNs (RFC 3187) should be identified as "Historic" after this and ISBNs [RFC3187] should be identified as "Historic" after this
document is approved and immediately after the new registration document is approved. The new registration templates for those
templates for those namespaces are submitted and incorporated into namespaces have already been submitted and incorporated into the URN
the URN Namespace registry by IANA. Namespace registry by IANA.
The updated templates reflect not only 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
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 URNs, it is intended that the registrations
track the evolution of ISO standardization without requiring track the evolution of ISO standardization without requiring
resubmission of the templates or other formal IETF or IANA resubmission of the templates or other formal IETF or IANA
registration update approval procedures. The subsections that follow registration update approval procedures. The subsections that follow
clarify the relationship between the original URN namespace clarify the relationship between the original URN namespace
registrations for ISBN and ISSN and new templates being registered registrations for ISBN and ISSN and the newly-registered templates
that follow the principles of RFC 8141. Approval and registration of that follow the principles of RFC 8141. Approval and registration of
those new templates makes the older templates obsolete and RFCs 3044 those new templates makes the older templates obsolete.
and 3187 Historic.
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 13 character identifiers introduced in ISO 2108:2005 [ISO-ISBN-c]
(formerly known as ISBN-13). (formerly known as ISBN-13).
For information and help in understanding other parts of this For more details, review the new ISBN registration template and
document, review the new ISBN registration template [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 single media only, such
as printed version of a serial. as printed version of a serial.
For information and help in understanding other parts of this For more details, review the new ISSN registration template and
document, review the new ISSN registration template [ISSN-Template]. associated documentation [ISSN-Template].
3. Obsoleting 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 identifier system, but an umbrella concept which covers all of the
identifier systems the national libraries and their partners use to identifier systems the adopting national libraries and their partners
identify resources which do not have other identifier. For instance, use to identify resources that do not have other identifiers. For
if a book received via legal deposit does not have an ISBN, the instance, if a book received via legal deposit does not have an ISBN,
national library gives it a local identifier. NBN specification the national library gives it a local identifier. The NBN
provides simple means of expressing these local identifiers so that specification provides simple means of expressing these local
they become globally unique URNs, such as urn:nbn:fi-fe19981001. identifiers so that they become globally unique URNs, such as
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 which guarantees uniqueness by requiring the usage syntax of URN:NBNs. That syntax guarantees uniqueness by requiring
of country codes and institutional identifiers as a part of the NSS. 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
When RFC 3188 is revised, it should be accompanied with a template template which revises the registration of the URN:NBN namespace.
which 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 IANA Registry contain many URN namespace
registrations in addition to those for which this document calls out registrations in addition to those for which this document calls out
explicit actions. In general, those existing registrations are still explicit actions. In general, those existing registrations are still
appropriate but omit some information called for in RFC 8141 appropriate but omit some information called for in RFC 8141
[RFC8141]. Reregistration with new templates is recommended, but not [RFC8141]. Reregistration with new templates is recommended, but not
required. Until and unless those registrations are updated as 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. IANA Considerations 5. Registration Examples
IANA is requested to update the registry entries for URN ISSN, ISBN, For examples of registrations using the new model and for information
and NBN namespaces to reflect the new, RFC 8141-compliant templates and help in understanding other parts of this document, review the
as soon as they are available and to no longer reference the now- new ISBN and ISSN registration templates and associated documentation
historic RFCs. With respect to namespaces other than those listed in the IANA registry [ISBN-Template] [ISSN-Template].
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 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 6. IANA Considerations
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).
6. Security Considerations IANA has completed updates for the registry entries for URN ISSN and
ISBN namespaces to reflect the new, RFC 8141-compliant, templates.
With respect to namespaces other than those listed above, when
registrations and templates are available that conform to the newer
rules, they may be substituted for the older ones. However, neither
this document nor RFC 8141 supersedes any existing registrations
(those for ISBN and ISSN are superceded by the newly-registered
templates). Therefore, IANA needs to be prepared to maintain a
registry whose contents reflect old-style templates for some
namespaces and the newer ones for others.
IANA should also note that the portions of the ISBN and ISSN
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). That provision relies on ISO and the ISBN and ISSN
Centres to maintain stability of URN references.
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.
7. Acknowledgements 8. Acknowledgements
This document draws heavily on discussions in the IETF URNbis Working This document draws heavily on discussions in the IETF URNbis Working
Group in the second and third quarters of 2013, particularly during Group in the second and third quarters of 2013, particularly during
IETF 87 in August 2013, and on informal discussions during the 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 plenary meeting of ISO TC 46 in June 2013. The efforts of those who
participated in those discussions are greatly appreciated. It also participated in those discussions are greatly appreciated. It also
draws on internet-drafts that were developed to update the older draws on internet-drafts that were developed to update the older
registrations before that approach was replaced by the new extended registrations before that approach was replaced by the new extended
template model. Those drafts were prepared by Pierre Godefroy, Juha template model. Those drafts were prepared by Pierre Godefroy, Juha
Hakala, Alfred Hoenes, and Maarit Huttunen. Hakala, Alfred Hoenes, and Maarit Huttunen.
The current draft benefits significantly from a careful reading and The current draft benefits significantly from a careful reading and
suggestions for editorial changes by Peter Saint-Andre and from suggestions for editorial changes by Peter Saint-Andre and from
considerable work by Stella Griffiths of the ISBN international considerable work by Stella Griffiths of the ISBN international
Centre to refine the ISBN discussion and from Pierre Godefroy and Centre to refine the ISBN discussion and develop the corresponding
Clement Oury of the ISSN International Centre for similar refinements template and from Gaelle Bequet, Pierre Godefroy, and Clement Oury of
of the ISSN discussion. the ISSN International Centre for similar refinements of the ISSN
[[CREF1: RFC Editor and IANA: Please note that "Centre" is the discussion and template.
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 you to use that information.]]
8. Contributors 9. Contributors
Alfred Hoenes was the editor and co-author of two of the documents 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 from which this one is, in part, derived. This document would not
have been possible without his contributions. have been possible without his contributions.
9. References 10. References
9.1. Normative References 10.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>. <http://www.rfc-editor.org/info/rfc8141>.
9.2. Informative References 10.2. Informative References
[ANSI-SICI] [ANSI-SICI]
ANSI/NISO, "Serial Item and Contribution Identifier, ANSI/ ANSI/NISO, "Serial Item and Contribution Identifier, ANSI/
NISO Z39.56-1996 (Version 2)", 1996. NISO Z39.56-1996 (Version 2)", 1996.
[IANA-Namespace-Registry] [IANA-Namespace-Registry]
IANA, "Uniform Resource Names (URN) Namespaces", 2016, IANA, "Uniform Resource Names (URN) Namespaces", 2017,
<http://www.iana.org/assignments/urn-namespaces/ <http://www.iana.org/assignments/urn-namespaces/
urn-namespaces.xhtml>. urn-namespaces.xhtml>.
[ISBN-Template] [ISBN-Template]
ISBN International Centre, "... to be supplied ...", 2017, ISBN International Centre, "Namespace Registration for
<http://www.iana.org/???>. International Standard Book Number (ISBN) ISO 2108:2017",
June 2017, <https://www.iana.org/assignments/urn-formal/
RFC Editor: please be sure the correct IANA links are isbn>.
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-ISBN-a]
ISO, "Information and documentation - The International ISO, "Information and documentation - The 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 - The International
Standard Book Number (ISBN)", ISO 2108:2017, 2017. Standard Book Number (ISBN)", ISO 2108:2017, 2017.
Note to RFC Editor: As of early March, the 2017 version is Note to RFC Editor: As of early July 2017, the 2017
awaiting publication, but the ISBN International Center version is awaiting publication, but the ISBN
strongly prefers that we reference it and not some earlier International Centre strongly prefers that we reference it
version. If this note is still present when the document and not some earlier version. If this note is still
is otherwise ready for AUTH48, please see present when the document is otherwise ready for AUTH48,
https://www.iso.org/standard/65483.html and discuss status please see https://www.iso.org/standard/65483.html and
with the authors. discuss status with the authors.
[ISO-ISBN-c] [ISO-ISBN-c]
ISO, "Information and documentation - The International ISO, "Information and documentation - The 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)ISO 3297:2007", 2017, ISSN (ISSN-L) based on ISO 3297:2007", June 2017,
<http://www.iana.org/???>. <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, <http://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>. <http://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,
skipping to change at page 8, line 40 skipping to change at page 8, line 35
"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>. <http://www.rfc-editor.org/info/rfc3406>.
Appendix A. Change Log Appendix A. Change Log
RFC Editor: Please remove this appendix. RFC Editor: Please remove this appendix.
A.1. Changes from version -00 to -01 A.1. Changes from version -00 to -01
o Modified the introduction to Section 2 and Section 5 to make it o Modified the introduction to Section 2 and Section 6 to make it
clear that registry update procedures should not be required to clear that registry update procedures should not be required to
keep the registrations current with ISO Standard reaffirmations or keep the registrations current with ISO Standard reaffirmations or
replacments. replacments.
o Many editorial changes to improve readability and clarity. o Many editorial changes to improve readability and clarity.
A.2. Changes from version -01 to -02 A.2. Changes from version -01 to -02
o Several small editorial changes and clarifications suggested by o Several small editorial changes and clarifications suggested by
Peter Saint-Andre. Peter Saint-Andre.
skipping to change at page 9, line 35 skipping to change at page 9, line 35
o Updated references. o Updated references.
A.6. Changes from version -05 to -06 A.6. Changes from version -05 to -06
o Reissued to keep draft alive; some editorial updates but no o Reissued to keep draft alive; some editorial updates but no
substantive changes. substantive changes.
o Updated references. o Updated references.
A.7. Changes from version -06 (2016-02-07) to -07 (2017-05-09) 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 o Removed old CREFs. Added a new one, but only as a forward-looking
note to the RFC Editor. note to the RFC Editor.
o Moved expansions of ISBN, ISSN, SICI, and NBN to the first uses of o Moved expansions of ISBN, ISSN, SICI, and NBN to the first uses of
those terms, after which the abbreviations are used exclusively. those terms, after which the abbreviations are used exclusively.
o Removed text that made promises about the content and schedule for o Removed text that made promises about the content and schedule for
RFC 3188bis. RFC 3188bis.
skipping to change at page 10, line 20 skipping to change at page 10, line 20
versions of those templates. versions of those templates.
o Updated references, including the reference to the recently- o Updated references, including the reference to the recently-
published RFC 8141 (aka 2141bis). published RFC 8141 (aka 2141bis).
o Added placeholder references for the registrations of the new IANA o Added placeholder references for the registrations of the new IANA
templates. templates.
o Corrected minor typographical errors. o Corrected minor typographical errors.
A.8. Changes from version -07 (2017-05-09) to -08
o Inserted references for the new, updated, registrations for ISBN
and ISSN.
o Corrected or completed several references.
o Many editorial changes, including being clear about actions
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,
remaining instructions and advice to the RFC Editor have been
converted to notes in the XML source.
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 USA
Phone: +1 617 245 1457 Phone: +1 617 245 1457
Email: john-ietf@jck.com Email: john-ietf@jck.com
 End of changes. 42 change blocks. 
115 lines changed or deleted 133 lines changed or added

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