OID repository
OID Repository
Display OID:
Operation of a country Registration Authority
General Check-list of actions to be taken Suggested template for notifying an RA for a country Known country RAs 
  bulletOID handbook
separation line
Frequently Asked Questions (FAQ)

It is strongly recommended today that any country wishing to establish a Registration Authority (RA) for allocations within that country reach agreement between the administration of an ITU Member State for the country/state and the ISO Member Body for the country/state (if any) for a given organization to do the allocations within that country using the arc {joint-iso-itu-t(2) country(16)}.  The organization may be an agency of the administration of the ITU Member State or part of the ISO Member Body, or may be an independent organization operating for both of them – in all three cases by mutual agreement (see the check-list of actions to be taken).

It can happen that a country is already operating an RA under one or more of the arcs {itu-t(0) administration(2)}, {iso(1) member-body(2)} or {joint-iso-itu-t(2) country(16)} (see the known country RAs and the correspondence table between country codes and OIDs). It is however recommended that preference be given to using arc {joint-iso-itu-t(2) country(16)}. The value assigned to a country OID is the numerical code of the UN Statistics Division (without leading zeros) together with the corresponding ISO 3166-1 alpha-2 code.

The structure to allocate child OIDs underneath a country OID is a national decision but question 12 in the FAQ may be of help.

separation line
  Check-list of actions to be taken

If a Registration Authority (RA) is to be established for a country, either at the initiative of the administration of the ITU Member State or of the ISO Member Body, the following steps need to be followed (as an application of Recommendation ITU-T X.660 | ISO/IEC 9834-1, clauses A.4.6 and A.5.5):

  1. Identify the organization(s) for the administration of the ITU Member State and the ISO Member Body (if any), and agree a contact point between them.
    Note: In the exceptional case that a country/state has only an administration of the ITU Member State or only an ISO Member Body, then that organization can and will operate alone, but the letter referred to below should still be sent.
  2. Determine to set up an RA for the country under arc {joint-iso-itu-t(2) country(16)} (preferably; otherwise under arc {iso(1) member-body(2)}), and agree and appoint the organization that will administer it (see "What are the duties of an RA?").
    Note: It is the responsibility of the administration of the ITU Member State and of the ISO Member Body to (regularly) check that the designated RA abides by the requirements of Rec. ITU-T X.660 | ISO/IEC 9834-1 and in particular that fees (if any) are charged on a cost-recovery basis (clause 11).
  3. Agree and (if appropriate) document the criteria that will be used for the first level of allocations within the country and any charging regime that is to operate (see "Are there guidelines or standards regarding subsequent arcs of a country arc?").
  4. Consider whether the top-level of allocations within the country are to be made public (e.g. placed in this OID repository) or not.
    Note: There is no requirement for the allocations to be public, but backed-up records should be kept, and it is recommended that preference be given to making public at least the top-level of allocations within the country .
  5. Establish how organizations within the country will become aware of the criteria for getting sub-allocations (see "Which information is necessary to apply for an OID?"), and how they are to contact the RA for the country.
  6. Consider whether it might be appropriate to develop a dedicated application or web-site to assist those organizations wishing to obtain allocations under the country RA.
  7. Produce a letter (preferably in English, otherwise in one of the 5 other official languages of the United Nations, using the suggested template), signed by official representatives (perhaps with a seal/stamp) of the administration of the ITU Member State and the ISO Member Body.
    Note: In the case of a country arc under {iso(1) member-body(2)} the decision is only taken by the ISO National Body of the country.
  8. Forward this letter to either or both of ITU-T SG17 and ISO/IEC JTC 1/SC 6.
    Note: In practice, this letter is forwarded to the ITU-T SG17 OID Project leader (who also happens to be the webmaster of this web site), and the Project leader will arrange for further progression.
  9. The country RA can then begin operation.
  10. The letter will in due course be recorded in the report of the relevant ITU-T SG17 plenary meeting, and in a Resolution of the relevant ISO/IEC JTC 1/SC 6 meeting. A copy will also be made available in this OID repository.

OID helper Would you have any question, please ask it to OID helper.

separation line
  Suggested template for notifying an RA for a country
Examples of agreements

This is the template usually used by the administration of the ITU Member State and the ISO Member Body to appoint the organization which will operate the RA for a country. This letter shall be sent (in English) to either or both of ITU-T SG17 and ISO/IEC JTC 1/SC 6. In practice, this letter can be forwarded to the ITU-T SG17 OID Project leader who will arrange for further progression.

The signatories below, representing
                     [give the name of the administration representing the ITU Member State]
and representing
                     [give the name of the organization representing the ISO Member Body, if any]
for the country
                     [give the name of your country]
have jointly agreed that
                     [give the name and postal address of the organization that will be
                      the RA for the country as well as the name, email address and
                      phone number of a contact person for the registration of OIDs
                      within that organization
will operate the Registration Authority for object identifiers (OIDs) under the country arc
                     {joint-iso-itu-t(2) country(16) xx(nn)}
                     [replace xx and nn in accordance with ISO 3166-1 and the
                      correspondence table between country codes and OIDs
in accordance with the provisions of Recommendation ITU-T X.660 | ISO/IEC 9834-1.

The signatories endeavour to regularly check that the Registration Authority abide by the requirements of Recommendation ITU-T X.660 | ISO/IEC 9834-1, and in particular that, if fees are charged, this is done on a cost-recovery basis.

It is agreed that this information will be recorded by ITU-T and ISO/IEC, and can be made publicly available, e.g. in the OID repository.

It is further agreed that if this information is changed, ITU-T SG17 and ISO/IEC JTC 1/SC 6 will be informed.

Signed:  <add signatures and official stamps as necessary>

separation line
  Known country RAs
Agreement template

The following countries are known to operate a Registration Authority. Some of them began to operate the RA many years ago and there is no record of a signed agreement.

Country name OID Agreement
Algeria {joint-iso-itu-t(2) country(16) dz(12)} Agreement (Sep 2014)
Andorra {joint-iso-itu-t(2) country(16) ad(20)} Agreement (Jan 2014)
Argentina {joint-iso-itu-t(2) country(16) ar(32)} (May 2006)
Australia {iso(1) member-body(2) au(36)} N/A
Austria {iso(1) member-body(2) at(40)} (1993)
Bahrain {joint-iso-itu-t(2) country(16) bh(48))

(Apr 2021)

Bangladesh (the People's Republic of) {joint-iso-itu-t(2) country(16) bd(50))

(June 2012)

Benin {joint-iso-itu-t(2) country(16) bj(204)} Agreement (Apr 2019)
Bolivia (Plurinational State of) {joint-iso-itu-t(2) country(16) bo(68)) Agreement
(Apr 2015)
Brazil {joint-iso-itu-t(2) country(16) br(76)} N/A
Bulgaria {joint-iso-itu-t(2) country(16) bg(100)} Agreement (Nov 2012)
Canada {joint-iso-itu-t(2) country(16) ca(124)}

Agreement * (Apr 2012)

Cape Verde {joint-iso-itu-t(2) country(16) cv(132)} Agreement (Nov 2008)
China (People's Republic of) {iso(1) member-body(2) cn(156)} Agreement (Apr 2006)
{joint-iso-itu-t(2) country(16) cn(156)}
Côte d'Ivoire {joint-iso-itu-t(2) country(16) ci(384)} Agreement (Mar 2020)
Czech Republic {iso(1) member-body(2) cz(203)} N/A
Denmark {iso(1) member-body(2) dk(208)} N/A
Ecuador {joint-iso-itu-t(2) country(16) ec(218)} Agreement (Apr 2021)
Finland {iso(1) member-body(2) fi(246)} N/A
France {iso(1) member-body(2) fr(250)} N/A
Germany {iso(1) member-body(2) de(276)} N/A
{joint-iso-itu-t(2) country(16) de(276)}
Greece {iso(1) member-body(2) gr(300)} (Oct 2006)
Honduras {joint-iso-itu-t(2) country(16) hn(340)} Agreement (Nov 2018)
Hong Kong Special Administrative Region of China {iso(1) member-body(2) hk(344)} N/A
{joint-iso-itu-t(2) country(16) hk(344)}
Hungary {itu-t(0) administration(2) 216} (May 2006)
Iceland {joint-iso-itu-t(2) country(16) is(352)} Agreement (Feb 2007)
Iran (Islamic Republic of) {joint-iso-itu-t(2) country(16) ir(364)} Agreement (Feb 2009)
Ireland {iso(1) member-body(2) ie(372)} N/A
Italy {joint-iso-itu-t(2) country(16) it(380)} N/A
Jamaica {joint-iso-itu-t(2) country(16) jm(388)} Agreement (Apr 2021)
Japan {iso(1) member-body(2) jp(392)} N/A
{itu-t(0) administration(2) japan(440)} N/A
Kazakhstan {iso(1) member-body(2) kz(398)} Agreement (Nov 2008)
Kenya {joint-iso-itu-t(2) country(16) ke(404)} Agreement (Jul 2022)
Korea (Republic of) {iso(1) member-body(2) kr(410)} N/A
{joint-iso-itu-t(2) country(16) kr(410)} Agreement (Jan 2022)
Lao People's Democratic Republic {joint-iso-itu-t(2) country(16) la(418)} Agreement (Oct 2019)
Liechtenstein {joint-iso-itu-t(2) country(16) li(438)} Agreement (Mar 2011)
Malta {joint-iso-itu-t(2) country(16) mt(470)} (Oct 2006)
Moldova (Republic of) {iso(1) member-body(2) md(498)} Agreement (Oct 2011)
Monaco {joint-iso-itu-t(2) country(16) mc(492)} Agreement (Nov 2019)
Mongolia {joint-iso-itu-t(2) country(16) mn(496)} Agreement (Jul 2014)
Netherlands {iso(1) member-body(2) nl(528)} N/A
{joint-iso-itu-t(2) country(16) nl(528)}
New Zealand {joint-iso-itu-t(2) country(16) nz(554)} N/A
Nicaragua {joint-iso-itu-t(2) country(16) ni(558)} Agreement (Aug 2015)
Nigeria {iso(1) member-body(2) ng(566)} Agreement (July 2013)
Norway {joint-iso-itu-t(2) country(16) no(578)} N/A
Oman {joint-iso-itu-t(2) country(16) om(512)} Agreement (July 2012)
Panama (Republic of) {joint-iso-itu-t(2) country(16) pa(591)} Agreement (Apr 2008)
Philippines {joint-iso-itu-t(2) country(16) ph(608)} Agreement (Feb 2014)
Poland {iso(1) member-body(2) pl(616)} N/A
Qatar {joint-iso-itu-t(2) country(16) qa(634)} Agreement (Apr 2008)
Russian Federation {iso(1) member-body(2) ru(643)} Agreement (Nov 2014)
Rwanda {joint-iso-itu-t(2) country(16) rw(646)} Agreement (Jan 2014)
Saudi Arabia {joint-iso-itu-t(2) country(16) sa(682)} (Dec 2007)
Singapore {iso(1) member-body(2) sg(702)} (Mar 2001)
Spain {joint-iso-itu-t(2) country(16) es(724)} N/A
Sri Lanka {joint-iso-itu-t(2) country(16) lk(144)} Agreement (Dec 2015)
Sweden {iso(1) member-body(2) se(752)} N/A
Switzerland {joint-iso-itu-t(2) country(16) ch(756)} N/A
Taiwan, Province of China {joint-iso-itu-t(2) country(16) tw(158)} (1998)
Thailand {joint-iso-itu-t(2) country(16) th(764)} Agreement (Apr 2013)
Tunisia {joint-iso-itu-t(2) country(16) tn(788)} Agreement (Apr 2010)
Turkey {joint-iso-itu-t(2) country(16) tr(792)} N/A
Ukraine {iso(1) member-body(2) ua(804)} Agreement (Mar 2011)
{joint-iso-itu-t(2) country(16) ua(804)} Agreement (Nov 2010)
United Arab Emirates {joint-iso-itu-t(2) country(16) ae(784)} Agreement (Aug 2017)
United Kingdom {iso(1) member-body(2) gb(826)} N/A
United States of America {iso(1) member-body(2) us(840)} N/A
{joint-iso-itu-t(2) country(16) us(840)} N/A
Uruguay {joint-iso-itu-t(2) country(16) uy(858)} Agreement (Nov 2005)
Viet Nam {joint-iso-itu-t(2) country(16) vn(704)} Agreement (Nov 2020)

Disclaimer: OID-info.com is an information site on OIDs and is not intended to provide any specific legal advice to individuals or entities, and should not be relied upon or used for any such purposes. Information on this web site is believed to be complete and up-to-date. We reserve the right to modify the information on this web site at any time without notice.

OID helper Webmaster