Rev 6 | Rev 20 | Go to most recent revision | Show entire file | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed
Rev 6 | Rev 15 | ||
---|---|---|---|
Line 124... | Line 124... | ||
124 | <li><a href="#29">What are the duties of a Registration Authority?</a></li> |
124 | <li><a href="#29">What are the duties of a Registration Authority?</a></li> |
125 | <li><a href="#size-limitations">Are there size limitations for OID encoding?</a></li> |
125 | <li><a href="#size-limitations">Are there size limitations for OID encoding?</a></li> |
126 | <li><a href="#31">Are there binary encoders/decoders for OIDs?</a></li> |
126 | <li><a href="#31">Are there binary encoders/decoders for OIDs?</a></li> |
127 | <li><a href="#cookies">Does this web site use cookies?</a></li> |
127 | <li><a href="#cookies">Does this web site use cookies?</a></li> |
128 | <li><a href="#33">How does this web site protect users' privacy?</a></li> |
128 | <li><a href="#33">How does this web site protect users' privacy?</a></li> |
- | 129 | <li><a href="#guidelines">What are the guidelines to adequately describe an OID in this OID repository?</a></li> |
|
129 | </ol><br></td> |
130 | </ol><br></td> |
130 | </tr> |
131 | </tr> |
131 | </table> |
132 | </table> |
132 | </div> |
133 | </div> |
133 | <div id="table_answers_in_faq"> |
134 | <div id="table_answers_in_faq"> |
Line 268... | Line 269... | ||
268 | so any OID described in this OID repository has to be officially allocated |
269 | so any OID described in this OID repository has to be officially allocated |
269 | by the Registration Authority of its parent OID. There are at least |
270 | by the Registration Authority of its parent OID. There are at least |
270 | 4 ways of adding a new OID description to the repository: <br>a. Enter the OID value in the box under "Add a description for the |
271 | 4 ways of adding a new OID description to the repository: <br>a. Enter the OID value in the box under "Add a description for the |
271 | following OID to the database" on the <a href="index.htm">main page</a> and |
272 | following OID to the database" on the <a href="index.htm">main page</a> and |
272 | click on the "Create" button; a new page will then be displayed with |
273 | click on the "Create" button; a new page will then be displayed with |
273 | some boxes to fill. You can also enter the OID in the following box:<br><form method="post" action="/cgi-bin/manage" enctype="multipart/form-data"> |
274 | some boxes to fill (see <a href="#guidelines">guidelines for describing an OID</a>). You can also enter the OID in the following box:<br><form method="post" action="/cgi-bin/manage" enctype="multipart/form-data"> |
274 | <input type="hidden" name="a" value="create"> <strong>{</strong> |
275 | <input type="hidden" name="a" value="create"> <strong>{</strong> |
275 | <input type="text" name="oid" size="30" value=""><strong>}</strong> |
276 | <input type="text" name="oid" size="30" value=""><strong>}</strong> |
276 | <input type="submit" name="submit" value="Create"></form> |
277 | <input type="submit" name="submit" value="Create"></form> |
277 | b. Go to the parent OID of the OID that you want to add (i.e. the |
278 | b. Go to the parent OID of the OID that you want to add (i.e. the |
278 | OID at the immediate upper level in the OID tree) and click on the |
279 | OID at the immediate upper level in the OID tree) and click on the |
279 | "Create a child OID" link on the top right-hand side of the page; |
280 | "Create a child OID" link on the top right-hand side of the page; |
280 | a new page will then be displayed with some boxes to fill.<br>c. Go to an OID at the same level as the OID that you want to add |
281 | a new page will then be displayed with some boxes to fill (see <a href="#guidelines">guidelines for describing an OID</a>).<br>c. Go to an OID at the same level as the OID that you want to add |
281 | (a.k.a. sibling OID) and click on the "Create a sibling OID" link |
282 | (a.k.a. sibling OID) and click on the "Create a sibling OID" link |
282 | on the top right-hand side of the page; a new page will then be displayed |
283 | on the top right-hand side of the page; a new page will then be displayed |
283 | with some boxes to fill.<br>d. If you have a lot of OID descriptions to add, it is more convenient |
284 | with some boxes to fill (see <a href="#guidelines">guidelines for describing an OID</a>).<br>d. If you have a lot of OID descriptions to add, it is more convenient |
284 | to describe them in an XML document that conforms to our <a href="oid.xsd">XML |
285 | to describe them in an XML document that conforms to our <a href="oid.xsd">XML |
285 | Schema for OIDs</a> and <a href="submit.htm">submit</a> this document |
286 | Schema for OIDs</a> and <a href="submit.htm">submit</a> this document |
286 | through the web interface. <br><em> |
287 | through the web interface. <br><em> |
287 | Note: In all 4 cases, the person (if any) you mention as <a href="#registration-authorities">registrant</a> |
288 | Note: In all 4 cases, the person (if any) you mention as <a href="#registration-authorities">registrant</a> |
288 | for the OID, and the person (if known) who is the <a href="#registration-authorities">registrant</a> |
289 | for the OID, and the person (if known) who is the <a href="#registration-authorities">registrant</a> |
Line 401... | Line 402... | ||
401 | <div class="question"> |
402 | <div class="question"> |
402 | How many OIDs are currently described in this repository?<a name="9"></a> |
403 | How many OIDs are currently described in this repository?<a name="9"></a> |
403 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
404 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
404 | </div> |
405 | </div> |
405 | <div class="answer"> |
406 | <div class="answer"> |
406 | There are more than 950 000 OID descriptions stored in our repository |
407 | There are close to 2 billion OID descriptions stored in this repository |
407 | (see <a href="/cgi-bin/display?a=count_nodes">exact number</a>). The |
408 | (see <a href="/cgi-bin/display?a=count_nodes">exact number</a>). The |
408 | repository is well alive and updated as often as necessary; <a href="/cgi-bin/display?a=count_nodes">statistics</a> |
409 | repository is well alive and updated as often as necessary; <a href="/cgi-bin/display?a=count_nodes">statistics</a> |
409 | are available about the number of OIDs added to the repository (or |
410 | are available about the number of OIDs added to the repository (or |
410 | updated) over the past 12 months. A (non-exhaustive) list of standards |
411 | updated) over the past 12 months. A (non-exhaustive) list of standards |
411 | (and other documents that define OIDs) which have been captured in |
412 | (and other documents that define OIDs) which have been captured in |
Line 550... | Line 551... | ||
550 | good idea is probably to look at <a href="country_oids.htm#agreements">how |
551 | good idea is probably to look at <a href="country_oids.htm#agreements">how |
551 | other countries have organized subsequent arcs beneath their country |
552 | other countries have organized subsequent arcs beneath their country |
552 | arc</a> as well as reading the ITU handbook on "<a href="http://www.itu.int/pub/T-HDB-LNG.4-2010"><em> |
553 | arc</a> as well as reading the ITU handbook on "<a href="http://www.itu.int/pub/T-HDB-LNG.4-2010"><em> |
553 | Object |
554 | Object |
554 | identifiers (OIDs) and their registration authorities |
555 | identifiers (OIDs) and their registration authorities |
555 | </em></a>".<br><br></div> |
556 | </em></a>". You can also take benefit from the |
- | 557 | <a href="#guidelines">guidelines to adequately describe an OID in this OID repository</a>.<br><br></div> |
|
556 | </li> |
558 | </li> |
557 | <li> |
559 | <li> |
558 | <div class="question"> |
560 | <div class="question"> |
559 | What is the Internet OID?<a name="13"></a> |
561 | What is the Internet OID?<a name="13"></a> |
560 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
562 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
Line 683... | Line 685... | ||
683 | The <a href="display-example.htm">description page</a> for each OID |
685 | The <a href="display-example.htm">description page</a> for each OID |
684 | offers the ability to: |
686 | offers the ability to: |
685 | <ul type="disc"> |
687 | <ul type="disc"> |
686 | <li> |
688 | <li> |
687 | have a synthetic <a href="/cgi-bin/display?tree=">graphical |
689 | have a synthetic <a href="/cgi-bin/display?tree=">graphical |
688 | view</a> of the tree (click on the<img src="images/pm.gif" width="19" height="18">and<img src="images/mm.gif" width="19" height="18">icons to |
690 | view</a> of the tree (click on the<img src="images/pm.gif" width="19" height="18" alt="Unfolding the subtree">and<img src="images/mm.gif" width="19" height="18" alt="Folding the subtree">icons to |
689 | fold and unfold arcs); |
691 | fold and unfold arcs); |
690 | </li> |
692 | </li> |
691 | <li>display the description of another OID (the "Go" button);</li> |
693 | <li>display the description of another OID (the "Go" button);</li> |
692 | <li> |
694 | <li> |
693 | use the "remote control" to display the description |
695 | use the "remote control" to display the description |
Line 800... | Line 802... | ||
800 | According to clause 8.2 f of <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation |
802 | According to clause 8.2 f of <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation |
801 | ITU-T X.660 | ISO/IEC 9834-1</a>, the registration record for an OID |
803 | ITU-T X.660 | ISO/IEC 9834-1</a>, the registration record for an OID |
802 | shall include at least:<br>a) the definition of the object (when the registration authority of |
804 | shall include at least:<br>a) the definition of the object (when the registration authority of |
803 | the parent OID performs a technical role, it checks that the objet |
805 | the parent OID performs a technical role, it checks that the objet |
804 | can be registered under the parent OID);<br>b) when applicable, the identifier (beginning with a lowercase letter) |
806 | can be registered under the parent OID);<br>b) when applicable, the identifier (beginning with a lowercase letter) |
805 | assigned to the object (in addition to the unique number);<br>b) the name and contact information of the organization that proposed |
807 | assigned to the object (in addition to the unique number);<br>c) the name and contact information of the organization that proposed |
806 | the entry (usually it is the "<a href="#registration-authorities">First |
808 | the entry (usually it is the "<a href="#registration-authorities">First |
807 | registration authority</a>" for the requested OID);<br>c) the dates of submission/registration.<br><br></div> |
809 | registration authority</a>" for the requested OID);<br>d) the dates of submission/registration.<br><br></div> |
808 | </li> |
810 | </li> |
809 | <li> |
811 | <li> |
810 | <div class="question"> |
812 | <div class="question"> |
811 | Is there a particular OID that can be used for documenting |
813 | Is there a particular OID that can be used for documenting |
812 | examples of object identifiers?<a name="22"></a><a name="example"></a> |
814 | examples of object identifiers?<a name="22"></a><a name="example"></a> |
Line 860... | Line 862... | ||
860 | </div> |
862 | </div> |
861 | <div class="answer"> |
863 | <div class="answer"> |
862 | The constraints are gathered in sections 4.6.5, 4.6.6, and Appendix |
864 | The constraints are gathered in sections 4.6.5, 4.6.6, and Appendix |
863 | D of IETF <a href="https://datatracker.ietf.org/doc/html/rfc4181">RFC 4181</a> |
865 | D of IETF <a href="https://datatracker.ietf.org/doc/html/rfc4181">RFC 4181</a> |
864 | (updated by <a href="https://datatracker.ietf.org/doc/html/rfc4841">RFC 4841</a>) |
866 | (updated by <a href="https://datatracker.ietf.org/doc/html/rfc4841">RFC 4841</a>) |
865 | which makes references to <a href="https://datatracker.ietf.org/doc/html/rfc2578">RFC |
867 | which makes references to IETF <a href="https://datatracker.ietf.org/doc/html/rfc2578">RFC |
866 | 2578</a>, sections 3.5, 3.6, 5.6, 7.10, and <a href="https://datatracker.ietf.org/doc/html/rfc3416">RFC |
868 | 2578</a>, sections 3.5, 3.6, 5.6, 7.10, and <a href="https://datatracker.ietf.org/doc/html/rfc3416">RFC |
867 | 3416</a>, section 4.1.<br> |
869 | 3416</a>, section 4.1.<br> |
868 | - 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> |
870 | - According to IETF <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> |
869 | - 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> |
871 | - 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 IETF <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> |
870 | </li> |
872 | </li> |
871 | <li> |
873 | <li> |
872 | <div class="question"> |
874 | <div class="question"> |
873 | 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> |
875 | 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> |
874 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
876 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
Line 1091... | Line 1093... | ||
1091 | only be used by the OID repository administrator to explain or undo |
1093 | only be used by the OID repository administrator to explain or undo |
1092 | changes if needed.<br>For any other question related to data protection or to request the |
1094 | changes if needed.<br>For any other question related to data protection or to request the |
1093 | rectification or erasure of your personal data, you can <a href="/helper">contact |
1095 | rectification or erasure of your personal data, you can <a href="/helper">contact |
1094 | the webmaster</a>. Repetitive, disproportionate or impracticable requests |
1096 | the webmaster</a>. Repetitive, disproportionate or impracticable requests |
1095 | may be rejected. |
1097 | may be rejected. |
- | 1098 | <br><br></div> |
|
- | 1099 | </li> |
|
- | 1100 | ||
- | 1101 | ||
- | 1102 | ||
- | 1103 | <li> |
|
- | 1104 | <div class="question"> |
|
- | 1105 | What are the guidelines to adequately describe an OID in this OID repository?<a name="34"></a><a name="guidelines"></a> |
|
- | 1106 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
|
- | 1107 | </div> |
|
- | 1108 | <div class="answer"> |
|
- | 1109 | The following rules are followed by the OID repository administrator to validate OID descriptions: |
|
- | 1110 | <ul> |
|
- | 1111 | <li>The description shall be as short as possible (usually, not more than one line) and focus on <em>what</em> (i.e., which object) is identified by the OID. The description shall not be a sentence (with a verb). Consequently, the description does not end up with a full stop "." (except when the full stop is part of an abbreviation). See also the <a href="#syntax-rules">syntax rules</a>.</li> |
|
- | 1112 | <li>The description should be easily understandable by any user of the OID repository. Substantives should not be put one after the other without inserting small words like "for", "of", etc. This helps understanding the description and avoids ambiguities when translating to other languages.</li> |
|
- | 1113 | <li>Useless expressions like "OID for", "OID identifying", "Root OID for", "Top arc for", "Arc for", "This OID describes", "This arc describes", etc., are forbidden.</li> |
|
- | 1114 | <li>Words are not capitalized (contrarily to what is usually done for paper or book titles in English) except for an abbreviation or acronym which is put between parentheses after the expression that defines it (with each letter of the abbreviation being capitalized in its definition), e.g., Meaning of My Abbreviation (MMA).</li> |
|
- | 1115 | <li>Any text (e.g., how it is used, how child OIDs are allocated, etc.) which is not related to <em>what</em> is identified by the OID shall be moved to the "Information" part. Any text which can be assimilated to a publicity or a company description shall be avoided (a URL can be associated to the company name).</li> |
|
- | 1116 | </ul> |
|
1096 | </div> |
1117 | </div> |
1097 | </li> |
1118 | </li> |
- | 1119 | ||
- | 1120 | ||
1098 | </ol> |
1121 | </ol> |
1099 | 1122 | ||
1100 | </td> |
1123 | </td> |
1101 | </tr> |
1124 | </tr> |
1102 | </table> |
1125 | </table> |
Line 1124... | Line 1147... | ||
1124 | d=new Date(document.lastModified) |
1147 | d=new Date(document.lastModified) |
1125 | month=new Array("Jan","Feb","Mar","Apr","May","Jun","Jul","Aug","Sep","Oct","Nov","Dec") |
1148 | month=new Array("Jan","Feb","Mar","Apr","May","Jun","Jul","Aug","Sep","Oct","Nov","Dec") |
1126 | if (Date.parse(document.lastModified) != 0) |
1149 | if (Date.parse(document.lastModified) != 0) |
1127 | document.write(d.getDate()+" "+month[d.getMonth()]+" "+d.getFullYear()); |
1150 | document.write(d.getDate()+" "+month[d.getMonth()]+" "+d.getFullYear()); |
1128 | </script>--> |
1151 | </script>--> |
1129 | 15 Jul 2022 |
1152 | 27 Nov 2022 |
1130 | </font> |
1153 | </font> |
1131 | </td> |
1154 | </td> |
1132 | <td width="24" align="center"><img src="images/pointorange_small.gif" width="14" height="10"></td> |
1155 | <td width="24" align="center"><img src="images/pointorange_small.gif" width="14" height="10"></td> |
1133 | <td align="center" width="409"> |
1156 | <td align="center" width="409"> |
1134 | <font size=-1> |
1157 | <font size=-1> |