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
|
<pre>Internet Engineering Task Force (IETF) A. Thomas
Request for Comments: 8069 IEEE
Category: Informational February 2017
ISSN: 2070-1721
<span class="h1">URN Namespace for IEEE</span>
Abstract
This document describes the Namespace Identifier (NID) 'ieee' for
Uniform Resource Names (URNs) used to identify resources published by
the Institute of Electrical and Electronics Engineers (IEEE). IEEE
specifies and manages resources that utilize this URN identification
model. Management activities for these and other resources types are
handled by the manager of the IEEE Registration Authority.
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="./rfc7841#section-2">Section 2 of RFC 7841</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/rfc8069">http://www.rfc-editor.org/info/rfc8069</a>.
Copyright Notice
Copyright (c) 2017 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">Thomas Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc8069">RFC 8069</a> URN Namespace for IEEE February 2017</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-1.1">1.1</a>. Terminology ................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. URN Specification for IEEE ......................................<a href="#page-3">3</a>
<a href="#section-3">3</a>. Examples ........................................................<a href="#page-5">5</a>
<a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-5">5</a>
<a href="#section-5">5</a>. IANA Considerations .............................................<a href="#page-5">5</a>
<a href="#section-6">6</a>. References ......................................................<a href="#page-5">5</a>
<a href="#section-6.1">6.1</a>. Normative References .......................................<a href="#page-5">5</a>
<a href="#section-6.2">6.2</a>. Informative References .....................................<a href="#page-6">6</a>
Acknowledgements ...................................................<a href="#page-6">6</a>
Author's Address ...................................................<a href="#page-6">6</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Institute of Electrical and Electronic Engineers (IEEE) is an
organization whose objectives include the educational and technical
advancement of electrical and electronic engineering,
telecommunications, computer engineering, and allied disciplines.
Within IEEE, standardization activities are organized into sponsors,
such as the LAN/MAN Standards Committee, and then working groups such
as 802.1 and 802.3. See <<a href="http://standards.ieee.org">http://standards.ieee.org</a>>.
As part of these specification efforts, there is a need to maintain
identifiers in a managed namespace that is unique and persistent. To
ensure that this namespace's uniqueness is absolute, a registration
of a specific URN Syntax [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>] Namespace Identifier (NID) for use
by IEEE is specified in this document, in full conformance with the
NID registration process specified in URN Namespace Definition
Mechanisms [<a href="./rfc3406" title=""Uniform Resource Names (URN) Namespace Definition Mechanisms"">RFC3406</a>].
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology</span>
+---------+---------------------------------------------------+
| Acronym | Meaning |
+---------+---------------------------------------------------+
| IEEE | Institute of Electrical and Electronics Engineers |
| | |
| NID | Namespace Identifier |
| | |
| URN | Uniform Resource Name |
+---------+---------------------------------------------------+
<span class="grey">Thomas Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc8069">RFC 8069</a> URN Namespace for IEEE February 2017</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. URN Specification for IEEE</span>
Namespace ID:
ieee
Registration information:
registration version number: 1
registration date: 2016-12-05
Declared registrant of the namespace:
Registering organization:
Name:
Institute of Electrical and Electronics Engineers
Address:
445 Hoes Lane
Piscataway, NJ 08854
USA
Designated contact person:
Angela Thomas
Role: Manager, IEEE Registration Authority
Email: ieee-registration-authority@ieee.org
Declaration of syntactic structure:
The Namespace Specific String (NSS) of all URNs that use the IEEE
NID will have the following structure:
urn:ieee:{IEEEresource}:{ResourceSpecificString}
where "IEEEresource" is a US-ASCII string that conforms to the URN
syntax requirements [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>] and defines a specific class of
resource type. Each resource type has a specific labeling scheme
that is covered by "ResourceSpecificString", which also conforms
to the naming requirements [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>].
IEEE maintains a registration authority, the IEEE Registration
Authority (IEEE RA), that will manage the assignment of
"IEEEresource" and the specific registration values assigned for
each resource class.
<span class="grey">Thomas Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc8069">RFC 8069</a> URN Namespace for IEEE February 2017</span>
Relevant ancillary documentation:
The IEEE Registration Authority (IEEE RA) provides information on
the registered resources and the registrations for each. More
information about this registry and the procedures to be followed
are available at:
<a href="http://standards.ieee.org/develop/regauth/tut/ieeeurn.pdf">http://standards.ieee.org/develop/regauth/tut/ieeeurn.pdf</a>
Identifier uniqueness considerations:
The IEEE RA will manage resources using the IEEE NID and will be
the authority for managing the resources and subsequent associated
strings. In the associated procedures, the IEEE RA will ensure
the uniqueness of the strings themselves or will permit secondary
responsibility for management of well-defined sub-trees.
Identifier persistence considerations:
IEEE will update documentation of the registered uses of the IEEE
NID as needed. This will be structured such that each
"IEEEresource" will have a separate description and registration
table.
The registration tables and information are published and
maintained by the IEEE RA on its web site.
Process of identifier assignment:
IEEE RA will provide procedures for registration of each type of
resource that it maintains.
Process for identifier resolution:
The namespace is not listed with an RDS; this is not relevant.
Rules for Lexical Equivalence:
The strings used as values for "IEEEresource" and
"ResourceSpecificString" are case insensitive.
Conformance with URN Syntax:
No special considerations.
<span class="grey">Thomas Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc8069">RFC 8069</a> URN Namespace for IEEE February 2017</span>
Validation mechanism:
None specified. URN assignment will be handled by procedures
implemented in support of IEEE activities.
Scope:
Global
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Examples</span>
The following examples are representative URNs that could be assigned
by the IEEE RA. While support for YANG [<a href="./rfc6020" title=""YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)"">RFC6020</a>] [<a href="./rfc7950" title=""The YANG 1.1 Data Modeling Language"">RFC7950</a>] was a
catalyst for the creation of the namespace, the following are not
necessarily the strings that would be assigned.
urn:ieee:std:802.5:yang
urn:ieee:foobar
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
There are no additional security considerations other than those
normally associated with the use and resolution of URNs in general,
which are described in Functional Requirements for URNs [<a href="./rfc1737" title=""Functional Requirements for Uniform Resource Names"">RFC1737</a>],
URN Syntax [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>], and URN Namespace Definition Mechanisms
[<a href="./rfc3406" title=""Uniform Resource Names (URN) Namespace Definition Mechanisms"">RFC3406</a>].
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
This document adds "ieee" to the "Formal URN Namespaces" registry
<<a href="http://www.iana.org/assignments/urn-namespaces">http://www.iana.org/assignments/urn-namespaces</a>>. This is the
defining document.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
[<a id="ref-RFC3406">RFC3406</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>, DOI 10.17487/RFC3406,
October 2002, <<a href="http://www.rfc-editor.org/info/rfc3406">http://www.rfc-editor.org/info/rfc3406</a>>.
[<a id="ref-RFC2141">RFC2141</a>] Moats, R., "URN Syntax", <a href="./rfc2141">RFC 2141</a>, DOI 10.17487/RFC2141,
May 1997, <<a href="http://www.rfc-editor.org/info/rfc2141">http://www.rfc-editor.org/info/rfc2141</a>>.
<span class="grey">Thomas Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc8069">RFC 8069</a> URN Namespace for IEEE February 2017</span>
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-RFC1737">RFC1737</a>] Sollins, K. and L. Masinter, "Functional Requirements for
Uniform Resource Names", <a href="./rfc1737">RFC 1737</a>, DOI 10.17487/RFC1737,
December 1994, <<a href="http://www.rfc-editor.org/info/rfc1737">http://www.rfc-editor.org/info/rfc1737</a>>.
[<a id="ref-RFC6020">RFC6020</a>] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", <a href="./rfc6020">RFC 6020</a>,
DOI 10.17487/RFC6020, October 2010,
<<a href="http://www.rfc-editor.org/info/rfc6020">http://www.rfc-editor.org/info/rfc6020</a>>.
[<a id="ref-RFC7950">RFC7950</a>] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
<a href="./rfc7950">RFC 7950</a>, DOI 10.17487/RFC7950, August 2016,
<<a href="http://www.rfc-editor.org/info/rfc7950">http://www.rfc-editor.org/info/rfc7950</a>>.
Acknowledgements
The IEEE Registration Authority Committee (RAC) is the oversight
committee for the IEEE Registration Authority. The content of this
document has been coordinated with the RAC. The technical contact
from the RAC was:
Glenn Parsons
Email: glenn.parsons@ericsson.com
Author's Address
Angela Thomas
IEEE Registration Authority
445 Hoes Lane
Piscataway, NJ 08854
USA
Phone: +1 732 465 6481
Email: a.n.thomas@ieee.org
Thomas Informational [Page 6]
</pre>
|
