EN ISP 10609-10:1996

SLOVENSKI STANDARD
01-december-1997
Information technology - International Standardized Profiles TB, TC, TD and TE -
Connection-mode Transport Service over connection-mode Network Service - Part
10: LAN subnetwork-dependent, media-independent requirements (ISO/IEC ISP
10609-10:1994)
Information technology - International Standardized Profiles TB, TC, TD and TE -
Connection-mode Transport Service over connection-mode Network Service - Part 10:
LAN subnetwork-dependent, media-independent requirements (ISO/IEC ISP 10609-
10:1994)
Technologie de l'information - Profils normalisés internationaux TB, TC, TD et TE -
Service de transport en mode connexion sur service de réseau en mode connexion -
Partie 10: Prescriptions dépendantes du sous-réseau du RLE, indépendantes des
supports (ISO/IEC ISP 10609-10:1994)
Ta slovenski standard je istoveten z: EN ISP 10609-10:1996
ICS:
35.100.05 9HþVORMQHXSRUDEQLãNH Multilayer applications
UHãLWYH
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

INTERNATIONAL
ISO/IEC
STANDARDIZED
ISP
PROFILE
106094 0
First edition
1994-12-15
Information technology - International
Standardized Profiles TB, TC, TD and
TE - Connection-mode Transport Service
over connection-mode Network Service -
Part 10:
LAN subnetwork-dependent,
media-independent requirements
Technologi ’es de I ’information
- Profils normalk& internatjonaux TB, TC,
TD et TE - Service de transport en mode connexion sur Service de
r&eau en mode connexion -
Partie 7 0: Prescrjp tions dkpendantes du sous-rbeau du RL E,
independantes des supports
Reference number
ISO/IEC ISP 10609-10:1994(E)
ISO/IEC ISP 10609-10: 1994(E)
Page
Contents
iv
Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .“.
vi
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 Normative references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Requirements .
5.1 Introduction .
......................................... 3
5.2 Static conformance requirements
....................................... 5
5.3 Dynamit conformance requirements
......................................... 10
Annex A ISPICS requirements list (normative)
.......................................................
A.l Introduction
..............................................
A.2 Notation and conventions
...............................................
A.3 IPRL for ISO/IEC 8208
.................................................
A.4 IPRL for ISO 8802-2
.... 16
Annex B Assumed base Standard PICS proforma for ISO 8802-2 Logical Link Control (normative)
.......................................................
B.l Introduction
.......................................
B.2 Abbreviations and special Symbols
............................... 18
B.3 Instructions for completing the PICS proforma
.......................................... 21
B.4 PICS proforma - Identification
................................................... 23
B.5 Major capabilities
................... 24
B.6 LLC Type 1 Operation - Unacknowledged connectionless-mode
.................................. 30
B.7 LLC Type 2 Operation - Connection-mode
..................... 35
B.8 LLC Type 3 Operation - Acknowledged connectionless-mode
............................................. 42
B.9 Route Determination Entity
............................................ 43
Annex C Recommendations (informative)
.......................................................
C.1 Introduction
......................................... 43
C.2 ISO/IEC 8208 recommendations
........................................... 43
C.3 ISO 8802-2 recommendations
................................................
Annex D Bibliography (informative)
................................................
D. 1 Informative references
OISO/IEC 1994
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any
form or by any means, electronie or mechanical, including photocopying and microfilm, without Permission in
writing from the publisher.
l CH-1211 Geneve l Switzerland
ISO/IEC Copyright Office l Case postale 56
Printed in Switzerland
ii
0 ISO/IEC ISO/IEC ISP 10609=10:1994(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission)
together form a System for worldwide standardization as a whole. 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-govemmental,
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.
In addition to developing International Standards, ISO/IEC JTC 1 has created a Special Group on Functional
Standardization (ISO/IEC JTC l/SGFS) for the processing of International Standardized Profiles.
An International Standardized Profile is an intemationally agreed, harmonized document which identifies a
Standard or group of Standards, together with Options and Parameters, necessary to accomplish a function or set
of functions.
Draft International Standardized Profiles are circulated to national bodies for voting. Publication as
the national
International Standardized Profile requires approval by at least 75% of bodies casting a vote.
S-liaison may be established with JTC l/SGFS by specialized organizations involved in the work of functional
standardization. This part of ISO/IEC ISP 10614 was prepared with the collaboration of the following S-liaisons:
- Asia-Oceania Workshop (AOW);
- European Workshop for Open Systems (EWOS);
- Open Systems Environment Tmplementors’ Workshop (OIW).
ISO/IEC ISP 10609 consists of several parts, under the general title Information technology - International
Standardized Profiles TB, TC, TD and TE - Connection-mode Transport Service over connection-mode Network
Service:
Part 1: Subnetwork-type independent requirements for Group TB
Part 2: Subnetwork-type independent requirements for Group TC
Part 3: Subnetwork-type independent requirements for Group TD
Part 4: Subnetwork-type independent requirements for Group TE
- Part 5: Definition of profiles TH 111 iTBll21
- Part 6: Definition of profiles TC1 11 l/TCl121
- Part 7: Definition of profiles TDI 111 lTDl.121
*
-
Part 8: Dejinition of profiles TE1 111 lTEl121
.
- Part 9 . * Subnetwork-type dependent requirements for Network Layer, Data Link Layer and Physical
Layer concerning permanent access to a packet switched data network using virtual calls
. . .
ISO/IEC ISP 10609- 10: 1994(E) 0 ISO/IEC
Part IO: LAN subnetwork-dependent, media-independent requirements
- Part 11: CSMAICD LAN subnetwork-dependent, media-dependent requirements
-
Part 12: Definition of Profile TC51, Provision of the OS1 connection-mode Transport Service using
the 0% connection-mode Network Service in an End System attached to a CSMAICD LAN
- Part 14: Definition of Profile TC53, Provision of the OSI connection-rnode Transport Service using
the OS/ connection-mo& Network Service in an End System attached to a Token Ring LAN
This part of ISO/IEC ISP 10609 contains four annexes. Annexes A and B are normative, annexes C and D are
informative.
iv
0 ISO/IEC ISO/IEC ISP 10609=10:1994(E)
Introduction
This International Standardized Profile (ISP) is defined in accordance with the principles specified by ISO/IEC
Technical Report 10000, “Information technology - Framework and taxonomy of International Standardized
Profiles ”.
The context of Functional Standardization is one area in the Overall field of Information Technology (IT)
standardization activities, covering base Standards, profiles, and registration mechanisms. A Profile defines a
combination of base Standards that collectively perform a specific weh-defined IT function. Profiles standardize
the use of Options and other variations in the base Standards, and provide a base for the development of uniform,
internationally recognized System tests.
ISPs are produced not simply to “legitimize” a particular choice of base Standards and Options, but to promote
real System interoperability. One of the most important roles for an ISP is to serve as the basis for the
development (by organizations other than ISO and IEC) of intemationally recognized test methods. The
development and widespread acceptance of tests based on this and other ISPs is crucial to the successful
realization of this goal.
ISO/IEC ISP 10609 consists of several parts, of which this is part 10. Parts 1 to 4 of ISO/IEC ISP 10609 specify
Profile requirements that are subnetwork-independent, for each of the transport groups TB, TC, TD and TE,
respectively. There are further parts which specify subnetwork-dependent and media-dependent requirements. In
addition, for each individual Profile there is a part of ISO/IEC ISP 10609 which identifies the specific
requirements of that Profile, making reference to appropriate material from the relevant subnetwork-independent
and subnetwork-dependent Parts.

ISO/IEC ISP 10609-10: 1994(E) 0 ISO/IEC
This page is intentionally left blank.

INTERNATIONAL STANDARDIZED PROFILE OISO/IEC
ISOIIEC HP 10609-10:1994(E)
International Standardized
Information technology -
Profiles TB, TC, TD and TE - Connection-mode Transport
Service over connection-mode Network Service -
Part 10:
LAN subnetwork-dependent, media-independent requirements
1 Scope
This International Standardized Profile is applicable to end Systems concerned with operating in the Open Systems
Interconnection (OSI) environment. It specifies a combination of OS1 Standards, which collectively provide the
connection-mode Transport Service using the connection-mode Network Service.
This part of ISO/IEC ISP 10609 specifies subnetwork-type dependent requirements applicable to an end System
attached to a local area network (LAN) subnetwork and using the ISO 8802-2 LLC type 2 protocol, irrespective
of the LAN medium.
2 Normative references
The following documents contain provisions which, through reference in this text, constitute provisions of this
part of ISO/IEC ISP 10609. At the time of publication, the editions indicated were valid. All documents are
subject to revision, and Parties to agreements based on this part of ISO/IEC ISP 10609 arc wamed against
automatically applying any more recent editions of the documents listed below, since the nature of references
made by ISPs to such documents is that they may be specific to a particular edition. Members of IEC and ISO
maintain registers of currently valid International Standards and ISPs, and ITU-T maintains published editions
of its current Recommendations.
Data communications - X.25 Packet Layer Protocol for Data
ISO/IEC 8208 : 1990, Information technology -
Terminal Equipment
ISO/IEC 8208 : 1990/Amd.3 : 1991, Information technology - Data communications - X.25 Packet Layer Protocol
for Data Terminal Equipment - Amendment 3: Conformance requirements
ISO/IEC 8208 : 199O/Amd.3 : 1991/Cor.l : 1993, Information technology - Data communications - X.25 Packet
Layer Protocol for Data Terminal Equipment - Amendment 3: Conformance requirements - TECHNICAL
CORRKENDUM 1
ISO/IEC 8348 : 1993, Information technology - Open Systems Interconnection - Network Service Definition
ISWIEC ISP 10609-10: 1994(E) 0 ISO/IEC
ISO 8802-2 : 1989, Ir3formation processing Systems - Local area networks - Part 2: Logical link control
Information processing Systems - Local area networks - Part 2: Logical link
ISO 8802-2 : 1989/Amd.l : - ‘),
control - Amendment 1: Flow control techniques for bridged local area networks
ISO 8802-2 : 1989/Amd.2 : - ‘), Information processing Systems - Local area networks - Part 2: Logical link
control - Amendment 2: Acknowledged connectionless-mode Service and protocol - Type 3 Operation
Information processing Systems - Local area networks - Part 2: Logical link
ISO 8802-2 : 1989/Amd.3 : - *),
control - Amendment 3: Conformance requirements
Local area networks - Part 2: Logical link
ISO 8802-2 : 1989lAmd.4 : - ‘), Information processing Systems -
control - Amendment 4: Editorial changes and technical corrections
Information processing Systems - Local area networks - Part 2: Logical link
ISO 8802-2 : 1989/AmdS : - ‘),
control - Amendment 5: Bridged LAN Source routeing Operation by end Systems
: 1992, Information technology - Telecommunications and information exchange between
ISO/IEC 8878
Use of X.25 to provi& the OH Connection-mode Network Service
systems -
ISO/IEC 8881 : 1989, Ir$ormation processing Systems - Data communications - Use of the X.25 packet level
protocol in iocal area networks
Data communications - Use of the X.25
ISO/IEC 8881 : 1989/Cor. 1 : 199 1, Information processing Systems -
TECHNICAL CORRIGENDUM 1
packet level protocol in local area networks -
This Technical Conigendum to ISO/IEC 8881 is to apply throughout in this part of ISO/IEC ISP 10614, wherever
NOTE -
ISO/IEC 8881 itself is referenced.
ISo/IEC TR 1oooo-l : 1992, Injormation t&mology - Framework and taxonomy of International Standardized
Profiles - Part 1: Framework
ISO/IEC TR lOQOO-2 : 1992, Information technology - Framework and taxonomy of International Standardized
Profiles - Part 2: Taxonomy of 0% Profiles
3 Definitions
The terms used in this part of ISO/IEC ISP 10609 are defined in the referenced base Standards (See clause 2).
4 Abbreviations
Abbreviations used in this part of ISO/IEC ISP 10609 arc defined in the referenced base Standards (see clause
.
2)
1) To be published
ISO/IEC ISP 10609~10:1994(E)
0 ISO/IEC
5 Requirements
51 . Introduction
The requirements in this clause specify the subnetwork-type dependent, media-independent requirements for end
System Operation when the end System is attached to a local area network (LAN).
Static conformance requirements
52 .
52.1 Overall requirements
An implementation conforming to this part of ISO/IEC ISP 10609 shall:
meet the requirements for ISO/IEC 8878 in subclause 5.2.2 below;
a)
meet the requirements for ISO/IEC 8208, as modified for Operation over LLC type 2 in a LAN
b)
environment by ISO/IEC 8881, in subclause 5.2.3 below;
meet the requirements for ISO 8802-2 in subclause 5.2.4 below;
Cl
support all the features identified as requirements in the ISPICS requirements list in annex A.
5.2.2 ISOIIEC 8878
The implementation shall:
meet the requircments for the Provision of the OS1 Network Service as defined in ISO/IEC 8878
a)
excluding: the Receipt Confirmation Service (clause 9), the Expedited Data Transfer Service (clause
lO), and annex A;
be capable of using the Source and destination OS1 network addresses of any of the formats and values
b)
defined in ISO/IEC 8348.
ISO/IEC 8208
5.2.3
5.2.3.1 General requirements
The implementation shall:
meet the static conformance requirements specified in clause 21 of ISO/IEC 8208/Amd.3;
a)
implement the Virtual Cal1 Service;
b)
ISO/IEC ISP 10609-10: 1994(E) 0 ISO/IEC
implemcnt the following capabilities identified in Table 37 of ISO/IEC 8208/Amd.3:
C)
- Virtual Cal1 setup; initiating an outgoing VC, with subsequent acceptance or rejection, or receiving
an incoming VC and responding by acceptance, and receiving an incoming VC and responding
by rejec tion;
NOTE - An implementation may do one or the other or both.
- Aborting an outgoing VC attempt, by Clearing;
Clearing an established VC as initiator and as responder;
- Resetting a logical channel as responder;
impiement the following Options from subclause 21.1.2 of ISO/IEC 8208/Amd.3:
d)
support of transfer of User data in cal1 setup packets, for both transmission and reception;
- support of DATA packet transfer;
- support of DATA packets with M-bit set to 1 for reception;
- transmit updated window rotation information;
- transmit RR packets;
be capable of accepting incoming VCs as fast select calls;
e)
support the following optional facilities:
- Throughput Class Negotiation;
- Fast Select;
Fast Select Acceptance;
- Transit Delay Selection and Indication;
- Calling Address Extension;
- Called Address Extension;
- Minimum Throughput Class Negotiation;
- End-to-End Transit Delay Negotiation;
- Expedited Data Negotiation;
meet the requirements on network addresses in subclause 5.2.3.2 below.
g)
0 ISO/IEC ISO/IEC ISP 10609-10: 1994(E)
5.2.3.2 Network addresses
A System conforming to this part of ISO/IEC ISP 10609 shall be capable of using Source and destination OS1
network addresses of any of the formats and values defined in ISO/IEC 8348.
The calling, called and responding NSAP addresses shall be conveyed in their entirety, using the preferred bimry
encoding, in the facility Parameter field of the Called and Calling Address Extension Facility.
NOTE - If a conformant implementation receives an INCOMING CALL packet which does not conform to this
specification, it is recommended that a CLEAR REQUEST packet is transmitted, using Cause Code ‘DTE
Originated’ and either diagnostic code 235 or diagnostic Code 232.
5.2.4 ISO 8802-2
The implementation shall:
support the functions required by ISO 8802-2 for the support of the Logical Link Control Type 2
a)
protocol;
in Order to achieve intercommunication, agree the values of Nl and the Ack Timer on a LAN-wide
b)
support an Ack Timer value of 5 -t 1 seconds, and it is recommended that the Ack Timer
be
C)
configurable.
53 . Dynamit conformance requirements
53.1 Overall requirements
An implementation conforming to this part of ISO/IEC ISP 10609 shall:
meet the requirements for ISO/IEC 8208 in the subclause 5.3.2 below;
a)
meet the requirements for ISO 8802-2 in the subclause 5.3.3 below;
b)
behave in accordance with the requirements of the ISPICS requirements list in annex A.
C)
5.3.2 ISO/IEC 8208
5.3.2.1 General requirements
The implementation shall:
carry out the supported ISO/lEC 8208 functions in accordance with the procedures for the X.25 Packet
a>
Layer Protocol of ISO/IEC 8208, as modified for Operation over LLC type 2 in a LAN environment
by ISO/IEC 8881, sections 1 and 2;

ISO/IEC ISP 10609-10: 1994(E) 0 ISO/IEC
not make use of the procedures for the Operation of ISO/IEC 8208 over LLC type 1 defined in ISO/IEC
b)
8881, section 3, as they are prohibited by this International Standardized Profile;
This does not apply to the use of the ISO/IEC 10030 routeing protocol which tan make use of LLC
NOTE -
type 1 in a LAN environment.
meet the requirements on expedited data in subclause 5.3.2.2 below;
C)
meet the requirements on receipt confirmation in subclause 5.3.2.3 below;
d)
support the method for determining the range of logical channels detailed in subclause 5.3.2.4 below.
The implementation may:
ignore the X.25 PLP called-DTE and calling-DTE addresses as this part of ISO/IEC ISP 10609 does
a)
not require their use.
5.3.2.2 Expedited data
The expedited data Service is not supported.
The Expedited Data Negotiation (EDN) facility of ISO/IEC 8208 is used to negotiate non-use of expedited data
Service.
When a network layer entity receives an N-CONNECT request primitive from a Network Service User,
i)
the CALL REQUEST packet sent may contain the EDN facility set to ‘no use of expedited data’ or,
altematively, the EDN facility may be omitted which this implies ‘no-use’ of the facility;
ii) When a network layer entity receives an N-CONNECT response primitive from a Network Service
User, the CALL ACCEPTED packet sent may contain the EDN facility set to ‘no use of expedited data’
or, altematively, the EDN facility may be omitted which implies ‘no-use’ of the facility.
NOTES
1 If an implementation, operating according to this part of ISO/IEC ISP 10609, receives an INTERRUPT packet
during the data transfer Phase, it is recommended that the virtual cal1 is cleared using the CLEAR REQUEST
packet (and associated procedures defined in ISO/IEC 8208) using the Cause Code ‘DTE Originated’ and diagnostic
code 44.
2 When operating certain other profiles, for instance to support X.29 terminal access, then the support of Single octet
INTERRUPT packets will be required.
5.3.2.3 Receipt confirmation
The receipt confirmation Service is not supported.
Bit 7 of octet 1 (the D-bit) in the GF1 of ISO/IEC 8208 cal1 setup packets is used to negotiate the non-use of the
receipt confirmation Service.
CALL REQUEST packets sent by the DTE shall have the D-bit set to 0;
ISO/IEC ISP 10609-10:1994(E)
0 ISO/IEC
ii) When a network layer entity receives an N-CONNECT response primitive, the receipt confirmation
selection Parameter shall be set to ‘No use of Receipt Confirmation’ and consequently bit 7 of the GF1
in the CALL ACCEPTED packet is set to 0.
If a conformant implementation receives a DATA packet with the D-bit set to 1, it is recommended that the virtual
NOTE -
cal1 is cleared using the CLEAR REQUEST packet (and associated procedures defined in ISO/IEC 8208) using
the Cause Code ‘DTE Originated’ and either the diagnostic code 225 or diagnostic code 166.
5.3.2.4 Method for the determination of the range of logical channels
The logical channel ranges (LIC, HIC, LTC, HTC, LOC and HOC) to be used are determined by local
knowledge. If local knowledge is not available, then by default only a Single two-way logical channel will be
used (i.e. LTC and HTC will be set to 1, while LIC, HIC, LOC and HOC will be set to Zero). If more then one
channel is available, a higher value of HTC may be negotiated using the On-line Facility Registration facility.
If a DTE is capable of initiating a REGISTRATION REQUEST packet, then the registration Parameter fields
shall be set as follows:
The LIC, HIC, LOC and HOC Parameters shall be set to Zero. The LTC shall be set to the value 1. The
value in the total number of logical channels Parameter field shall be set equal to the value in the HTC
Parameter field;
ii) No other optional User facilities shall be identified in the REGISTRATION REQUEST packet, and may
be ignored by a responder if they are present;
If a DTE is capable of responding with a REGISTRATION CONFIRMATION packet, the maximum number
of two-way logical channels allowed between the two DTEs shall be indicated in the HTC Parameter field. The
value in the HTC Parameter field shall be less than or equal to the value requested in the HTC Parameter field
in the REGISTRATION REQUEST packet.
Registration of facilities normally applies in one direction only for the DTE/DTE case (i.e. registration of
facilities is performed independently for each direction), but for the logical channel range negotiation it applies
to both directions.
NOTE - A REGISTRATION REQUEST packet may be ignored by a responder. However, it is recommended that DTEs
are capable of responding with a REGISTRATION CONFIRMATION packet even if they support only a Single
two-way logical channel. This will prevent unnecessary delays for the initiator in transmitting a CALL REQUEST
packet. Such delays arc determined by the initiator ’s values for timer T28 and retry counter R28.
ISO 8802-2
53.3
5.3.3.1 General requirements
The implementation shall:
carry out the supported ISO 8802-2 functions in accordance with the procedures specified in ISO
a)
8802-2;
use the LLC actual address value of ’ 111 1110 ’. Table 1 illustrates the coding of the DSAP and the
b)
SSAP address fields;
ISO/IEC ISP 10609=10:1994(E)
0 ISO/IEC
Table 1 - LLC address values
DSAP address field SSAP address field
Field format I/G DDDDDDD c/R s s s s s s s
Value 0 1111110 c/R 1 1 1 1 1 10
if a value of k other than 7 is to be used, negotiate the value to be used by XID frames according to
C)
the procedures specified in subclause 5.3.3.2 below.
5.3.3.2 Use of XID
This part of ISO/IEC ISP 10609 does not require an implementation to transmit XID command frames, except
for the negotiation of values of k other than 7.
NOTE - ISO 8802-2 requires that the receipt of an XID command fkme is responded to with an XID response Erame.
An implementation receiving an XID command frame addressed to the individual actual address value specified
in subclause 5.3.3.1 (b) above is required to respond with an XID response frame using the individual actual
adclress. The implementation shall act as follows:
Take note of the initiator ’s receive window size. If the default value is in use this would be 7.
However, if the value is different the implementation shall not use a transmit window size greater than
the value indicated in the received XID command. If a transmit window size is used which is greater
than the receive window size, it tan lead to LLC connection resets. There is no requirement to actually
use the full window size indicated in the received XID command;
ii) The information field in the XID response should contain the responder ’s receive window size. The
default window size (specified in ISO/IEC 8881) is 7;
iii) The initiator receiving the XID response shall note and act on the receive window size as indicated in
(i) above.
An implementation receiving an XID command frame addressed to the null address shall respond with an XID
response frame using the null address in both the DSAP and SSAP fields. The implementation shall act as
follows:
The value of received window size shall be ignored;
It is recommended that the information field in the XID response should contain the value of the LLC
ii)
Types/Classes set to the value indicating ‘Class 11 LLC ’, and the receive window size set to ‘000 0000 ’.

ISO/IEC ISP 10609-10:1994(E)
0 ISO/rEC
NOTES -
The value for ‘Class 11 LLC’ is defined in ISO 8802-2 and is ‘11000 ’.
2 The receive window size in an XID frame associated with the null address has no meaning. Therefore, its
value must be ignored. Whilst any value could be used for this Geld, the value ‘000 0000’ is suggested.

ISO/IEC ISP 10609-10: 1994(E) 0 ISO/IEC
Annex A
(normative)
ISPICS requirements list
Al . Introduction
ISO/IEC TR 10000-1 identifies three items to be included in an ISPICS requirements list. These are:
general Options of the Profile;
list of standards selected in the Profile;
constraints on the allowable answers in the PICS proforma of each such Standard.
The first two items relate to the Profile as a whole, and so are included only in those parts of ISO/IEC ISP 10609
which are specific to individual profiles. However, each part of ISO/IEC ISP 10609 contains the identification
of those PICS proforma constraints which are within its scope.
ISO/IEC TI3 100004 indicates that an ISPICS proforma may consist either of a simple list of constraints or of
amended copies of the base Standard PICS proforma. ln this gart of ISO/IEC ISP 10609 the former method is
used.
Notation and conve-ntions
A.2
A.2.1 Intt-oduction
In many cases the constraints imposed by the IPRL are expressed in the form of Symbols indicating the Status,
in the context of this part of ISO/IEC 10609, of those base Standard PICS proforma items to which the constraints
apply. The Symbols used are defined in the following two subclauses.
A.2.2 Notation for static conformance
The following Symbols are used to identify constraints on the capabilities to be supported by a conforming
implementation:
Symbols directly specifying Status
a)
Symbol Meaninq
m mandatory
optional
prohibited
X
not applicable
out of scope, not relevant to this Profile
i
It should be noted that, in the context of received PDUs or fields or Parameters of received PDUs, the
capability to support them is the ability to interpret the significance of the PDU or field and act upon
0 ISO/IEC ISO/IEC ISP 10609-10: 1994(E)
it in accordance with the dynamic conformance requirements of the protocol (which may in some cases
mean generating an error report). PDUs or fields which are not supported are those whose receipt is
ignored and have no impact on the protocol Operation.
Other associated notation
W
Meaning
Symbol
condi tional (see below)
c
condi tional (sec below)
:cstatus>
Symbols of the form c are used when the Status of an item is dependent on the support of other
items. In this case, is a number which refers to a definition at the end of the subclause in which
it is used. That definition specifies the conditional Status which may, for example, be in a form such
as ‘if ABC then m else x ’, which would indicate that the Status is mandatory if the item in the PICS
proforma with reference ABC is supported, and otherwise prohibited.
Symbols of the form : arc used as an abbreviated way of expressing a condition wherein
the Status is as identified if the specified item is supported, and otherwise the Status is not applicable.
So, for example, ‘ABC:m’ would be equivalent to a conditional Status ‘if ABC then m else -‘.
Notation for dynamic conformance
A.2.3
In some cases it is necessary to specify constraints not only on the capabilities which are implemented, but on
whether they are used. When this is necessary the static conformance Status Symbol from subclause A.2.2 (a)
above is followed by an additional Symbol to create a two-Character Status definition. The second Symbol specifies
the dynamic constraints, and the meanings are as follows:
Symbol Meaning
m mandatory - the implementation is required to use the capability whenever
applicable
optional - use of the capability is optional
X prohibited - use of the capability is not permitted
not applicable
i outside the scope of this Profile
Thus, for example, a Status of ‘mm’ would mean that it is mandatory to provide the capability indicated by the
proforma item and that it is also mandatory to use that capability wherever applicable.
PICS
Where only a Single Status Character is used, it specifies the static requirement and indicates that no additional
constraint is placed upon the dynamic use of the capability.
A.2.4 Identification of PICS proforma items
PICS proforma items are identified by using the subclause number followed by a solidus followed by the item
reference of the relevant PICS proforma line. When identifying an item which is within the same subclause, the
subclause number and solidus at-e not necessari!y present.
ISO/IEC ISP 10609=10:1994(E) 0 ISO/IEC
A.3 IPRL for ISO/IEC 8208
The relevant base Standard PICS proforma is the PICS proforma given in annex C of ISO/IEC 8208/Amd.3. This
part of ISO/IEC ISP 10609 imposes the following additional constraints:
C5 . General DTE Characteristics
Constraint
Base Item Description
m
Virtual Cal1 Service
VS
X
EC/8 DTE/DCE (1988)
X
Ec/4 DTE/DCE (1984)
X
DTE/DCE (1980)
Ec/O
C.6.4.1 Cal1 Setup
Constraint
Description
Base Item
i
Non-Fast-Select cal1 request
Sic
m
Accept Fast-Select cal1
S2a
i
s2c Accept Non-Fast-Select cal1
C.6.4.2 Cal1 Clearing
Constraint
Description
Base Item
m
Cal1 clearing to abort outgoing VC
C2a
m
Cal1 clearing to reject incoming VC
C2b
m
Originating Clearing of established VC
c2c
b
t
Resetting of logical channels
C.6.5
Constraint
Description
Base Item
m
Resetting as responder
RSr
v
C.6.8.1 Sending data
Constraint
Description
Base Item
m
Sending DATA packets
DSl
m
Send-window rotation
DS2
m
Sending Q=O in DATA packets
DSSa
b
ISO/IEC ISP 10609-10: 1994(E)
0 ISO/IEC
C.6.8.2 Receiving data
Base Item Description Constraint
m
DR1 Receiving DATA packets
m
DR2 Receive-window rotation
Receive M=l in DATA packets m
DR4b
Receiving Q=O in DATA packets m
DRSa
C.8.1 .l Facilities sent in CALL REQUEST packets
Description Constraint
Base Item
FS2i Throughput Class Negotiation m
m
FS6a Fast Select
m
FS12 Transit Delay Selection and Indication
m
FS20i Facility Marker
m
FS2li Calling Address Extension
m
FS22i Called Address Extension
Minimum Throughput Class Negotiation m
FS23i
End-to-End Transit Delay Negotiation m
FS24i
Expedited Data Negotiation m
FS25i
C.8.1.2 Facilities sent in CALL ACCEPT packets
Description Constraint
Base Item
m
FS2r Throughput Class Negotiation
m
FS20r Facility Marker
Called Address Extension m
FS22r
End-to-End Transit Delay Negotiation m
FS24r
m
FS25r Expedited Data Negotiation
C.8.1.3 Facilities sent in CLEAR REQUEST packets
Constraint
Base Item Description
Facility Marker m
FS2Od
m
FS22d Called Address Extension
ISO/IEC ISP 10609=10:1994(E)
C.8.2.1 Facilities received in INCOMING CALL packets
Constraint
Base Item Description
m
FR2i Throughput Class Negotiation
m
FR6a Fast Select
FR12i Transit Delay Selection and Indication m
m
FR2Oi Facility Marker
m
FR21 Calling Address Extension
m
FR22i Called Address Extension
Minimum Throughput Class Negotiation m
FR23
FR24i End-to-End Transit Delay Negotiation m
m
FR25i Expedited Data Negotiation
C.8.2.2 Facilities received in CALL CONNECT packets
Base Item Description Constraint
m
FR2r Throughput Class Negotiation
m
FR12r Transit Delay Selection and Indication
m
FR20r Facility Marker
Called Address Extension m
FR22r
m
End-to-End Transit Delay Negotiation
FR24r
Expedited Data Negotiation m
FR25r
IPRL for ISO 8802-2
A4 l
The relevant base Standard PICS proforma is the PICS proforma given in annex B. This part of ISO/IEC ISP
10609 imposes the following addi tional constraints:
LLC type 1 - supported PDU types
B.6.1
Constraint
Base Item Description
i
UI/l UI CMD supported on transmission
-
i
UI-CMD supported on receipt
u1/2
XID CMD supported on transmission Cl
XID/3 -
Cl
XID/6 XID RSP supported on receipt
-
i
TEs/7 TEST CMD supported on transmission
-
0 ISO/rEC ISO/IEC ISP 10609=10:1994(E)
B.6.2 LLC type 1 - supported Parameters in PDUs on transmission
Base Item Description Constraint
UIT/l3 UI CMD - P-bit=0 i
-
XDT/17 XID CMD - P-bit=1 c2
-
XID CMD - P-bit=0
XDT/18 c3
-
TST/26 TEST CMD - P-bit=1 i
-
TSTJ27 TEST CMD - P-bit=0 i
-
B.6.3 LLC type 1 - supported Parameters in PDUs on receipt
Base Item Description Constraint
WR/35 UI CMD - P-bit=0 i
-
I I
B.7.5 LLC type 2 - protocol Parameters
Base Item Description Constraint
ACK TIMER range the value of 5+1 seconds -
-
shall be supported
the value 7 shall be
Maximum valuc of k
supported
Definition of conditional Status items:
Cl if a value of k other than 7 is supported then m else o
c2 if a value of k other than 7 is supported AND NOT XDT/l7 then m else x
c3 if a value of k other than 7 is supported AND NOT XDT/lS then m else x
ISO/IEC ISP 10609-10: 1994(E)
0 1s0/rEc
Annex B1
(normative)
Assumed base Standard PICS proforma
for ISO 8802-2 Logical Link Control
Bl . Introduction
The supplier of a protocol implementation which is claimed to conform to ISO 8802-2: 1989 and its amendments:
Amd.1, Amd.2, Amd.4, and Amd.5, shall complete the following Protocol Implementation Conformance
Statement (PICS) proforma.
A completed PICS proforma is the PICS for the implementation in question. The PICS is a Statement of which
capabilities and Options of the protocol have been implemented. The PICS tan have a number of uses, including
use:
by the protocol implementor, as a check-list to reduce the risk of failure to conform to the Standard
through oversight;
by the supplier and acquirer - or potential acquirer - of the implementation, as a detailed indication of
the capabilities of the implementation, stated relative to the common basis for understanding provided
by the Standard PICS proforma;
by the user - or potential User - of the implementation, as a basis for initially checking the possibility
of interworking with another implementation (note that, while interworking tan never be guaranteed,
failure to interwork tan often be predicted from incompatible PICSs);
by a protocol tester, as the basis for selecting appropriate tests against which to assess the claim for
conformance of the implementation.
B2 . Abbreviations and special Symbols
B.2.1 Status Symbols
M mandatory
Osn> optional, but support of at least one of the group of Options labelled by the same numeral
en> is required
X prohibited
1) Copyright release for PICS proformas
Users of this International Standardized Profile may freely reproduce the PICS proforma in this a.nnex so that it ca,n be used
for its intended purpose and may further fkeely publish the completed PICS.
0 ISO/IEC ISO/IEC ISP 10609-10:1994(E)
applicable
particular item
or a group of tables
(sec B.3.4)
B.2.2 General abbreviations
not applicable
N/A
Protocol Implementation Conformance Statement
PILS
B.2.3 1 tem references
The following is a list of item references used in the PICS proforma:
Major capabilities:
CLS Class of LLC supported
RDE Route Determination Entity
LLC type 1:
UI UI PDUs
XID PDUs
XID
TES TEST PDUs
UIT Parameters in transmitted UI PDUs
XDT Parameters in transmitted XID PDUs
TST Parameters in transmitted TEST PDUs
UIR Parameters in received UI PDUs
XDR Parameters in received XID PDUs
TSR Parameters in received TEST PDUs
Miscellaneous protocol features
MIS
LLC type 2:
IP 1 PDUs
IC 1 CMD PDUs
IR IRSP PDUs
RRC KR CMD PDUs
RRR RR-RSP PDUs
RNR CMD PDUs
RNC
RNR RNR-RSP PDUs
REJ ?MD PDUS
RJC
RJR REJ-RSP PDUs
SAE%lE PDUs
SAC
DISC PDUs
DIC
UAR UA PDUs
ISO/IEC ISP 10609-10: 1994(E)
0 ISO/IEC
DMR DM PDUs
FRR FRMR PDUs
PPT Parameters in transmitted PDUs
PPR Parameters in received PDUs
PRS Protocol procedures
PPA Protocol Parameters
MIS Miscellaneous protocol features
LLC type 3:
AnC ACn command PDUs
AC0 CMD PDUs
AOC
ACO-RSP PDUs
AOR
AX ACl-CMD PDUs
AlR ACl-RSP PDUs
AOT ParAeters in transmitted AC0 PDUs
A1T Parameters in transmitted AC1 PDUs
AOR Parameters in received AC0 PDUs
AIR Parameters in received AC1 PDUs
PRS Protocol procedures
PPA Protocol Parameters
MIS Miscellaneous protocol features
B3 Instructions for completing the PICS proforma
.
B.3.1 General structure of the PICS proforma
Implementation Identification and Protocol Summary - is to be completed
The first part of the PICS proforma -
as indicated with the information necessary to identify fully both the supplier and the implementation.
divided into subclauses each containing a
The main part of the PICS proforma is a fixed format questionnaire,
number of individual items. Answers to the questionnaire items are provided in the rightmost column, either by
simply marking an answer to indicate a restricted choice (usually Yes or No) or by entering a value or a set or
range of values.
NOTE - There are some items for which two or more choices fi-om a set of possible answers tan apply. All relevant choices
are to be marked in these cases.
Esch item is identified by an item referencc in the first column; the second column contains the questions to be
answered; and the third column contains the reference(s) to the material that specifies the item in the main body
of ISO 8802-2: 1989 and its amendments Amd.l, Amd.2, Amd.4, and Amd.5. The remaining columns record the
Status of the item - whether support is mandatory, optional, prohibited or conditional - and provide the space for
the answers; see also B.3.4.
further information, categorized as either Additional
A supplier may also provide - or be required to provide -
Information or Exception Information. When present, each kind of further information is to be provided in a
further subclause of items labelled Aci> or Xci>, respectively, for Cross-referencing purposes, where ci> is an
unambiguous identification for the item (e.g. a numeral). There are no other restrictions on its format or
presentation.
0 ISO/IEC ISO/IEC ISP 10609=10:1994(E)
A completed PICS proforma, including any Additional Information and Exception Information, is the
Protocol
Implementation Conformance Statement for the implementation in question.
NOTE - Where an implementation is capable of being configured in more than one way, a Single PICS may be able to
describe all such configurations. However, the supplier has the choice of providing more than one PICS, each
covering a subset of the implementation ’s configuration capabilities, in case that makes for easier and clearer
presentation of the information.
Additional information
B.3.2
Items of Additional Information allow a supplier to provide further information intended to assist the
interpretation of the PICS. It is not intended or expected that a large quantity of information will be supplied
and a PICS tan be considered complete without any such information. Examples of Additional Information might
be an outline of the ways in which a (Single) implementation tan be set up to operate in a variety of
environmcnts and configurations, or a brief rationale -
based perhaps upon specific application requirements -
for the exclusion of features which, although optional, are commonly present in implernentations of the ISO
8802-2: 1989 protocol.
References to items of Additional Information may be entered next to an
...