Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC 10164-3:1995 (Confirmed 2004) – Systems Management: Attributes for Representing Relationships
Understanding the Technical Framework for Relationship Representation in OSI Systems Management
ISO/IEC 10164 is a multi-part standard under the joint ISO/IEC JTC 1 subcommittee for Information Technology. Part 3, formally designated as ISO/IEC 10164-3:1995 (also known as ITU-T Recommendation X.723), defines the management attributes that allow managed objects in an OSI environment to represent relationships with other managed objects. This standard, confirmed in 2004, remains a foundational component for systems management, providing a consistent and interoperable method to model associations, dependencies, and hierarchies within the Open Systems Interconnection (OSI) management framework.
Scope
ISO/IEC 10164-3 establishes the attributes that represent relationships between managed objects. It applies to any OSI systems management environment where managed objects need to express connections, such as:
- Dependency relationships (e.g., service A depends on service B)
- Peer relationships (e.g., two network nodes at the same level)
- Hierarchical associations (e.g., a container and its contained objects)
- General associations (e.g., a simple link between objects)
The standard specifies the abstract syntax and semantics for attributes that are used to describe such relationships. It also defines the Managed Object Relationship (MOR) concept and the Relationship Object (RO) class, enabling systems to exchange relationship information consistently across different management domains. The scope includes both mandatory and optional packages for the relationship attributes.
Tip: When implementing relationship attributes, ensure consistent usage of the
relationshipLabel attribute for unique identification across management domains.Technical Requirements
The core of ISO/IEC 10164-3 consists of a set of attributes, each with a defined ASN.1 syntax and behavioral semantics. These attributes are used within managed object classes to represent one or more relationships. The following table summarizes the primary attribute types defined by the standard:
| Attribute Name | Description | Requirement Level |
|---|---|---|
relationshipLabel | A label that uniquely identifies a relationship in the context of the managing system. | Mandatory |
relationshipObject | Specifies the managed object instance(s) that are participants in the relationship. May be a single object or a set. | Mandatory |
relationshipType | Indicates the kind of relationship (e.g., dependency, peer, containment). | Conditional |
relationshipMode | Describes the cardinality of the relationship (e.g., one-to-one, one-to-many, many-to-many). | Optional |
relationshipDirection | Defines the direction of the relationship (e.g., source, target, bidirectional). | Optional |
In addition to attributes, the standard defines the Relationship Object class, a managed object that explicitly represents a relationship. This object class contains the relationship attributes and may support additional operations such as create, delete, and get. The GDMO (Guidelines for the Definition of Managed Objects) template for the Relationship Object is included, allowing implementers to incorporate it directly into their management information bases (MIBs).
Warning: The
relationshipObject attribute may contain references to managed objects located in different management domains. Cross-domain reference handling requires careful management of naming contexts and access control.Implementation Highlights
Implementing ISO/IEC 10164-3 involves the following key steps:
1. Attribute Inclusion in Managed Object Classes
Designers of managed object classes (in GDMO) should include the relevant relationship attributes as ATTRIBUTE templates. The mandatory attributes (relationshipLabel and relationshipObject) must be present in any class that claims conformance to a relationship package. The optional attributes can be added as conditionally required based on the relationship type.
2. Use of Relationship Object Class
When relationships are complex or require independent lifecycle management, the Relationship Object class should be instantiated. This object class is defined using GDMO and includes the attributes listed in the table. Operations on relationship objects should follow the standard’s specifications for create, delete, and attribute change notifications.
3. Behaviour Compliance
The standard defines specific behavior for attribute operations. For example, when a relationshipObject reference points to a managed object that no longer exists, the relationship attribute should indicate the inconsistency. Implementers must ensure that the management application handles such cases according to the standard’s error handling rules.
4. Notifications
Changes in relationship state can be reported using the attributeValueChange notification defined in companion standards (e.g., ISO/IEC 10164-5). The relationship attributes are designed to be compatible with these event reporting mechanisms.
Success: Proper implementation of ISO/IEC 10164-3 enables robust event correlation and dependency tracking, which is critical for integrated network, system, and application management.
Compliance Notes
Conformance to ISO/IEC 10164-3 is claimed with respect to the System Management Overview standard (ISO/IEC 10040) and the OSI management framework. Key compliance requirements include:
- Mandatory Packages: An implementation must support the relationship attributes as defined in the relevant packages. The relationshipLabel and relationshipObject are mandatory for any relationship instance.
- Optional and Conditional Packages: The standard defines several packages (e.g., the “relationshipPackage” and the “conditionalRelationshipPackage”). Conformance statements must specify which packages are supported, and conditional packages must be implemented if the corresponding conditions (e.g., specific relationship types) are present.
- GDMO Conformance: Managed object classes that claim conformance to this standard must provide GDMO templates that are consistent with the standard’s attribute definitions. The class must also follow the behavior requirements for attribute operations.
- Interoperability Testing: Exchanged relationship information must be syntactically compatible. Implementations should be validated against test cases that verify the consistency of relationshipLabel uniqueness and relationshipObject referential integrity.
Danger: Non-compliance with the attribute definition semantics, especially regarding the interpretation of relationshipObject references, may lead to serious interoperability failures when relationship information is exchanged across OSI management systems.
The standard is stable and has been confirmed in 2004, meaning it has not undergone technical changes but remains a recognized specification. For modern systems management environments, concepts from this standard continue to influence relationship modeling in frameworks like CORBA, TM Forum’s SID, and DMTF’s CIM.
Frequently Asked Questions
Q: What is the relationship between ISO/IEC 10164-3 and ITU-T X.723?
A: They are technically identical. ITU-T Recommendation X.723 corresponds to ISO/IEC 10164-3:1995. Both reference the same attribute definitions and object classes.
A: They are technically identical. ITU-T Recommendation X.723 corresponds to ISO/IEC 10164-3:1995. Both reference the same attribute definitions and object classes.
Q: Are the attributes defined in this standard mandatory for all managed objects?
A: No. They are applicable only to managed objects that represent relationships with other objects. The standard provides optional and conditional packages, so an implementer may choose to include only the attributes relevant to the relationship model.
A: No. They are applicable only to managed objects that represent relationships with other objects. The standard provides optional and conditional packages, so an implementer may choose to include only the attributes relevant to the relationship model.
Q: How does this standard relate to GDMO?
A: The attribute definitions are given in GDMO template form. The standard includes complete GDMO specifications for the Relationship Object class, making it straightforward to integrate the attributes into any OSI management information base (MIB).
A: The attribute definitions are given in GDMO template form. The standard includes complete GDMO specifications for the Relationship Object class, making it straightforward to integrate the attributes into any OSI management information base (MIB).
Q: Is ISO/IEC 10164-3 still current?
A: Yes, it was confirmed in 2004 and remains a stable specification for OSI systems management. While newer frameworks increase abstraction, the underlying concepts of relationship attributes continue to be relevant for interoperability.
A: Yes, it was confirmed in 2004 and remains a stable specification for OSI systems management. While newer frameworks increase abstraction, the underlying concepts of relationship attributes continue to be relevant for interoperability.
—
© 2026 International Standards Article. This work is provided for informational purposes and does not constitute an official interpretation of ISO/IEC 10164-3.