Rev 6 | Rev 33 | Go to most recent revision | Only display areas with differences | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed
| Rev 6 | Rev 13 | ||
|---|---|---|---|
| 1 | <!DOCTYPE html> |
1 | <!DOCTYPE html> |
| 2 | <html lang="en"> |
2 | <html lang="en"> |
| 3 | <head> |
3 | <head> |
| 4 | <title>OID repository - Introduction</title> |
4 | <title>OID repository - Introduction</title> |
| 5 | <meta charset="UTF-8"><!-- <meta content="text/html; charset=iso-8859-1" http-equiv="content-type"> --> |
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"> |
6 | <meta name="google-translate-customization" content="ae799a386ca63905-075d0f84d2caa8b0-g8dbf29cdfe9cdbeb-c"> |
| 7 | <link rel="Stylesheet" type="text/css" href="style.css"> |
7 | <link rel="Stylesheet" type="text/css" href="style.css"> |
| 8 | <meta name="viewport" content="width=device-width, initial-scale=1"> |
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."> |
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"> |
10 | <meta name="keywords" content="object identifier oid OID repository registration authority ISO ITU"> |
| 11 | <link rel="SHORTCUT ICON" href="/images/favicon.ico"> |
11 | <link rel="SHORTCUT ICON" href="/images/favicon.ico"> |
| 12 | <script src="scripts.js"></script> |
12 | <script src="scripts.js"></script> |
| 13 | </head> |
13 | </head> |
| 14 | <body id="body" onload="_onload()"> |
14 | <body id="body" onload="_onload()"> |
| 15 | <div id="global_container"> |
15 | <div id="global_container"> |
| 16 | <div id="header"> |
16 | <div id="header"> |
| 17 | <a href="index.htm"> |
17 | <a href="index.htm"> |
| 18 | <img src="images/treewall.jpg" width="130" height="110"> |
18 | <img src="images/treewall.jpg" width="130" height="110"> |
| 19 | </a> |
19 | </a> |
| 20 | <h1 id="header_h1">OID Repository</h1><br><br><br><br> |
20 | <h1 id="header_h1">OID Repository</h1><br><br><br><br> |
| 21 | <div id="header_url_and_menu"> |
21 | <div id="header_url_and_menu"> |
| 22 | <div id="header_url">www.oid-info.com</div> |
22 | <div id="header_url">www.oid-info.com</div> |
| 23 | <div id="header_url_right"> |
23 | <div id="header_url_right"> |
| 24 | <ul id="header_menu"> |
24 | <ul id="header_menu"> |
| 25 | <li><a href="index.htm">Home</a></li> |
25 | <li><a href="index.htm">Home</a></li> |
| 26 | <li><a href="/cgi-bin/display?tree=">Tree display</a></li> |
26 | <li><a href="/cgi-bin/display?tree=">Tree display</a></li> |
| 27 | <li><a href="basic-search.htm">Search</a></li> |
27 | <li><a href="basic-search.htm">Search</a></li> |
| 28 | <li><a href="faq.htm">FAQ</a></li> |
28 | <li><a href="faq.htm">FAQ</a></li> |
| 29 | <li><a href="/helper">Helper</a></li> |
29 | <li><a href="/helper">Helper</a></li> |
| 30 | </ul> |
30 | </ul> |
| 31 | </div> |
31 | </div> |
| 32 | </div> |
32 | </div> |
| 33 | <div style="top: 11px; left: 694px; margin-left:-120px;" id="search"> |
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> |
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"> |
35 | <form name="form_go" method="get" action="/cgi-bin/display" enctype="multipart/form-data"> |
| 36 | <input type="hidden" name="action" value="display"> |
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"> |
37 | <input name="oid" size="20" value="" onfocus="empty();" placeholder="-- OID --" type="text"> <input value="Go" type="submit"> |
| 38 | </form> |
38 | </form> |
| 39 | </div> |
39 | </div> |
| 40 | <div id="google_translate"> |
40 | <div id="google_translate"> |
| 41 | <script> |
41 | <script> |
| 42 | function googleTranslateElementInit() { |
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'); |
43 | new google.translate.TranslateElement({ pageLanguage: 'en', layout: google.translate.TranslateElement.InlineLayout.SIMPLE, gaTrack: true, gaId: 'UA-33779649-1' }, 'google_translate_element'); |
| 44 | } |
44 | } |
| 45 | </script> |
45 | </script> |
| 46 | <!--<script src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"> |
46 | <!--<script src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"> |
| 47 | </script>--> |
47 | </script>--> |
| 48 | </div> |
48 | </div> |
| 49 | </div> |
49 | </div> |
| 50 | </div> |
50 | </div> |
| 51 | <div id="mobile_version"> |
51 | <div id="mobile_version"> |
| 52 | <aside class="sidebar"> |
52 | <aside class="sidebar"> |
| 53 | <nav id="navigation" role="navigation"> |
53 | <nav id="navigation" role="navigation"> |
| 54 | <form name="form_go" method="get" action="/cgi-bin/display" enctype="multipart/form-data"> |
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> |
55 | <a><input name="oid" id="searchbox_mobile" size="35" value="" onfocus="empty();" placeholder="-- Display OID --" type="search"></a> |
| 56 | </form> |
56 | </form> |
| 57 | <a href="index.htm">Home</a> |
57 | <a href="index.htm">Home</a> |
| 58 | <a href="/cgi-bin/display?tree=">Tree display</a> |
58 | <a href="/cgi-bin/display?tree=">Tree display</a> |
| 59 | <a href="basic-search.htm">Search</a> |
59 | <a href="basic-search.htm">Search</a> |
| 60 | <a href="faq.htm">FAQ</a> |
60 | <a href="faq.htm">FAQ</a> |
| 61 | <a href="/helper">Chatbot helper</a> |
61 | <a href="/helper">Chatbot helper</a> |
| 62 | </nav> |
62 | </nav> |
| 63 | </aside> |
63 | </aside> |
| 64 | </div> |
64 | </div> |
| 65 | <div class="wrapper"> |
65 | <div class="wrapper"> |
| 66 | <table width="100%" id="header_mobile"> |
66 | <table width="100%" id="header_mobile"> |
| 67 | <tr> |
67 | <tr> |
| 68 | <td width="20%"> |
68 | <td width="20%"> |
| 69 | <a href="#body" class="nav-button-open" aria-label="open navigation"></a> |
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> |
70 | <a href="#" class="nav-button-close" aria-label="close navigation"></a> |
| 71 | </td> |
71 | </td> |
| 72 | <td width="60%" valign="middle"> |
72 | <td width="60%" valign="middle"> |
| 73 | <h1 id="header_h1">OID Repository</h1> |
73 | <h1 id="header_h1">OID Repository</h1> |
| 74 | <div id="header_url">www.oid-info.com</div> |
74 | <div id="header_url">www.oid-info.com</div> |
| 75 | </td> |
75 | </td> |
| 76 | <td width="20%"><a href="index.htm"><img src="images/treewall.jpg" style="height:10vh;width:auto"></a></td> |
76 | <td width="20%"><a href="index.htm"><img src="images/treewall.jpg" style="height:10vh;width:auto"></a></td> |
| 77 | </tr> |
77 | </tr> |
| 78 | </table> |
78 | </table> |
| 79 | 79 | ||
| 80 | <div id="global_content"> |
80 | <div id="global_content"> |
| 81 | <div id="introduction"> |
81 | <div id="introduction"> |
| 82 | 82 | ||
| 83 | <table width="100%" border="0" cellpadding="0" cellspacing="0"> |
83 | <table width="100%" border="0" cellpadding="0" cellspacing="0"> |
| 84 | <tbody> |
84 | <tbody> |
| 85 | <tr> |
85 | <tr> |
| 86 | <td><span class="page_title"><a name="oid"></a>Introduction to OIDs</span></td> |
86 | <td><span class="page_title"><a name="oid"></a>Introduction to OIDs</span></td> |
| - | 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 | ||
| 87 | </tr> |
101 | </tr> |
| 88 | <tr><td> |
102 | <tr><td colspan="2"> |
| 89 | <p> |
103 | <p> |
| 90 | The Object Identifier (OID) concept and implementation dates back to |
104 | The Object Identifier (OID) concept and implementation dates back to |
| 91 | the mid-1980s, based on collaboration with the International Federation |
105 | the mid-1980s, based on collaboration with the International Federation |
| 92 | for Information Processing (IFIP) over the previous several years. |
106 | for Information Processing (IFIP) over the previous several years. |
| 93 | </p> |
107 | </p> |
| 94 | <p> |
108 | <p> |
| 95 | OIDs provide a persistent identification of objects based on a hierarchical |
109 | OIDs provide a persistent identification of objects based on a hierarchical |
| 96 | structure of Registration Authorities (RA), where each parent has an |
110 | structure of Registration Authorities (RA), where each parent has an |
| 97 | object identifier and allocates object identifiers to child nodes. It |
111 | object identifier and allocates object identifiers to child nodes. It |
| 98 | provides a universal and flexible identification scheme for persistent |
112 | provides a universal and flexible identification scheme for persistent |
| 99 | objects. It has been supported and recommended by ITU-T, ISO and IEC, |
113 | 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 |
114 | 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 |
115 | and IEC International Standards, since the middle 1980s, as part of |
| 102 | the ASN.1 (Abstract Syntax Notation One). |
116 | the ASN.1 (Abstract Syntax Notation One). |
| 103 | </p> |
117 | </p> |
| 104 | <p> |
118 | <p> |
| 105 | Almost any organization, Recommendation, or Standard can obtain (if |
119 | Almost any organization, Recommendation, or Standard can obtain (if |
| 106 | it not already has) an OID node. OIDs are fundamental for all security |
120 | 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. |
121 | work in ITU, ISO and IETF, and are widely used in many standards. |
| 108 | </p> |
122 | </p> |
| 109 | </td></tr> |
123 | </td></tr> |
| 110 | 124 | ||
| 111 | <tr><td> |
125 | <tr><td> |
| 112 | <p> |
126 | <p> |
| 113 | <img src="images/fl.png" style="width: 10px; height: 8px;" |
127 | <img src="images/fl.png" style="width: 10px; height: 8px;" |
| - | 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;" |
|
| 114 | width="41" border="0" height="8"> <a href="faq.htm#16"><span style="font-size:11px;"> |
134 | width="41" border="0" height="8"> <a href="faq.htm#16"><span style="font-size:12px;"> |
| 115 | What |
135 | What |
| 116 | do we call a registration tree (or object identifier tree)? |
136 | do we call a registration tree (or object identifier tree)? |
| 117 | </span></a> |
137 | </span></a> |
| 118 | </p> |
138 | </p> |
| 119 | <p> |
139 | <p> |
| 120 | <img src="images/fl.png" style="width: 10px; height: 8px;" |
140 | <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;"> |
141 | width="41" border="0" height="8"> <a href="faq.htm#18"><span style="font-size:12px;"> |
| 122 | How |
142 | How |
| 123 | is the entire registration tree managed? |
143 | is the entire registration tree managed? |
| 124 | </span></a> |
144 | </span></a> |
| 125 | </p> |
145 | </p> |
| 126 | <p> |
146 | <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;"> |
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;"> |
| 128 | Where |
148 | Where |
| 129 | can I learn more about OIDs and registration? |
149 | can I learn more about OIDs and registration? |
| 130 | </span></a> |
150 | </span></a> |
| 131 | </p> |
151 | </p> |
| 132 | </td></tr> |
152 | </td></tr> |
| 133 | 153 | ||
| 134 | </tbody> |
154 | </tbody> |
| 135 | </table> |
155 | </table> |
| 136 | <table width="100%" border="0" cellpadding="0" cellspacing="0"> |
156 | <table width="100%" border="0" cellpadding="0" cellspacing="0"> |
| 137 | <tbody> |
157 | <tbody> |
| 138 | <tr> |
158 | <tr> |
| 139 | <span class="section_title"><a name="long-arc"></a>Internationalization and the long arc concept</span> |
159 | <span class="section_title"><a name="long-arc"></a>Internationalization and the long arc concept</span> |
| 140 | </tr> |
160 | </tr> |
| 141 | </tbody> |
161 | </tbody> |
| 142 | </table> |
162 | </table> |
| 143 | <table width="100%" border="0" cellpadding="0" cellspacing="0"> |
163 | <table width="100%" border="0" cellpadding="0" cellspacing="0"> |
| 144 | <tbody> |
164 | <tbody> |
| 145 | <tr><td> |
165 | <tr><td> |
| 146 | <p> |
166 | <p> |
| 147 | In the early years of 2000, the Object Identifier tree was renamed as |
167 | 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 |
168 | the International Object Identifier tree, and the names of arcs were |
| 149 | extended to allow what were called "Unicode labels" - names in any language, |
169 | 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 |
170 | using the <a href="http://www.unicode.org">Unicode</a> character set |
| 151 | - and were made available for computer communication alongside the original |
171 | - and were made available for computer communication alongside the original |
| 152 | numbers. |
172 | numbers. |
| 153 | </p> |
173 | </p> |
| 154 | <p> |
174 | <p> |
| 155 | At the same time, the concept of "long arcs" from the root of the International |
175 | 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 |
176 | 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 |
177 | not have numerical values, but provide an unambiguous reference to the |
| 158 | node from the root using a Unicode label. |
178 | node from the root using a Unicode label. |
| 159 | </p> |
179 | </p> |
| 160 | <p> |
180 | <p> |
| 161 | Use of a path specified purely in terms of the set of Unicode labels |
181 | 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 |
182 | on the (normal or long) arcs from the root to a node is called an International |
| 163 | Object Identifier for that node. |
183 | Object Identifier for that node. |
| 164 | </p> |
184 | </p> |
| 165 | <p> |
185 | <p> |
| 166 | In order to support names of arcs in multiple languages, an arc can |
186 | 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 |
187 | 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 |
188 | 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 |
189 | to identify the node. This is handled by the OID Resolution System (described |
| 170 | below). |
190 | below). |
| 171 | </p> |
191 | </p> |
| 172 | </td></tr> |
192 | </td></tr> |
| 173 | 193 | ||
| 174 | <tr><td> |
194 | <tr><td> |
| 175 | <img src="images/fl.png" style="width: 10px; height: 8px;" width="41" border="0" height="8"> |
195 | <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;"> |
196 | <a href="faq.htm#iri"><span style="font-size:12px;"> |
| 177 | What |
197 | What |
| 178 | is an OID-IRI (Internationalized Resource Identifier)? |
198 | is an OID-IRI (Internationalized Resource Identifier)? |
| 179 | </span></a> |
199 | </span></a> |
| 180 | </td></tr> |
200 | </td></tr> |
| 181 | 201 | ||
| 182 | </tbody> |
202 | </tbody> |
| 183 | </table> |
203 | </table> |
| 184 | <br><table width="100%" border="0" cellpadding="0" cellspacing="0"> |
204 | <br><table width="100%" border="0" cellpadding="0" cellspacing="0"> |
| 185 | <tbody> |
205 | <tbody> |
| 186 | <tr> |
206 | <tr> |
| 187 | <td><span class="section_title"><a name="use"></a>Use of OIDs</span></td> |
207 | <td><span class="section_title"><a name="use"></a>Use of OIDs</span></td> |
| 188 | </tr> |
208 | </tr> |
| 189 | <tr><td> |
209 | <tr><td> |
| 190 | <p> |
210 | <p> |
| 191 | It is hard to summarize the uses. This OID repository gives an impression |
211 | It is hard to summarize the uses. This OID repository gives an impression |
| 192 | of the wide-spread use. |
212 | of the wide-spread use. |
| 193 | </p> |
213 | </p> |
| 194 | <p>Known areas of use include:</p> |
214 | <p>Known areas of use include:</p> |
| 195 | <ul> |
215 | <ul> |
| 196 | <li> |
216 | <li> |
| 197 | Extensive use in security in IETF, Rec. ITU-T X.500, ISO/IEC, RSA |
217 | Extensive use in security in IETF, Rec. ITU-T X.500, ISO/IEC, RSA |
| 198 | and NIST encryption algorithms, etc.; |
218 | and NIST encryption algorithms, etc.; |
| 199 | </li> |
219 | </li> |
| 200 | <li> extensive use in e-health standards;</li> |
220 | <li> extensive use in e-health standards;</li> |
| 201 | <li> |
221 | <li> |
| 202 | extensive use for network management (Management Information Bases, |
222 | extensive use for network management (Management Information Bases, |
| 203 | MIBS); |
223 | MIBS); |
| 204 | </li> |
224 | </li> |
| 205 | <li>use related to RFID tags;</li> |
225 | <li>use related to RFID tags;</li> |
| 206 | <li>emerging use for the Common Alerting Protocol for disaster notification:</li> |
226 | <li>emerging use for the Common Alerting Protocol for disaster notification:</li> |
| 207 | <li>use forcybersecurity alerts. </li> |
227 | <li>use forcybersecurity alerts. </li> |
| 208 | </ul> |
228 | </ul> |
| 209 | </td></tr> |
229 | </td></tr> |
| 210 | <tr><td> |
230 | <tr><td> |
| 211 | <p> |
231 | <p> |
| 212 | <img src="images/fl.png" style="width: 10px; height: 8px;" |
232 | <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;"> |
233 | width="41" border="0" height="8"> <a href="faq.htm#2"><span style="font-size:12px;"> |
| 214 | Which |
234 | Which |
| 215 | kind of objects can be referenced by OIDs? |
235 | kind of objects can be referenced by OIDs? |
| 216 | </span></a> |
236 | </span></a> |
| 217 | </p> |
237 | </p> |
| 218 | <p> |
238 | <p> |
| 219 | <img src="images/fl.png" style="width: 10px; height: 8px;" |
239 | <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;"> |
240 | width="41" border="0" height="8"> <a href="faq.htm#10"><span style="font-size:12px;"> |
| 221 | How |
241 | How |
| 222 | to get an OID assigned? |
242 | to get an OID assigned? |
| 223 | </span></a> |
243 | </span></a> |
| 224 | </p> |
244 | </p> |
| 225 | </td></tr> |
245 | </td></tr> |
| 226 | </tbody> |
246 | </tbody> |
| 227 | </table> |
247 | </table> |
| 228 | 248 | ||
| 229 | <table width="100%" border="0" cellpadding="0" cellspacing="0"> |
249 | <table width="100%" border="0" cellpadding="0" cellspacing="0"> |
| 230 | <tbody> |
250 | <tbody> |
| 231 | <tr> |
251 | <tr> |
| 232 | <td><span class="section_title"><a name="ors"></a>Introduction to the ORS (OID Resolution System)</span></td> |
252 | <td><span class="section_title"><a name="ors"></a>Introduction to the ORS (OID Resolution System)</span></td> |
| 233 | </tr> |
253 | </tr> |
| 234 | </tbody> |
254 | </tbody> |
| 235 | </table> |
255 | </table> |
| 236 | <table width="100%" border="0" cellpadding="0" cellspacing="0"> |
256 | <table width="100%" border="0" cellpadding="0" cellspacing="0"> |
| 237 | <tbody> |
257 | <tbody> |
| 238 | <tr><td> |
258 | <tr><td> |
| 239 | <p> |
259 | <p> |
| 240 | Given that there are multiple ways of identifying an International |
260 | Given that there are multiple ways of identifying an International |
| 241 | Object Identifier tree node by a set of Unicode labels defining the |
261 | 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 |
262 | 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 |
263 | 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). |
264 | consisting of the all-numeric identification of arcs of the path (canonicalization). |
| 245 | </p> |
265 | </p> |
| 246 | <p> |
266 | <p> |
| 247 | There was also a requirement for the management of a node to be able |
267 | There was also a requirement for the management of a node to be able |
| 248 | to store (and applications to retrieve) information associated with |
268 | to store (and applications to retrieve) information associated with |
| 249 | a node in a flexible way (node information retrieval). This was first |
269 | 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 |
270 | 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 |
271 | jar of jam? Who is the owner of this piece of hold baggage? etc.) but |
| 252 | now extends more widely. |
272 | now extends more widely. |
| 253 | </p> |
273 | </p> |
| 254 | <p> |
274 | <p> |
| 255 | There was a requirement for both of these look-up activities to be |
275 | 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 |
276 | fully supported by authentication of the returned result with a trust |
| 257 | anchor. |
277 | anchor. |
| 258 | </p> |
278 | </p> |
| 259 | <p> |
279 | <p> |
| 260 | The OID Resolution System (ORS) was developed from 2004 onwards, and |
280 | The OID Resolution System (ORS) was developed from 2004 onwards, and |
| 261 | allows an application to obtain (online) application-specific information |
281 | allows an application to obtain (online) application-specific information |
| 262 | related to any node identified by an OID. |
282 | related to any node identified by an OID. |
| 263 | </p> |
283 | </p> |
| 264 | <p> |
284 | <p> |
| 265 | The ORS enables any one of the OID nodes to be mapped into DNS name |
285 | 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 |
286 | zone files, and information about it can be obtained by a DNS look-up |
| 267 | for further application processing. The system was initially designed |
287 | for further application processing. The system was initially designed |
| 268 | to support RFID tag activity, but also has applications in many other |
288 | to support RFID tag activity, but also has applications in many other |
| 269 | application areas. |
289 | application areas. |
| 270 | </p> |
290 | </p> |
| 271 | </td></tr> |
291 | </td></tr> |
| 272 | <tr><td> |
292 | <tr><td> |
| 273 | <img src="images/fl.png" style="width: 10px; height: 8px;" |
293 | <img src="images/fl.png" style="width: 10px; height: 8px;" |
| 274 | width="41" border="0" height="8"> More |
294 | width="41" border="0" height="8"> More |
| 275 | information in the |
295 | information in the |
| 276 | <a href="http://www.itu.int/pub/T-HDB-LNG.4-2010">OID |
296 | <a href="http://www.itu.int/pub/T-HDB-LNG.4-2010">OID |
| 277 | handbook</a> (part 6) |
297 | handbook</a> (part 6) |
| 278 | </td></tr> |
298 | </td></tr> |
| 279 | </tbody> |
299 | </tbody> |
| 280 | </table> |
300 | </table> |
| 281 | <br><table width="100%" border="0" cellpadding="0" cellspacing="0"> |
301 | <br><table width="100%" border="0" cellpadding="0" cellspacing="0"> |
| 282 | <tbody> |
302 | <tbody> |
| 283 | <tr> |
303 | <tr> |
| 284 | <td><span class="section_title"><a name="features"></a>Features of the ORS (OID Resolution System)</span></td> |
304 | <td><span class="section_title"><a name="features"></a>Features of the ORS (OID Resolution System)</span></td> |
| 285 | </tr> |
305 | </tr> |
| 286 | <tr><td> |
306 | <tr><td> |
| 287 | <ul> |
307 | <ul> |
| 288 | <li> |
308 | <li> |
| 289 | <em>Support for the International Object Identifier tree naming scheme</em>: |
309 | <em>Support for the International Object Identifier tree naming scheme</em>: |
| 290 | Uses Unicode, so all languages can be included in the identification |
310 | Uses Unicode, so all languages can be included in the identification |
| 291 | of an object.<br><br></li> |
311 | of an object.<br><br></li> |
| 292 | <li> |
312 | <li> |
| 293 | <em>Relation to DNS</em>: International OIDs map to DNS names of the |
313 | <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 |
314 | 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 |
315 | information, obtained via DNS port 53 (designed for the return of |
| 296 | application-specific information).<br><br></li> |
316 | application-specific information).<br><br></li> |
| 297 | <li> |
317 | <li> |
| 298 | <em>Security</em>: DNS servers supporting the mapping from the International |
318 | <em>Security</em>: DNS servers supporting the mapping from the International |
| 299 | OID tree are required to support the DNSSEC protocol of the IETF, |
319 | 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 |
320 | and will return information authenticated using an ITU-T X.500 certificate |
| 301 | chain and a trust anchor.<br><br></li> |
321 | chain and a trust anchor.<br><br></li> |
| 302 | <li> |
322 | <li> |
| 303 | <em>Hierarchical structure</em><strong>:</strong>Any Registration Authority |
323 | <em>Hierarchical structure</em><strong>:</strong>Any Registration Authority |
| 304 | that has been allocated a node in the International OID tree can make |
324 | that has been allocated a node in the International OID tree can make |
| 305 | allocations to children (entirely within its own responsibility), |
325 | allocations to children (entirely within its own responsibility), |
| 306 | and can provide (if requested) a pointer from its DNS zone files to |
326 | 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 |
327 | 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> |
328 | is entirely a matter between the parent and child, and is not constrained.<br><br></li> |
| 309 | <li> |
329 | <li> |
| 310 | <em>Absence of restrictions</em>: The International OID tree has potentially |
330 | <em>Absence of restrictions</em>: The International OID tree has potentially |
| 311 | infinitely many children from each node, and an infinite depth of |
331 | 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 |
332 | 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> |
333 | identify arcs (or on the characters used, within Unicode).<br><br></li> |
| 314 | <li> |
334 | <li> |
| 315 | <em>Application data</em>: The ORS can resolve an OID into its canonical |
335 | <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 |
336 | form, and can return authenticated URLs for access to any application |
| 317 | information recorded in the zone files for that OID. |
337 | information recorded in the zone files for that OID. |
| 318 | </li> |
338 | </li> |
| 319 | </ul> |
339 | </ul> |
| 320 | </td></tr> |
340 | </td></tr> |
| 321 | </tbody> |
341 | </tbody> |
| 322 | </table> |
342 | </table> |
| 323 | </div> |
343 | </div> |
| 324 | <div class="clear"></div> |
344 | <div class="clear"></div> |
| 325 | </div> |
345 | </div> |
| 326 | 346 | ||
| 327 | 347 | ||
| 328 | <center id="footer"> |
348 | <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> |
349 | <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"> |
350 | <table width="710" cellspacing="0" cellpadding="0" border="0"> |
| 331 | <tr valign="baseline"> |
351 | <tr valign="baseline"> |
| 332 | <td width="34"> |
352 | <td width="34"> |
| 333 | <a href="/helper"> |
353 | <a href="/helper"> |
| 334 | <img src="images/enveloppe.png" width="30" height="13" name="mail" border="0" alt="OID helper"> |
354 | <img src="images/enveloppe.png" width="30" height="13" name="mail" border="0" alt="OID helper"> |
| 335 | </a> |
355 | </a> |
| 336 | </td> |
356 | </td> |
| 337 | <td width="58" align="center"><font size="-2">Webmaster</font></td> |
357 | <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> |
358 | <td width="10" align="center"><img src="images/pointorange_small.gif" width="14" height="10"></td> |
| 339 | <td width="78" align="center"> |
359 | <td width="78" align="center"> |
| 340 | <font size="-2"> |
360 | <font size="-2"> |
| 341 | <!--<script language="JavaScript"> |
361 | <!--<script language="JavaScript"> |
| 342 | d=new Date(document.lastModified) |
362 | d=new Date(document.lastModified) |
| 343 | month=new Array("Jan","Feb","Mar","Apr","May","Jun","Jul","Aug","Sep","Oct","Nov","Dec") |
363 | month=new Array("Jan","Feb","Mar","Apr","May","Jun","Jul","Aug","Sep","Oct","Nov","Dec") |
| 344 | if (Date.parse(document.lastModified) != 0) |
364 | if (Date.parse(document.lastModified) != 0) |
| 345 | document.write(d.getDate()+" "+month[d.getMonth()]+" "+d.getFullYear()); |
365 | document.write(d.getDate()+" "+month[d.getMonth()]+" "+d.getFullYear()); |
| 346 | </script>--> |
366 | </script>--> |
| 347 | 15 Apr 2022 |
367 | 27 Nov 2022 |
| 348 | </font> |
368 | </font> |
| 349 | </td> |
369 | </td> |
| 350 | <td width="24" align="center"><img src="images/pointorange_small.gif" width="14" height="10"></td> |
370 | <td width="24" align="center"><img src="images/pointorange_small.gif" width="14" height="10"></td> |
| 351 | <td align="center" width="409"> |
371 | <td align="center" width="409"> |
| 352 | <font size=-1> |
372 | <font size=-1> |
| 353 | 373 | ||
| 354 | </font> |
374 | </font> |
| 355 | </td> |
375 | </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> |
376 | <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> |
377 | </tr> |
| 358 | </table><br> |
378 | </table><br> |
| 359 | </center> |
379 | </center> |
| 360 | </div> |
380 | </div> |
| 361 | </body> |
381 | </body> |
| 362 | </html> |
382 | </html> |
| 363 | 383 | ||