idnits 2.17.1
draft-ietf-urnbis-ns-reg-transition-05.txt:
Checking boilerplate required by RFC 5378 and the IETF Trust (see
https://trustee.ietf.org/license-info):
----------------------------------------------------------------------------
No issues found here.
Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
----------------------------------------------------------------------------
No issues found here.
Checking nits according to https://www.ietf.org/id-info/checklist :
----------------------------------------------------------------------------
-- The draft header indicates that this document obsoletes RFC3187, but the
abstract doesn't seem to mention this, which it should.
-- The draft header indicates that this document obsoletes RFC3044, but the
abstract doesn't seem to mention this, which it should.
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the IETF Trust and authors Copyright Line does not
match the current year
-- The document date (August 10, 2015) is 3175 days in the past. Is this
intentional?
Checking references for intended status: Proposed Standard
----------------------------------------------------------------------------
(See RFCs 3967 and 4897 for information about using normative references
to lower-maturity documents in RFCs)
** Obsolete normative reference: RFC 2141 (Obsoleted by RFC 8141)
-- Duplicate reference: RFC2141, mentioned in 'RFC2141', was also mentioned
in 'RFC2141bis'.
-- Obsolete informational reference (is this intentional?): RFC 2141
(Obsoleted by RFC 8141)
-- Obsolete informational reference (is this intentional?): RFC 2611
(Obsoleted by RFC 3406)
-- Obsolete informational reference (is this intentional?): RFC 3044
(Obsoleted by RFC 8254)
-- Obsolete informational reference (is this intentional?): RFC 3187
(Obsoleted by RFC 8254)
-- Obsolete informational reference (is this intentional?): RFC 3188
(Obsoleted by RFC 8458)
-- Obsolete informational reference (is this intentional?): RFC 3406
(Obsoleted by RFC 8141)
Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 10 comments (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
2 URNbis J. Klensin
3 Internet-Draft
4 Obsoletes: 3044, 3187 (if approved) J. Hakala
5 Intended status: Standards Track The National Library of Finland
6 Expires: February 11, 2016 August 10, 2015
8 Uniform Resource Name (URN) Namespace Registration Transition
9 draft-ietf-urnbis-ns-reg-transition-05
11 Abstract
13 The original registration procedure for formal Uniform Resource Name
14 (URN) namespaces required IETF Consensus. That requirement
15 discouraged some registrations and increased the risk for problems
16 that could occur as a result. The requirements have now been changed
17 in [[RFC 2141bis]]. That document adopts a different model. This
18 document specifies IANA instructions to adapt selected existing
19 registrations to the new model. It also obsoletes some previous RFCs
20 to eliminate any ambiguity about the status of new templates and
21 updated registrations.
23 Status of This Memo
25 This Internet-Draft is submitted in full conformance with the
26 provisions of BCP 78 and BCP 79.
28 Internet-Drafts are working documents of the Internet Engineering
29 Task Force (IETF). Note that other groups may also distribute
30 working documents as Internet-Drafts. The list of current Internet-
31 Drafts is at http://datatracker.ietf.org/drafts/current/.
33 Internet-Drafts are draft documents valid for a maximum of six months
34 and may be updated, replaced, or obsoleted by other documents at any
35 time. It is inappropriate to use Internet-Drafts as reference
36 material or to cite them other than as "work in progress."
38 This Internet-Draft will expire on February 11, 2016.
40 Copyright Notice
42 Copyright (c) 2015 IETF Trust and the persons identified as the
43 document authors. All rights reserved.
45 This document is subject to BCP 78 and the IETF Trust's Legal
46 Provisions Relating to IETF Documents
47 (http://trustee.ietf.org/license-info) in effect on the date of
48 publication of this document. Please review these documents
49 carefully, as they describe your rights and restrictions with respect
50 to this document. Code Components extracted from this document must
51 include Simplified BSD License text as described in Section 4.e of
52 the Trust Legal Provisions and are provided without warranty as
53 described in the Simplified BSD License.
55 Table of Contents
57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
58 2. Obsoleting Older Registration RFCs for ISSNs and ISBNs . . . 3
59 2.1. ISBN URN Changes . . . . . . . . . . . . . . . . . . . . 4
60 2.2. ISSN URN Changes . . . . . . . . . . . . . . . . . . . . 4
61 3. Other existing URN registrations and RFCs . . . . . . . . . . 4
62 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
63 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
64 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
65 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5
66 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
67 8.1. Normative References . . . . . . . . . . . . . . . . . . 6
68 8.2. Informative References . . . . . . . . . . . . . . . . . 6
69 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 7
70 A.1. Changes from version -00 to -01 . . . . . . . . . . . . . 7
71 A.2. Changes from version -01 to -02 . . . . . . . . . . . . . 7
72 A.3. Changes from version -02 to -03 . . . . . . . . . . . . . 7
73 A.4. Changes from version -03 to -04 . . . . . . . . . . . . . 7
74 A.5. Changes from version -04 to -05 . . . . . . . . . . . . . 8
75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
77 1. Introduction
79 [[CREF1: RFC Editor: Please note that mentions of "[[RFC 2141bis]]"
80 in this I-D are defined as an Entity in the XML with the brackets
81 providing extra emphasis. Before publication, they should be
82 corrected, and the brackets removed, to show the actual RFC number.]]
84 [[CREF2: Note in draft: This document has been written in RFC form,
85 i.e., assuming that it and 2141bis have been approved. That style of
86 writing assumes that RFC 3406 and the rules it specified are already
87 obsolete. It may be a bit awkward while the I-D is being evaluated
88 by the WG and the IETF, but lowers the risk for errors or other
89 surprises during the RFC editing process.]]
91 As a part of the initial development of the Uniform Resource Name
92 (URN) system in the late 1990s, the IETF URN working group agreed
93 that it was important to demonstrate that the URN syntax can
94 accommodate existing identifier systems. RFC 2288 [RFC2288]
95 investigated the feasibility of using three identifiers (ISBN, ISSN
96 and SICI) as URNs, with positive results; however, it did not
97 formally register corresponding URN namespaces. This was in part due
98 to the still evolving process to formalize criteria for namespace
99 definition documents and registration, consolidated later in the IETF
100 into successive Namespace Definition Mechanism documents [RFC2611]
101 [RFC3406].
103 URN Namespaces have subsequently been registered for NBN (National
104 Bibliography Number) [RFC3188], ISBN (International Standard Book
105 Number) [RFC3187], and ISSN (International Standard Serial Number)
106 [RFC3044].
108 The predecessor registration procedure for Uniform Resource Name
109 (URN) namespaces [RFC3406] required IETF Consensus for formal
110 namespaces. That requirement discouraged some registrations and
111 increased the risk for problems, including use of names without
112 registration ("squatting"), that could occur as a result. Those
113 potential problems included the possibility of the same name being
114 used to identify different namespaces with different rules. The
115 requirements have now been changed [RFC2141bis] to adopt a different
116 model that focuses more on encouraging registration of all namespaces
117 that follow the formal namespace syntax, with as much information
118 collected as possible consistent with that goal. This document
119 specifies IANA instructions to adapt selected existing registrations
120 to the new model and obsoletes the separate RFCs that specify the
121 namespaces for International Standard Serial Numbers (ISSNs)
122 [RFC3044] and International Standard Book Numbers (ISBNs) [RFC3187]
123 to eliminate any ambiguity about the status of new templates and
124 updated registrations.
126 An updated version of the specification for the namespace for
127 National Bibliography Numbers (NBNs) [RFC3188] will be issued
128 separately. NBN is not a formal international standard and RFC 3188
129 is the only formal document which specifies its scope. The intention
130 is to modernize the existing namespace registration so that it
131 specifies the identifier and provides examples of its use, while the
132 actual namespace registration will be done according to the new
133 practice.
135 2. Obsoleting Older Registration RFCs for ISSNs and ISBNs
137 The existing RFCs that describe URN namespaces for ISSNs (RFC 3044)
138 and ISBNs (RFC 3187) should be identified as "Historic" after this
139 document is approved and immediately after the new registration
140 templates for those namespaces are submitted and incorporated into
141 the URN Namespace registry by IANA.
143 [[CREF3: Note in draft: The more information that can be supplied in
144 the template or references from it, the better. But, if there is
145 information in the now-expired Internet-Drafts (draft-ietf-urnbis-
146 rfc3187bis-isbn-urn, draft-ietf-urnbis-rfc3044bis-issn-urn) that
147 should be captured somewhere and that doesn't fit naturally in the
148 template, the discussion below is probably a reasonable place to put
149 it.]]
150 [[CREF4: Similarly, if special transition discussions are needed for
151 other URN namespaces registered prior to the intended transition,
152 this document might be a place to discuss them if they are not too
153 complicated (if they are complicated, they probably deserve their own
154 documents).]]
156 The updated templates reflect not only new template formats but
157 substantive changes to the definitions of the namespaces. The
158 changes are summarized in the subsections that follow.
160 For both ISSN and ISBN URNs, it is intended that the registrations
161 track the evolution of ISO standardization without requiring
162 resubmission of the templates or other formal IETF or IANA
163 registration update approval procedures.
165 2.1. ISBN URN Changes
167 The revised ISBN namespace reflects the updated version of the ISO
168 Standard for ISBNs, ISO 2108:2005 [ISO-ISBN-b]. The namespace allows
169 for the use of both the ten character numbers described in RFC 3187
170 and the earlier ISO 2108:1992 [ISO-ISBN-a] (known as ISBN-10), as
171 well as the expanded ones specified in the revised and updated
172 standard (known as ISBN-13).
174 2.2. ISSN URN Changes
176 The ISSN namespace is also updated to reflect changes between the
177 ISSN Standard when RFC 3044 was written and the newest, 2007 version
178 [ISO-ISSN].
180 3. Other existing URN registrations and RFCs
182 The RFC Series and IANA Registry contain many URN definitions in
183 addition to those for which this document calls out explicit actions.
184 In general, those existing registrations are still appropriate but
185 omit some information called for in [[RFC 2141bis]]. Until and
186 unless those registrations are updated as provided for in [[RFC
187 2141bis]], the existing registration templates should be read as not
188 requiring or allowing any features that were not allowed and
189 specified by the earlier URN [RFC2141] and registration [RFC3406]
190 specifications.
192 4. IANA Considerations
194 IANA is requested to update the registry entries for URN ISSN, ISBN,
195 and NRN namespaces to reflect the new, [[RFC 2141bis]]-complaint
196 templates as soon as they are available and to no longer reference
197 the now-historic RFCs. With respect to namespaces other than those
198 listed above, registrations and templates conforming to the newer
199 rules may be substituted for the older ones when they are available.
200 However, neither this document nor [[RFC 2141bis]] supercedes
201 existing registrations other than those listed above. Therefore,
202 IANA needs to be prepared to maintain a registry whose contents
203 reflect old-style templates for some namespaces and the newer ones
204 for others.
206 IANA should also note that the portions of the registrations that
207 point to ISO Standards are intended to identify current versions
208 (which may change) rather than only the versions that are active at
209 the time this document is approved (see Section 2).
211 5. Security Considerations
213 While particular URN namespaces and their registrations might
214 conceivably have security implications, this specification merely
215 specifies a transition of a pair of registration procedures and does
216 not have such implications. The security implications associated
217 with particular namespaces are expected to be listed in registration
218 templates as specified in [[RFC 2141bis]].
220 6. Acknowledgements
222 This document draws heavily on discussions in the IETF URNbis Working
223 Group in the second and third quarters of 2013, particularly during
224 IETF 87 in August 2013, and on informal discussions during the
225 plenary meeting of ISO TC 46 in June 2013. The efforts of those who
226 participated in those discussions are greatly appreciated. It also
227 draws on internet-drafts that were developed to update the older
228 registrations before that approach was replaced by the new extended
229 template model. Those drafts were prepared by Pierre Godefroy, Juha
230 Hakala, Alfred Hoenes, and Maarit Huttunen.
232 The current draft benefits significantly from a careful reading and
233 suggestions for editorial changes by Peter Saint-Andre.
235 7. Contributors
237 Alfred Hoenes was the editor and co-author of two of the documents
238 from which this one is, in part, derived. This document would not
239 have been possible without his contributions.
241 8. References
243 8.1. Normative References
245 [RFC2141bis]
246 Saint-Andre, P. and J. Klensin, "Uniform Resource Name
247 (URN) Syntax", June 2015,
248 .
251 8.2. Informative References
253 [ISO-ISBN-a]
254 ISO, "Information and documentation - The International
255 Standard Book Number (ISBN)", ISO 2180:1992, 1992.
257 [ISO-ISBN-b]
258 ISO, "Information and documentation - The International
259 Standard Book Number (ISBN)", ISO 2180:2005, 2005.
261 [ISO-ISSN]
262 ISO, "Information and documentation - International
263 standard serial number (ISSN)", ISO 3297:2007, 2007.
265 [RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141,
266 May 1997, .
268 [RFC2288] Lynch, C., Preston, C., and R. Daniel, "Using Existing
269 Bibliographic Identifiers as Uniform Resource Names",
270 RFC 2288, DOI 10.17487/RFC2288, February 1998,
271 .
273 [RFC2611] Daigle, L., van Gulik, D., Iannella, R., and P. Falstrom,
274 "URN Namespace Definition Mechanisms", BCP 33, RFC 2611,
275 DOI 10.17487/RFC2611, June 1999,
276 .
278 [RFC3044] Rozenfeld, S., "Using The ISSN (International Serial
279 Standard Number) as URN (Uniform Resource Names) within an
280 ISSN-URN Namespace", RFC 3044, DOI 10.17487/RFC3044,
281 January 2001, .
283 [RFC3187] Hakala, J. and H. Walravens, "Using International Standard
284 Book Numbers as Uniform Resource Names", RFC 3187,
285 DOI 10.17487/RFC3187, October 2001,
286 .
288 [RFC3188] Hakala, J., "Using National Bibliography Numbers as
289 Uniform Resource Names", RFC 3188, DOI 10.17487/RFC3188,
290 October 2001, .
292 [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
293 "Uniform Resource Names (URN) Namespace Definition
294 Mechanisms", BCP 66, RFC 3406, DOI 10.17487/RFC3406,
295 October 2002, .
297 Appendix A. Change Log
299 A.1. Changes from version -00 to -01
301 o Modified the introduction to Section 2 and Section 4 to make it
302 clear that registry update procedures should not be required to
303 keep the registrations current with ISO Standard reaffirmations or
304 replacments.
306 o Many editorial changes to improve readability and clarity.
308 A.2. Changes from version -01 to -02
310 o Several small editorial changes and clarifications suggested by
311 Peter Saint-Andre.
313 o Updated acknowledgments.
315 A.3. Changes from version -02 to -03
317 o Updated to prevent expiration
319 o New text to allow for other already-registered namespaces and to
320 better explain relationships.
322 o Some small editorial changes.
324 A.4. Changes from version -03 to -04
326 o Updated references and, where needed, discussion to point to the
327 new, consolidated, 2141bis rather than to the formerly separate
328 and now obsolete 3406bis.
330 o Some small editorial changes.
332 A.5. Changes from version -04 to -05
334 o Reissued to keep draft alive; no substantive changes.
336 o Updated references.
338 Authors' Addresses
340 John C Klensin
341 1770 Massachusetts Ave, Ste 322
342 Cambridge, MA 02140
343 USA
345 Phone: +1 617 245 1457
346 Email: john-ietf@jck.com
348 Juha Hakala
349 The National Library of Finland
350 P.O. Box 15, Helsinki University
351 Helsinki, MA FIN-00014
352 Finland
354 Email: juha.hakala@helsinki.fi