ISO/IEC 7498-1 1994 Edition, November 15, 1994
Information Technology - Open Systems Interconnection - Basic Reference Model: the Basic Model
Additional Comments: ENGLISH * CORRECTED AND REPRINTED 06/15/96
Published By:International Organization for Standardization (ISO)
The purpose of this Reference Model of Open Systems Interconnection is to provide a common basis for the coordination of standards development for the purpose of systems interconnection. while allowing existing standards to be placed into perspective within the overall Reference Model.
The term Open Systems Interconnection (OSI) qualifies standards for the exchange of information among systems that are “open” to one another for this purpose by virtue of their mutual use of the applicable standards.
The fact that a system is open does not imply any particular systems implementation, technology or means of interconnection, but refers to the mutual recognition and support of the applicable standards.
It is also the purpose of this Reference Model to identify areas for developing or improving standards, and to provide a common reference for maintaining consistency of all related standards. It is not the intent of this Reference Model either to serve as an implementation specification, or to be a basis for appraising the conformance of actual implementations, or to provide a sufficient level of detail to define precisely the services and protocols of the interconnection architecture. Rather, this Reference Model provides a conceptual and functional framework which allows international teams of experts to work productively and independently on the development of standards for each layer of the Reference Model for OSI.
The Reference Model has sufficient flexibility to accommodate advances in technology and expansion in user demands. This flexibility is also intended to allow the phased transition from existing implementations to OSI standards.
While the scope of the general architectural principles required for OSI is very broad, this Reference Model is primarily concerned with systems comprising terminals, computers, and associated devices and the means for transferring information between such systems. Other aspects of OSI requiring attention are described briefly (see 4.2).
The description of the Basic Reference Model of OSI is developed in stages:
Clause 4 establishes the reasons for Open Systems Interconnection, defines what is being connected, the scope of the interconnection, and describes the modelling principles used in OSI.
Clause 5 describes the general nature of the architecture of the Reference Model; namely that it is layered, what layering means, and the principles used to describe layers.
Clause 6 names, and introduces the specific layers of the architecture.
Clause 7 provides the description of the specific layers.
Clause 8 provides the description of Management Aspects of OSI.
Clause 9 specifies compliance and consistency with the OSI Reference Model.
An indication of how the layers were chosen is given in Annex A to this Basic Reference Model.
Additional aspects of this Reference Model beyond the basic aspects are described in several parts. The first part describes the Basic Reference Model. The second part describes the architecture for OSI Security. The third part describes OSI Naming and Addressing. The fourth describes OSI System Management.
The Basic Reference Model serves as a framework for the definition of services and protocols which fit within the boundaries established by the Reference Model.
In those few cases where a feature is explicitly marked (optional) in the Basic Reference Model it should remain optional in the corresponding service or protocol (even if at a given instant the two cases of the option are not yet documented).
This Reference Model does not specify services and protocols for OSI. It is neither an implementation specification for systems, nor a basis for appraising the conformance of implementations.
For standards which meet the OSI requirements, a small number of practical subsets are defined from optional functions, to facilitate implementation and compatibility.