Rev 15 | Rev 26 | Go to most recent revision | Show entire file | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed
| Rev 15 | Rev 20 | ||
|---|---|---|---|
| Line 44... | Line 44... | ||
| 44 | <li><a href="#iri">What is an OID-IRI (Internationalized Resource Identifier)?</a></li> |
44 | <li><a href="#iri">What is an OID-IRI (Internationalized Resource Identifier)?</a></li> |
| 45 | <li><a href="#29">What are the duties of a Registration Authority?</a></li> |
45 | <li><a href="#29">What are the duties of a Registration Authority?</a></li> |
| 46 | <li><a href="#size-limitations">Are there size limitations for OID encoding?</a></li> |
46 | <li><a href="#size-limitations">Are there size limitations for OID encoding?</a></li> |
| 47 | <li><a href="#31">Are there binary encoders/decoders for OIDs?</a></li> |
47 | <li><a href="#31">Are there binary encoders/decoders for OIDs?</a></li> |
| 48 | <li><a href="#cookies">Does this web site use cookies?</a></li> |
48 | <li><a href="#cookies">Does this web site use cookies?</a></li> |
| 49 | <li><a href="#33">How does this web site protect users' privacy?</a></li> |
49 | <li><a href="#privacy">How does this web site protect users' privacy?</a></li> |
| 50 | <li><a href="#guidelines">What are the guidelines to adequately describe an OID in this OID repository?</a></li> |
50 | <li><a href="#guidelines">What are the guidelines to adequately describe an OID in this OID repository?</a></li> |
| 51 | </ol><br></td> |
51 | </ol><br></td> |
| 52 | </tr> |
52 | </tr> |
| 53 | </table> |
53 | </table> |
| 54 | </div> |
54 | </div> |
| Line 65... | Line 65... | ||
| 65 | What are the standards that define OIDs and the OID tree?<a name="1"></a> |
65 | What are the standards that define OIDs and the OID tree?<a name="1"></a> |
| 66 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
66 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
| 67 | </div> |
67 | </div> |
| 68 | <div class="answer"> |
68 | <div class="answer"> |
| 69 | They are defined in the <a href="standards.htm">Recommendation ITU-T |
69 | They are defined in the <a href="standards.htm">Recommendation ITU-T |
| 70 | X.660 | ISO/IEC 9834 series</a>, and in particular in <a href="http://www.itu.int/ITU-T/X.660">Rec. |
70 | X.660 | ISO/IEC 9834 series</a>, and in particular in <a href="https://www.itu.int/ITU-T/X.660">Rec. |
| 71 | ITU-T X.660 | ISO/IEC 9834-1</a>.<br>Binary encodings of OIDs are specified in <a href="http://www.itu.int/rec/T-REC-X.690/en">Rec. |
71 | ITU-T X.660 | ISO/IEC 9834-1</a>.<br>Binary encodings of OIDs are specified in <a href="https://www.itu.int/rec/T-REC-X.690/en">Rec. |
| 72 | ITU-T X.690 | ISO/IEC 8825-1</a> for the Binary (BER) and Distinguished |
72 | ITU-T X.690 | ISO/IEC 8825-1</a> for the Binary (BER) and Distinguished |
| 73 | (DER) Encoding rules, in <a href="http://www.itu.int/rec/T-REC-X.691/en">Rec. |
73 | (DER) Encoding rules, in <a href="https://www.itu.int/rec/T-REC-X.691/en">Rec. |
| 74 | ITU-T X.691 | ISO/IEC 8825-2</a> for the Packed Encoding rules (PER). |
74 | ITU-T X.691 | ISO/IEC 8825-2</a> for the Packed Encoding rules (PER). |
| 75 | An XML encoding of OIDs is specified in <a href="http://www.itu.int/rec/T-REC-X.693/en">Rec. |
75 | An XML encoding of OIDs is specified in <a href="https://www.itu.int/rec/T-REC-X.693/en">Rec. |
| 76 | ITU-T X.693 | ISO/IEC 8825-3</a>. (See also <a href="http://www.itu.int/rec/T-REC-X.691/en">question |
76 | ITU-T X.693 | ISO/IEC 8825-3</a>. (See also <a href="https://www.itu.int/rec/T-REC-X.691/en">question |
| 77 | 31</a> about binary encoders/decoders for OIDs.)<br><br></div> |
77 | 31</a> about binary encoders/decoders for OIDs.)<br><br></div> |
| 78 | </li> |
78 | </li> |
| 79 | <li> |
79 | <li> |
| 80 | <div class="question"> |
80 | <div class="question"> |
| 81 | Which kind of objects can be referenced by OIDs?<a name="2"></a> |
81 | Which kind of objects can be referenced by OIDs?<a name="2"></a> |
| Line 93... | Line 93... | ||
| 93 | <li> |
93 | <li> |
| 94 | a <a href="country_oids.htm">country</a>, a company, a |
94 | a <a href="country_oids.htm">country</a>, a company, a |
| 95 | project; |
95 | project; |
| 96 | </li> |
96 | </li> |
| 97 | <li> |
97 | <li> |
| 98 | a certificate policy specified according to <a href="http://itu.int/ITU-T/X.500">Rec. |
98 | a certificate policy specified according to <a href="https://itu.int/ITU-T/X.500">Rec. |
| 99 | ITU-T X.500</a>; |
99 | ITU-T X.500</a>; |
| 100 | </li> |
100 | </li> |
| 101 | <li>an encryption algorithm (for example <a href="/get/1.3.14.3.2.26">SHA-1</a>);</li> |
101 | <li>an encryption algorithm (for example <a href="/get/1.3.14.3.2.26">SHA-1</a>);</li> |
| 102 | <li> |
102 | <li> |
| 103 | <a href="/get/2.27">identification schemes</a> for tag-based |
103 | <a href="/get/2.27">identification schemes</a> for tag-based |
| 104 | applications (see <a href="http://itu.int/ITU-T/X.668">Recommendation |
104 | applications (see <a href="https://itu.int/ITU-T/X.668">Recommendation |
| 105 | ITU-T X.668 | ISO/IEC 9834-9</a>); |
105 | ITU-T X.668 | ISO/IEC 9834-9</a>); |
| 106 | </li> |
106 | </li> |
| 107 | <li> |
107 | <li> |
| 108 | e-health data (for example, data from the <a href="/get/2.16.840.1.113883">HL7 |
108 | e-health data (for example, data from the <a href="/get/2.16.840.1.113883">HL7 |
| 109 | Consortium</a>); |
109 | Consortium</a>); |
| Line 126... | Line 126... | ||
| 126 | </li> |
126 | </li> |
| 127 | <li>a MIB for SNMP network management;</li> |
127 | <li>a MIB for SNMP network management;</li> |
| 128 | <li> |
128 | <li> |
| 129 | a managed object class, one of its attributes, a notification |
129 | a managed object class, one of its attributes, a notification |
| 130 | or even other templates used in the area of network management |
130 | or even other templates used in the area of network management |
| 131 | and the GDMO standard (see <a href="http://www.itu.int/rec/T-REC-X.722/en">Recommendation |
131 | and the GDMO standard (see <a href="https://www.itu.int/rec/T-REC-X.722/en">Recommendation |
| 132 | ITU-T X.722 | ISO/IEC 10165-4</a>); |
132 | ITU-T X.722 | ISO/IEC 10165-4</a>); |
| 133 | </li> |
133 | </li> |
| 134 | <li> |
134 | <li> |
| 135 | an information object (see <a href="http://www.itu.int/rec/T-REC-X.681/en">Recommendation |
135 | an information object (see <a href="https://www.itu.int/rec/T-REC-X.681/en">Recommendation |
| 136 | ITU-T X.681 | ISO/IEC 8824-2</a>); |
136 | ITU-T X.681 | ISO/IEC 8824-2</a>); |
| 137 | </li> |
137 | </li> |
| 138 | <li>the type of some part of an ITU-T X.400 electronic message body;</li> |
138 | <li>the type of some part of an ITU-T X.400 electronic message body;</li> |
| 139 | <li>a file format;</li> |
139 | <li>a file format;</li> |
| 140 | <li>etc.</li> |
140 | <li>etc.</li> |
| 141 | </ul> |
141 | </ul> |
| 142 | Examples of OID uses are also listed on the <a href="http://www.itu.int/oth/T0B04000048/en">ITU-T flyer</a>.<br><br></div> |
142 | Examples of OID uses are also listed on the <a href="https://www.itu.int/oth/T0B04000048/en">ITU-T flyer</a>.<br><br></div> |
| 143 | </li> |
143 | </li> |
| 144 | <li> |
144 | <li> |
| 145 | <div class="question"> |
145 | <div class="question"> |
| 146 | Where can I learn more about OIDs and their registration?<a name="3"></a> |
146 | Where can I learn more about OIDs and their registration?<a name="3"></a> |
| 147 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
147 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
| Line 149... | Line 149... | ||
| 149 | <div class="answer"> |
149 | <div class="answer"> |
| 150 | Apart from the <a href="standards.htm">official standards</a> (see |
150 | Apart from the <a href="standards.htm">official standards</a> (see |
| 151 | <a href="faq.htm#1">question 1</a>), OIDs are explained in: |
151 | <a href="faq.htm#1">question 1</a>), OIDs are explained in: |
| 152 | <ul> |
152 | <ul> |
| 153 | <li> |
153 | <li> |
| 154 | the <a href="http://www.itu.int/oth/T0B04000048/en">OID flyer</a> |
154 | the <a href="https://www.itu.int/oth/T0B04000048/en">OID flyer</a> |
| 155 | from ITU-T Study Group 17; |
155 | from ITU-T Study Group 17; |
| 156 | </li> |
156 | </li> |
| 157 | <li> |
157 | <li> |
| 158 | the quick <a href="doc/introduction%20to%20object%20identifiers%20(OIDs).pdf">introduction |
158 | the quick <a href="doc/introduction%20to%20object%20identifiers%20(OIDs).pdf">introduction |
| 159 | to OIDs</a>; |
159 | to OIDs</a>; |
| 160 | </li> |
160 | </li> |
| 161 | <li>the ITU handbook "<a href="http://www.itu.int/pub/T-HDB-LNG.4-2010">Object identifiers (OIDs) and their registration authorities</a>";</li> |
161 | <li>the ITU handbook "<a href="https://www.itu.int/pub/T-HDB-LNG.4-2010">Object identifiers (OIDs) and their registration authorities</a>";</li> |
| 162 | <li> |
162 | <li> |
| 163 | section 10.8 of Olivier Dubuisson's <a href="http://www.oss.com/asn1/dubuisson.html">book |
163 | section 10.8 of Olivier Dubuisson's <a href="https://www.oss.com/asn1/dubuisson.html">book |
| 164 | "ASN.1 - Communication between heterogeneous systems"</a>; |
164 | "ASN.1 - Communication between heterogeneous systems"</a>; |
| 165 | </li> |
165 | </li> |
| 166 | <li> |
166 | <li> |
| 167 | John Larmouth's <a href="http://www.oss.com/asn1/larmouth.html">book |
167 | John Larmouth's <a href="https://www.oss.com/asn1/larmouth.html">book |
| 168 | "ASN.1 complete"</a>; |
168 | "ASN.1 complete"</a>; |
| 169 | </li> |
169 | </li> |
| 170 | <li> |
170 | <li> |
| 171 | John Larmouth's tutorial "Registration authorities |
171 | John Larmouth's tutorial "Registration authorities |
| 172 | for OID components" [<a href="doc/OID-tutorial.htm">html</a>] |
172 | for OID components" [<a href="doc/OID-tutorial.htm">html</a>] |
| Line 185... | Line 185... | ||
| 185 | How to add information to the OID repository?<a name="4"></a> |
185 | How to add information to the OID repository?<a name="4"></a> |
| 186 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
186 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
| 187 | </div> |
187 | </div> |
| 188 | <div class="answer"> |
188 | <div class="answer"> |
| 189 | This OID repository is not an official Registration Authority, |
189 | This OID repository is not an official Registration Authority, |
| 190 | so any OID described in this OID repository has to be officially allocated |
190 | so any OID <a href="#guidelines">described</a> in this OID repository has to be officially allocated |
| 191 | by the Registration Authority of its parent OID. There are at least |
191 | by the Registration Authority of its parent OID. There are at least |
| 192 | 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 |
192 | 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 |
| 193 | following OID to the database" on the <a href="index.htm">main page</a> and |
193 | following OID to the database" on the <a href="index.htm">main page</a> and |
| 194 | click on the "Create" button; a new page will then be displayed with |
194 | click on the "Create" button; a new page will then be displayed with |
| 195 | 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"> |
195 | 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"> |
| Line 200... | Line 200... | ||
| 200 | OID at the immediate upper level in the OID tree) and click on the |
200 | OID at the immediate upper level in the OID tree) and click on the |
| 201 | "Create a child OID" link on the top right-hand side of the page; |
201 | "Create a child OID" link on the top right-hand side of the page; |
| 202 | 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 |
202 | 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 |
| 203 | (a.k.a. sibling OID) and click on the "Create a sibling OID" link |
203 | (a.k.a. sibling OID) and click on the "Create a sibling OID" link |
| 204 | on the top right-hand side of the page; a new page will then be displayed |
204 | on the top right-hand side of the page; a new page will then be displayed |
| 205 | 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 |
205 | with some boxes to fill (see <a href="#guidelines">guidelines for describing an OID</a>).<br>d. If you have a lot of <a href="#guidelines">OID descriptions</a> to add, it is more convenient |
| 206 | to describe them in an XML document that conforms to our <a href="oid.xsd">XML |
206 | to describe them in an XML document that conforms to our <a href="oid.xsd">XML |
| 207 | Schema for OIDs</a> and <a href="submit.htm">submit</a> this document |
207 | Schema for OIDs</a> and <a href="submit.htm">submit</a> this document |
| 208 | through the web interface. <br><em> |
208 | through the web interface. <br><em> |
| 209 | Note: In all 4 cases, the person (if any) you mention as <a href="#registration-authorities">registrant</a> |
209 | Note: In all 4 cases, the person (if any) you mention as <a href="#registration-authorities">registrant</a> |
| 210 | for the OID, and the person (if known) who is the <a href="#registration-authorities">registrant</a> |
210 | for the OID, and the person (if known) who is the <a href="#registration-authorities">registrant</a> |
| Line 228... | Line 228... | ||
| 228 | <form method="post" action="/cgi-bin/manage" enctype="multipart/form-data"> |
228 | <form method="post" action="/cgi-bin/manage" enctype="multipart/form-data"> |
| 229 | <input type="hidden" name="a" value="modify"> <strong>{</strong> |
229 | <input type="hidden" name="a" value="modify"> <strong>{</strong> |
| 230 | <input type="text" name="oid" size="30" value=""><strong>}</strong> |
230 | <input type="text" name="oid" size="30" value=""><strong>}</strong> |
| 231 | <input type="submit" name="submit" value="Suggest a modification"></form> |
231 | <input type="submit" name="submit" value="Suggest a modification"></form> |
| 232 | <em> |
232 | <em> |
| 233 | Note: Your proposed modifications will have to be validated by |
233 | Note: Your <a href="#guidelines">proposed modifications</a> will have to be validated by |
| 234 | the <a href="#registration-authorities">registrant</a> of the OID |
234 | the <a href="#registration-authorities">registrant</a> of the OID |
| 235 | being modified (if known), the <a href="#registration-authorities">registrant</a> |
235 | being modified (if known), the <a href="#registration-authorities">registrant</a> |
| 236 | of the parent OID (if known) and the OID repository administrator |
236 | of the parent OID (if known) and the OID repository administrator |
| 237 | (who will all be automatically informed by e-mail) before they get |
237 | (who will all be automatically informed by e-mail) before they get |
| 238 | published. |
238 | published. |
| Line 252... | Line 252... | ||
| 252 | <div class="question"> |
252 | <div class="question"> |
| 253 | How to delete an OID (or move it elsewhere in the OID tree)?<a name="6"></a> |
253 | How to delete an OID (or move it elsewhere in the OID tree)?<a name="6"></a> |
| 254 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
254 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
| 255 | </div> |
255 | </div> |
| 256 | <div class="answer"> |
256 | <div class="answer"> |
| 257 | According to <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation |
257 | According to <a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation |
| 258 | ITU-T X.660 | ISO 9834-1</a>, an OID shall not be deleted once it |
258 | ITU-T X.660 | ISO 9834-1</a>, an OID shall not be deleted once it |
| 259 | has been allocated by a Registration Authority. However if an OID |
259 | has been allocated by a Registration Authority. However if an OID |
| 260 | that is described in this OID repository has never been officially |
260 | that is described in this OID repository has never been officially |
| 261 | allocated by the Registration Authority for the parent OID (or is |
261 | allocated by the Registration Authority for the parent OID (or is |
| 262 | misplaced in the OID tree), you can request its deletion from the |
262 | misplaced in the OID tree), you can request its deletion from the |
| Line 280... | Line 280... | ||
| 280 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
280 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
| 281 | </div> |
281 | </div> |
| 282 | <div class="answer"> |
282 | <div class="answer"> |
| 283 | We get Harald's agreement to dump his repository and merge the data |
283 | We get Harald's agreement to dump his repository and merge the data |
| 284 | into our repository. This was done in June 2003 and our OID repository |
284 | into our repository. This was done in June 2003 and our OID repository |
| 285 | now encompasses <a href="http://www.alvestrand.no/objectid/">Harald's |
285 | now encompasses <a href="https://www.alvestrand.no/objectid/">Harald's |
| 286 | registry</a>.<br><br></div> |
286 | registry</a>.<br><br></div> |
| 287 | </li> |
287 | </li> |
| 288 | <li> |
288 | <li> |
| 289 | <div class="question"> |
289 | <div class="question"> |
| 290 | How to reference an OID description in this repository?<a name="8"></a><a name="get"></a> |
290 | How to reference an OID description in this repository?<a name="8"></a><a name="get"></a> |
| Line 292... | Line 292... | ||
| 292 | </div> |
292 | </div> |
| 293 | <div class="answer"> |
293 | <div class="answer"> |
| 294 | The shortest and easiest means is to append the OID (whether it is |
294 | The shortest and easiest means is to append the OID (whether it is |
| 295 | in <a href="#17">ASN.1 notation</a>, <a href="#14">dot notation</a>, |
295 | in <a href="#17">ASN.1 notation</a>, <a href="#14">dot notation</a>, |
| 296 | <a href="#iri">IRI notation</a> or <a href="https://datatracker.ietf.org/doc/html/rfc3061">URN |
296 | <a href="#iri">IRI notation</a> or <a href="https://datatracker.ietf.org/doc/html/rfc3061">URN |
| 297 | notation</a>) to the <a href="/get/">http://oid-info.com/get/</a> |
297 | notation</a>) to the <a href="/get/">https://oid-info.com/get/</a> |
| 298 | URL, <em>e.g.</em>: |
298 | URL, <em>e.g.</em>: |
| 299 | <ul> |
299 | <ul> |
| 300 | <li> <a href="/get/2.999">http://oid-info.com/get/2.999</a> (recommended);</li> |
300 | <li> <a href="/get/2.999">https://oid-info.com/get/2.999</a> (recommended);</li> |
| 301 | <li> |
301 | <li> |
| 302 | <a href="/get/%7Bjoint-iso-itu-t%20example(999)%7D">http://oid-info.com/get/{joint |
302 | <a href="/get/%7Bjoint-iso-itu-t%20example(999)%7D">https://oid-info.com/get/{joint |
| 303 | iso-itu-t example(999)}</a> (ASN.1 notation); |
303 | iso-itu-t example(999)}</a> (ASN.1 notation); |
| 304 | </li> |
304 | </li> |
| 305 | <li> |
305 | <li> |
| 306 | <a href="/get//Joint-ISO-ITU-T/Example">http://oid-info.com/get//Joint-ISO-ITU-T/Example</a> |
306 | <a href="/get//Joint-ISO-ITU-T/Example">https://oid-info.com/get//Joint-ISO-ITU-T/Example</a> |
| 307 | or <a href="/get//2/999">http://oid-info.com/get//2/999</a> (OID-IRI |
307 | or <a href="/get//2/999">https://oid-info.com/get//2/999</a> (OID-IRI |
| 308 | notation; with a '/' at the beginning of the OID notation, hence |
308 | notation; with a '/' at the beginning of the OID notation, hence |
| 309 | two '/'s after 'get'); |
309 | two '/'s after 'get'); |
| 310 | </li> |
310 | </li> |
| 311 | <li> |
311 | <li> |
| 312 | <a href="/get//Example">http://oid-info.com/get//Example</a> |
312 | <a href="/get//Example">https://oid-info.com/get//Example</a> |
| 313 | (OID-IRI notation using a long arc; with a '/' at the beginning |
313 | (OID-IRI notation using a long arc; with a '/' at the beginning |
| 314 | of the OID notation, hence two '/'s after 'get'); |
314 | of the OID notation, hence two '/'s after 'get'); |
| 315 | </li> |
315 | </li> |
| 316 | <li> |
316 | <li> |
| 317 | <a href="/get/urn:oid:2.999">http://oid-info.com/get/urn:oid:2.999</a> |
317 | <a href="/get/urn:oid:2.999">https://oid-info.com/get/urn:oid:2.999</a> |
| 318 | (URN notation).<br><br></li> |
318 | (URN notation).<br><br></li> |
| 319 | </ul> |
319 | </ul> |
| 320 | </div> |
320 | </div> |
| 321 | </li> |
321 | </li> |
| 322 | <li> |
322 | <li> |
| Line 337... | Line 337... | ||
| 337 | <div class="question"> |
337 | <div class="question"> |
| 338 | How to get an OID assigned?<a name="10"></a> |
338 | How to get an OID assigned?<a name="10"></a> |
| 339 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
339 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
| 340 | </div> |
340 | </div> |
| 341 | <div class="answer"> |
341 | <div class="answer"> |
| 342 | The original intention of the <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation |
342 | The original intention of the <a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation |
| 343 | ITU-T X.660 | ISO/IEC 9834</a> series was that anyone should be able |
343 | ITU-T X.660 | ISO/IEC 9834</a> series was that anyone should be able |
| 344 | to get an OID if they needed one. There are registration authorities |
344 | to get an OID if they needed one. There are registration authorities |
| 345 | from which it is easy and quite cheap (sometimes even free!) to have |
345 | from which it is easy and quite cheap (sometimes even free!) to have |
| 346 | an OID assigned, such as: |
346 | an OID assigned, such as: |
| 347 | <ul> |
347 | <ul> |
| Line 361... | Line 361... | ||
| 361 | country arc under <a href="/get/1.2"><code>{iso(1) member-body(2)}</code></a> |
361 | country arc under <a href="/get/1.2"><code>{iso(1) member-body(2)}</code></a> |
| 362 | or <a href="/get/2.16"><code>{joint-iso-itu-t(2) country(16)}</code></a>, |
362 | or <a href="/get/2.16"><code>{joint-iso-itu-t(2) country(16)}</code></a>, |
| 363 | please see <a href="#11">question 11</a> below.) |
363 | please see <a href="#11">question 11</a> below.) |
| 364 | </li> |
364 | </li> |
| 365 | <li> |
365 | <li> |
| 366 | <a href="http://pen.iana.org/pen/PenApplication.page">IANA</a> |
366 | <a href="https://pen.iana.org/pen/PenApplication.page">IANA</a> |
| 367 | (Internet Assigned Numbers Authority) hands out OIDs for free under |
367 | (Internet Assigned Numbers Authority) hands out OIDs for free under |
| 368 | <a href="/get/1.3.6.1.4.1"><code>{iso(1) identified-organization(3) |
368 | <a href="/get/1.3.6.1.4.1"><code>{iso(1) identified-organization(3) |
| 369 | dod(6) internet(1) private(4) enterprise(1)}</code></a>; these OIDs |
369 | dod(6) internet(1) private(4) enterprise(1)}</code></a>; these OIDs |
| 370 | are used a lot (but not only) to identify Management Information |
370 | are used a lot (but not only) to identify Management Information |
| 371 | Bases (MIBs) for network management (SNMP). |
371 | Bases (MIBs) for network management (SNMP). |
| 372 | </li> |
372 | </li> |
| 373 | <li> |
373 | <li> |
| 374 | <a href="https://www.viathinksoft.com/freeoid">ViaThinkSoft</a> |
374 | <a href="https://oidplus.viathinksoft.com/oidplus/?goto=oidplus:com.viathinksoft.freeoid">ViaThinkSoft</a> |
| 375 | freely assigns an OID to private persons and developers of freeware, |
375 | freely assigns an OID to private persons and developers of freeware, |
| 376 | shareware or open-source software under <a href="/get/1.3.6.1.4.1.37476.9000"><code>{iso(1) |
376 | shareware or open-source software under <a href="/get/1.3.6.1.4.1.37476.9000"><code>{iso(1) |
| 377 | identified-organization(3) dod(6) internet(1) private(4) enterprise(1) |
377 | identified-organization(3) dod(6) internet(1) private(4) enterprise(1) |
| 378 | 37476 freesub(9000)}</code></a>. |
378 | 37476 freesub(9000)}</code></a>. |
| 379 | </li> |
379 | </li> |
| 380 | <li> |
380 | <li> |
| 381 | <a href="http://webapp.etsi.org/ASN1ObjectTree/ASN1.asp">ETSI</a> |
381 | <a href="https://webapp.etsi.org/ASN1ObjectTree/ASN1.asp">ETSI</a> |
| 382 | (European Telecommunication Standards Institute) hands out OIDs |
382 | (European Telecommunication Standards Institute) hands out OIDs |
| 383 | under <code><a href="/get/0.4.0.127.0">{itu-t(0) identified-organization(4) |
383 | under <code><a href="/get/0.4.0.127.0">{itu-t(0) identified-organization(4) |
| 384 | etsi(0) reserved(127) etsi-identified-organization(0)}</a></code> |
384 | etsi(0) reserved(127) etsi-identified-organization(0)}</a></code> |
| 385 | even for non-ETSI-members. |
385 | even for non-ETSI-members. |
| 386 | </li> |
386 | </li> |
| Line 389... | Line 389... | ||
| 389 | network-operator(3)}</a></code>; telecom operators can have an OID |
389 | network-operator(3)}</a></code>; telecom operators can have an OID |
| 390 | assigned by their national PTT administration under <code><a href="/get/0.2">{itu-t(0) |
390 | assigned by their national PTT administration under <code><a href="/get/0.2">{itu-t(0) |
| 391 | administration(2)}</a></code>. |
391 | administration(2)}</a></code>. |
| 392 | </li> |
392 | </li> |
| 393 | <li> |
393 | <li> |
| 394 | For the health sector, see <a href="http://wiki.hl7.org/index.php?title=HL7_OID_Registry_Frequently_Asked_Questions#Somebody_told_me_I_need_an_OID_for_my_Organization._What_do_I_do.3F">HL7's |
394 | For the health sector, see <a href="https://wiki.hl7.org/index.php?title=HL7_OID_Registry_Frequently_Asked_Questions#Somebody_told_me_I_need_an_OID_for_my_Organization._What_do_I_do.3F">HL7's |
| 395 | FAQ</a>. |
395 | FAQ</a>. |
| 396 | </li> |
396 | </li> |
| 397 | <li> |
397 | <li> |
| 398 | Dave Harvey (UK) <a href="http://www.medicalconnections.co.uk/Free_UID">sub-delegate |
398 | Dave Harvey (UK) <a href="https://www.medicalconnections.co.uk/Free_UID">sub-delegate |
| 399 | ranges of his own OID</a> to anyone who uses a <a href="http://medical.nema.org/">DICOM</a> |
399 | ranges of his own OID</a> to anyone who uses a <a href="https://www.dicomstandard.org">DICOM</a> |
| 400 | toolkit (communication in medicine). |
400 | toolkit (communication in medicine). |
| 401 | </li> |
401 | </li> |
| 402 | <li> |
402 | <li> |
| 403 | You can <a href="http://msdn.microsoft.com/en-us/library/ms677620.aspx">obtain |
403 | You can <a href="https://learn.microsoft.com/en-us/windows/win32/ad/obtaining-an-object-identifier-from-microsoft?redirectedfrom=MSDN">obtain |
| 404 | an OID from Microsoft</a> to extend the Active Directory schema. |
404 | an OID from Microsoft</a> to extend the Active Directory schema. |
| 405 | </li> |
405 | </li> |
| 406 | <li> |
406 | <li> |
| 407 | You can <a href="http://www.itu.int/ITU-T/asn1/uuid.html#UUID%20Generation%20&%20Registration">generate |
407 | You can <a href="https://www.itu.int/ITU-T/asn1/uuid.html#UUID%20Generation%20&%20Registration">generate |
| 408 | a UUID</a> (or use a UUID that you already hold) and append it as |
408 | a UUID</a> (or use a UUID that you already hold) and append it as |
| 409 | a subsequent arc of <a href="/get/2.25"><code>{joint-iso-itu-t(2) |
409 | a subsequent arc of <a href="/get/2.25"><code>{joint-iso-itu-t(2) |
| 410 | uuid(25)}</code></a> (without registering it, in particular in this |
410 | uuid(25)}</code></a> (without registering it, in particular in this |
| 411 | OID repository, because it is guaranteed to be globally unique with |
411 | OID repository, because it is guaranteed to be globally unique with |
| 412 | a high probability) according to <a href="http://www.itu.int/rec/T-REC-X.667/en">Recommendation |
412 | a high probability) according to <a href="https://www.itu.int/rec/T-REC-X.667/en">Recommendation |
| 413 | ITU-T X.667 | ISO/IEC 9834-8</a> (but see <a href="#size-limitations">question |
413 | ITU-T X.667 | ISO/IEC 9834-8</a> (but see <a href="#size-limitations">question |
| 414 | 30 about size limitations of OID encodings</a>). |
414 | 30 about size limitations of OID encodings</a>). |
| 415 | </li> |
415 | </li> |
| 416 | </ul> |
416 | </ul> |
| 417 | <em>Important note</em>: OIDs have to be requested from those registrations authorities because this OID repository |
417 | <em>Important note</em>: OIDs have to be requested from those registrations authorities because this OID repository |
| Line 426... | Line 426... | ||
| 426 | </div> |
426 | </div> |
| 427 | <div class="answer"> |
427 | <div class="answer"> |
| 428 | Country arcs are the subsequent arcs of <a href="/get/1.2"><code>{iso(1) |
428 | Country arcs are the subsequent arcs of <a href="/get/1.2"><code>{iso(1) |
| 429 | member-body(2)}</code></a> and <a href="/get/2.16"><code>{joint-iso-itu-t(2) |
429 | member-body(2)}</code></a> and <a href="/get/2.16"><code>{joint-iso-itu-t(2) |
| 430 | country(16)}</code></a>. The values assigned to country arcs are the |
430 | country(16)}</code></a>. The values assigned to country arcs are the |
| 431 | <a href="http://unstats.un.org/unsd/methods/m49/m49alpha.htm">numerical |
431 | <a href="https://unstats.un.org/unsd/methods/m49/m49alpha.htm">numerical |
| 432 | codes</a> (without leading zeros) assigned by the United Nations Statistics |
432 | codes</a> (without leading zeros) assigned by the United Nations Statistics |
| 433 | Division together with the corresponding and the <a href="https://www.iso.org/obp/ui/#search">ISO |
433 | Division together with the corresponding and the <a href="https://www.iso.org/obp/ui/#search">ISO |
| 434 | 3166-1-alpha-2 code</a>. <a href="/get/1.2"><code>{iso(1) member-body(2)}</code></a> |
434 | 3166-1-alpha-2 code</a>. <a href="/get/1.2"><code>{iso(1) member-body(2)}</code></a> |
| 435 | was deprecated in favour of <a href="/get/2.16"><code>{joint-iso-itu-t(2) |
435 | was deprecated in favour of <a href="/get/2.16"><code>{joint-iso-itu-t(2) |
| 436 | country(16)}</code></a>, thus countries which have never been operating |
436 | country(16)}</code></a>, thus countries which have never been operating |
| 437 | a national Registration Authority (RA) for OIDs are encouraged to |
437 | a national Registration Authority (RA) for OIDs are encouraged to |
| 438 | request an arc under <a href="/get/2.16"><code>{joint-iso-itu-t(2) |
438 | request an arc under <a href="/get/2.16"><code>{joint-iso-itu-t(2) |
| 439 | country(16)}</code></a>. Countries are discouraged to request an arc |
439 | country(16)}</code></a>. Countries are discouraged to request an arc |
| 440 | under both <a href="/get/1.2"><code>{iso(1) member-body(2)}</code></a> |
440 | under both <a href="/get/1.2"><code>{iso(1) member-body(2)}</code></a> |
| 441 | and <a href="/get/2.16"><code>{joint-iso-itu-t(2) country(16)}</code></a>.<br><a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation ITU-T |
441 | and <a href="/get/2.16"><code>{joint-iso-itu-t(2) country(16)}</code></a>.<br><a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation ITU-T |
| 442 | X.660 | ISO/IEC 9834-1</a>, clause A.4.5, specifies that the <a href="http://www.iso.org/iso/about/iso_members.htm">ISO |
442 | X.660 | ISO/IEC 9834-1</a>, clause A.4.5, specifies that the <a href="https://www.iso.org/members.html">ISO |
| 443 | National Body</a> of the country and the <a href="http://www.itu.int/GlobalDirectory/search.html">administration |
443 | National Body</a> of the country and the <a href="https://www.itu.int/hub/membership/our-members/">administration |
| 444 | representing the country in the ITU</a> shall agree together (as a |
444 | representing the country in the ITU</a> shall agree together (as a |
| 445 | national decision) on the organization that will be the RA for their |
445 | national decision) on the organization that will be the RA for their |
| 446 | country arc. In the case of a country arc under <a href="/get/1.2"><code>{iso(1) |
446 | country arc. In the case of a country arc under <a href="/get/1.2"><code>{iso(1) |
| 447 | member-body(2)}</code></a> the decision is only taken by the <a href="http://www.iso.org/iso/about/iso_members.htm">ISO |
447 | member-body(2)}</code></a> the decision is only taken by the <a href="https://www.iso.org/members.html">ISO |
| 448 | National Body</a> of the country. For more detailed information, see |
448 | National Body</a> of the country. For more detailed information, see |
| 449 | "<a href="country_oids.htm">Operation of a country Registration |
449 | "<a href="country_oids.htm">Operation of a country Registration |
| 450 | Authority</a>".<br>One way to know if your country is already operating an RA for OIDs |
450 | Authority</a>".<br>One way to know if your country is already operating an RA for OIDs |
| 451 | is too check the <a href="country_oids.htm#agreements">known |
451 | is too check the <a href="country_oids.htm#agreements">known |
| 452 | country RAs</a>.<br><br></div> |
452 | country RAs</a>.<br><br></div> |
| Line 458... | Line 458... | ||
| 458 | </div> |
458 | </div> |
| 459 | <div class="answer"> |
459 | <div class="answer"> |
| 460 | Country arcs are the subsequent arcs of <a href="/get/1.2"><code>{iso(1) |
460 | Country arcs are the subsequent arcs of <a href="/get/1.2"><code>{iso(1) |
| 461 | member-body(2)}</code></a> and <a href="/get/2.16"><code>{joint-iso-itu-t(2) |
461 | member-body(2)}</code></a> and <a href="/get/2.16"><code>{joint-iso-itu-t(2) |
| 462 | country(16)}</code></a>.<br>The structure underneath a country arc is a national decision. The |
462 | country(16)}</code></a>.<br>The structure underneath a country arc is a national decision. The |
| 463 | basic standard is of course <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation |
463 | basic standard is of course <a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation |
| 464 | ITU-T X.660 | ISO/IEC 9834-1</a>. It might be worth having a look |
464 | ITU-T X.660 | ISO/IEC 9834-1</a>. It might be worth having a look |
| 465 | at <a href="http://www.itu.int/rec/T-REC-X.670/en">Recommendation |
465 | at <a href="https://www.itu.int/rec/T-REC-X.670/en">Recommendation |
| 466 | ITU-T X.670</a> "<em> |
466 | ITU-T X.670</a> "<em> |
| 467 | Procedures for registration agents operating |
467 | Procedures for registration agents operating |
| 468 | on behalf of organizations to register organization names subordinate |
468 | on behalf of organizations to register organization names subordinate |
| 469 | to country names |
469 | to country names |
| 470 | </em>".<br>There is no guidelines besides the fact that any registration authority |
470 | </em>".<br>There is no guidelines besides the fact that any registration authority |
| 471 | needs to keep records according to the aforementioned standards. A |
471 | needs to keep records according to the aforementioned standards. A |
| 472 | good idea is probably to look at <a href="country_oids.htm#agreements">how |
472 | good idea is probably to look at <a href="country_oids.htm#agreements">how |
| 473 | other countries have organized subsequent arcs beneath their country |
473 | other countries have organized subsequent arcs beneath their country |
| 474 | arc</a> as well as reading the ITU handbook on "<a href="http://www.itu.int/pub/T-HDB-LNG.4-2010"><em> |
474 | arc</a> as well as reading the ITU handbook on "<a href="https://www.itu.int/pub/T-HDB-LNG.4-2010"><em> |
| 475 | Object |
475 | Object |
| 476 | identifiers (OIDs) and their registration authorities |
476 | identifiers (OIDs) and their registration authorities |
| 477 | </em></a>". You can also take benefit from the |
477 | </em></a>". You can also take benefit from the |
| 478 | <a href="#guidelines">guidelines to adequately describe an OID in this OID repository</a>.<br><br></div> |
478 | <a href="#guidelines">guidelines to adequately describe an OID in this OID repository</a>.<br><br></div> |
| 479 | </li> |
479 | </li> |
| Line 490... | Line 490... | ||
| 490 | <div class="question"> |
490 | <div class="question"> |
| 491 | Where does the dot notation for OIDs come from?<a name="14"></a> |
491 | Where does the dot notation for OIDs come from?<a name="14"></a> |
| 492 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
492 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
| 493 | </div> |
493 | </div> |
| 494 | <div class="answer"> |
494 | <div class="answer"> |
| 495 | (<em>from Harald Alvestrand's <a href="http://www.alvestrand.no/objectid/index.html">website</a></em>)<br>The dot notation is an IETF invention. The ASN.1 group thought it |
495 | (<em>from Harald Alvestrand's <a href="https://www.alvestrand.no/objectid/index.html">website</a></em>)<br>The dot notation is an IETF invention. The ASN.1 group thought it |
| 496 | better to have a notation using spaces and braces, with optional text |
496 | better to have a notation using spaces and braces, with optional text |
| 497 | labels, so that <code>1.3.6.1</code> would become something like <code>{iso(1) |
497 | labels, so that <code>1.3.6.1</code> would become something like <code>{iso(1) |
| 498 | identified-organization(3) dod(6) internet(1)}</code> or <code>{1 |
498 | identified-organization(3) dod(6) internet(1)}</code> or <code>{1 |
| 499 | 3 6 1}</code> or variants thereof.<br>The IETF folks thought this was somewhat inconvenient, and decided |
499 | 3 6 1}</code> or variants thereof.<br>The IETF folks thought this was somewhat inconvenient, and decided |
| 500 | to use a space-free notation. This is, among other things, spelled |
500 | to use a space-free notation. This is, among other things, spelled |
| Line 512... | Line 512... | ||
| 512 | </div> |
512 | </div> |
| 513 | <div class="answer"> |
513 | <div class="answer"> |
| 514 | This enables optimized binary encodings in which all arcs beneath |
514 | This enables optimized binary encodings in which all arcs beneath |
| 515 | top-level arcs <code>0</code> and <code>1</code>, and arcs <code>0</code> |
515 | top-level arcs <code>0</code> and <code>1</code>, and arcs <code>0</code> |
| 516 | to <code>47</code> beneath top-level arc <code>2</code> are encoded |
516 | to <code>47</code> beneath top-level arc <code>2</code> are encoded |
| 517 | on a single octet (see <a href="http://www.itu.int/rec/T-REC-X.690/en">Rec. |
517 | on a single octet (see <a href="https://www.itu.int/rec/T-REC-X.690/en">Rec. |
| 518 | ITU-T X.690 | ISO/IEC 8825-1</a>, clause 8.19). Arcs greater to <code>47</code> |
518 | ITU-T X.690 | ISO/IEC 8825-1</a>, clause 8.19). Arcs greater to <code>47</code> |
| 519 | benath top-level arc <code>2</code> are hence encoded on more than |
519 | benath top-level arc <code>2</code> are hence encoded on more than |
| 520 | one octet.<br><br></div> |
520 | one octet.<br><br></div> |
| 521 | </li> |
521 | </li> |
| 522 | <li> |
522 | <li> |
| Line 660... | Line 660... | ||
| 660 | <li> |
660 | <li> |
| 661 | do a <a href="basic-search.htm">quick search</a> of the entire |
661 | do a <a href="basic-search.htm">quick search</a> of the entire |
| 662 | OID repository by searching for a particular string in all attributes; |
662 | OID repository by searching for a particular string in all attributes; |
| 663 | </li> |
663 | </li> |
| 664 | <li> |
664 | <li> |
| 665 | do an <a href="advanced-search.htm">advanced search</a> of the entire |
665 | do an <a href="search.htm">advanced search</a> of the entire |
| 666 | OID repository by searching for a particular value for each description |
666 | OID repository by searching for a particular value for each description |
| 667 | attribute or even by using regular expressions. |
667 | attribute or even by using regular expressions. |
| 668 | </li> |
668 | </li> |
| 669 | </ul> |
669 | </ul> |
| 670 | Other features are available from the <a href="index.htm">main page</a> of |
670 | Other features are available from the <a href="index.htm">main page</a> of |
| Line 698... | Line 698... | ||
| 698 | <div class="answer"> |
698 | <div class="answer"> |
| 699 | When adding information about an OID into the OID repository, non-ASCII |
699 | When adding information about an OID into the OID repository, non-ASCII |
| 700 | characters such as accentuated letters are allowed in most fields |
700 | characters such as accentuated letters are allowed in most fields |
| 701 | ("Description", "Information", registrant "First |
701 | ("Description", "Information", registrant "First |
| 702 | name", "Last name" and "Address"). The software |
702 | name", "Last name" and "Address"). The software |
| 703 | will replace them by their equivalent <a href="http://www.w3.org/MarkUp/html-spec/html-spec_13.html#SEC106">HTML |
703 | will replace them by their equivalent <a href="https://www.w3.org/MarkUp/html-spec/html-spec_13.html#SEC106">HTML |
| 704 | code</a>.<br>The following HTML tags are allowed in the "Description", |
704 | code</a>.<br>The following HTML tags are allowed in the "Description", |
| 705 | "Information" and "Address" fields: <code><a></code>, |
705 | "Information" and "Address" fields: <code><a></code>, |
| 706 | <code><br/></code>, <code><code></code>, <code><em></code>, |
706 | <code><br/></code>, <code><code></code>, <code><em></code>, |
| 707 | <code><img></code>, <code><li></code>, <code><ol></code>, |
707 | <code><img></code>, <code><li></code>, <code><ol></code>, |
| 708 | <code><strong></code>, <code><sub></code>, <code><sup></code> |
708 | <code><strong></code>, <code><sub></code>, <code><sup></code> |
| Line 718... | Line 718... | ||
| 718 | <div class="question"> |
718 | <div class="question"> |
| 719 | Which information is necessary to apply for an OID?<a name="21"></a><a name="oid-info"></a> |
719 | Which information is necessary to apply for an OID?<a name="21"></a><a name="oid-info"></a> |
| 720 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
720 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
| 721 | </div> |
721 | </div> |
| 722 | <div class="answer"> |
722 | <div class="answer"> |
| 723 | According to clause 8.2 f of <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation |
723 | According to clause 8.2 f of <a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation |
| 724 | ITU-T X.660 | ISO/IEC 9834-1</a>, the registration record for an OID |
724 | ITU-T X.660 | ISO/IEC 9834-1</a>, the registration record for an OID |
| 725 | shall include at least:<br>a) the definition of the object (when the registration authority of |
725 | shall include at least:<br>a) the <a href="#guidelines">definition</a> of the object (when the registration authority of |
| 726 | the parent OID performs a technical role, it checks that the objet |
726 | the parent OID performs a technical role, it checks that the objet |
| 727 | can be registered under the parent OID);<br>b) when applicable, the identifier (beginning with a lowercase letter) |
727 | can be registered under the parent OID);<br>b) when applicable, the identifier (beginning with a lowercase letter) |
| 728 | assigned to the object (in addition to the unique number);<br>c) the name and contact information of the organization that proposed |
728 | assigned to the object (in addition to the unique number);<br>c) the name and contact information of the organization that proposed |
| 729 | the entry (usually it is the "<a href="#registration-authorities">First |
729 | the entry (usually it is the "<a href="#registration-authorities">First |
| 730 | registration authority</a>" for the requested OID);<br>d) the dates of submission/registration.<br><br></div> |
730 | registration authority</a>" for the requested OID);<br>d) the dates of submission/registration.<br><br></div> |
| Line 760... | Line 760... | ||
| 760 | OID repository but it is important to understand that an OID first |
760 | OID repository but it is important to understand that an OID first |
| 761 | need to be <em>officially</em> allocated by an RA before it can be |
761 | need to be <em>officially</em> allocated by an RA before it can be |
| 762 | described on this website which is not an official RA, but a <em>repository</em> |
762 | described on this website which is not an official RA, but a <em>repository</em> |
| 763 | of information about existing OIDs.<br>The <em>first Registration Authority</em> of an OID is the very first |
763 | of information about existing OIDs.<br>The <em>first Registration Authority</em> of an OID is the very first |
| 764 | person or company to whom the OID was allocated by the RA of the superior |
764 | person or company to whom the OID was allocated by the RA of the superior |
| 765 | OID. According to <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation |
765 | OID. According to <a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation |
| 766 | ITU-T X.660 | ISO/IEC 9834-1</a>,<!-- clause 9.2.f.a --> the first |
766 | ITU-T X.660 | ISO/IEC 9834-1</a>,<!-- clause 9.2.f.a --> the first |
| 767 | RA can't be changed (if the responsibility is transfered to someone |
767 | RA can't be changed (if the responsibility is transfered to someone |
| 768 | else, the information is recorded in the "Current Registration |
768 | else, the information is recorded in the "Current Registration |
| 769 | Authority" section, without changing the "First Registration |
769 | Authority" section, without changing the "First Registration |
| 770 | Authority" section).<br>By default, if the OID has recently been allocated, the Current RA |
770 | Authority" section).<br>By default, if the OID has recently been allocated, the Current RA |
| Line 795... | Line 795... | ||
| 795 | <div class="question"> |
795 | <div class="question"> |
| 796 | 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> |
796 | 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> |
| 797 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
797 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
| 798 | </div> |
798 | </div> |
| 799 | <div class="answer"> |
799 | <div class="answer"> |
| 800 | - 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> |
800 | - If you're using <img src="images/firefox-icon.png" width="16" height="16" alt="[Firefox Icon]"><a href="https://www.mozilla.org/firefox/">Mozilla Firefox</a> or <img src="images/mozilla-icon.png" width="16" height="16" alt="[Mozilla Icon]"><a href="https://www.seamonkey-project.org">Mozilla SeaMonkey</a> |
| 801 | 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 |
801 | or <img src="images/google-chrome.ico" width="16" height="16" alt="[Chrome Icon]" border="0"><a href="https://www.google.com/chrome/">Google Chrome</a>, an <a href="https://mycroft.mozdev.org/search-engines.html?name=oid+resolver&skipcache=yes">OpenSearch |
| 802 | Plugin</a> (a.k.a. search engine) allows to display information about |
802 | Plugin</a> (a.k.a. search engine) allows to display information about |
| 803 | an OID when an ASN.1 notation, dot notation, <a href="https://datatracker.ietf.org/doc/html/rfc3061">URN</a> notation |
803 | an OID when an ASN.1 notation, dot notation, <a href="https://datatracker.ietf.org/doc/html/rfc3061">URN</a> notation |
| 804 | or <a href="#iri">OID-IRI</a> notation is entered in the search bar |
804 | or <a href="#iri">OID-IRI</a> notation is entered in the search bar |
| 805 | at the top-right.<br><!-- - If you're using <a href="http://www.mozilla.org/products/thunderbird/">Mozilla |
805 | at the top-right.<br><!-- - If you're using <a href="https://www.mozilla.org/products/thunderbird/">Mozilla |
| 806 | 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> |
806 | Thunderbird</a>, <img src="images/firefox-icon.png" width="16" height="16" alt="[Firefox Icon]"><a href="https://www.mozilla.org/products/firefox/">Mozilla Firefox</a> |
| 807 | 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> |
807 | or <img src="images/mozilla-icon.png" width="16" height="16" alt="[Mozilla Icon]"><a href="https://www.mozilla.org/projects/seamonkey/">Mozilla SeaMonkey</a> |
| 808 | (formerly known as Mozilla Application Suite), the <a href="http://dictionarysearch.mozdev.org">DictionarySearch |
808 | (formerly known as Mozilla Application Suite), the <a href="https://dictionarysearch.mozdev.org">DictionarySearch |
| 809 | add-on</a> is easy to configure so that you can display information |
809 | add-on</a> is easy to configure so that you can display information |
| 810 | about an OID by right-clicking on its selection:<br><ul> |
810 | about an OID by right-clicking on its selection:<br><ul> |
| 811 | <li>install the DictionarySearch extension corresponding to your |
811 | <li>install the DictionarySearch extension corresponding to your |
| 812 | tool from <a href="http://dictionarysearch.mozdev.org">http://dictionarysearch.mozdev.org</a>;</li> |
812 | tool from <a href="https://dictionarysearch.mozdev.org">https://dictionarysearch.mozdev.org</a>;</li> |
| 813 | <li>in the "Tools" menu of your tool, select the "Extensions" |
813 | <li>in the "Tools" menu of your tool, select the "Extensions" |
| 814 | item;</li> |
814 | item;</li> |
| 815 | <li>highlight the line for DictionarySearch, then click on the "Options" |
815 | <li>highlight the line for DictionarySearch, then click on the "Options" |
| 816 | button;</li> |
816 | button;</li> |
| 817 | <li>add a new Dictionary with the following information (this will |
817 | <li>add a new Dictionary with the following information (this will |
| 818 | display the description of the selected OID in dot notation; it |
818 | display the description of the selected OID in dot notation; it |
| 819 | doesn't work well for a selected OID in ASN.1 notation because |
819 | doesn't work well for a selected OID in ASN.1 notation because |
| 820 | the closing parentheses are removed for whatever reason):<br><em>Text</em>: <code>Search for OID "$"</code><br><em>Access key</em>: <code>O</code><br><em>URL</em>: <code>http://oid-info.com/cgi-bin/display?oid=$&a=display</code></li> |
820 | the closing parentheses are removed for whatever reason):<br><em>Text</em>: <code>Search for OID "$"</code><br><em>Access key</em>: <code>O</code><br><em>URL</em>: <code>https://oid-info.com/cgi-bin/display?oid=$&a=display</code></li> |
| 821 | <li>This other new "Dictionary" may also be useful (it |
821 | <li>This other new "Dictionary" may also be useful (it |
| 822 | will display a tree for the selected OID in dot notation):<br><em>Text</em>: <code>Display tree for OID "$"</code><br><em>Access key</em>: <code>T</code><br><em>URL</em>: <code>http://oid-info.com/cgi-bin/display?oid=$&a=tree</code> |
822 | will display a tree for the selected OID in dot notation):<br><em>Text</em>: <code>Display tree for OID "$"</code><br><em>Access key</em>: <code>T</code><br><em>URL</em>: <code>https://oid-info.com/cgi-bin/display?oid=$&a=tree</code> |
| 823 | </li> |
823 | </li> |
| 824 | </ul> --> - See also <a href="#8">question 8</a>.<br><br></div> |
824 | </ul> --> - See also <a href="#8">question 8</a>.<br><br></div> |
| 825 | </li> |
825 | </li> |
| 826 | <li> |
826 | <li> |
| 827 | <div class="question"> |
827 | <div class="question"> |
| Line 875... | Line 875... | ||
| 875 | Historically, OIDs could only be denoted in <a href="#14">dot notation</a> |
875 | Historically, OIDs could only be denoted in <a href="#14">dot notation</a> |
| 876 | (<em>e.g.</em>, <code>2.27</code>) or in <a href="#17">ASN.1 notation</a> |
876 | (<em>e.g.</em>, <code>2.27</code>) or in <a href="#17">ASN.1 notation</a> |
| 877 | (<em>e.g.</em>, <code>{joint-iso-itu-t(2) tag-based(27)}</code>) where |
877 | (<em>e.g.</em>, <code>{joint-iso-itu-t(2) tag-based(27)}</code>) where |
| 878 | only ASCII identifiers are allowed. The need was identified for a |
878 | only ASCII identifiers are allowed. The need was identified for a |
| 879 | human-friendly notation which would not be limited to latin alphabets |
879 | human-friendly notation which would not be limited to latin alphabets |
| 880 | and would encompass the diversity of <a href="http://www.unicode.org">Unicode |
880 | and would encompass the diversity of <a href="https://www.unicode.org">Unicode |
| 881 | alphabets</a>.<br>An OID-IRI (a.k.a. international OID) is a string of slash-separated |
881 | alphabets</a>.<br>An OID-IRI (a.k.a. international OID) is a string of slash-separated |
| 882 | Unicode labels from the root of the OID tree, which unambiguously |
882 | Unicode labels from the root of the OID tree, which unambiguously |
| 883 | identifies a node in the OID tree (e.g., "<a href="/get//Joint-ISO-ITU-T/Example"><code>/Joint-ISO-ITU-T/Example</code></a>").<br>A Unicode label is a case-sensitive string of Unicode characters (except |
883 | identifies a node in the OID tree (e.g., "<a href="/get//Joint-ISO-ITU-T/Example"><code>/Joint-ISO-ITU-T/Example</code></a>").<br>A Unicode label is a case-sensitive string of Unicode characters (except |
| 884 | the <code>SPACE</code> character). Just as an OID node can have multiple |
884 | the <code>SPACE</code> character). Just as an OID node can have multiple |
| 885 | identifiers in ASN.1 notation, it can have multiple Unicode labels |
885 | identifiers in ASN.1 notation, it can have multiple Unicode labels |
| Line 893... | Line 893... | ||
| 893 | an OID that is not immediately beneath the root of the OID tree. For |
893 | an OID that is not immediately beneath the root of the OID tree. For |
| 894 | example, OID <code>{joint-iso-itu-t(2) example(999)}</code> has a |
894 | example, OID <code>{joint-iso-itu-t(2) example(999)}</code> has a |
| 895 | long arc named "<code>Example</code>" allowing OID-IRI "<code><a href="/get//Example">/Example</a></code>" |
895 | long arc named "<code>Example</code>" allowing OID-IRI "<code><a href="/get//Example">/Example</a></code>" |
| 896 | which is shorter than OID-IRI "<code><a href="/get//Joint-ISO-ITU-T/Example">/Joint-ISO-ITU-T/Example</a></code>". |
896 | which is shorter than OID-IRI "<code><a href="/get//Joint-ISO-ITU-T/Example">/Joint-ISO-ITU-T/Example</a></code>". |
| 897 | Long arcs are only allowed for OIDs under the <code>joint-iso-itu-t(2)</code> |
897 | Long arcs are only allowed for OIDs under the <code>joint-iso-itu-t(2)</code> |
| 898 | top-level arc (see the <a href="http://itu.int/go/X660">register of |
898 | top-level arc (see the <a href="https://www.itu.int/go/X660">register of |
| 899 | long arcs)</a>.<br>The <a href="http://www.itu.int/rec/T-REC-X.680/en">ASN.1 standard</a> |
899 | long arcs)</a>.<br>The <a href="https://www.itu.int/rec/T-REC-X.680/en">ASN.1 standard</a> |
| 900 | specifies an <code>OID-IRI</code> type for exchanging OID-IRI values |
900 | specifies an <code>OID-IRI</code> type for exchanging OID-IRI values |
| 901 | between machines.<br><br></div> |
901 | between machines.<br><br></div> |
| 902 | </li> |
902 | </li> |
| 903 | <li> |
903 | <li> |
| 904 | <div class="question"> |
904 | <div class="question"> |
| 905 | What are the duties of a Registration Authority?<a name="29"></a> |
905 | What are the duties of a Registration Authority?<a name="29"></a> |
| 906 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
906 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
| 907 | </div> |
907 | </div> |
| 908 | <div class="answer"> |
908 | <div class="answer"> |
| 909 | Guidance is given in sections 8.2 (Operation), 9 (registration procedures) |
909 | Guidance is given in sections 8.2 (Operation), 9 (registration procedures) |
| 910 | and 11 (recommended fee structure) of <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation |
910 | and 11 (recommended fee structure) of <a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation |
| 911 | ITU-T X.660 | ISO/IEC 9834-1</a>.<br>The open-source database system <a href="https://oidplus.viathinksoft.com/oidplus/">OIDplus</a> |
911 | ITU-T X.660 | ISO/IEC 9834-1</a>.<br>The open-source database system <a href="https://oidplus.viathinksoft.com/oidplus/">OIDplus</a> |
| 912 | from ViaThinkSoft can be used by Registration Authorities to manage |
912 | from ViaThinkSoft can be used by Registration Authorities to manage |
| 913 | their OIDs. It includes a feature to export data into an <a href="submit.htm">XML |
913 | their OIDs. It includes a feature to export data into an <a href="submit.htm">XML |
| 914 | document that can then be uploaded to this OID repository</a>.<br><br></div> |
914 | document that can then be uploaded to this OID repository</a>.<br><br></div> |
| 915 | </li> |
915 | </li> |
| Line 918... | Line 918... | ||
| 918 | Are there size limitations for OID encoding?<a name="30"></a><a name="size-limitations"></a> |
918 | Are there size limitations for OID encoding?<a name="30"></a><a name="size-limitations"></a> |
| 919 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
919 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
| 920 | </div> |
920 | </div> |
| 921 | <div class="answer"> |
921 | <div class="answer"> |
| 922 | The <a href="standards.htm">OID standards</a> have no limit whatsoever about the depth of an OID in the OID tree (i.e., number of arcs) and the size of the integer associated to each OID arc. At the moment, the <a href="/get/1.3.6.1.4.1.1248.1.1.2.1.3.21.69.112.115.111.110.32.83.116.121.108.117.115.32.80.114.111.32.52.57.48.48">longest OID</a> described in the OID repository has 171 chars and 34 arcs. The <a href="/get/2.25.336702412625001560652410773774433371419">greatest number</a> for an OID arc has 39 digits. However, there are constraints for OIDs used in SNMP Management Information Bases (<a href="#mib">see question 24</a>) and some tools may have size limitations (or bugs):<br>- The <a href="https://lapo.it/asn1js/">ASN.1 JavaScript decoder at |
922 | The <a href="standards.htm">OID standards</a> have no limit whatsoever about the depth of an OID in the OID tree (i.e., number of arcs) and the size of the integer associated to each OID arc. At the moment, the <a href="/get/1.3.6.1.4.1.1248.1.1.2.1.3.21.69.112.115.111.110.32.83.116.121.108.117.115.32.80.114.111.32.52.57.48.48">longest OID</a> described in the OID repository has 171 chars and 34 arcs. The <a href="/get/2.25.336702412625001560652410773774433371419">greatest number</a> for an OID arc has 39 digits. However, there are constraints for OIDs used in SNMP Management Information Bases (<a href="#mib">see question 24</a>) and some tools may have size limitations (or bugs):<br>- The <a href="https://lapo.it/asn1js/">ASN.1 JavaScript decoder at |
| 923 | lapo.it</a>, <a href="http://www.bouncycastle.org">Bouncy Castle Crypto |
923 | lapo.it</a>, <a href="https://www.bouncycastle.org">Bouncy Castle Crypto |
| 924 | APIs</a>, OpenSSL (version 0.9.8o, 1 Jun 2010) and the built-in Java |
924 | APIs</a>, OpenSSL (version 0.9.8o, 1 Jun 2010) and the built-in Java |
| 925 | class "<code>org.ietf.jgss.Oid</code>" can handle <a href="/get/2.25">UUIDs |
925 | class "<code>org.ietf.jgss.Oid</code>" can handle <a href="/get/2.25">UUIDs |
| 926 | used as OIDs</a>.<br>- Windows CryptoAPI Shell Extension (tested with Windows XP and Windows |
926 | used as OIDs</a>.<br>- Windows CryptoAPI Shell Extension (tested with Windows XP and Windows |
| 927 | 7) cannot handle <a href="/get/2.25">UUIDs used as OIDs</a>: The maximum |
927 | 7) cannot handle <a href="/get/2.25">UUIDs used as OIDs</a>: The maximum |
| 928 | useable OID value in Windows is 2<sup>64</sup>-1 (e.g., <code>2.999.18446744073709551615</code>). |
928 | useable OID value in Windows is 2<sup>64</sup>-1 (e.g., <code>2.999.18446744073709551615</code>). |
| Line 930... | Line 930... | ||
| 930 | OIDs</a>: The maximum useable OID value in Mozilla software is 2<sup>32</sup>-1 |
930 | OIDs</a>: The maximum useable OID value in Mozilla software is 2<sup>32</sup>-1 |
| 931 | (e.g., <code>2.999.4294967295</code>). The program will show "Unknown" |
931 | (e.g., <code>2.999.4294967295</code>). The program will show "Unknown" |
| 932 | when an arc contains a higher value (e.g., <code>{2 999 Unknown 0}</code>). |
932 | when an arc contains a higher value (e.g., <code>{2 999 Unknown 0}</code>). |
| 933 | <br>- Mac OS X cannot handle OIDs of the form <code>2.<em>n</em></code> |
933 | <br>- Mac OS X cannot handle OIDs of the form <code>2.<em>n</em></code> |
| 934 | where <code><em>n</em></code> > 47 (i.e., it wrongly decodes OIDs |
934 | where <code><em>n</em></code> > 47 (i.e., it wrongly decodes OIDs |
| 935 | which need more than one octet in the first two arcs). <br>More details can be found in <a href="http://www.viathinksoft.de/~daniel-marschall/asn.1/oid_facts.html">Daniel |
935 | which need more than one octet in the first two arcs). <br>More details can be found in <a href="https://misc.daniel-marschall.de/asn.1/oid_facts.html">Daniel |
| 936 | Marschall's study about OID encoding and size limitations</a>. Daniel's |
936 | Marschall's study about OID encoding and size limitations</a>. Daniel's |
| 937 | <a href="https://www.viathinksoft.de/%7Edaniel-marschall/asn.1/oid-converter/online.php">DER |
937 | <a href="https://misc.daniel-marschall.de/asn.1/oid-converter/online.php">DER |
| 938 | encoder</a> can also help in your testing.<br><br></div> |
938 | encoder</a> can also help in your testing.<br><br></div> |
| 939 | </li> |
939 | </li> |
| 940 | <li> |
940 | <li> |
| 941 | <div class="question"> |
941 | <div class="question"> |
| 942 | Are there binary encoders/decoders for OIDs?<a name="31"></a> |
942 | Are there binary encoders/decoders for OIDs?<a name="31"></a> |
| 943 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
943 | <a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a> |
| 944 | </div> |
944 | </div> |
| 945 | <div class="answer"> |
945 | <div class="answer"> |
| 946 | See for example (non-exhaustive list):<strong><br></strong>- OSS Nokalva's online <a href="http://asn1-playground.oss.com/">ASN.1 |
946 | See for example (non-exhaustive list):<strong><br></strong>- OSS Nokalva's online <a href="https://asn1.io">ASN.1 |
| 947 | playground</a> encodes/decodes OIDs in any encoding rule (BER, DER, |
947 | playground</a> encodes/decodes OIDs in any encoding rule (BER, DER, |
| 948 | PER, UPER, XER) with the following schema:<br><code> OID-Module DEFINITIONS ::= BEGIN<br> OID ::= OBJECT IDENTIFIER<br> END</code><br> The OID is provided in ASN.1 notation in the "Data: |
948 | PER, UPER, XER) with the following schema:<br><code> OID-Module DEFINITIONS ::= BEGIN<br> OID ::= OBJECT IDENTIFIER<br> END</code><br> The OID is provided in ASN.1 notation in the "Data: |
| 949 | Encode" box as follows:<br><code> oid OID ::= {2 999}</code><br>- Daniel Marschall's online <a href="https://www.viathinksoft.de/%7Edaniel-marschall/asn.1/oid-converter/online.php">DER |
949 | Encode" box as follows:<br><code> oid OID ::= {2 999}</code><br>- Daniel Marschall's online <a href="https://misc.daniel-marschall.de/asn.1/oid-converter/online.php">DER |
| 950 | encoder/decoder</a> (for PHP and C);<br>- <a href="http://bouncycastle.org">The Legion of the Bouncy Castle</a>'s |
950 | encoder/decoder</a> (for PHP and C);<br>- <a href="https://bouncycastle.org">The Legion of the Bouncy Castle</a>'s |
| 951 | API for Java and C#;<br>- <a href="http://wireshark.org">Wireshark</a>'s subtool for ASN.1.<br>See also <a href="https://misc.daniel-marschall.de/asn.1/oid_facts.html#chap4">Daniel |
951 | API for Java and C#;<br>- <a href="https://www.wireshark.org">Wireshark</a>'s subtool for ASN.1.<br>See also <a href="https://misc.daniel-marschall.de/asn.1/oid_facts.html#chap4">Daniel |
| 952 | Marschall's software compatibility analysis for large OIDs</a>.<br><br></div> |
952 | Marschall's software compatibility analysis for large OIDs</a>.<br><br></div> |
| 953 | </li> |
953 | </li> |
| 954 | <li> |
954 | <li> |
| 955 | <div class="question"> |
955 | <div class="question"> |
| 956 | Does this web site use cookies?<a name="32"></a><a name="cookies"></a> |
956 | Does this web site use cookies?<a name="32"></a><a name="cookies"></a> |
| Line 962... | Line 962... | ||
| 962 | a new OID or proposed modifications to an existing OID) have a unique |
962 | a new OID or proposed modifications to an existing OID) have a unique |
| 963 | cookie placed on their machine with their first name, last name and |
963 | cookie placed on their machine with their first name, last name and |
| 964 | email address, so that the "submitter" section is automatically |
964 | email address, so that the "submitter" section is automatically |
| 965 | filled the next time they submit information. This cookie is not used |
965 | filled the next time they submit information. This cookie is not used |
| 966 | to track your use of the OID repository.<br>The <a href="/helper">OID helper</a> chatbot is (externally) hosted |
966 | to track your use of the OID repository.<br>The <a href="/helper">OID helper</a> chatbot is (externally) hosted |
| 967 | by <a href="http://pandorabots.com/botmaster/en/~121e02c2b4d4270afe6afac6~/faq">Pandorabots</a> |
967 | by <a href="https://pandorabots.com/botmaster/en/~121e02c2b4d4270afe6afac6~/faq">Pandorabots</a> |
| 968 | which normally tracks individual conversations by placing a cookie |
968 | which normally tracks individual conversations by placing a cookie |
| 969 | on your browser, in order to offer contextual answers to your questions |
969 | on your browser, in order to offer contextual answers to your questions |
| 970 | (please check <a href="https://home.pandorabots.com/policies.html#privacy-policy">Pandorabots' |
970 | (please check <a href="https://home.pandorabots.com/policies.html#privacy-policy">Pandorabots' |
| 971 | privacy policy</a>). However, if your browser is not setup to accept |
971 | privacy policy</a>). However, if your browser is not setup to accept |
| 972 | cookies, an alternative mechanism is used through a hidden variable |
972 | cookies, an alternative mechanism is used through a hidden variable |
| Line 1003... | Line 1003... | ||
| 1003 | authority of an OID; such requests are recorded). These users are |
1003 | authority of an OID; such requests are recorded). These users are |
| 1004 | automatically notified by email when information about them is entered |
1004 | automatically notified by email when information about them is entered |
| 1005 | and can request deletion of such data.<br>In some cases, your personal data appears in the OID repository because |
1005 | and can request deletion of such data.<br>In some cases, your personal data appears in the OID repository because |
| 1006 | it is publicly available on another web site (e.g., <a href="https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers">IANA |
1006 | it is publicly available on another web site (e.g., <a href="https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers">IANA |
| 1007 | enterprise numbers</a>).<br>To check if personal data related to you appears in the OID repository, |
1007 | enterprise numbers</a>).<br>To check if personal data related to you appears in the OID repository, |
| 1008 | please use the <a href="advanced-search.htm">advanced search</a>. You can |
1008 | please use the <a href="search.htm">advanced search</a>. You can |
| 1009 | also <a href="/cgi-bin/manage?a=get-personal-data">get a copy</a> |
1009 | also <a href="/cgi-bin/manage?a=get-personal-data">get a copy</a> |
| 1010 | of all personal data appearing in the OID repository. In any case, |
1010 | of all personal data appearing in the OID repository. In any case, |
| 1011 | your personal data is never used for sending any kind of publicity |
1011 | your personal data is never used for sending any kind of publicity |
| 1012 | to you.<br>A log of all modifications made to an OID is also kept (hence your |
1012 | to you.<br>A log of all modifications made to an OID is also kept (hence your |
| 1013 | personal data may appear in that log) but it is not public and would |
1013 | personal data may appear in that log) but it is not public and would |