ISO/IEC 8208:1990/Amd 3:1991
(Amendment)Information technology — Data communications — X.25 Packet Layer Protocol for Data Terminal Equipment — Amendment 3
Information technology — Data communications — X.25 Packet Layer Protocol for Data Terminal Equipment — Amendment 3
Technologies de l'information — Communication de données — Protocole X.25 de couche paquet pour terminal de données — Amendement 3
General Information
Relations
Standards Content (Sample)
INTER NATIONAL ISOIIEC
STANDARD 8208
Second edition
1990-03- 1 5
AMENDMENT 3
I991 -06-01
Information technology -
Data communications - X.25 Packet Layer
Protocol for Data Terminal Equipment
AMENDMENT 3 : Conformance requirements
Technologies de I'information - Communication de données - Protocole X.25 de
couche paquet pour terminal de données
AMENDEMENT 3: Prescriptions de conformité
Reference number
ISO/IEC 8208 : 1990/Amd.3 : 1991 (E)
---------------------- Page: 1 ----------------------
ISO/IEC 8208 : 199WAmd.3 : 1991 (E)
Contents Page
Foreword . iii
Introduction . iv
1 Scope . 1
2 Normative References . 1
21 Conformance . 1
21.1 Static conformance . 1
21.2 Protocol Implementation Conformance Statement . 4
21.3 Dynamic conformance . 4
Annexes
C PICS proforma . 5
C.l Introduction . 5
C.2 Abbreviations and special symbols . 5
C.3 Instructions for completing the PICS proforma . 6
C.4 Identification . 8
C.5 General DTE characteristics . 9
C.6 Procedures. packet types and packet formats . 9
(2.7 Miscellaneous features and options . 16
C.8 Facilities . 18
C.9 Registration-facilities . 24
C.10 Parameter values and ranges . 27
O ISO/IEC 1991
All rights reserved . Unless otherwise specified. no part of this publication may be reproduced or
utilized in any form or by any means. electronic or mechanical. including photocopying and
microfilm. without permission in writing from the publisher .
ISO/IEC Copyright Office 0 Case postale 56 0 CH-1211 Genève 20 0 Switzerland
Printed in Switzerland
ii
---------------------- Page: 2 ----------------------
ISO/IEC 8208 : 199WAmd.3 : 1991 (E)
Foreword
IS0 (the International Organization for Standardization) and IEC (the International
Electrotechnical Commission) form the specialized system for worldwide standardiz-
ation. 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
committees collaborate in fields of mutual interest. Other international organizations,
governmental and non-governmental, in liaison with IS0 and IEC, also take part in the
work.
In the field of information technology, IS0 and IEC have established a joint technical
committee, ISO/IEC JTC 1. Draft International Standards adopted by the joint
technical committee are circulated to national bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the national bodies casting
a vote.
Amendment 3 to International Standard ISO/IEC 8208 : 1990 was prepared by Joint
Technical Committee ISO/IEC JTC 1, Information technology.
---------------------- Page: 3 ----------------------
ISO/IEC 8208 : 1990/Amd.3 : 1991 (E)
lntrod uction
This amendment to ISO/IEC 8208: 1990 consists of four items to be added to EO/
IEC 8208:1990. The two main items are a new clause 21 which states the
conformance requirements for implementations of ISO/IEC 8208, and a new annex
containing the Protocol Implementation Conformance Statement (PICS) proforma
for ISO/IEC 8208:1990. The other two items add related material to clauses 1 and
2 (Scope and Normative references). The remaining clauses 3 to 20, and the
present annexes, of ISO/IEC 8208:i 990 are unchanged by this amendment.
---------------------- Page: 4 ----------------------
ISO/IEC82ûû : 199WAmd.3 : 1991 (E)
Information technology - Data communications - X.25
Packet Layer Protocol for Data Terminal Equipment
AMENDMENT 3: Conformance requirements
Instructions for amending ISO/IEC 8208 : 1990 are given in italics and only modulo 128 packet sequencing, or use of only Fast Select in
numbered from 1 to 4; clause numbers and titles in this amendment call setup).
correspond to those in ISO/IEC 8208 : 1990.
21.1.1 General requirements
A DTE that claims conformance to this International
1 Scope
Standard shall implement:
1. Add the following paragraph at the end of cloiise I, Scope
a) either Permanent Virtual Circuit Service or Virtual Call
Service (and may support both);
To evaluate conformance of a particular implementation, it
is necessary to have a statement of which capabilities and
b) operation in either a DTE/DCE or DTE/DTE
options have been implemented. Such a statement is called
environment (and may support both);
a Protocol Implementation Conformance Statement (PICS),
as defined in ISO/IEC 9646-1. This International Standard
c) in the case of operation in a DTE/DTE environment,
provides the PICS proforma in compliance with the relevant
operation with the role as DTE or DCE either
requirements, and in accordance with the relevant
9646-2.
guidance, given in ISO/IEC
1) initialized to DTE, or
2) initialized to DCE, or
dynamically selected according to the procedures
3)
2 Normative references
in 4.5
e
2. Add the following references in clause 2, Normative
(and may support more than one of these methods of
references, after that for ISOIIEC 9574:1989.
role selection);
ISOIIEC 9646-1 :I 991, Iriformation technology - OSI
d) either modulo 8 packet sequencing or modulo 128
conformance testing methodo1og)l and framework - Part 1 :
packet sequencing (and may support both);
General concepts.
e) the functions specified in table 37 as Mandatory or as
ISOIIEC 9646-211 991, Information technology - OS1
Conditional when the relevant conditions apply,
conformance testing methodology and framework - Part 2:
according to the procedures specified in the clauses to
Abstract test suite specifcation.
which the table items refer;
f) the timers and retransmission counters specified in
3. Add the following new clause 2 I.
table 38 as Mandatory, or as Conditional when the
relevant conditions apply;
21 Conformance
g) the mapping onto the Data Link Layer as specified in
21.1 Static conformance
clause 3, third items (a) to (c); 3.3 first item (d); clause
IO; and 12.1 (Data Link Layer Information Fields, Data
NOTE - Many DTE capabilities are optional. Designers of DTEs
Link Service data units)
use by a DTE of certain options to the
should be aware that
exclusion of others may adversely affect the DTE's general
Such a DTE shall not implement the functions specified in
interconnection capabilities, since complementary options may not
be supported by the DXE or remote DTE (for example, the use of table 37 as Prohibited, when the relevant conditions apply.
1
---------------------- Page: 5 ----------------------
ISO/IEC 8208 : 199WAmd.3 : 1991 (E)
Table 37 - DTE capabilities for static conformance
-
Item DTE capability [ Clauses specifying the Service:
no. corresponding procedures ] PVC vc
1 Restarting the packet layer:
la - as initiator [ 4,4.1,4.3,4.4 ] M M
Ib - as responder [ 4,4.2,4.3,4.4 ] M M
-
2 Support of DIAGNOSTIC packet:
M M
2a - receipt [ 11.1 ]
2b - sending [ 11.1 ] /DCE: X /DCE: X
/DTE: O /DTE:O
3 Virtual Call setup:
[MI
3a - initiating an outgoing VC, with subsequent acceptance or
rejection [ 55.2.1, 5.2.4, 5.2.5, 5.5.2, 5.5.41 (Note 1) O
Receiving an incoming VC and responding by:
3b - acceptance [ 5,5.2.2, 5.2.3,5.2.5] (Note 1) O
3c - rejection [ 5, 5.2.2, 5.2.5,5.3, O
5.5, 5.5.1, 5.5.3, 5.5.41 (Notes 1,2]
4 Aborting an outgoing VC attempt, by clearing
[ 5.4, 5.5, 5.5.1, 5.5.3, 5.5.41 (Note 3) O
5 Clearing an established VC (Note 3)
O
5a - as initiator [ 5.5, 5.5.1, 5.5.3, 5.5.41
5b - as responder [ 5.5, 5.5.2, 5.5.41 O
-
6 Response to errors and unsupported packets on an assigned
[MI
logical channel
- expiry ofT21 [ 5.2.1, 5.41 or R22 [ 8.1 ]
- received packets causing the ERROR procedure in Call
Setup and Call Clearing states [ table 33 ]
- received CLEAR INDICATION if clearing as responder is
not supported (item 5b)
- received RESET INDICATION if resetting as responder is
not supported (item 8b)
by:
6a - initiating clearing O
6b - initiating restarting (Notes 4,5, 6,7) O
6c - other X
7 Response to other errors and to receipt of other unsupported
packets, or fields of packets, on an assigned logical channel,
e
by:
7a - initiating clearing [ 6.3, 6.4, 6.6, 6.8.1, 6.8.2, O
7b - initiating restarting 7.1.3,7.1.4,8.2, 11.2.1, O O
7c - initiating resetting 13.4.1, tables 34, 35, 36 ] O O
7d - other (Notes 5, 6, 7,8) X X
8 Resetting a logical channel:
8a - as initiator [ 8,8.1, 8.3, 8.4 ] (Note 9) O O
8b - as responder [ 8,8.2, 8.3, 8.4 ] (Note IO) O O
-
Where:
M = Mandatory X = Prohibited O = ODtional
=
at least one of the items in this group shall be supported
[MI
=
not applicable to the PVC service
/DCE: = specification for operation in a DTE/DCE environment
/DTE: = specification for operation in a DTElDTE environment
NOTES
1 The reference to 5.2.5 (call collision) applies only if two-way logical channels are supported.
2 Rejection because of errors is covered by item 6.
2
---------------------- Page: 6 ----------------------
ISO/IEC 8208 : 1990/Amd.3 : 1991 (E)
Table 37 (concluded)
,
\
3 Although many implementations that support VCs will be designed to implement call clearing as a matter of course, clearing is classed as
optional because implementations are free to initiate a restart at any time; some implementations, therefore, may exercise this freedom in
I
I
situations where call clearing would otherwise apply.
4 This item does not include unrecognized or unsupported facility codes within a Facilities Field (15.1)
Where optional capabilities are specified for these items, the DTE may choose any permitted option on each occasion that an error, etc.,
5
occurs, independently of the options chosen on other occasions or for other errors, etc.
Packets with LCI = O are excluded, since that is not an assigned logical channel (figure 1).
6
The clauses and tables listed are those specifying the occurrence of errors: items 5, 8 and 9 cover the error procedures themselves.
7
,
8 Although many implementations will be designed to reset on the errors covered by item 7, resetting is classed as optional in item 7
because implementations are free to initiate a restart, or to initiate clearing of a virtual call, at any time; some implementations, therefore,
may exercise this freedom in situations where resetting would otherwise apply.
9 Initiation of resetting is optional: a) because of the considerations in Note 8 with respect to events internal to the packet layer; and b)
because initiation of resetting on request from the higher-layer entity is intrinsically optional, in that an implementation could be designed
for use specifically by a higher-layer entity that in turn is designed never to request resetting.
a
10 Although many implementations will be designed to reset a logical channel by responding to a reset, response to resetting is classed as
optional because implementations are free to initiate restarting, or to initiate clearing of a virtual call, at any time; some implementations ,
therefore, may exercise this freedom in situations where resetting would otherwise apply.
Table 38 - Static conformance: required timers and retransmission counters
M
Restart Request Response Timer and R20 Restart Request Retransmission Counter
T20
c.1
T2 1 Call Request Response Timer
c.2
T22 Reset Request Response Timer and R22 Reset Request Retransmission Counter
c.3
Clear Request Response Timer and R23 Clear Request Retransmission Counter
T23
c.4
T24 Window Status Transmission Timer
c.5
Window Rotation Timer and R25 Data Packet Retransmission Counter
T25
C.6
T26 Interrupt Response Timer
c.7
T27 Reject Response Timer and R27 Reject Retransmission Counter
C.8
T28 Registration Request Response Timer and R28 Registration Request Retransmission Counter
I I
Where: M = Mandatory C.n = Conditional, as follows:
C.l = required if the DTE initiates Virtual Calls
C.2 = required if the DTE initiates resetting
= required if the DTE implements the Virtual Call service and initiates clearing
C.3
C.4 = required if the DTE implements the optional procedure for window status transmission, specified in 11.2.2
= required if the DTE implements either of the optional procedures relating to the receipt of window rotation information,
C.5
specified in 11.2.1
= required if the DTE supports sending of Interrupt data
C.6
C.7 = required if the DTE supports the optional user facility for Packet Retransmission
= required if the DTE supports the optional user facility for On-line Facility Registration
C.8
21 .I .2 Options
A DTE that claims conformance to this International e) support either the use of the D-bit, or the optional
mechanism for negotiating use or non-use of the D-bit
Standard is not required to:
(6.3);
a) send DIAGNOSTIC packets (3.3, second item (d);
11 .I); f) transmit specific diagnostic code values when
originating restarting, clearing or resetting (tables 24 and
25; 12.2.3.1, 12.5.1, 12.6.1);
b) support any optional user facilities (clause 13);
c) support any optional CCITT-specified DTE facilities g) implement transient states r3, p3, p7, d3, j2;
(clause 14);
h) transmit RNR packets (7.1.6);
d) transmit a specific value of the Q-bit in DATA packets
3
---------------------- Page: 7 ----------------------
ISO/IEC $208 : 1990/Amd.3 : 1991 (E)
j) implement any of the optional procedures relating to
non-receipt of window rotation information (1 1.2.1,
11.2.2);
k) implement either of the non-standard alternative
modes of recovery from receipt of out of sequence DATA
packets (1 1.3 (b) and (c));
I) support Interrupt data transfer (6.8);
m) support transfer of user data in call setup and clearing
packets (5.2.1, 5.2.2, 5.2.3, 5.2.4, 5.5.1, 5.5.2);
n) support DATA packet transfer (clause 6);
p) support DATA packets with the M-bit set to 1 (6.4,
6.7);
q) transmit updated window rotation information (7.1.3);
r) transmit RR packets (7.1 5)
(I), (m), (n) and (p) support refers to
In items (b), (c), (e),
transmission and reception, independently.
NOTE - Non-support by a DTE of any of items (I) to (r), and to a
lesser extent of item (d), would normally be appropriate only for an
unusual and highly application-specific implementation; these
items, although strictly optional, are generally expected to be part
of the normal functionality of a DTE.
21.2 Protocol Implementation Conformance
Statement
The supplier of a protocol implementation which is claimed
to conform to this International Standard shall complete a
copy of the PICS proforma provided in annex C, including
to identify fully both the supplier
the information necessary
and the implementation.
21.3 Dynamic conformance
A DTE for which conformance to this International Standard
is claimed shall exhibit external behaviour consistent with
having implemented, for each function that the PICS states
to be supported,
a) the corresponding Packet Layer procedures and
b) the encoding of any transmitted packets
as specified in the clauses to which the PICS proforma
entry for the function refers, and using the Data Link Layer
as specified in 3.3, clause 1 O, and 12.1.
4. Add a new norinative annex C as follows.
4
---------------------- Page: 8 ----------------------
ISO/IEC 8208 : 1990/Amd.3 : 1991 (E)
Annex C *
(normative)
PICS Proforma
N/A not applicable
C.l Introduction
PICS Protocol Implementation Conformance Statement
The supplier of a protocol implementation which is claimed PVC Permanent Virtual Circuit
to conform to ISO/IEC 8208 : 1990 shall complete the
following Protocol Implementation Conformance Statement C.2.3 Item references
(PICS) proforma.
PICS items dealing with related functions are identified by
item references sharing the same initial letter or letter-pair
A completed PICS proforma is the PICS for the
implementation in question. The PICS is a statement of (in capitals). There follow two lists of those initials, first in
the order in which the items occur in the PICS proforma,
which capabilities and options of the protocol have been
and then in alphabetical order.
implemented. The PICS can have a number of uses,
including use:
C.2.3.1 In order of occurrence
- by the protocol implementor, as a check-list to reduce
V permanent Virtual circuit or Virtual call service
the risk of failure to conform to the standard through
E Environment: DTE/DCE or DTE/DTE; X.25 1988,
oversight;
1984 or 1980
- by the supplier and acquirer - or potential acquirer - M Modulo 8 or Modulo 128 packet sequence numbers
of the implementation, stated relative to the common RN Reference Number optional user facility
basis for understanding provided by the standard PICS
L Link layer interactions
proforma;
P general Packet formatting
Z packet layer functions independent of logical
- by the user - or potential user - of the
implementation, as a basis for initially checking the channels (packets with LC identifier Zero)
possibility of interworking with another implementation S call Setup
(note that, while interworking can never be guaranteed, SP call Setup Packets
DN D-bit Negotiation
failure to interwork can often be predicted from
call Clearing
incompatible PICSs); C
call Clearing Packets
CP
RS Resetting of logical channels
- by a protocol tester, as the basis for selecting
error procedures (response to Wrong behaviour)
appropriate tests against which to assess the claim for W
conformance of the implementation. I Interrupt transfer
DS
Data packet Sending
DR Data packet Receiving
Delivery Confirmation
DC
C.2 Abbreviations and special symbols
Y cause and diagnostic code values (why resets, etc.,
C.2.1 Status symbols
initiated)
M mandatory O Observability of transient states
O optional B X.25 (1 980) interworking: Backward compatibility
0.n optional, but support of at least one of the group of N X.25 Network differences from ISO/IEC 8208
options labelled by the same numeral n is required
X prohibited FS Facilities Sent during call setup and clearing
pred: conditional-item symbol, including predicate FR Facilities Received during call setup and clearing
identification: see C.3.4 GS reGistration facilities Sent
7 logical negation, applied to a conditional item's GR reGistration facilities Received
predicate
V parameter Values and ranges
Timers
C.2.2 General abbreviations T
R
Retransmission counts
Logical Channel ranges
LC logical channel LC
*) Copyright release for PICS proformas
Users of this International Standard may freely reproduce the PICS proforma in this annex so that it can be used for the intended purpose and
may further publish the completed PICS.
5
---------------------- Page: 9 ----------------------
ISOllEC 8208 : 1990/Amd.3 : 1991 (E)
mandatory, optional, prohibited or conditional - and provide
A Additional information the space for the answers: see also C.3.4 below. (Status is
X exception information
sometimes indicated by other means than a separate
Status column: for example, where the same status applies
C.2.3.2 In alphabetical order to a whole group of items, as in C.8.1.)
A Additional information
A supplier may also provide, or can be required to provide,
B X.25 (1 980) interworking: Backwards compatibility further information, categorized as either Additional
C call Clearing Information or Exception Information. When present, each
CP call Clearing Packets kind of further information is to be provided in a further
DC Delivery Confirmation subclause of items labelled Ai or Xi respectively for cross-
DN D-bit Negotiation referencing purposes, where i is any unambiguous
DR Data packet Receiving identification for the item (e.g., simply a numeral): there are
DS Data packet Sending no other restrictions on its format and presentation.
E Environment: DTE/DCE or DTE/DTE; X.25 1988,
1984 or 1980 A completed PICS proforma, including any Additional
FR Facilities Received during call setup and clearing Information and Exception Information, is the Protocol
FS
Facilities Sent during call setup and clearing Implementation Conformance Statement for the
GR reGistration facilities Received implementation in question.
GS reGistration facilities Sent
I Interrupt transfer NOTE - Where an implementation is capable of being configured
in more than one way according, for example, to the items in C.5, a
L Link layer interactions
single PICS may be able to describe all such configurations.
Logical Channel ranges
LC
However, the supplier has the choice of providing more than one
M Modulo 8 or Modulo 128 packet sequence numbers
PICS, each covering some subset of the implementation's
N X.25 Network differences from ISO/IEC 8208
configuration capabilities, in case that makes for easier and clearer
O Observability of transient states
presentation of the information.
P general Packet formatting
R Retransmission counts
C.3.2 Additional Information
RN Reference Number optional user facility
RS Resetting of logical channels
Items of Additional Information allow a supplier to provide
S call Setup
further information intended to assist the interpretation of
SP call Setup Packets
the PICS. It is not intended or expected that a large quantity
T Timers
will be supplied, and a PICS can be considered complete
V permanent Virtual circuit or Virtual call service
without any such information. Examples might be an outline
Vn parameter Values and ranges
of the ways in which a (single) implementation can be set
W
error procedures (response to Wrong behaviour)
up to operate in a variety of environments and
X exception information
configurations; or a brief rationale - based perhaps upon
Y cause and diagnostic code values (why resets, etc.,
specific application needs - for the exclusion of features
initiated)
which, although optional, are nonetheless commonly
2
packet layer functions independent of logical
present in implementations of the X.25 packet layer
channels (packets with LC identifier Zero)
protocol.
References to items of Additional Information may be
C.3 Instructions for completing the PICS
entered next to any answer in the questionnaire, and may
proforma
be included in items of Exception Information.
C.3.1 General structure of the PICS proforma
C.3.3 Exception Information
The first part of the PICS proforma - Identification, C.4 - is
It may occasionally happen that a supplier will wish to
to be completed as indicated with the information necessary
answer an item with mandatory or prohibited status (after
to identify fully both the supplier and the implementation.
any conditions have been applied) in a way that conflicts
with the indicated requirement. No pre-printed answer will
The main part of the PICS proforma is a fixed-format
be found in the Support column for this: instead, the
questionnaire divided into six major subclauses; these can
supplier shall write the missing answer into the Support
be divided into further subclauses each containing a group
column, together with an Xi reference to an item of
of individual items. Answers to the questionnaire items are
Exception Information, and shall provide the appropriate
to be provided in the rightmost column, either by simply
rationale in the Exception item itself.
marking an answer to indicate a restricted choice (usually
Yes or No), or by entering a value or a set or range of
An implementation for which an Exception item is required
values. Note that there are some items where two or more
in this way does not conform to ISO/IEC 8208 : 1990.
choices from a set of possible answers can apply: all
relevant choices are to be marked.
NOTE - A possible reason for the situation described above is
that a defect in this International Standard has been reported, a
Each item is identified by an item reference in the first correction for which is expected to change the requirement not met
by the implementation.
column; the second column contains the question to be
answered; the third column contains the reference or
references to the material that specifies the item in the main
body of ISO/IEC 8208 : 1990. The remaining columns
record the status of the item - whether support is
6
---------------------- Page: 10 ----------------------
ISO/IEC 8208 : 1990/Amd.3 : 1991 (E)
C.3.4 Conditional status
C.3.4.1 Conditional items
The PICS proforma contains a number of conditional items.
These are items for which the status - mandatory, optional
or prohibited - that applies is dependent upon whether or
not certain other items are supported.
In many cases, whether or not the item applies at all is
conditional in this way, as well as the status when the item
does apply.
Where a group of items is subject to the same condition for
applicability, a separate preliminary question about the
condition appears at the head of the group, with an
instruction to skip to a later point in the questionnaire if the
"Not Applicable" answer is selected. Otherwise, individual
conditional items are indicated by one or more conditional
symbols (on separate lines) in the Status column.
A conditional symbol is of the form "pred S" where pred is
a predicate as described in C.3.4.2 below, and S is one of
the status symbols M, O, 0.n or X.
If the value of the predicate in any line of a conditional item
is true (see C.3.4.2), the conditional item is applicable, and
its status is that indicated by the status symbol following the
predicate: the answer column is to be marked in the usual
If the value of a predicate is false, the Not Applicable
way.
(N/A) answer is to be marked in the relevant line. (Each line
in a multi-line conditional item should be marked: at most
one line will require an answer other than NIA.)
C.3.4.2 Predicates
A predicate is one of the following:
a) an item-reference for an item in the PICS proforma:
the value of the predicate is true if the item is marked as
supported, and is false otherwise: or
b) a predicate name, for a predicate defined elsewhere
in the PICS proforma: see below; or
c) the logical negation symbol "4' prefixed to an item-
reference or predicate name: the value of the predicate is
true if the value of the predicate obtained by omitting the
"Y'' symbol is false, and vice versa.
The definition for a predicate name is a boolean expression
constructed by combining simple predicates, as at (a) or (b)
above, using the boolean operators AND, OR and NOT,
and parentheses, in the usual way. The value of such a
predicate is true if the boolean expression evaluates to true
when the item-references are interpreted as at (a) above.
Each item whose reference is used in a predicate or
predicate definition is indicated by an asterisk in the Item
colu m n.
7
---------------------- Page: 11 ----------------------
ISO/IEC 8208 : 1990/Amd.3 : 1991 (E)
C.4 ldent ification
C.4.1 Implementation identification
Supplier
Contact point for queries about the PICS
Implementation Name(s) and Version(s)
Other information necessary for full
identification - e.g., name(s) and
version(s) of machines and /or operating
systems; system names
NOTES
1 Only the first three items are required for all implementations; other information may be completed as appropriate in meeting the
requirement for full identification.
2 The terms Name and Version should be interpreted appropriately to correspond with a supplier's terminology (e.g., Type, Series, Model).
C.4.2 Protocol summary
I
Identification of protocol specification IS011 EC 8208 : 1990
ISO/IEC 8208 : 1990/Amd.l : 1990
l
I
Identification of amendments and corrigenda to ISO/IEC 8208 : 19901
this PICS proforma which have been completed
as part of this PICS
Amd. Corr.
Amd. Corr.
Amd. Corr.
Amd. Corr.
Have any Exception items been required (see C.3.3)?
No 0 Yes O
(The answer Yes means that the implementation does not conform to ISO1IEC 8208 : 1990)
Date of Statement
8
---------------------- Page: 12 ----------------------
ISO/IEC 8208 : 1990/Amd.3 : 1991 (E)
C.5 General DTE Characteristics
References Status support
Protocol Feature
Item
Service supported:
0.1 Yeso Non
vs - Virtual Call
o. 1
- Permanent Virtual Circuit Yes0 NOO
* VP
What environments are supported? 3, 3.2
0.2 Yeso Non
Ec/8 - DTE/DCE (1988)
0.2
- DTE/DCE (1984) Yeso Non
Ec/4
0.2 Yes0 NOO
* Ec/O - DTE/DCE (1980)
- DTE/DTE in fixed role as DTE 0.2
Yes0 NOO
Eüt
vs: 0.2
- DTE/DTE in fixed role as DCE N/AO Yes0 NOO
Et/c
vs: 0.2
4.5 Yes0 NOD
Et/ d - DTElDTE with dynamic role selection N/AO
What packet sequence numbering is supported?
0.3
* M8 - MûduIo 8 13.2, 12.1 .I, table 3 Yeso Non
a
0.3
13.2, 12.1.1, table 3 Yes0 NOO
MI28 - Modulo 128 (extended)
Is the Reference Number optional user facility 13.28, 13.28.1,
supported, for the alternative Logical Channel 13.28.2, 13.28.3,
13.28.3, 13.28.4,
Identifier assignment mechanism:
figure 36,
Et: O
13.28.2.1 N/AO Yes0 NOO
RNa - without reversion to use of logical channel ranges?
-Et: X
NIACI NOO
Et: O
- with possible reversion of operating mode to use 13.28.2.1 N/AO Yes0 NOO
RNb
logical channel ranges?
-.Et: X
N/AO NOO
Predicate def
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.