375,7 → 375,7 |
<div class="answer"> |
The shortest and easiest means is to append the OID (whether it is |
in <a href="#17">ASN.1 notation</a>, <a href="#14">dot notation</a>, |
<a href="#iri">IRI notation</a> or <a href="https://tools.ietf.org/html/rfc3061">URN |
<a href="#iri">IRI notation</a> or <a href="https://datatracker.ietf.org/doc/html/rfc3061">URN |
notation</a>) to the <a href="/get/">http://oid-info.com/get/</a> |
URL, <em>e.g.</em>: |
<ul> |
579,8 → 579,8 |
identified-organization(3) dod(6) internet(1)}</code> or <code>{1 |
3 6 1}</code> or variants thereof.<br>The IETF folks thought this was somewhat inconvenient, and decided |
to use a space-free notation. This is, among other things, spelled |
out in IETF <a href="https://tools.ietf.org/html/rfc1778">RFC 1778, |
section 2.15</a>, but was in use long before that time. IETF <a href="https://tools.ietf.org/html/rfc2252">RFC |
out in IETF <a href="https://datatracker.ietf.org/doc/html/rfc1778">RFC 1778, |
section 2.15</a>, but was in use long before that time. IETF <a href="https://datatracker.ietf.org/doc/html/rfc2252">RFC |
2252, section 4.1</a>, eliminates the "<code>ds.4.10</code>" form.<br><br></div> |
</li> |
<li> |
820,7 → 820,7 |
<a href="/get/2.999">{joint-iso-itu-t(2) example(999)}</a> (or <a href="/get/2.999">2.999</a>) |
can be used by anyone, without any permission, for the purpose of |
documenting examples of object identifiers (in the same way as "example.com" |
is defined in <a href="https://tools.ietf.org/html/rfc2606">IETF RFC |
is defined in <a href="https://datatracker.ietf.org/doc/html/rfc2606">IETF RFC |
2606</a> as an example for web sites). <br><br></div> |
</li> |
<li> |
864,13 → 864,13 |
</div> |
<div class="answer"> |
The constraints are gathered in sections 4.6.5, 4.6.6, and Appendix |
D of IETF <a href="http://tools.ietf.org/html/rfc4181">RFC 4181</a> |
(updated by <a href="http://tools.ietf.org/html/rfc4841">RFC 4841</a>) |
which makes references to <a href="http://tools.ietf.org/html/rfc2578">RFC |
2578</a>, sections 3.5, 3.6, 5.6, 7.10, and <a href="http://tools.ietf.org/html/rfc3416">RFC |
D of IETF <a href="https://datatracker.ietf.org/doc/html/rfc4181">RFC 4181</a> |
(updated by <a href="https://datatracker.ietf.org/doc/html/rfc4841">RFC 4841</a>) |
which makes references to <a href="https://datatracker.ietf.org/doc/html/rfc2578">RFC |
2578</a>, sections 3.5, 3.6, 5.6, 7.10, and <a href="https://datatracker.ietf.org/doc/html/rfc3416">RFC |
3416</a>, section 4.1.<br> |
- 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> |
- 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> |
- 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> |
- 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> |
</li> |
<li> |
<div class="question"> |
881,7 → 881,7 |
- 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> |
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 |
Plugin</a> (a.k.a. search engine) allows to display information about |
an OID when an ASN.1 notation, dot notation, <a href="https://tools.ietf.org/html/rfc3061">URN</a> notation |
an OID when an ASN.1 notation, dot notation, <a href="https://datatracker.ietf.org/doc/html/rfc3061">URN</a> notation |
or <a href="#iri">OID-IRI</a> notation is entered in the search bar |
at the top-right.<br><!-- - If you're using <a href="http://www.mozilla.org/products/thunderbird/">Mozilla |
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> |
1130,7 → 1130,7 |
if (Date.parse(document.lastModified) != 0) |
document.write(d.getDate()+" "+month[d.getMonth()]+" "+d.getFullYear()); |
</script>--> |
15 Apr 2022 |
15 Jul 2022 |
</font> |
</td> |
<td width="24" align="center"><img src="images/pointorange_small.gif" width="14" height="10"></td> |