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

Subversion Repositories oidinfo_new_design

oidinfo_new_design/trunk/introduction.htm – Rev 33