WebSVN – oidinfo_new_design – Blame – /trunk/faq.htm

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

Subversion Repositories oidinfo_new_design

oidinfo_new_design/trunk/faq.htm – Rev 6