draft-ietf-urnbis-ns-reg-transition-05.txt   draft-ietf-urnbis-ns-reg-transition-06.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 11, 2016 August 10, 2015 Expires: August 10, 2016 February 7, 2016
Uniform Resource Name (URN) Namespace Registration Transition Uniform Resource Name (URN) Namespace Registration Transition
draft-ietf-urnbis-ns-reg-transition-05 draft-ietf-urnbis-ns-reg-transition-06
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 2141bis]]. 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
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 11, 2016. This Internet-Draft will expire on August 10, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 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
skipping to change at page 2, line 30 skipping to change at page 2, line 30
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 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 A.4. Changes from version -03 to -04 . . . . . . . . . . . . . 7
A.5. Changes from version -04 to -05 . . . . . . . . . . . . . 8 A.5. Changes from version -04 to -05 . . . . . . . . . . . . . 8
A.6. Changes from version -05 to -06 . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
[[CREF1: RFC Editor: Please note that mentions of "[[RFC 2141bis]]" [[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 in this I-D are defined as an Entity in the XML with the brackets
providing extra emphasis. Before publication, they should be providing extra emphasis. Before publication, they should be
corrected, and the brackets removed, to show the actual RFC number.]] 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,
skipping to change at page 3, line 13 skipping to change at page 3, line 14
and SICI) as URNs, with positive results; however, it did not and SICI) as URNs, with positive results; however, it did not
formally register corresponding URN namespaces. This was in part due formally register corresponding URN namespaces. This was in part due
to the still evolving process to formalize criteria for namespace 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 in 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 NBN (National URN Namespaces have subsequently been registered for NBN (National
Bibliography Number) [RFC3188], ISBN (International Standard Book Bibliography Number) [RFC3188], ISBN (International Standard Book
Number) [RFC3187], and ISSN (International Standard Serial Number) Number) [RFC3187], and ISSN (International Standard Serial Number)
[RFC3044]. [RFC3044] as well as for a fairly large collection of other
namespaces [IANA-Namespace-Registry].
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 [RFC2141bis] 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
skipping to change at page 5, line 28 skipping to change at page 5, line 28
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 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 2141bis]]. 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
skipping to change at page 6, line 11 skipping to change at page 6, line 11
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
[RFC2141bis] [RFC2141bis]
Saint-Andre, P. and J. Klensin, "Uniform Resource Name Saint-Andre, P. and J. Klensin, "Uniform Resource Name
(URN) Syntax", June 2015, (URN) Syntax", February 2016,
<https://datatracker.ietf.org/doc/draft-ietf-urnbis- <https://datatracker.ietf.org/doc/draft-ietf-urnbis-
rfc2141bis-urn/>. rfc2141bis-urn/>.
8.2. Informative References 8.2. Informative References
[IANA-Namespace-Registry]
IANA, "Uniform Resource Names (URN) Namespaces", 2016,
<http://www.iana.org/assignments/urn-namespaces/
urn-namespaces.xhtml>.
[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.
[ISO-ISSN] [ISO-ISSN]
ISO, "Information and documentation - International ISO, "Information and documentation - International
skipping to change at page 8, line 11 skipping to change at page 8, line 11
and now obsolete 3406bis. and now obsolete 3406bis.
o Some small editorial changes. o Some small editorial changes.
A.5. Changes from version -04 to -05 A.5. Changes from version -04 to -05
o Reissued to keep draft alive; no substantive changes. o Reissued to keep draft alive; no substantive changes.
o Updated references. 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.
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. 10 change blocks. 
7 lines changed or deleted 21 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/