1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
|
<pre>Internet Engineering Task Force (IETF) C. Ishikawa
Request for Comments: 6588 YRP Ubiquitous Networking Lab
Category: Informational April 2012
ISSN: 2070-1721
<span class="h1">A URN Namespace for ucode</span>
Abstract
This document describes a Uniform Resource Name (URN) namespace for
ucode, an identifier system for objects and places. ucode technology
is used in many applications, and this document provides a URN
namespace for ucode to enable its use in Internet-related devices and
software.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6588">http://www.rfc-editor.org/info/rfc6588</a>.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Ishikawa Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6588">RFC 6588</a> URN Namespace for ucode April 2012</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
ucode [<a href="#ref-UCODE" title=""ucode: Ubiquitous Code"">UCODE</a>] is an identifier to be stored in many types of tags
(not limited to Radio Frequency Identification (RFID) tags). Its
allocation and management is handled by the Ubiquitous ID Center
[<a href="#ref-UIDC">UIDC</a>]. The embedding of ucode in many types of tags (RFID tags,
optical code, infrared markers, and even sound source) is also
specified by the Ubiquitous ID Center.
The basic length of ucode is 128 bits, but it is extensible in units
of 128 bits if necessary.
ucode has been devised to identify objects and places where existing
standards do not fit the application needs or the scope of the
applications or where the allocation policy of existing standards is
too limited for Small and Medium Enterprises (SMEs), small-scale
research laboratories at academic institutions, or individual users.
Applications that use ucode take advantage of the Internet
extensively. Use of ucode is open to anybody. Those who wish to
have ucode allocated can do so either by having ucode subspace
allocated to them directly from the Ubiquitous ID Center [<a href="#ref-UIDC">UIDC</a>] or by
obtaining tags that have pre-stored ucode from so called "providers"
[<a href="#ref-UCDMIP" title=""ucode Management Implementing Procedures"">UCDMIP</a>]. Such tags are certified as ucode tags [<a href="#ref-UIDTAG" title=""ucode Tag Architecture"">UIDTAG</a>], and the
reader specifications are published so that there will be many
readers available for such tags.
By having a URN for ucode, we can facilitate the use of ucode in many
Internet-related devices and software for the benefit of existing and
future users of ucode and people who will access such tags attached
to objects and places. Since an application based on ucode can run
across organizational boundaries and spread across regions and
countries, a formal URN Namespace Identifier (NID) assignment for
'ucode' is requested.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. 'ucode' Registration Template</span>
Namespace ID:
'ucode' requested
Registration Information:
Registration Version Number: 1
Registration Date: 2011-12-21
<span class="grey">Ishikawa Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6588">RFC 6588</a> URN Namespace for ucode April 2012</span>
Declared registrant of the namespace:
T-Engine Forum
2-20-1, Nishi-Gotanda
Shinagawa, Tokyo, 141-0031
Japan
office@t-engine.org
Tel: +81-3-5437-0572
Declaration of syntactic structure:
The structure of the namespace for 'ucode' using the hexadecimal
representation of the identifier is as follows using ABNF [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>].
UCODE-URN = "urn:ucode:" ucode-name
ucode-name = "_" ucode-number
ucode-number = 1*ucode-value
ucode-value = 32HEXDIG
HEXDIG = DIGIT / "A" / "B" / "C" / "D" / "E" / "F"
DIGIT = %x30-39
; 0-9
NOTE 1: "1*" at the start of the ucode-number definition is not a
typo. Although the currently used ucode [<a href="#ref-UCODE" title=""ucode: Ubiquitous Code"">UCODE</a>] is 128 bits (16
octets), thus requiring 32 hexadecimal characters to represent
serially, ucode is designed to be extensible in increments of 128
bits. So, in the distant future, we may need to repeat the chunks of
128 bits. This is why "1*" precedes ucode-value.
NOTE 2: ucode-name starts with a "_" because it is also intended to
be used as an identifier for XML [<a href="#ref-W3CXML" title=""Extensible Markup Language (XML) 1.1"">W3CXML</a>]. Because an XML tag can't
start with a digit, an "_" (underscore) is inserted at the beginning
to make sure ucode-name starts with a non-digit. For example, the
128-bit ucode value 0123456789ABCDEF0123456789ABCDEF, expressed in a
series of hexadecimal digits, is as follows:
urn:ucode:_0123456789ABCDEF0123456789ABCDEF
Relevant ancillary documentation:
ucode, the identifier expressed by ucode-number, is managed by the
Ubiquitous ID Center [<a href="#ref-UIDC">UIDC</a>], which is a sub-organization of the
T-Engine Forum [<a href="#ref-TEF">TEF</a>]. The document "Ubiquitous Code: ucode" [<a href="#ref-UCODE" title=""ucode: Ubiquitous Code"">UCODE</a>]
defines this identifier system.
<span class="grey">Ishikawa Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6588">RFC 6588</a> URN Namespace for ucode April 2012</span>
Identifier uniqueness considerations:
The 'ucode' namespace is managed by the Ubiquitous ID Center. The
Ubiquitous ID Center assigns the identifier, ucode, in such a way
that the uniqueness of the 'ucode' namespace will be maintained.
Identifier persistence considerations:
The assignment process guarantees that names are not reassigned and
that the binding between the name and its resource is permanent,
regardless of any standards or organizational changes or the
assignment period.
Process of identifier assignment:
Names are assigned by the Ubiquitous ID Center and by any entities
that are sub-delegated by the Ubiquitous ID Center. This assignment
process is based on "ucode Management Implementing Procedures"
[<a href="#ref-UCDMIP" title=""ucode Management Implementing Procedures"">UCDMIP</a>] established by the Ubiquitous ID Center.
Process of identifier resolution:
The process of identifier resolution is currently based on the "ucode
Resolution Protocol" [<a href="#ref-UCSURP" title=""Simplified ucode Resolution Protocol"">UCSURP</a>]. It will be enhanced by using newer
recommendations from ITU-T and/or standards from ISO.
Rules for lexical equivalence:
The entire UCODE-URN is case-sensitive.
NOTE: This is an additional restriction imposed on the ucode
namespace by the requirements of some major applications of ucode in
existence. Only capital "A", "B", "C", ..., "F" are allowed as part
of hexadecimal characters.
Conformance with URN syntax:
There are no special reserved characters. The URN of this namespace
conforms to <a href="./rfc2141">RFC 2141</a> [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>] and <a href="./rfc3986">RFC 3986</a> [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>].
Validation mechanism:
No special considerations.
Scope:
Global.
<span class="grey">Ishikawa Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6588">RFC 6588</a> URN Namespace for ucode April 2012</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Considerations</span>
One URN Namespace registration for 'ucode' (46) has been entered
into the IANA "Formal URN Namespaces" sub-registry for URN NIDs.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Namespace Considerations</span>
ucode, the identifier expressed by ucode-number, is a unique
identification number to identify a tangible object or a place.
Additionally, ucode can be assigned to "content" or "information"
that does not exist in the real world or a "concept" that is yet more
abstract.
ucode has been devised to identify objects and places where existing
standards do not fit the application needs or the scope of the
applications or where the allocation policy of existing standards is
too limited for SMEs, small-scale research laboratories at academic
institutions, or individual users.
ucode is only an identification number, and its value (or its sub-
bitfields) does not contain any pre-assigned meaning. Any relevant
information about the object or place to which a ucode is assigned is
stored in a data server that can be reached after a "resolution
process" [<a href="#ref-UCSURP" title=""Simplified ucode Resolution Protocol"">UCSURP</a>]. This resolution process usually occurs over the
Internet.
ucode can be assigned to an object to be identified regardless of the
type of application. ucode is expected to be stored in any kind of
tags (2D optical code, RFID, etc.), and it provides a framework where
anyone can obtain unique numbers for identification purposes.
ucode has been designed to provide the services outlined in ITU-T
Recommendation F.771 [<a href="#ref-ITU-T-F771" title=""Service description and requirements for multimedia information access triggered by tag-based identification"">ITU-T-F771</a>] and to operate in the framework of
ITU-T Recommendation H.621 [<a href="#ref-ITU-T-H621" title=""Architecture of a system for multimedia information access triggered by tag-based identification"">ITU-T-H621</a>].
ucode architecture is general enough to cover many applications for
the users.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Community Considerations</span>
This namespace enables ucode to be stored in tags that are designed
to store URN. Also, ucode-related information can be described as
metadata using the URN namespace. Thus, the namespace facilitates
the exchange of descriptions regarding objects and places among
multiple organizations.
<span class="grey">Ishikawa Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6588">RFC 6588</a> URN Namespace for ucode April 2012</span>
It is expected that many small-scale providers will offer ucode tags
to small users and that large scale providers will hand out millions
of tags to users.
The resolution servers and applications will be available to general
users with appropriate access control over the Internet. The
published specification for resolver and access services for 'ucode'
allows the creation of client software for many types of computers
including small mobile terminals and ever-popular smartphones.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
There are no additional security considerations other than those
normally associated with the use and resolution of URNs in general.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
[<a id="ref-UCODE">UCODE</a>] T-Engine Forum, Ubiquitous ID Center, "ucode: Ubiquitous
Code", UID-00010,
<<a href="http://www.uidcenter.org/spec#UID-00010">http://www.uidcenter.org/spec#UID-00010</a>>.
[<a id="ref-UCDMIP">UCDMIP</a>] T-Engine Forum, Ubiquitous ID Center, "ucode Management
Implementing Procedures", UID-00034,
<<a href="http://www.uidcenter.org/spec#UID-00034">http://www.uidcenter.org/spec#UID-00034</a>>.
[<a id="ref-UCSURP">UCSURP</a>] T-Engine Forum, Ubiquitous ID Center, "Simplified ucode
Resolution Protocol", UID-00005,
<<a href="http://www.uidcenter.org/spec#UID-00005">http://www.uidcenter.org/spec#UID-00005</a>>.
[<a id="ref-UIDTAG">UIDTAG</a>] T-Engine Forum, Ubiquitous ID Center, "ucode Tag
Architecture", UID-00017,
<<a href="http://www.uidcenter.org/spec#UID-00017">http://www.uidcenter.org/spec#UID-00017</a>>.
[<a id="ref-RFC2141">RFC2141</a>] Moats, R., "URN Syntax", <a href="./rfc2141">RFC 2141</a>, May 1997.
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, <a href="./rfc3986">RFC</a>
<a href="./rfc3986">3986</a>, January 2005.
[<a id="ref-RFC5234">RFC5234</a>] Crocker, D., Ed., and P. Overell, "Augmented BNF for
Syntax Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>, January
2008.
<span class="grey">Ishikawa Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6588">RFC 6588</a> URN Namespace for ucode April 2012</span>
[<a id="ref-ITU-T-F771">ITU-T-F771</a>] ITU-T, "Service description and requirements for
multimedia information access triggered by tag-based
identification", ITU-T Recommendation F.771,
<<a href="http://www.itu.int/rec/T-REC-F.771-200808-I">http://www.itu.int/rec/T-REC-F.771-200808-I</a>>.
[<a id="ref-ITU-T-H621">ITU-T-H621</a>] ITU-T, "Architecture of a system for multimedia
information access triggered by tag-based
identification", ITU-T Recommendation H.621,
<<a href="http://www.itu.int/rec/T-REC-H.621-200808-I">http://www.itu.int/rec/T-REC-H.621-200808-I</a>>.
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a> Informative References</span>
[<a id="ref-W3CXML">W3CXML</a>] W3C, "Extensible Markup Language (XML) 1.1",
<<a href="http://www.w3.org/TR/xml11/">http://www.w3.org/TR/xml11/</a>>.
[<a id="ref-UIDC">UIDC</a>] Ubiquitous ID Center, <<a href="http://www.uidcenter.org/">http://www.uidcenter.org/</a>>.
[<a id="ref-TEF">TEF</a>] T-Engine Forum, <<a href="http://www.t-engine.org/">http://www.t-engine.org/</a>>.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgments</span>
The author would like to thank Peter Saint-Andre, the Document
Shepherd/Responsible Area Director for this document, for providing
valuable suggestions. The author would also like to thank the
following people who helped to improve this document:
Adrian Farrel
David Harrington
Pete Resnick
Stephen Farrel
Ted Hardie
Wesley Eddy
The author would also like to thank the members of T-Engine Forum who
have built prototype and real-world applications using ucode and
offered valuable feedback. Application examples from these members
can be found on the Ubiquitous ID Center web site [<a href="#ref-UIDC">UIDC</a>] and on
www.youtube.com (search for "uidcenter" without the quotes).
<span class="grey">Ishikawa Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6588">RFC 6588</a> URN Namespace for ucode April 2012</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Contributors</span>
Ken Sakamura
Noboru Koshizuka
Katsunori Shindo
Tomonori Usaka
Past and current members of the uID architecture group at the
University of Tokyo and the YRP Ubiquitous Networking Laboratory (YRP
UNL)
Author's Address
Chiaki Ishikawa
YRP Ubiquitous Networking Laboratory
2-20-1, Nishi-Gotanda
Shinagawa, Tokyo, 141-0031
Japan
Tel: +81-3-5437-2270
FAX: +81-3-5437-2271
EMail: chiaki.ishikawa@ubin.jp
Ishikawa Informational [Page 8]
</pre>
|
