idnits 2.17.1
draft-ietf-urnbis-ns-reg-transition-06.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 (February 7, 2016) is 2995 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: August 10, 2016 February 7, 2016
8 Uniform Resource Name (URN) Namespace Registration Transition
9 draft-ietf-urnbis-ns-reg-transition-06
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 August 10, 2016.
40 Copyright Notice
42 Copyright (c) 2016 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 A.6. Changes from version -05 to -06 . . . . . . . . . . . . . 8
76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
78 1. Introduction
80 [[CREF1: RFC Editor: Please note that mentions of "[[RFC 2141bis]]"
81 in this I-D are defined as an Entity in the XML with the brackets
82 providing extra emphasis. Before publication, they should be
83 corrected, and the brackets removed, to show the actual RFC number.]]
85 [[CREF2: Note in draft: This document has been written in RFC form,
86 i.e., assuming that it and 2141bis have been approved. That style of
87 writing assumes that RFC 3406 and the rules it specified are already
88 obsolete. It may be a bit awkward while the I-D is being evaluated
89 by the WG and the IETF, but lowers the risk for errors or other
90 surprises during the RFC editing process.]]
92 As a part of the initial development of the Uniform Resource Name
93 (URN) system in the late 1990s, the IETF URN working group agreed
94 that it was important to demonstrate that the URN syntax can
95 accommodate existing identifier systems. RFC 2288 [RFC2288]
96 investigated the feasibility of using three identifiers (ISBN, ISSN
97 and SICI) as URNs, with positive results; however, it did not
98 formally register corresponding URN namespaces. This was in part due
99 to the still evolving process to formalize criteria for namespace
100 definition documents and registration, consolidated later in the IETF
101 into successive Namespace Definition Mechanism documents [RFC2611]
102 [RFC3406].
104 URN Namespaces have subsequently been registered for NBN (National
105 Bibliography Number) [RFC3188], ISBN (International Standard Book
106 Number) [RFC3187], and ISSN (International Standard Serial Number)
107 [RFC3044] as well as for a fairly large collection of other
108 namespaces [IANA-Namespace-Registry].
110 The predecessor registration procedure for Uniform Resource Name
111 (URN) namespaces [RFC3406] required IETF Consensus for formal
112 namespaces. That requirement discouraged some registrations and
113 increased the risk for problems, including use of names without
114 registration ("squatting"), that could occur as a result. Those
115 potential problems included the possibility of the same name being
116 used to identify different namespaces with different rules. The
117 requirements have now been changed [RFC2141bis] to adopt a different
118 model that focuses more on encouraging registration of all namespaces
119 that follow the formal namespace syntax, with as much information
120 collected as possible consistent with that goal. This document
121 specifies IANA instructions to adapt selected existing registrations
122 to the new model and obsoletes the separate RFCs that specify the
123 namespaces for International Standard Serial Numbers (ISSNs)
124 [RFC3044] and International Standard Book Numbers (ISBNs) [RFC3187]
125 to eliminate any ambiguity about the status of new templates and
126 updated registrations.
128 An updated version of the specification for the namespace for
129 National Bibliography Numbers (NBNs) [RFC3188] will be issued
130 separately. NBN is not a formal international standard and RFC 3188
131 is the only formal document which specifies its scope. The intention
132 is to modernize the existing namespace registration so that it
133 specifies the identifier and provides examples of its use, while the
134 actual namespace registration will be done according to the new
135 practice.
137 2. Obsoleting Older Registration RFCs for ISSNs and ISBNs
139 The existing RFCs that describe URN namespaces for ISSNs (RFC 3044)
140 and ISBNs (RFC 3187) should be identified as "Historic" after this
141 document is approved and immediately after the new registration
142 templates for those namespaces are submitted and incorporated into
143 the URN Namespace registry by IANA.
145 [[CREF3: Note in draft: The more information that can be supplied in
146 the template or references from it, the better. But, if there is
147 information in the now-expired Internet-Drafts (draft-ietf-urnbis-
148 rfc3187bis-isbn-urn, draft-ietf-urnbis-rfc3044bis-issn-urn) that
149 should be captured somewhere and that doesn't fit naturally in the
150 template, the discussion below is probably a reasonable place to put
151 it.]]
152 [[CREF4: Similarly, if special transition discussions are needed for
153 other URN namespaces registered prior to the intended transition,
154 this document might be a place to discuss them if they are not too
155 complicated (if they are complicated, they probably deserve their own
156 documents).]]
158 The updated templates reflect not only new template formats but
159 substantive changes to the definitions of the namespaces. The
160 changes are summarized in the subsections that follow.
162 For both ISSN and ISBN URNs, it is intended that the registrations
163 track the evolution of ISO standardization without requiring
164 resubmission of the templates or other formal IETF or IANA
165 registration update approval procedures.
167 2.1. ISBN URN Changes
169 The revised ISBN namespace reflects the updated version of the ISO
170 Standard for ISBNs, ISO 2108:2005 [ISO-ISBN-b]. The namespace allows
171 for the use of both the ten character numbers described in RFC 3187
172 and the earlier ISO 2108:1992 [ISO-ISBN-a] (known as ISBN-10), as
173 well as the expanded ones specified in the revised and updated
174 standard (known as ISBN-13).
176 2.2. ISSN URN Changes
178 The ISSN namespace is also updated to reflect changes between the
179 ISSN Standard when RFC 3044 was written and the newest, 2007 version
180 [ISO-ISSN].
182 3. Other existing URN registrations and RFCs
184 The RFC Series and IANA Registry contain many URN definitions in
185 addition to those for which this document calls out explicit actions.
186 In general, those existing registrations are still appropriate but
187 omit some information called for in [[RFC 2141bis]]. Until and
188 unless those registrations are updated as provided for in [[RFC
189 2141bis]], the existing registration templates should be read as not
190 requiring or allowing any features that were not allowed and
191 specified by the earlier URN [RFC2141] and registration [RFC3406]
192 specifications.
194 4. IANA Considerations
196 IANA is requested to update the registry entries for URN ISSN, ISBN,
197 and NRN namespaces to reflect the new, [[RFC 2141bis]]-complaint
198 templates as soon as they are available and to no longer reference
199 the now-historic RFCs. With respect to namespaces other than those
200 listed above, registrations and templates conforming to the newer
201 rules may be substituted for the older ones when they are available.
202 However, neither this document nor [[RFC 2141bis]] supercedes
203 existing registrations other than those listed above. Therefore,
204 IANA needs to be prepared to maintain a registry whose contents
205 reflect old-style templates for some namespaces and the newer ones
206 for others.
208 IANA should also note that the portions of the registrations that
209 point to ISO Standards are intended to identify current versions
210 (which may change) rather than only the versions that are active at
211 the time this document is approved (see Section 2).
213 5. Security Considerations
215 While particular URN namespaces and their registrations might
216 conceivably have security implications, this specification merely
217 specifies a transition of a set of namespace registrations and does
218 not have such implications. The security implications associated
219 with particular namespaces are expected to be listed in registration
220 templates as specified in [[RFC 2141bis]].
222 6. Acknowledgements
224 This document draws heavily on discussions in the IETF URNbis Working
225 Group in the second and third quarters of 2013, particularly during
226 IETF 87 in August 2013, and on informal discussions during the
227 plenary meeting of ISO TC 46 in June 2013. The efforts of those who
228 participated in those discussions are greatly appreciated. It also
229 draws on internet-drafts that were developed to update the older
230 registrations before that approach was replaced by the new extended
231 template model. Those drafts were prepared by Pierre Godefroy, Juha
232 Hakala, Alfred Hoenes, and Maarit Huttunen.
234 The current draft benefits significantly from a careful reading and
235 suggestions for editorial changes by Peter Saint-Andre.
237 7. Contributors
239 Alfred Hoenes was the editor and co-author of two of the documents
240 from which this one is, in part, derived. This document would not
241 have been possible without his contributions.
243 8. References
245 8.1. Normative References
247 [RFC2141bis]
248 Saint-Andre, P. and J. Klensin, "Uniform Resource Name
249 (URN) Syntax", February 2016,
250 .
253 8.2. Informative References
255 [IANA-Namespace-Registry]
256 IANA, "Uniform Resource Names (URN) Namespaces", 2016,
257 .
260 [ISO-ISBN-a]
261 ISO, "Information and documentation - The International
262 Standard Book Number (ISBN)", ISO 2180:1992, 1992.
264 [ISO-ISBN-b]
265 ISO, "Information and documentation - The International
266 Standard Book Number (ISBN)", ISO 2180:2005, 2005.
268 [ISO-ISSN]
269 ISO, "Information and documentation - International
270 standard serial number (ISSN)", ISO 3297:2007, 2007.
272 [RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141,
273 May 1997, .
275 [RFC2288] Lynch, C., Preston, C., and R. Daniel, "Using Existing
276 Bibliographic Identifiers as Uniform Resource Names",
277 RFC 2288, DOI 10.17487/RFC2288, February 1998,
278 .
280 [RFC2611] Daigle, L., van Gulik, D., Iannella, R., and P. Falstrom,
281 "URN Namespace Definition Mechanisms", BCP 33, RFC 2611,
282 DOI 10.17487/RFC2611, June 1999,
283 .
285 [RFC3044] Rozenfeld, S., "Using The ISSN (International Serial
286 Standard Number) as URN (Uniform Resource Names) within an
287 ISSN-URN Namespace", RFC 3044, DOI 10.17487/RFC3044,
288 January 2001, .
290 [RFC3187] Hakala, J. and H. Walravens, "Using International Standard
291 Book Numbers as Uniform Resource Names", RFC 3187,
292 DOI 10.17487/RFC3187, October 2001,
293 .
295 [RFC3188] Hakala, J., "Using National Bibliography Numbers as
296 Uniform Resource Names", RFC 3188, DOI 10.17487/RFC3188,
297 October 2001, .
299 [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
300 "Uniform Resource Names (URN) Namespace Definition
301 Mechanisms", BCP 66, RFC 3406, DOI 10.17487/RFC3406,
302 October 2002, .
304 Appendix A. Change Log
306 A.1. Changes from version -00 to -01
308 o Modified the introduction to Section 2 and Section 4 to make it
309 clear that registry update procedures should not be required to
310 keep the registrations current with ISO Standard reaffirmations or
311 replacments.
313 o Many editorial changes to improve readability and clarity.
315 A.2. Changes from version -01 to -02
317 o Several small editorial changes and clarifications suggested by
318 Peter Saint-Andre.
320 o Updated acknowledgments.
322 A.3. Changes from version -02 to -03
324 o Updated to prevent expiration
326 o New text to allow for other already-registered namespaces and to
327 better explain relationships.
329 o Some small editorial changes.
331 A.4. Changes from version -03 to -04
333 o Updated references and, where needed, discussion to point to the
334 new, consolidated, 2141bis rather than to the formerly separate
335 and now obsolete 3406bis.
337 o Some small editorial changes.
339 A.5. Changes from version -04 to -05
341 o Reissued to keep draft alive; no substantive changes.
343 o Updated references.
345 A.6. Changes from version -05 to -06
347 o Reissued to keep draft alive; some editorial updates but no
348 substantive changes.
350 o Updated references.
352 Authors' Addresses
354 John C Klensin
355 1770 Massachusetts Ave, Ste 322
356 Cambridge, MA 02140
357 USA
359 Phone: +1 617 245 1457
360 Email: john-ietf@jck.com
362 Juha Hakala
363 The National Library of Finland
364 P.O. Box 15, Helsinki University
365 Helsinki, MA FIN-00014
366 Finland
368 Email: juha.hakala@helsinki.fi