idnits 2.17.1 draft-sangug-uci-urn-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3667, Section 5.1 on line 41. -- Found old boilerplate from RFC 3978, Section 5.1.a on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 314. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document seems to lack an RFC 3979 Section 5, para. 1 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 2 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 3 IPR Disclosure Invitation. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 6 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 2 instances of too long lines in the document, the longest one being 1 character in excess of 72. == There are 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 (Feburuary 2005) is 7034 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: '1' is defined on line 265, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 270, 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: 13 errors (**), 0 flaws (~~), 6 warnings (==), 5 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 Expires: July 1, 2005 Feburuary 2005 6 Using Universal Content Identifier as Uniform Resource Names 7 draft-sangug-uci-urn-01.txt 9 Status of this Memo 11 This document is an Internet-Draft and is subject to all provisions 12 of section 3 of RFC 3667. By submitting this Internet-Draft, each 13 author represents that any applicable patent or other IPR claims of 14 which he or she is aware have been or will be disclosed, and any of 15 which he or she become aware will be disclosed, in accordance with 16 RFC 3668. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as 21 Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/1id-abstracts.html 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html" 34 This Internet-Draft will expire on July 1, 2005. 36 Intellectual Property Rights (IPR) Statement 38 By submitting this Internet-Draft, I certify that any applicable 39 patent or other IPR claims of which I am aware have been disclosed, or 40 will be disclosed, and any of which I become aware will be disclosed, 41 in accordance with RFC 3668. 43 Abstract 45 This document describes a Uniform Resource Name (URN) namespace for 46 the National Computerization Agency (NCA) for naming persistent 47 digital resources such as musics, videos, texts, images, e-books and 48 other types of digital resources produced or managed by NCA. 50 1. Introduction 52 NCA is a non-profit organization with a mandate to develop and 53 promote information infrastructure and manage public digital 54 contents in Korea and possibly worldwide. 55 NCA has been supervising digitalization projects with various 56 organizations. The contents involved in such projects include 57 millions of technical papers, cultural properties, educational 58 materials, scientific research reports. Those organizations manage 59 the digital contents in a standardized way set by NCA and provide 60 users with various content services via internet. 62 NCA wishes to issue globally unique and persistent IDs to digital 63 resources and assign relevant organizations as its registration 64 agencies under Universal Content Identifier (UCI) scheme. It is 65 beneficial for NCA, its registration agencies, and the value chain 66 players in e-commerce, to have the UCI URN namespace, under which all 67 the contents and components NCA produces and manages are digitally 68 registered, identified and resolved. 70 NCA has been developing and operating the UCI system that provides 71 registration, resolution, search, and administration functionalities. 72 The functionalities are going to be added and modified once the use 73 of UCI URN namespace is approved. NCA would like to assign unique, 74 permanent, and location-independent names based on the URNs for the 75 resources it produces or manages. See http://www.nca.or.kr/eindex.htm 76 for more information on NCA. 78 This namespace specification is for a formal namespace. 80 2. Specification Template 82 Namespace ID: 84 "UCI" 86 Registration Information: 88 Registration Version Number: 1 Registration Date: 2004-07-xx 90 Declared registrant of the namespace: 92 Name : Sang-ug Kang 93 Affiliation: National Computerization Agency 94 Address : NCA Bldg. 77 Mookyo-Dong, Chung-Ku, Seoul, Korea 95 Phone : +82 (2) 2131-0443 96 Email : 97 Web : or 99 Expires: July 1, 2005 Feburuary 2005 101 Declaration of syntactic structure: 103 The Namespace specific string of all URNs assigned by NCA conforms 104 to the syntax defined in section 2.2. of RFC2141, "URN Syntax"[1]. 105 The syntax convention is described in the form of ABNF rules [2] 106 as the following. 108 UCI = prefix "-" instance *1(":" qualifier) 110 prefix = 1*(alphaDigit) *1(":" 1*(alphaDigit)) 111 *1("+" 1*(alphaDigit)) 112 instance = 1*(trans / "%" HEXDIG HEXDIG) 113 qualifier = head 1*(alphaDigit) *2("-" head 1*(alphaDigit)) 114 trans = alphaDigit / other 115 alphaDigit = ALPHA / DIGIT 116 head = "C" / "R" / "F" 117 other = "(" / ")" / "+" / "," / "-" / "." / "=" / "@" / 118 ";" / "$" / "_" / "!" / "*" / "'" 119 reserved = "%" / "/" / "?" / "#" 121 The UCI identifier consists of two parts : prefix code and 122 content code. The content code is also divided into instance code 123 and qualifier code which is optional. A prefix code is given to a 124 registration agency, subordinate registration agency, and/or its 125 registrants such as 'G3000+music', 'I600', 'I500+paper' and so 126 forth. A content code is issued to each individual digital 127 resource such as 'cii90007', '8987409' and so on. 129 Relevant ancillary documentation: 131 None. 133 Identifier uniqueness considerations: 135 It is the responsibility of registration authority, or NCA, to 136 guarantee the uniqueness of identifiers and the names of 137 subordinate naming authorities. For example, a 138 software tool developed and used by NCA checks if a UCI identifier 139 is being reassigned and verifies that it is assigned to at most 140 one resource, during the registration process. 142 Identifier persistence considerations: 144 Registration Agencies are all eligible to maintain the usability 145 of the UCI URNs for a reasonably long period. As a government 146 sponsored organization, NCA will operate a backup service and 147 make an effort to find a substitute in case a registration agency 148 becomes out of operation. 150 Expires: July 1, 2005 Feburuary 2005 152 Process of identifier assignment: 154 Assignment of UCI identifier is delegated to the registration 155 agencies. NCA appoints UCI registration agencies and provides its 156 namespace by assigning a unique registration agency code which is 157 a part of NSS. Followed by the authorized namespace, each 158 registration agency sets its own identifier scheme that conforms 159 to the UCI syntactic structure. 161 An UCI for a digital resource is issued by the registration agency, 162 upon a request of a regitrant. The following is an example 163 identifier. 165 e.g., urn:uci:I700-2987098 167 where, I700 is a registration agency code and 2987098 is an 168 identifier assigned to a digital content. 170 Process for identifier resolution: 172 Resolution is controlled by NCA and its delegatees. The list of 173 UCI registration agency codes is maintained by the regitration 174 authority. Each registration agency maintains the list of 175 subordinate registrant codes and identifiers registered to the 176 registration agency. 178 Identifier resolution steps are as follows. 180 - (Step1)Global resolution : NCA resolves which RA is dealing with 181 the associated resource by parsing the registration agency code 182 of the UCI. 183 - (Step2) Local resolution : The corresponding RA parses and 184 resolves the rest of the identifier 186 The global resolution is performed by UCI resolution server that 187 is open to public. (Currently http://rootadmin.uci.or.kr:9000/ 188 {UCI identifier} will give you resolution results.) 190 Rules for Lexical Equivalence: 192 The "prefix" is case-insensitive. So there will not be two 193 registration agencies whose names differ only in case. 195 urn:uci:{prefix code}: 197 is case-insensitive for matches. Remainder of the identifier is 198 case-sensitive. 200 Expires: July 1, 2005 Feburuary 2005 202 Conformance with URN Syntax: 204 The UCI syntax fully conforms to RFC2141 syntax rules for both NSS 205 and NID. 207 Validation mechanism: 209 Valid list of prefix code will be available via both on-line and 210 off-line upon request. The validity of the rest of identifier can 211 be offered via on-line service. (Currently at http://rootadmin. 212 uci.or.kr:9000/{UCI identifier} by typing a query UCI identifier) 214 Scope: 216 Global. 218 3. Security Considerations 220 There are no additional security considerations beyond those 221 normally associated with the use and resolution of URNs in general. 223 4. Namespace Considerations 225 The Korean government has been funding the UCI project with the 226 vision that it will be an essential component in realizing 227 interoperability of digital contents owned by individual institutes 228 and organizations. The resolution service provided by NCA and its 229 registration agencies via networks will play a central role in 230 achieving such a goal. Moreover, the resolution service is open to 231 the public without discrimination. 233 The assignment and use of identifiers is performed according to the 234 rules established by NCA. It abides by the URN requirements and 235 syntax. Within a UCI namespace, a registration agency manages 236 subordinate namespaces and maintains the metadata of digital 237 contents. 239 For making the service available to the public, a global resolution 240 service is run by NCA through a service server and local resolution 241 service is provided by the corresponding registration agency. 243 5. Community Considerations 245 The assignment and use of identifiers within the namespace are open 246 and the related rule is established by NCA. Registration agencies 247 are evaluated and selected fairly and shall have the responsibility 248 for processing registrant's requests for registering digital 249 contents. Registration authority and registration agencies shall 250 operate resolution servers for UCI namespace and subordinate 252 Expires: July 1, 2005 Feburuary 2005 254 namespaces, respectively. Digital content users can access to the 255 resolution servers to fetch resolution results. The reference 256 software is developed and resolution servers are now in operation. 258 6. IANA Considerations 260 This document requests the registration of the "UCI" namespace in 261 the IANA registry of URN NIDs. 263 7. Normative References 265 [1] Moats, R., "URN Syntax", RFC 2141, May 1997. 267 [2] Crocker, D. and P. Overell, "Augmented BNF for Syntax 268 Specifications: ABNF", RFC 2234, November 1997. 270 [3] Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom, "URN 271 Namespace Definition Mechanisms", BCP 33, RFC 2611, June 1999. 273 8. Authors' Addresses 275 Kang, Sang-ug 276 NCA Bldg. 77 Mookyo-Dong, 277 Joong-Ku, Seoul, 278 Korea 280 Phone: 82-2-2131-0443 281 EMail: sukang@nca.or.kr 283 9. Full Copyright Statement 285 Copyright (C) The Internet Society (2005). This document is subject 286 to the rights, licenses and restrictions contained in BCP 78, and 287 except as set forth therein, the authors retain all their rights. 289 This document and translations of it may be copied and furnished to 290 others, and derivative works that comment on or otherwise explain it 291 or assist in its implementation may be prepared, copied, published 292 and distributed, in whole or in part, without restriction of any 293 kind, provided that the above copyright notice and this paragraph are 294 included on all such copies and derivative works. However, this 295 document itself may not be modified in any way, such as by removing 296 the copyright notice or references to the Internet Society or other 297 Internet organizations, except as needed for the purpose of 298 developing Internet standards in which case the procedures for 299 copyrights defined in the Internet Standards process must be 300 followed, or as required to translate it into languages other than 301 English. 303 Expires: July 1, 2005 Feburuary 2005 305 The limited permissions granted above are perpetual and will not be 306 revoked by the Internet Society or its successors or assignees. 308 This document and the information contained herein are provided on an 309 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 310 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 311 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 312 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 313 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 314 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 316 Acknowledgement 318 Funding for the RFC Editor function is currently provided by the 319 Internet Society.