draft-ietf-urnbis-ns-reg-transition-03.txt   draft-ietf-urnbis-ns-reg-transition-04.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: February 26, 2015 August 25, 2014 Expires: August 20, 2015 February 16, 2015
Uniform Resource Name (URN) Namespace Registration Transition Uniform Resource Name (URN) Namespace Registration Transition
draft-ietf-urnbis-ns-reg-transition-03 draft-ietf-urnbis-ns-reg-transition-04
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
in [[RFC 3406bis]]. That document adopts a different model. This in [[RFC 2141bis]]. That document adopts a different model. This
document specifies IANA instructions to adapt selected existing document specifies IANA instructions to adapt selected existing
registrations to the new model. It also obsoletes some previous RFCs registrations to the new model. It also obsoletes some previous RFCs
to eliminate any ambiguity about the status of new templates and to eliminate any ambiguity about the status of new templates and
updated registrations. updated 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 February 26, 2015. This Internet-Draft will expire on August 20, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 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
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 . . . . . . . . . . . . . . . . . . . . . . . . 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. Other existing URN registrations and RFCs . . . . . . . . . . 4 3. Other existing URN registrations and RFCs . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . 6 8.2. Informative References . . . . . . . . . . . . . . . . . 6
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 7 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 7
A.1. Changes from version -00 to -01 . . . . . . . . . . . . . 7 A.1. Changes from version -00 to -01 . . . . . . . . . . . . . 7
A.2. Changes from version -01 to -02 . . . . . . . . . . . . . 7 A.2. Changes from version -01 to -02 . . . . . . . . . . . . . 7
A.3. Changes from version -02 to -03 . . . . . . . . . . . . . 7 A.3. Changes from version -02 to -03 . . . . . . . . . . . . . 7
A.4. Changes from version -03 to -04 . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
[[CREF1: RFC Editor: Please note that mentions of "RFC 3406bis" in [[CREF1: RFC Editor: Please note that mentions of "[[RFC 2141bis]]"
this I-D are defined as an Entity in the XML. They should be in this I-D are defined as an Entity in the XML with the brackets
corrected to show the actual RFC number before publication.]] 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, [[CREF2: Note in draft: This document has been written in RFC form,
i.e., assuming that it and 3406bis have been approved. That style of 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 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 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 by the WG and the IETF, but lowers the risk for errors or other
surprises during the RFC editing process.]] surprises during the RFC editing process.]]
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 can
accommodate existing identifier systems. RFC 2288 [RFC2288] accommodate existing identifier systems. RFC 2288 [RFC2288]
investigated the feasibility of using three identifiers (ISBN, ISSN investigated the feasibility of using three identifiers (ISBN, ISSN
skipping to change at page 3, line 19 skipping to change at page 3, line 21
Number) [RFC3187], and ISSN (International Standard Serial Number) Number) [RFC3187], and ISSN (International Standard Serial Number)
[RFC3044]. [RFC3044].
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"), that could occur as a result. Those
potential problems included the possibility of the same name being potential problems included the possibility of the same name being
used to identify different namespaces with different rules. The used to identify different namespaces with different rules. The
requirements have now been changed [RFC3406bis] to adopt a different requirements have now been changed [RFC2141bis] to adopt a different
model that focuses more on encouraging registration of all namespaces model that focuses more on encouraging registration of all namespaces
that follow the formal namespace syntax, with as much information that follow the formal namespace syntax, with as much information
collected as possible consistent with that goal. This document collected as possible consistent with that goal. This document
specifies IANA instructions to adapt selected existing registrations specifies IANA instructions to adapt selected existing registrations
to the new model and obsoletes the separate RFCs that specify the to the new model and obsoletes the separate RFCs that specify the
namespaces for International Standard Serial Numbers (ISSNs) namespaces for International Standard Serial Numbers (ISSNs)
[RFC3044] and International Standard Book Numbers (ISBNs) [RFC3187] [RFC3044] and International Standard Book Numbers (ISBNs) [RFC3187]
to eliminate any ambiguity about the status of new templates and to eliminate any ambiguity about the status of new templates and
updated registrations. updated registrations.
skipping to change at page 3, line 42 skipping to change at page 3, line 44
separately. NBN is not a formal international standard and RFC 3188 separately. NBN is not a formal international standard and RFC 3188
is the only formal document which specifies its scope. The intention is the only formal document which specifies its scope. The intention
is to modernize the existing namespace registration so that it is to modernize the existing namespace registration so that it
specifies the identifier and provides examples of its use, while the specifies the identifier and provides examples of its use, while the
actual namespace registration will be done according to the new actual namespace registration will be done according to the new
practice. practice.
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 (RFC 3044)
and ISBNs (RFC 3187) should be identified as "Historic" immediately and ISBNs (RFC 3187) should be identified as "Historic" after this
after this document is approved and the new registration templates document is approved and immediately after the new registration
for those namespaces are submitted and incorporated into the URN templates for those namespaces are submitted and incorporated into
Namespace registry by IANA. the URN Namespace registry by IANA.
[[CREF3: Note in draft: The more information that can be supplied in [[CREF3: Note in draft: The more information that can be supplied in
the template or references from it, the better. But, if there is the template or references from it, the better. But, if there is
information in the now-expired Internet-Drafts (draft-ietf-urnbis- information in the now-expired Internet-Drafts (draft-ietf-urnbis-
rfc3187bis-isbn-urn, draft-ietf-urnbis-rfc3044bis-issn-urn) that rfc3187bis-isbn-urn, draft-ietf-urnbis-rfc3044bis-issn-urn) that
should be captured somewhere and that doesn't fit naturally in the should be captured somewhere and that doesn't fit naturally in the
template, the discussion below is probably a reasonable place to put template, the discussion below is probably a reasonable place to put
it.]] it.]]
[[CREF4: Similarly, if special transition discussions are needed for [[CREF4: Similarly, if special transition discussions are needed for
other URN namespaces registered prior to the intended transition, other URN namespaces registered prior to the intended transition,
skipping to change at page 4, line 27 skipping to change at page 4, line 29
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. registration update approval procedures.
2.1. ISBN URN Changes 2.1. ISBN URN Changes
The revised ISBN namespace reflects the updated version of the ISO The revised ISBN namespace reflects the updated version of the ISO
Standard for ISBNs, ISO 2108:2005 [ISO-ISBN-b]. The namespace allows Standard for ISBNs, ISO 2108:2005 [ISO-ISBN-b]. The namespace allows
for the use of both the ten character numbers described in RFC 3187 for the use of both the ten character numbers described in RFC 3187
and the earlier ISO 2108:1992 [ISO-ISBN-a] (known as ISBN-10), as and the earlier ISO 2108:1992 [ISO-ISBN-a] (known as ISBN-10), as
well as the expanded ones of the revised standard (known as ISBN-13). well as the expanded ones specified in the revised and updated
standard (known as ISBN-13).
2.2. ISSN URN Changes 2.2. ISSN URN Changes
The ISSN namespace is also updated to reflect changes between the The ISSN namespace is also updated to reflect changes between the
ISSN Standard when RFC 3044 was written and the newest, 2007 version ISSN Standard when RFC 3044 was written and the newest, 2007 version
[ISO-ISSN]. [ISO-ISSN].
3. Other existing URN registrations and RFCs 3. Other existing URN registrations and RFCs
The RFC Series and IANA Registry contain many URN definitions in The RFC Series and IANA Registry contain many URN definitions in
addition to those for which this document calls out explicit actions. addition to those for which this document calls out explicit actions.
In general, those existing registrations are still appropriate but In general, those existing registrations are still appropriate but
omit some information called for in RFC 3406bis. Until and unless omit some information called for in [[RFC 2141bis]]. Until and
those registrations are updated as provided for in RFC 3406bis, the unless those registrations are updated as provided for in [[RFC
existing registration templates should be read as not requiring any 2141bis]], the existing registration templates should be read as not
features not specified by the earlier URN [RFC2141] and registration requiring or allowing any features that were not allowed and
[RFC3406] specifications. specified by the earlier URN [RFC2141] and registration [RFC3406]
specifications.
4. IANA Considerations 4. IANA Considerations
IANA is requested to update the registry entries for URN ISSNs, IANA is requested to update the registry entries for URN ISSN, ISBN,
ISBNs, and NRNs to reflect the new, RFC 3406bis-complaint templates and NRN namespaces to reflect the new, [[RFC 2141bis]]-complaint
as soon as they are available and to no longer reference the now- templates as soon as they are available and to no longer reference
historic RFCs. With respect to namespaces other than those listed the now-historic RFCs. With respect to namespaces other than those
above, registrations and templates conforming to the newer rules may listed above, registrations and templates conforming to the newer
be substituted for the older ones when they are available. However, rules may be substituted for the older ones when they are available.
neither this document nor RFC 3406bis supercedes existing However, neither this document nor [[RFC 2141bis]] supercedes
registrations other than those listed above. Therefore, IANA needs existing registrations other than those listed above. Therefore,
to be prepared to maintain a registry whose contents reflect old- IANA needs to be prepared to maintain a registry whose contents
style templates for some namespaces and the newer ones for others. reflect old-style templates for some namespaces and the newer ones
for others.
IANA should also note that the portions of the registrations that IANA should also note that the portions of the registrations that
point to ISO Standards are intended to identify current versions point to ISO Standards are intended to identify current versions
(which may change) rather than only the versions that are active at (which may change) rather than only the versions that are active at
the time this document is approved (see Section 2). the time this document is approved (see Section 2).
5. Security Considerations 5. 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 pair of registration procedures and does specifies a transition of a pair of registration procedures 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 3406bis. templates as specified in [[RFC 2141bis]].
6. Acknowledgements 6. 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
skipping to change at page 6, line 4 skipping to change at page 6, line 6
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. suggestions for editorial changes by Peter Saint-Andre.
7. Contributors 7. 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.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC3406bis] [RFC2141bis]
Saint-Andre, P., Ed., "Uniform Resource Name (URN) Saint-Andre, P. and J. Klensin, "Uniform Resource Name
Namespace Definition Mechanisms", February 2014, (URN) Syntax", February 2015,
<https://datatracker.ietf.org/doc/draft-ietf-urnbis- <https://datatracker.ietf.org/doc/draft-ietf-urnbis-
rfc3406bis-urn-ns-reg/>. rfc2141bis-urn/>.
8.2. Informative References 8.2. Informative References
[ISO-ISBN-a] [ISO-ISBN-a]
ISO, "Information and documentation - The International ISO, "Information and documentation - The International
Standard Book Number (ISBN)", ISO 2180:1992, 1992. Standard Book Number (ISBN)", ISO 2180: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 2180:2005, 2005. Standard Book Number (ISBN)", ISO 2180:2005, 2005.
skipping to change at page 7, line 32 skipping to change at page 7, line 32
A.3. Changes from version -02 to -03 A.3. Changes from version -02 to -03
o Updated to prevent expiration o Updated to prevent expiration
o New text to allow for other already-registered namespaces and to o New text to allow for other already-registered namespaces and to
better explain relationships. better explain relationships.
o Some small editorial changes. 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.
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
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
Email: juha.hakala@helsinki.fi Email: juha.hakala@helsinki.fi
 End of changes. 21 change blocks. 
38 lines changed or deleted 51 lines changed or added

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