ISO/IEC 29168-1:2011 情報技術—オープンシステム相互接続—パート1：オブジェクト識別子解決システム | ページ 6

3.2.1

application-specific OID resolution process

Actions by an application to retrieve application-specific information from the information returned by the general OID resolution process.

3.2.2

canonical form (of an OID-IRI)

A form which uses only integer-valued Unicode labels.

Note 1 to entry: OID-IRI is an ASN.1 type defined in Rec. ITU-T X.680 | ISO/IEC 8824-1. The term OID-IRI value refers to the ASN.1 value notation that is the same as the IANA"oid:" IRI/URI scheme, with the omission of the initial"oid:".

3.2.3

DNS delegation name (DNAME)

A DNS resource record used to create an alias for a domain name and all of its sub-domains.

3.2.4

DNS-mapped name

The result of transforming an OID-IRI value to an FQDN (see 7.3).

Note 1 to entry: The DNS-mapped name may or may not exist in the DNS. If it does not, then an ORS query will result in an error message (see 7.4), and the node identified by the OID-IRI is not ORS-supported.

3.2.5

DNS name server (NS)

A DNS resource record providing the authoritative name server for a domain.

3.2.6

DNS resource record

A component of a DNS zone file.

3.2.7

DNS zone file

A text file that describes a portion of the DNS.

Note 1 to entry: The format of a DNS zone file is defined in IETF RFC 1035, section 5 and IETF RFC 1034, section 3.6.1.

3.2.8

fully qualified domain name

The name used in a DNS look-up operation (see IETF RFC 1594).

3.2.9

general OID resolution process

That part of the ORS where an ORS client obtains information from the DNS (recorded in a zone file) about any specified OID and returns it to an application.

3.2.10

operational agency procedures

The specification of the actions required by the .oid-res.org operational agency.

3.2.11

NAPTR resource record

A DNS resource record used to store rules which can be retrieved by a DNS lookup for use by an application.

3.2.12

OID resolution process

Process which provides information associated with an OID.

Note 1 to entry: This information can be application-specific (see Figure 1 and the annexes).

3.2.13

OID resolution system

Implementation of the OID resolution process in accordance with this Recommendation | International Standard.

3.2.14

.oid-res.org operational agency

Organization that manages the DNS server for .oid-res.org and some subordinate nodes.

3.2.15

ORS client

Entity that interfaces between an application and a DNS client.

3.2.16

ORS service type

A character string (used in NAPTR resource records) that identifies an ORS service (see Annex A).

3.2.17

ORS-supported OID node

An OID node for which the DNS-mapped names for all of the OID-IRI values that identify the OID node exist in the DNS, and have all necessary DNS zone files configured as specified in this Recommendation | International Standard, including mandatory requirements for all ORS services (see Annex A).

Note 1 to entry: The canonical OID service specified in Annex B requires the presence of a NAPTR record in the associated DNS zone file.

Note 2 to entry: The .oid-res.org operational agency is required by the operational procedures to provide ORS-support for all the OID nodes listed in those procedures. ORS support for nodes beneath these depends on agreements between that OID node and its parent.