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