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

Rev	Author	Line No.	Line
2	daniel-mar	1	<!DOCTYPE html>
		2	<html lang="en">
		3	<head>
		4	<title>OID repository - Introduction</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="introduction">
		82
		83	<table width="100%" border="0" cellpadding="0" cellspacing="0">
		84	<tbody>
		85	<tr>
		86	<td><span class="page_title"><a name="oid"></a>Introduction to OIDs</span></td>
		87	</tr>
		88	<tr><td>
		89	<p>
		90	The Object Identifier (OID) concept and implementation dates back to
		91	the mid-1980s, based on collaboration with the International Federation
		92	for Information Processing (IFIP) over the previous several years.
		93	</p>
		94	<p>
		95	OIDs provide a persistent identification of objects based on a hierarchical
		96	structure of Registration Authorities (RA), where each parent has an
		97	object identifier and allocates object identifiers to child nodes. It
		98	provides a universal and flexible identification scheme for persistent
		99	objects. It has been supported and recommended by ITU-T, ISO and IEC,
		100	and has been used in many ITU-T (and ITU-R) Recommendations, and ISO
		101	and IEC International Standards, since the middle 1980s, as part of
		102	the ASN.1 (Abstract Syntax Notation One).
		103	</p>
		104	<p>
		105	Almost any organization, Recommendation, or Standard can obtain (if
		106	it not already has) an OID node. OIDs are fundamental for all security
		107	work in ITU, ISO and IETF, and are widely used in many standards.
		108	</p>
		109	</td></tr>
		110
		111	<tr><td>
		112	<p>
		113	<img src="images/fl.png" style="width: 10px; height: 8px;"
		114	width="41" border="0" height="8"> <a href="faq.htm#16"><span style="font-size:11px;">
		115	What
		116	do we call a registration tree (or object identifier tree)?
		117	</span></a>
		118	</p>
		119	<p>
		120	<img src="images/fl.png" style="width: 10px; height: 8px;"
		121	width="41" border="0" height="8"> <a href="faq.htm#18"><span style="font-size:11px;">
		122	How
		123	is the entire registration tree managed?
		124	</span></a>
		125	</p>
		126	<p>
		127	<img src="images/fl.png" style="width: 10px; height: 8px;" width="41" border="0" height="8"> <a href="#" onclick="showdiv('Q3');"><span style="font-size:11px;">
		128	Where
		129	can I learn more about OIDs and registration?
		130	</span></a>
		131	</p>
		132	</td></tr>
		133
		134	</tbody>
		135	</table>
		136	<table width="100%" border="0" cellpadding="0" cellspacing="0">
		137	<tbody>
		138	<tr>
		139	<span class="section_title"><a name="long-arc"></a>Internationalization and the long arc concept</span>
		140	</tr>
		141	</tbody>
		142	</table>
		143	<table width="100%" border="0" cellpadding="0" cellspacing="0">
		144	<tbody>
		145	<tr><td>
		146	<p>
		147	In the early years of 2000, the Object Identifier tree was renamed as
		148	the International Object Identifier tree, and the names of arcs were
		149	extended to allow what were called "Unicode labels" - names in any language,
		150	using the <a href="http://www.unicode.org">Unicode</a> character set
		151	- and were made available for computer communication alongside the original
		152	numbers.
		153	</p>
		154	<p>
		155	At the same time, the concept of "long arcs" from the root of the International
		156	OID tree to a node at level 2 or below was introduced. Long arcs do
		157	not have numerical values, but provide an unambiguous reference to the
		158	node from the root using a Unicode label.
		159	</p>
		160	<p>
		161	Use of a path specified purely in terms of the set of Unicode labels
		162	on the (normal or long) arcs from the root to a node is called an International
		163	Object Identifier for that node.
		164	</p>
		165	<p>
		166	In order to support names of arcs in multiple languages, an arc can
		167	have multiple Unicode labels, giving rise to a need to transform a path
		168	using Unicode labels into a canonical form of purely numerical labels
		169	to identify the node. This is handled by the OID Resolution System (described
		170	below).
		171	</p>
		172	</td></tr>
		173
		174	<tr><td>
		175	<img src="images/fl.png" style="width: 10px; height: 8px;" width="41" border="0" height="8">
		176	<a href="faq.htm#iri"><span style="font-size:11px;">
		177	What
		178	is an OID-IRI (Internationalized Resource Identifier)?
		179	</span></a>
		180	</td></tr>
		181
		182	</tbody>
		183	</table>
		184	<br><table width="100%" border="0" cellpadding="0" cellspacing="0">
		185	<tbody>
		186	<tr>
		187	<td><span class="section_title"><a name="use"></a>Use of OIDs</span></td>
		188	</tr>
		189	<tr><td>
		190	<p>
		191	It is hard to summarize the uses. This OID repository gives an impression
		192	of the wide-spread use.
		193	</p>
		194	<p>Known areas of use include:</p>
		195	<ul>
		196	<li>
		197	Extensive use in security in IETF, Rec. ITU-T X.500, ISO/IEC, RSA
		198	and NIST encryption algorithms, etc.;
		199	</li>
		200	<li> extensive use in e-health standards;</li>
		201	<li>
		202	extensive use for network management (Management Information Bases,
		203	MIBS);
		204	</li>
		205	<li>use related to RFID tags;</li>
		206	<li>emerging use for the Common Alerting Protocol for disaster notification:</li>
		207	<li>use forcybersecurity alerts. </li>
		208	</ul>
		209	</td></tr>
		210	<tr><td>
		211	<p>
		212	<img src="images/fl.png" style="width: 10px; height: 8px;"
		213	width="41" border="0" height="8"> <a href="faq.htm#2"><span style="font-size:11px;">
		214	Which
		215	kind of objects can be referenced by OIDs?
		216	</span></a>
		217	</p>
		218	<p>
		219	<img src="images/fl.png" style="width: 10px; height: 8px;"
		220	width="41" border="0" height="8"> <a href="faq.htm#10"><span style="font-size:11px;">
		221	How
		222	to get an OID assigned?
		223	</span></a>
		224	</p>
		225	</td></tr>
		226	</tbody>
		227	</table>
		228
		229	<table width="100%" border="0" cellpadding="0" cellspacing="0">
		230	<tbody>
		231	<tr>
		232	<td><span class="section_title"><a name="ors"></a>Introduction to the ORS (OID Resolution System)</span></td>
		233	</tr>
		234	</tbody>
		235	</table>
		236	<table width="100%" border="0" cellpadding="0" cellspacing="0">
		237	<tbody>
		238	<tr><td>
		239	<p>
		240	Given that there are multiple ways of identifying an International
		241	Object Identifier tree node by a set of Unicode labels defining the
		242	path from the root to that node, there was a requirement to be able
		243	to transform that by an efficient on-line look-up into a canonical form
		244	consisting of the all-numeric identification of arcs of the path (canonicalization).
		245	</p>
		246	<p>
		247	There was also a requirement for the management of a node to be able
		248	to store (and applications to retrieve) information associated with
		249	a node in a flexible way (node information retrieval). This was first
		250	identified in terms of RFID applications (What is the content of this
		251	jar of jam? Who is the owner of this piece of hold baggage? etc.) but
		252	now extends more widely.
		253	</p>
		254	<p>
		255	There was a requirement for both of these look-up activities to be
		256	fully supported by authentication of the returned result with a trust
		257	anchor.
		258	</p>
		259	<p>
		260	The OID Resolution System (ORS) was developed from 2004 onwards, and
		261	allows an application to obtain (online) application-specific information
		262	related to any node identified by an OID.
		263	</p>
		264	<p>
		265	The ORS enables any one of the OID nodes to be mapped into DNS name
		266	zone files, and information about it can be obtained by a DNS look-up
		267	for further application processing. The system was initially designed
		268	to support RFID tag activity, but also has applications in many other
		269	application areas.
		270	</p>
		271	</td></tr>
		272	<tr><td>
		273	<img src="images/fl.png" style="width: 10px; height: 8px;"
		274	width="41" border="0" height="8"> More
		275	information in the
		276	<a href="http://www.itu.int/pub/T-HDB-LNG.4-2010">OID
		277	handbook</a> (part 6)
		278	</td></tr>
		279	</tbody>
		280	</table>
		281	<br><table width="100%" border="0" cellpadding="0" cellspacing="0">
		282	<tbody>
		283	<tr>
		284	<td><span class="section_title"><a name="features"></a>Features of the ORS (OID Resolution System)</span></td>
		285	</tr>
		286	<tr><td>
		287	<ul>
		288	<li>
		289	<em>Support for the International Object Identifier tree naming scheme</em>:
		290	Uses Unicode, so all languages can be included in the identification
		291	of an object.<br><br></li>
		292	<li>
		293	<em>Relation to DNS</em>: International OIDs map to DNS names of the
		294	form <code>zz.yy.xx.oid-res.org</code>. Look-ups are based on DNS zone-file
		295	information, obtained via DNS port 53 (designed for the return of
		296	application-specific information).<br><br></li>
		297	<li>
		298	<em>Security</em>: DNS servers supporting the mapping from the International
		299	OID tree are required to support the DNSSEC protocol of the IETF,
		300	and will return information authenticated using an ITU-T X.500 certificate
		301	chain and a trust anchor.<br><br></li>
		302	<li>
		303	<em>Hierarchical structure</em><strong>:</strong>Any Registration Authority
		304	that has been allocated a node in the International OID tree can make
		305	allocations to children (entirely within its own responsibility),
		306	and can provide (if requested) a pointer from its DNS zone files to
		307	a server maintained by its child for its own DNS zone files. This
		308	is entirely a matter between the parent and child, and is not constrained.<br><br></li>
		309	<li>
		310	<em>Absence of restrictions</em>: The International OID tree has potentially
		311	infinitely many children from each node, and an infinite depth of
		312	the tree. There is also no length restriction on the names used to
		313	identify arcs (or on the characters used, within Unicode).<br><br></li>
		314	<li>
		315	<em>Application data</em>: The ORS can resolve an OID into its canonical
		316	form, and can return authenticated URLs for access to any application
		317	information recorded in the zone files for that OID.
		318	</li>
		319	</ul>
		320	</td></tr>
		321	</tbody>
		322	</table>
		323	</div>
		324	<div class="clear"></div>
		325	</div>
		326
		327
		328	<center id="footer">
		329	<img style="border: 0px solid ; width: 760px; height: 2px;" alt="separation line" src="images/separation800.png" width="760" height="2"><br><br>
		330	<table width="710" cellspacing="0" cellpadding="0" border="0">
		331	<tr valign="baseline">
		332	<td width="34">
		333	<a href="/helper">
		334	<img src="images/enveloppe.png" width="30" height="13" name="mail" border="0" alt="OID helper">
		335	</a>
		336	</td>
		337	<td width="58" align="center"><font size="-2">Webmaster</font></td>
		338	<td width="10" align="center"><img src="images/pointorange_small.gif" width="14" height="10"></td>
		339	<td width="78" align="center">
		340	<font size="-2">
		341	<!--<script language="JavaScript">
		342	d=new Date(document.lastModified)
		343	month=new Array("Jan","Feb","Mar","Apr","May","Jun","Jul","Aug","Sep","Oct","Nov","Dec")
		344	if (Date.parse(document.lastModified) != 0)
		345	document.write(d.getDate()+" "+month[d.getMonth()]+" "+d.getFullYear());
		346	</script>-->
		347	15 Apr 2022
		348	</font>
		349	</td>
		350	<td width="24" align="center"><img src="images/pointorange_small.gif" width="14" height="10"></td>
		351	<td align="center" width="409">
		352	<font size=-1>
		353
		354	</font>
		355	</td>
		356	<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>
		357	</tr>
		358	</table><br>
		359	</center>
		360	</div>
		361	</body>
		362	</html>

Subversion Repositories oidinfo_new_design

oidinfo_new_design/trunk/introduction.htm – Rev 6