GB/T 17969.1-2015 PDF in English
GB/T 17969.1-2015 (GB/T17969.1-2015, GBT 17969.1-2015, GBT17969.1-2015)
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Name of Chinese Standard | Status |
| GB/T 17969.1-2015 | English | 395 |
Add to Cart
|
0-9 seconds. Auto-delivery.
|
Information technology -- Open systems interconnection -- Procedures for the operation of OSI registration authorities -- Part 1: General procedures and top arcs of the International Object Identifier tree
| Valid |
| GB/T 17969.1-2000 | English | 719 |
Add to Cart
|
3 days
|
Information technology. Open Systems interconnection. Procedures for the operation of OSI Registration Authorities. Part 1: General procedures
| Obsolete |
Standards related to (historical): GB/T 17969.1-2015
PDF Preview
GB/T 17969.1-2015: PDF in English (GBT 17969.1-2015) GB/T 17969.1-2015
GB
NATIONAL STANDARD OF THE
PEOPLE'S REPUBLIC OF CHINA
ICS 35.100.01
L 79
Replacing GB/T 17969.1-2000
Information technology - Open systems interconnection -
Procedures for the operation of OSI registration authorities
- Part 1: General procedures and top arcs of the
International Object Identifier tree
(ISO/IEC 9834-1:2008, Information technology - Open systems interconnection -
Procedures for the operation of OSI Registration Authorities: General procedures and
top arcs of the International Object Identifier tree, NEQ)
ISSUED ON: DECEMBER 10, 2015
IMPLEMENTED ON: AUGUST 1, 2016
Issued by: General Administration of Quality Supervision, Inspection and
Quarantine of PRC;
Standardization Administration of PRC.
Table of Contents
Foreword ... 3
1 Scope ... 5
2 Normative references ... 5
3 Terms and definitions ... 6
4 Abbreviations ... 11
5 Registration ... 12
6 Registration-hierarchical-name ... 13
7 Registration procedures for specific types of objects ... 18
Appendix A (Normative) Top-level arcs of the OID tree ... 21
Appendix B (Normative) Derivation of directory names ... 32
Appendix C (Normative) Directory names based on object identifiers ... 35
Appendix D (Informative) National Registration Center for OID ... 37
References ... 38
Information technology - Open systems interconnection -
Procedures for the operation of OSI registration authorities
- Part 1: General procedures and top arcs of the
International Object Identifier tree
1 Scope
This part of GB/T 17969 specifies the concept of registration, and also specifies the
registration-hierarchical-name-tree, the content of the registration procedures for
specific types of objects, the top arc of the International Object Identifier tree, the
derivation of directory names and directory names based on object identifiers.
This standard applies to the registration, development and maintenance of object
identifiers.
2 Normative references
The following documents are essential for the application of this document. For any
referenced document with a date, only the version with the date applies to this document.
For any referenced document without a date, the latest version (including all
amendments) applies to this document.
GB/T 9387.3 Information technology - Open systems interconnection - Basic
reference model - Part 3: Naming and addressing (GB/T 9387.3-2008, ISO/IEC
7498-3:1997, IDT)
GB 13000 Information technology - Universal multiple-octet coded character set
(UCS) (GB 13000-2010, ISO/IEC 10646:2003, IDT)
GB/T 16264.1 Information technology - Open systems interconnection - The
directory - Part 1: Overview of concepts, models and services (GB/T 16264.1-2008,
ISO/IEC 9594-1:2005, IDT)
GB/T 16264.2 Information technology - Open systems interconnection - The
directory - Part 2: Models (GB/T 16264.2-2008, ISO/IEC 9594-2:2005, IDT)
ISO 3166-1 Codes for the representation of names of countries and their
subdivisions - Part 1: Country codes
Secondary identifiers for top-level arcs of the International Object Identifier tree, which
are assigned by decision of the relevant ITU-T study group and the relevant ISO/IEC
JTC subcommittee (see A.6.4).
3.6.2 additional Unicode label
The Unicode labels for the top-level arcs of the International Object Identifier tree,
which are assigned by decision of the relevant ITU-T study group and the relevant
ISO/IEC JTC subcommittee (see A.6.4).
3.6.3 administrative role (of a Registration Authority)
The role assigning unambiguous names and making them valid according to procedures
defined by a Registration Authority.
3.6.4 integer-valued Unicode label
The Unicode label for an arc, which is the character representation of the primary
integer value of the arc (without a leading 0).
NOTE: Arcs of the International Object Identifier tree must not have Unicode labels represented by other
integer-valued characters (with or without a leading 0) (see 6.2.4).
3.6.5 International Object Identifier tree
A specific form of RH name tree whose root corresponds to this part and whose nodes
correspond to the registration authorities responsible for allocating arcs from superior
nodes.
3.6.6 Joint ITU-T | ISO/IEC JTC 1 Collaborative Team for object identifiers
A group established in accordance with relevant ITU-T recommendations and ISO/IEC
JTC 1 guidelines to promote the joint standardization work related to object identifiers
(OIDs).
3.6.7 long arc
A Unicode label from a superior node in the International Object Identifier tree that
identifies a node that is not immediately beneath the superior node.
NOTE 1: Long arcs (other than normal arcs) are subject to the unambiguity requirement for all arcs from
the superior node (see 6.2.8).
NOTE 2: The only content of a long arc is its Unicode label. A long arc has no primary integer value or
secondary identifier. A long arc is essentially a shortcut for a series of arcs, each of which has a primary
integer value and its own Unicode label.
NOTE 3: A long arc cannot be used to define the value of an (ASN.1) object identifier type. It can only
be used in OID internationalized resource identifiers.
3.6.8 object (of interest)
Anything in the world, usually the world of communications and information
processing, that has the following properties:
a) identifiable (capable of being named);
b) registrable.
NOTE: Examples of objects are ASN.1 modules (see ISO/IEC 8824-1), information objects (see
ISO/IEC 8824-2), XML namespaces (see W3C XML Namespaces), and any other object that can be
identified by an OID, URI or IRI.
3.6.9 object identifier
An ordered sequence from the root of the International Object Identifier tree to the
primary integer value of a node, which unambiguously identifies the node (see 6.2.8).
3.6.10 OID internationalized resource identifier
An IRI/URI value constrained to the "oid" IRI/URI scheme.
NOTE 1: Semantically, this is an ordered sequence of Unicode labels starting from the root of the
International Object Identifier tree that unambiguously identifies nodes for a resource (see 6.2.8).
NOTE 2: The ASN.1 OID-IRI type (see ISO/IEC 8824-1) is the set of all OID internationalized resource
identifier values and provides value notations for all OID international resource identifiers based on the
International Object Identifier tree. The corresponding encoding is specified in ISO/IEC 8825.
3.6.11 primary integer value
A primary value of integer type used to unambiguously identify an arc of the
International Object Identifier tree.
NOTE: An arc of the International Object Identifier tree has exactly one primary integer value, except
for long arcs (which have only Unicode labels).
3.6.12 primary value
A value of a particular type assigned to an RH name tree arc, which unambiguously
identifies that arc in the set of arcs that begin at its superior node.
3.6.13 properties of an arc
Assigned primary integer value, Unicode label, and secondary identifier to an arc.
5.2.2 The Registration Authority responsible for a given naming domain shall assign
names to that portion of the naming domain administered by subordinate authorities.
The names assigned shall be globally unambiguous and shall be concatenated as
prefixes to the names assigned by the subordinate authority. This process, applied
repeatedly by various levels of Registration Agents, ensures the generation of
unambiguous names. The generation of registered names is further specified in Chapter
6.
NOTE: An organization, a recommended standard or an automated facility can be a registration authority
for more than one naming domain partition.
5.3 Operation
5.3.1 Registration Authorities may be concerned with the allocation of unambiguous
names (administrative role) and may also be concerned with the definition of registered
objects to verify that these definitions are consistent with the standards that define them
(technical role).
5.3.2 The criteria for registering objects may vary between registration authorities. Each
authority is responsible for establishing these criteria. A Registration Authority may
also define criteria for use by any of its subordinate authorities.
NOTE: The criteria considered in registering an object are the level at which the registration is
appropriate. For example, the definition of an object registered by a particular Registration Authority
may find wider use beyond the scope of that Registration Authority. Although the assigned name is
globally unambiguous and usable outside that Registration Authority, it may be desirable to redefine it
in a manner that is acceptable to a wider range of people. If so, the redefinition shall be registered with a
Registration Authority that is appropriate to the wider scope.
5.3.3 Synonyms are created when an instance of an object type is registered more than
once. There are many valid reasons for creating synonyms, such as directory aliases.
Detecting the existence of synonyms is difficult. Where synonyms are not needed, their
number can be minimized through technical review or administrative (in the case of the
registration authority) measures. A decision shall be made in each case as to whether
this is necessary and practical.
NOTE: There is no practical way to ensure that the same object is not registered by more than one
Registration Authority and this part does not ensure that an object is assigned only a single name.
6 Registration-hierarchical-name
6.1 Generic RH name tree
6.1.1 The RH name tree is a general concept applicable to any form of hierarchical
names, where a name is a concatenation of arc values from the root of the tree to the
leaf. RH name trees differ in the values assigned to the arcs (typically alphanumeric,
numeric, or attribute type value pairs). All directory names, MHS names, ASN.1 object
identifiers, and OID internationalized resource identifiers are hierarchical names of a
specific form of RH name tree.
6.1.2 The root of all currently defined RH name trees (OID trees, and trees supporting
directory names and MHS names) corresponds to this part, and its leaf and non-leaf
nodes correspond to registered objects. Non-leaf nodes correspond to registration
authorities, and registration responsibilities are delegated by superior nodes.
6.1.3 Arcs from a given node to its immediate subordinate nodes are unambiguously
defined within the scope of that node by one of one or more primary values of different
types. These primary values are assigned by the Registration Authority of its superior
nodes, so that a path from the root to a node provides an unambiguous name for that
node by concatenating the primary values of the arcs on the path. Arcs may have
secondary values, which do not necessarily identify the arc unambiguously, but are
readable so as to more clearly describe the nature of the object.
6.1.4 In general, the types of values assigned by a Registration Authority include integer
values, alphanumeric values, and other types of values, but the specific form of the RH
name tree restricts the types of values. The character set range and value composition
rules shall be defined in the Registration Authority's procedures. Subordinate
Registration Authorities may further restrict or extend the character set range and value
composition rules as needed.
6.1.5 The generation of certain specific name forms is defined in Appendix A, Appendix
B and Appendix C.
6.2 OID-specific RH name tree
6.2.1 The two types of ASN.1 object identifier (OBJECT IDENTIFIER) and OID
internationalized resource identifier (OID-IRI) are both ASN.1 types as specified in
ISO/IEC 8824-1, and their abstract values are associated with a specific form of RH
name tree (OID tree). The semantics of values of these types refer to the OID tree
specification.
NOTE 1: The ASN.1 OID-IRI type is more convenient for reading, while the ASN.1 OBJECT
IDENTIFIER type is more efficient for binary transmission. Protocol designers can choose when to use
the ASN.1 OBJECT IDENTIFIER type and when to use the ASN.1 OID-IRI type.
NOTE 2: For all objects in the OID tree, both ASN.1 OBJECT IDENTIFIER and OID-IRI types are
available for identification. This is because all arcs with a primary integer value automatically have an
integer-valued Unicode label defined (see 6.2.4). The former can be used for OID values and the latter
for OID-IRI values, even if there are no other Unicode labels and no secondary identifiers.
but need not be unambiguous. The alphanumeric value identifiers of arcs are required
to start with a lowercase letter and contain only letters, numbers, and hyphens; the
Unicode label identifiers of arcs are characters that conform to GB 13000. The last
character of the secondary identifier and additional secondary identifier shall not be a
HYPHEN-MINUS character, and the name shall not contain two consecutive
HYPHEN-MINUS characters (see ISO/IEC 8824-1).
NOTE: It is recommended that the same secondary identifier should not be used for two different arcs
under a given node.
6.2.8 For a given node, the primary integer values and all Unicode labels assigned to an
arc (including a long arc) under this node must be different from all primary integer
values and Unicode labels assigned to other arcs (including long arcs) of the same node.
NOTE 1: No requirements are placed on secondary identifiers.
NOTE 2: In the case of a root arc with primary identifier 2, it is possible to assign a Unicode label from
the root to the node directly under arc 2. The above unambiguous requirement for a Unicode label starting
at a node applies to these labels in addition to the labels of the node directly under the root.
NOTE 3: Two Unicode labels are different if and only if they contain different GB13000 character sets.
Unicode characters that are sometimes considered "similar" (such as uppercase and lowercase letters, or
numbers in different languages and different spaces) are distinguished in this part. The concept of font
or typeface related to display and print representation is not involved here. All of these belong to GB
13000 character code issues.
6.2.9 Each object identified is assigned to exactly one node (usually, but not necessarily,
a leaf node), and no other object is assigned to the same node. Thus, an object is
uniquely and unambiguously identified by the sequence of primary integer values of
the arcs on the path from the root to the node to which it is assigned, and is also
unambiguously identified by the sequence of Unicode labels of the arcs on the path
from the root to the node to which it is assigned.
NOTE: The mechanism for assigning primary integer values (defining an integer-valued Unicode label),
secondary identifiers, and additional secondary identifiers to top-level arcs is specified in Appendix A.
6.2.10 The arcs below root arc 2 are allocated by the joint agreement between ITU-T
and ISO/IEC. The allocation of Unicode labels is also determined by the joint
agreement between ITU-T and ISO/IEC.
NOTE: It is possible to assign a Unicode label that directly identifies a path consisting of two arcs, from
the root to the arc below arc 2 (Unicode label "JOINT-ISO-ITU-T", see A.7).
6.2.11 An ASN.1 OID value is semantically an ordered list of OID components. Starting
from the root of the OID tree, each OID component identifies an arc of the tree using
the arc's primary integer value. The final OID component identifies the arc
corresponding to the object node, and the object identified by the ASN.1 OBJECT
IDENTIFIER value is this object.
NOTE: ISO/IEC 8825 specifies the encoding of OBJECT IDENTIFIER values that can be used in
computer communications.
6.2.12 An OID-IRI value is semantically an ordered list of OID-IRI components.
Starting from the root of the OID tree, each OID-IRI component identifies an arc of the
tree using the arc's Unicode label. The final OID-IRI component identifies the arc
corresponding to the object node, and the object identified by the OID-IRI value is this
object.
NOTE: ISO/IEC 8825 specifies the encoding of OID-IRI values that can be used for computer
communications.
6.2.13 An ASN.1 value notation of an OBJECT IDENTIFIER type may contain
secondary identifiers.
6.2.14 When a standard assigns primary integer values, Unicode labels, and/or
secondary identifiers to identify objects, it is recommended that the standard contain an
appendix summarizing the assignments made, recording all the variants of the name
that can be used to identify the object (using an appropriate convention when there are
multiple variants), using either or both OBJECT IDENTIFIER and OID-IRI value
notations.
6.2.15 When a Registration Authority assigns an OBJECT IDENTIFIER value or an
OID-IRI value to identify an object, it is recommended that the Registration Authority
also assign a value of the ASN.1 Object Descriptor type (see ISO/IEC 8824-1) to
describe the object.
6.2.16 The ASN.1 value notation for an OID-IRI can be used outside of an ASN.1
module to identify an object. The ASN.1 value notation for an OBJECT IDENTIFIER
value can be used outside of an ASN.1 module to identify an object, as long as the
notation does not contain an ASN.1 value reference.
7 Registration procedures for specific types of objects
7.1 Registration procedures for specific types of objects may be specified in separate
standards. A distinction shall be made between registration procedures applicable to
general registration of object types and registration procedures applicable to specific
registrations specified by specific standards.
7.2 The standard content shall include:
a) Legitimate reasons for registration;
corresponding primary integer value.
A.3.3.2 Arcs below the arcs defined in A.3.3.1 have primary integer values (and
therefore integer-valued Unicode labels) corresponding to their numbers in the
sequence recommended by the ITU-T standard.
A.3.3.3 The editor of an identifier proposal may submit the proposal to the Standards
Development and Maintenance Study Group for agreement on the Unicode labels to be
assigned to the arcs of the standard proposal.
A.3.3.4 The secondary identifiers for the arcs specified in A.3.3.2 may be assigned in
the relevant ITU-T (or CCITT) Recommendations.
A.3.3.5 The necessity of arcs below the arc specified in A.3.3.2 is determined by the
corresponding ITU-T (or CCITT) Recommendations.
A.3.4 Arcs below the arc with primary integer value 1 (secondary identifier question)
have primary integer values corresponding to the ITU-T study group.
A.3.5 Arcs below the arc with primary integer value 2 (Unicode label "Administration",
secondary identifier administration) have primary integer values (and therefore integer-
valued Unicode labels) that are Data Country Code (DCC) values as defined in ITU-T
Rec.X.121.
A.3.6 Arcs below the arc with primary integer value 3 (Unicode label "Network-
Operator", secondary identifier network-operator) have primary integer values (and
therefore integer-valued Unicode labels) of the Data Network Identification Code
(DNIC) value defined in ITU-T Rec.X.121.
A.3.7 Arcs below the arc with primary integer value 4 (Unicode label "Identified-
Organization", secondary identifier identified-organization) are assigned primary
integer values (and therefore integer-valued Unicode labels), non-integer Unicode
labels, and secondary identifiers by ITU TSB in accordance with appropriate
procedures.
A.3.8 Arcs below the arc with primary integer value 5 (Unicode label "R-
Recommendation", secondary identifier r-recommendation) are determined by ITU-R
according to procedures defined by ITU-R.
A.4 Assignment of primary integer values, Unicode labels, and secondary
identifiers to ISO-administered arcs
A.4.1 Arcs below the root arc with primary integer value 1 (Unicode label "ISO",
secondary identifier iso) are administered by ISO.
A.4.2 Four arcs are defined under the node with primary integer value 1 (Unicode label
ISO 3166-1 to identify the ISO national body of that country. Non-integer Unicode
labels are assigned according to the "two-letter code (uppercase)" specified in ISO
3166-1. Arcs below the "country code" are assigned by each national body. Information
on the Chinese OID Registration Authority is shown in Appendix D.
A.4.7 Arcs below the arc with primary integer value 3 (Unicode label "Identified-
Organization", secondary identifier identified-organization) have primary integer
values (and hence integer-valued Unicode labels) that are International Code
Designator (ICD) values assigned by the Registration Authority specified in ISO/IEC
6523-2. Arcs below the ICD arc have primary integer values (and hence integer-valued
Unicode labels) that are assigned according to the "Organization Code" values assigned
by the issuing organization of ISO/IEC 6523-2. Secondary identifiers and Unicode
labels for arcs below the ICD may be assigned by the corresponding organization.
A.5 Assignment of OID components jointly administered by ISO and ITU-T
A.5.1 Arcs below the jointly-administered root arc with primary integer value 2
(Unicode label "Joint-ISO-ITU-T", secondary identifier joint-iso-itu-t) are assigned
through decisions of the relevant ITU-T study group and the relevant ISO/IEC JTC 1
Sub-Committee.
NOTE: The joint assignment of one or more arcs, and the responsibility of an organization for nodes
below those arcs, may result in additional Unicode labels or additional secondary identifiers for the top-
level arc with a primary integer value of 2 (Unicode label "Joint-ISO-ITU-T", secondary identifier joint-
iso-itu-t). These additional Unicode labels and secondary identifiers are assigned in accordance with
Chapters A.6 and A.7.
A.5.2 The values of the arcs below the jointly administered root arc with primary integer
value 2 (Unicode label "Joint-ISO-ITU-T", secondary identifier joint-iso-itu-t) are
assigned in real-time as needed through decisions of the relevant ITU-T study group
and the relevant ISO/IEC JTC 1 Sub-Committee, and are recorded and published in the
register of arcs below the root arc with primary integer value 2 in A.8. These allocations
can provide OID and IRI namespaces for other international standards organizations,
joint work areas, or other groups requiring object identifiers or OID international
resource identifiers. For detailed information on the contents of the registry entry and
the application and approval process, see ISO/IEC 9834-3.
NOTE: Unicode labels (long arcs) can also be assigned to directly identify nodes starting from the root
node, see A.7.
A.5.3 The arcs beneath each arc allocated in accordance with A.5.1 shall be allocated
according to the mechanism established when allocating that arc.
A.5.4 (Informative) One of the arcs below joint-iso-itu-t with primary integer value 17,
non-integer Unicode label "Registration_Procedures", and secondary identifier
at http://www.oid-info.com to provide information about registrations.
A.8.1.3 Other top-level arcs and additional information associated with top-level arcs
are determined by simple resolutions between the relevant ITU-T study group and the
relevant ISO/IEC JTC 1 Sub-Committee. The information includes:
a) the assignment of arcs (and their attributes) below the root arc with primary
integer value 2 (see A.5);
b) the assignment of additional secondary identifiers and non-integer Unicode
labels to root arcs, including the root arc with primary integer value 2 (see A.6);
c) the assignment of Unicode labels for long arcs (see A.7).
These are called "jointly administered registers".
A.8.1.4 The jointly administered registers are maintained by the relevant ITU-T study
group on the website and updated by the ISO/IEC JTC 1 Collaborative Team for Object
Identifiers when there are changes to the register entries. The OID database at
http://www.oid-info.com is also updated accordingly.
A.8.2 Application for an entry to a jointly administered register
A.8.2.1 The application shall be submitted to the relevant ITU-T study group (through
ITU-TTSB) or the relevant ISO/IEC JTC 1 Sub-Committee (through the Sub-
Committee Secretariat), or to both, with the information specified in A.8.3.
A.8.2.2 These applications will be initially discussed at the next meeting of the Joint
ITU-T | ISO/IEC JTC 1 Collaborative Team for Object Identifiers, with appropriate
resolutions to be taken in a timely manner.
A.8.2.3 Upon approval, additional top-level arcs and additional attributes shall be
published via a page on the ITU-T study group website maintained by TSB. New
content on this page shall be provided by the Joint ITU-T | ISO/IEC JTC 1 Collaborative
Team for Object Identifiers when there is a change in the allocation status of top-level
arcs.
A.8.2.4 There is no charge for this activity.
A.8.3 Information to be recorded on the Web page for jointly administered
registers
A.8.3.1 Register of additional Unicode labels and secondary identifiers for root arcs:
See A.6.3 for information to be recorded for each entry.
A.8.3.2 Register of arcs below the root arc with primary integer value 2: See ISO/IEC
9834-3 for information to be recorded for each entry.
......
Source: Above contents are excerpted from the PDF -- translated/reviewed by: www.chinesestandard.net / Wayne Zheng et al.
|