SIST EN ISP 10609-10: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)

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)

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)

General Information

• Status: Withdrawn
• Publication Date: 30-Nov-1997
• Withdrawal Date: 30-Sep-2003
• ICS: 35.100.05 - Multilayer applications
• Technical Committee: ITC - Information technology
• Current Stage: 9900 - Withdrawal (Adopted Project)
• Start Date: 01-Oct-2003
• Due Date: 01-Oct-2003
• Completion Date: 01-Oct-2003
• Ref Project: EN ISP 10609-10:1996 - 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)

Standards Content (Sample)

SLOVENSKI STANDARD
SIST EN ISP 10609-10:1997
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
SIST EN ISP 10609-10:1997 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST EN ISP 10609-10:1997

---------------------- Page: 2 ----------------------

SIST EN ISP 10609-10:1997

---------------------- Page: 3 ----------------------

SIST EN ISP 10609-10:1997

---------------------- Page: 4 ----------------------

SIST EN ISP 10609-10:1997
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)

---------------------- Page: 5 ----------------------

SIST EN ISP 10609-10:1997
ISO/IEC ISP 10609-10: 1994(E)
Page
Contents
iv
Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .“.
vi
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
2 Normative references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
2
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
3
Requirements .
5
3
5.1 Introduction .
......................................... 3
5.2 Static conformance requirements
....................................... 5
5.3 Dynamit conformance requirements
......................................... 10
Annex A ISPICS requirements list (normative)
10
.......................................................
A.l Introduction
..............................................
10
A.2 Notation and conventions
...............................................
12
A.3 IPRL for ISO/IEC 8208
.................................................
14
A.4 IPRL for ISO 8802-2
.... 16
Annex B Assumed base Standard PICS proforma for ISO 8802-2 Logical Link Control (normative)
.......................................................
16
B.l Introduction
.......................................
16
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)
.......................................................
43
C.1 Introduction
......................................... 43
C.2 ISO/IEC 8208 recommendations
........................................... 43
C.3 ISO 8802-2 recommendations
................................................
46
Annex D Bibliography (informative)
................................................
46
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

---------------------- Page: 6 ----------------------

SIST EN ISP 10609-10:1997
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
. . .
111

---------------------- Page: 7 ----------------------

SIST EN ISP 10609-10:1997
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

---------------------- Page: 8 ----------------------

SIST EN ISP 10609-10:1997
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.

---------------------- Page: 9 ----------------------

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

---------------------- Page: 10 ----------------------

SIST EN ISP 10609-10:1997
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
1

---------------------- Page: 11 ----------------------

SIST EN ISP 10609-10:1997
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
2

---------------------- Page: 12 ----------------------

SIST EN ISP 10609-10:1997
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.
0
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)

---------------------- Page: 13 ----------------------

SIST EN ISP 10609-10:1997
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:
0
- 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)

---------------------- Page: 14 ----------------------

SIST EN ISP 10609-10:1997
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;

---------------------- Page: 15 ----------------------

SIST EN ISP 10609-10:1997
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;
6

---------------------- Page: 16 ----------------------

SIST EN ISP 10609-10:1997
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;
7

---------------------- Page: 17 ----------------------

SIST EN ISP 10609-10:1997
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.
0
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;
0
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 ’.

---------------------- Page: 18 ----------------------

SIST EN ISP 10609-10:1997
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 ’.
1
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.

---------------------- Page: 19 ----------------------

SIST EN ISP 10609-10:1997
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 defin
...