idnits 2.17.1 draft-ietf-urnbis-ns-reg-transition-07.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 (May 9, 2017) is 2541 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) == Unused Reference: 'RFC3044' is defined on line 340, but no explicit reference was found in the text == Unused Reference: 'RFC3187' is defined on line 345, but no explicit reference was found in the text -- 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: 0 errors (**), 0 flaws (~~), 3 warnings (==), 9 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: November 10, 2017 May 9, 2017 8 Uniform Resource Name (URN) Namespace Registration Transition 9 draft-ietf-urnbis-ns-reg-transition-07 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 by RFC 8141, which adopts a different model, focusing on encouraging 18 registration and publication of information for all appropriate 19 namespaces. This document clarifies that status of relevant older 20 RFCs and advises IANA about selected existing registrations. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on November 10, 2017. 39 Copyright Notice 41 Copyright (c) 2017 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Obsoleting Older Registration RFCs for ISSNs and ISBNs . . . 3 58 2.1. ISBN URN Changes . . . . . . . . . . . . . . . . . . . . 4 59 2.2. ISSN URN Changes . . . . . . . . . . . . . . . . . . . . 4 60 3. Obsoleting older registration RFC for NBNs . . . . . . . . . 4 61 4. Other existing URN registrations and RFCs . . . . . . . . . . 5 62 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 63 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 64 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 65 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6 66 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 67 9.1. Normative References . . . . . . . . . . . . . . . . . . 6 68 9.2. Informative References . . . . . . . . . . . . . . . . . 6 69 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 8 70 A.1. Changes from version -00 to -01 . . . . . . . . . . . . . 8 71 A.2. Changes from version -01 to -02 . . . . . . . . . . . . . 8 72 A.3. Changes from version -02 to -03 . . . . . . . . . . . . . 9 73 A.4. Changes from version -03 to -04 . . . . . . . . . . . . . 9 74 A.5. Changes from version -04 to -05 . . . . . . . . . . . . . 9 75 A.6. Changes from version -05 to -06 . . . . . . . . . . . . . 9 76 A.7. Changes from version -06 (2016-02-07) to -07 (2017-05-09) 9 77 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 79 1. Introduction 81 As a part of the initial development of the Uniform Resource Name 82 (URN) system in the late 1990s, the IETF URN working group agreed 83 that it was important to demonstrate that the URN syntax can 84 accommodate existing identifier systems. RFC 2288 [RFC2288] proved 85 the feasibility of using International Standard Book Number (ISBN), 86 International Standard Serial Number (ISSN), and Serial Item and 87 Contribution Identifier (SICI) [ANSI-SICI]) as URNs; however, it did 88 not formally register corresponding URN namespaces. This was in part 89 due to the still evolving process to formalize criteria for namespace 90 definition documents and registration, consolidated later in the IETF 91 into successive Namespace Definition Mechanism documents [RFC2611] 92 [RFC3406]. 94 URN Namespaces have subsequently been registered for ISBN and ISSN as 95 well as for a fairly large collection of other identifiers including 96 National Bibliography Number (NBN) [RFC3188]. The comprehensive list 97 can be found in the IANA registry [IANA-Namespace-Registry] (see also 98 Section 4). 100 While a URN namespace for SICI could be registered at any time, the 101 standard has not gained broad international acceptance and has not 102 had a namespace defined to date. 104 The predecessor registration procedure for Uniform Resource Name 105 (URN) namespaces [RFC3406] required IETF Consensus for formal 106 namespaces. That requirement discouraged some registrations and 107 increased the risk for problems, including use of names without 108 registration ("squatting"), that could occur as a result. Those 109 potential problems included the possibility of the same name being 110 used to identify different namespaces with different rules. The 111 requirements have now been changed in RFC 8141 [RFC8141] to adopt a 112 different model that focuses more on encouraging registration of all 113 namespaces that follow the formal namespace syntax, with as much 114 information collected as possible consistent with that goal. 116 Therefore this document does the following: 118 o Specifies IANA instructions to adapt selected existing 119 registrations to the new model. 121 o Obsoletes the separate RFCs that specify the namespaces for ISSNs 122 and ISBNs to eliminate any ambiguity about the status of new 123 templates and updated registrations. 125 o Provides information about the status of NBNs under the 126 definitions. 128 o Provides suggestions to IANA about the handling of other existing 129 registrations not explicitly mentioned herein. 131 2. Obsoleting Older Registration RFCs for ISSNs and ISBNs 133 The existing RFCs that describe URN namespaces for ISSNs (RFC 3044) 134 and ISBNs (RFC 3187) should be identified as "Historic" after this 135 document is approved and immediately after the new registration 136 templates for those namespaces are submitted and incorporated into 137 the URN Namespace registry by IANA. 139 The updated templates reflect not only new template formats but 140 substantive changes to the definitions of the namespaces. The 141 changes are summarized in the subsections that follow. 143 For both ISSN and ISBN URNs, it is intended that the registrations 144 track the evolution of ISO standardization without requiring 145 resubmission of the templates or other formal IETF or IANA 146 registration update approval procedures. The subsections that follow 147 clarify the relationship between the original URN namespace 148 registrations for ISBN and ISSN and new templates being registered 149 that follow the principles of RFC 8141. Approval and registration of 150 those new templates makes the older templates obsolete and RFCs 3044 151 and 3187 Historic. 153 2.1. ISBN URN Changes 155 The revised ISBN namespace reflects the latest version of the ISO 156 ISBN Standard, ISO 2108:2017 [ISO-ISBN-b]. The namespace allows for 157 the use of both the old ten character ISBN numbers described in RFC 158 3187 and ISO 2108:1992 [ISO-ISBN-a] (formerly known as ISBN-10) and 159 the 13 character identifiers introduced in ISO 2108:2005 [ISO-ISBN-c] 160 (formerly known as ISBN-13). 162 For information and help in understanding other parts of this 163 document, review the new ISBN registration template [ISBN-Template]. 165 2.2. ISSN URN Changes 167 The updated ISSN namespace reflects the changes between the current 168 ISSN standard [ISO-ISSN] and its predecessor on which RFC 3044 was 169 based. ISO 3297:2007 introduced the linking ISSN (ISSN-L), which is 170 designated for all media of a serial publication, irrespective of how 171 many there are. Traditional ISSN applies to single media only, such 172 as printed version of a serial. 174 For information and help in understanding other parts of this 175 document, review the new ISSN registration template [ISSN-Template]. 177 3. Obsoleting older registration RFC for NBNs 179 NBN is not a formal international standard or even a single 180 identifier system, but an umbrella concept which covers all 181 identifier systems the national libraries and their partners use to 182 identify resources which do not have other identifier. For instance, 183 if a book received via legal deposit does not have an ISBN, the 184 national library gives it a local identifier. NBN specification 185 provides simple means of expressing these local identifiers so that 186 they become globally unique URNs, such as urn:nbn:fi-fe19981001. 188 In addition to the namespace registration itself, RFC 3188 provides 189 some generic information about NBNs and their use, and specifies the 190 syntax of URN:NBNs which guarantees uniqueness by requiring the usage 191 of country codes and institutional identifiers as a part of the NSS. 193 When RFC 3188 is revised, it should be accompanied with a template 194 which revises the registration of the URN:NBN namespace. 196 4. Other existing URN registrations and RFCs 198 The RFC Series and IANA Registry contain many URN namespace 199 registrations in addition to those for which this document calls out 200 explicit actions. In general, those existing registrations are still 201 appropriate but omit some information called for in RFC 8141 202 [RFC8141]. Reregistration with new templates is recommended, but not 203 required. Until and unless those registrations are updated as 204 provided for in RFC 8141, the existing registration templates should 205 be read as not requiring or allowing any features that were not 206 allowed and specified by the earlier URN [RFC2141] and registration 207 [RFC3406] specifications. 209 5. IANA Considerations 211 IANA is requested to update the registry entries for URN ISSN, ISBN, 212 and NBN namespaces to reflect the new, RFC 8141-compliant templates 213 as soon as they are available and to no longer reference the now- 214 historic RFCs. With respect to namespaces other than those listed 215 above, registrations and templates conforming to the newer rules may 216 be substituted for the older ones when they are available. However, 217 neither this document nor RFC 8141 supersedes existing registrations 218 other than those listed above. Therefore, IANA needs to be prepared 219 to maintain a registry whose contents reflect old-style templates for 220 some namespaces (including, temporarily, those for ISBN and ISSN 221 ones) and the newer ones for others. 223 IANA should also note that the portions of the registrations that 224 point to ISO Standards are intended to identify current versions 225 (which may change) rather than only the versions that are active at 226 the time this document is approved (see Section 2). 228 6. Security Considerations 230 While particular URN namespaces and their registrations might 231 conceivably have security implications, this specification merely 232 specifies a transition of a set of namespace registrations and does 233 not have such implications. The security implications associated 234 with particular namespaces are expected to be listed in registration 235 templates as specified in RFC 8141. 237 7. Acknowledgements 239 This document draws heavily on discussions in the IETF URNbis Working 240 Group in the second and third quarters of 2013, particularly during 241 IETF 87 in August 2013, and on informal discussions during the 242 plenary meeting of ISO TC 46 in June 2013. The efforts of those who 243 participated in those discussions are greatly appreciated. It also 244 draws on internet-drafts that were developed to update the older 245 registrations before that approach was replaced by the new extended 246 template model. Those drafts were prepared by Pierre Godefroy, Juha 247 Hakala, Alfred Hoenes, and Maarit Huttunen. 249 The current draft benefits significantly from a careful reading and 250 suggestions for editorial changes by Peter Saint-Andre and from 251 considerable work by Stella Griffiths of the ISBN international 252 Centre to refine the ISBN discussion and from Pierre Godefroy and 253 Clement Oury of the ISSN International Centre for similar refinements 254 of the ISSN discussion. 255 [[CREF1: RFC Editor and IANA: Please note that "Centre" is the 256 correct spelling of the names of those bodies. If you want to spell 257 out the names, use "International Standard Book Number" and 258 "International Standard Series Number" although the abbreviations are 259 well-known internationally. And M. Oury's first name is properly 260 spelled with an acute accent over the initial "e", i.e., with U+00E9 261 should things be far enough along for you to use that information.]] 263 8. Contributors 265 Alfred Hoenes was the editor and co-author of two of the documents 266 from which this one is, in part, derived. This document would not 267 have been possible without his contributions. 269 9. References 271 9.1. Normative References 273 [RFC8141] Saint-Andre, P. and J. Klensin, "Uniform Resource Names 274 (URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017, 275 . 277 9.2. Informative References 279 [ANSI-SICI] 280 ANSI/NISO, "Serial Item and Contribution Identifier, ANSI/ 281 NISO Z39.56-1996 (Version 2)", 1996. 283 [IANA-Namespace-Registry] 284 IANA, "Uniform Resource Names (URN) Namespaces", 2016, 285 . 288 [ISBN-Template] 289 ISBN International Centre, "... to be supplied ...", 2017, 290 . 292 RFC Editor: please be sure the correct IANA links are 293 filled in for this and the ISSN one. Also, if you would 294 like addresses and other contact information for these, 295 that information is easily provided. 297 [ISO-ISBN-a] 298 ISO, "Information and documentation - The International 299 Standard Book Number (ISBN)", ISO 2108:1992, 1992. 301 [ISO-ISBN-b] 302 ISO, "Information and documentation - The International 303 Standard Book Number (ISBN)", ISO 2108:2017, 2017. 305 Note to RFC Editor: As of early March, the 2017 version is 306 awaiting publication, but the ISBN International Center 307 strongly prefers that we reference it and not some earlier 308 version. If this note is still present when the document 309 is otherwise ready for AUTH48, please see 310 https://www.iso.org/standard/65483.html and discuss status 311 with the authors. 313 [ISO-ISBN-c] 314 ISO, "Information and documentation - The International 315 Standard Book Number (ISBN)", ISO 2108:2005, 2005. 317 [ISO-ISSN] 318 ISO, "Information and documentation - International 319 standard serial number (ISSN)", ISO 3297:2007, 2007. 321 [ISSN-Template] 322 ISSN International Centre, "Namespace Registration for 323 International Standard Serial Number (ISSN) and Linking 324 ISSN (ISSN-L)ISO 3297:2007", 2017, 325 . 327 [RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141, 328 May 1997, . 330 [RFC2288] Lynch, C., Preston, C., and R. Daniel, "Using Existing 331 Bibliographic Identifiers as Uniform Resource Names", 332 RFC 2288, DOI 10.17487/RFC2288, February 1998, 333 . 335 [RFC2611] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, 336 "URN Namespace Definition Mechanisms", BCP 33, RFC 2611, 337 DOI 10.17487/RFC2611, June 1999, 338 . 340 [RFC3044] Rozenfeld, S., "Using The ISSN (International Serial 341 Standard Number) as URN (Uniform Resource Names) within an 342 ISSN-URN Namespace", RFC 3044, DOI 10.17487/RFC3044, 343 January 2001, . 345 [RFC3187] Hakala, J. and H. Walravens, "Using International Standard 346 Book Numbers as Uniform Resource Names", RFC 3187, 347 DOI 10.17487/RFC3187, October 2001, 348 . 350 [RFC3188] Hakala, J., "Using National Bibliography Numbers as 351 Uniform Resource Names", RFC 3188, DOI 10.17487/RFC3188, 352 October 2001, . 354 [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, 355 "Uniform Resource Names (URN) Namespace Definition 356 Mechanisms", RFC 3406, DOI 10.17487/RFC3406, October 2002, 357 . 359 Appendix A. Change Log 361 RFC Editor: Please remove this appendix. 363 A.1. Changes from version -00 to -01 365 o Modified the introduction to Section 2 and Section 5 to make it 366 clear that registry update procedures should not be required to 367 keep the registrations current with ISO Standard reaffirmations or 368 replacments. 370 o Many editorial changes to improve readability and clarity. 372 A.2. Changes from version -01 to -02 374 o Several small editorial changes and clarifications suggested by 375 Peter Saint-Andre. 377 o Updated acknowledgments. 379 A.3. Changes from version -02 to -03 381 o Updated to prevent expiration 383 o New text to allow for other already-registered namespaces and to 384 better explain relationships. 386 o Some small editorial changes. 388 A.4. Changes from version -03 to -04 390 o Updated references and, where needed, discussion to point to the 391 new, consolidated, 2141bis rather than to the formerly separate 392 and now obsolete 3406bis. 394 o Some small editorial changes. 396 A.5. Changes from version -04 to -05 398 o Reissued to keep draft alive; no substantive changes. 400 o Updated references. 402 A.6. Changes from version -05 to -06 404 o Reissued to keep draft alive; some editorial updates but no 405 substantive changes. 407 o Updated references. 409 A.7. Changes from version -06 (2016-02-07) to -07 (2017-05-09) 411 o Removed old CREFs. Added a new one, but only as a forward-looking 412 note to the RFC Editor. 414 o Moved expansions of ISBN, ISSN, SICI, and NBN to the first uses of 415 those terms, after which the abbreviations are used exclusively. 417 o Removed text that made promises about the content and schedule for 418 RFC 3188bis. 420 o Rewrote or removed several paragraphs that seemed to confuse the 421 status of various documents and registrations. 423 o Added a cross-reference and additional detail for existing 424 registrations not specifically discussed in this document. 426 o Modified the IANA Considerations section to improve clarity and 427 remove references to the expected template appendices. Because 428 RFC 8141 (2141bis) has been published and the new registration 429 procedures are in effect, there is presumably no reason to add 430 length and confusion to this document by including preliminary 431 versions of those templates. 433 o Updated references, including the reference to the recently- 434 published RFC 8141 (aka 2141bis). 436 o Added placeholder references for the registrations of the new IANA 437 templates. 439 o Corrected minor typographical errors. 441 Authors' Addresses 443 John C Klensin 444 1770 Massachusetts Ave, Ste 322 445 Cambridge, MA 02140 446 USA 448 Phone: +1 617 245 1457 449 Email: john-ietf@jck.com 451 Juha Hakala 452 The National Library of Finland 453 P.O. Box 15, Helsinki University 454 Helsinki, MA FIN-00014 455 Finland 457 Email: juha.hakala@helsinki.fi