Rev 2 | Rev 15 | Go to most recent revision | Show entire file | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed
| Rev 2 | Rev 3 | ||
|---|---|---|---|
| Line 290... | Line 290... | ||
| 290 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
290 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
| 291 | </div> |
291 | </div> |
| 292 | <div class="answer"> |
292 | <div class="answer"> |
| 293 | The shortest and easiest means is to append the OID (whether it is |
293 | The shortest and easiest means is to append the OID (whether it is |
| 294 | in <a href="#17">ASN.1 notation</a>, <a href="#14">dot notation</a>, |
294 | in <a href="#17">ASN.1 notation</a>, <a href="#14">dot notation</a>, |
| 295 | <a href="#iri">IRI notation</a> or <a href="https://tools.ietf.org/html/rfc3061">URN |
295 | <a href="#iri">IRI notation</a> or <a href="https://datatracker.ietf.org/doc/html/rfc3061">URN |
| 296 | notation</a>) to the <a href="/get/">http://oid-info.com/get/</a> |
296 | notation</a>) to the <a href="/get/">http://oid-info.com/get/</a> |
| 297 | URL, <em>e.g.</em>: |
297 | URL, <em>e.g.</em>: |
| 298 | <ul> |
298 | <ul> |
| 299 | <li> <a href="/get/2.999">http://oid-info.com/get/2.999</a> (recommended);</li> |
299 | <li> <a href="/get/2.999">http://oid-info.com/get/2.999</a> (recommended);</li> |
| 300 | <li> |
300 | <li> |
| Line 494... | Line 494... | ||
| 494 | better to have a notation using spaces and braces, with optional text |
494 | better to have a notation using spaces and braces, with optional text |
| 495 | labels, so that <code>1.3.6.1</code> would become something like <code>{iso(1) |
495 | labels, so that <code>1.3.6.1</code> would become something like <code>{iso(1) |
| 496 | identified-organization(3) dod(6) internet(1)}</code> or <code>{1 |
496 | identified-organization(3) dod(6) internet(1)}</code> or <code>{1 |
| 497 | 3 6 1}</code> or variants thereof.<br>The IETF folks thought this was somewhat inconvenient, and decided |
497 | 3 6 1}</code> or variants thereof.<br>The IETF folks thought this was somewhat inconvenient, and decided |
| 498 | to use a space-free notation. This is, among other things, spelled |
498 | to use a space-free notation. This is, among other things, spelled |
| 499 | out in IETF <a href="https://tools.ietf.org/html/rfc1778">RFC 1778, |
499 | out in IETF <a href="https://datatracker.ietf.org/doc/html/rfc1778">RFC 1778, |
| 500 | section 2.15</a>, but was in use long before that time. IETF <a href="https://tools.ietf.org/html/rfc2252">RFC |
500 | section 2.15</a>, but was in use long before that time. IETF <a href="https://datatracker.ietf.org/doc/html/rfc2252">RFC |
| 501 | 2252, section 4.1</a>, eliminates the "<code>ds.4.10</code>" form.<br><br></div> |
501 | 2252, section 4.1</a>, eliminates the "<code>ds.4.10</code>" form.<br><br></div> |
| 502 | </li> |
502 | </li> |
| 503 | <li> |
503 | <li> |
| 504 | <div class="question"> |
504 | <div class="question"> |
| 505 | Why are top-level arcs restricted to three |
505 | Why are top-level arcs restricted to three |
| Line 735... | Line 735... | ||
| 735 | </div> |
735 | </div> |
| 736 | <div class="answer"> |
736 | <div class="answer"> |
| 737 | <a href="/get/2.999">{joint-iso-itu-t(2) example(999)}</a> (or <a href="/get/2.999">2.999</a>) |
737 | <a href="/get/2.999">{joint-iso-itu-t(2) example(999)}</a> (or <a href="/get/2.999">2.999</a>) |
| 738 | can be used by anyone, without any permission, for the purpose of |
738 | can be used by anyone, without any permission, for the purpose of |
| 739 | documenting examples of object identifiers (in the same way as "example.com" |
739 | documenting examples of object identifiers (in the same way as "example.com" |
| 740 | is defined in <a href="https://tools.ietf.org/html/rfc2606">IETF RFC |
740 | is defined in <a href="https://datatracker.ietf.org/doc/html/rfc2606">IETF RFC |
| 741 | 2606</a> as an example for web sites). <br><br></div> |
741 | 2606</a> as an example for web sites). <br><br></div> |
| 742 | </li> |
742 | </li> |
| 743 | <li> |
743 | <li> |
| 744 | <div class="question"> |
744 | <div class="question"> |
| 745 | What is the difference between the first and current Registration Authorities |
745 | What is the difference between the first and current Registration Authorities |
| Line 779... | Line 779... | ||
| 779 | What constraints are imposed to OIDs used in SNMP MIBs (Management Information Bases)?<a name="24"></a><a name="mib"></a> |
779 | What constraints are imposed to OIDs used in SNMP MIBs (Management Information Bases)?<a name="24"></a><a name="mib"></a> |
| 780 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
780 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
| 781 | </div> |
781 | </div> |
| 782 | <div class="answer"> |
782 | <div class="answer"> |
| 783 | The constraints are gathered in sections 4.6.5, 4.6.6, and Appendix |
783 | The constraints are gathered in sections 4.6.5, 4.6.6, and Appendix |
| 784 | D of IETF <a href="http://tools.ietf.org/html/rfc4181">RFC 4181</a> |
784 | D of IETF <a href="https://datatracker.ietf.org/doc/html/rfc4181">RFC 4181</a> |
| 785 | (updated by <a href="http://tools.ietf.org/html/rfc4841">RFC 4841</a>) |
785 | (updated by <a href="https://datatracker.ietf.org/doc/html/rfc4841">RFC 4841</a>) |
| 786 | which makes references to <a href="http://tools.ietf.org/html/rfc2578">RFC |
786 | which makes references to <a href="https://datatracker.ietf.org/doc/html/rfc2578">RFC |
| 787 | 2578</a>, sections 3.5, 3.6, 5.6, 7.10, and <a href="http://tools.ietf.org/html/rfc3416">RFC |
787 | 2578</a>, sections 3.5, 3.6, 5.6, 7.10, and <a href="https://datatracker.ietf.org/doc/html/rfc3416">RFC |
| 788 | 3416</a>, section 4.1.<br> |
788 | 3416</a>, section 4.1.<br> |
| 789 | - According to <a href="https://tools.ietf.org/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> |
789 | - According to <a href="https://datatracker.ietf.org/doc/html/rfc2578">RFC 2578</a>, section 3.5, all OIDs are limited to 128 child OIDs and each OID has a maximum (integer) value of 2<sup>32</sup>-1 (<code>4294967295</code>).<br> |
| 790 | - The last arc of an OID assigned to any object (be it table, row, column, or scalar) must not be equal to 0.<br>- In some cases, a final arc 0 is used to translate between SNMPv1 and SNMPv2 notification parameters as explained in <a href="http://tools.ietf.org/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="http://tools.ietf.org/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> |
790 | - The last arc of an OID assigned to any object (be it table, row, column, or scalar) must not be equal to 0.<br>- In some cases, a final arc 0 is used to translate between SNMPv1 and SNMPv2 notification parameters as explained in <a href="https://datatracker.ietf.org/doc/html/rfc2576">RFC 2576</a>, section 3.<br>One example of a MIB module whose OID assignments follow the recommended scheme is the <code>POWER-ETHERNET-MIB</code> defined in <a href="https://datatracker.ietf.org/doc/html/rfc3621">RFC 3621</a>.<br>MIBs use a notation like "<code>.2.999</code>" where the leading dot shows that this OID is absolute while "<code>2.999</code>" might be considered as a relative OID by some tools which would then add a root OID in front of it.<br><br></div> |
| 791 | </li> |
791 | </li> |
| 792 | <li> |
792 | <li> |
| 793 | <div class="question"> |
793 | <div class="question"> |
| 794 | 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> |
794 | 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> |
| 795 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
795 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
| 796 | </div> |
796 | </div> |
| 797 | <div class="answer"> |
797 | <div class="answer"> |
| 798 | - If you're using <img src="images/firefox-icon.png" width="16" height="16" alt="[Firefox Icon]"><a href="http://www.mozilla.com/firefox/">Mozilla Firefox</a> or <img src="images/mozilla-icon.png" width="16" height="16" alt="[Mozilla Icon]"><a href="http://www.mozilla.org/projects/seamonkey/">Mozilla SeaMonkey</a> |
798 | - If you're using <img src="images/firefox-icon.png" width="16" height="16" alt="[Firefox Icon]"><a href="http://www.mozilla.com/firefox/">Mozilla Firefox</a> or <img src="images/mozilla-icon.png" width="16" height="16" alt="[Mozilla Icon]"><a href="http://www.mozilla.org/projects/seamonkey/">Mozilla SeaMonkey</a> |
| 799 | or <img src="images/google-chrome.ico" width="16" height="16" alt="[Chrome Icon]" border="0"><a href="http://www.google.com/chrome/">Google Chrome</a>, an <a href="http://mycroft.mozdev.org/search-engines.html?name=oid+resolver&skipcache=yes">OpenSearch |
799 | or <img src="images/google-chrome.ico" width="16" height="16" alt="[Chrome Icon]" border="0"><a href="http://www.google.com/chrome/">Google Chrome</a>, an <a href="http://mycroft.mozdev.org/search-engines.html?name=oid+resolver&skipcache=yes">OpenSearch |
| 800 | Plugin</a> (a.k.a. search engine) allows to display information about |
800 | Plugin</a> (a.k.a. search engine) allows to display information about |
| 801 | an OID when an ASN.1 notation, dot notation, <a href="https://tools.ietf.org/html/rfc3061">URN</a> notation |
801 | an OID when an ASN.1 notation, dot notation, <a href="https://datatracker.ietf.org/doc/html/rfc3061">URN</a> notation |
| 802 | or <a href="#iri">OID-IRI</a> notation is entered in the search bar |
802 | or <a href="#iri">OID-IRI</a> notation is entered in the search bar |
| 803 | at the top-right.<br><!-- - If you're using <a href="http://www.mozilla.org/products/thunderbird/">Mozilla |
803 | at the top-right.<br><!-- - If you're using <a href="http://www.mozilla.org/products/thunderbird/">Mozilla |
| 804 | Thunderbird</a>, <img src="images/firefox-icon.png" width="16" height="16" alt="[Firefox Icon]"><a href="http://www.mozilla.org/products/firefox/">Mozilla Firefox</a> |
804 | Thunderbird</a>, <img src="images/firefox-icon.png" width="16" height="16" alt="[Firefox Icon]"><a href="http://www.mozilla.org/products/firefox/">Mozilla Firefox</a> |
| 805 | or <img src="images/mozilla-icon.png" width="16" height="16" alt="[Mozilla Icon]"><a href="http://www.mozilla.org/projects/seamonkey/">Mozilla SeaMonkey</a> |
805 | or <img src="images/mozilla-icon.png" width="16" height="16" alt="[Mozilla Icon]"><a href="http://www.mozilla.org/projects/seamonkey/">Mozilla SeaMonkey</a> |
| 806 | (formerly known as Mozilla Application Suite), the <a href="http://dictionarysearch.mozdev.org">DictionarySearch |
806 | (formerly known as Mozilla Application Suite), the <a href="http://dictionarysearch.mozdev.org">DictionarySearch |