TECHNICAL ISO/IEC

REPORT TR 10000-2

Fifth edition
1998-11-01

Information technology — Framework and

taxonomy of International Standardized
Profiles —
Part 2:
Principles and Taxonomy for OSI Profiles
Technologies de l'information — Cadre et taxinomie des profils normalisés
internationaux —
Partie 2: Principes et taxinomie pour profils OSI

BC Reference number
ISO/IEC TR 10000-2:1998(E)
ISO/IEC TR 10000-2:1998(E)

Contents

FOREWORD .............................................................................................................................................. iv
INTRODUCTION ........................................................................................................................................... v
1 SCOPE....................................................................................................................................................1
2 REFERENCES ..........................................................................................................................................1
3 DEFINITION .............................................................................................................................................1
4 ABBREVIATIONS.......................................................................................................................................2
4.1 General abbreviations .......................................................................................................................................................... 2
4.2 Abbreviations used in Profile identifiers.............................................................................................................................. 2
5 THE OSI TAXONOMY: PRINCIPLES............................................................................................................2
5.1 General................................................................................................................................................................................. 2
5.2 The Class concept for OSI Profiles...................................................................................................................................... 3
5.3 Relationship between OSI Profiles....................................................................................................................................... 3
5.3.1 A/T and B/U Boundaries............................................................................................................................................... 3
5.3.2 A/F and B/F Boundaries ............................................................................................................................................... 3
5.4 The Group concept for OSI Lower Layer Profiles............................................................................................................... 5
5.5 Profile classes....................................................................................................................................................................... 5
5.5.1 Transport Profiles ......................................................................................................................................................... 5
5.5.1.1 Principles ............................................................................................................................................................... 5
5.5.1.2 Transport Profile Identifier .................................................................................................................................... 5
5.5.1.3 Connection-mode Transport Service: profile class T ............................................................................................. 6
5.5.1.4 Connectionless-mode Transport Service: Profile class U ...................................................................................... 6
5.5.1.5 Interworking between Transport Profile Groups.................................................................................................... 6
5.5.1.6 Introduction to the Taxonomy of Subnetwork Profiles .......................................................................................... 7
5.5.1.6.1 Packet Switched Data Network ....................................................................................................................... 8
5.5.1.6.2 Digital Data Circuit ......................................................................................................................................... 8
5.5.1.6.3 Analogue Telephone Circuit ........................................................................................................................... 8
5.5.1.6.4 Integrated Services Digital Network ............................................................................................................... 8
5.5.1.6.5 Local Area Networks ...................................................................................................................................... 8
5.5.1.6.6 Frame Relay Data Networks ........................................................................................................................... 8
5.5.2 Relay Profiles................................................................................................................................................................ 9
5.5.2.1 Principles ............................................................................................................................................................... 9
5.5.2.2 Relay Profile Identifier........................................................................................................................................... 9
5.5.3 Application Profiles ...................................................................................................................................................... 9
5.5.3.1 Principles ............................................................................................................................................................... 9
5.5.3.2 Common Upper Layer Requirements................................................................................................................... 10
5.5.3.3 Application Profile Identifier ............................................................................................................................... 10
5.5.3.4 Introduction to the Taxonomy of Application Profiles......................................................................................... 10
5.5.3.4.1 File Transfer, Access and Management ........................................................................................................ 10
5.5.3.4.2 Message Handling......................................................................................................................................... 10
5.5.3.4.3 Directory ....................................................................................................................................................... 11
5.5.3.4.4 Virtual Terminal............................................................................................................................................ 11
5.5.3.4.5 OSI Management .......................................................................................................................................... 11
5.5.3.4.6 Transaction Processing.................................................................................................................................. 12

© ISO/IEC 1998
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or
utilized in any form or by any means, electronic or mechanical, including photocopying and micro-
film, without permission in writing from the publisher.
ISO/IEC Copyright Office • Case postale 56 • CH-1211 Genève 20 • Switzerland
Printed in Switzerland

ii
© ISO/IEC ISO/IEC TR 10000-2:1998(E)

5.5.3.4.7 Remote Database Access ...............................................................................................................................12

5.5.3.4.8 Manufacturing Messaging .............................................................................................................................12
5.5.3.4.9 Library and Documentation ...........................................................................................................................12
5.5.3.4.10 Document Filing and Retrieval....................................................................................................................12
5.5.3.4.11 Interactive Manipulation of ODA Documents .............................................................................................13
5.5.4 Interchange Format and Representation Profiles .........................................................................................................13
5.5.4.1 Principles ..............................................................................................................................................................13
5.5.4.2 Interchange Format and Representation Profile Identifier....................................................................................13
5.5.4.3 Introduction to the Taxonomy of Interchange Format and Representation Profiles .............................................14
5.5.4.3.1 Open Document Format.................................................................................................................................14
5.5.4.3.2 Computer Graphics Metafile Interchange Format .........................................................................................14
5.5.4.3.3 SGML Interchange Format............................................................................................................................14
5.5.4.3.4 Directory Data Definitions.............................................................................................................................14
5.5.4.3.5 Virtual Terminal Environment.......................................................................................................................14
5.5.4.3.6 Character Sets................................................................................................................................................15
6 TAXONOMY OF PROFILES ...................................................................................................................... 15
6.1 Transport Profiles ...............................................................................................................................................................15
6.1.1 Taxonomy of Subnetworks..........................................................................................................................................15
6.1.2 Transport Groups.........................................................................................................................................................16
6.2 Relay Profiles .....................................................................................................................................................................17
6.2.1 Relaying the Network Internal Layer Service, as defined in ISO/IEC 10028..............................................................17
6.2.2 Network Layer Protocol Relaying ...............................................................................................................................17
6.2.3 Relaying the MAC Service ..........................................................................................................................................17
6.2.4 CO/CL Interworking....................................................................................................................................................17
6.3 Application Profiles............................................................................................................................................................17
6.3.1 File Transfer, Access and Management.......................................................................................................................17
6.3.2 Message Handling .......................................................................................................................................................17
6.3.3 Directory......................................................................................................................................................................18
6.3.3.1 Edition 1988 .........................................................................................................................................................18
6.3.3.2 Edition 1993 .........................................................................................................................................................18
6.3.4 Virtual Terminal ..........................................................................................................................................................18
6.3.5 OSI Management.........................................................................................................................................................18
6.3.6 Transaction Processing................................................................................................................................................19
6.3.7 Remote Database Access.............................................................................................................................................19
6.3.8 Manufacturing Messaging ...........................................................................................................................................19
6.3.9 Library and Documentation .........................................................................................................................................19
6.3.10 Document Filing and Retrieval..................................................................................................................................20
6.3.11 Interactive Manipulation of ODA Documents...........................................................................................................20
6.4 Interchange Format and Representation Profiles ................................................................................................................20
6.4.1 Open Document Format ..............................................................................................................................................20
6.4.2 Computer Graphics Metafile Interchange Format .......................................................................................................20
6.4.3 SGML Interchange Format..........................................................................................................................................20
6.4.4 Directory Data Definitions ..........................................................................................................................................20
6.4.4.1 Edition 1988 .........................................................................................................................................................20
6.4.4.2 Edition 1993 .........................................................................................................................................................21
6.4.5 Virtual Terminal Environment.....................................................................................................................................21
6.4.6 Character Sets..............................................................................................................................................................21
7 CONFORMANCE OF OSI PROFILES ......................................................................................................... 22
ANNEX A ................................................................................................................................................. 23
Bibliography.............................................................................................................................................................................23

iii
ISO/IEC TR 10000-2:1998(E) © ISO/IEC

Foreword

ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical
activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the
work.

In the field of information technology, ISO and IEC have established a joint technical committee,
ISO/IEC JTC 1.

The main task of technical committees is to prepare International Standards, but in exceptional
circumstances a technical committee may propose the publication of a Technical Report of one of the
following types:

 type 1, when the required support cannot be obtained for the publication of an International
Standard, despite repeated efforts;

 type 2, when the subject is still under technical development or where for any other reason there
is the future but not immediate possibility of an agreement on an International Standard;

 type 3, when a technical committee has collected data of a different kind from that which is
normally published as an International Standard ("state of the art", for example).

Technical Reports of types 1 and 2 are subject to review within three years of publication, to decide
whether they can be transformed into International Standards. Technical Reports of type 3 do not
necessarily have to be reviewed until the data they provide are considered to be no longer valid or
useful.

ISO/IEC TR 10000-2, which is a Technical Report of type 3, was prepared by Joint Technical
Committee ISO/IEC JTC 1, Information technology.

This fifth edition cancels and replaces the fourth edition (ISO/IEC TR 10000-2:1995), which has been
technically revised.

ISO/IEC TR 10000 consists of the following parts, under the general title Information technology -
Framework and taxonomy of International Standardized Profiles :

 Part 1: General principles and documentation framework

 Part 2: Principles and Taxonomy for OSI Profiles
 Part 3: Principles and Taxonomy for Open System Environment Profiles

Other parts to be defined as necessary.

iv
© ISO/IEC ISO/IEC TR 10000-2:1998(E)

Introduction

The context of Functional Standardization is one part of the overall field of Information
Technology standardization activities covering

• Base standards, which define fundamentals and generalized procedures. They

provide an infrastructure that can be used by a variety of applications, each of which
can make its own selection from the options offered by them.

• Profiles, which define conforming subsets or combinations of base standards used to

provide specific functions. Profiles identify the use of particular options available in the
base standards, and provide a basis for the development of uniform, internationally
recognized, conformance tests.

• Registration mechanisms, which provide the means to specify detailed

parameterization within the framework of the base standards or profiles.

Within ISO/IEC JTC 1, the process of Functional Standardization is concerned with the
methodology of defining profiles, and their publication in documents called "International
Standardized Profiles" (ISPs) in accordance with procedures contained in the Directives of
JTC 1. The scope of Information Technology standardization to which this process is being
applied is that which corresponds to the generally understood, but loosely defined, concept of
“Open Systems“. The objective is to facilitate the specification of IT systems characterized by
a high degree of interoperability and portability of their components.

In addition to ISO/IEC TR 10000, the secretariat of the Special Group on Functional

Standardization maintains a standing document (SD-4) entitled "Directory of ISPs and Profiles
contained therein". This is a factual record of which ISPs exist, or are in preparation, together
with an executive summary of each profile. It is subject to regular updating by the Secretariat
of ISO/IEC JTC 1/SGFS.

v
TECHNICAL REPORT © ISO/IEC ISO/IEC TR 10000-2:1998(E)

Information technology — Framework and taxonomy of

International Standardized Profiles —
Part 2:
Principles and Taxonomy for OSI Profiles

1 Scope also provide additional information, including the status of the

identified profiles.
The purpose of this part of ISO/IEC TR 10000 is to provide
principles and a classification scheme for OSI profiles which may
be or have been submitted for ratification as International 2 References
Standardized Profiles (ISPs).1
ISO/IEC 9646-6:1994, Information technology - Open Systems
ISO/IEC TR 10000-1 defines the concept of profiles which are Interconnection - Conformance testing methodology and
documented in ISPs. OSI profiles are a subset of OSE profiles. framework - Part 6: Protocol profile test specification. {ITU-T Rec.
ISO/IEC TR 10000-3 defines the concept of OSE profiles and, X.295 (1995)}
along with ISO/IEC TR 10000-1, gives guidance to organizations
making proposals for Draft ISPs, on the nature and content of the
ISO/IEC 9646-7:1995, Information technology - Open Systems
documents they are producing.
Interconnection - Conformance testing methodology and
framework - Part 7: Implementation Conformance Statements.
The existence of a profile classification in this part of
{ITU-T Rec. X.296 (1995)}
ISO/IEC TR 10000 does not reflect a judgment by
ISO/IEC JTC 1/SGFS that a profile is required for such capability.
It merely provides a capability to identify uniquely such a function ISO/IEC TR 10000-1:1998, Information technology - Framework
and to enable evaluation of PDISPs. and taxonomy of International Standardized Profiles - Part 1:
General principles and documentation framework.
Since profiles will be proposed according to needs identified to
SGFS and according to the progress of international base ISO/IEC TR 10000-3:1998, Information technology - Framework
standardization, the Taxonomy will be periodically updated or have and taxonomy of International Standardized Profiles - Part 3:
new parts added in order to reflect the progress reached. It is also Principles and Taxonomy for Open System Environment Profiles.
recognized that there will be proposals for the extension of the
Taxonomy to cover functions which were not identified during A number of other ISO, IEC, and ISO/IEC JTC 1 Standards and
preparation of this edition of ISO/IEC TR 10000. These extensions ITU-T Recommendations are quoted in examples which do not
may be identified by a variety of proposers and involve simple constitute provisions of this part of ISO/IEC TR 10000.
extensions to the existing Taxonomy or the addition of new func-
tional areas not currently covered by ISO/IEC TR 10000. The
inclusion of such extensions is administered following the proce-
dures elaborated by SGFS. 3 Definition

A distinction has been made between a profile and an ISP For the purposes of this part of ISO/IEC TR 10000, the following
documenting one or more profiles. The Taxonomy is only definition applies.
concerned with profiles, but further information is given in the
"Directory of ISPs and Profiles contained therein" as to which ISP 3.1 Group: A set of OSI profiles that are compatible, in the sense
contains the documentation of a profile. that an IT implementing one profile from a Group can interwork,
according to OSI, with another IT system implementing a different
This Directory is maintained as an SGFS standing document SD-4 profile from the same Group, in terms of the operation of the
(see Annex A). For each draft profile submitted to SGFS, it will protocols specified within these profiles.

1 This part of ISO/IEC TR 10000 defines only a taxonomy for OSI based
communication profiles; the issue of the placement of other communication
profiles is not addressed.

1
ISO/IEC TR 10000-2:1998(E) © ISO/IEC

4 Abbreviations 4.2 Abbreviations used in Profile

identifiers
4.1 General abbreviations
Abbr. Profile sub-class (Applications)
CGM Computer Graphics Metafile ADF Document Filing and Retrieval
CL Connectionless-mode ADI Directory (1988) 2
CLNS Connectionless-mode Network Service ADY Directory (1993) 2
CLTS Connectionless-mode Transport Service AFT File Transfer, Access and Management
CO Connection-mode ALD Library, Documentation
CONS Connection-mode Network Service AMH Message Handling
COTS Connection-mode Transport Service AMM Manufacturing Messaging
CSDN Circuit Switched Data Network AOD Interactive Manipulation of ODA Documents
CSI Communication Services Interface ARD Remote Database Access
CSMA/CD Carrier Sense, Multiple Access / Collision Detection ATP Transaction Processing
CULR Common Upper Layer Requirements100 AVT Virtual Terminal
DFR Document Filing and Retrieval
DSA Directory Service Agent Abbr. Profile sub-class (Formats)
DTAM-DM Document Transfer and Manipulation - Document FCG Computer Graphics Metafile Interchange Format
Manipulation FCS Character Sets
DTE Data Terminal Equipment FDI Directory Data Definitions (1988) 2
DUA Directory User Agent FDY Directory Data Definitions (1993) 2
EDI Electronic Data Interchange FOD Open Document Format
EDIMG EDI Messaging FSG SGML Interchange Format
FDDI Fibre Distributed Data Interface FVT Virtual Terminal Registered Objects
FR PVC Frame Relay Permanent Virtual Circuit
FR SVC Frame Relay Switched Virtual Call Abbr. Profile sub-class (Lower Layers)
FRBS Frame Relay Bearer Service TA COTS over CLNS
FRDN Frame Relay Data Network TB COTS over CONS
FRDTS Frame Relay Data Transmission Service TC COTS over CONS
IIF Image Interchange Facility TD COTS over CONS
IPI Image Processing and Interchange TE COTS over CONS
IPM Interpersonal Message UA CLTS over CLNS
ISDN Integrated Services Digital Network UB CLTS over CONS
ISP International Standardized Profile RA Relaying the CLNS
LAN Local Area Network RB Relaying the CONS
MAC Media Access Control RC X.25 Protocol Relaying
MMS Manufacturing Message Specification RD Relaying the MAC Service using transparent bridging
MOTIS Message Oriented Text Interchange System RE Relaying the MAC Service using source routing
MS Message Store RZ Relaying between CLNS and CONS
MTA Message Transfer Agent
MTS Message Transfer System
ODA Open Document Architecture 5 The OSI Taxonomy: Principles
P1 Message Transfer Protocol
P2 Interpersonal Messaging Protocol
P3 MTS Access Protocol
5.1 General
P7 MS Access Protocol
OSI profiles are primarily arranged into classes, each class
PSDN Packet Switched Data Network
representing a category of functionality of reasonable
PSTN Public Switched Telephone Network
independence from other classes. The different classes of profile
PVC X.25 Permanent Virtual Circuit
correspond to the major divisions of the taxonomy.
QOS Quality of Service
SGFS ISO/IEC JTC 1/Special Group on Functional
Within each class, a class-specific subdivision will be used.
Standardization
SGML Standardized General Markup Language
TP Transaction Processing
TPSU TP Service User
UA User Agent
VC X.25 Virtual Call 2 The taxonomy substructure for the 1988 edition of the Directory
specifications differs from the taxonomy substructure developed for the 1993
VT Virtual Terminal edition.

2
© ISO/IEC ISO/IEC TR 10000-2:1998(E)

OSI profile identifiers are structured in accordance with the F-profiles specify the characteristics and representation of various
general OSE taxonomy defined in ISO/IEC TR 10000-3. Thus, an types of information interchanged by A- and B-profiles.
OSI profile identifier comprises:
R-profiles specify Relay functionality needed to enable IT systems
• the suffix “-C“ (for a CSI profile); using different T- or U-profiles to interwork. Interworking between
T- and U-profiles is not contemplated in any JTC 1 work.
• a root mnenomic which is a character string commencing with
one letter that indicates the primary class of the profile; Within each of these classes, sub-classes of profiles are identified
which, again, may require further subdivision such that the
• an alphanumeric string that is as long as necessary to reflect granularity of the Taxonomy meets the requirements outlined in
the position of the profile within the hierarchic structure. ISO/IEC TR 10000-1. This leads to a hierarchical structure of
profile (sub-)classes which is given in full in clause “6 Taxonomy
The syntax of all but the first letter is subject to individual of Profiles“.
definitions (see below).
For the identification of sub-classes and a further subdivision
NOTE - In the context of the general OSE taxonomy defined in ISO/IEC TR 10000-3, within a given class, a class-dependent methodology is applied.
OSI profiles are identified as Communication Services Interface profiles by the
suffix “-C“. This suffix is omitted in the description of the OSI taxonomy in this
This is explained in the subsequent class-individual sections.
part of ISO/IEC TR 10000.
5.3 Relationship between OSI Profiles
5.2 The Class concept for OSI Profiles
The schematic illustration in Figure 1 brings together examples of
In order to decouple representation of information or objects from the relationships which exist between OSI profiles, particularly the
communication protocols, and application-related protocol from three main subdivisions of the Taxonomy, and the combinations
subnetwork types, OSI and OSI-related profiles are divided into which can be made between profiles from different classes.
the following classes:
5.3.1 A/T and B/U Boundaries
T- Transport profiles providing connection-mode Transport
Service Actual use of an A- or B-profile requires that an IT system operate
it in combination with a T- or U-profile, in order to provide a
U- Transport profiles providing connectionless-mode particular application protocol over a particular subnetwork type.
Transport Service The separation of A- and B-profiles from T- and U-profiles is
represented by an A/T or B/U boundary. This relationship is
R- Relay profiles illustrated vertically in Figure 1. The location of a set of A-profiles
above a set of T-profiles, separated by a common A/T boundary,
A- Application profiles requiring connection-mode Transport represents the possibility of combining any pair of A- and
Service T-profiles, one from each of the two classes.

B- Application profiles requiring connectionless-mode A similar situation exists for the B- and U-profiles. The A/T
Transport Service boundaries correspond to the OSI Connection-mode Transport
Service, and the B/U-boundaries to the OSI Connectionless-mode
F- Interchange format and representation profiles Transport Service. The possibility of making the combination
arises from the fact that a T- or U-profile is specified to provide the
Other classes may be required. OSI Transport Service and an A- or B-profile is specified to use
the OSI Transport Service.
Transport profiles of classes T and U specify how the two modes
of OSI Transport Service are provided over the two modes of OSI 5.3.2 A/F and B/F Boundaries
Network Service, and over specific subnetwork types, such as in-
dividual types of LANs, PSDNs, etc. In this way they isolate the The combination of an A- or B-profile with one or more F-profiles
A/B-profiles and F-profiles from network technology. will be selected by the user to meet the functional requirements in
each case. The various general possibilities are illustrated by the
T- and U-profiles are further subdivided into Groups. vertical relationships in Figure 1. The location of one or more
See “5.4 The Group concept for OSI Lower Layer Profiles“ for F-profiles above one or more A-/B-profiles, represents the
details. possibility of combining profiles from each class.

Application profiles of classes A and B specify communications Unlike the A/T and B/U boundaries, the A/F and B/F boundaries
protocol support for particular application types over the two are not characterized by a single service definition.
modes of OSI Transport Service, respectively.

3
ISO/IEC TR 10000-2:1998(E) © ISO/IEC

4
© ISO/IEC ISO/IEC TR 10000-2:1998(E)

The Application Layer base standards require, implicitly or working between IT systems conforming to them is made possible
explicitly, the structure of information carried or referenced by by LAN bridges and/or Network Layer relays.
them to be specified for each instance of communication. The
combination of A-/B-profiles with one or more F-profiles will be A Group is identified by labels of the form YXnnn, where Y is the
selected by the user to meet the functional requirements in each class identifier and X is a letter identifying the Group.
case. However, the choice may be subject to constraints which
can be expressed within either A-/B-profiles, F-profiles, or both.
5.5 Profile classes
In other A-/B-profiles, the Application Layer base standards
themselves constrain the choice of presentation context. 5.5.1 Transport Profiles
Constraints may also exist within an F-profile, arising either from 5.5.1.1 Principles
its base standard, or as a result of profile creation. These
constraints will limit the A-/B-profiles which can be used to transfer Transport profiles define the use of protocol standards from OSI
the information. layers 1 to 4, to provide the OSI Transport Service.

In summary, therefore, there are three forms of constraints A primary distinction is made between Transport profiles, based
affecting the combination of A-/B- and F-profiles: on the mode of Transport Service offered:

a) the choice of information to be transferred may be  Connection-mode Transport Service:

constrained by the Application Layer base standards, and profile class T
possibly further constrained by the A-/B-profile;
 Connectionless-mode Transport Service:
b) some interchange and representation base standards may profile class U
limit transfer to particular Application base standards; this
choice may be further constrained by the F-profiles; For the Transport profile classification within each class, the
following methodology is applied:
c) the combinations are not constrained by base standards,
but may be constrained by either A-/B- or F-profiles to a) As a first level distinction the Group concept
achieve some general function. (see “5.4 The Group concept for OSI Lower Layer
Profiles“) is used in the following way:
Note that, as always, in making his choice of combination, a user
must in practice take account not only of the constraints derived A lower layer Group is a collection of profiles which:
from profiles, but also the capabilities implemented in the end
systems involved in each instance of communication, to support • support the same combination of modes of Transport
the various profiles.
and Network Service;

5.4 The Group concept for OSI Lower • support the same Transport Protocol Class(es);
Layer Profiles
The notion of a Group is incorporated in the classification.
The Group concept is used in the Taxonomy as follows:
b) The second level distinction between profiles, i.e. within a
A Group is a set of T- or U-profiles that are compatible in the Group, is made according to the subnetwork type
sense that an IT system implementing one profile from the Group supported
and another IT system implementing a profile from the same (see “6.1.1 Taxonomy of Subnetworks“ for examples of
Group can be expected to interwork, according to OSI, to some subnetwork types).
minimum level which is determined by the mandatory features of
the profiles in the Group. c) Further subdivisions are made according to the
characteristics of a particular subnetwork, e.g., switched
Interworking according to OSI means end-to-end operation across versus leased line
a single subnetwork, or across multiple subnetworks linked by (see 6.1.1 for examples of such characteristics).
means of Network (or lower) Layer relays.
5.5.1.2 Transport Profile Identifier
An example of a Group is the set of T-profiles that provide the
Connection-mode Transport Service, using Class 4 Transport The identifier for a profile in the lower layers is of the form:
Protocol over the Connectionless-mode Network Service, provided
by ITU-T Rec. X.233 | ISO/IEC 8473-1. This Group has members YXabcde
which correspond to different subnetwork technologies but inter-

5
ISO/IEC TR 10000-2:1998(E) © ISO/IEC

where: Group TB: 0 and 2 and 4 (see note 2)

Group TC: 0 and 2 (see note 2)
Y = class designator, indicating the Transport Service Group TD: 0
mode: Group TE: 2 (see note 3)

T for Connection-mode NOTES

U for Connectionless-mode 1 'Mandatory' means those Transport Protocol classes made mandatory by the
base standard, ISO/IEC 8073, plus any class required for Group membership.
X = one letter indicating the lower-layer Group within the
2 The class negotiation rules to be employed are those in ITU-T
class, as defined in “5.5.1.3 Connection-mode Recommendation X.224.
Transport Service: profile class T“ and “5.5.1.4
Connectionless-mode Transport Service: Profile 3 An IT system implementing a profile from Group TE and claiming conform-
class U“ below. ance to ITU-T Recommendation X.224 also has to implement transport
protocol class 0.

abcde = the structured numerical identifier indicating the

subnetwork type supported in this profile. It is possible
that a further level of identifier may become necessary. 5.5.1.4 Connectionless-mode Transport
In general, when referencing a profile, only that level of Service: Profile class U
identifier which is necessary for uniqueness needs to
be used. a) Connectionless-mode Transport Service over
Connectionless-mode Network Service:
The identifier structure is not meant to capture the
variety of details and options of OSI layer 1 such as Group UA
attachment speeds and connectors. However, it is re-
cognized that this issue must be covered by the appro- The Connectionless-mode Transport Service (CLTS) is provided
priate profile specification. using the ITU-T Rec. X.234  ISO/IEC 8602 Connection-
less-mode Transport Protocol. This Group supports the mandatory
5.5.1.3 Connection-mode Transport Service: profile
operation of the ITU-T Rec. X.234  ISO/IEC 8602, over Connec-
class T
tionless-mode Network Service.
Based on functional standardization already under way in organi-
zations represented in SGFS and on standards already b) Connectionless-mode Transport Service over
developed, the following lower layer Groups are identified as be- Connection-mode Network Service:
ing of value. They are characterized as follows:
Group UB
a) Connection-mode Transport Service over
Connectionless-mode Network Service: The Connectionless-mode Transport Service (CLTS) is provided
using the ITU-T Rec. X.234  ISO/IEC 8602 Connection-
Group TA less-mode Transport Protocol. This Group supports the option of
the ITU-T Rec. X.234  ISO/IEC 8602 that operates over
The Connection-mode Transport Service (COTS) is provided over
Connection-mode Network Service.
the Connectionless-mode Network Service (CLNS) by requiring
the use of the Class 4 Transport Protocol as defined in ITU-T Rec.
NOTE - An IT system implementing a profile from Group UB and claiming conformance
X.224  ISO/IEC 8073. to the ITU-T Rec. X.234  ISO/IEC 8602 also has to implement the mandatory
operation over CLNS as required by the ITU-T Rec. X.234  ISO/IEC 8602.
NOTE - An IT system implementing a profile from Group TA and claiming conformance
to ITU-T Rec. X.224  ISO/IEC 8073 also has to implement the mandatory
transport protocol classes for operation over CONS as required by ITU-T Rec.
X.224  ISO/IEC 8073. 5.5.1.5 Interworking between Transport Profile
Groups
b) Connection-mode Transport Service over
Connection-mode Network Service The following tables 1 and 2 show the interworking capabilities
between profiles. Table 1 shows the interworking between profiles
The Connection-mode Transport Service (COTS) is provided over in profile class T, and table 2 shows the interworking among
the Connection-mode Network Service (CONS). profiles in profile class U. Successful establishment of a Transport
Connection is dependent upon successful negotiation of parame-
Profiles of this characteristic are further grouped according to their
ters, some of which are not considered in the following tables.
required support of Transport Protocol class(es):
No interworking is possible between Groups in class T and U
mandatory (see note 1)
because of the different mode of Transport Service provided.
transport protocol classes

6
© ISO/IEC ISO/IEC TR 10000-2:1998(E)

Entries in the tables have the following meaning: Special 1: Special restrictions for interworking exist
(see “6.2.4 CO/CL Interworking“).
Full: Full OSI interworking (an OSI relay may be
required (see “6.2 Relay Profiles“)) Special 2: Interworking between these profile types is not
contemplated in any JTC 1 work.
Restricted: Interworking capabilities are restricted in the
sense that the choice of Transport Protocol NOTE - Successful interworking depends not only on the satisfactory outcome of the
transport protocol class negotiation but also on dynamic responses during
classes may be restricted by the static transport initiation. Such dynamic responses can include, amongst others, re-
capability of the responder. Successful inter- sponder reactions to the offered Quality of Service (QOS) or to the specific op-
working is dependent on the satisfactory out- tions requested by the initiator.

come of class negotiation.

Special: Non-OSI relay required for interworking

(see also “5.5.2.1 Principles“)

Table 1 - Interworking amongst Groups in class T

Responder in Network Initiator in Group

Group Service mode TA TB TC TD TE

TA CL full special 1 special 1 special 1 special 1

TB CO special 1 full full full full
TC CO special 1 restricted full full full
TD CO special 1 restricted restricted full special 2
TE CO special 1 restricted restricted special 2 full

Table 2 - Interworking amongst Groups in class U

Responder in Initiator in Group

Group UA UB

UA full special 2
UB special 2 full

5.5.1.6 Introduction to the Taxonomy of The number of ways in which subnetworks may be implemented
Subnetwork Profiles and used is potentially very large. There are also cases where one
subnetwork type is used to access another subnetwork type which
Subnetwork types are characterized by a structured numerical has a higher network functionality. For example, an ISDN or a
identifier. The first digit of the numerical identifier classifies the FRDN may be used to access a PSDN which offers a higher
major subnetwork type being used for system interconnection functionality. The subnetwork taxonomy needs to reflect such
while the subsequent digits represent a subdivision of the combinations which are defined by ITU recommendations and
subnetwork type, indicating how use is made of the subnetwork offered by public network service providers.
type, or describing how the subnetwork is accessed. The major
subnetwork types, as identified by the first digit of the subnetwork Other subnetwork variations have been deemed to be, in practice,
identifier, are the following: less important to the goal of end system interoperability, e.g. some
electrical and physical interfaces that are prerequisites to
1 Packet Switched Data Network (PSDN) subnetwork connection establishment but transparent to data
2 Digital Data Circuit exchange. Therefore, aspects such as line speed, connector type,
3 Analogue Telephone Circuit or modem type have, in general, not been reflected in the
4 Integrated Services Digital Network (ISDN) subnetwork taxonomy. Such requirements may be included in
5 Local Area Network (LAN) actual ISPs, if considered important, or this area may be left as a
6 Frame Relay Data Network (FRDN) local matter for system installation.

7
ISO/IEC TR 10000-2:1998(E) © ISO/IEC

5.5.1.6.1 Packet Switched Data Network The permanent and circuit-mode services operate on ISDN B-
channels (indicated by the third digit of the subnetwork identifier)
The second digit of the subnetwork taxonomy identifier makes the through which the communicating DTEs are connected
overall distinction as to whether the access to the PSDN is transparently. In this case, the taxonomy uses the fourth digit to
permanent or switched. For each of these two major types of indicate whether the B-channel is used to operate the X.25 packet
access to the PSDN, the third digit of the subnetwork identifier layer protocol between DTEs or whether the connection is used to
denotes the type of network used to gain access to the PSDN. operate the ITU-T Rec. X.233 | ISO/IEC 8473-1. connectionless-
Currently defined networks for gaining access to the PSDN are a mode network protocol between DTEs. This last case of operating
PSTN line, a CSDN line, an ISDN B-channel, and a FRDN. the ITU-T Rec. X.233 | ISO/IEC 8473-1. connectionless-mode
network protocol without an underlying X.25 protocol is applicable
Except for the more complicated case of a FRDN access, the only to the RA and TA groups of profiles whereas the X.25
fourth digit of the PSDN subnetwork taxonomy identifier indicates operation over an ISDN subnetwork may be used to provide either
whether the X.25 logical channel operates on a Virtual Call or a the connection-mode network service or the connectionless-mode
Permanent Virtual Circuit. In the case of switched access to the network service.
PSDN, only Virtual Call operation is possible.
In the case of packet-mode service or frame relay bearer service
In the case of FRDN access to a PSDN, the fourth digit of the being used from the ISDN, the third digit of the ISDN subnetwork
subnetwork identifier indicates that a Frame Relay Permanent taxonomy identifier determines the type of ISDN channel being
Virtual Circuit (FR PVC) is used while a fifth digit indicates that the used to access the service. Such channels may be a
PSDN is used to provide for X.25 DTE operation. (semi-)permanent B-channel, a demand access B-channel, a
D-channel, or a permanent H-channel.
Place holders have been left in the PSDN subnetwork taxonomy
to allow for future specification of access to the PSDN through For packet-mode service or frame relay bearer service over ISDN,
other means, e.g. through an ISDN D-channel or H-channel, or the fourth digit of the ISDN taxonomy identifier indicates the type
through various combinations of a Frame Relay service operating of virtual path being used (Virtual Call, Permanent Virtual Circuit or
over ISDN. Switched Virtual Call) while the fifth digit, if present, provides
further detail on call control (with or without use of ITU-T Rec.
Q.931) or the type of DTE operation (TE1 operation for frame
5.5.1.6.2 Digital Data Circuit relay bearer service).
A Digital Data Circuit is typically an X.21 based service offering Place holders have been left in the ISDN subnetwork taxonomy to
although other interfaces are conceivable, e.g. ITU-T Rec. G.703 allow for future expansion of the level of detail in operation of the
based service offerings. The taxonomy currently makes no frame relay bearer service, as well as addition of a frame
distinction on this point which is left to actual profile definitions. switching bearer service over ISDN.
The second digit of the subnetwork taxonomy identifier determines 5.5.1.6.5 Local Area Networks
whether the circuit is established permanently (leased service) or
established by circuit-switching (dial-up). There is no further The subnetwork identifier has only two digits where the second
subdivision of the Digital Data Circuit subnetwork taxonomy digit indicates the type of LAN, no matter what protocol is
identifier. operating over such LAN. The types of LAN that are currently
recognized in the taxonomy are CSMA/CD, Token Bus, Token
5.5.1.6.3 Analogue Telephone Circuit Ring and FDDI.

The subnetwork identifiers for Analogue Telephone Circuits are 5.5.1.6.6 Frame Relay Data Networks
structured identically to the subnetwork identifiers for Digital Data
Circuits, i.e. the second digit of the subnetwork identifier indicates The FRDN subnetwork taxonomy is applicable to situations where
whether the analogue circuit is established permanently (leased a FRDN is used directly for system interconnection. Frame relay
service) or by circuit-switching (dial-up). subnetwork technology may also be used to access a PSDN
(covered under the PSDN subnetwork taxonomy) or to operate as
a service within an ISDN (covered under the ISDN subnetwork
5.5.1.6.4 Integrated Services Digital Network taxonomy).

The second digit of the ISDN subnetwork taxonomy identifier The second digit of the subnetwork taxonomy denotes whether
indicates the type of service being assumed from the ISDN. Four access to the FRDN is permanent (leased service) or switched
types of such service have been identified at this time; these being (dial-up). The third digit of the FRDN taxonomy indicates the type
permanent service (including semi-permanent service), circuit- of network used to access the FRDN. This may be an analogue
mode service, packet-mode service and frame relay bearer data circuit (PSTN leased or dial-up) or a special FRDTS (Frame
service. Relay Data Transmission Service, permanent or switched access).

8
© ISO/IEC ISO/IEC TR 10000-2:1998(E)

The fourth digit of the FRDN taxonomy is used to distinguish RXp.q represents a relay of type X between subnetwork type p
between the types of frame relay virtual connection (permanent and subnetwork type q.
virtual circuit or switched virtual call) whereas a fifth digit is used to
indicate the type of terminal operation (Frame Relay TE1 as A relay RXp.q is considered to provide the same functionality as
defined by the ITU-T). RXq.p unless otherwise stated.

Place holders have been left in the FRDN subnetwork taxonomy

to allow for future expansion of the level of detail in operation of 5.5.3 Application Profiles
the frame relay service.
5.5.3.1 Principles

5.5.2 Relay Profiles Application profiles define the use of protocol standards from OSI
layers 5 to 7, to provide for the structured transfer of information
5.5.2.1 Principles between end systems.

Relay profiles define the use of standards from OSI layers 1 to 4, Each Application profile is a complete definition of the use of
to provide relaying functions between OSI Transport profiles. protocol standards from OSI layers 5 to 7, though it may share
one or more common definitions of some part of its content with
No relays exist between different profiles of different Transport other Application profiles.
profile classes (T, U). To avoid, wherever appropriate, duplication of text related to
common parts, the concept of the Common Upper Layer
Relays may operate at various layers up to layer 4. However, Requirements has been introduced. These Common Upper Layer
relays operating at layer 4 are not OSI relays and hence some Requirements can be documented in a separate ISP or part
restrictions or limitations may be expected in their operation. Many thereof, to be referenced by using Application profiles
proposals for such relays have significant architectural issues (see “5.5.3.2 Common Upper Layer Requirements“).
associated with them relating to integrity, security, QOS, etc., and
the fact that an identifier has been allocated to them does not in- Furthermore, Application profiles can build on each other in such a
dicate that such issues have been resolved. way that one Application profile makes use of services provided by
another Application profile for specific modes of communication
5.5.2.2 Relay Profile Identifier (i.e. ALD22 profile, which is based on AMH2n profiles and AMH2n
profiles, which themselves are based on AMH1n profiles). The
The identifier for a Relay profile is of the form resulting combination of A-/B-profiles with one or more
underlaying A-/B-profile(s) will be selected by the user to meet the
RXp.q functional requirements in each case. However, the choice may
be subject to constraints which can be expressed within either
where A-/B-profile.

R= relay function In analogy with the primary distinction made between Transport
profiles, a primary distinction is made between Application profiles,
X= relay type identifier based on the mode of Transport Service they require:

This identifier will cover Profile class A: Application profiles requiring Con-
nection-mode Transport Service, i.e., using
- the layer at which the relay operates T-profiles

- the service mode being supported Profile class B: Application profiles requiring Connec-
tionless-mode Transport Service, i.e., using
- the type of relay U-profiles

p, q= subnetwork type identifier A further distinction is based on Application categories, related to

Application Layer OSI standards defined by JTC 1 and ITU-T.
p and q may each take the value of the abcde-structured
numerical identifier defined for Transport profiles. The fully In addition, Application categories have been identified related to
qualified structure need only be used where necessary the use of OSI protocols by other Technical Committees such as
(e.g., for circumstances where a distinction must be made ISO TC 184 (Manufacturing Messaging) and TC 46 (Library and
between LANs). Documentation).

9
ISO/IEC TR 10000-2:1998(E) © ISO/IEC

5.5.3.2 Common Upper Layer Requirements The AFT1n profiles are for the file transfer service covering a
single transfer of a file or part of a file between the filestores of two
Profiling specifications on Common Upper Layer Requirements end systems, taking into account files with differing complexity of
(CULR) describe sets of upper layer elements for common use by their internal file structure (constraint sets).
several Application profiles and are documented in an ISP.
The AFT2n profiles are for the file access service covering
CULR define the common use of OSI standards for the session repeated read/write access to files between the filestores of two
layer, presentation layer and part of the application layer. end systems, again for files with differing complexity of their
internal file structure.
An ISP defining an Application profile may reference the CULR as
the common basis for the selection of options for the upper layers AFT3 is a profile for the creation and deletion of files and the
and may add it’s own requirements in the form of further additional management of their characteristics, and AFT4 profiles the
choices for the use of the upper layer standards. function to manage directories of files in the filestore of a remote
system.
CULR do not specify a complete profile, and therefore have no
entry within the taxonomy of this Technical Report and no profile 5.5.3.4.2 Message Handling
identifier will be assigned.
The Message Handling profiles AMH1n, AMH2n and AMH3n are
5.5.3.3 Application Profile Identifier based on ISO/IEC 10021 and the equivalent CCITT/ITU-T X.400
Recommendations.
The identifier for a profile in the Application class is of the form:
The common messaging profiles (AMH1n) specify generic
CXYabc requirements that are expected to be supported by all MHS
implementations. The AMH13 profile covers the common
where: requirements to be supported by a UA or MS component when
using the P7 protocol versions defined in ITU-T X.413(1992) |
C = Application profile class designator: ISO/IEC 10021-5:1990, while the AMH15 profile covers the
common requirements to be supported by a UA or MS component
A for profiles requiring Connection-mode when using the new P7 protocol versions defined in ITU-T
Transport Service X.413(1995) | ISO/IEC 10021-5:1994. The AMH14 profile covers
the common requirements to be supported by a UA or MS
B for profiles requiring Connectionless-mode component when using the new P7 protocol versions defined in
Transport Service ITU-T X.413(1995) | ISO/IEC 10021-5:1994. Additionally, the
AMH13 and AMH15 profiles allow minimal support of content type-
XY = two letters corresponding to the names of the primary specific MS attributes to be claimed if support of the
subdivisions. These subdivisions are taken from the corresponding content type is claimed. The AMH12 profile covers
main categories of application functions and OSI ma- the common requirements to be supported by a MTS-user or MTA
nagement, as identified as main projects in JTC 1. component when using the P3 protocol versions defined in ITU-T
X.411(1992) | ISO/IEC 10021-4:1990, while the AMH14 profile
abc = the structured numerical identifier for the member(s) of covers the common requirements to be supported by a MTS-user
the subdivision. It is possible that a further level of or MTA component when using the new P3 protocol versions
subdivision may become necessary. Only that level of defined in ITU-T X.411(1996) | ISO/IEC 10021-4:1996.
identifier will be used which is necessary for
uniqueness. This level may vary among application The content type-specific profiles (AMH2n, AMH3n and further
functions (see Note). content types to be defined in the future) cover both end-to-end
UA-to-UA communication (the content protocol and associated UA
NOTE - An extension has been adopted for the use by the Network Management
taxonomy, which proposes to use also lower-case letters.
functionality) and use of Message Handling services (by requiring
See “5.5.3.4.5 OSI Management“ for details. conformance to the appropriate AMH1n profile(s) plus any
additional content type-specific requirements).
5.5.3.4 Introduction to the Taxonomy of
Application Profiles The AMH24/AMH34 and AMH26/AMH36 profiles allow an
IPM/EDIMG UA to interact with an MS in a full and flexible manner
5.5.3.4.1 File Transfer, Access and without having to retrieve complete messages. The
Management AMH24/AMH34 profiles cover the P7 protocol aspects in relation
to IPM/EDIMG as defined in ITU-T X.413(1992) | ISO/IEC
The profiles for File Transfer, Access and Management are based 10021-5:1990 and ITU-T X.435(1991) | ISO/IEC 10021-9:1995,
on ISO/IEC 8571. These profiles are subdivided into four classes. while the AMH26 profile covers the IPM P7 aspects defined in the
context of the new P7 protocol versions, as defined in ITU-T

10
© ISO/IEC ISO/IEC TR 10000-2:1998(E)

X.420(1996) | ISO/IEC 10021-7:1996. The AMH36 profile will 5.5.3.4.4 Virtual Terminal
cover the EDIMG P7 aspects defined in the context of the new P7
protocol versions and will be based on future new edition of ITU-T The Application profiles for the Virtual Terminal protocol have
X435 | ISO/IEC 10021-9. The AMH25 profile covers the IPM P7 taxonomy identifiers of the form AVTab, in which the identifier
aspects defined in the context of the new P7 protocol versions, as component a is a single digit and b is an integer that is not
defined in ITU-T X.413(1995) | ISO/IEC 10021-5:1994 and ITU-T restricted to a single digit. At present only two values are defined
X.420(1992) | ISO/IEC 10021-7:1995. Minimal attribute support for for the component a, corresponding to the two modes of operation
MS access in an IPM/EDIMG environment can be specified by of the Virtual Terminal Basic Class protocol specified in
claiming conformance to AMH13 and/or AMH15 with an additional ISO 9041-1. These are the asynchronous mode (A-mode) and the
claim of IPM/EDIMG content type and attribute support. The synchronous mode (S-mode) of operation. Other values of the
AMH23/AMH33 profiles cover the P3 protocol aspects in relation component a are reserved for future developments that may
to IPM/EDIMG as defined in ITU-T X.420(1992) | ISO/IEC specify additional modes of operation within the Basic Class, or
10021-7:1990 and ITU-T X.435(1991) | ISO/IEC 10021-9:1995, additional classes of operation of the Virtual Terminal protocol
while the AMH25 profile covers the IPM P3 aspects defined in the besides the Basic Class.
context of the new P3 protocol versions, as defined in ITU-T
X.420(1996) | ISO/IEC 10021-7:1996. The AMH35 profile will The Virtual Terminal protocol also makes use of Interchange
cover the EDIMG P3 aspects defined in the context of the new P3 Format and Representation Profiles. An introduction to the
protocol versions and will be based on future new edition of ITU-T taxonomy of these profiles is given in “5.5.4.3.5 Virtual Terminal
X435 | ISO/IEC 10021-9. Environment“.

5.5.3.4.3 Directory 5.5.3.4.5 OSI Management

Profiles for the Directory, based on the use of ISO/IEC 9594 and The taxonomy identifiers for OSI Management are of the form
the corresponding ITU-T X.500 Recommendations fall into two AOMabc.e.
classes:
The first digit of the taxonomy identifier, a, identifies the nature of
- Protocol and associated procedures; profiles within OSI Management:
- Schema and contents.
AOM1bc are the Management Communications profiles, i.e. the
The first of these is for the 1988 edition of the Directory profiles that specify the use of the OSI Upper layers and CMIP
specifications represented by the ADInn series of profiles, the protocol. Within AOM1bc profiles, the second digit, b, identifies
second by the FDInn series (see “5.5.4.3.4 Directory Data Management Communications profiles offering different support
Definitions“). levels of the OSI management communications features.

Withing the ADInn series, three classes are currently defined AOM2bc are the Systems Management Functions profiles, i.e. the
which relate to the protocol for accessing The Directory from profiles that specify the use of Systems Management Functions as
Directory User Agents, the protocol for interworking between defined in ISO/IEC 10164 series and corresponding ITU-T X.700
Directory System Agents within The Directory, and procedures for Recommendations. Within AOM2bc profiles, the second digit, b,
distributed operation of The Directory. identifies separate Management functionalities or capabilities such
as Performance or Security. These functionalities can undergo
Sub-categorisation relates to support for mechanisms related to one or more levels of refinement and grouping, with identifiers in
the distinct rôles of Directory User Agents and Directory System the form AOM2ab..e. For these taxonomy identifiers, a value of "1"
Agents, responders and initiators. in positions c, d or e indicates a "general" profile, i.e. a profile that
represents a grouping of functionalities which is of a general
A new taxonomy has been developed for the 1993 edition of the applicability nature and includes all detailed capabilities
Directory specifications. The ISPs developed for the 1988 edition associated with other values of the taxonomy identifier in the
of the Directory specification will be current in parallel with the same position.
ISPs for the 1993 edition. There should therefore be no overlap
between taxonomy identifiers for the two editions. The taxonomy AOM3bc are the Management Ensemble profiles.
developed for the 1993 edition of the Directory uses the taxonomy
identifier ADYnn for the protocol and associated procedures and In the area of Network Management it is probable that the use of
FDYnn for the Schema and contents (see 5.5.4.3.4). numerical identifiers alone would limit the substructuring of the
taxonomy. It is therefore planned to use alphanumerical identifiers
Interoperability between profiles belonging to the ADInn series in the sequence 1, 2, ...., 8, 9, a, b, ...., y, z. Only lower-case
and the profiles belonging to the ADYnn series is being addressed letters shall be used and the lower-case letter "l" has to be
by the ADYnn profiles. avoided.

11
ISO/IEC TR 10000-2:1998(E) © ISO/IEC

5.5.3.4.6 Transaction Processing The market requires open access to office libraries and archives in
a heterogenous environment, i.e. interchange of documents
The first level of the Taxonomy substructure corresponds to the accross domains using open standards. Existing products are
definition of the three conformance classes defined in the OSI TP specifically designed to the needs of their application areas.
standard. The second level corresponds to the selection between Therefore they support only parts of the basic DFR functionality,
Polarized Control and Shared Control for each of the conformance however, providing extended functionality for the domain they are
classes. designed for. In order to ensure a DFR based integration of these
products in a heterogeneous office joint functional subsets of DFR
5.5.3.4.7 Remote Database Access have to be defined.

(for further study) The functionality covered by DFR is currently implemented by a

wide variety of products supporting a subset of the DFR
5.5.3.4.8 Manufacturing Messaging functionality, namely:

The Manufacturing Message Specification allows interworking of − access to manuals on line

various equipment such as computers and programmable devices − access to project documentation
within the manufacturing environment. It resides in the Application − document archives and retieval systems
Layer of the OSI Reference Model and uses an object modelling − databases tailored for the storage of images or forms
approach for the description of manufacturing applications. MMS − distributed file systems
defines a set of messages suitable for the manipulation of the real
devices in the manufacturing environment. DFR functional standards provide the common subset of the
different systems - offering a unified access protocol to these
MMS has evolved into a multi-part ISO standard, ISO 9506. Parts different applications, flexible enough to provide the functionality
1 and 2, known as the core, describe the modelling approach, the concerned with the storage and archiving requirements of the
syntax and semantics of the service and protocol. Additional parts, different office systems.
known as the companion standards, describe the extensions of
the core for specific application areas, for example numerical Besides native DFR implementations gateways may be used. A
controllers, robot controllers and process control systems. gateway maps the internal protocol of the client applications in
one domain to the DFR protocol, therefore allowing applications to
5.5.3.4.9 Library and Documentation access other DFR sotres connected to the network. Also the DFR
protocol is mapped to the internal protocol, allowing outside DFR
The Library and Documentation (ALD) profiles are based on client applications to use the data stored within the domain. If
ISO/IEC 10163 Search & Retrieve (SR) and ISO/IEC 10161 required the information content may be converted to a
Interlibrary Loan (ILL) protocols. These specifications for SR and standardized format within the gateway. To use existing
ILL enable interworking between IT systems supporting services applications without modifications to the greatest extent possible,
for organizations such as libraries, information utilities and union functional levels have to be introduced in the DFR protocol.
catalogue centres.
The following substructure of the taxonomy has been chosen:
SR is intended for use by IT systems supporting information
retrieval services. SR provides capabilities for an IT system to a) Common Filing and Retrieval (ADF1n)
search a database in another open system for a record and
receive a result set of records in response. In many offices, some document stores and terminals such as
personal computers are connected by network. However, one
ILL is intended for use by IT systems supporting interlibrary loan terminal can not access to all document stores on the network,
services. These may participate in an interlibrary loan transaction because there are many kinds of protocols between document
in the role of a requester (i.e. an initiator of ILL requests), stores and terminals. The market needs interactive access to
responder (i.e. a provider of bibliographic material or information) all multi-vendors’ document stores on the network. Therefore
and/or intermediary (i.e. an agent that acts on behalf of a DFR Functional standards are required.
requester to find suitable responders).
b) Remote Store Management (ADF2n)
5.5.3.4.10 Document Filing and Retrieval
There is a need of having functional profiles oriented to the
Functional Standards for ISO/IEC 10166 DFR are required in management of a document store from remote applications.
order to satisfy the market needs of interactive access to
documents stored in office and library systems. This approach An example of this kind of application is when a user is provided
covers the most urgent needs of open document interchange for with the ability to handle a document store and manipulate,
the office systems in the market today. remotely, a selected document. For the selection of the
document and hte handling of the store, DFR is needed. For

12
© ISO/IEC ISO/IEC TR 10000-2:1998(E)

the inner manipulation of the documents, a second standards [1] ITU-T Recommendation T.413 (1994) | ISO/IEC 8613-3:1994,
for inner manipulation of the document is necessary. For Information technology - Open Document Architecture (ODA) and
example, if documents follow the ODA standard structure, the interchange format: Abstract interface for the manipulation of ODA
ODA Abstract Interface for Manipulation, combined with a documents.
communication mechansism, could be used.
[2] ITU-T Recommendation T.422 (1995) | ISO/IEC 8613-12:1996,
The “Remote Store Management“ profiles are oriented towards: Information technology - Open Document Architecture (ODA) and
interchange format: Identification of document fragments.
− remote manipulation of the remote store structure, without
reading documents or creating new ones, because all [3] ITU-T Recommendation T.435 (1995) Document Transfer And
document manipulation is performed at the server; Manipultion (DTAM) - Services and Protocols - Abstract service
− remote handling of DFR objects for further manipulation of definition and procedures for confirmed document manipulation.
selected documents by other applications that know the
structure of the document. [4] ITU-T Recommendation T.436 (1995) Document Transfer And
Manipultion (DTAM) - Services and Protocols - Protocol
All ADFnn profiles are defined hierarchically, with ADFn1 having specifications for confirmed document manipulation.
the lowest functionality, ADFn2 including the functionality of
ADFn1, etc.
5.5.4 Interchange Format and
5.5.3.4.11 Interactive Manipulation of ODA Representation Profiles
Documents
5.5.4.1 Principles
This taxonomy (AOD) specifies profiles for the remote interactive
manipulation of ODA documents. The profiles specify constraints Interchange Format and Representation Profiles define the
on the ODA manipulation operations, as specified in [1], and on structure and/or content of the information being interchanged by
the communication protocols to use. Application profiles. Hence, the main feature which distinguishes
them from Application profiles is the absence of a transfer
The taxonomy is based first on the communication protocols to function.
use:
Currently, only interchange formats defined in standards prepared
− AOD1x profiles: DTAM-DM service and protocol [3][4] by JTC 1/SC18, SC21, SC24 and ITU-T Study Group 7 and 8 are
− AOD2y profiles: Reserved for other services and protocols. included.3

For the moment, only one communication mechanism

(DTAM-DM) has been identified. 5.5.4.2 Interchange Format and Representation
Profile Identifier
Then the second level of the structure is the subset of the
manipulation operations used. The identifier for a profile in the Interchange Format and
Representation class is of the form:
The different aspects of the Abstract Interface (AI) for the
manipulation of ODA documents [1] and related communications FXYabc
standards, DTAM Manipulation [3] [4], that are considered in the
profiles for interactive ODA manipulations are: where:

− which operations to implement; F = Interchange Format

− which restrictions to apply to the arguments and results of the
allowed operations. Arguments and results have a direct XY = two letters corresponding to the names of the primary
relationship with the use of the mechanism for identification of subdivisions.
ODA document fragments [2];
− which errors to support; abc = the structured numerical identifier for the member(s) of
− which application contexts to use. the subdivision. It is possible that a further level of sub-
division may become necessary. Only that level of
Other aspects of the manipulation process should be considered identifier will be used which is necessary for unique-
in the applications using the profiles, but not in the profiles ness. This level may vary among the primary subdivi-
themselves. These may include: sions.

− which manipulation rules should be used:

3 F-profiles may also be relevant for OSE profiles (rather than only of OSI
− which DFR profiles should be used. profiles).

13
ISO/IEC TR 10000-2:1998(E) © ISO/IEC

5.5.4.3 Introduction to the Taxonomy of in the figure below. This shows profiles being described within the
Interchange Format and Representation model by the complexity of the problem and by the CGM version
Profiles (as defined in the base standard).

5.5.4.3.1 Open Document Format increasing (2) (4)

problem
The Open Document Format (FOD) profiles consist of a hierarchy size (3)
of related ODA Document Application profiles supporting
formatted, as well as, processable documents and image
applications. (1)

The structure of the Open Document Format (FOD) profile

Taxonomy consists of three levels of subdivision: a, b and c and 1 2 3
will have the appearance of FODabc. CGM Version

 Level a reflects the source of application or use and two The following profiles are defined and are described on the model
initial values are proposed: shown in the figure above:

0 Document processing applications (1) FCG11 Basic Scientific and Technical Graphics (BST);
1 Image applications e.g. business presentation graphics, simple desk
top publishing;
 Level b reflects the hierarchically related complexity and
functionality of the document structures and provides for (2) FCG23 Advanced Scientific and Technical Graphics
three values as currently defined: (AST); e.g. CAD, mapping, earth sciences;

1 Simple Document Structure (3) FCG32 Basic Presentation and Visualization (BPV); - the
2 Enhanced Document Structure model profile from the CGM standard, e.g.
3 Extended Document Structure graphics arts, high end desk top publishing;
The Simple Document Structure is intended to address (4) FCG33 Advanced Presentation and Visualization (APV);
the general requirements of current word processing e.g. imaging, scientific visualization.
applications. The Enhanced Document Structure is
intended to address the general requirements of emerging 5.5.4.3.3 SGML Interchange Format
word processing applications that have been enhanced
from the earlier, simple document structures supported by (for further study)
current word processing applications. The Extended
Document Structure is intended to address the general 5.5.4.3.4 Directory Data Definitions
requirements of emerging personal publishing, document
processing applications. The Directory Data Definition Format (FDI) profiles specify the
properties of Object Classes, Attribute Types, and Attribute
 Level c reflects the combination of content architectures
Syntaxes related to the use of the Directory Application profiles
supported and four values as currently defined (see note 2): (ADInn - see “5.5.3.4.3 Directory“). Two types of usage are
covered - common usage relevant to all such cases, and specific
1 Character Content Architecture only.
usage relevant to particular Application profiles.
2 Raster Graphics Content Architecture only.
3 Geometric Graphics Content Architecture only.
Similarly to the profiles for the Directory, a new taxonomy has
6 Character, Raster Graphics and Geometric Graphics
been developed for the 1993 edition of the Directory
Content Architectures.
specifications. The ISPs developed for the 1988 edition of the
NOTES Directory specification will be current in parallel with the ISPs for
1 For a given profile all three levels should be specified. the 1993 edition. There should therefore be no overlap between
taxonomy identifiers for the two editions. The taxonomy developed
2 Other values may be added as additional ISPs with different content
architectures are developed. for the 1993 edition of the Directory uses the taxonomy identifier
FDYnn.
5.5.4.3.2 Computer Graphics Metafile
Interchange Format 5.5.4.3.5 Virtual Terminal Environment

The CGM Format (FCG) profiles support the interchange of The Interchange Format and Representation profiles for the
picture information. Profiles fit within the conceptual model shown Virtual Terminal protocol have taxonomy identifiers of the form

14
© ISO/IEC ISO/IEC TR 10000-2:1998(E)

FVTabc, in which the identifier components a and b are single The syntax of all but the first letter is subject to individual definitions.
digits and c is an integer that is not restricted to be a single digit.
Each taxonomy entry corresponds to an information object that For historical reasons ISPs exist which use profile identifiers
may be referenced in a particular instance of communication by without the suffix “-C“. ISPs using these profile identifiers remain
the Virtual Terminal Basic Class protocol specified in ISO 9041-1. valid. In case of existing ISPs, the suffix “-C“ will be added when
revisions or maintenance occurs. New ISPs containing OSI
The specifications of these information objects are subject to profiles will include the suffix “-C“.
registration in accordance with ISO/IEC 9834. Two of the parts of
ISO/IEC 9834, namely parts 4 and 5, concern registration The inclusion of a profile in this clause is purely for the purpose of
procedures that are specific to the Virtual Terminal service and assigning a unique, meaningful identifier. It should be noted that
protocol. The three values defined in the identifier component a the inclusion of a profile identifier in this clause does not imply that
distinguish between the object types that are subject to one of such a profile has been developed or is under development. For
these specific procedures and the object types that are subject to such information, see the "Directory of ISPs and Profiles
the general registration procedures of ISO/IEC 9834-1. contained therein" (Standing document SD-4).

Furthermore, additional details of the functionality addressed by a

The significance of the identifier component b differs according to
specific taxonomy entry can be found in the Executive Summary
the value of the component a. The objects registered in
of the profile, which is included in SD-4.
accordance with ISO/IEC 9834-4 are VTE-profiles that are specific
to one of the two modes of operation of the Virtual Terminal Basic
Class protocol. The component b distinguishes between these two
6.1 Transport Profiles
modes. The objects registered in accordance with ISO/IEC 9834-5
6.1.1 Taxonomy of Subnetworks
are control object type definitions, each of which is entered into
one of a number of sub-registeres defined by these registration The following Taxonomy classifies subnetworks and, where
procedures. The component b distinguishes between these existing, different modes of operation over a particular
different sub-registers. The Virtual Terminal service defined in subnetwork, to provide the OSI Network Service. The Taxonomy
ISO 9040 also identifies a number of other object types that are is used in all Transport profile Groups, unless otherwise stated.
subject to registration under the general procedures of
ISO/IEC 9834-1. For these, the component b distinguishes abcde Subnetwork Type
between these different types of object.
1 PACKET SWITCHED DATA NETWORK (PSDN)
5.5.4.3.6 Character Sets 11 Permanent Access to a PSDN
111 PSTN leased line
Taxonomy identifiers for character set profiles are of the form 1111 Virtual Call (VC)
FCSab. The first level, FCSa, represents the top level 1112 Permanent Virtual Circuit (PVC)
categorization of character set profiles. To date, only one category
112 Digital data circuit / CSDN leased line
has been identified - Code Structures. Other categories may be
1121 Virtual Call (VC)
added as the result of future study. Within code structures, the
1122 Permanent Virtual Circuit (PVC)
second level, FCS1b, corresponds to the different classes of code
structure. To date, two classes are identified. Further classes may 113 ISDN B-channel, permanent5
be added. Within each class a number of options may be 1131 Virtual Call (VC)
identified. Each option may identify a type of use which may be, 1132 Permanent Virtual Circuit (PVC)
for instance, dependent on a particular region of the world. 114 ISDN H-channel, permanent 6
115 ISDN D-channel 5
116 Frame Relay Data Network (FRDN)
6 Taxonomy of Profiles 1162 Frame Relay PVC 7
11621 X.25 operation, Virtual Call8 9 10
OSI profile identifiers are structured in accordance with the
general OSE taxonomy defined in ISO/IEC TR 10000-3. Thus, an 5 Also includes the semi-permanent case.
OSI profile identifier comprises: 6 For further study.
7 It is for further study that the profiles make a distinction between the cases
when the Frame Relay connection is established over a circuit-switched
• the suffix “-C“ (for a CSI profile) 4; connection and when the Frame Relay connection is established using the
• a root mnenomic which is a character string commencing with frame relaying capabilities of the FRDN.
one letter that indicates the primary class of the profile; 8 This profile may be replaced with the following profiles: X.25 DTE operation,
• an alphanumeric string that is as long as necessary to reflect VC; X.25 DTE operation, PVC.
9 In case of X.25 DTE, it is for further study that the profiles make a distinction
the position of the profile within the hierarchic structure. between the case when an ISO/IEC 7776 frame is encapsulated within LAPF
frame and the case when ISO/IEC 8208 operates directly over LAPF using the
generic multiprotocol encapsulation method.
4 This suffix is omitted in the description of the OSI taxonomy in this part of 10 It is for further study that the profiles make a distinction between the cases
ISO/IEC TR 10000. when access to PSDN is by port access or by call control mapping.

15
ISO/IEC TR 10000-2:1998(E) © ISO/IEC

abcde Subnetwork Type abcde Subnetwork Type

12 Switched Access to a PSDN 5 LOCAL AREA NETWORKS

121 PSTN Case 51 CSMA/CD
1211 Virtual Call (VC) 52 Token Bus
122 CSDN Case 53 Token Ring
1221 Virtual Call (VC) 54 FDDI
123 ISDN B-channel Case
1231 Virtual Call (VC) 6 FRAME RELAY DATA NETWORK (FRDN)
61 Permanent access
2 DIGITAL DATA CIRCUIT 612 Frame Relay Data Transmission Service
21 Leased (Permanent) Service (FRDTS), permanent access
22 Dial-up (CSDN) 6122 Frame Relay Permanent Virtual Connection
61221 TE1 to TE1 operation 9 12
3 ANALOGUE TELEPHONE CIRCUIT
31 Leased (Permanent) Service
32 Dial-up (PSTN) 6.1.2 Transport Groups
4 INTEGRATED SERVICES DIGITAL NETWORK (ISDN)
41 Permanent Service 5 TA Group TA: COTS over CLNS
411 B-channel
4111 X.25 DTE to DTE operation For the detailed subnetwork Taxonomy
4112 CLNS DTE to DTE operation see “6.1.1 Taxonomy of Subnetworks“.

42 Circuit-mode Service TB Group TB: COTS over CONS :

421 B-channel with mandatory Transport Protocol
4211 X.25 DTE to DTE operation Classes: 0 and 2 and 4
4212 CLNS DTE to DTE operation
For the detailed subnetwork Taxonomy see 6.1.1.
43 Packet-mode Service
431 D-channel access TC Group TC: COTS over CONS :
4311 Virtual Call (VC) with mandatory Transport Protocol
43111 without use of Q.931 Classes: 0 and 2
43112 with use of Q.931
4312 Permanent Virtual Circuit (PVC) For the detailed subnetwork Taxonomy see 6.1.1.
432 B-channel permanent access 5
4321 Virtual Call (VC) TD Group TD: COTS over CONS :
43211 without use of Q.931 with mandatory Transport Protocol
43212 with use of Q.931 Class: 0
4322 Permanent Virtual Circuit (PVC)
For the detailed subnetwork Taxonomy see 6.1.1.
433 B-channel demand access
4331 Virtual Call (VC) TE Group TE: COTS over CONS :
with mandatory Transport Protocol
44 Frame Relay Bearer Service (FRBS) Class: 2
442 B-channel, permanent
4423 Frame Relay PVC For the detailed subnetwork Taxonomy see 6.1.1.
44231 TE1 operation 11

444 H-channel, permanent UA Group UA: CLTS over CLNS

4443 Frame Relay PVC
44431 TE1 operation 11 For the detailed subnetwork Taxonomy see 6.1.1.

UB Group UB: CLTS over CONS

11 A Frame Relay TE1 is defined as a Terminal Equipment that operates any For the detailed subnetwork Taxonomy see 6.1.1.
Layer 3 protocol (probably X.25 Packet Layer Procedures (PLP) or X.25 Data
Transfer Phase (DTP) as candidates among many others) over the core
functions of Q.922. An X.25 Data Terminal Equipment (DTE) is a DTE that
operates X.25 PLP or X.25 DTP in Layer 3 of data transfer. Therefore, "X.25
DTE operation" is considered as a special case of "TE1 operation" and this 12 This profile may be replaced with the following profiles: TE1 operation to
profile may be replaced with the following profiles: TE1 operation; X.25 DTE TE1 operation; X.25 DTE to X.25 DTE operation, VC; X.25 DTE to X.25 DTE
operation. operation, PVC.

16
© ISO/IEC ISO/IEC TR 10000-2:1998(E)

6.2 Relay Profiles The final position in the Taxonomy and the substructure of
this relay type is for further study.
6.2.1 Relaying the Network Internal Layer
Service, as defined in ISO/IEC 10028 An approach for this type of relay could be as suggested
in ISO/IEC TR 10172.
RA Relaying the Connectionless-mode Network Service
6.3 Application Profiles
For the subnetwork identifiers p, q (as defined in “5.5.2.2
Relay Profile Identifier“) see the detailed subnetwork 6.3.1 File Transfer, Access and
Taxonomy in “6.1.1 Taxonomy of Subnetworks“. Management

RB Relaying the Connection-mode Network Service AFT File Transfer, Access and Management

For the subnetwork identifiers p, q (as defined in “5.5.2.2 ab Substructure

Relay Profile Identifier“) see the detailed subnetwork
Taxonomy in “6.1.1 Taxonomy of Subnetworks“. 1 FILE TRANSFER SERVICE
11 Simple (Unstructured)
12 Positional (Flat)
6.2.2 Network Layer Protocol Relaying 13 Full (Hierarchical)

2 FILE ACCESS SERVICE

RC X.25 Protocol Relaying 22 Positional (Flat)
23 Full (Hierarchical)
An approach for this type of relay could be as suggested
in ISO/IEC TR 10029. 3 FILE MANAGEMENT SERVICE

For the subnetwork identifiers p, q (as defined in “5.5.2.2 4 FILESTORE MANAGEMENT SERVICE
Relay Profile Identifier“) see the detailed subnetwork
Taxonomy in “6.1.1 Taxonomy of Subnetworks“. 6.3.2 Message Handling

Only the following subnetwork type identifiers are valid: AMH Message Handling
11n, 21n, 31n, 41n, 43111, 4312, 43211, 4322, 5n.
abc Substructure

6.2.3 Relaying the MAC Service 1 COMMON MESSAGING

11 Message Transfer (P1)
RD Relaying the MAC Service using transparent bridging 111 Normal mode
112 X.410(1984) mode
For the subnetwork identifiers p, q (as defined in “5.5.2.2 12 MTS Access (P3)
Relay Profile Identifier“) see the detailed subnetwork 13 MS Access (P7)
Taxonomy in “6.1.1 Taxonomy of Subnetworks“. 14 MTS 94 Access (P3)
15 MS 94 Access (P7)
Only subnetwork type identifiers of the form 5n are valid
for use with RD relays. 2 INTERPERSONAL MESSAGING (IPM)
21 IPM Content
RE Relaying the MAC Service using source routing 22 IPM Requirements for Message Transfer (P1)
23 IPM Requirements for MTS Access (P3)
For the subnetwork identifiers p, q (as defined in “5.5.2.2 24 IPM Requirements for Enhanced MS Access (P7)
Relay Profile Identifier“) see the detailed subnetwork 25 IPM Requirements for MTS 94 Access (P3)
Taxonomy in “6.1.1 Taxonomy of Subnetworks“. 26 IPM Requirements for Enhanced MS 94 (P7)

Only subnetwork type identifiers of the form 53 and 54 are 3 EDI MESSAGING (EDIMG)
valid for use with RE relays. 31 EDIMG Content
32 EDIMG Requirements for Message Transfer (P1)
33 EDIMG Requirements for MTS Access (P3)
6.2.4 CO/CL Interworking 34 EDIMG Requirements for Enhanced MS Access
(P7)
RZ Relaying between Connectionless-mode Network Service 35 EDIMG Requirements for MTS 94 Access (P3)
and Connection-mode Network Service 36 EDIMG Requirements for Enhanced MS 94 (P7)

17
ISO/IEC TR 10000-2:1998(E) © ISO/IEC

6.3.3 Directory 6.3.4 Virtual Terminal

6.3.3.1 Edition 1988 AVT Virtual Terminal

ADI Directory ab Substructure

ab Substructure 1 BASIC CLASS (A-MODE)

11 A-mode Default
1 DIRECTORY ACCESS 12 Telnet
11 DUA Support of Directory Access 13 Scroll
12 DSA Support of Directory Access 14 ITU-T X.3 PAD Interworking
15 Transparent
2 DIRECTORY SYSTEM 16 Generalized Telnet
21 DSA Responder Role
22 DSA Initiator Role 2 BASIC CLASS (S-MODE)
21 S-mode Default
3 DISTRIBUTED OPERATIONS 22 Forms
31 DUA Support of Distributed Operations 23 Paged
32 DSA Support of Distributed Operations 24 Enhanced 13 Forms
25 Enhanced Paged

6.3.3.2 Edition 1993 6.3.5 OSI Management

ADY Directory AOM OSI Management

ab Substructure abcde Substructure

1 DUA BASIC FUNCTIONALITY 1 MANAGEMENT COMMUNICATIONS

11 DUA Support of Directory Access 11 Basic Management Communications
12 DUA Support of Distributed Operations 12 Enhanced Management Communications

2 DSA BASIC FUNCTIONALITY 2 MANAGEMENT FUNCTIONS

21 DSA Support of Directory Access 20 Super Combinations 14
22 DSA Support of Distributed Operations 21 Management Capabilities
211 General Management Capabilities
4 SECURITY CAPABILITIES 212 Alarm Reporting and State Management
41 DUA Authentication as DAP initiator Capabilities
42 DSA Authentication as DAP responder 213 Alarm Reporting Capabilities
43 DSA Authentication for DSP
44 DSA Simple Access Control 22 Event Report Management
45 DSA Basic Access Control 221 General Event Report Management

5 SHADOWING CAPABILITIES 23 Log Control

51 Shadowing using ROSE 231 General Log Control
52 Shadowing using RTSE
53 Shadowing subset 24 Security
241 General Security Capability
6 DIRECTORY ADMINISTRATION AND MANAGEMENT 242 Security Management Capabilities
61 Administrative areas 2421 General Security Management Capability
62 Establishment and utilisation of shadowing 2422 Security Alarm Reporting Capabilities
agreements 2423 Security Audit Trail Capabilities
63 Schema administration and publication 243 Security Services and Mechanism for
Management
7 DIRECTORY OPERATIONAL BINDING MANAGEMENT
PROTOCOL (DOP) CABAILITIES
71 Shadowing Operational Binding 13 The "enhanced" entries are placeholders for the addition of facilities which
72 Hierarchical Operational Binding will be specified in the forthcoming second addenda to the Basic Class Virtual
Terminal standards. These include specifically "ripple" editing functions.
73 Non-specific Hierarchical Operational Binding
14 The identification of these profiles is for further study.

18
© ISO/IEC ISO/IEC TR 10000-2:1998(E)

abcde Substructure ab Substructure

2431 General Security Services and Mechanisms 2 PROVIDER SUPPORTED UNCHAINED TRANSACTIONS
for Management 21 Polarized Control
2432 Access Control 22 Shared Control
24321 General Access Control 3 PROVIDER SUPPORTED CHAINED TRANSACTIONS
24322 Item rules Access Control List 31 Polarized Control
24323 Item rules Security Labels 32 Shared Control
24324 Item rules Capability List
24325 Global rules Access Control List
24326 Global rules Security Labels
6.3.7 Remote Database Access
24327 Global rules Capability List
ARD Remote Database Access
25 Performance
251 General Performance
ab Substructure
252 Metric Objects
2521 General Metric Capability (to be studied)
2522 Monitor Metric Object
2523 Mean Monitor Metric Object
2524 Algorithm Indicating Mean Monitor Metric 6.3.8 Manufacturing Messaging
Object
2525 Moving Average Mean Monitor Metric Object AMM Manufacturing Messaging
2526 Mean and Variance Monitor Metric Object
2527 Mean and Percentile Monitor Metric Object ab Substructure 15
2528 Mean and Min Max Monitor Metric Object
1 GENERAL APPLICATIONS
253 Summarization Objects 11 MMS General Application Base Profile 16
2531 General Summarization Capability
2 ROBOT CONTROLLER APPLICATIONS
2532 Simple Scanner Object
21 ROBOT CONTROLLER APPLICATION BASE PROFILE 16
2533 Dynamic Simple Scanner Object
2534 Heterogeneous Scanner Object 3 NUMERICAL CONTROLLER APPLICATIONS
2535 Buffered Scanner Object 31 NUMERICAL CONTROLLER APPLICATION BASE PROFILE 16
2536 Mean Scanner Object
2537 Mean Variance Scanner Object 4 PROGRAMMABLE LOGIC CONTROLLER APPLICATIONS
2538 Percentile Scanner Object
5 PROCESS INDUSTRIES APPLICATIONS
2539 Min Max Scanner Object

3 MANAGEMENT ENSEMBLE PROFILES

31 Lower Layer Systems and Network Management 6.3.9 Library and Documentation
Ensemble
311 Lower Layer Systems and Network ALD Library, Documentation
Management Ensemble for TA/RA/RD Profiles
312 Lower Layer Systems and Network ab Substructure 17
Management Ensemble for 1 SEARCH AND RETRIEVE (SR)
TB/TC/TD/TE/RB/RC Profiles 11 ACSE

2 INTERLIBRARY LOAN (ILL)

6.3.6 Transaction Processing 21 ACSE
22 Store-and-Forward (IPMS) 18
ATP Transaction Processing
15 Further refinement of the substructure, beneath this level, to increase the
ab Substructure granularity of the profile classification, is for further study.
16 This taxonomy entry has been added, based on a contribution from ISO/TC
1 APPLICATION SUPPORTED TRANSACTIONS 18/SC 5/WG 2, which seems to reflect a significant level of approval, although
it has not been formallly approved and is therefore included provisionally.
11 Polarized Control 17 Further refinement of the substructure, beneath this level is for further
12 Shared Control study.
18 This A-profile is intended to be used "over" AMH2x profiles.
This combination of A-profiles is an extension of the concept of A-profiles,
which also has been reflected in section 5.5.3.1.

19
ISO/IEC TR 10000-2:1998(E) © ISO/IEC

6.3.10 Document Filing and Retrieval abc Substructure 19

02 Enhanced Document Structure

ADF Document Filing and Retrieval
026 Character, Raster Graphics and Geometric
Graphics content architecture
ab Substructure
03 Extended document structure
ADF Document Filing and Retrieval
036 Character, Raster Graphics and Geometric
1 Common Filing and Retrieval Graphics content architecture
11 Read-Only
1 IMAGE APPLICATIONS
12 Archiving
11 Simple Document Structure
13 Document Store Manipulation
112 Raster Graphics content architecture only
2 REMOTE STORE MANAGEMENT 12 Enhanced Document Structure
21 Simple Management 126 Character, Raster Graphics and Geometric
22 Full Management Graphics content architecture

6.3.11 Interactive Manipulation of ODA

Documents 6.4.2 Computer Graphics Metafile
Interchange Format
AOD Interactive Manipulation of ODA Documents
FCG Computer Graphics Metafile Interchange Format
ab Substructure
ab Substructure
1 DTAM-BASED PROFILES
11 DTAM / Read-only 11 BASIC SCIENTIFIC AND TECHNICAL GRAPHICS
12 DTAM / Insert (BST)
13 DTAM / Manipulation 23 ADVANCED SCIENTIFIC AND TECHNICAL GRAPHICS
(AST)
2 RESERVED FOR OTHER SERVICES AND PROTOCOLS
32 BASIC PRESENTATION AND VISUALIZATION
(BPV)
6.4 Interchange Format and 33 ADVANCED PRESENTATION AND VISUALIZATION
Representation Profiles (APV)

The particular classification of the F-profiles in the context of OSE

is for further study. For historical reasons these profiles are 6.4.3 SGML Interchange Format
considered OSI profiles.
FSG SGML Document Interchange Format
For historical reasons ISPs exist which use profile identifiers
without a suffix. These ISPs and profile identifiers remain valid. ab Substructure
New ISPs and profile identifiers containing Interchange Format
and Representation profiles will include the appropriate suffix. For (to be studied)
existing ISPs the suffix will be added when revisions or
maintenance occurs.
6.4.4 Directory Data Definitions
6.4.1 Open Document Format
6.4.4.1 Edition 1988
FOD Open Document Format
FDI Directory Data Definitions
abc Substructure 19

0 DOCUMENT PROCESSING APPLICATIONS ab Substructure

01 Simple Document Structure
011 Character content architecture only 1 COMMON DIRECTORY USE

11 Normal

19 The FOD Taxonomy has been changed from two to three levels of
2 MHS USE OF THE DIRECTORY
subdivision.
Since the currently defined profiles (FOD11, FOD26, FOD36) are all intended 3 FTAM USE OF THE DIRECTORY
for document processing applications, they will be referred to as FOD011,
FOD026, FOD036.

20
© ISO/IEC ISO/IEC TR 10000-2:1998(E)

ab Substructure abc Substructure

4 TP USE OF THE DIRECTORY 214 Unsequenced Terminal

41 Basic Naming and Addressing 215 Application RIO Record Loading
42 TPSU characteristics 216 Terminal RIO Record Notification
43 Application characteristics 217 Horizontal Tabulation
218 Logical Image
5 VT USE OF THE DIRECTORY 219 Status Message
2 1 10 Entry Control
6 EDI USE OF THE DIRECTORY
2 1 11 Waiting Time
2 1 12 Printer
2 1 13 Field Definition Management
6.4.4.2 Edition 1993
2 1 14 Terminal Signal Titles
2 1 15 Form Help Text
FDY Directory Data Definitions
2 1 16 Generalized Telnet Synch
2 1 17 Generalized Telnet Signal
ab Substructure
2 1 18 Generalized Telnet Negotiation
1 SCHEMA 2 1 19 Generalized Telnet Subnegotiation
11 Common Directory Use
22 Field Entry Instruction Control Object (FEICO) 20
12 Directory System Schema
221 Forms FEICO No.1
2 MHS USE OF THE DIRECTORY 222 Paged FEICO No.1

3 FTAM USE OF THE DIRECTORY 23 Field Entry Pilot Control Object (FEPCO) 20
231 Forms FEPCO No.1
4 TP USE OF THE DIRECTORY 232 Paged FEPCO No.1
41 Basic Naming and Addressing
42 TPSU characteristics 24 Reference Information Object (RIO) 20
43 Application characteristics
25 Termination Conditions Control Objects (TCCO)
5 VT USE OF THE DIRECTORY 251 TCCO No.1

6 EDI USE OF THE DIRECTORY 3 BASIC CLASS ASSIGNMENT TYPES

31 Repertoire 20
311 Repertoire Assignment Type for ISO/IEC 10646
6.4.5 Virtual Terminal Environment 312 Repertoire Assignment Type for ISO/IEC 2022
Level 2
FVT Virtual Terminal Registered Objects 32 Font
321 Font Assignment Type No.1
abc Substructure 322 Font Assignment Type No.2
33 Colour 20
1 BASIC CLASS VTE-PROFILES
11 A-mode
111 Telnet 6.4.6 Character Sets
112 Scroll
113 ITU-T X.3 PAD Interworking FCS Character Set Profiles
114 Transparent
115 Generalized Telnet abc Substructure 21

12 S-mode 1 CODE STRUCTURES

121 Forms 11 ISO/IEC 2022 Code Structure
122 Paged 111 2022 Option 1
123 Enhanced Forms 12 ISO/IEC 10646 Code Structure
124 Enhanced Paged 121 10646 Option 1
2 BASIC CLASS CONTROL OBJECTS
21 Miscellaneous
211 Sequenced Application 20 Entries in this classification are subject to registration.
212 Unsequenced Application 21 This taxonomy entry has been added, based on a contribution (SGFS
N1149), which reflects a significant level of approval, although it has not been
213 Sequenced Terminal
formallly approved and is therefore included provisionally.

21
ISO/IEC TR 10000-2:1998(E) © ISO/IEC

7 Conformance of OSI Profiles Conformance Statement (Profile ICS) and the Profile
Requirements List (Profile RL). These requirements have to be
The general principles of Conformance requirements of OSI addressed in the Conformance-section of an OSI profile.
profiles are outlined in ISO/IEC TR 10000-1.
For each profile, a Profile Test Specification (PTS) should be
The detailed Conformance requirements of OSI profiles are provided, either as part of the ISP which defines a profile, or as a
defined in the ITU-T Rec. X.296 | ISO/IEC 9646-7, which define free-standing ISP, with an explicit reference to it from the profile
the requirements related to the Profile Implementation definition. The details of the PTS are defined in ITU-T Rec. X.295 |
ISO/IEC 9646-6.

22
© ISO/IEC ISO/IEC TR 10000-2:1998(E)

Annex A

Bibliography

SGFS Standing Document SD-4. 22 Directory of ISPs and Profiles contained therein.

22 Updated and published regularly by the SGFS Secretariat as an ISO/IEC JTC 1 SGFS N-numbered document.

23
ISO/IEC TR 10000-2:1998(E) © ISO/IEC

ICS 35.100.05
Price based on 23 pages