Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 10742-94 / amd1-1997: OSI Network Layer Management Information Elements
Technical Overview of the Standard Defining Managed Objects for OSI Network Layer and Its 1997 Amendment
Scope and Purpose
The standard IEC 10742-94 (first edition 1994) and its amendment amd1-1997 (2001) specify the elements of management information related to the OSI Network Layer as defined in the OSI Basic Reference Model (ISO/IEC 7498). It is a joint ISO/IEC standard developed by JTC 1, SC 6.
This document defines the managed objects, attributes, operations, notifications, and behaviour that enable management of network layer entities, network service access points (NSAPs), and routing information. It forms a critical part of the OSI Systems Management framework (ISO/IEC 10165 series).
Amendment 1, approved in 1997 and consolidated in 2001, extends the original standard to align with evolving network layer protocols such as connectionless service (CLNS) and connection-oriented service (CONS), adding new managed object classes and clarifying conformance requirements.
Tip: When implementing IEC 10742-94, ensure alignment with the GDMO (Guidelines for the Definition of Managed Objects) syntax specified in ISO/IEC 10165-4. The amendment introduces mandatory changes that affect object behaviour.
Technical Requirements
Managed Object Classes
The core of IEC 10742-94 is its definition of network-layer managed objects. These include:
- networkLayerEntity – represents a single network layer entity within a system.
- networkServiceAccessPoint – represents an NSAP for connection establishment.
- routingInformationBase – contains the routing table and related forwarding information.
- networkProtocolMachine – models the state machine for protocol operation (added in Amendment 1).
Attributes and Operations
Each managed object class has a set of mandatory and optional attributes (e.g., nsapAddress, entityId, relayCapability). The standard specifies operations such as Get, Set, Action, and Notification (event reports) to manage these objects.
| Managed Object Class | Key Attributes | Operations |
|---|---|---|
| networkLayerEntity | entityId, configuredNSAPs, relayCapability | Get, Set, Action (reset), Notification (stateChange) |
| networkServiceAccessPoint | nsapAddress, nsapCategory, supportedOptions | Get, Set, Action (create/delete) |
| routingInformationBase | routingTable, routingAlgorithms, nextHop | Get, Action (flush, update) |
| networkProtocolMachine (amd1) | state, protocolVersion, errorCount | Get, Notification (stateChange, protocolError) |
Amendment 1 Enhancements
Amendment 1 (1997) introduced several important technical changes:
- Addition of the networkProtocolMachine object class to enable real-time protocol monitoring.
- New attributes for NSAP categories (e.g., nsapCategory values for CLNS vs CONS).
- Updated behaviour for relay operations to support multi-protocol environments.
- Clarified conformance requirements: implementations must declare which network layer protocols they support against the augmented object definitions.
Warning: Implementations that were compliant with the original 1994 edition must re-validate conformance after the amendment. In particular, the mandatory status of the networkProtocolMachine object may be required depending on the protocol profile.
Implementation Highlights
Use of GDMO and CMIP
IEC 10742-94 follows the GDMO framework (ISO/IEC 10165-4). Managed object definitions are provided in GDMO notation, which can be compiled into management information bases (MIBs) for use with CMIP (Common Management Information Protocol). The standard itself does not mandate a specific management protocol, but its object definitions are designed to be protocol-independent.
For practical implementations, most vendors map these objects to SNMP MIBs using appropriate translation guidelines. However, the native CMIR (Common Management Information Service) environment remains the most direct target.
Interoperability Considerations
To achieve interoperable network layer management, all implementations must share the same object identifiers (OIDs) for each class and attribute. The standard assigns these OIDs under the joint-iso-ccitt branch. The amendment reissues the OID assignments for the new objects.
Success: Products that conform to IEC 10742-94 / amd1-1997 can be integrated into a larger OSI management system using standard tools (e.g., TMN). Many legacy telecommunications systems still rely on these definitions.
Compliance and Testing
Conformance to IEC 10742-94 is assessed through a combination of static and dynamic testing. The standard defines conformance requirements in its base text and amendment:
- Static conformance: mandatory classes and attributes must be present as declared in a Protocol Implementation Conformance Statement (PICS).
- Dynamic conformance: behaviour of operations and notifications must match the state machine and event sequences defined in the standard.
Testing is typically performed using standardized test suites based on the GDMO definitions. An implementation can claim conformance to the amendment only if it supports all added objects and modified behaviours.
Important: IEC 10742:1994 and its amendment have been superseded by later revisions (e.g., ISO/IEC 10742:2004). Check the current status of your target standard before investing in new development. For maintenance of existing systems, this edition remains relevant documentation.
Frequently Asked Questions
Q: What is the relationship between IEC 10742-94 and the OSI management framework?
A: IEC 10742-94 is a Layer Management standard that specifies managed objects for the OSI Network Layer, operating under the Systems Management framework (ISO/IEC 10165). It defines the information model used by management applications to monitor and control network layer resources.
A: IEC 10742-94 is a Layer Management standard that specifies managed objects for the OSI Network Layer, operating under the Systems Management framework (ISO/IEC 10165). It defines the information model used by management applications to monitor and control network layer resources.
Q: What managed objects does the standard define?
A: The standard defines several classes including networkLayerEntity, networkServiceAccessPoint, routingInformationBase, and networkProtocolMachine (added in the amendment). Each class has a set of attributes, operations, and notifications that enable management of addressing, routing, and protocol functions.
A: The standard defines several classes including networkLayerEntity, networkServiceAccessPoint, routingInformationBase, and networkProtocolMachine (added in the amendment). Each class has a set of attributes, operations, and notifications that enable management of addressing, routing, and protocol functions.
Q: How does Amendment 1 (1997) change the original standard?
A: Amendment 1 adds the networkProtocolMachine object class, extends attributes for NSAP categories, updates relay behaviour, and tightens conformance requirements. It also aligns the standard with newer network layer protocols such as CLNP (connectionless) and X.25 PLP (connection-oriented).
A: Amendment 1 adds the networkProtocolMachine object class, extends attributes for NSAP categories, updates relay behaviour, and tightens conformance requirements. It also aligns the standard with newer network layer protocols such as CLNP (connectionless) and X.25 PLP (connection-oriented).
Q: Is this standard still relevant today?
A: While the 1994 edition plus 1997 amendment is superseded, the concepts are still used in legacy OSI and TMN networks. Modern network management often uses SNMP, but the object definitions in IEC 10742-94 continue to influence management information models for layer 3 in telecommunications environments.
A: While the 1994 edition plus 1997 amendment is superseded, the concepts are still used in legacy OSI and TMN networks. Modern network management often uses SNMP, but the object definitions in IEC 10742-94 continue to influence management information models for layer 3 in telecommunications environments.
Technical article prepared for education and reference purposes. Always refer to the latest official IEC release for compliance. — 2026.