Subversion Repositories oidinfo_new_design

Rev

Details | Last modification | View Log | RSS feed

Rev Author Line No. Line
2 daniel-mar 1
<div id="global_content">
2
	<div id="table_faq">
3
		<table cellspacing="0" cellpadding="0" border="0" width="100%">
4
			<tr>
5
				<td width="2%" valign="top"></td>
6
				<td valign="top" colspan="3">
7
					<span class="page_title">Frequently Asked Questions</span>
8
					<p><a href="/helper"><img src="images/helper.png" alt="OID helper" height="55" width="55" border="0" align="middle"></a> 	Try to ask your question directly to your new <a href="http://www.pandorabots.com/pandora/talk?botid=c6bc63db9e377b4f">OID 	helper</a></p>
9
					<ol>
10
						<li>
11
							<a href="#1">What are the standards that define OIDs and the OID
12
								tree?</a>
13
						</li>
14
						<li><a href="#2">Which kind of objects can be referenced by OIDs?</a></li>
15
						<li><a href="#3">Where can I learn more about OIDs and their registration?</a></li>
16
						<li><a href="#4">How to add information to the OID repository?</a></li>
17
						<li><a href="#modify">How to modify the description of an OID?</a></li>
18
						<li>
19
							<a href="#6">How to delete an OID (or move it elsewhere in the OID
20
								tree)?</a>
21
						</li>
22
						<li>
23
							<a href="#7">How does the OID repository provided on this website
24
								compare with Harald Alvestrand's repository?</a>
25
						</li>
26
						<li><a href="#8">How to reference an OID description in this repository?</a></li>
27
						<li><a href="#9">How many OIDs are currently described in this repository?</a></li>
28
						<li><a href="#10">How to get an OID assigned?</a></li>
29
						<li>
30
							<a href="#national-RA">What decision needs be taken if a country
31
								wants a national Registration Authority for OIDs?</a>
32
						</li>
33
						<li>
34
							<a href="#12">Are there guidelines or standards regarding subsequent
35
								arcs of a country arc?</a>
36
						</li>
37
						<li><a href="#13">What is the Internet OID?</a></li>
38
						<li><a href="#14">Where does the dot notation for OIDs come from?</a></li>
39
						<li>
40
							<a href="#15">Why are top-level arcs restricted to three arcs numbered
41
								<tt>0</tt> to <tt>2</tt>, and why are arcs beneath top-level arcs
42
								<tt>0</tt> and <tt>1</tt> restricted to fourty arcs numbered <tt>0</tt>
43
								to <tt>39</tt>?</a>
44
						</li>
45
						<li>
46
							<a href="#16">What do we call a registration tree (or object identifier
47
								tree)?</a>
48
						</li>
49
						<li><a href="#17">What is the ASN.1 notation of an OID?</a></li>
50
						<li><a href="#management">How is the entire registration tree managed?</a></li>
51
						<li><a href="#features">Which features are offered by this repository?</a></li>
52
						<li>
53
							<a href="#syntax-rules">What are the syntax rules to enter information
54
								about OIDs through the web interface?</a>
55
						</li>
56
						<li>
57
							<a href="#oid-info">Which information is necessary to apply for
58
								an OID?</a>
59
						</li>
60
						<li>
61
							<a href="#example">Is there a particular OID that can be used for
62
								documenting examples of object identifiers?</a>
63
						</li>
64
						<li>
65
							<a href="#registration-authorities">What is the difference between
66
								the first and current Registration Authorities that appear in the
67
								description of some OIDs? What is their duty?</a>
68
						</li>
69
						<li>
70
							<a href="#mib">What constraints are imposed to OIDs used in SNMP
71
								MIBs (Management Information Bases)?</a>
72
						</li>
73
						<li>
74
							<a href="#lookup">Is there a way to look up an OID in the OID repository
75
								from my web browser?</a>
76
						</li>
77
						<li><a href="#leaf">What is a leaf OID? What is a frozen OID?</a></li>
78
						<li><a href="#orphan">What is an orphan OID?</a></li>
79
						<li><a href="#iri">What is an OID-IRI (Internationalized Resource Identifier)?</a></li>
80
						<li><a href="#29">What are the duties of a Registration Authority?</a></li>
81
						<li><a href="#size-limitations">Are there size limitations for OID encoding?</a></li>
82
						<li><a href="#31">Are there binary encoders/decoders for OIDs?</a></li>
83
						<li><a href="#cookies">Does this web site use cookies?</a><br><li><a href="#33">How does this web site protect users' privacy?</a></li>
84
					</ol><br /></td>
85
			</tr>
86
		</table>
87
	</div>
88
	<div id="table_answers_in_faq">
89
		<table cellspacing="0" cellpadding="0" border="0" width="100%">
90
			<tr>
91
				<td width="2%" valign="top"></td>
92
				<td valign="top" colspan="3">
93
					<span class="page_title">Answers</span>
94
					<ol>
95
						<li style="font-weight:bold;">
96
							<a name="1"></a>What are the standards that define OIDs and the OID tree?
97
							<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a>
98
							<a href="#1" onclick="javascript: switchInfoPerso('Q1');"></a>
99
						</li>
100
						<div id="question" style="display:block; width:auto; height:auto">
101
							They are defined in the <a href="standards.htm">Recommendation ITU-T
102
								X.660 | ISO/IEC 9834 series</a>. A new release of the whole series
103
							has been published in 2008; a new release of <a href="http://www.itu.int/ITU-T/X.660">Recommendation
104
								ITU-T X.660 | ISO/IEC 9834-1</a> is planned for 2014 .<br>Binary encodings of OIDs are specified in <a href="http://www.itu.int/rec/T-REC-X.690/en">Rec.
105
								ITU-T X.690 | ISO/IEC 8825-1</a> for the Binary (BER) and Distinguished
106
							(DER) Encoding rules, in <a href="http://www.itu.int/rec/T-REC-X.691/en">Rec.
107
								ITU-T X.691 | ISO/IEC 8825-2</a> for the Packed Encoding rules (PER).
108
							An XML encoding of OIDs is specified in <a href="http://www.itu.int/rec/T-REC-X.693/en">Rec.
109
								ITU-T X.693 | ISO/IEC 8825-3</a>. (See also <a href="faq.htm#31">question
110
								31</a> about binary encoders/decoders for OIDs.)<br><br></div>
111
						<li style="font-weight:bold;">
112
							<a name="2"></a>Which kind of objects can be referenced by OIDs?
113
							<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a>
114
							<a href="#2" onclick="javascript: switchInfoPerso('Q2');"></a>
115
						</li>
116
						<div id="question" style="width:auto; height:auto">
117
							Objects that can typically be identified by an object identifier are
118
							(non exhaustively):
119
							<ul>
120
								<li>
121
									an <a href="/cgi-bin/display?tree=0.0">ITU-T Recommendation</a>,
122
									an <a href="/cgi-bin/display?tree=1.0&amp;see=all">ISO International
123
										Standard</a>;
124
								</li>
125
								<li>
126
									a <a href="country_oids.htm">country</a>, a company, a
127
									project;
128
								</li>
129
								<li>
130
									a certificate policy specified according to <a href="http://itu.int/ITU-T/X.500">Rec.
131
										ITU-T X.500</a>;
132
								</li>
133
								<li>an encryption algorithm (for example <a href="/get/1.3.14.3.2.26">SHA-1</a>);</li>
134
								<li>
135
									<a href="/get/2.27">identification schemes</a> for tag-based
136
									applications (see <a href="http://itu.int/ITU-T/X.668">Recommendation
137
										ITU-T X.668 | ISO/IEC 9834-9</a>);
138
								</li>
139
								<li>
140
									e-health data (for example, data from the <a href="/get/2.16.840.1.113883">HL7
141
										Consortium</a>);
142
								</li>
143
								<li>
144
									Common Alerting Protocol (<a href="/get/0.0.24.1303">CAP</a>)
145
									emergency messages;
146
								</li>
147
								<li>
148
									an attribute of an ITU-T X.500- or LDAP-based directory to make
149
									up a <code>DistinguishedName</code>;
150
								</li>
151
								<li>
152
									an ASN.1 module (for example, for the <a href="/get/2.41.0.1">BioAPI
153
										Interworking Protocol</a>), an ASN.1 type (or abstract syntax);
154
								</li>
155
								<li>
156
									a <a href="/cgi-bin/display?tree=2.1(1,2,3,4,5">set of ASN.1
157
										encoding rules</a>;
158
								</li>
159
								<li>a MIB for SNMP network management;</li>
160
								<li>
161
									a managed object class, one of its attributes, a notification
162
									or even other templates used in the area of network management
163
									and the GDMO standard (see <a href="http://www.itu.int/rec/T-REC-X.722/en">Recommendation
164
										ITU-T X.722 | ISO/IEC 10165-4</a>);
165
								</li>
166
								<li>
167
									an information object (see <a href="http://www.itu.int/rec/T-REC-X.681/en">Recommendation
168
										ITU-T X.681 | ISO/IEC 8824-2</a>);
169
								</li>
170
								<li>the type of some part of an ITU-T X.400 electronic message body;</li>
171
								<li>a file format;</li>
172
								<li>
173
									etc.<br><br></li>
174
							</ul>
175
						</div>
176
 
177
						<li style="font-weight:bold;">
178
							<a name="3"></a>Where can I learn more about OIDs and their registration?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a>
179
							<a href="#3" onclick="javascript: switchInfoPerso('Q3');"></a>
180
						</li>
181
						<div id="question" style="width:auto; height:auto">
182
							Apart from the <a href="standards.htm">official standards</a> (see
183
							<a href="faq.htm#1">question 1</a>), OIDs are explained in:
184
							<ul>
185
								<li>
186
									<a href="http://www.itu.int/oth/T0B04000048/en">OID flyer</a>
187
									from ITU-T Study Group 17;
188
								</li>
189
								<li>
190
									<a href="http://www.itu.int/pub/T-HDB-LNG.4-2010">ITU handbook</a>
191
									on Object identifiers (OIDs) and their registration authorities;
192
								</li>
193
								<li>
194
									a quick <a href="doc/introduction%20to%20object%20identifiers%20(OIDs).pdf">introduction
195
										to OIDs</a>, by Olivier Dubuisson;
196
								</li>
197
								<li>
198
									section 10.8 of Olivier Dubuisson's <a href="http://www.oss.com/asn1/dubuisson.html">book
199
										&quot;ASN.1 - Communication between heterogeneous systems&quot;</a>;
200
								</li>
201
								<li>
202
									John Larmouth's <a href="http://www.oss.com/asn1/larmouth.html">book
203
										&quot;ASN.1 complete&quot;</a>;
204
								</li>
205
								<li>
206
									a tutorial by John Larmouth entitled &quot;Registration authorities
207
									for OID components&quot; [<a href="doc/OID-tutorial.htm">html</a>]
208
									[<a href="doc/OID-tutorial.ppt">ppt</a>];
209
								</li>
210
								<li>
211
									a presentation entitled &quot;<a href="doc/MoU%20presentation%20on%20OIDs.pdf">Identifying
212
										objects: The ASN.1 approach</a>&quot;;
213
								</li>
214
								<li>
215
									see also <a href="#16">question 16</a>.<br><br></li>
216
							</ul>
217
						</div>
218
 
219
						<li style="font-weight:bold;">
220
							<a name="4"></a>How to add information to the OID repository?	 	 <a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a>
221
							<a href="#4" onclick="javascript: switchInfoPerso('Question');"></a>
222
						</li>
223
						<div id="question" style="width:auto; height:auto">
224
							There are at least 4 ways of adding a new OID description to
225
							the repository: <br>a. Enter the OID value in the box under "Add a description for the
226
							following OID to the database" on the <a href="/">main page</a> and
227
							click on the "Create" button; a new page will then be displayed with
228
							some boxes to fill. You can also enter the OID in the following box:<br><form method="post" action="/cgi-bin/manage" enctype="multipart/form-data">
229
								<input type="hidden" name="action" value="create">
230
								&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<strong>{</strong>
231
								<input type="text" name="oid" size="30" value="">
232
								<strong>}</strong>
233
								<input type="submit" name="submit" value="Create">
234
							</form>
235
							b. Go to the parent OID of the OID that you want to add (i.e. the OID at the immediate upper level in the OID tree) and click
236
							on the "Create a child OID" link on the top right-hand side of the
237
							page; a new page will then be displayed with some boxes to fill.<br>c. Go to an OID at the same level as the OID that you want to add (a.k.a. sibling OID)
238
							and click on the "Create a sibling OID" link on the top right-hand
239
							side of the page; a new page will then be displayed with some boxes
240
							to fill.<br>d. If you have a lot of OID descriptions to add, it is more convenient
241
							to describe them in an XML document that conforms to our <a href="oid.xsd">XML
242
								Schema for OIDs</a> and <a href="submit.htm">submit</a> this document
243
							through the web interface. <br><em>
244
								Note: In all 4 cases, the person (if any) you mention as <a href="#registration-authorities">registrant</a>
245
								for the OID, and the person (if known) who is the <a href="#registration-authorities">registrant</a>
246
								for the parent OID are automatically informed by email and can make
247
								comments on your submission. The description of an OID will not be
248
								visible until it is validated by the webmaster who is also automatically
249
								informed by email.
250
							</em><br><strong><br></strong>
251
 
252
						</div>
253
						<li style="font-weight:bold;">
254
							<a name="modify"></a>How to modify the description of an OID?	 	 <a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a>
255
							<a href="#5" onclick="javascript: switchInfoPerso('Question');"></a>
256
						</li>
257
						<div id="question" style="width:auto; height:auto">
258
							If you want to update an OID that is described in the OID repository,
259
							please click on the &quot;Modify this OID&quot; hyperlink at the top-right
260
							of the web page that describes the OID or enter the OID in the following
261
							box:
262
							<form method="post" action="/cgi-bin/manage" enctype="multipart/form-data">
263
								<input type="hidden" name="action" value="modify">
264
								&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<strong>{</strong>
265
								<input type="text" name="oid" size="30" value="">
266
								<strong>}</strong>
267
								<input type="submit" name="submit" value="Suggest a modification">
268
							</form>
269
							<em>
270
								Note: Your proposed modifications will have to be validated by
271
								the <a href="#registration-authorities">registrant</a> of the OID
272
								being modified (if known), the <a href="#registration-authorities">registrant</a>
273
								of the parent OID (if known) and the OID repository administrator
274
								(who will all be automatically informed by e-mail) before they get
275
								published.
276
							</em><br>If the First or Current Registration Authorities requested privacy
277
							protection, their postal address, email address and phone number are
278
							not displayed (but you can receive them by email). In that case, please
279
							use the &quot;Comments&quot; box at the bottom of the &quot;Suggest
280
							a modification&quot; web page to describe the changes.<br>If an OID is misplaced in the OID tree and should be moved elsewhere
281
							in the tree, please use the &quot;Comments&quot; box at the bottom
282
							of the &quot;Suggest a modification&quot; web page to be displayed
283
							to explain where (and why) the OID should be moved.<br>You can also mention in the &quot;Comments&quot; box that an OID is
284
							a <a href="#leaf">leaf</a> in the OID tree (i.e. child OIDs cannot
285
							be allocated) or is <a href="#leaf">frozen</a> (i.e. no more child
286
							OIDs can be allocated).<br><br></div>
287
						<li style="font-weight:bold;">
288
							<a name="6"></a>How to delete an OID (or move it elsewhere in the OID
289
							tree)?	 	 <a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a>
290
							<a href="#6" onclick="javascript: switchInfoPerso('Question');"></a>
291
						</li>
292
						<div id="question" style="width:auto; height:auto">
293
							According to <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation
294
								ITU-T X.660 | ISO 9834-1</a>, an OID shall not be deleted once it
295
							has been allocated by a Registration Authority. However there be the
296
							case that an OID is decribed in this OID repository but was never
297
							officially allocated by the Registration Authority for the parent
298
							OID (or is misplaced in the OID tree). In this case the OID has to
299
							be deleted from the OID repository (or moved elsewhere). To request
300
							the deletion (or to propose to move it elsewhere) please click on
301
							the &quot;Modify this OID&quot; hyperlink at the top-right of the
302
							web page that describes the OID or enter the OID in the following
303
							box:
304
							<form method="post" action="/cgi-bin/manage" enctype="multipart/form-data">
305
								<input type="hidden" name="action" value="modify">
306
								&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<strong>{</strong>
307
								<input type="text" name="oid" size="30" value="">
308
								<strong>}</strong>
309
								<input type="submit" name="submit" value="Suggest deletion">
310
							</form>
311
							Use the &quot;Comments&quot; box at the bottom of the web page to
312
							be displayed to explain why the OID should be deleted (or moved elsewhere).
313
							Your suggestion will have to be validated by the registrant of the
314
							OID (if known), the registrant of the parent OID (if known) and the
315
							OID repository administrator (who will all be automatically informed
316
							by e-mail) before they get published.
317
						</div>
318
						<br><li style="font-weight:bold;">
319
							<a name="7"></a>How does the OID repository provided on this website
320
							compare with Harald Alvestrand's repository?	 	 <a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a>
321
							<a href="#7" onclick="javascript: switchInfoPerso('Question');"></a>
322
						</li>
323
						<div id="question" style="width:auto; height:auto">
324
							We get Harald's agreement to dump his repository and merge the data
325
							into our repository. This was done in June 2003 and our OID repository
326
							now encompasses <a href="http://www.alvestrand.no/objectid/">Harald's
327
								registry</a>.
328
						</div>
329
						<br><li style="font-weight:bold;">
330
							<a name="8"></a>How to reference an OID description in this repository?	 	 <a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a>
331
							<a href="#8" onclick="javascript: switchInfoPerso('Question');"></a>
332
						</li>
333
						<div id="question" style="width:auto; height:auto">
334
							The shortest and easiest means is to append the OID (whether it is
335
							in ASN.1 notation, dot notation or <a href="http://www.ietf.org/rfc/rfc3061.txt">URN
336
								notation</a>) to the <a href="/get/">http://oid-info.com/get/</a>
337
							URL, <em>e.g.</em>:
338
							<ul>
339
								<li> <a href="/get/2.999">http://oid-info.com/get/2.999</a> (recommended);</li>
340
								<li>
341
									<a href="/get/%7Bjoint-iso-itu-t%20example(999)%7D">http://oid-info.com/get/{joint
342
										iso-itu-t example(999)}</a> (ASN.1 notation);
343
								</li>
344
								<li>
345
									<a href="/get/urn:oid:2.999">http://oid-info.com/get/urn:oid:2.999</a>
346
									(URN notation);
347
								</li>
348
								<li>
349
									<a href="/get//Joint-ISO-ITU-T/Example">http://oid-info.com/get//Joint-ISO-ITU-T/Example</a>
350
									or <a href="/get//2/999">http://oid-info.com/get//2/999</a> (OID-IRI
351
									notation; with a '/' at the beginning of the OID notation, hence
352
									two '/'s after 'get');
353
								</li>
354
								<li>
355
									<a href="/get//Example">http://oid-info.com/get//Example</a>
356
									(OID-IRI notation using a long arc; with a '/' at the beginning
357
									of the OID notation, hence two '/'s after 'get').<br><br></li>
358
							</ul>
359
						</div>
360
						<br><li style="font-weight:bold;">
361
							<a name="9"></a>How many OIDs are currently described in this repository?	 	 <a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a>
362
							<a href="#9" onclick="javascript: switchInfoPerso('Question');"></a>
363
						</li>
364
						<div id="question" style="width:auto; height:auto">
365
							There are more than 930 000 OID descriptions stored in our repository
366
							(see <a href="/cgi-bin/display?action=count_nodes">exact number</a>).
367
							The repository is well alive and updated as often as necessary; <a href="/cgi-bin/display?action=count_nodes">statistics</a>
368
							are available about the number of OIDs added to the repository (or
369
							updated) over the past 12 months. A (non-exhaustive) list of standards
370
							(and other documents that define OIDs) which have been captured in
371
							our repository is <a href="captured-standards.htm">available</a>.
372
 
373
						</div>
374
						<br><li style="font-weight:bold;">
375
							<a name="10"></a>How to get an OID assigned?	 	 <a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a>
376
							<a href="#10" onclick="javascript: switchInfoPerso('Question');"></a>
377
						</li>
378
						<div id="question" style="width:auto; height:auto">
379
							The original intention of the <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation
380
								ITU-T X.660 | ISO/IEC 9834</a> series was that anyone should be able
381
							to get an OID if they needed one. There are registration authorities
382
							from which it is easy and quite cheap (sometimes even free!) to have
383
							an OID assigned, such as (<em>important note</em>: OIDs have to be requested
384
							from those registrations authorities because this OID repository is
385
							<em>not</em> a registration authority):</li>
386
							<ul>
387
								<li>
388
									If you only need an OID for an example in a document, use <code><a href="/get/2.999">{joint-iso-itu-t(2)
389
											example(999)}</a></code> as explained in <a href="#example">question
390
										22</a>.
391
								</li>
392
								<li>
393
									<a href="country_oids.htm#agreements">Several countries</a>
394
									are handling out OIDs (usually after paying a fee decided by the
395
									national registration authority) under their country arc <a href="/get/2.16"><code>{joint-iso-itu-t(2)
396
											country(16)}</code></a> and/or <a href="/get/1.2"><code>{iso(1) member-body(2)}</code></a>
397
									(see <a href="country_codes.htm">correspondence table between
398
										country codes and OIDs</a>). (Note: If you are representing a country
399
									and want to nominate a registration authority for your country arc
400
									under <a href="/get/1.2"><code>{iso(1) member-body(2)}</code></a> or
401
									<a href="/get/2.16"><code>{joint-iso-itu-t(2) country(16)}</code></a>,
402
									please see <a href="#11">question 11</a> below.)
403
								</li>
404
								<li>
405
									<a href="https://pen.iana.org/pen/PenApplication.page">IANA</a>
406
									(Internet Assigned Numbers Authority) hands out OIDs for free under
407
									<a href="/get/1.3.6.1.4.1"><code>{iso(1) identified-organization(3)
408
											dod(6) internet(1) private(4) enterprise(1)}</code></a>; these OIDs
409
									are used a lot (but not only) to identify Management Information
410
									Bases (MIBs) for network management (SNMP).
411
								</li>
412
								<li>
413
									<a href="http://webapp.etsi.org/ASN1ObjectTree/ASN1.asp">ETSI</a>
414
									(European Telecommunication Standards Institute) hands out OIDs
415
									under <code><a href="/get/0.4.0.127.0">{itu-t(0) identified-organization(4)
416
											etsi(0) reserved(127) etsi-identified-organization(0)}</a></code>
417
									even for non-ETSI-members.
418
								</li>
419
								<li>
420
									Network operators can have an OID assigned by ITU-T under <code><a href="/get/0.3">{itu-t(0)
421
											network-operator(3)}</a></code>; telecom operators can have an OID
422
									assigned by their national PTT administration under <code><a href="/get/0.2">{itu-t(0)
423
											administration(2)}</a></code>.
424
								</li>
425
							</ul>
426
							<ul>
427
								<li>
428
									ViaThinkSoft <a href="https://www.viathinksoft.de/freeoid/index.php">freely
429
										assigns</a> an OID to private persons and developers of freeware,
430
									shareware or open-source software under <a href="/get/1.3.6.1.4.1.37476.9000"><code>{iso(1)
431
											identified-organization(3) dod(6) internet(1) private(4) enterprise(1)
432
											37476 freesub(9000)}</code></a>.
433
								</li>
434
								<li>
435
									Dave Harvey (UK) <a href="http://www.medicalconnections.co.uk/Free_UID">sub-delegate
436
										ranges of his own OID</a> to anyone who uses a <a href="http://medical.nema.org/">DICOM</a>
437
									toolkit (communication in medicine).
438
								</li>
439
								<li>
440
									You can <a href="https://docs.microsoft.com/en-us/windows/win32/ad/obtaining-an-object-identifier-from-microsoft">obtain
441
										an OID from Microsoft</a> to extend the Active Directory schema.
442
								</li>
443
								<li>
444
									You can <a href="http://www.itu.int/ITU-T/asn1/uuid.html#UUID%20Generation%20&amp;%20Registration">generate
445
										a UUID</a> (or use a UUID that you already hold) and append it as
446
									a subsequent arc of <a href="/get/2.25"><code>{joint-iso-itu-t(2)
447
											uuid(25)}</code></a> (without registering it because it is guaranteed
448
									to be globally unique with a high probability) according to
449
									<a href="http://www.itu.int/rec/T-REC-X.667/en">Recommendation
450
										ITU-T X.667 | ISO/IEC 9834-8</a> (but see <a href="#size-limitations">question
451
										30 about size limitations of OID encodings</a>).<br><br></li>
452
							</ul>
453
						</div>
454
						<br><li style="font-weight:bold;">
455
							<a name="national-RA"></a>What decision needs be taken if a country
456
							wants a national Registration Authority for OIDs?
457
							<a href="#11" onclick="javascript: switchInfoPerso('Question');"></a>
458
						</li>
459
						<div align="right"><a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a></div>
460
						<div id="question" style="width:auto; height:auto">
461
							Country arcs are the subsequent arcs of <a href="/get/1.2"><code>{iso(1)
462
									member-body(2)}</code></a> and <a href="/get/2.16"><code>{joint-iso-itu-t(2)
463
									country(16)}</code></a>. The values assigned to country arcs are the
464
							<a href="http://unstats.un.org/unsd/methods/m49/m49alpha.htm">numerical
465
								codes</a> (without leading zeros) assigned by the United Nations Statistics
466
							Division together with the corresponding and the <a href="https://www.iso.org/obp/ui/#search">ISO
467
								3166-1-alpha-2 code</a>. <a href="/get/1.2"><code>{iso(1) member-body(2)}</code></a>
468
							was deprecated in favour of <a href="/get/2.16"><code>{joint-iso-itu-t(2)
469
									country(16)}</code></a>, thus countries which have never been operating
470
							a national Registration Authority (RA) for OIDs are encouraged to
471
							request an arc under <a href="/get/2.16"><code>{joint-iso-itu-t(2) country(16)}</code></a>.
472
							Countries are discouraged to request an arc under both <a href="/get/1.2"><code>{iso(1)
473
									member-body(2)}</code></a> and <a href="/get/2.16"><code>{joint-iso-itu-t(2)
474
									country(16)}</code></a>.<br><a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation ITU-T
475
								X.660 | ISO/IEC 9834-1</a>, clause A.4.5, specifies that the <a href="http://www.iso.org/iso/about/iso_members.htm">ISO
476
								National Body</a> of the country and the <a href="http://www.itu.int/GlobalDirectory/search.html">administration
477
								representing the country in the ITU</a> shall agree together (as a
478
							national decision) on the organization that will be the RA for their
479
							country arc. In the case of a country arc under <a href="/get/1.2"><code>{iso(1)
480
									member-body(2)}</code></a> the decision is only taken by the <a href="http://www.iso.org/iso/about/iso_members.htm">ISO
481
								National Body</a> of the country. For more detailed information, see
482
							&quot;<a href="country_oids.htm">Operation of a country Registration
483
								Authority</a>&quot;.<br>One way to know if your country is already operating an RA for OIDs
484
							is too check the <a href="country_oids.htm#agreements">known
485
								country RAs</a>.
486
 
487
						</div>
488
						<br><li style="font-weight:bold;">
489
							<a name="12"></a>Are there guidelines or standards regarding subsequent
490
							arcs of a country arc?	 	 <a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a>
491
							<a href="#12" onclick="javascript: switchInfoPerso('Question');"></a>
492
						</li>
493
						<div id="question" style="width:auto; height:auto">
494
							Country arcs are the subsequent arcs of <a href="/get/1.2"><code>{iso(1)
495
									member-body(2)}</code></a> and <a href="/get/2.16"><code>{joint-iso-itu-t(2)
496
									country(16)}</code></a>.<br>The structure underneath a country arc is a national decision. The
497
							basic standard is of course <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation
498
								ITU-T X.660 | ISO/IEC 9834-1</a>. It might be worth having a look
499
							at <a href="http://www.itu.int/rec/T-REC-X.670/en">Recommendation
500
								ITU-T X.670</a> "<em>
501
								Procedures for registration agents operating on
502
								behalf of organizations to register organization names subordinate
503
								to country names
504
							</em>".<br>There is no guidelines besides the fact that any registration authority
505
							needs to keep records according to the aforementioned standards. A
506
							good idea is probably to look at <a href="country_oids.htm#agreements">how
507
								other countries have organized subsequent arcs beneath their country
508
								arc</a> as well as reading the ITU handbook on &quot;<a href="http://www.itu.int/pub/T-HDB-LNG.4-2010"><em>
509
									Object
510
									identifiers (OIDs) and their registration authorities
511
								</em></a>&quot;.
512
 
513
						</div>
514
						<br><li style="font-weight:bold;"><a name="13"></a>What is the Internet OID?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#13" onclick="javascript: switchInfoPerso('Question');"></a></li>
515
						<div id="question" style="width:auto; height:auto">
516
							The Internet OID is <code><a href="/get/1.3.6.1">{iso(1) identified-organization(3)
517
									dod(6) internet(1)}</a></code> or equivalently in dot notation <code><a href="/get/1.3.6.1">1.3.6.1</a></code>.
518
						</div>
519
 
520
						<li style="font-weight:bold;"><a name="14"></a>Where does the dot notation for OIDs come from?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#14" onclick="javascript: switchInfoPerso('Question');"></a></li>
521
						<div id="question" style="width:auto; height:auto">
522
							(<em>from Harald Alvestrand's <a href="http://www.alvestrand.no/objectid/index.html">website</a></em>)<br>The dot notation is an IETF invention. The ASN.1 group thought it
523
							better to have a notation using spaces and braces, with optional text
524
							labels, so that <code>1.3.6.1</code> would become something like <code>{iso(1)
525
								identified-organization(3) dod(6) internet(1)}</code> or <code>{1 3 6
526
								1}</code> or variants thereof.<br>The IETF folks thought this was somewhat inconvenient, and decided
527
							to use a space-free notation. This is, among other things, spelled
528
							out in IETF <a href="http://www.ietf.org/rfc/rfc1778.txt">RFC 1778,
529
								section 2.15</a>, but was in use long before that time. IETF <a href="http://www.ietf.org/rfc/rfc2252.txt">RFC
530
								2252, section 4.1</a>, eliminates the "<code>ds.4.10</code>" form.
531
						</div>
532
						<br><li style="font-weight:bold;">
533
							<a name="15"></a>Why are top-level arcs restricted to three arcs numbered
534
							<code>0</code> to <code>2</code>, and why are arcs beneath top-level arcs
535
							<code>0</code> and <code>1</code> restricted to fourty arcs numbered <code>0</code>
536
							to <code>39</code>?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#15" onclick="javascript: switchInfoPerso('Question');"></a>
537
						</li>
538
						<div id="question" style="width:auto; height:auto">
539
							This enables optimized binary encodings in which all arcs beneath
540
							top-level arcs <code>0</code> and <code>1</code>, and arcs <code>0</code> to <code>47</code>
541
							beneath top-level arc <code>2</code> are encoded on a single octet (see
542
							<a href="http://www.itu.int/rec/T-REC-X.690/en">Rec. ITU-T X.690 |
543
								ISO/IEC 8825-1</a>, clause 8.19). Arcs greater to <code>47</code> benath
544
							top-level arc <code>2</code> are hence encoded on more than one octet.
545
						</div>
546
						<br><li style="font-weight:bold;">
547
							<a name="16"></a>What do we call a registration tree (or object identifier
548
							tree)?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#16" onclick="javascript: switchInfoPerso('Question');"></a>
549
						</li>
550
						<div id="question" style="width:auto; height:auto">
551
							In an open and international world such as the one of telecommunications
552
							and information technologies, you often need to be able to reference
553
							an "object" (see <a href="#1">question 1</a>) in a unique and universal
554
							way. The ASN.1 standard defines an object as being "<em>
555
								a well-defined
556
								piece of information, definition or specification which requires a
557
								name in order to identify its use in an instance of communication
558
							</em>".<br>In general, an object is a class of information (for example, a file
559
							format), rather than an instance of such a class (for example, an
560
							individual file). It is thus the class of information (defined by
561
							some referenceable specification), rather than the piece of information
562
							itself, that is assigned a place in the tree.<br>The naming structure that has been chosen is a tree structure that
563
							allows to name objects in a local or international context, without
564
							beeing limited either by the registration authority, nor by the number
565
							of objects they can register.
566
						</div>
567
						<br><li style="font-weight:bold;"><a name="17"></a>What is the ASN.1 notation of an OID?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#17" onclick="javascript: switchInfoPerso('Question');"></a></li>
568
						<div id="question" style="width:auto; height:auto">
569
							Each OID arc is associated with a mandatory number (used for data
570
							transfers) and an optional, recommended, identifier (for legibility).
571
							This is called the NameAndNumberForm in Rec. ITU-T X.680 | ISO/IEC
572
							8824-1, clause 32.<br>An "identifier" begins with a lower-case letter and is followed by
573
							letters, digits and hyphens. In <a href="name-forms.htm">some cases</a>,
574
							the identifier has been standardized and can be used alone (without
575
							the associated number) in the ASN.1 notation; this is called the <a href="name-forms.htm">NameForm</a>
576
							in Rec. ITU-T X.680 | ISO/IEC 8824-1, clause 32.<br>The number can only be used alone; this is called the NumberForm in
577
							Rec. ITU-T X.680 | ISO/IEC 8824-1, clause 32.<br>An object identifier is semantically an ordered list of object identifier
578
							components (NameAndNumberForm, NumberForm or NameForm). Starting with
579
							the root of the object identifier tree, each object identifier component
580
							identifies an arc in the object identifier tree. The last object identifier
581
							component identifies an arc leading to a vertex to which an object
582
							has been assigned. It is this object which is identified by the object
583
							identifier.<br>Example: <code><a href="/cgi-bin/display?oid=2.5.4.49&amp;action=display">{joint-iso-itu-t(2)
584
									ds(5) attributeType(4) distinguishedName(49)}</a></code> <br>(See also <a href="#14">question 14</a> for the dot notation and <a href="#iri">question
585
								28</a> about the OID-IRI notation.)
586
						</div>
587
						<br><li style="font-weight:bold;"><a name="management"></a>How is the entire registration tree managed?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#18" onclick="javascript: switchInfoPerso('Question');"></a></li>
588
						<div id="question" style="width:auto; height:auto">
589
							The management of the entire registration tree is accomplished by
590
							a process of delegation of authority. In this process the registration
591
							authority responsible for a given arc in the registration tree may
592
							partition that naming-domain. In doing so, it may or may not delegate
593
							the registration responsibility for the naming-domain formed by each
594
							partition to a subordinate Registration Authority. The naming of a
595
							partition does not necessarily imply authority to register objects
596
							under that partition. This delegation of registration responsibility
597
							can be applied repeatedly with a subordinate registration authority
598
							partitioning further the naming domain for which it is responsible
599
							and delegating responsibility for those partitions to registration
600
							authorities subordinate to it.<br>The registration authority responsible for a given naming-domain must
601
							assign a name to the partition of that naming-domain that a given
602
							sub-authority will manage. The name assigned shall be globally unambiguous,
603
							and shall be concatenated as a prefix to all names assigned by that
604
							sub-authority. The repeated application of this process through a
605
							hierarchy of registration agents ensures the generation of unambiguous
606
							names.<br>An organization, a standard or an automated facility can be the registration
607
							authority for more than one partition of a naming-domain (see also
608
							<a href="faq.htm#national-RA">questions 11 and 12</a> for how country arcs are managed).
609
						</div>
610
						<br><li style="font-weight:bold;"><a name="features"></a>Which features are offered by this repository?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#19" onclick="javascript: switchInfoPerso('Question');"></a></li>
611
						<div id="question" style="width:auto; height:auto">
612
							The <a href="display-example.htm">description page</a> for each OID
613
							offers the ability to:
614
							<ul type="disc">
615
								<li>
616
									have a synthetic <a href="/cgi-bin/display?tree=">graphical
617
										view</a> of the tree (click on the<img src="images/pm.gif" width="19" height="18">
618
									and<img src="images/mm.gif" width="19" height="18"> icons to
619
									fold and unfold arcs);
620
								</li>
621
								<li>display the description of another OID (the &quot;Go&quot; button);</li>
622
								<li>
623
									use the &quot;remote control&quot; to display the description
624
									of:
625
									<ul>
626
										<li>the parent OID,</li>
627
										<li> the previous or next sibling OID,</li>
628
										<li>the very first or very last sibling OID, or</li>
629
										<li> the first child OID; </li>
630
									</ul>
631
								</li>
632
								<li>
633
									submit a description of a child OID under the current OID (see
634
									also <a href="#syntax-rules">question 20</a>): After putting down
635
									some information (description of the OID, its registrant...),
636
									the registrant of the OID (if known), the registrant of the parent
637
									OID (if known) and the OID repository administrator will be automatically
638
									asked by email to review and validate your submission. Note that
639
									the description page of the newly created OID will only be available
640
									after validation;
641
								</li>
642
								<li>
643
									submit a description of a sibling OID at the same level as the
644
									current OID (see also <a href="#syntax-rules">question 20</a>);
645
								</li>
646
								<li>
647
									propose modifications of the description of the current OID:
648
									these modifications will have to be validated by the registrant
649
									of the OID (if known), the registrant of the parent OID (if known)
650
									and the OID repository administrator (who will all be automatically
651
									informed by e-mail) before they get published;
652
								</li>
653
								<li>
654
									do a <a href="basic-search.htm">quick search</a> of the entire
655
									OID repository by searching for a particular string in all attributes;
656
								</li>
657
								<li>
658
									do an <a href="advanced-search.htm">advanced search</a> of the entire
659
									OID repository by searching for a particular value for each description
660
									attribute or even by using regular expressions.
661
								</li>
662
							</ul>
663
							Other features are available from the <a href="/">main page</a> of
664
							the OID repository:
665
							<ul>
666
								<li>
667
									display the <a href="/cgi-bin/display?action=count_nodes">number
668
										of OIDs</a> in the repository as well as statistics about how
669
									many OID descriptions were added or modified over the past 12
670
									months;
671
								</li>
672
								<li>
673
									add the description of a given OID (see also <a href="#syntax-rules">question
674
										20</a>);
675
								</li>
676
								<li>
677
									<a href="submit.htm">submit</a> many OIDs to the database by
678
									describing them in an XML file.<br><br></li>
679
							</ul>
680
						</div>
681
						<br><li style="font-weight:bold;">
682
							<a name="syntax-rules"></a>What are the syntax rules to enter information
683
							about OIDs through the web interface?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#20" onclick="javascript: switchInfoPerso('Question');"></a>
684
						</li>
685
						<div id="question" style="width:auto; height:auto">
686
							When adding information about an OID into the OID repository, non-ASCII
687
							characters such as accentuated letters are allowed in most fields
688
							(&quot;Description&quot;, &quot;Information&quot;, registrant &quot;First
689
							name&quot;, &quot;Last name&quot; and &quot;Address&quot;). The software
690
							will replace them by their equivalent <a href="http://www.w3.org/MarkUp/html-spec/html-spec_13.html#SEC106">HTML
691
								code</a>.<br>The following HTML tags are allowed in the &quot;Description&quot;,
692
							&quot;Information&quot; and &quot;Address&quot; fields: <code>&lt;a&gt;</code>,
693
							<code>&lt;br/&gt;</code>, <code>&lt;code&gt;</code>, <code>&lt;em&gt;</code>,
694
							<code>&lt;hr/&gt;</code>, <code>&lt;img&gt;</code>, <code>&lt;li&gt;</code>, <code>&lt;ol&gt;</code>,
695
							<code>&lt;strong&gt;</code>, <code>&lt;sub&gt;</code>, <code>&lt;sup&gt;</code>
696
							and <code>&lt;ul&gt;</code>. Use of <code>&lt;br&gt;</code> or <code>&lt;br/&gt;</code>
697
							is not mandatory to break lines because the software will replace
698
							by <code>&lt;br/&gt;</code> any newline character that appears in these
699
							fields.
700
						</div>
701
						<br><li style="font-weight:bold;">
702
							<a name="21"></a>Which information is necessary to apply for
703
							an OID?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#21" onclick="javascript: switchInfoPerso('Question');"></a>
704
						</li>
705
						<div id="question" style="width:auto; height:auto">
706
							According to clause 8.2 f of <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation
707
								ITU-T X.660 | ISO/IEC 9834-1</a>, the registration record for an OID
708
							shall include at least:<br>a) the definition of the object (when the registration authority of
709
							the parent OID performs a technical role, it checks that the objet
710
							can be registered under its node);<br>b) when applicable, the identifier (beginning with a lowercase letter)
711
							assigned to the object (in addition to the unique number);<br>b) the name and contact information of the organization that proposed
712
							the entry (usually it is the &quot;<a href="#registration-authorities">First
713
								registration authority</a>&quot; for the requested OID);<br>c) the dates of submission/registration.
714
						</div>
715
						<br><li style="font-weight:bold;">
716
							<a name="example"></a>Is there a particular OID that can be used for
717
							documenting examples of object identifiers?<a href="#22" onclick="javascript: switchInfoPerso('Question');"></a>
718
						</li>
719
						<div align="right"><a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a></div>
720
						<div id="question" style="width:auto; height:auto">
721
							<a href="/get/2.999">{joint-iso-itu-t(2) example(999)}</a> (or <a href="/get/2.999">2.999</a>)
722
							can be used by anyone, without any permission, for the purpose of
723
							documenting examples of object identifiers (in the same way as "example.com"
724
							is defined in <a href="http://www.faqs.org/rfcs/rfc2606.html">IETF
725
								RFC 2606</a> as an example for web sites).
726
						</div>
727
						<br><li style="font-weight:bold;">
728
							<a name="registration-authorities"></a>What is the difference between
729
							the first and current Registration Authorities that appear in the
730
							description of some OIDs? What is their duty?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#23" onclick="javascript: switchInfoPerso('Question');"></a>
731
						</li>
732
						<div id="question" style="width:auto; height:auto">
733
							A <em>Registration Authority</em> (RA) is responsible for allocating
734
							child arcs to the OID for which it manages. It ensures that an integer
735
							is used once among the subsequent arcs (child OIDs). As much as possible,
736
							it avoids the same identifier (beginning with a lowercase letter)
737
							being used for multiple sub-arcs. It also keeps a record of information
738
							(name of a contact person, postal address, telephone and fax numbers,
739
							email address, etc.) about the RA for each child OID and delegates
740
							its duty to each 'child' RA. Such information can be stored in the
741
							OID repository but it is important to understand that an OID first
742
							need to be <em>officially</em> allocated by an RA before it can be described
743
							on this website which is not an official RA, but a <em>repository</em>
744
							of information about existing OIDs.<br>The <em>first Registration Authority</em> of an OID is the very first
745
							person or company to whom the OID was allocated by the RA of the superior
746
							OID. According to the <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation
747
								ITU-T X.660 | ISO/IEC 9834-1</a><!-- clause 9.2.f.a --> standard, the first RA can't be changed
748
							(if the responsibility is transfered to someone else, the information
749
							is recorded in the &quot;Current Registration Authority&quot; section,
750
							without changing the &quot;First Registration Authority&quot; section).<br>By default, if the OID has recently been allocated, the Current RA
751
							is the First RA. So, if you are <a href="#4">entering information
752
								in the OID repository</a>, please fill only the &quot;First Registration
753
							Authority&quot; section, and don't copy the same information in the
754
							&quot;Current Registration Authority&quot; section).<br>When someone or an organization takes over the duty from the First
755
							RA, the relevant information is indicated in the &quot;Current Registration
756
							Authority&quot; section without changing the &quot;First Registration
757
							Authority&quot; section.
758
						</div>
759
						<br><li style="font-weight:bold;">
760
							<a name="mib"></a>What constraints are imposed to OIDs used in SNMP
761
							MIBs (Management Information Bases)?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#24" onclick="javascript: switchInfoPerso('Question');"></a>
762
						</li>
763
						<div id="question" style="width:auto; height:auto">
764
							The constraints are gathered in sections 4.6.5, 4.6.6, and Appendix
765
							D of IETF <a href="https://datatracker.ietf.org/doc/html/rfc4181">RFC 4181</a>
766
							(updated by <a href="https://datatracker.ietf.org/doc/html/rfc4841">RFC 4841</a>)
767
							which makes references to <a href="https://datatracker.ietf.org/doc/html/rfc2578">RFC
768
								2578</a>, sections 3.5, 3.6, 5.6, 7.10, and <a href="https://datatracker.ietf.org/doc/html/rfc3416">RFC
769
								3416</a>, section 4.1.<br>- According to RFC 2578, section 3.5, all OIDs are limited to 128
770
							child OIDs.<br>- The last arc of an OID assigned to any object (be it table, row,
771
							column, or scalar) must not be equal to 0.<br>- In some cases, a final arc 0 is used to translate between SNMPv1
772
							and SNMPv2 notification parameters as explained in <a href="https://datatracker.ietf.org/doc/html/rfc2576">RFC
773
								2576</a>, section 3.<br>One example of a MIB module whose OID assignments follow the recommended
774
							scheme is the <code>POWER-ETHERNET-MIB</code> defined in <a href="https://datatracker.ietf.org/doc/html/rfc3621">RFC
775
								3621</a>.<br>MIBs use a notation like ".2.999" where the leading dot shows that
776
							this OID is absolute while "2.999" might be considered as a relative
777
							OID by some tools which would then add a root OID in front of it.
778
						</div>
779
						<br><li style="font-weight:bold;">
780
							<a name="lookup"></a>Is there a way to look up an OID in the OID repository from my web browser?<a href="#25" onclick="javascript: switchInfoPerso('Question');"></a>
781
						</li>
782
						<div align="right"><a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a></div>
783
						<div id="question" style="width:auto; height:auto">
784
							- If you're using <img src="images/firefox-icon.png" width="16" height="16" alt="[Firefox Icon]">
785
							<a href="https://www.mozilla.org/firefox/">Mozilla Firefox</a> or <img src="images/mozilla-icon.png" width="16" height="16" alt="[Mozilla Icon]">
786
							<a href="https://www.mozilla.org/projects/seamonkey/">Mozilla SeaMonkey</a>
787
							(formerly known as Mozilla Application Suite) or <img src="images/microsoft_ie7.gif" width="16" height="16" alt="[Mozilla Icon]">
788
							<a href="http://www.microsoft.com/windows/downloads/ie/getitnow.mspx">Internet
789
								Explorer 7</a> or <img src="images/google-chrome.ico" width="16" height="16" alt="[Chrome Icon]" border="0">
790
							<a href="http://www.google.com/chrome/">Google Chrome</a>, an <a href="http://mycroft.mozdev.org/search-engines.html?name=oid+resolver&amp;skipcache=yes">OpenSearch
791
								Plugin</a> (a.k.a. search engine) allows to display information about
792
							an OID when an ASN.1, dot, <a href="http://www.ietf.org/rfc/rfc3061.txt">URN</a>
793
							or <a href="#iri">OID-IRI</a> notation is entered in the search bar
794
							at the top-right.<br><!-- - If you're using <a href="http://www.mozilla.org/products/thunderbird/">Mozilla
795
								Thunderbird</a>, <img src="images/firefox-icon.png" width="16" height="16" alt="[Firefox Icon]">
796
							<a href="http://www.mozilla.org/products/firefox/">Mozilla Firefox</a>
797
							or <img src="images/mozilla-icon.png" width="16" height="16" alt="[Mozilla Icon]">
798
							<a href="http://www.mozilla.org/projects/seamonkey/">Mozilla SeaMonkey</a>
799
							(formerly known as Mozilla Application Suite), the <a href="http://dictionarysearch.mozdev.org">DictionarySearch
800
								add-on</a> is easy to configure so that you can display information
801
							about an OID by right-clicking on its selection:<br><ul>
802
								<li>
803
									install the DictionarySearch extension corresponding to your
804
									tool from <a href="http://dictionarysearch.mozdev.org">http://dictionarysearch.mozdev.org</a>;
805
								</li>
806
								<li>
807
									in the &quot;Tools&quot; menu of your tool, select the &quot;Extensions&quot;
808
									item;
809
								</li>
810
								<li>
811
									highlight the line for DictionarySearch, then click on the "Options"
812
									button;
813
								</li>
814
								<li>
815
									add a new Dictionary with the following information (this will
816
									display the description of the selected OIDin dot notation; it
817
									doesn't work well for a selected OID in ASN.1 notation because
818
									the closing parentheses are removed for whatever reason):<br><em>Text</em>: <code>Search for OID "$"</code><br><em>Access key</em>: <code>O</code><br><em>URL</em>: <code>http://oid-info.com/cgi-bin/display?oid=$&amp;action=display</code>
819
								</li>
820
								<li>
821
									This other new &quot;Dictionary&quot; may also be useful (it
822
									will display a tree for the selected OID in dot notation):<br><em>Text</em>: <code>Display tree for OID "$"</code><br><em>Access key</em>: <code>T</code><br><em>URL</em>: <code>http://oid-info.com/cgi-bin/display?oid=$&action=tree</code>
823
								</li>
824
							</ul>
825
							- If you're using <img src="images/firefox-icon.png" width="16" height="16" alt="[Firefox Icon]">
826
							<a href="https://www.mozilla.org/firefox/">Mozilla Firefox</a>, the
827
							<a href="https://addons.mozilla.org/en-US/firefox/addon/1940">&quot;URN
828
								Support&quot; add-on</a> from <a href="https://addons.mozilla.org/en-US/firefox/user/9480">SHIMODA
829
								Hiroshi</a> redirects a <a href="http://www.ietf.org/rfc/rfc3061.txt">URN</a>
830
							of the form urn:oid:x.y.z to the description of this OID in this OID
831
							repository. Note: This add-on is not compatible with the &quot;OID
832
							resolver&quot; add-on mentioned in the first bullet above.<br>- See also <a href="#8">question 8</a>.-->
833
							See also <a href="#8">question 8</a>.<br></div>
834
						<br><li style="font-weight:bold;"><a name="leaf"></a>What is a leaf OID? What is a frozen OID?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#26" onclick="javascript: switchInfoPerso('Question');"></a></li>
835
						<div id="question" style="width:auto; height:auto">
836
							These are not standardized concepts. In case an OID is a <em>leaf</em>
837
							in the OID repository, no child OIDs can be allocated under that OID.
838
							In case an OID is <em>frozen</em> in the OID repository, no more child
839
							OIDs can be created in addition to the existing ones. In both cases,
840
							the system does not accept the creation of child OIDs. The status
841
							is also mentioned on the web page that describes an OID (see example
842
							for a <a href="/get/0.0.2">leaf OID</a> and for a <a href="/get/2.25">frozen
843
								OID</a>).<br>To report that an OID is a leaf or is frozen, please <a href="#modify">suggest
844
								a modification</a> for this OID and use the &quot;Comments&quot; box
845
							at the bottom.
846
						</div>
847
						<br><li style="font-weight:bold;"><a name="orphan"></a>What is an orphan OID?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#27" onclick="javascript: switchInfoPerso('Question');"></a></li>
848
						<div id="question" style="width:auto; height:auto">
849
							This is not a standardized concept but this term is used to qualify
850
							an OID that is described in the OID repository, but some of its parent
851
							OIDs are not described in the OID repository. This does not mean that
852
							these unknown parent OIDs do not exist (actually they do exist because
853
							an OID can only be allocated by the Registration Authority of its
854
							parent OID). However the user who submitted the description of this
855
							OID has no knowledge of how to describe these parent OIDs.<br><!-- This is useful in cases such as:<br>- you have found the description of an OID somewhere on the web or
856
							in a document, but you don't know how to describe all arcs along the
857
							path;<br>- you have a bunch of OIDs to submit to the OID repository, so you
858
							can submit them in any order because there is no obligation to submit
859
							the parent OID first.<br>-->
860
							Orphan OIDs are not visible when one
861
							<a href="/cgi-bin/display?tree=">walks down the OID tree</a>. However,
862
							they are <a href="display-example.htm">displayed</a> when one asks
863
							for the description of a particular OID. <em>Orphan grandchild OIDs</em>
864
							(<em>i.e.</em>, OIDs for which we have a description as well as a description
865
							of their grandparent OID, but no description of their parent OID)
866
							are accessible from the <a href="display-example.htm">description
867
								page</a> of their grandparent OID.
868
						</div>
869
						<br><li style="font-weight:bold;"><a name="iri"></a>What is an OID-IRI (Internationalized Resource Identifier)?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#28" onclick="javascript: switchInfoPerso('Question');"></a></li>
870
						<div id="question" style="width:auto; height:auto">
871
							Historically, OIDs could only be denoted in <a href="#14">dot notation</a>
872
							(<em>e.g.</em>, <code>2.27</code>) or in <a href="#17">ASN.1 notation</a>
873
							(<em>e.g.</em>, <code>{joint-iso-itu-t(2) tag-based(27)}</code>) where only
874
							ASCII identifiers are allowed. The need was identified for a human-friendly
875
							notation which would not be limited to latin alphabets and would encompass
876
							the diversity of <a href="http://www.unicode.org">Unicode alphabets</a>.<br>An OID-IRI (a.k.a. international OID) is a string of slash-separated
877
							Unicode labels from the root of the OID tree, which unambiguously
878
							identifies a node in the OID tree (e.g., &quot;<a href="/get//Joint-ISO-ITU-T/Example"><code>/Joint-ISO-ITU-T/Example</code></a>&quot;).<br>A Unicode label is a case-sensitive string of Unicode characters (except
879
							the <code>SPACE</code> character). Just as an OID node can have multiple
880
							identifiers in ASN.1 notation, it can have multiple Unicode labels
881
							(this allows backwards-compatibility when a company changes its name,
882
							for example). Each OID node has a default Unicode label which is its
883
							number (<em>e.g.</em>, &quot;<a href="/get//2/999"><code>/2/999</code></a>&quot;).<br>A <em>long arc</em> is a particular kind of Unicode label which identifies
884
							an OID that is not immediately beneath the root of the OID tree, <em>e.g.</em>,
885
							OID <code>{joint-iso-itu-t(2) example(999)}</code> has a long arc named
886
							&quot;<code>Example</code>&quot; which allows to build the OID-IRI &quot;<code><a href="/get//Example">/Example</a></code>&quot;
887
							which is shorter than the OID-IRI &quot;<code><a href="/get//Joint-ISO-ITU-T/Example">/Joint-ISO-ITU-T/Example</a></code>&quot;.
888
							Long arcs are only allowed under the <code>joint-iso-itu-t(2)</code> top-level
889
							arc (see the <a href="http://www.itu.int/ITU-T/studygroups/com17/oid-registers.html">register
890
								of long arcs</a>.<br>The <a href="http://www.itu.int/rec/T-REC-X.680/en">ASN.1 standard</a>
891
							specifies an <code>OID-IRI</code> type for exchanging OID-IRI values between
892
							machines.
893
						</div>
894
						<br><li style="font-weight:bold;"><a name="29"></a>What are the duties of a Registration Authority?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#29" onclick="javascript: switchInfoPerso('Question');"></a></li>
895
						<div id="question" style="width:auto; height:auto">
896
							Guidance is given in sections 8.2 (Operation), 9 (registration procedures)
897
							and 11 (recommended fee structure) of <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation
898
								ITU-T X.660 | ISO/IEC 9834-1</a>.
899
						</div>
900
						<br><li style="font-weight:bold;"><a name="size-limitations"></a>Are there size limitations for OID encoding?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#30" onclick="javascript: switchInfoPerso('Question');"></a></li>
901
						<div id="question" style="width:auto; height:auto">
902
							The <a href="standards.htm">OID standards</a> have no limit whatsoever
903
							about the depth of an OID in the OID tree (i.e., number of arcs) and
904
							the size of the integer associated to each OID arc. However, some
905
							tools may have size limitations (or bugs):<br>- The <a href="https://lapo.it/asn1js/">ASN.1 JavaScript decoder at
906
								lapo.it</a>, <a href="http://www.bouncycastle.org">Bouncy Castle Crypto
907
								APIs</a>, OpenSSL (0.9.8o, 1 Jun 2010) and the built-in Java class
908
							"<code>org.ietf.jgss.Oid</code>" can handle <a href="/get/2.25">UUIDs
909
								used as OIDs</a>.<br>- Windows CryptoAPI Shell Extension (tested with Windows XP and Windows
910
							7) cannot handle <a href="/get/2.25">UUIDs used as OIDs</a>: The maximum
911
							useable OID value in Windows is 2<sup>64</sup>-1 (e.g., <code>2.999.18446744073709551615</code>).
912
							Windows will show whitespace when any higher value occurs.<br>- Mozilla software cannot handle <a href="/get/2.25">UUIDs used as
913
								OIDs</a>: The maximum useable OID value in Mozilla software is 2<sup>32</sup>-1
914
							(e.g., <code>2.999.4294967295</code>). The program will show "Unknown"
915
							when an arc contains a higher value (e.g., <code>{2 999 Unknown 0}</code>).
916
							<br>- Mac OS X cannot handle OIDs over 2.47 (it wrongly decodes OIDs which
917
							need more than one octet in the first two arcs). <br>More details can be found in <a href="http://www.viathinksoft.de/~daniel-marschall/asn.1/oid_facts.html">Daniel
918
								Marschall's study about OID encoding and size limitations</a>. Daniel's
919
							<a href="https://www.viathinksoft.de/%7Edaniel-marschall/asn.1/oid-converter/online.php">DER
920
								encoder</a> can also help you in your testing.
921
						</div>
922
						<br><li style="font-weight:bold;"><a name="31"></a>Are there binary encoders/decoders for OIDs?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#31" onclick="javascript: switchInfoPerso('Question');"></a></li>
923
						<div id="question" style="width:auto; height:auto">
924
							See for example (non-exhaustive list):<strong><br></strong>- OSS Nokalva's online <a href="https://asn1.io/asn1playground/">ASN.1
925
								playground</a> encodes/decodes OIDs in any encoding rule (BER, DER,
926
							PER, UPER, XER) with the following schema:<br><code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OID-Module DEFINITIONS ::= BEGIN<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OID ::= OBJECT IDENTIFIER<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;END</code><br>&nbsp;&nbsp;The OID is provided in ASN.1 notation in the &quot;Data:
927
							Encode&quot; box as follows:<br><code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;oid OID ::= {2 999}</code><br>- Daniel Marschall's online <a href="https://www.viathinksoft.de/%7Edaniel-marschall/asn.1/oid-converter/online.php">DER encoder/decoder</a> (for PHP and C);<br>- <a href="http://bouncycastle.org">The Legion of the Bouncy Castle</a>'s
928
							API for Java and C#;<br>- <a href="http://wireshark.org">Wireshark</a>'s subtool for ASN.1;<br>- Etc.
929
						</div>
930
						<br><li style="font-weight:bold;"><a name="32"></a><a name="cookies"></a>Does this web site use cookies?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#32" onclick="javascript: switchInfoPerso('Question');"></a></li>
931
						<div id="question" style="width:auto; height:auto">
932
							Only those users who have submitted information on OIDs (creation of a new OID or proposed modifications to an 			existing OID) have a unique cookie placed on their machine with their first name, last name and email address, so 			that the "submitter" section is automatically filled for them the next time they submit information.
933
							The <a href="/helper">OID helper</a> chatbot is hosted by <a href="http://pandorabots.com/botmaster/en/~121e02c2b4d4270afe6afac6~/faq">Pandorabots</a> which normally tracks individual conversations by placing a cookie on your browser, in order to offer contextual answers to your questions. However, if you browser is not setup to accept cookies, an alternative mechanism is used through a hidden variable in the HTML form. <br>This web site relies on Google Analytics, a tool from Google Inc.,
934
							that uses cookies in the form of textual data relative to your use
935
							of Internet (including your IP address). This data is <a href="https://support.google.com/analytics/topic/2919631?hl=en&amp;ref_topic=1008008">anonymously
936
								saved</a> on servers from Google Inc. located in the United States
937
							of America. Users who don't want their data collected with Google
938
							Analytics can install the <a href="https://support.google.com/analytics/answer/181881?hl=en">Google
939
								Analytics opt-out browser add-on</a>.
940
						</div>
941
						<br><li style="font-weight:bold;"><a name="33"></a><a name="privacy"></a>How does this web site protect users' privacy?<a href="#top"><img src="images/page_top_fleche.jpg" width="27" height="17" border="0"></a><a href="#32" onclick="javascript: switchInfoPerso('Question');"></a></li>
942
						<div id="question" style="width:auto; height:auto">
943
							The purpose of this section (updated on 24 Jan 2019) is to inform
944
							you about the way your personal data is handled on this web site.
945
							By providing your personal data to this web site, you acknowledge
946
							and consent to the collection, use and disclosure of your personal
947
							data for a legitimate interest as explained hereunder. This web site
948
							never sells, leases or rents your personal data.<br>Only users who have submitted information on OIDs (description of
949
							a new OID or proposed modifications to an existing OID) have personal
950
							data stored in the OID repository database. The only reason to keep
951
							such information is to inform them when the OID description is validated
952
							or modified by the OID repository administrator, or when modifications
953
							are suggested by another user (see also <a href="#cookies">question
954
								32 about cookies</a>). This information is not publicly disclosed
955
							on the web site. (Note, however, that it may be sent by email to the
956
							<a href="#registration-authorities">(current or first) registration
957
								authority</a> of the OID and of its parent OID, when they are known).<br>Only those users who are the contact of a <a href="#registration-authorities">(current
958
								or first) registration authority</a> for an OID and have not ticked
959
							the box &quot;<i>
960
								Protect the privacy of the Registration Authority
961
								by not displaying the contact information on the web site
962
							</i>&quot;
963
							have their personal data (email address, postal address, phone number)
964
							publicly visible on the web site. (Note, however, that even when the
965
							&quot;privacy&quot; box is ticked, any user of this web site can <a href="/cgi-bin/manage?a=get-info">receive
966
								by email a copy of such data</a> so as to be able to contact the registration
967
							authority of an OID; such requests are recorded). These users are
968
							automatically notified by email when information about them is entered
969
							and can request deletion of such data.<br>In some cases, your personal data appears in the OID repository because
970
							it is publicly available on another web site (e.g., <a href="https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers">IANA
971
								enterprise numbers</a>).<br>To check if personal data related to you appears in the OID repository,
972
							please use the <a href="advanced-search.htm">advanced search</a>. You can
973
							also <a href="/cgi-bin/manage?a=get-personal-data">get a copy</a>
974
							of all personal data appearing in the OID repository. In any case,
975
							your personal data is never used for sending any kind of publicity
976
							to you.<br>A log of all modifications made to an OID is also kept (hence your
977
							personal data may appear in that log) but it is not public and would
978
							only be used by the OID repository administrator to explain or undo
979
							changes if needed.<br>For any other question related to data protection or to request the
980
							rectification or erasure of your personal data, you can <a href="/oid-helper">contact
981
								the webmaster</a>. Repetitive, disproportionate or impracticable requests
982
							may be rejected.
983
						</div>
984
						<br /></ol>
985
 
986
				</td>
987
			</tr>
988
		</table>
989
 
990
	</div>
991
 
992
	<div class="clear"></div>
993
</div>