ISO/IEC TR 10000-2:1992

TECHNICAL ISO/IEC
REPORT
TR 10000-2
Second edition
1992-1 2-1 5
Information technology - Framework and
taxonomy of International Standardized
Profiles -
Part 2:
Taxonomy of OS1 Profiles
Technologies de l’information - Cadre et taxonomie des profils
internationaux normalisés -
Partie 2: Taxonomie

---------------------- Page: 1 ----------------------
ISOllEC TR 10000-2: 1992 (E)
Contents Page
..............................
................................ ...............................
.....................................
2 .
..... Normative references ....................
..........................
4 . Abbreviations . .
................ ...........................
4.2 . Abbreviations used in Profile identifiers
5. The Taxonomy: Principles .
5.1 . General . . .
............................... 3
........................
........................
.........................
.......................
............... ........................... ..................... ............................. 6
5.5 Profile classes
........................ ........................
........................
....................
.......................
.......................
.................... .........................
................
...................
....................
..................... .................
.................
...................
....................... ....................
....................
.................... ..................
5.5.3.1 . Principles .
......................
...............
0 ISO/IEC 1992
All rights reserved. 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 per-
mission in writing from the publisher.
ISO/IEC Copyright Office Case Postale 56 CH-1 21 1 Genève 20 Switzerland
Printed in Switzerland
ii

---------------------- Page: 2 ----------------------
ISOIIEC TR 10000-2 : 1992 (E)
O ISOllEC
............... <..,.......... 9
......................................
........................... 10
......., <.<...,................. 10
.... <......<.............. 11
..................................................
5.5.4.3.3 . SGML Interchange Format.
5.5.4.3.4 . Directory Data Definitions .
......................................
5.5.4.3.5 . Virtual Terminal Environment
..................................... <. 12
....................................... 14
......... <..<...........<..,..,.,....<........,,....
...................................... 15
................................................... 15
.................................................... 16
...................................... 16
..................................................
...................................... 18
Bibliography of other referenced documents
iii

---------------------- Page: 3 ----------------------
ISOIIEC TR 10000-2: 1992 (E) O ISOIIEC
Foreword
IS0 (the International Organization for Standardization) and IEC (the Inter-
national Electrotechnical Commission) form the specialized system for
worldwide standardization. National bodies that are members of IS0 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. IS0 and IEC technical commit-
tees collaborate in fields of mutual interest. Other international organiza-
tions, 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 Stan-
dards, but in exceptional circumstances a technical committee may pro-
pose the publication of a Technical Report of one of the following types:
- type 1, when the required support cannot be obtained for the publica-
tion 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 Interna-
tional 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 second edition cancels and replaces the first edition (ISO/IEC
TR 10000-2: 1990), 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: Framework
- Part 2: Taxonomy of OS/ Profiles
Annex A of this part of ISO/IEC TR 10000 is for information only.
IV

---------------------- Page: 4 ----------------------
O ISOIIEC ISOIIEC TR 10000-2 : 1992 (E)
Introduction
The context of Functional Standardization is one part of the overall field of Information
Technology standardization activities covering
a
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.
0
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.
0 Registration mechanisms, which provide the means to specify detailed
parameterization within the framework of the base standards or Profiles.
Within ISOIIEC 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.
In addition to ISOIIEC 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 ISOIIEC JTC I/SGFS.
V

---------------------- Page: 5 ----------------------
TECHNICAL REPORT O ISO/IEC ISO/IEC TR 10000-2 : 1992 (E)
Information technology - Framework and taxonomy of
International Standardized Profiles
Part 2:
Taxonomy of OS1 Profiles
This Directory is maintained as an SGFS standing document
1 Scope
SD-4 (see Annex A). For each draft Profile submitted to SGFS, it
will also provide additional information, including the status of the
The purpose of this part of ISOlIEC TR 10000 is to provide a
identified Profiles.
classification for Profiles which may be or have been submitted
for ratification as International Standardized Profiles (ISPs).
2 Normative references
0 ISOAEC TR 10000-1 defines the concept of Profiles, as
documented in ISPs, and gives guidance to organizations making The following standards contain provisions which, through
proposals for Draft ISPs, on the nature and content of the docu- of this part of
reference in this text, constitute provisions
ments they are producing. ISOllEC TR 10000, At the time of publication, the editions
indicated were valid. All standards are subject to revision, and
ISOAEC TR 10000 is intended to be applied to Profiles in the parties to agreements based on this part of ISO/IEC TR 10000
area of competence of JTC 1, and within this, priority
are encouraged to investigate the possibility of applying the most
consideration has been given to Profiles in the OS1 area, i.e. recent editions of the standards listed below. Members of IEC
those which specify OS1 base standards, and those which are ex- and IS0 maintain registers of currently valid International Stand-
pected to be used in conjunction with them. Nevertheless, it is
ards.
also applicable to Profiles specifying the use of other JTC 1 and
CCITT base standards. ISOllEC 8073 : 1992, lnformation technology -
Telecommunications and information exchange between systems
The existence of a Profile classification in this part of - Open Systems lnterconnection - Protocol for providing the
ISOlIEC TR 10000 does not reflect a judgement by connection-mode transport service.
ISOllEC JTC I/SGFS that a Profile is required for such capabi-
lity. It merely provides a capability to identify uniquely such a ISOllEC 8473 : 1988, lnformation processing systems - Data
function and to enable evaluation of PDISPs. communications - Protocol for providing the connectionless-mode
network service.
0 Since Profiles will be proposed according to needs identified to
SGFS and according to the progress of international base ISOllEC 8602 : 1987, lnformationprocessing systems - Open
standardization, the Taxonomy will be periodically updated or Systems lnterconnection - Protocol for providing the
have new parts added in order to reflect the progress reached. It connectionless-mode fransport service.
is also recognized that there will be proposals for the extension of
ISO/IEC 9506 : 1 990, Industrial automation systems - Manufxturing
the Taxonomy to cover functions which were not identified during
preparation of this edition of ISOllEC TR 10000. These
Messaging Spification.
extensions may be identified by a variety of proposers and
involve simple extensions to the existing Taxonomy or the ISOlIEC TR 10000-1 : 1992, lnformation technology - Framework
addition of new functional areas not currently covered by
and taxonomy of lnterna tional standardized Profiles Part 1:
ISO/IEC TR 10000. The inclusion of such extensions is admi- Frame work.
nistered following the procedures elaborated by SGFS.
ISOilEC 10021 : 1990, lnformation technology - Texf
A distinction has been made between a Profile and an ISP
Communication - Message Oriented Text lnterchange Systems
documenting one or more Profiles. The Taxonomy is only
(MO TIS).
concerned with Profiles, but further information is given in the
"Directory of lSPs and Profiles contained therein" as to which ISP
ISOlIEC 10028 : 1992, lnformafion technology -
contains the documentation of a Profile.
Telecommunications and information exchange between systems
- Definition of the relaying functions of a Network Layer
intermediate system.
1

---------------------- Page: 6 ----------------------
ISOliEC TR 10000-2: 1992 (E) O ISOllEC
CLTS Connectionless-mode Transport Service
ISOllEC TR 10029 : 1989, lnformation technology -
Telecommunications and informa tion exchange between systems CO Connection-mode
CONS Connection-mode Network Service
- Operation of an X.25 interworking unit.
COTS Connection-mode Transpori Service
ISOllEC TR 101 72 : 1991, lnformation technology - CSDN Circuit Switched Data Network
CSMNCD Carrier Sense, Multiple Access / Collision Detection
Telecommunications and information exchange between systems
Common Upper Layer Requirements
CULR
- NetworWTransport Protocol interworking specification.
Directory Service Agent
DSA
Data Terminal Equipment
DTE
CClTT Q.931 (1988), Digital Subscriber Signalling System No. f
Directory User Agent
DUA
[DSS I), Network Layer, User-Network Management,
Electronic Data Interchange
EDI
EDI Messaging
EDlM
CCITT X.3 (1 988), Packet AssernblylDassembly Facility [PAD) in
FDDl Fibre Distributed Data lnterface
a Public Data Network.
IPM Interpersonal Message
Integrated Services Digital Network
ISDN
CClTT X.25 (1988), lnterface Between Data Terminal fquipmenf
International Standardized Profile
ISP
[DE) and Data Circuit-Terminating Equipment (DCf) for
Local Area Network
LAN
Terminals Operating in the Packet Mode and Connected to Public
Media Access Control
MAC
Data Networks by Dedicated Circuit.
Manufacturing Message Specification
MMS
Message Oriented Text Interchange System
MOTIS
CCITT X.224 (1 988), Transporf Protocol Specification for Open
MS Message Store
Systems lnterconnection for CClTT Applications.
MTA Message Transfer Agent
Message Transfer System
MTS
CClTT Recommendations X400-X.420 (1984), Message
ODA Open Document Architecture
Handling Systems.
PI Message Transfer Protocol
P2 Interpersonal Messaging Protocol
CClTT Recommendations X.400-X.420 (1988), Message
P3 MTS Access Protocol
Handling Systems.
P7 MS Access Protocol
Packet Switched Data Network
PSDN
CCITT X.435 (1991) Message Handling Systems, fDI Messaging
Public Switched Telephonie Network
PSTN
System.
Permanent Virtual Circuit
PVC
Quality of Service
QOS
SGFS ISOllEC JTC l/Special Group on Functional
3 Definitions
Standardization
Standardized General Markup Language
SGML
For the purposes of this part of ISOllEC TR 10000, the
Transaction Processing
TP
following definitions apply:
UA User Agent
vc Virtual Call
Group: A set of OS1 Profiles that are compatible, in the
VT Virtual Terminal
sense that a system implementing one Profile from a
Group can interwork, according to OSI, with another
4.2 . Abbreviations used in Profile identifiers
system implementing a different Profile from the same
Group, in terms of the operation of the protocols specified
m Profile sub-class
within these Profiles.
AD1 Directory
AFT File Transfer, Access and Management
4 Abbreviations
Library, Documentation
ALD
AMH Message Handling
4.1 General abbreviations
AMM Manufacturing Messaging
AOM OS1 Management
CL Connectionless-mode
ARD Remote Database Access
CLNS Connectionless-mode Network Service
ATP Transaction Processing
AVT Virtual Terminal

---------------------- Page: 7 ----------------------
ISOllEC TR 10000-2 : 1992 (E)
O ISOllEC
&& Profile sub-class A - Application Profiles requiring connection-mode Transport
Service
FCG Computer Graphics Metafile Interchange Format
I Directory Data Definitions
FD
FOD Open Document Format B - Application Profiles requiring connectionless-mode
Transport Service
FSG SGML Interchange Format
FVT Virtual Terminal Registered Objects
F - Interchange format and representation Profiles
Other classes may be required.
5 The Taxonomy: Principles
Transport Profiles of classes T and U specify how the two modes
5.1 General
of OS1 Transport Service are provided over the two modes of OS1
Network Service, and over specific subnetwork types, such as in-
Profiles are primarily arranged into classes, each class
dividual types of LANs, PSDNs, etc. In this way they isolate the
representing a category of functionality of reasonable
NB-Profiles and F-Profiles from network technology.
independence from other classes. The different classes of profile
correspond to the major divisions of the taxonomy.
T- and U-Profiles are further subdivided into Groups. See 5.4 for
ISOAEC TR 10000-1 provides some further information about the
details.
principles used in this primary classification.
Application Profiles of classes A and B specify communications
Within each class, a class-specific subdivision will be used.
protocol support for particular application types over the two
modes of OS1 Transport Service, respectively.
Profile identifiers have been introduced such that each Profile is
identified by a character string commencing with one letter (indi-
F-Profiles specify the characteristics and representation of
cating the primary class of the Profile), and continuing with as
various types of information interchanged by A- and B-Profiles.
many further letters or digits as are necessary to reflect its
position within the hierarchic structure of the class. The syntax of
R-Profiles specify Relay functionality needed to enable systems
all but the first letter is subject to individual definitions for each
using different T- or U-Profiles to interwork. lnterworking between
class (see below).
T- and U-Profiles is not contemplated in any JTC 1 work.
5.2 The Class concept for OS1 Profiles
Within each of these classes, sub-classes of Profiles are
identified which, again, may require further subdivision such that
In order to decouple representation of information or objects from
the granularity of the Taxonomy meets the requirements outlined
communication protocols, and application-related protocol from
in ISOilEC TR 10000-1. This leads to a hierarchical structure of
subnetwork types, OS1 and OSI-related Profiles are divided into
Profile (sub-)classes which is given in full in clause 6.
the following classes:
For the identification of sub-classes and a further subdivision
Transport Profiles providing connection-mode Transport
T -
within a given class, a class-dependent methodology is applied.
Service
This is explained in the subsequent class-individual sections.
U - Transport Profiles providing connectionless-mode
Transport Service
R - Relay Profiles
3

---------------------- Page: 8 ----------------------
O ISOllEC
ISOllEC TR 10000-2: 1992 (E)
Fxxnn
Fxxnn
F- Profiles Fxxnn Fxxnn
-
A- and 6-
Bxxnn
Profiles Axxnn Bxxnn
AFTnn
iMHni
-
-
T- ad U-
Profiles
NOTE - Thls figure Illustrates logical structuring possibllffles, not the lnterrelatlonshlps of specific ldenîifled Profiles.
Figure 1: Examples of relationships beWeen Profiles in the OS1 Taxonomy

---------------------- Page: 9 ----------------------
O ISOllEC
ISOllEC TR 10000.2 : 1992 (E)
Constraints may also exist within an F-Profile, arising either from
5.3 Relationship between OS1 Profiles
its base standard, or as a result of Profile creation. These
constraints will limit the A-/B-Profiles which can be used to
The schematic illustration in Figure 1 brings together examples of
transfer the information.
the relationships which exist between OS1 Profiles, particularly
the three main subdivisions of the Taxonomy, and the
In summary, therefore, there are three forms of constraints
combinations which can be made between Profiles from different
affecting the combination of A-/B- and F-Profiles:
classes.
5.3.1 A/T and BIU Boundaries the choice of information to be transferred may be
a)
constrained by the Application Layer base standards, and
possibly further constrained by the A-/B-Profile;
Actual use of an A- or B-Profile requires that a system operate it
in combination with a T- or U-Profile, in order to provide a
some interchange and representation base standards
particular application protocol over a particular subnetwork type.
b)
may limit transfer to particular Application base
The separation of A- and B-Profiles from T- and U-Profiles is
standards; this choice may be further constrained by the
represented by an AIT or B/U boundary. This relationship is
F-Profiles;
illustrated vertically in Figure 1. The location of a set of A-Profiles
above a set of T-Profiles, separated by a common AIT boundary,
the combinations are not constrained by base standards,
represents the possibility of combining any pair of A- and T-
c)
but may be constrained by either A4B- or F-Profiles to
Profiles, one from each of the two classes.
achieve some general function.
A similar situation exists for the B- and U-Profiles. The AIT
Note that, as always, in making his choice of combination, a user
boundaries correspond to the OS1 Connection-mode Transport
must in practice take account not only of the constraints derived
Service, and the B/U boundaries to the OS1 Connectionless-
from Profiles, but also the capabilities implemented in the end
mode Transport Service. The possibility of making the
systems involved in each instance of communication, to support
combination arises from the fact that a T- or U-Profile is specified
the various Profiles.
to provide the OS1 Transport Service and an A- or B-Profile is
specified to use the OS1 Transport Service.
5.4 The Group concept for OS1 Lower Layer
5.3.2 AiF and BIF Boundaries
Profiles
The combination of an A- or B-Profile with one or more F-Profiles
will be selected by the user to meet the functional requirements in
The Group concept is used in the Taxonomy as follows:
each case. The various general possibilities are illustrated by the
vertical relationsships in Figure 1. The location of one or more F-
A Group is a set of T- or U-Profiles that are compatible in the
Profiles above one or more A-/B-Profiles, represents the
sense that a system implementing one Profile from the Group
possibility of combining Profiles from each class.
and another system implementing a Profile from the same Group
can be expected to interwork, according to OSI, to some mini-
Unlike the A/T and B/U boundaries, the NF and B/F boundaries
mum level which is determined by the mandatory features of the
are not characterised by a single service definition.
Profiles in the Group.
The Application Layer base standards require, implicitly or
lnterworking according to OS1 means end-to-end operation
explicitly, the structure of information carried or referenced by
across a single subnetwork, or across multiple subnetworks
them to be specified for each instance of communication. The
linked by means of Network (or lower) Layer relays.
combination of A-/B-Profiles with one or more F-Profiles will be
selected by the user to meet the functional requirements in each
An example of a Group is the set of T-Profiles that provide the
case. However, the choice may be subject to constraints which
Connection-mode Transport Service, using Class 4 Transport
can be expressed within either A-/B-Profiles, F-Profiles, or both.
Protocol over the Connectionless-mode Network Service, pro-
vided by ISOllEC 8473. This Group has members which
In other A-IB-Profiles, the Application Layer base standards
correspond to different subnetwork technologies but interworking
themselves constrain the choice of presentation context.
between systems conforming to them is made possible by LAN
bridges and/or Network Layer relays.
5

---------------------- Page: 10 ----------------------
ISOllEC TR 10000-2: 1992 (E)
O ISO/IEC
A Group is identified by labels of the form YXnnn, where Y is the YXabcde
class identifier and X is a letter identifying the Group.
where:
Y = class designator, indicating the Transport Service mode:
5.5 Profile classes
T for Connection-mode
5.5.1 Transport Profiles
U for Connectionless-mode
5.5.1.1 Principles
X = one letter indicating the lower-layer Group within the
class, as defined in 5.5.1.3 and 5.5.1.4 below.
Transport Profiles define the use of protocol standards from OS1
layers 1 to 4, to provide the OS1 Transport Service.
abcde = the structured numerical identifier indicating the
subnetwork type supported in this Profile. It is
A primary distinction is made between Transport Profiles, based
possible that a further level of identifier may become
on the mode of Transport Service offered:
necessary. In general, when referencing a Profile,
only that level of identifier which is necessary for
- Connection-mode Transport Service:
uniqueness needs to be used.
Profile class T
The identifier structure is not meant to capture the
- Connectionless-mode Transport Service:
variety of details and options of OS1 layer 1 such as
Profile class U
attachment speeds and connectors. However, it is re-
cognized that this issue must be covered by the ap-
For the Transport Profile classification within each class, the
propriate Profile specification.
following methodology is applied:
5.5.1.3 Connection-mode Transport Service: Profile
a) As a first level distinction the Group concept (see 5.4) is
class T
used in the following way:
Based on functional standardization already under way in organi-
A lower layer Group is a collection of Profiles which:
zations represented in SGFS and on standards already
developed, the following lower layer Groups are identified as be-
0 support the same combination of modes of Transport
ing of value. They are characterized as follows:
and Network Service;
a) Connection-mode Transport Service over
0 support the same Transport Protocol Class(es);
Connectionless-mode Network Service:
The notion of a Group is incorporated in the
Group TA
classification.
The Connection-mode Transport Service (COTS) is provided over
Thescond level distinction between Profiles, i.e. within
b)
the Connectionless-mode Network Service (CLNS) by requiring
a Group, is made according to the subnetwork type
the use of the Class 4 Transport Protocol as defined in
supported.
ISOilEC 8073.
(See 6.1.1 for examples of subnetwork types).
A system implementing Group TA and claiming conformance to ISO/IEC 8073
NOTE -
c) Further subd ivisions are made according to the
also has to implement the mandatory lranspori prolocol classes for operation
over CONS as required by ISOllEC 8073
characteristics of a particular subnetwork, e.g., switched
versus leased line.
b) Connection-mode Transport Service over
(See 6.1 .I for examples of such Characteristics).
Connection-mode Network Service
5.5.1.2 Transport Profile identifier
The Connection-mode Transport Service (COTS) is provided over
the Connection-mode Network Service (CONS).
The identifier for a Profile in the lower layers is of the form:
6

---------------------- Page: 11 ----------------------
O ISO/IEC ISOllEC TR 10000-2 : 1992 (E)
NOTE - A system implementing Group UB and claiming conformance Io ISOAEC 8602
Profiles of this characteristic are further grouped according to
also has to implement the mandatory operation over CLNS as required by
their required support of Transport Protocol ciass(es):
ISOIIEC 8602
mandatory (see note 1) 5.5.1.5 Interworking between Transport Profile Groups
transport protocol classes
The following tables 1 and 2 show the interworking capabilities
between Profiles. Table 1 shows the interworking between
Group TB: O and 2 and 4 (see note 2)
Profiles in Profile class T, and table 2 shows the interworking
Group TC: O and 2 (see note 2)
among Profiles in Profile class U. Successful establishment of a
Group TD: O
Transport Connection is dependent upon successful negotiation
Group TE: 2 (see note 3)
of parameters, some of which are not considered in the following
NOTES
tables.
1 'Mandatory' means those Transport Protocol classes made mandatory by the
base standard, ISO/IEC 6073, plus any class required for Group membership
No interworking is possible between Groups in class T and U
2 The class negotiation rules to be employed are those in CClTT
because of the different mode of Transport Service provided.
Recommendation X 224
A system implementing Group TE and claiming conformance to CCln Entries in the tables have the following meaning:
3
Recommendation X 224 also has to implement transport protocol class O
Full OS1 interworking (an OS1 relay may be
Full:
5.5.1.4 Connectionless-mode Transport Service: Profile
required (see 6.2))
class U
Restricted: lnterworking capabilities are restricted in the
a) Connectionless-mode Transport Service over
sense that the choice of Transport Protocol
Connectionless-mode Network Service:
classes may be restricted by the static
capability of the responder. Successful inter-
working is dependent on the satisfactory out-
come of class negotiation.
The Connectionless-mode Transport Service (CLTS) is provided
using the ISO/IEC 8602 Connectionless-mode Transport
Non-OS1 relay required for interworking (see
Special:
Protocol. This Group supports the mandatory operation of
also 5.5.2.1)
ISOllEC 8602, over Connectionless-mode Network Service.
Special restrictions for interworking exist (see
Special 1 :
b) Connectionless-mode Transport Service over
6.2.4).
Connection-mode Network Service:
Special 2: Interworking between these Profile types is
Group UB
not contemplated in any JTC 1 work.
0 The Connectionless-mode Transport Service (CLTS) is provided
Successful interworking depends not only on the satisfactory outcome of the
NOTE -
using the ISOilEC 8602 Connectionless-mode Transport transport protocol class negotiation but also on dynamic responses dunng
transport Initiation Such dynamic responses can include, amongst others, re-
Protocol. This Group supports the option of ISOllEC 8602 that
çponder reactions to the offered Quality of Service (COS) or to the specific
operates over Connection-mode Network Service.
options requested by the initiator
7

---------------------- Page: 12 ----------------------
O ISOllEC
ISOllEC TR 10000-2: 1992 (E)
Table 1 - Interworking amongst Groups in class T
Table 2 - Interworking amongst Groups in class U
Inihatot in Group
UA full lal 2
UB tal 2 full
Introduction to the Taxonomy of Subnetwork No relays exist between different Profiles of different Transport
5.5.1.6
Profile classes (T, U).
Profiles
5.5.1.6.1 Packet Switched Data Network Relays may operate at various layers up to layer 4. However,
relays operating at layer 4 are not OS1 relays and hence some
restrictions or limitations may be expected in their operation.
...