idnits 2.17.1 draft-ietf-urnbis-ns-reg-transition-00.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 26, 2013) is 3895 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 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 (==), 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: February 27, 2014 August 26, 2013 8 Uniform Resource Name (URN) Namespace Registration Transition 9 draft-ietf-urnbis-ns-reg-transition-00 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]] to adopt a different model. This document 18 specifies IANA instructions to adapt selected existing registrations 19 to the new model. It also obsoletes some previous RFCs to eliminate 20 any ambiguity about the status of new templates and updated 21 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 27, 2014. 40 Copyright Notice 42 Copyright (c) 2013 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 . . . . . . . . . . . . . 3 59 2.1. ISBN URN Changes . . . . . . . . . . . . . . . . . . . . 4 60 2.2. ISSN URN Changes . . . . . . . . . . . . . . . . . . . . 4 61 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 62 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 63 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 64 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5 65 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 66 7.1. Normative References . . . . . . . . . . . . . . . . . . 5 67 7.2. Informative References . . . . . . . . . . . . . . . . . 5 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 70 1. Introduction 72 [[Note in draft: This document has been written in RFC form, i.e., 73 assuming that it and 3406bis have been approved. That style of 74 writing assumes that RFC 3406 and the rules it specified are already 75 obsolete. It may be a bit awkward while the I-D is being evaluated 76 by the WG and the IETF, but lowers the risk for errors or other 77 surprises during the RFC editing process.]] 79 As a part of the initial development of the URN system back in the 80 late 1990s, the IETF URN working group agreed that it was important 81 to demonstrate that the URN syntax can accommodate existing 82 identifier systems. RFC 2288 [RFC2288] investigated the feasibility 83 of using three identifiers (ISBN, ISSN and SICI) as URNs, with 84 positive results; however, it did not formally register corresponding 85 URN namespaces. This was in part due to the still evolving process 86 to formalize criteria for namespace definition documents and 87 registration, consolidated later in the IETF, first into RFC 2611 88 [RFC2611] and then into RFC 3406 [RFC3406]. 90 URN Namespaces have subsequently been registered for NBN (National 91 Bibliography Number), ISBN (International Standard Book Number), and 92 ISSN (International Serial Standard Number) in RFCs 3188 [RFC3188], 93 3187 [RFC3187], 3044 [RFC3044] respectively. 95 The original registration procedure for Uniform Resource Name (URN) 96 namespaces [RFC3406] required IETF Consensus for formal ones. That 97 requirement discouraged some registrations and increased the risk for 98 problems that could occur as a result. Those potential problems 99 included the possibility of the same name being used to identify 100 different namespaces with different rules. The requirements have now 101 been changed [RFC3406bis] to adopt a different model that focuses 102 more on attempting to get all namespaces that follow the syntax of 103 formal ones registered, with as much information collected as a 104 possible consistent with that goal. This document specifies IANA 105 instructions to adapt selected existing registrations to the new 106 model and obsoletes the RFCs that specify the namespaces for 107 International Standard Serial Numbers (ISSNs) [RFC3044], 108 International Standard Book Numbers (ISBNs) [RFC3187] to eliminate 109 any ambiguity about the status of new templates and updated 110 registrations. 112 An updated version of the specification for the namespace for 113 National Bibliography Numbers (NBNs) [RFC3188] will be issued 114 separately. NBN is not a formal standard and RFC 3188 is the only 115 formal document which specifies its scope. The intention is to 116 modernize the existing namespace registration so that it specifies 117 the identifier and provides examples of its use, while the actual 118 namespace registration will be done according to the new practice. 120 2. Obsoleting Older Registration RFCs 122 The existing RFCs that describe URN namespaces for ISSNs (RFC 3044) 123 and ISBNs (RFC 3187) should be identified as "Historic" immediately 124 after this document is approved and the new registration templates 125 for those namespaces are submitted and incorporated into the URN 126 Namespace registry by IANA. 128 [[Note in draft: The more information that can be supplied in the 129 template or references from it, the better. But, if there is 130 information in the now-expired Internet-Drafts (draft-ietf-urnbis- 131 rfc3187bis-isbn-urn, draft-ietf-urnbis-rfc3044bis-issn-urn) that 132 should be captured somewhere and that doesn't fit naturally in the 133 template, the discussion below is probably a reasonable place to put 134 it.]] 136 Those updated templates reflect not only new formats but substantive 137 changes to the definitions of the namespaces, as described in the 138 following subsections. 140 2.1. ISBN URN Changes 142 The revised ISBN namespace reflects the updated version of the ISO 143 Standard for ISBNs, ISO 2108:2005 [ISO-ISBN-b] and allows for the use 144 of both the ten character numbers described in RFC 3187 and the 145 earlier ISO 2108:1992 [ISO-ISBN-a] (known as ISBN-10) and the 146 expanded ones of the revised standard (known as ISBN-13). 148 2.2. ISSN URN Changes 150 The ISSN namespace is also updated to reflect changes between the 151 ISSN Standard when RFC 3044 was written and the newest, 2007 version 152 [ISO-ISSN]. 154 3. IANA Considerations 156 IANA is requested to update the registry entries for URN ISSNs, 157 ISBNs, and NRNs to reflect the new, RFC 3406bis-complaint templates 158 as soon as they are available and to no longer reference the now- 159 historic RFCs. Other registrations and templates conforming to the 160 newer rules may be substituted for the older ones when they are 161 available. However, neither this document nor RFC 3406bis 162 invalidates existing registrations other than those listed above, so 163 IANA needs to be prepared to maintain a registry whose contents 164 reflect both old and new templates. 166 4. Security Considerations 168 While particular URN namespaces and their registrations might 169 conceivably have security implications, this specification merely 170 specifies a transition in a registration procedure and does not have 171 such implications. The security implications associated with 172 particular namespaces are expected to be listed in registration 173 templates as specified in RFC 3406bis. 175 5. Acknowledgements 177 This document draws heavily on discussions in the IETF URNbis Working 178 Group in the second and third quarters of 2013, particularly during 179 IETF 87 in August 2013, and on informal discussions during the 180 plenary meeting of ISO TC 46 in June 2013. The efforts of those who 181 participated in those discussions are greatly appreciated. It also 182 draws on internet-drafts that were developed to update the older 183 registrations before that approach was replaced by the new extended 184 template model. Those drafts were prepared by Pierre Godefroy, Juha 185 Hakala, Alfred Hoenes, and Maarit Huttunen. 187 6. Contributors 189 Alfred Hoenes was the editor and co-author of two of the documents 190 from which this one is, in part, derived. This document would not 191 have been possible without his contributions. 193 7. References 195 7.1. Normative References 197 [RFC3406bis] 198 Saint-Andre, P., Ed., Daigle, L., van Gulik, D., Iannella, 199 R., and P. Faltstrom, "Uniform Resource Name (URN) 200 Namespace Definition Mechanisms", August 2013, . 204 7.2. Informative References 206 [ISO-ISBN-a] 207 ISO, "Information and documentation - The International 208 Standard Book Number (ISBN)", ISO 2180:1992, 1992. 210 [ISO-ISBN-b] 211 ISO, "Information and documentation - The International 212 Standard Book Number (ISBN)", ISO 2180:2005, 2005. 214 [ISO-ISSN] 215 ISO, "Information and documentation - International 216 standard serial number (ISSN)", ISO 3297:2007, 2007. 218 [RFC2288] Lynch, C., Preston, C., and R. Jr, "Using Existing 219 Bibliographic Identifiers as Uniform Resource Names", RFC 220 2288, February 1998. 222 [RFC2611] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, 223 "URN Namespace Definition Mechanisms", BCP 33, RFC 2611, 224 June 1999. 226 [RFC3044] Rozenfeld, S., "Using The ISSN (International Serial 227 Standard Number) as URN (Uniform Resource Names) within an 228 ISSN-URN Namespace", RFC 3044, January 2001. 230 [RFC3187] Hakala, J. and H. Walravens, "Using International Standard 231 Book Numbers as Uniform Resource Names", RFC 3187, October 232 2001. 234 [RFC3188] Hakala, J., "Using National Bibliography Numbers as 235 Uniform Resource Names", RFC 3188, October 2001. 237 [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, 238 "Uniform Resource Names (URN) Namespace Definition 239 Mechanisms", BCP 66, RFC 3406, October 2002. 241 Authors' Addresses 243 John C Klensin 244 1770 Massachusetts Ave, Ste 322 245 Cambridge, MA 02140 246 USA 248 Phone: +1 617 245 1457 249 Email: john-ietf@jck.com 251 Juha Hakala 252 The National Library of Finland 253 P.O. Box 15, Helsinki University 254 Helsinki, MA FIN-00014 255 Finland 257 Email: juha.hakala@helsinki.fi