idnits 2.17.1 draft-ishikawa-yrpunl-ucode-urn-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 : ---------------------------------------------------------------------------- ** There is 1 instance of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 17, 2012) is 4449 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 2141 (Obsoleted by RFC 8141) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Chiaki Ishikawa 3 urn (YRP UNL) 4 Intended Status: Informational 5 Expires: August 20, 2012 February 17, 2012 7 A URN Namespace For The ucode 8 draft-ishikawa-yrpunl-ucode-urn-03 10 Abstract 12 This document describes a URN (Uniform Resource Name) namespace for 13 ucode, an identifier system for objects and places. The ucode 14 technology is used in many applications, and this document provides a 15 URN namespace for ucode to enable its use in Internet-related devices 16 and software. 18 Status of this Memo 20 This Internet-Draft is submitted to IETF in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that 25 other groups may also distribute working documents as 26 Internet-Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/1id-abstracts.html 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html 39 Copyright and License Notice 41 Copyright (c) 2011 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 1 Introduction 56 ucode [UCODE] is an identifier to be stored in many types of tags 57 (not limited to RFID tags). Its allocation and management is handled 58 by Ubiquitous ID center [UIDC]. The embedding of ucode in many type 59 of tags (RFID tags, optical code, infrared markers, and even sound 60 source) is also specified by Ubiquitous ID center. 62 Basic length of ucode is 128 bits, but it is extensible in units of 63 128 bits if necessary. 65 ucode has been devised to identify objects and places where existing 66 standard doesn't fit the application needs or the scope of the 67 applications, or the allocation policy of existing standard is too 68 limited for small users or individual users. 70 Applications that use ucode take advantage of the Internet 71 extensively. Use of ucode is open to anybody. Those who wish to have 72 ucode allocated can do so either by having ucode subspace allocated 73 to them directly from Ubiquitous ID center or obtain tags that have 74 pre-stored ucode in them. Tags which can store ucode are certified 75 as ucode tags, and their reader specification is published so that 76 there will be many readers available for such tags. 78 By having URN (uniform resource name) for ucode, we can facilitate 79 the use of ucode in many Internet-related devices and software for 80 the benefit of existing and future users of ucode and people who will 81 access such tags attached to objects and places. Since the 82 application based on ucode can run across organizational boundaries, 83 and spread across regions and countries, we request a formal URN NID 84 assignment for 'ucode'. 86 2 'ucode' Registration Template 88 Namespace ID: 90 'ucode' requested 92 Registration Information: 94 Registration Version Number: 1 95 Registration Date: 2011-12-21 97 Declared registrant of the namespace: 99 T-Engine Forum 100 2-20-1, Nishi-Gotanda 101 Shinagawa, Tokyo, 141-0031, JAPAN 102 office@t-engine.org 103 Tel: +81-3-5437-0572 105 Declaration of syntactic structure: 107 The structure of the name space for 'ucode' using the hexadecimal 108 representation of identifier is as follows using ABNF [RFC5234]. 110 UCODE-URN = "urn:ucode:" ucode-name 111 ucode-name = "_" ucode-number 112 ucode-number = 1*ucode-value 113 ucode-value = 32HEXDIG 114 HEXDIG = DIGIT / "A" / "B" / "C" / "D" / "E" / "F" 115 DIGIT = %x30-39 116 ; 0-9 118 NOTE 1: "1*" at the start of ucode-number definition is not a typo. 119 Although the currently used ucode [UCODE] is 128-bits (16 octets), 120 thus requiring 32 hexadecimal characters to represent serially, ucode 121 is designed to be extensible in increment of 128 bits. So in the 122 distant future, we may need to repeat the chunks of 128 bits. This 123 is why "1*" precedes ucode-value. 125 NOTE 2: ucode-name start with a "_". The reason is as follows. This 126 ucode-name is also intended to be used as an identifier as a tag for 127 XML [W3CXML]. An XML tag can't start with a digit. We insert "_" at 128 the beginning to make sure ucode-name starts with a non-digit, 129 i.e.,"_" since ucode-number can start with a decimal digit. 131 An example 133 The 128-bit ucode value, 0123456789ABCDEF0123456789ABCDEF, expressed 134 in a series of hexadecimal digits, is expressed as follows: 136 urn:ucode:_0123456789ABCDEF0123456789ABCDEF 138 Relevant ancillary documentation: 140 ucode, the identifier expressed by ucode-number, is managed by 141 Ubiquitous ID Center [UIDC], which is a sub-organization of T-Engine 142 Forum [TEF]. "Ubiquitous Code: ucode" [UCODE] defines this 143 identifier system. 145 Identifier uniqueness considerations 147 'ucode' namespace is managed by Ubiquitous ID Center. Ubiquitous ID 148 Center assigns the identifier, ucode, in such a way that the 149 uniqueness of 'ucode' name space will be maintained. 151 Identifier persistence considerations: 153 The assignment process guarantees that names are not reassigned and 154 that the binding between the name and its resource is permanent, 155 regardless of any standards or organizational changes or the 156 assignment period. 158 Process of identifier assignment: 160 Names are assigned by Ubiquitous ID Center and by any entities that 161 are sub-delegated by Ubiquitous ID Center. This assignment process 162 is based on "ucode Management Implementing Procedures" [UCDMIP] 163 established by Ubiquitous ID Center. 165 Process of identifier resolution 167 The process of identifier resolution is currently based on "ucode 168 Resolution Protocol" [UCSURP]. It will be enhanced by using newer 169 Recommendations from ITU-T and/or standards from ISO. 171 Rules for lexical equivalence: 173 The entire UCODE-URN is case-sensitive. 175 Conformance with URN syntax: 177 There are no special reserved characters. The URN of this namespace 178 conform to RFC 2141 [RFC2141] and RFC 3986 [RFC3986]. 180 Validation mechanism: 182 No special consideration. 184 Scope: 186 Global. 188 3 IANA considerations 190 This document includes one URN Namespace registration request for 191 'ucode' to be entered into the IANA registry for URN NIDs. 193 4 Namespace considerations 195 ucode, the identifier expressed by ucode-number, is a unique 196 identification number to identify a tangible object or a place. 197 Additionally, ucode can be assigned to "content" or "information" 198 that does not exist in the real world, and a "concept" that is yet 199 more abstract. 201 ucode has been devised to identify objects and places where existing 202 standard doesn't fit the application needs or the scope of the 203 applications, or the allocation policy of existing standard is too 204 limited for SMEs (Small to Medium Enterprises), small scale research 205 laboratories at academic institutions, or individual users. 207 ucode is only an identification number, and its value (or its sub 208 bit-fields) does not contain any pre-assigned meaning. Any relevant 209 information about the object or place to which a ucode is assigned is 210 stored in a data server that can be reached after a "resolution 211 process" [UCSURP]. This resolution process usually occurs over the 212 Internet. 214 ucode can be assigned to an object to be identified regardless of the 215 type of application. ucode is expected to be stored in any kind of 216 tags (2D optical code, RFID, and other form of tags) and it provides 217 a framework where anyone can obtain unique numbers for identification 218 purposes. 220 ucode has been designed to provide the services outlined in ITU-T 221 recommendation, "Service description and requirements for multimedia 222 information access triggered by tag-based identification" [ITU-T- 223 F771] and to operate in the framework of "Architecture of a system 224 for multimedia information access triggered by tag-based 225 identification" [ITU-T-H621]. 227 ucode architecture is general enough to cover many applications for 228 the users. 230 5 Community Considerations 232 This namespace enables ucode to be stored in tags that can store URN, 233 and ucode related information to be described as metadata. This 234 allows exchange of descriptions regarding objects and places among 235 multiple organizations. 237 We expect many small-scale providers who will offer ucode tags to 238 small users as well as large scale providers who will hand out more 239 than millions of tags to users. 241 The resolution servers and applications will be available to general 242 users with appropriate access control over the Internet. The 243 published specification for resolver and access services for 'ucode' 244 allows the creation of client software for the many types of 245 computers including small mobile terminals and ever popular 246 smartphones. 248 6 Security Considerations 250 There are no additional security considerations other than those 251 normally associated with the use and resolution of URNs in general. 253 7 References 255 7.1 Normative References 257 [UCODE] T-Engine Forum, Ubiquitous ID Center. "ucode: Ubiquitous 258 Code", UID-00010, http://www.uidcenter.org/wp- 259 content/themes/wp.vicuna/pdf/UID-00010-01.A0.10_en.pdf 261 [UCDMIP] T-Engine Forum, Ubiquitous ID Center. "ucode Management 262 Implementing Procedures", UID-00034, 263 http://www.uidcenter.org/wp- 264 content/themes/wp.vicuna/pdf/UID-CO00034-01.A0.10_en.pdf 266 [UCSURP] T-Engine Forum, Ubiquitous ID Center. " Simplified ucode 267 Resolution Protocol", UID-00005, 268 http://www.uidcenter.org/wp- 269 content/themes/wp.vicuna/pdf/UID-00005-01.A0.01_en.pdf 271 [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. 273 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 274 Resource Identifier (URI): Generic Syntax", STD 66, 275 RFC 3986, January 2005. 277 [RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for 278 Syntax Specifications: ABNF", STD 68, RFC 5234, January 279 2008. 281 [ITU-T-F771] ITU-T, "Service description and requirements for 282 multimedia information access triggered by tag-based 283 identification", F.771, http://www.itu.int/rec/T-REC- 284 F.771-200808-I 286 [ITU-T-H621] ITU-T, "Architecture of a system for multimedia 287 information access triggered by tag-based identification", 288 H.621, http://www.itu.int/rec/T-REC-H.621-200808-I 290 7.2 Informative References 292 [W3CXML] W3C, "Extensible Markup Language (XML) 1.1", 293 http://www.w3.org/TR/xml11/ 295 [UIDC] Ubiquitous ID Center. http://www.uidcenter.org/ 297 [TEF] T-Engine Forum. http://www.t-engine.org/ 299 Contributors 301 Ken Sakamura 302 Noboru Koshizuka 303 Katsunori Shindo 304 Tomonori Usaka, and 305 other past and current members of uID architecture group at the 306 University of Tokyo and YRP Ubiquitous Networking Laboratory (YRP 307 UNL). 309 Acknowledgments 311 We would like to thank the members of T-Engine Forum who have built 312 applications using ucode and offered valuable feedback. (Application 313 examples from these members can be found at uidcenter web sites 314 [UIDC], and www.youtube.com: search for "uidcenter" without the 315 quotes.) 317 Authors' Addresses 319 Chiaki Ishikawa 320 YRP Ubiquitous Networking Laboratory 321 2-20-1, Nishi-Gotanda 322 Shinagawa, Tokyo, 141-0031, JAPAN 324 Tel: +81-3-5437-2270 325 FAX: +81-3-5437-2271 326 EMail: chiaki.ishikawa@ubin.jp