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>Network Working Group M. Mealling
Request for Comments: 3553 VeriSign
BCP: 73 L. Masinter
Category: Best Current Practice Adobe Systems
T. Hardie
Qualcomm
G. Klyne
Nine by Nine
June 2003
<span class="h1">An IETF URN Sub-namespace for Registered Protocol Parameters</span>
Status of this Memo
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
This document describes a new sub-delegation for the 'ietf' URN
namespace for registered protocol items. The 'ietf' URN namespace is
defined in <a href="./rfc2648">RFC 2648</a> as a root for persistent URIs that refer to
IETF-defined resources.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
From time to time IETF standards require the registration of various
protocol elements in well known central repository. The Internet
Assigned Numbers Authority maintains this central repository and
takes direction from the IETF on what, how and when to add items to
it. The IANA maintains lists of items such as all assigned port
numbers, MIME media types, enterprise numbers, etc.
Over time there has developed a need to be able to reference these
elements as URIs in various schema. In the past this was done in a
very ad hoc way that easily led to interoperability problems. This
document creates a new sub-delegation below the "ietf" [<a href="#ref-2" title=""A URN Namespace for IETF Documents"">2</a>]URN
namespace [<a href="#ref-1" title=""URN Syntax"">1</a>] called 'params' which acts as a standardized mechanism
for naming the items registered for IETF standards. Any assignments
below that are specified in an RFC according to the IETF consensus
process and which include the template found in <a href="#section-4">Section 4</a>.
<span class="grey">Mealling, et. al. Best Current Practice [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc3553">RFC 3553</a> IANA URN Namespace June 2003</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a>.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IETF Sub-namespace Specifics</span>
Sub-namespace name:
params
Declared registrant of the namespace:
The Internet Engineering Task Force
Declaration of structure:
The namespace is primarily opaque. The IANA, as operator of the
registry, may take suggestions for names to assign but they
reserve the right to assign whatever name they desire, within
guidelines set by the IESG. The colon character (":") is used to
denote a very limited concept of hierarchy. If a colon is present
then the items on both sides of it are valid names. In general,
if a name has a colon then the item on the left hand side
represents a class of those items that would contain other items
of that class. For example, a name can be assigned to the entire
list of DNS resource record type codes as well as for each
individual code. The URN for the list might look like this:
urn:ietf:params:dns:rr-type-codes
while the URN for the SOA records type code might look like this:
urn:ietf:params:dns:rr-type-codes:soa
Relevant ancillary documentation:
[<a href="#ref-3" title=""Uniform Resource Names (URN) Namespace Definition Mechanisms"">3</a>], [<a href="#ref-2" title=""A URN Namespace for IETF Documents"">2</a>], [<a href="#ref-1" title=""URN Syntax"">1</a>]
Identifier uniqueness considerations:
The IESG uses the IETF consensus process to ensure that
sub-namespaces generate unique names within that
sub-namespace. The IESG delegates to the IANA the task of
ensuring that the sub-namespace names themselves are unique.
Until and unless the IESG specifies differently, the IANA is
directed to ensure uniqueness by comparing the name to be assigned
<span class="grey">Mealling, et. al. Best Current Practice [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc3553">RFC 3553</a> IANA URN Namespace June 2003</span>
with the list of previously assigned names. In the case of a
conflict the IANA is to request a new string from the registrant
until the conflict is resolved.
Identifier persistence considerations:
Once a name has been allocated it MUST NOT be re-allocated for a
different purpose. The rules provided for assignments of values
within a sub-namespace MUST be constructed so that the meaning of
values cannot change. This registration mechanism is not
appropriate for naming values whose meaning may change over time.
If a value that changes over time the assignment MUST name the
container or concept that contains the value, not the value
itself. For example, if a parameter called 'foo' has a value that
changes over time, it is valid to create the name
'urn:ietf:params:foo-params:foo' that identifies that 'slot'. It
is not valid to actually create a name that contains that value
unless it is a persistent and unique value such as a version
number.
Process of identifier assignment:
Identifiers are assigned only after a particular protocol element
or number has been registered with the IANA using standard
policies and procedures, or documented in an RFC describing a
standards track protocol. This means that the 'gating' function
for assignment is the "IETF Consensus" process documented in <a href="./rfc2434">RFC</a>
<a href="./rfc2434">2434</a> [<a href="#ref-4" title="">4</a>].
Process of identifier resolution:
At this time no resolution mechanism is defined.
Rules for Lexical Equivalence:
Lexical equivalence is achieved by exact string match according to
the rules for URN syntax found in <a href="./rfc2141">RFC 2141</a> [<a href="#ref-1" title=""URN Syntax"">1</a>]. Specifically, due
to the URN syntax definitions, the 'stringprep' standard found in
<a href="./rfc3454">RFC 3454</a> [<a href="#ref-7" title=""Preparation of Internationalized Strings ("">7</a>] does not apply.
Conformance with URN Syntax:
There are no additional characters reserved.
Validation mechanism:
None.
<span class="grey">Mealling, et. al. Best Current Practice [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc3553">RFC 3553</a> IANA URN Namespace June 2003</span>
Scope:
Global
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Assigning Names</span>
The creation of a new registry name will be simple for most flat
registries. The only required elements will be the registry name, a
reference to relevant documents, a statement about which
current/proposed document repositories contains the authoritative
data for the registry, and a statement specifying which element in
the registry is the value to be used in the URN. In most cases this
last element will be the index value assigned by the IANA.
More complex registries (DNS Parameters for example) will need to
repeat that information for any sub-namespaces. It should also be
clear as to whether or not a name is assigned to the sub-namespace
itself (i.e., is 'urn:ietf:params:dns:rr-types' valid by itself and
if so, what does it name?).
The template:
Registry name: -- The name of the sub-namespace. In many cases this
should be the same name that the IANA calls the registry itself.
Specification: -- Relevant IETF published documents that define the
registry and the items in it.
Repository: -- A pointer to the 'current' location of the registry in
the protocol parameters repository or the relevant RFCs that
document the items being named. This value will change over time
as the entity that maintains the repository moves files and or
fileservers. It is not meant as a permanent binding to the
filename but as a hint to the IANA for what the initial mapping
would be.
Index value: -- Description of how a registered value is to be
embedded in the URI form. This MUST include details of any
transformations that may be needed for the resulting string to
conform to URN syntax rules and any canonicalization needed so
that the case-sensitive string comparison yields the expected
equivalences.
The process for requesting that a URN be assigned is currently to put
the above template or a reference to it in the IANA considerations
section of the specifying document. Other more automated processes
may be proposed at a latter time if demand requires it.
<span class="grey">Mealling, et. al. Best Current Practice [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc3553">RFC 3553</a> IANA URN Namespace June 2003</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
None not already inherent to using URNs. Security considerations for
URNs in general can be found in <a href="./rfc2141">RFC 2141</a> [<a href="#ref-1" title=""URN Syntax"">1</a>]. Further security
considerations for one specific URN resolution method can be found in
Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform
Resource Identifiers (URI) Resolution Application (<a href="./rfc3404">RFC 3404</a>) [<a href="#ref-5" title=""Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)"">5</a>]
which is part of a series starting with Dynamic Delegation Discovery
System (DDDS) Part One: The Comprehensive DDDS (<a href="./rfc3401">RFC 3401</a>) [<a href="#ref-6" title=""Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS"">6</a>].
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
This document puts a new and significant burden on the IANA since it
may require an additional assignment process to happen for each new
IANA registry. To minimize the administrative burden on IANA, any
parameter namespace registration is very clear about the criteria for
inclusion in that namespace.
Defining a registry that fits the constraints of a URN namespace will
impose extra discipline that should take some of the guess-work about
creating and maintaining that registry.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Intellectual Property Statement</span>
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in <a href="https://www.rfc-editor.org/bcp/bcp11">BCP-11</a>. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
<span class="grey">Mealling, et. al. Best Current Practice [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc3553">RFC 3553</a> IANA URN Namespace June 2003</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Normative References</span>
[<a id="ref-1">1</a>] Moats, R., "URN Syntax", <a href="./rfc2141">RFC 2141</a>, May 1997.
[<a id="ref-2">2</a>] Moats, R., "A URN Namespace for IETF Documents", <a href="./rfc2648">RFC 2648</a>,
August 1999.
[<a id="ref-3">3</a>] Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom,
"Uniform Resource Names (URN) Namespace Definition Mechanisms",
<a href="https://www.rfc-editor.org/bcp/bcp66">BCP 66</a>, <a href="./rfc3406">RFC 3406</a>, October 2002.
[<a id="ref-4">4</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc2434">RFC 2434</a>, October 1998.
[<a id="ref-5">5</a>] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
Four: The Uniform Resource Identifiers (URI)", <a href="./rfc3404">RFC 3404</a>,
February 2002.
[<a id="ref-6">6</a>] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
One: The Comprehensive DDDS", <a href="./rfc3401">RFC 3401</a>, May 2002.
[<a id="ref-7">7</a>] Hoffman, P. and M. Blanchet, "Preparation of Internationalized
Strings ("stringprep")", <a href="./rfc3454">RFC 3454</a>, December 2002.
<span class="grey">Mealling, et. al. Best Current Practice [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc3553">RFC 3553</a> IANA URN Namespace June 2003</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Authors' Addresses</span>
Michael Mealling
VeriSign
21345 Ridgetop Circle
Sterling, VA 20166
US
EMail: michael@verisignlabs.com, michael@neonym.net
URI: <a href="http://www.verisign.com">http://www.verisign.com</a>
Larry Masinter
Adobe Systems Incorporated
345 Park Ave
San Jose, CA 95110
US
Phone: +1 408 536-3024
EMail: LMM@acm.org
URI: <a href="http://larry.masinter.net">http://larry.masinter.net</a>
Ted Hardie
Qualcomm, Inc.
675 Campbell Technology Parkway
Suite 200
Campbell, CA
U.S.A.
EMail: hardie@qualcomm.com
Graham Klyne
Nine by Nine
EMail: GK-IETF@ninebynine.org
URI: <a href="http://www.ninebynine.net/">http://www.ninebynine.net/</a>
<span class="grey">Mealling, et. al. Best Current Practice [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc3553">RFC 3553</a> IANA URN Namespace June 2003</span>
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Full Copyright Statement</span>
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Mealling, et. al. Best Current Practice [Page 8]
</pre>
|
