Subversion Repositories oidinfo_new_design

Compare Revisions

Regard whitespace Rev 19 → Rev 20

/trunk/advanced-search.htm
424,7 → 424,8
<td colspan="2" valign="middle" height="8%">
<div align="left">
<span style="font-size:12px;">
The <a href="faq.htm#registration-authorities">registration authority</a> is either the person or company (if known) who is currently
The <a href="faq.htm">registration
authority</a> is either the person or company (if known) who is currently
in charge of managing the OID, allocating subarcs and registering
information on these subarcs, <strong>or</strong> the first person or company
(if known) who was responsible to manage the OID in the first instance
/trunk/daniel_internal/hyperlink_compare.php
0,0 → 1,11
<?php
 
//$cont = file_get_contents('http://oid-info.com/faq.htm');
$cont = file_get_contents(__DIR__.'/../faq.raw.htm');
 
 
preg_match_all('@href="(.+)"@ismU', $cont, $m);
foreach ($m[1] as $link) {
if ($link == '#top') continue;
echo "$link\n";
}
/trunk/doc/ICD-list.htm
1,5 → 1,4
 
<!-- saved from url=(0040)http://www.oid-info.com/doc/ICD-list.htm -->
<html><head><meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
 
<meta name="Generator" content="Microsoft Word 11 (filtered)">
/trunk/faq.htm
125,7 → 125,7
<li><a href="#size-limitations">Are there size limitations for OID encoding?</a></li>
<li><a href="#31">Are there binary encoders/decoders for OIDs?</a></li>
<li><a href="#cookies">Does this web site use cookies?</a></li>
<li><a href="#33">How does this web site protect users' privacy?</a></li>
<li><a href="#privacy">How does this web site protect users' privacy?</a></li>
<li><a href="#guidelines">What are the guidelines to adequately describe an OID in this OID repository?</a></li>
</ol><br></td>
</tr>
146,13 → 146,13
</div>
<div class="answer">
They are defined in the <a href="standards.htm">Recommendation ITU-T
X.660 | ISO/IEC 9834 series</a>, and in particular in <a href="http://www.itu.int/ITU-T/X.660">Rec.
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.
X.660 | ISO/IEC 9834 series</a>, and in particular in <a href="https://www.itu.int/ITU-T/X.660">Rec.
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.
ITU-T X.690 | ISO/IEC 8825-1</a> for the Binary (BER) and Distinguished
(DER) Encoding rules, in <a href="http://www.itu.int/rec/T-REC-X.691/en">Rec.
(DER) Encoding rules, in <a href="https://www.itu.int/rec/T-REC-X.691/en">Rec.
ITU-T X.691 | ISO/IEC 8825-2</a> for the Packed Encoding rules (PER).
An XML encoding of OIDs is specified in <a href="http://www.itu.int/rec/T-REC-X.693/en">Rec.
ITU-T X.693 | ISO/IEC 8825-3</a>. (See also <a href="http://www.itu.int/rec/T-REC-X.691/en">question
An XML encoding of OIDs is specified in <a href="https://www.itu.int/rec/T-REC-X.693/en">Rec.
ITU-T X.693 | ISO/IEC 8825-3</a>. (See also <a href="https://www.itu.int/rec/T-REC-X.691/en">question
31</a> about binary encoders/decoders for OIDs.)<br><br></div>
</li>
<li>
174,13 → 174,13
project;
</li>
<li>
a certificate policy specified according to <a href="http://itu.int/ITU-T/X.500">Rec.
a certificate policy specified according to <a href="https://itu.int/ITU-T/X.500">Rec.
ITU-T X.500</a>;
</li>
<li>an encryption algorithm (for example <a href="/get/1.3.14.3.2.26">SHA-1</a>);</li>
<li>
<a href="/get/2.27">identification schemes</a> for tag-based
applications (see <a href="http://itu.int/ITU-T/X.668">Recommendation
applications (see <a href="https://itu.int/ITU-T/X.668">Recommendation
ITU-T X.668 | ISO/IEC 9834-9</a>);
</li>
<li>
207,11 → 207,11
<li>
a managed object class, one of its attributes, a notification
or even other templates used in the area of network management
and the GDMO standard (see <a href="http://www.itu.int/rec/T-REC-X.722/en">Recommendation
and the GDMO standard (see <a href="https://www.itu.int/rec/T-REC-X.722/en">Recommendation
ITU-T X.722 | ISO/IEC 10165-4</a>);
</li>
<li>
an information object (see <a href="http://www.itu.int/rec/T-REC-X.681/en">Recommendation
an information object (see <a href="https://www.itu.int/rec/T-REC-X.681/en">Recommendation
ITU-T X.681 | ISO/IEC 8824-2</a>);
</li>
<li>the type of some part of an ITU-T X.400 electronic message body;</li>
218,7 → 218,7
<li>a file format;</li>
<li>etc.</li>
</ul>
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>
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>
</li>
<li>
<div class="question">
230,7 → 230,7
<a href="faq.htm#1">question 1</a>), OIDs are explained in:
<ul>
<li>
the <a href="http://www.itu.int/oth/T0B04000048/en">OID flyer</a>
the <a href="https://www.itu.int/oth/T0B04000048/en">OID flyer</a>
from ITU-T Study Group 17;
</li>
<li>
237,13 → 237,13
the quick <a href="doc/introduction%20to%20object%20identifiers%20(OIDs).pdf">introduction
to OIDs</a>;
</li>
<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>
<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>
<li>
section 10.8 of Olivier Dubuisson's <a href="http://www.oss.com/asn1/dubuisson.html">book
section 10.8 of Olivier Dubuisson's <a href="https://www.oss.com/asn1/dubuisson.html">book
&quot;ASN.1 - Communication between heterogeneous systems&quot;</a>;
</li>
<li>
John Larmouth's <a href="http://www.oss.com/asn1/larmouth.html">book
John Larmouth's <a href="https://www.oss.com/asn1/larmouth.html">book
&quot;ASN.1 complete&quot;</a>;
</li>
<li>
266,7 → 266,7
</div>
<div class="answer">
This OID repository is not an official Registration Authority,
so any OID described in this OID repository has to be officially allocated
so any OID <a href="#guidelines">described</a> in this OID repository has to be officially allocated
by the Registration Authority of its parent OID. There are at least
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
following OID to the database" on the <a href="index.htm">main page</a> and
281,7 → 281,7
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
(a.k.a. sibling OID) and click on the "Create a sibling OID" link
on the top right-hand side of the page; a new page will then be displayed
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
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
to describe them in an XML document that conforms to our <a href="oid.xsd">XML
Schema for OIDs</a> and <a href="submit.htm">submit</a> this document
through the web interface. <br><em>
309,7 → 309,7
<input type="text" name="oid" size="30" value=""><strong>}</strong>
<input type="submit" name="submit" value="Suggest a modification"></form>
<em>
Note: Your proposed modifications will have to be validated by
Note: Your <a href="#guidelines">proposed modifications</a> will have to be validated by
the <a href="#registration-authorities">registrant</a> of the OID
being modified (if known), the <a href="#registration-authorities">registrant</a>
of the parent OID (if known) and the OID repository administrator
333,7 → 333,7
<a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a>
</div>
<div class="answer">
According to <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation
According to <a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation
ITU-T X.660 | ISO 9834-1</a>, an OID shall not be deleted once it
has been allocated by a Registration Authority. However if an OID
that is described in this OID repository has never been officially
361,7 → 361,7
<div class="answer">
We get Harald's agreement to dump his repository and merge the data
into our repository. This was done in June 2003 and our OID repository
now encompasses <a href="http://www.alvestrand.no/objectid/">Harald's
now encompasses <a href="https://www.alvestrand.no/objectid/">Harald's
registry</a>.<br><br></div>
</li>
<li>
373,27 → 373,27
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://datatracker.ietf.org/doc/html/rfc3061">URN
notation</a>) to the <a href="/get/">http://oid-info.com/get/</a>
notation</a>) to the <a href="/get/">https://oid-info.com/get/</a>
URL, <em>e.g.</em>:
<ul>
<li> <a href="/get/2.999">http://oid-info.com/get/2.999</a> (recommended);</li>
<li> <a href="/get/2.999">https://oid-info.com/get/2.999</a> (recommended);</li>
<li>
<a href="/get/%7Bjoint-iso-itu-t%20example(999)%7D">http://oid-info.com/get/{joint
<a href="/get/%7Bjoint-iso-itu-t%20example(999)%7D">https://oid-info.com/get/{joint
iso-itu-t example(999)}</a> (ASN.1 notation);
</li>
<li>
<a href="/get//Joint-ISO-ITU-T/Example">http://oid-info.com/get//Joint-ISO-ITU-T/Example</a>
or <a href="/get//2/999">http://oid-info.com/get//2/999</a> (OID-IRI
<a href="/get//Joint-ISO-ITU-T/Example">https://oid-info.com/get//Joint-ISO-ITU-T/Example</a>
or <a href="/get//2/999">https://oid-info.com/get//2/999</a> (OID-IRI
notation; with a '/' at the beginning of the OID notation, hence
two '/'s after 'get');
</li>
<li>
<a href="/get//Example">http://oid-info.com/get//Example</a>
<a href="/get//Example">https://oid-info.com/get//Example</a>
(OID-IRI notation using a long arc; with a '/' at the beginning
of the OID notation, hence two '/'s after 'get');
</li>
<li>
<a href="/get/urn:oid:2.999">http://oid-info.com/get/urn:oid:2.999</a>
<a href="/get/urn:oid:2.999">https://oid-info.com/get/urn:oid:2.999</a>
(URN notation).<br><br></li>
</ul>
</div>
418,7 → 418,7
<a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a>
</div>
<div class="answer">
The original intention of the <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation
The original intention of the <a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation
ITU-T X.660 | ISO/IEC 9834</a> series was that anyone should be able
to get an OID if they needed one. There are registration authorities
from which it is easy and quite cheap (sometimes even free!) to have
442,7 → 442,7
please see <a href="#11">question 11</a> below.)
</li>
<li>
<a href="http://pen.iana.org/pen/PenApplication.page">IANA</a>
<a href="https://pen.iana.org/pen/PenApplication.page">IANA</a>
(Internet Assigned Numbers Authority) hands out OIDs for free under
<a href="/get/1.3.6.1.4.1"><code>{iso(1) identified-organization(3)
dod(6) internet(1) private(4) enterprise(1)}</code></a>; these OIDs
450,7 → 450,7
Bases (MIBs) for network management (SNMP).
</li>
<li>
<a href="https://www.viathinksoft.com/freeoid">ViaThinkSoft</a>
<a href="https://oidplus.viathinksoft.com/oidplus/?goto=oidplus:com.viathinksoft.freeoid">ViaThinkSoft</a>
freely assigns an OID to private persons and developers of freeware,
shareware or open-source software under <a href="/get/1.3.6.1.4.1.37476.9000"><code>{iso(1)
identified-organization(3) dod(6) internet(1) private(4) enterprise(1)
457,7 → 457,7
37476 freesub(9000)}</code></a>.
</li>
<li>
<a href="http://webapp.etsi.org/ASN1ObjectTree/ASN1.asp">ETSI</a>
<a href="https://webapp.etsi.org/ASN1ObjectTree/ASN1.asp">ETSI</a>
(European Telecommunication Standards Institute) hands out OIDs
under <code><a href="/get/0.4.0.127.0">{itu-t(0) identified-organization(4)
etsi(0) reserved(127) etsi-identified-organization(0)}</a></code>
470,25 → 470,25
administration(2)}</a></code>.
</li>
<li>
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
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
FAQ</a>.
</li>
<li>
Dave Harvey (UK) <a href="http://www.medicalconnections.co.uk/Free_UID">sub-delegate
ranges of his own OID</a> to anyone who uses a <a href="http://medical.nema.org/">DICOM</a>
Dave Harvey (UK) <a href="https://www.medicalconnections.co.uk/Free_UID">sub-delegate
ranges of his own OID</a> to anyone who uses a <a href="https://www.dicomstandard.org">DICOM</a>
toolkit (communication in medicine).
</li>
<li>
You can <a href="http://msdn.microsoft.com/en-us/library/ms677620.aspx">obtain
You can <a href="https://learn.microsoft.com/en-us/windows/win32/ad/obtaining-an-object-identifier-from-microsoft?redirectedfrom=MSDN">obtain
an OID from Microsoft</a> to extend the Active Directory schema.
</li>
<li>
You can <a href="http://www.itu.int/ITU-T/asn1/uuid.html#UUID%20Generation%20&amp;%20Registration">generate
You can <a href="https://www.itu.int/ITU-T/asn1/uuid.html#UUID%20Generation%20&amp;%20Registration">generate
a UUID</a> (or use a UUID that you already hold) and append it as
a subsequent arc of <a href="/get/2.25"><code>{joint-iso-itu-t(2)
uuid(25)}</code></a> (without registering it, in particular in this
OID repository, because it is guaranteed to be globally unique with
a high probability) according to <a href="http://www.itu.int/rec/T-REC-X.667/en">Recommendation
a high probability) according to <a href="https://www.itu.int/rec/T-REC-X.667/en">Recommendation
ITU-T X.667 | ISO/IEC 9834-8</a> (but see <a href="#size-limitations">question
30 about size limitations of OID encodings</a>).
</li>
507,7 → 507,7
Country arcs are the subsequent arcs of <a href="/get/1.2"><code>{iso(1)
member-body(2)}</code></a> and <a href="/get/2.16"><code>{joint-iso-itu-t(2)
country(16)}</code></a>. The values assigned to country arcs are the
<a href="http://unstats.un.org/unsd/methods/m49/m49alpha.htm">numerical
<a href="https://unstats.un.org/unsd/methods/m49/m49alpha.htm">numerical
codes</a> (without leading zeros) assigned by the United Nations Statistics
Division together with the corresponding and the <a href="https://www.iso.org/obp/ui/#search">ISO
3166-1-alpha-2 code</a>. <a href="/get/1.2"><code>{iso(1) member-body(2)}</code></a>
517,13 → 517,13
request an arc under <a href="/get/2.16"><code>{joint-iso-itu-t(2)
country(16)}</code></a>. Countries are discouraged to request an arc
under both <a href="/get/1.2"><code>{iso(1) member-body(2)}</code></a>
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
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
National Body</a> of the country and the <a href="http://www.itu.int/GlobalDirectory/search.html">administration
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
X.660 | ISO/IEC 9834-1</a>, clause A.4.5, specifies that the <a href="https://www.iso.org/members.html">ISO
National Body</a> of the country and the <a href="https://www.itu.int/hub/membership/our-members/">administration
representing the country in the ITU</a> shall agree together (as a
national decision) on the organization that will be the RA for their
country arc. In the case of a country arc under <a href="/get/1.2"><code>{iso(1)
member-body(2)}</code></a> the decision is only taken by the <a href="http://www.iso.org/iso/about/iso_members.htm">ISO
member-body(2)}</code></a> the decision is only taken by the <a href="https://www.iso.org/members.html">ISO
National Body</a> of the country. For more detailed information, see
&quot;<a href="country_oids.htm">Operation of a country Registration
Authority</a>&quot;.<br>One way to know if your country is already operating an RA for OIDs
539,9 → 539,9
Country arcs are the subsequent arcs of <a href="/get/1.2"><code>{iso(1)
member-body(2)}</code></a> and <a href="/get/2.16"><code>{joint-iso-itu-t(2)
country(16)}</code></a>.<br>The structure underneath a country arc is a national decision. The
basic standard is of course <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation
basic standard is of course <a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation
ITU-T X.660 | ISO/IEC 9834-1</a>. It might be worth having a look
at <a href="http://www.itu.int/rec/T-REC-X.670/en">Recommendation
at <a href="https://www.itu.int/rec/T-REC-X.670/en">Recommendation
ITU-T X.670</a> "<em>
Procedures for registration agents operating
on behalf of organizations to register organization names subordinate
550,7 → 550,7
needs to keep records according to the aforementioned standards. A
good idea is probably to look at <a href="country_oids.htm#agreements">how
other countries have organized subsequent arcs beneath their country
arc</a> as well as reading the ITU handbook on &quot;<a href="http://www.itu.int/pub/T-HDB-LNG.4-2010"><em>
arc</a> as well as reading the ITU handbook on &quot;<a href="https://www.itu.int/pub/T-HDB-LNG.4-2010"><em>
Object
identifiers (OIDs) and their registration authorities
</em></a>&quot;. You can also take benefit from the
571,7 → 571,7
<a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a>
</div>
<div class="answer">
(<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
(<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
better to have a notation using spaces and braces, with optional text
labels, so that <code>1.3.6.1</code> would become something like <code>{iso(1)
identified-organization(3) dod(6) internet(1)}</code> or <code>{1
593,7 → 593,7
This enables optimized binary encodings in which all arcs beneath
top-level arcs <code>0</code> and <code>1</code>, and arcs <code>0</code>
to <code>47</code> beneath top-level arc <code>2</code> are encoded
on a single octet (see <a href="http://www.itu.int/rec/T-REC-X.690/en">Rec.
on a single octet (see <a href="https://www.itu.int/rec/T-REC-X.690/en">Rec.
ITU-T X.690 | ISO/IEC 8825-1</a>, clause 8.19). Arcs greater to <code>47</code>
benath top-level arc <code>2</code> are hence encoded on more than
one octet.<br><br></div>
741,7 → 741,7
OID repository by searching for a particular string in all attributes;
</li>
<li>
do an <a href="advanced-search.htm">advanced search</a> of the entire
do an <a href="search.htm">advanced search</a> of the entire
OID repository by searching for a particular value for each description
attribute or even by using regular expressions.
</li>
779,7 → 779,7
characters such as accentuated letters are allowed in most fields
(&quot;Description&quot;, &quot;Information&quot;, registrant &quot;First
name&quot;, &quot;Last name&quot; and &quot;Address&quot;). The software
will replace them by their equivalent <a href="http://www.w3.org/MarkUp/html-spec/html-spec_13.html#SEC106">HTML
will replace them by their equivalent <a href="https://www.w3.org/MarkUp/html-spec/html-spec_13.html#SEC106">HTML
code</a>.<br>The following HTML tags are allowed in the &quot;Description&quot;,
&quot;Information&quot; and &quot;Address&quot; fields: <code>&lt;a&gt;</code>,
<code>&lt;br/&gt;</code>, <code>&lt;code&gt;</code>, <code>&lt;em&gt;</code>,
799,9 → 799,9
<a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a>
</div>
<div class="answer">
According to clause 8.2 f of <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation
According to clause 8.2 f of <a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation
ITU-T X.660 | ISO/IEC 9834-1</a>, the registration record for an OID
shall include at least:<br>a) the definition of the object (when the registration authority of
shall include at least:<br>a) the <a href="#guidelines">definition</a> of the object (when the registration authority of
the parent OID performs a technical role, it checks that the objet
can be registered under the parent OID);<br>b) when applicable, the identifier (beginning with a lowercase letter)
assigned to the object (in addition to the unique number);<br>c) the name and contact information of the organization that proposed
841,7 → 841,7
described on this website which is not an official RA, but a <em>repository</em>
of information about existing OIDs.<br>The <em>first Registration Authority</em> of an OID is the very first
person or company to whom the OID was allocated by the RA of the superior
OID. According to <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation
OID. According to <a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation
ITU-T X.660 | ISO/IEC 9834-1</a>,<!-- clause 9.2.f.a --> the first
RA can't be changed (if the responsibility is transfered to someone
else, the information is recorded in the &quot;Current Registration
876,19 → 876,19
<a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a>
</div>
<div class="answer">
- 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&amp;skipcache=yes">OpenSearch
- 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>
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&amp;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://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>
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>
(formerly known as Mozilla Application Suite), the <a href="http://dictionarysearch.mozdev.org">DictionarySearch
at the top-right.<br><!-- - If you're using <a href="https://www.mozilla.org/products/thunderbird/">Mozilla
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>
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>
(formerly known as Mozilla Application Suite), the <a href="https://dictionarysearch.mozdev.org">DictionarySearch
add-on</a> is easy to configure so that you can display information
about an OID by right-clicking on its selection:<br><ul>
<li>install the DictionarySearch extension corresponding to your
tool from <a href="http://dictionarysearch.mozdev.org">http://dictionarysearch.mozdev.org</a>;</li>
tool from <a href="https://dictionarysearch.mozdev.org">https://dictionarysearch.mozdev.org</a>;</li>
<li>in the &quot;Tools&quot; menu of your tool, select the &quot;Extensions&quot;
item;</li>
<li>highlight the line for DictionarySearch, then click on the "Options"
896,9 → 896,9
<li>add a new Dictionary with the following information (this will
display the description of the selected OID in dot notation; it
doesn't work well for a selected OID in ASN.1 notation because
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=$&amp;a=display</code></li>
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=$&amp;a=display</code></li>
<li>This other new &quot;Dictionary&quot; may also be useful (it
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>
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>
</li>
</ul> --> - See also <a href="#8">question 8</a>.<br><br></div>
</li>
956,7 → 956,7
(<em>e.g.</em>, <code>{joint-iso-itu-t(2) tag-based(27)}</code>) where
only ASCII identifiers are allowed. The need was identified for a
human-friendly notation which would not be limited to latin alphabets
and would encompass the diversity of <a href="http://www.unicode.org">Unicode
and would encompass the diversity of <a href="https://www.unicode.org">Unicode
alphabets</a>.<br>An OID-IRI (a.k.a. international OID) is a string of slash-separated
Unicode labels from the root of the OID tree, which unambiguously
identifies a node in the OID tree (e.g., &quot;<a href="/get//Joint-ISO-ITU-T/Example"><code>/Joint-ISO-ITU-T/Example</code></a>&quot;).<br>A Unicode label is a case-sensitive string of Unicode characters (except
974,8 → 974,8
long arc named &quot;<code>Example</code>&quot; allowing OID-IRI &quot;<code><a href="/get//Example">/Example</a></code>&quot;
which is shorter than OID-IRI &quot;<code><a href="/get//Joint-ISO-ITU-T/Example">/Joint-ISO-ITU-T/Example</a></code>&quot;.
Long arcs are only allowed for OIDs under the <code>joint-iso-itu-t(2)</code>
top-level arc (see the <a href="http://itu.int/go/X660">register of
long arcs)</a>.<br>The <a href="http://www.itu.int/rec/T-REC-X.680/en">ASN.1 standard</a>
top-level arc (see the <a href="https://www.itu.int/go/X660">register of
long arcs)</a>.<br>The <a href="https://www.itu.int/rec/T-REC-X.680/en">ASN.1 standard</a>
specifies an <code>OID-IRI</code> type for exchanging OID-IRI values
between machines.<br><br></div>
</li>
986,7 → 986,7
</div>
<div class="answer">
Guidance is given in sections 8.2 (Operation), 9 (registration procedures)
and 11 (recommended fee structure) of <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation
and 11 (recommended fee structure) of <a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation
ITU-T X.660 | ISO/IEC 9834-1</a>.<br>The open-source database system <a href="https://oidplus.viathinksoft.com/oidplus/">OIDplus</a>
from ViaThinkSoft can be used by Registration Authorities to manage
their OIDs. It includes a feature to export data into an <a href="submit.htm">XML
999,7 → 999,7
</div>
<div class="answer">
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
lapo.it</a>, <a href="http://www.bouncycastle.org">Bouncy Castle Crypto
lapo.it</a>, <a href="https://www.bouncycastle.org">Bouncy Castle Crypto
APIs</a>, OpenSSL (version 0.9.8o, 1 Jun 2010) and the built-in Java
class "<code>org.ietf.jgss.Oid</code>" can handle <a href="/get/2.25">UUIDs
used as OIDs</a>.<br>- Windows CryptoAPI Shell Extension (tested with Windows XP and Windows
1011,9 → 1011,9
when an arc contains a higher value (e.g., <code>{2 999 Unknown 0}</code>).
<br>- Mac OS X cannot handle OIDs of the form <code>2.<em>n</em></code>
where <code><em>n</em></code> &gt; 47 (i.e., it wrongly decodes OIDs
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
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
Marschall's study about OID encoding and size limitations</a>. Daniel's
<a href="https://www.viathinksoft.de/%7Edaniel-marschall/asn.1/oid-converter/online.php">DER
<a href="https://misc.daniel-marschall.de/asn.1/oid-converter/online.php">DER
encoder</a> can also help in your testing.<br><br></div>
</li>
<li>
1022,12 → 1022,12
<a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a>
</div>
<div class="answer">
See for example (non-exhaustive list):<strong><br></strong>- OSS Nokalva's online <a href="http://asn1-playground.oss.com/">ASN.1
See for example (non-exhaustive list):<strong><br></strong>- OSS Nokalva's online <a href="https://asn1.io">ASN.1
playground</a> encodes/decodes OIDs in any encoding rule (BER, DER,
PER, UPER, XER) with the following schema:<br><code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OID-Module DEFINITIONS ::= BEGIN<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OID ::= OBJECT IDENTIFIER<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;END</code><br>&nbsp;&nbsp;The OID is provided in ASN.1 notation in the &quot;Data:
Encode&quot; box as follows:<br><code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;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
encoder/decoder</a> (for PHP and C);<br>- <a href="http://bouncycastle.org">The Legion of the Bouncy Castle</a>'s
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
Encode&quot; box as follows:<br><code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;oid OID ::= {2 999}</code><br>- Daniel Marschall's online <a href="https://misc.daniel-marschall.de/asn.1/oid-converter/online.php">DER
encoder/decoder</a> (for PHP and C);<br>- <a href="https://bouncycastle.org">The Legion of the Bouncy Castle</a>'s
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
Marschall's software compatibility analysis for large OIDs</a>.<br><br></div>
</li>
<li>
1043,7 → 1043,7
email address, so that the &quot;submitter&quot; section is automatically
filled the next time they submit information. This cookie is not used
to track your use of the OID repository.<br>The <a href="/helper">OID helper</a> chatbot is (externally) hosted
by <a href="http://pandorabots.com/botmaster/en/~121e02c2b4d4270afe6afac6~/faq">Pandorabots</a>
by <a href="https://pandorabots.com/botmaster/en/~121e02c2b4d4270afe6afac6~/faq">Pandorabots</a>
which normally tracks individual conversations by placing a cookie
on your browser, in order to offer contextual answers to your questions
(please check <a href="https://home.pandorabots.com/policies.html#privacy-policy">Pandorabots'
1084,7 → 1084,7
and can request deletion of such data.<br>In some cases, your personal data appears in the OID repository because
it is publicly available on another web site (e.g., <a href="https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers">IANA
enterprise numbers</a>).<br>To check if personal data related to you appears in the OID repository,
please use the <a href="advanced-search.htm">advanced search</a>. You can
please use the <a href="search.htm">advanced search</a>. You can
also <a href="/cgi-bin/manage?a=get-personal-data">get a copy</a>
of all personal data appearing in the OID repository. In any case,
your personal data is never used for sending any kind of publicity
/trunk/faq.raw.htm
46,7 → 46,7
<li><a href="#size-limitations">Are there size limitations for OID encoding?</a></li>
<li><a href="#31">Are there binary encoders/decoders for OIDs?</a></li>
<li><a href="#cookies">Does this web site use cookies?</a></li>
<li><a href="#33">How does this web site protect users' privacy?</a></li>
<li><a href="#privacy">How does this web site protect users' privacy?</a></li>
<li><a href="#guidelines">What are the guidelines to adequately describe an OID in this OID repository?</a></li>
</ol><br></td>
</tr>
67,13 → 67,13
</div>
<div class="answer">
They are defined in the <a href="standards.htm">Recommendation ITU-T
X.660 | ISO/IEC 9834 series</a>, and in particular in <a href="http://www.itu.int/ITU-T/X.660">Rec.
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.
X.660 | ISO/IEC 9834 series</a>, and in particular in <a href="https://www.itu.int/ITU-T/X.660">Rec.
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.
ITU-T X.690 | ISO/IEC 8825-1</a> for the Binary (BER) and Distinguished
(DER) Encoding rules, in <a href="http://www.itu.int/rec/T-REC-X.691/en">Rec.
(DER) Encoding rules, in <a href="https://www.itu.int/rec/T-REC-X.691/en">Rec.
ITU-T X.691 | ISO/IEC 8825-2</a> for the Packed Encoding rules (PER).
An XML encoding of OIDs is specified in <a href="http://www.itu.int/rec/T-REC-X.693/en">Rec.
ITU-T X.693 | ISO/IEC 8825-3</a>. (See also <a href="http://www.itu.int/rec/T-REC-X.691/en">question
An XML encoding of OIDs is specified in <a href="https://www.itu.int/rec/T-REC-X.693/en">Rec.
ITU-T X.693 | ISO/IEC 8825-3</a>. (See also <a href="https://www.itu.int/rec/T-REC-X.691/en">question
31</a> about binary encoders/decoders for OIDs.)<br><br></div>
</li>
<li>
95,13 → 95,13
project;
</li>
<li>
a certificate policy specified according to <a href="http://itu.int/ITU-T/X.500">Rec.
a certificate policy specified according to <a href="https://itu.int/ITU-T/X.500">Rec.
ITU-T X.500</a>;
</li>
<li>an encryption algorithm (for example <a href="/get/1.3.14.3.2.26">SHA-1</a>);</li>
<li>
<a href="/get/2.27">identification schemes</a> for tag-based
applications (see <a href="http://itu.int/ITU-T/X.668">Recommendation
applications (see <a href="https://itu.int/ITU-T/X.668">Recommendation
ITU-T X.668 | ISO/IEC 9834-9</a>);
</li>
<li>
128,11 → 128,11
<li>
a managed object class, one of its attributes, a notification
or even other templates used in the area of network management
and the GDMO standard (see <a href="http://www.itu.int/rec/T-REC-X.722/en">Recommendation
and the GDMO standard (see <a href="https://www.itu.int/rec/T-REC-X.722/en">Recommendation
ITU-T X.722 | ISO/IEC 10165-4</a>);
</li>
<li>
an information object (see <a href="http://www.itu.int/rec/T-REC-X.681/en">Recommendation
an information object (see <a href="https://www.itu.int/rec/T-REC-X.681/en">Recommendation
ITU-T X.681 | ISO/IEC 8824-2</a>);
</li>
<li>the type of some part of an ITU-T X.400 electronic message body;</li>
139,7 → 139,7
<li>a file format;</li>
<li>etc.</li>
</ul>
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>
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>
</li>
<li>
<div class="question">
151,7 → 151,7
<a href="faq.htm#1">question 1</a>), OIDs are explained in:
<ul>
<li>
the <a href="http://www.itu.int/oth/T0B04000048/en">OID flyer</a>
the <a href="https://www.itu.int/oth/T0B04000048/en">OID flyer</a>
from ITU-T Study Group 17;
</li>
<li>
158,13 → 158,13
the quick <a href="doc/introduction%20to%20object%20identifiers%20(OIDs).pdf">introduction
to OIDs</a>;
</li>
<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>
<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>
<li>
section 10.8 of Olivier Dubuisson's <a href="http://www.oss.com/asn1/dubuisson.html">book
section 10.8 of Olivier Dubuisson's <a href="https://www.oss.com/asn1/dubuisson.html">book
&quot;ASN.1 - Communication between heterogeneous systems&quot;</a>;
</li>
<li>
John Larmouth's <a href="http://www.oss.com/asn1/larmouth.html">book
John Larmouth's <a href="https://www.oss.com/asn1/larmouth.html">book
&quot;ASN.1 complete&quot;</a>;
</li>
<li>
187,7 → 187,7
</div>
<div class="answer">
This OID repository is not an official Registration Authority,
so any OID described in this OID repository has to be officially allocated
so any OID <a href="#guidelines">described</a> in this OID repository has to be officially allocated
by the Registration Authority of its parent OID. There are at least
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
following OID to the database" on the <a href="index.htm">main page</a> and
202,7 → 202,7
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
(a.k.a. sibling OID) and click on the "Create a sibling OID" link
on the top right-hand side of the page; a new page will then be displayed
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
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
to describe them in an XML document that conforms to our <a href="oid.xsd">XML
Schema for OIDs</a> and <a href="submit.htm">submit</a> this document
through the web interface. <br><em>
230,7 → 230,7
<input type="text" name="oid" size="30" value=""><strong>}</strong>
<input type="submit" name="submit" value="Suggest a modification"></form>
<em>
Note: Your proposed modifications will have to be validated by
Note: Your <a href="#guidelines">proposed modifications</a> will have to be validated by
the <a href="#registration-authorities">registrant</a> of the OID
being modified (if known), the <a href="#registration-authorities">registrant</a>
of the parent OID (if known) and the OID repository administrator
254,7 → 254,7
<a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a>
</div>
<div class="answer">
According to <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation
According to <a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation
ITU-T X.660 | ISO 9834-1</a>, an OID shall not be deleted once it
has been allocated by a Registration Authority. However if an OID
that is described in this OID repository has never been officially
282,7 → 282,7
<div class="answer">
We get Harald's agreement to dump his repository and merge the data
into our repository. This was done in June 2003 and our OID repository
now encompasses <a href="http://www.alvestrand.no/objectid/">Harald's
now encompasses <a href="https://www.alvestrand.no/objectid/">Harald's
registry</a>.<br><br></div>
</li>
<li>
294,27 → 294,27
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://datatracker.ietf.org/doc/html/rfc3061">URN
notation</a>) to the <a href="/get/">http://oid-info.com/get/</a>
notation</a>) to the <a href="/get/">https://oid-info.com/get/</a>
URL, <em>e.g.</em>:
<ul>
<li> <a href="/get/2.999">http://oid-info.com/get/2.999</a> (recommended);</li>
<li> <a href="/get/2.999">https://oid-info.com/get/2.999</a> (recommended);</li>
<li>
<a href="/get/%7Bjoint-iso-itu-t%20example(999)%7D">http://oid-info.com/get/{joint
<a href="/get/%7Bjoint-iso-itu-t%20example(999)%7D">https://oid-info.com/get/{joint
iso-itu-t example(999)}</a> (ASN.1 notation);
</li>
<li>
<a href="/get//Joint-ISO-ITU-T/Example">http://oid-info.com/get//Joint-ISO-ITU-T/Example</a>
or <a href="/get//2/999">http://oid-info.com/get//2/999</a> (OID-IRI
<a href="/get//Joint-ISO-ITU-T/Example">https://oid-info.com/get//Joint-ISO-ITU-T/Example</a>
or <a href="/get//2/999">https://oid-info.com/get//2/999</a> (OID-IRI
notation; with a '/' at the beginning of the OID notation, hence
two '/'s after 'get');
</li>
<li>
<a href="/get//Example">http://oid-info.com/get//Example</a>
<a href="/get//Example">https://oid-info.com/get//Example</a>
(OID-IRI notation using a long arc; with a '/' at the beginning
of the OID notation, hence two '/'s after 'get');
</li>
<li>
<a href="/get/urn:oid:2.999">http://oid-info.com/get/urn:oid:2.999</a>
<a href="/get/urn:oid:2.999">https://oid-info.com/get/urn:oid:2.999</a>
(URN notation).<br><br></li>
</ul>
</div>
339,7 → 339,7
<a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a>
</div>
<div class="answer">
The original intention of the <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation
The original intention of the <a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation
ITU-T X.660 | ISO/IEC 9834</a> series was that anyone should be able
to get an OID if they needed one. There are registration authorities
from which it is easy and quite cheap (sometimes even free!) to have
363,7 → 363,7
please see <a href="#11">question 11</a> below.)
</li>
<li>
<a href="http://pen.iana.org/pen/PenApplication.page">IANA</a>
<a href="https://pen.iana.org/pen/PenApplication.page">IANA</a>
(Internet Assigned Numbers Authority) hands out OIDs for free under
<a href="/get/1.3.6.1.4.1"><code>{iso(1) identified-organization(3)
dod(6) internet(1) private(4) enterprise(1)}</code></a>; these OIDs
371,7 → 371,7
Bases (MIBs) for network management (SNMP).
</li>
<li>
<a href="https://www.viathinksoft.com/freeoid">ViaThinkSoft</a>
<a href="https://oidplus.viathinksoft.com/oidplus/?goto=oidplus:com.viathinksoft.freeoid">ViaThinkSoft</a>
freely assigns an OID to private persons and developers of freeware,
shareware or open-source software under <a href="/get/1.3.6.1.4.1.37476.9000"><code>{iso(1)
identified-organization(3) dod(6) internet(1) private(4) enterprise(1)
378,7 → 378,7
37476 freesub(9000)}</code></a>.
</li>
<li>
<a href="http://webapp.etsi.org/ASN1ObjectTree/ASN1.asp">ETSI</a>
<a href="https://webapp.etsi.org/ASN1ObjectTree/ASN1.asp">ETSI</a>
(European Telecommunication Standards Institute) hands out OIDs
under <code><a href="/get/0.4.0.127.0">{itu-t(0) identified-organization(4)
etsi(0) reserved(127) etsi-identified-organization(0)}</a></code>
391,25 → 391,25
administration(2)}</a></code>.
</li>
<li>
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
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
FAQ</a>.
</li>
<li>
Dave Harvey (UK) <a href="http://www.medicalconnections.co.uk/Free_UID">sub-delegate
ranges of his own OID</a> to anyone who uses a <a href="http://medical.nema.org/">DICOM</a>
Dave Harvey (UK) <a href="https://www.medicalconnections.co.uk/Free_UID">sub-delegate
ranges of his own OID</a> to anyone who uses a <a href="https://www.dicomstandard.org">DICOM</a>
toolkit (communication in medicine).
</li>
<li>
You can <a href="http://msdn.microsoft.com/en-us/library/ms677620.aspx">obtain
You can <a href="https://learn.microsoft.com/en-us/windows/win32/ad/obtaining-an-object-identifier-from-microsoft?redirectedfrom=MSDN">obtain
an OID from Microsoft</a> to extend the Active Directory schema.
</li>
<li>
You can <a href="http://www.itu.int/ITU-T/asn1/uuid.html#UUID%20Generation%20&amp;%20Registration">generate
You can <a href="https://www.itu.int/ITU-T/asn1/uuid.html#UUID%20Generation%20&amp;%20Registration">generate
a UUID</a> (or use a UUID that you already hold) and append it as
a subsequent arc of <a href="/get/2.25"><code>{joint-iso-itu-t(2)
uuid(25)}</code></a> (without registering it, in particular in this
OID repository, because it is guaranteed to be globally unique with
a high probability) according to <a href="http://www.itu.int/rec/T-REC-X.667/en">Recommendation
a high probability) according to <a href="https://www.itu.int/rec/T-REC-X.667/en">Recommendation
ITU-T X.667 | ISO/IEC 9834-8</a> (but see <a href="#size-limitations">question
30 about size limitations of OID encodings</a>).
</li>
428,7 → 428,7
Country arcs are the subsequent arcs of <a href="/get/1.2"><code>{iso(1)
member-body(2)}</code></a> and <a href="/get/2.16"><code>{joint-iso-itu-t(2)
country(16)}</code></a>. The values assigned to country arcs are the
<a href="http://unstats.un.org/unsd/methods/m49/m49alpha.htm">numerical
<a href="https://unstats.un.org/unsd/methods/m49/m49alpha.htm">numerical
codes</a> (without leading zeros) assigned by the United Nations Statistics
Division together with the corresponding and the <a href="https://www.iso.org/obp/ui/#search">ISO
3166-1-alpha-2 code</a>. <a href="/get/1.2"><code>{iso(1) member-body(2)}</code></a>
438,13 → 438,13
request an arc under <a href="/get/2.16"><code>{joint-iso-itu-t(2)
country(16)}</code></a>. Countries are discouraged to request an arc
under both <a href="/get/1.2"><code>{iso(1) member-body(2)}</code></a>
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
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
National Body</a> of the country and the <a href="http://www.itu.int/GlobalDirectory/search.html">administration
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
X.660 | ISO/IEC 9834-1</a>, clause A.4.5, specifies that the <a href="https://www.iso.org/members.html">ISO
National Body</a> of the country and the <a href="https://www.itu.int/hub/membership/our-members/">administration
representing the country in the ITU</a> shall agree together (as a
national decision) on the organization that will be the RA for their
country arc. In the case of a country arc under <a href="/get/1.2"><code>{iso(1)
member-body(2)}</code></a> the decision is only taken by the <a href="http://www.iso.org/iso/about/iso_members.htm">ISO
member-body(2)}</code></a> the decision is only taken by the <a href="https://www.iso.org/members.html">ISO
National Body</a> of the country. For more detailed information, see
&quot;<a href="country_oids.htm">Operation of a country Registration
Authority</a>&quot;.<br>One way to know if your country is already operating an RA for OIDs
460,9 → 460,9
Country arcs are the subsequent arcs of <a href="/get/1.2"><code>{iso(1)
member-body(2)}</code></a> and <a href="/get/2.16"><code>{joint-iso-itu-t(2)
country(16)}</code></a>.<br>The structure underneath a country arc is a national decision. The
basic standard is of course <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation
basic standard is of course <a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation
ITU-T X.660 | ISO/IEC 9834-1</a>. It might be worth having a look
at <a href="http://www.itu.int/rec/T-REC-X.670/en">Recommendation
at <a href="https://www.itu.int/rec/T-REC-X.670/en">Recommendation
ITU-T X.670</a> "<em>
Procedures for registration agents operating
on behalf of organizations to register organization names subordinate
471,7 → 471,7
needs to keep records according to the aforementioned standards. A
good idea is probably to look at <a href="country_oids.htm#agreements">how
other countries have organized subsequent arcs beneath their country
arc</a> as well as reading the ITU handbook on &quot;<a href="http://www.itu.int/pub/T-HDB-LNG.4-2010"><em>
arc</a> as well as reading the ITU handbook on &quot;<a href="https://www.itu.int/pub/T-HDB-LNG.4-2010"><em>
Object
identifiers (OIDs) and their registration authorities
</em></a>&quot;. You can also take benefit from the
492,7 → 492,7
<a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a>
</div>
<div class="answer">
(<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
(<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
better to have a notation using spaces and braces, with optional text
labels, so that <code>1.3.6.1</code> would become something like <code>{iso(1)
identified-organization(3) dod(6) internet(1)}</code> or <code>{1
514,7 → 514,7
This enables optimized binary encodings in which all arcs beneath
top-level arcs <code>0</code> and <code>1</code>, and arcs <code>0</code>
to <code>47</code> beneath top-level arc <code>2</code> are encoded
on a single octet (see <a href="http://www.itu.int/rec/T-REC-X.690/en">Rec.
on a single octet (see <a href="https://www.itu.int/rec/T-REC-X.690/en">Rec.
ITU-T X.690 | ISO/IEC 8825-1</a>, clause 8.19). Arcs greater to <code>47</code>
benath top-level arc <code>2</code> are hence encoded on more than
one octet.<br><br></div>
662,7 → 662,7
OID repository by searching for a particular string in all attributes;
</li>
<li>
do an <a href="advanced-search.htm">advanced search</a> of the entire
do an <a href="search.htm">advanced search</a> of the entire
OID repository by searching for a particular value for each description
attribute or even by using regular expressions.
</li>
700,7 → 700,7
characters such as accentuated letters are allowed in most fields
(&quot;Description&quot;, &quot;Information&quot;, registrant &quot;First
name&quot;, &quot;Last name&quot; and &quot;Address&quot;). The software
will replace them by their equivalent <a href="http://www.w3.org/MarkUp/html-spec/html-spec_13.html#SEC106">HTML
will replace them by their equivalent <a href="https://www.w3.org/MarkUp/html-spec/html-spec_13.html#SEC106">HTML
code</a>.<br>The following HTML tags are allowed in the &quot;Description&quot;,
&quot;Information&quot; and &quot;Address&quot; fields: <code>&lt;a&gt;</code>,
<code>&lt;br/&gt;</code>, <code>&lt;code&gt;</code>, <code>&lt;em&gt;</code>,
720,9 → 720,9
<a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a>
</div>
<div class="answer">
According to clause 8.2 f of <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation
According to clause 8.2 f of <a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation
ITU-T X.660 | ISO/IEC 9834-1</a>, the registration record for an OID
shall include at least:<br>a) the definition of the object (when the registration authority of
shall include at least:<br>a) the <a href="#guidelines">definition</a> of the object (when the registration authority of
the parent OID performs a technical role, it checks that the objet
can be registered under the parent OID);<br>b) when applicable, the identifier (beginning with a lowercase letter)
assigned to the object (in addition to the unique number);<br>c) the name and contact information of the organization that proposed
762,7 → 762,7
described on this website which is not an official RA, but a <em>repository</em>
of information about existing OIDs.<br>The <em>first Registration Authority</em> of an OID is the very first
person or company to whom the OID was allocated by the RA of the superior
OID. According to <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation
OID. According to <a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation
ITU-T X.660 | ISO/IEC 9834-1</a>,<!-- clause 9.2.f.a --> the first
RA can't be changed (if the responsibility is transfered to someone
else, the information is recorded in the &quot;Current Registration
797,19 → 797,19
<a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a>
</div>
<div class="answer">
- 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&amp;skipcache=yes">OpenSearch
- 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>
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&amp;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://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>
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>
(formerly known as Mozilla Application Suite), the <a href="http://dictionarysearch.mozdev.org">DictionarySearch
at the top-right.<br><!-- - If you're using <a href="https://www.mozilla.org/products/thunderbird/">Mozilla
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>
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>
(formerly known as Mozilla Application Suite), the <a href="https://dictionarysearch.mozdev.org">DictionarySearch
add-on</a> is easy to configure so that you can display information
about an OID by right-clicking on its selection:<br><ul>
<li>install the DictionarySearch extension corresponding to your
tool from <a href="http://dictionarysearch.mozdev.org">http://dictionarysearch.mozdev.org</a>;</li>
tool from <a href="https://dictionarysearch.mozdev.org">https://dictionarysearch.mozdev.org</a>;</li>
<li>in the &quot;Tools&quot; menu of your tool, select the &quot;Extensions&quot;
item;</li>
<li>highlight the line for DictionarySearch, then click on the "Options"
817,9 → 817,9
<li>add a new Dictionary with the following information (this will
display the description of the selected OID in dot notation; it
doesn't work well for a selected OID in ASN.1 notation because
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=$&amp;a=display</code></li>
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=$&amp;a=display</code></li>
<li>This other new &quot;Dictionary&quot; may also be useful (it
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>
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>
</li>
</ul> --> - See also <a href="#8">question 8</a>.<br><br></div>
</li>
877,7 → 877,7
(<em>e.g.</em>, <code>{joint-iso-itu-t(2) tag-based(27)}</code>) where
only ASCII identifiers are allowed. The need was identified for a
human-friendly notation which would not be limited to latin alphabets
and would encompass the diversity of <a href="http://www.unicode.org">Unicode
and would encompass the diversity of <a href="https://www.unicode.org">Unicode
alphabets</a>.<br>An OID-IRI (a.k.a. international OID) is a string of slash-separated
Unicode labels from the root of the OID tree, which unambiguously
identifies a node in the OID tree (e.g., &quot;<a href="/get//Joint-ISO-ITU-T/Example"><code>/Joint-ISO-ITU-T/Example</code></a>&quot;).<br>A Unicode label is a case-sensitive string of Unicode characters (except
895,8 → 895,8
long arc named &quot;<code>Example</code>&quot; allowing OID-IRI &quot;<code><a href="/get//Example">/Example</a></code>&quot;
which is shorter than OID-IRI &quot;<code><a href="/get//Joint-ISO-ITU-T/Example">/Joint-ISO-ITU-T/Example</a></code>&quot;.
Long arcs are only allowed for OIDs under the <code>joint-iso-itu-t(2)</code>
top-level arc (see the <a href="http://itu.int/go/X660">register of
long arcs)</a>.<br>The <a href="http://www.itu.int/rec/T-REC-X.680/en">ASN.1 standard</a>
top-level arc (see the <a href="https://www.itu.int/go/X660">register of
long arcs)</a>.<br>The <a href="https://www.itu.int/rec/T-REC-X.680/en">ASN.1 standard</a>
specifies an <code>OID-IRI</code> type for exchanging OID-IRI values
between machines.<br><br></div>
</li>
907,7 → 907,7
</div>
<div class="answer">
Guidance is given in sections 8.2 (Operation), 9 (registration procedures)
and 11 (recommended fee structure) of <a href="http://www.itu.int/rec/T-REC-X.660/en">Recommendation
and 11 (recommended fee structure) of <a href="https://www.itu.int/rec/T-REC-X.660/en">Recommendation
ITU-T X.660 | ISO/IEC 9834-1</a>.<br>The open-source database system <a href="https://oidplus.viathinksoft.com/oidplus/">OIDplus</a>
from ViaThinkSoft can be used by Registration Authorities to manage
their OIDs. It includes a feature to export data into an <a href="submit.htm">XML
920,7 → 920,7
</div>
<div class="answer">
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
lapo.it</a>, <a href="http://www.bouncycastle.org">Bouncy Castle Crypto
lapo.it</a>, <a href="https://www.bouncycastle.org">Bouncy Castle Crypto
APIs</a>, OpenSSL (version 0.9.8o, 1 Jun 2010) and the built-in Java
class "<code>org.ietf.jgss.Oid</code>" can handle <a href="/get/2.25">UUIDs
used as OIDs</a>.<br>- Windows CryptoAPI Shell Extension (tested with Windows XP and Windows
932,9 → 932,9
when an arc contains a higher value (e.g., <code>{2 999 Unknown 0}</code>).
<br>- Mac OS X cannot handle OIDs of the form <code>2.<em>n</em></code>
where <code><em>n</em></code> &gt; 47 (i.e., it wrongly decodes OIDs
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
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
Marschall's study about OID encoding and size limitations</a>. Daniel's
<a href="https://www.viathinksoft.de/%7Edaniel-marschall/asn.1/oid-converter/online.php">DER
<a href="https://misc.daniel-marschall.de/asn.1/oid-converter/online.php">DER
encoder</a> can also help in your testing.<br><br></div>
</li>
<li>
943,12 → 943,12
<a href="#top"><img src="images/page_top_fleche.png" width="27" height="17" border="0"></a>
</div>
<div class="answer">
See for example (non-exhaustive list):<strong><br></strong>- OSS Nokalva's online <a href="http://asn1-playground.oss.com/">ASN.1
See for example (non-exhaustive list):<strong><br></strong>- OSS Nokalva's online <a href="https://asn1.io">ASN.1
playground</a> encodes/decodes OIDs in any encoding rule (BER, DER,
PER, UPER, XER) with the following schema:<br><code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OID-Module DEFINITIONS ::= BEGIN<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OID ::= OBJECT IDENTIFIER<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;END</code><br>&nbsp;&nbsp;The OID is provided in ASN.1 notation in the &quot;Data:
Encode&quot; box as follows:<br><code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;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
encoder/decoder</a> (for PHP and C);<br>- <a href="http://bouncycastle.org">The Legion of the Bouncy Castle</a>'s
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
Encode&quot; box as follows:<br><code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;oid OID ::= {2 999}</code><br>- Daniel Marschall's online <a href="https://misc.daniel-marschall.de/asn.1/oid-converter/online.php">DER
encoder/decoder</a> (for PHP and C);<br>- <a href="https://bouncycastle.org">The Legion of the Bouncy Castle</a>'s
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
Marschall's software compatibility analysis for large OIDs</a>.<br><br></div>
</li>
<li>
964,7 → 964,7
email address, so that the &quot;submitter&quot; section is automatically
filled the next time they submit information. This cookie is not used
to track your use of the OID repository.<br>The <a href="/helper">OID helper</a> chatbot is (externally) hosted
by <a href="http://pandorabots.com/botmaster/en/~121e02c2b4d4270afe6afac6~/faq">Pandorabots</a>
by <a href="https://pandorabots.com/botmaster/en/~121e02c2b4d4270afe6afac6~/faq">Pandorabots</a>
which normally tracks individual conversations by placing a cookie
on your browser, in order to offer contextual answers to your questions
(please check <a href="https://home.pandorabots.com/policies.html#privacy-policy">Pandorabots'
1005,7 → 1005,7
and can request deletion of such data.<br>In some cases, your personal data appears in the OID repository because
it is publicly available on another web site (e.g., <a href="https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers">IANA
enterprise numbers</a>).<br>To check if personal data related to you appears in the OID repository,
please use the <a href="advanced-search.htm">advanced search</a>. You can
please use the <a href="search.htm">advanced search</a>. You can
also <a href="/cgi-bin/manage?a=get-personal-data">get a copy</a>
of all personal data appearing in the OID repository. In any case,
your personal data is never used for sending any kind of publicity