idnits 2.17.1 draft-sangug-uci-urn-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == The page length should not exceed 58 lines per page, but there was 5 longer pages, the longest (page 2) being 70 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 5 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. ** There is 1 instance of lines with control characters in the document. == There is 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 2004) is 7223 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: '1' is defined on line 240, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 247, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2141 (ref. '1') (Obsoleted by RFC 8141) ** Obsolete normative reference: RFC 2234 (ref. '2') (Obsoleted by RFC 4234) ** Obsolete normative reference: RFC 2611 (ref. '3') (Obsoleted by RFC 3406) Summary: 11 errors (**), 0 flaws (~~), 6 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Sang-ug Kang 3 Internet-Draft National Computerization Agency 4 Category: Informational July 2004 6 Using Universal Content Identifier as Uniform Resource Names 7 draft-sangug-uci-urn-00.txt 9 Status of this Memo 11 This memo provides information for the Internet community. It does 12 not specify an Internet standard of any kind. Distribution of this 13 memo is unlimited. 15 Copyright Notice 17 Copyright (C) The Internet Society (2004). All Rights Reserved. 19 Abstract 21 This document describes a Uniform Resource Name (URN) namespace for 22 the National Computerization Agency (NCA) for naming persistent 23 digital resources such as musics, videos, texts, images, e-books and 24 other types of digital resources produced or managed by NCA. 26 1. Introduction 28 NCA is a non-profit organization with a mandate to develop and 29 promote information infrastructure and manage public digital 30 contents in Korea and possibly worldwide. 32 NCA has been supervising digitalization projects with various 33 organizations. The contents involved in such projects include 34 millions of technical papers, cultural properties, educational 35 materials, scientific research reports. Those organizations manage 36 the digital contents in a standardized way set by NCA and provide 37 users with various content services via internet. 39 NCA wishes to issue globally unique and persistent IDs to digital 40 resources and assign relevant organizations as its registration 41 agencies under Universal Content Identifier (UCI) scheme. It is 42 beneficial for NCA, its registration agencies, and the value chain 43 players in e-commerce, to have the UCI URN namespace, under which all 44 the contents and components NCA produces and manages are digitally 45 registered, identified and resolved. 47 NCA has been developing and operating the UCI system that provides 48 registration, resolution, search, and administration functionalities. 49 The functionalities are going to be added and modified once the use 50 of UCI URN namespace is approved. NCA would like to assign unique, 51 permanent, and location-independent names based on the URNs for the 52 resources it produces or manages. See http://www.nca.or.kr/eindex.htm 53 for more information on NCA. 55 This namespace specification is for a formal namespace. 57 2. Specification Template 59 Namespace ID: 61 "UCI" 63 Registration Information: 65 Registration Version Number: 1 Registration Date: 2004-07-xx 67 Declared registrant of the namespace: 69 Name : Sang-ug Kang 70 Affiliation: National Computerization Agency 71 Address : NCA Bldg. 77 Mookyo-Dong, Chung-Ku, Seoul, Korea 72 Phone : +82 (2) 2131-0443 73 Email : 74 Web : or 76 Declaration of syntactic structure: 78 The Namespace specific string of all URNs assigned by NCA conforms 79 to the syntax defined in section 2.2. of RFC2141, "URN Syntax"[1]. 80 The syntax convention is described in the form of ABNF rules [2] 81 as the following. 83 UCI = prefix "-" instance *1(":" qualifier) 85 prefix = 1*(alphaDigit) *1(":" 1*(alphaDigit)) 86 *1("+" 1*(alphaDigit)) 87 instance = 1*(trans / "%" HEXDIG HEXDIG) 88 qualifier = head 1*(alphaDigit) *2("-" head 1*(alphaDigit)) 89 trans = alphaDigit / other / reserved 90 alphaDigit = ALPHA / DIGIT 91 head = "C" / "R" / "F" 92 other = "(" / ")" / "+" / "," / "-" / "." / "=" / "@" / 93 ";" / "$" / "_" / "!" / "*" / "'" 94 reserved = "%" / "/" / "?" / "#" 96 Category: Informational July 2004 98 The UCI identifier consists of two parts : prefix code and 99 content code. The content code is also divided into instance code 100 and qualifier code which is optional. A prefix code is given to a 101 registration agency, subordinate registration agency, and/or its 102 registrants such as 'G3000+music', 'I600', 'I500+paper' and so 103 forth. A content code is issued to each individual digital 104 resource such as 'cii90007', '8987409' and so on. 106 Relevant ancillary documentation: 108 None. 110 Identifier uniqueness considerations: 112 It is the responsibility of registration authority, or NCA, to 113 guarantee the uniqueness of identifiers and the names of 114 subordinate naming authorities. For example, a 115 software tool developed and used by NCA checks if a UCI identifier 116 is being reassigned and verifies that it is assigned to at most 117 one resource, during the registration process. 119 Identifier persistence considerations: 121 Registration Agencies are all eligible to maintain the usability 122 of the UCI URNs for a reasonably long period. As a government 123 sponsored organization, NCA will operate a backup service and 124 make an effort to find a substitute in case a registration agency 125 becomes out of operation. 127 Process of identifier assignment: 129 Assignment of UCI identifier is delegated to the registration 130 agencies. NCA appoints UCI registration agencies and provides its 131 namespace by assigning a unique registration agency code which is 132 a part of NSS. Followed by the authorized namespace, each 134 registration agency sets its own identifier scheme that conforms 135 to the UCI syntactic structure. 137 An UCI for a digital resource is issued by the registration agency, 138 upon a request of a regitrant. The following is an example 139 identifier. 141 e.g., urn:uci:I700-2987098 143 where, I700 is a registration agency code and 2987098 is an 144 identifier assigned to a digital content. 146 Category: Informational July 2004 148 Process for identifier resolution: 150 Resolution is controlled by NCA and its delegatees. The list of 151 UCI registration agency codes is maintained by the regitration 152 authority. Each registration agency maintains the list of 153 subordinate registrant codes and identifiers registered to the 154 registration agency. 156 Identifier resolution steps are as follows. 158 - (Step1)Global resolution : NCA resolves which RA is dealing with 159 the associated resource by parsing the registration agency code 160 of the UCI. 161 - (Step2) Local resolution : The corresponding RA parses and 162 resolves the rest of the identifier 164 The global resolution is performed by UCI resolution server that 165 is open to public. (Currently http://rootadmin.uci.or.kr:9000/ 166 {UCI identifier} will give you resolution results.) 168 Rules for Lexical Equivalence: 170 The "prefix" is case-insensitive. So there will not be two 171 registration agencies whose names differ only in case. 173 urn:uci:{prefix code}: 175 is case-insensitive for matches. Remainder of the identifier is 176 case-sensitive. 178 Conformance with URN Syntax: 180 The UCI syntax fully conforms to RFC2141 syntax rules for both NSS 181 and NID. 183 Validation mechanism: 185 Valid list of prefix code will be available via both on-line and 186 off-line upon request. The validity of the rest of identifier can 187 be offered via on-line service. (Currently at http://rootadmin. 188 uci.or.kr:9000/{UCI identifier} by typing a query UCI identifier) 190 Scope: 192 Global. 194 Category: Informational July 2004 196 3. Security Considerations 198 There are no additional security considerations beyond those 199 normally associated with the use and resolution of URNs in general. 201 4. Namespace Considerations 203 The Korean government has been funding the UCI project with the 204 vision that it will be an essential component in realizing 205 interoperability of digital contents owned by individual institutes 206 and organizations. The resolution service provided by NCA and its 207 registration agencies via networks will play a central role in 208 achieving such a goal. Moreover, the resolution service is open to 209 the public without discrimination. 211 The assignment and use of identifiers is performed according to the 212 rules established by NCA. It abides by the URN requirements and 213 syntax. Within a UCI namespace, a registration agency manages 214 subordinate namespaces and maintains the metadata of digital 215 contents. 217 For making the service available to the public, a global resolution 218 service is run by NCA through a service server and local resolution 219 service is provided by the corresponding registration agency. 221 5. Community Considerations 223 The assignment and use of identifiers within the namespace are open 224 and the related rule is established by NCA. Registration agencies 225 are evaluated and selected fairly and shall have the responsibility 226 for processing registrant's requests for registering digital 227 contents. Registration authority and registration agencies shall 228 operate resolution servers for UCI namespace and subordinate 229 namespaces, respectively. Digital content users can access to the 230 resolution servers to fetch resolution results. The reference 231 software is developed and resolution servers are now in operation. 233 6. IANA Considerations 235 This document requests the registration of the "UCI" namespace in 236 the IANA registry of URN NIDs. 238 7. Normative References 240 [1] Moats, R., "URN Syntax", RFC 2141, May 1997. 242 [2] Crocker, D. and P. Overell, "Augmented BNF for Syntax 243 Specifications: ABNF", RFC 2234, November 1997. 245 Category: Informational July 2004 247 [3] Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom, "URN 248 Namespace Definition Mechanisms", BCP 33, RFC 2611, June 1999. 250 8. Authors' Addresses 252 Kang, Sang-ug 253 NCA Bldg. 77 Mookyo-Dong, 254 Joong-Ku, Seoul, 255 Korea 257 Phone: 82-2-2131-0443 258 EMail: sukang@nca.or.kr 260 9. Full Copyright Statement 262 Copyright (C) The Internet Society (2004). All Rights Reserved. 264 This document and translations of it may be copied and furnished to 265 others, and derivative works that comment on or otherwise explain it 266 or assist in its implementation may be prepared, copied, published 267 and distributed, in whole or in part, without restriction of any 268 kind, provided that the above copyright notice and this paragraph are 269 included on all such copies and derivative works. However, this 270 document itself may not be modified in any way, such as by removing 271 the copyright notice or references to the Internet Society or other 272 Internet organizations, except as needed for the purpose of 273 developing Internet standards in which case the procedures for 274 copyrights defined in the Internet Standards process must be 275 followed, or as required to translate it into languages other than 276 English. 278 The limited permissions granted above are perpetual and will not be 279 revoked by the Internet Society or its successors or assignees. 281 This document and the information contained herein is provided on an 282 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 283 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 284 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 285 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 286 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 288 Acknowledgement 290 Funding for the RFC Editor function is currently provided by the 291 Internet Society.