ISO/IEC 29168-2:2025
(Main)Information technology — Open systems interconnection — Part 2: Procedures for the object identifier resolution system operational agency
Information technology — Open systems interconnection — Part 2: Procedures for the object identifier resolution system operational agency
This document specifies the mechanisms and criteria to be applied for the selection and approval of the object identifier resolution system (ORS) operational agency and includes procedures that the operational agency is required to follow. It also addresses any future modification of the procedures and the procedures for any change of the operational agency. This document: — lists the object identifier (OID) nodes for which the operational agency is required to provide ORS support and gives the required level of support for these nodes; — gives the procedures by which lower-level nodes can apply for ORS support (class A, class B, or class C) and the role of the operational agency in providing these levels of support; — determines the basis for charges that can be levied for these levels of support.
Technologies de l'information — Interconnection de systèmes ouverts (OSI) — Partie 2: Procédures pour l'agence opérationnelle du système de résolution de l'identificateur d'objet
General Information
Relations
Standards Content (Sample)
International
Standard
ISO/IEC 29168-2
Second edition
Information technology — Open
2025-09
systems interconnection —
Part 2:
Procedures for the object identifier
resolution system operational agency
Technologies de l'information — Interconnection de systèmes
ouverts (OSI) —
Partie 2: Procédures pour l'agence opérationnelle du système de
résolution de l'identificateur d'objet
Reference number
© ISO/IEC 2025
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
© ISO/IEC 2025 – All rights reserved
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 3
5 Appointment of the operational agency . 3
5.1 Formal appointment .3
5.2 Nominating bodies .3
5.3 Criteria for nominations and statements from nominees .4
5.4 Selection and approval of an operational agency .4
5.5 Term of appointment .5
5.6 Transfer of .oid-res.org .5
6 OID nodes to be supported by the operational agency . 5
7 Operational agency support . 6
7.1 General .6
7.2 Support for the OID nodes supported by the operational agency .6
7.3 ORS-support for lower-level nodes .7
7.4 Procedures for requesting support for lower-level nodes .7
7.5 Up-to-date OID root zone file access .8
8 Charging issues . . 8
© ISO/IEC 2025 – All rights reserved
iii
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical activity.
ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations,
governmental and non-governmental, in liaison with ISO and IEC, also take part in the work.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of document should be noted. This document was drafted in accordance with the editorial rules of the ISO/
IEC Directives, Part 2 (see www.iso.org/directives or www.iec.ch/members_experts/refdocs).
ISO and IEC draw attention to the possibility that the implementation of this document may involve the
use of (a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any
claimed patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had not
received notice of (a) patent(s) which may be required to implement this document. However, implementers
are cautioned that this may not represent the latest information, which may be obtained from the patent
database available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held
responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www.iso.org/iso/foreword.html.
In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 6, Telecommunications and information exchange between systems.
This second edition cancels and replaces the first edition (ISO/IEC 29168-2:2011), which has been technically
revised.
The main changes are as follows:
— a secondary operational agency has been introduced as a complement to the primary operational agency,
along with rules for its appointment;
— requirements for the nominees for the primary operational agency have been added;
— requirements for accessing an up-to-date OID root zone file have been added.
A list of all parts in the ISO/IEC 29168 series can be found on the ISO and IEC websites.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/national-committees.
© ISO/IEC 2025 – All rights reserved
iv
Introduction
An introduction to the object identifier (OID) resolution system is provided in ISO/IEC 29168-1.
This document specifies the mechanisms and criteria to be applied for the selection and approval of the
object identifier resolution system (ORS) operational agency. It also covers the procedures that the ORS
operational agency is required to follow when managing the ORS.
The domain name system (DNS) zone files for .oid-res.org must provide ORS support for the root of the
International Object Identifier tree.
These procedures include the appointment (or re-appointment) of the ORS operational agency (the
operational agency).
The procedures require the operational agency to provide DNS zone file support for .oid-res.org, as well as
for a specified set (see Clause 6) of top-level OID nodes, including domain name system security extension
(DNSSEC) (NSEC3) support for those zone files.
The operational agency is also required to support specified procedures (some, but not all, on a commercial
basis) that enable the provision of ORS support for OID nodes beneath those that it is fully required to
support (see Table 1).
Clause 5 specifies the approval mechanisms for the appointment of the operational agency and any necessary
subsequent changes.
Clause 6 specifies the OID nodes to be supported by the operational agency.
Clause 7 specifies the nature of operational agency support.
Clause 8 addresses charging issues for services provided by the operational agency.
© ISO/IEC 2025 – All rights reserved
v
International Standard ISO/IEC 29168-2:2025(en)
Information technology — Open systems interconnection —
Part 2:
Procedures for the object identifier resolution system
operational agency
1 Scope
This document specifies the mechanisms and criteria to be applied for the selection and approval of the
object identifier resolution system (ORS) operational agency and includes procedures that the operational
agency is required to follow. It also addresses any future modification of the procedures and the procedures
for any change of the operational agency.
This document:
— lists the object identifier (OID) nodes for which the operational agency is required to provide ORS support
and gives the required level of support for these nodes;
— gives the procedures by which lower-level nodes can apply for ORS support (class A, class B, or class C)
and the role of the operational agency in providing these levels of support;
— determines the basis for charges that can be levied for these levels of support.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 9834-1, Information technology — Procedures for the operation of object identifier registration
authorities — Part 1: General procedures and top arcs of the international object identifier tree
ISO/IEC 9834-3, Information technology — Open Systems Interconnection — Procedures for the operation of
OSI Registration Authorities — Part 3: Registration of Object Identifier arcs beneath the top-level arc jointly
administered by ISO and ITU-T
ISO/IEC 29168-1:2023, Information technology — Open systems interconnection — Part 1: Object identifier
resolution system
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
© ISO/IEC 2025 – All rights reserved
3.1
object identifier
OID
ordered list of primary integer values from the root of the international object identifier tree (3.2) to a node,
which unambiguously identifies that node
3.2
international object identifier tree
tree whose root corresponds to this document and whose nodes correspond to registration authorities
responsible for allocating arcs from a parent node
3.3
long arc
unicode label (3.5) from a superior node in the international object identifier tree (3.2) that identifies a node
that is not immediately beneath the superior node
3.4
object identifier internationalized resource identifier
OID-IRI
ordered list of unicode labels (3.5) from the root of the international object identifier tree (3.2) that
unambiguously identifies a node in that tree
3.5
unicode label
primary value that consists of an unbounded sequence of unicode characters that does not contain the
SPACE character used to unambiguously identify an arc of the object identifier tree
3.6
domain name system delegation name
DNAME
domain name system resource record used to create an alias for a domain name and all of its sub-domains
3.7
domain name system name server
DNS NS
domain name system resource record providing the authoritative name server for a domain
3.8
domain name system zone file
text file that describes a portion of the domain name system
3.9
naming authority pointer resource record
domain name system resource record, which specifies a regular-expression-based rewrite rule that, when
applied to an existing string, will produce a new domain label or Uniform Resource Identifier
3.10
operational agency procedure
specification of the actions required by the .oid-res.org operational agency
3.11
object identifier resolution system operational agency
organization that manages the domain name system server for the object identifier resolution system root
and some subordinate nodes
3.12
object identifier resolution system-supported object identifier node
object identifier (OID) node for which the
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.