ISO/IEC TR 10000-2:1995

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

General Information

• Status: Withdrawn
• Publication Date: 26-Dec-1995
• Withdrawal Date: 26-Dec-1995
• ICS: 35.100.05 - Multilayer applications
• Technical Committee: ISO/IEC JTC 1 - Information technology
• Drafting Committee: ISO/IEC JTC 1 - Information technology
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 29-Oct-1998
• Completion Date: 30-Oct-2025

Relations

• Revises: ISO/IEC TR 10000-2:1994 - Information technology - Framework and taxonomy of International Standardized Profiles - Part 2: Principles and Taxonomy for OSI Profiles
• Effective Date: 15-Apr-2008
• Revised: ISO/IEC TR 10000-2:1998 - Information technology - Framework and taxonomy of International Standardized Profiles - Part 2: Principles and Taxonomy for OSI Profiles
• Effective Date: 15-Apr-2008

Standards Content (Sample)

TECHNICAL ISOAEC
REPORT
TR 10000-2
Fourth edition
1995-1 2-1 5
Information technology - Framework and
taxonomy of International Standardized
Profiles -
Part 2:
Principles and Taxonomy for OS1 profiles
Technologies de l’information - Cadre et taxonomie des profils
normalisés internationaux -
Partie 2: Principes et taxonomie pour profils OS1
Reference number
ISO/IEC/TR 10000-2:1995(E)
ISO/IEC TR 10000-2: 1995 (E)
Contents
Page
Foreword . IV
Introduction . v
1 . Scope I
...........................................................................................................................................
2 . References . I
3 . Definition . I
4 . Abbreviations . 2
4.1 . General abbreviations. . . . 2
4.2 . Abbreviations used in Profile identifiers .
5 . The OS1 Taxonomy: Principles .
5.1 . General . . . .
5.2 . The Class concept for OS1 Profiles .
5.3 . Relationship between OS1 Profiles .
5.3.1
....... A/T and B/U Boundaries.. ............................................................................................................................. .4
....... A/F and BE Boundaries.. ...............................................................
5.3.2
..................................... 5
5.4 . The Group concept for OS1 Lower Layer Profiles . 5
5.5 . Profile classes. . . 5
....... Transport P
5.5.1 . 5
5.5.1.1 . Princip1 .
5.5.1.2 . Transport Profile Identifier
......................................................................... 6
5.5.1.3 . Connec .
5.5.1.4 . Connect
5.5.1.5 . Inte
5.5.1.6 . Introduction to the Taxonomy of Subnetwork Profiles . . 8
5.5.1.6.2 . Digital Data Circuit .
5.5.1.6.6 . Frame Relay Data Networks .
.......................................................................................................... .......................... 9
5 52.1 . Principles
5.5.2.2 . Relay Profile Identifier., . .
................... 10
......................................
5.5.3.2 . Common Upper Layer Requirements .
................................. .........................................
5.5.3.3 . Application Profile Identifier
.............................. 11
.... .Directo
5.5.3.4.3
5.5.3.4.4 . Virtual
0 ISOAEC 1995
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
microfilm, without permission in writing from the publisher.
ISO/IEC Copyright Office Case Postale 56 CH-1 21 1 Genève Switzerland
Printed in Switzerland
ii
O ISO/IEC ISOAEC TR 10000-2 : 1995 (E)
5.5.3.4.6 . Transaction Processing . 12
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 . 13
5.5.3.4.1 1 . Interactive Manipulation of ODA Documents . 14
5.5.4 . Interchange Format and Representation Profiles . 14
5.5.4.1 . Principles . 14
5.5.4.2 . Interchange Format and Representation Profile Identifier . 14
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 . 15
5.5.4.3.3 . SGML Interchange Format . 15
5.5.4.3.4 . Directory Data Definitions . 15
5.5.4.3.5 . Virtual Terminal Environment . 15
5.5.4.3.6 . Character Sets . 16
5.5.4.3.7 . Medical Image Interchange . 16
6 . Taxonomy of Profiles . 17
6.1 . Transport Profiles . 17
6.1.1 . Taxonomy of Subnetworks . 17
6.1.2 . Transport Groups . 18
6.2 . Relay Profiles . 18
6.2.1 . Relaying the Network Internal Layer Service, as defined in ISOEC 10028 . 18
6.2.2 . Network Layer Protocol Relaying . . 19
6.2.3 . Relaying the MAC Service . 19
6.2.4 . CO/CL Interworking . 19
6.3 . Application Profiles . 19
6.3.1 . File Transfer, Access and Management . 19
6.3.2 . Message Handling . . 19
....... Directory ...................................................................................................................................................... 20
6.3.3
6.3.3.1 . Edition 1988 . 20
6.3.3.2 . Edition 1993 . 20
....... Virtual Terminal .......................................................................................................... ............................ 20
6.3.4
6.3.5 . OS1 Management . 20
6.3.6 . Transaction Processing . 21
6.3.7 . Remote Database Access . 21
6.3.8 . Manufacturing Messaging . 21
Library and Documentation . 22
Document Filing and Retrieval . . 22
6.3.1 1 . Interactive Manipulation of ODA Documents . . 22
6.4 . Interchange Format and Representation Profiles . 22
6.4.1 . Open Document Format . . 22
6.4.2 . Computer Graphics Metafile Interchange Format . 22
6.4.3 . SGML Interchange Format . 22
6.4.4 . Directory Data Definitions . 23
6.4.4.1 . Edition 1988 . . 23
6.4.4.2 . Edition 1993 . 23
6.4.5 . Virtual Terminal Environment . 23
6.4.6 . Medical Image Interchange . 24
6.4.7 . Character Sets . 24
7 . Conformance of OS1 Profiles . 25
Annex A . 26
Bibliography . 26
iii
ISOllEC TR 10000-2: 1995 (E)
O ISOAEC
Foreword
IS0 (the International Organization for Standardization) and IEC (the International
Electrotechnical Commission) form the specialized system for worldwide stan-
dardization. National bodies that are members of IS0 or IEC participate in the
development of International Standards through technical committees estab-
lished by the respective organization to deal with particular fields of technical
activity. IS0 and IEC technical committees collaborate in fields of mutual
interest. Other international organizations, governmental and non-governmental,
in liaison with IS0 and IEC, also take part in the work.
In the field of information technology, IS0 and IEC have established a joint
technical committee, ISO/IEC JTC 1.
The main task of technical committees is to prepare International Standards. 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 Stan-
dards. 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 fourth edition cancels and replaces the third edition (ISO/IEC
TR 10000-2:1994), which has been technically revised.
ISO/IEC TR 10000 consists of the following parts, under the general title Infor-
- Framework and taxonomy of International Standardized
mation technology
Profiles:
-
Part 1: General principles and documentation framework
-
Part 2: Principles and Taxonomy for OS1 profiles

ISOIIEC TR 10000-2 : 1995 (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,
conform an ce tests.
Registration mechanisms, which provide the means to specify
detailed parameterization within the framework of the base standards
or profiles.
Within ISOAEC 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 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 lSPs and Profiles contained therein". This is a factual record of
which lSPs exist, or are in preparation, together with an executive summary
of each profile. It is subject to regular updating by the Secretariat of
ISOAEC JTC l/SGFS.
V
TECHNICAL REPORT O ISO/IEC ISO/IEC TR 10000-2: 1995 (E)
Information technology - Framework and taxonomy of
International Standardized Profiles -
Part 2:
Principles and Taxonomy for OS1 profiles
1 Scope
submitted to SGFS, it will also provide additional infor-
The purpose of this part of ISOAEC TR 10000 is to
mation, including the status of the identified profiles.
provide principles and a classification scheme for OS1
profiles which may be or have been submitted for
2 References
ratification as International Standardized Profiles
(ISPs).
The following standards contain provisions which,
ISOAEC TR 10000-1 defines the concept of profiles through reference in this text, constitute provisions of
which are documented in ISPs. OS1 profiles are a this part of ISOAEC TR 10000. At the time of
subset of OSE profiles. ISO/IEC TR 10000-3 defines publication, the editions indicated were valid. All
the concept of OSE profiles and, along with standards are subject to revision, and parties to
agreements based on this part of iSO/iEC TR 10000
ISOAEC TR 10000-1, gives guidance to organizations
making proposals for Draft ISPs, on the nature and are encouraged to investigate the possibility of
content of the documents they are producing. applying the most recent editions of the standards
indicated below. Members of IEC and IS0 maintain
The existence of a profile classification in this part of registers of currently valid International Standards.
ISOAEC TR 10000 does not reflect a judgment by
ISO/IEC JTC l/SGFS that a profile is required for ISO/IEC 9646-6 : 1994, lnformation technology -
such capability. It merely provides a capability to iden- Open Systems lnterconnection - Conformance testing
methodology and framework - Part 6: Protocol profile
tify uniquely such a function and to enable evaluation
of P D I SPs. test specification. [ ITU-T Rec. X.295 (1 995)]
Since profiles will be proposed according to needs ISOAEC 9646-7 : 1995, Information technology -
identified to SGFS and according to the progress of Open Systems lnterconnection - Conformance testing
international base standardization, the Taxonomy will methodology and framework - Part 7: Implementation
be periodically updated or have new parts added in or- Conformance Statements. [ ITU-T Rec. X.296 (1 995)]
der to reflect the progress reached. It is also
recognized that there will be proposals for the exten- ISOAEC TR 10000-1 : 1 995, Information technology -
sion of the Taxonomy to cover functions which were Framework and taxonomy of International Stand-
not identified during preparation of this edition of ardized Profiles - Part 1: General principles and
ISOAEC TR 10000. These extensions may be documentation framework.
identified by a variety of proposers and involve simple
extensions to the existing Taxonomy or the addition of ISO/I EC TR 10000-3 : 1 995, Information technology -
new functional areas not currently covered by Framework and taxonomy of International Stand-
ISOAEC TR 10000. The inclusion of such extensions ardized Profiles - Part 3: Principles and Taxonomy for
is administered following the procedures elaborated
Open System Environment profiles.
by SGFS.
A number of other ISO, IEC, and ISOAEC JTC1
A distinction has been made between a profile and an
Standards and ITU-T Recommendations are quoted in
ISP documenting one or more profiles. The Taxonomy do not constitute provisions of this
examples which
is only concerned with profiles, but further information
part of ISOAEC TR 10000.
is given in the "Directory of lSPs and Profiles
contained therein" as to which ISP contains the
3 Definition
documentation of a profile.
For the purposes of this part of ISOAEC TR 10000,
This Directory is maintained as an SGFS standing do-
the following definition applies.
cument SD-4 (see Annex A). For each draft profile
ISOllEC TR 10000-2: 1995 (E) Q ISOlIEC
SGFS ISO/IEC JTC l/Special Group on Functional
3.1 Group
Standardization
SGML Standardized General Markup Language
A set of OS1 profiles that are compatible, in the sense
TP Transaction Processing
that an IT implementing one profile from a Group can
TPSU TP Service User
interwork, according to OSI, with another IT system
UA User Agent
implementing a different profile from the same Group,
vc X.25 Virtual Call
in terms of the operation of the protocols specified
VT Virtual Terminal
within these profiles.
4.2 Abbreviations used in Profile
4 Abbreviations
identifiers
4.1 General abbreviations
Abbr. Profile sub-class (Amlications)
ADF Document Filing and Retrieval
CGM Computer Graphics Metafile
AD1 Directory (1988)
CL Connectionless-mode
ADY Directory (1993)
CLNS Connectionless-mode Network Service
AFT File Transfer, Access and Management
CLTS Connectionless-mode Transport Service
ALD Library, Documentation
CO Connection-mode
AMH Message Handling
CONS Connection-mode Network Service
AM I Medical Image Interchange
COTS Connection-mode Transport Service
AMM Manufacturing Messaging
CSDN Circuit Switched Data Network
AOD Interactive Manipulation of ODA Documents
CSI Communication Services Interface
Remote Database Access
ARD
CSMA/CD Carrier Sense, Multiple Access / Collision
ATP Transaction Processing
Detection
AVT Virtual Terminal
CULR Common Upper Layer Requirements
DFR Document Filing and Retrieval
Abbr. - Profile sub-class {Formats)
DSA Directory Service Agent
FCG Computer Graphics Metafile Interchange
DTAM-DM Document Transfer and Manipulation
Format
- Document Manipulation
Character Sets
FCS
DTE Data Terminal Equipment
Directory User Agent FDI Directory ùata Definitions (1988)
DUA
EDI Electronic Data Interchange
FDY Directory Data Definitions (1993) ’
EDI Messaging
EDIMG
Medical Image Interchange
FMI
FDDl Fibre Distributed Data Interface
FOD Open Document Format
FR PVC Frame Relay Permanent Virtual Circuit
FSG SGML Interchange Format
FR SVC Frame Relay Switched Virtual Call
FVT Virtual Terminal Registered Objects
FRBS Frame Relay Bearer Service
Frame Relay Data Network
FRDN
Profile sub-class JLower Lavers)
Abbr.
FRDTS Frame Relay Data Transmission Service
TA COTS over CLNS
Image Interchange Facility
IIF
COTS over CONS
TB
IPI Image Processing and Interchange
TC COTS over CONS
IPM Interpersonal Message
TD COTS over CONS
ISDN Integrated Services Digital Network
COTS over CONS
TE
ISP International Standardized Profile
UA CLTS over CLNS
Local Area Network
LAN
UB CLTS over CONS
MAC Media Access Control
Relaying the CLNS
RA
Manufacturing Message Specification
MMS
RB Relaying the CONS
MOTIS Message Oriented Text Interchange System
X.25 Protocol Relaying
RC
Message Store
MS
RD Relaying the MAC Service using transparent
MTA Message Transfer Agent
bridging
Message Transfer System
MTS
Relaying the MAC Service using source
RE
Open Document Architecture
ODA
routing
P1 Message Transfer Protocol
Relaying between CLNS and CONS
RZ
Interpersonal Messaging Protocol
P2
P3 MTS Access Protocol
MS Access Protocol
P7
PSDN Packet Switched Data Network
PSTN Public Switched Telephone Network
PVC X.25 Permanent Virtual Circuit 1 The laxonomy substructure for the 1988 edition of the Directory
specifications differs from the taxonomy substructure developed for the 1993
QOS Quality of Service
edllion.
Q ISO/IEC
ISO/IEC TR 10000-2 : 1995 (E)
Other classes may be required.
5 The OS1 Taxonomy: Principles
Transport profiles of classes T and U specify how the
5.1 General
two modes of OS1 Transport Service are provided
over the two modes of OS1 Network Service, and over
OS1 profiles are primarily arranged into classes, each
specific subnetwork types, such as individual types of
class representing a category of functionality of rea-
LANs, PSDNs, etc. In this way they isolate the
sonable independence from other classes. The
A/B-profiles and F-profiles from network technology.
different classes of profile correspond to the major
divisions of the taxonomy.
T- and U-profiles are further subdivided into Groups.
The Group concept for OS1 Lower Layer
See "5.4
Within each class, a class-specific subdivision will be
Profiles" for details.
used.
B specify com-
Application profiles of classes A and
OS1 profile identifiers are structured in accordance
munications protocol support for particular application
with the general OSE taxonomy defined in
types over the two modes of OS1 Transport Service,
ISO/IEC TR 10000-3. Thus, an OS1 profile identifier
respectively.
comprises:
F-profiles specify the characteristics and represen-
0 the suffix "-C" (for a CSI profile);
tation of various types of information interchanged by
A- and 6-profiles.
a root mnenomic which is a character string
commencing with one letter that indicates the
R-profiles specify Relay functionality needed to en-
primary class of the profile;
able IT systems using different T- or U-profiles to in-
terwork. lnterworking between T- and U-profiles is not
contemplated in any JTC 1 work.
0 an alphanumeric string that is as long as
necessary to reflect the position of the profile
Within each of these classes, sub-classes of profiles
within the hierarchic structure.
are identified which, again, may require further sub-
division such that the granularity of the Taxonomy
The syntax of all but the first letter is subject to
meets the requirements outlined in
individual definitions (see below).
ISO/IEC TR 10000-1. This leads to a hierarchical
NOTE - In the context of the general OSE taxonomy defined in
structure of profile (sub-)classes which is given in full
ISO/IEC TR 10000-3,OSI profiles are identified as
in clause "6 Taxonomy of Profiles".
Communication Services Interface profiles by the suffix "-CY.
This suffix is omitted in the description of the OS1 taxonomy in
this Dari of ISOllEC TR 10000.
For the identification of sub-classes and a further sub-
division within a given class, a class-dependent
5.2 The Class concept for OS1 Profiles
methodology is applied. This is explained in the sub-
sequent class-individual sections.
In order to decouple representation of information or
objects from communication protocols, and applica-
5.3 Relationship between OS1 Profiles
tion-related protocol from subnetwork types, OS1 and
OSI-related profiles are divided into the following
The schematic illustration in Figure 1 brings together
classes:
examples of the relationships which exist between
OS1 profiles, particularly the three main subdivisions
Transport profiles providing connection-mode
T -
of the Taxonomy, and the combinations which can be
Transport Service
made between profiles from different classes.
U - Transport profiles providing
connectionless-mode Transport Service
R - Relay profiles
A - Application profiles requiring connection-mode
Transport Service
B - Application profiles requiring connection-
less-mode Transport Service
F - Interchange format and representation profiles
ISO/IEC TR 10000-2: 1995 (E)
O ISO/IEC
represents the possibility of combining any pair of A-
5.3.1 A/T and B/U Boundaries
and T-profiles, one from each of the two classes.
Actual use of an A- or B-profile requires that an IT
A similar situation exists for the B- and U-profiles. The
system operate it in combination with a T- or
A/T boundaries correspond to the OS1 Connection-
U-profile, in order to provide a particular application
mode Transport Service, and the B/U-boundaries to
protocol over a particular subnetwork type. The
the OS1 Connectionless-mode Transport Service. The
separation of A- and B-profiles from T- and U-profiles
possibility of making the combination arises from the
is represented by an A/T or B/U boundary. This
fact that a T- or U-profile is specified to provide the
relationship is illustrated vertically in Figure 1. The
OS1 Transport Service and an A- or B-profile is
location of a set of A-profiles above a set of
specified to use the OS1 Transport Service.
T-profiles, separated by a common A/T boundary,
Fxxnn Fxxnn
F- Profiles
-
A- and B-
Profiles
Axxnn Bxxnn Bxxnn
............... :.: .............
jJ$y$ij$
;:;:;:;:;:;<:.:~:.::~.~~~.~~,.,
T- and U-
Profiles
UB2nn
.......................
NOTE - This figure illustrates logical structuring possibilities, not the interrelatlonships of specific identified profiles.
Figure 1 - Examples of relationships between profiles in the OS1 taxonomy
O ISOAEC
ISOAEC TR 10000-2 : 1995 (E)
5.3.2 A/F and B/F Boundaries
The Group concept for OS1 Lower
5.4
Layer Prof iles
The combination of an A- or B-profile with one or
more F-profiles will be selected by the user to meet
The Group concept is used in the Taxonomy as
the functional requirements in each case. The various
fol I ows:
general possibilities are illustrated by the vertical
relationships in Figure 1. The location of one or more
A Group is a set of T- or U-profiles that are compa-
F-profiles above one or more A-/B-profiles, represents
tible in the sense that an IT system implementing one
the possibility of combining profiles from each class.
profile from the Group and another IT system imple-
menting a profile from the same Group can be ex-
Unlike the A/T and B/U boundaries, the A/F and B/F
pected to interwork, according to OSI, to some mini-
boundaries are not characterised by a single service
mum level which is determined by the mandatory
definition.
features of the profiles in the Group.
The Application Layer base standards require,
lnterworking according to OS1 means end-to-end
implicitly or explicitly, the structure of information
operation across a single subnetwork, or across mul-
carried or referenced by them to be specified for each
tiple subnetworks linked by means of Network (or
instance of communication. The combination of
lower) Layer relays.
A-/B-profiles with one or more F-profiles will be
selected by the user to meet the functional
An example of a Group is the set of T-profiles that
requirements in each case. However, the choice may
provide the Connection-mode Transport Service,
be subject to constraints which can be expressed
using Class4 Transport Protocol over the Connec-
within either A-/B-profiles, F-profiles, or both.
tionless-mode Network Service, provided by ITU-T
Rec. X.233 I ISOAEC 8473-1. This Group has
In other A-/B-profiles, the Application Layer base
members which correspond to different subnetwork
standards themselves constrain the choice of
technologies but interworking between IT systems
presentation context.
conforming to them is made possible by LAN bridges
and/or Network Layer relays.
Constraints may also exist within an F-profile, arising
either from its base standard, or as a result of profile
A Group is identified by labels of the form YXnnn,
creation. These constraints will limit the A-/B-profiles
where Y is the class identifier and X is a letter
which can be used to transfer the information.
identifying the Group.
In summary, therefore, there are three forms of
constraints affecting the combination of A-/B- and
5.5 Profile classes
F-profiles:
5.5.1 Transport Profiles
the choice of information to be transferred may
a)
be constrained by the Application Layer base
5.5.1 .l Principles
standards, and possibly further constrained by
the A-/B-profile;
Transport profiles define the use of protocol standards
b) some interchange and representation base from OS1 layers 1 to 4, to provide the OS1 Transport
standards may limit transfer to particular Service.
Application base standards; this choice may be
further constrained by the F-profiles; A primary distinction is made between Transport
profiles, based on the mode of Transport Service
the combinations are not constrained by base offered:
c)
standards, but may be constrained by either
A-/B- or F-profiles to achieve some general - Connection-mode Transport Service:
function.
profile class T
Note that, as always, in making his choice of
- Connectionless-mode Transport Service:
combination, a user must in practice take account not
profile class U
only of the constraints derived from profiles, but also
the capabilities implemented in the end systems
For the Transport profile classification within each
involved in each instance of communication, to
class, the following methodology is applied:
support the various profiles.
As a first level distinction the Group concept
a)
(see “5.4 The Group concept for OS1 Lower
Layer Profiles“) is used in the following way:
ISOAEC TR 10000-2: 1995 (E) O ISOAEC
A lower layer Group is a collection of profiles 5.5.1.3 Connection-mode Transport Service:
which:
profile class T
0 support the same combination of modes of Based on functional standardization already under
way in organizations represented in SGFS and on
Transport and Network Service;
standards already developed, the following lower
layer Groups are identified as being of value. They
0 support the same Transport Protocol
are characterized as follows:
Class(es);
a) Connection-mode Transport Service over
The notion of a Group is incorporated in the
Connectionless-mode Network Service:
classification.
Group TA
The second level distinction between profiles,
b)
i.e. within a Group, is made according to the
The Connection-mode Transport Service (COTS) is
subnetwork type supported
provided over the Connectionless-mode Network
(see “6.1 .I Taxonomy of Subnetworks“ for
Service (CLNS) by requiring the use of the Class4
examples of subnetwork types).
Transport Protocol as defined in ITU-T Rec. X.224 I
Further subdivisions are made according to the
ISOAEC 8073.
c)
characteristics of a particular subnetwork, e.g.,
NOTE - An IT system implementing a profile from Group TA and claim-
switched versus leased line
ing conformance to ITU-T Rec. X.224 I ISOAEC 8073 also has
(see 6.1.1 for examples of such characte-
to implement the mandatory transport protocol classes for
ristics). operation over CONS as required by ITU-T Rec. X.224 I
ISO/IEC 8073.
5.5.1.2 Transport Profile Identifier
b) Connection-mode Transport Service over
Connection-mode Network Service
The identifier for a profile in the lower layers is of the
form:
The Connection-mode Transport Service (COTS) is
provided over the Connection-mode Network Service
YXabcde
(CONS).
where:
Profiles of this characteristic are further grouped ac-
cording to their required support of Transport Protocol
Y = class designator, indicating the Transport
class(es):
Service mode:
mandatory (see note 1)
T for Connection-mode
transport protocol classes
U for Connectionless-mode
O and 2 and 4 (see note 2)
Group TB:
X = one letter indicating the lower-layer Group
O and 2 (see note 2)
Group TC:
within the class, as defined in “5.5.1.3
GroupTD: O
Connection-mode Transport Service:
Group TE: 2 (see note 3)
profile class T“ and “5.5.1.4
Connectionless-mode Transport Service:
NOTES
‘Mandatory‘ means those Transport Protocol classes made
Profile class U“ below. 1
mandatory by the base standard, ISOAEC 8073, plus any class
required for Group membership
abcde = the structured numerical identifier indicating
The class negotiation rules to be employed are those in ITU-T
the subnetwork type supported in this profile.
Recommendation X.224.
It is possible that a further level of identifier
may become necessary. In general, when 3 An IT system implementing a profile from Group TE and
claiming conformance to ITU-T Recommendation X.224 also
referencing a profile, only that level of
has to implement transport protocol class O.
identifier which is necessary for uniqueness
needs to be used.
5.5.1.4 Connectionless-mode Transport
Service: Profile class U
The identifier structure is not meant to cap-
ture the variety of details and options of OS1
a) Connectionless-mode Transport Service over
layer I such as attachment speeds and
Connectionless-mode Network Service:
connectors. However, it is recognized that
this issue must be covered by the appro-
Group UA
priate profile specification.
O ISO/IEC
ISO/IEC TR 10000-2 : I995 (E)
No interworking is possible between Groups in class T
The Connectionless-mode Transport Service (CLTS
and U because of the different mode of Transport
Service provided.
is provided using the ITU-T Rec. X.234
I
ISO/IEC 8602 Connectionless-mode Transport
Entries in the tables have the following meaning:
Protocol. This Group supports the mandatory
operation of the ITU-T Rec. X.234 1 ISO/IEC 8602,
Full: Full OS1 interworking (an OS1 relay
over Connectionless-mode Network Service.
may be required (see "6.2 Relay
Prof i I es"))
b) Connectionless-mode Transport Service over
Connection-mode Network Service:
Restricted: Interworking capabilities are restricted
in the sense that the choice of Trans-
Group U6
port Protocol classes may be restricted
by the static capability of the respond-
The Connectionless-mode Transport Service (CLTS
er. Successful interworking is depen-
is provided using the ITU-T Rec. X.234
dent on the satisfactory outcome of
ISO/IEC 8602 Connectionless-mode Transport
class negotiation.
Protocol. This Group supports the option of the ITU-T
Rec. X.234 I ISO/IEC8602 that operates over
Special: Non-OS1 relay required for interworking
Connection-mode Network Service.
(see also "5.5.2.1 Principles")
NOTE - An IT system implementing a profile from Group U6 and
Special 1 : Special restrictions for interworking
claiming conformance to the ITU-T Rec. X.234 I ISO/IEC 8602
also has to implement the mandatory operation over CLNS as exist
required by the ITU-T Rec. X.234 I ISOIIEC 8602.
(see "6.2.4 CO/CL Interworking").
5.5.1.5 Interworking between Transport Profile
Interworking between these profile
Special 2:
Groups
types is not contemplated in any
JTC 1 work.
The following tables 1 and 2 show the interworking
capabilities between profiles. Table 1 shows the in-
NOTE - Successful interworking depends not only on the satisfactory
outcome of the transport protocol class negotiation but also on
terworking between profiles in profile class T, and
dynamic responses during transport initiation. Such dynamic
table 2 shows the interworking among profiles in
responses can include, amongst others, responder reactions to
the offered Quality of Service (QOS) or to the specific options
profile class U. Successful establishment of a Trans-
requested by the initiator.
port Connection is dependent upon successful nego-
tiation of parameters, some of which are not consider-
ed in the following tables.
Table 1 - Interworking amongst Groups in class T
Network Initiator in Group
Responder In
Group Service mode TA TB TC TD TE
CL full special 1 special 1 special 1 special 1
TA
CO special 1 lull full full full
TB
full
TC CO special 1 restricted full full
CO special 1 restricted restricted full special 2
TO
special 2 full
TE CO special 1 restricted restricted
ISOllEC TR 10000-2: 1995 (E)
Q ISO/IEC
Table 2 - Interworking amongst Groups in class U
Responder in Initiator in Group
Group UA UB
I
I I
I full I special 2 II
soacial 2 llill
5.5.1.6 Introduction to the Taxonomy of
PSDN, the third digit of the subnetwork identifier
denotes the type of network used to gain access to
Subnetwork Profiles
the PSDN. Currently defined networks for gaining
access to the PSDN are a PSTN line, a CSDN line,
Subnetwork types are characterized by a structured
an ISDN B-channel, and a FRDN.
numerical identifier. The first digit of the numerical
identifier classifies the major subnetwork type being
Except for the more complicated case of a FRDN
used for system interconnection while the subsequent
access, the fourth digit of the PSDN subnetwork
digits represent a subdivision of the subnetwork type,
taxonomy identifier indicates whether the X.25 logical
indicating how use is made of the subnetwork type, or
channel operates on a Virtual Call or a Permanent
describing how the subnetwork is accessed. The
Virtual Circuit. In the case of switched access to the
major subnetwork types, as identified by the first digit
PSDN, only Virtual Call operation is possible.
of the subnetwork identifier, are the following:
In the case of FRDN access to a PSDN, the fourth
1 Packet Switched Data Network (PSDN)
digit of the subnetwork identifier indicates that a
2 Digital Data Circuit
Frame Relay Permanent Virtual Circuit (FR PVC) is
3 Analogue Telephone Circuit
used while a fifth digit indicates that the PSDN is used
4 Integrated Services Digital Network (ISDN)
to provide for X.25 DTE operation.
5 Local Area Network (LAN)
6 Frame Relay Data Network (FRDN)
Place holders have been left in the PSDN subnetwork
taxonomy to allow for future specification of access to
The number of ways in which subnetworks may be
the PSDN through other means, e.g. through an ISDN
implemented and used is potentially very large. There
D-channel or H-channel, or through various
are also cases where one subnetwork type is used to
combinations of a Frame Relay service operating
access another subnetwork type which has a higher
over ISDN.
network functionality. For example, an ISDN or a
FRDN may be used to access a PSDN which offers a
5.5.1.6.2 Digital Data Circuit
higher functionality. The subnetwork taxonomy needs
to reflect such combinations which are defined by ITU
A Digital Data Circuit is typically an X.21 based
recommendations and offered by public network
service offering although other interfaces are
service providers.
conceivable, e.g. ITU-T Rec. G.703 based service
offerings. The taxonomy currently makes no
Other subnetwork variations have been deemed to
distinction on this point which is left to actual profile
be, in practice, less important to the goal of end
definitions.
system interoperability, e.g. some electrical and
physical interfaces that are prerequisites to
The second digit of the subnetwork taxonomy
subnetwork connection establishment but transparent
identifier determines whether the circuit is established
to data exchange. Therefore, aspects such as line
permanently (leased service) or established by circuit-
speed, connector type, or modem type have, in
switching (dial-up). There is no further subdivision of
general, not been reflected in the subnetwork
the Digital Data Circuit subnetwork taxonomy
taxonomy. Such requirements may be included in
identifier.
actual ISPs, if considered important, or this area may
be left as a local matter for system installation.
5.5.1.6.1 Packet Switched Data Network
The second digit of the subnetwork taxonomy
identifier makes the overall distinction as to whether
the access to the PSDN is permanent or switched.
For each of these two major types of access to the
...