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

Subversion Repositories oidinfo_new_design

oidinfo_new_design/trunk/faq.htm – Rev 20