Information technology — Telecommunications and information exchange between systems — X.25 DTE conformance testing — Part 2: Data link layer conformance test suite

Technologies de l'information — Télécommunications et échange d'information entre systèmes — Test de conformité X.25 DTE — Partie 2: Suite d'essais de conformité pour la couche liaison de données

General Information

Status
Withdrawn
Publication Date
26-Dec-1995
Withdrawal Date
26-Dec-1995
Current Stage
9599 - Withdrawal of International Standard
Start Date
01-Jun-2000
Completion Date
01-Jun-2000
Ref Project

RELATIONS

Buy Standard

Standard
ISO/IEC 8882-2:1995 - Information technology -- Telecommunications and information exchange between systems -- X.25 DTE conformance testing
English language
204 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

ISOJIEC
INTERNATIONAL
STANDARD 8882-2
Second edition
1995-l 2-15
Information technology -
Telecommunications and information
exchange between systems - X.25 DTE
conformance testing -
Part 2:
Data link layer conformance test suite
- T&kommunica tions et kchange
Technologies de /‘information
Test de conformit X.25 DTE -
d’information entre systhmes -
Partie 2: Suite d’essais de conformit pour la couche liaison de don&es
Reference number
&O/I EC 8882-2: 1995(E)
---------------------- Page: 1 ----------------------
ISO/IEC 8882=2:1995(E)
Contents
Page
1 Scope ........................................................
2 Normative references ................................................
........................................... 2
3 Definitions and abbreviations
3.1 Reference model definitions ...........................................
............................................ 2
3.2 Conformance testing terms
...................................... 3
3.3 X.25DTE conformance testing terms
...............................................
3.4 Additional definitions
............................................... 3
3.4.1 improper frame
3.4.2 inoppertune frame ..............................................
................................................. 3
3.4.3 properframe
3.5 Abbreviations ...................................................
4 Test suite information ................................................
4.1 Test suite structure ................................................

4.2 Data link layer test groups and subgroups ................................... 4

4.3 Method for conformance testing ......................................... 4
4.4 Test case notation ................................................
4.5 Preamble .....................................................
............................................... 5
4.6 Verification sequence
................................................ 5
4.7 IUT initiated actions
4.8 Acceptable unexpected IUT frames ....................................... 5
.................................................
4.9 Transient states 6
............................................... 6
4.10 Unreachable states
................................................... 6
4.11 Declarations
4.12 Order of bit transmission ............................................ 6
..................................................
4.13 PIXIT proforma
............................................... 8
4.14 Classification of IUT
............................................. 9
5 TTCN abstract test suite
. 9
...............................................
5.1 Test suite overview
.................................................
5.2 Test case index
................................................. 27
5.3 Test step index
5.4 ASN.l type definitions .............................................
5.5 Test suite parameter declarations .......................................
................................... 33
5.6 Test case selection expression definitions
........................................
5.7 Test case variable declarations
................................................ 34
5.8 PC0 declarations
............................................... 34
5.9 Timer declarations
0 ISO/IEC 1995

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced

or utilized in any form or by any means, electronic or mechanical, including photocopying and

microfilm, without permission in writing from the publisher.
I SO/I EC Copyright Off ice l Case Postale 56 l CH-1211 Gen&ve 20 l Switzerland
Printed in Switzerland
---------------------- Page: 2 ----------------------
lSO/IEC 0
ISO/IEC 8882-2: 1995(E)
5.10 ASN.1 PDU type definitions .......................................... 35
5.11 ASN.1 PDU constraint declarations ...................................... 38

5.12 Verification of the disconnected phase .................................... 63

5.13 Verification of the IUT link disconnection phase ............................... 77

5.14 Verification of link setup phase ......................................... 90

5.15 Verification of information transfer phase .................................. 102

5.16 Verification of frame reject condition ..................................... 121

5.17 Verification of IUT busy condition ....................................... 134

5.18 Verification of sent reject condition ...................................... 149

5.19 System parameters and error recovery tests ................................ 163

5.20 Preambles ................................................... 168
5.21 Verification sequences ............................................. 180
5.22 Common library sub-trees 183
...........................................
5.23 Local library sub-trees ............................................. 190

Annex A (informative) - Conformance Testing Summary IMatrix . . . . . . . . . . . . . . . . . . . . . . . . . 193

. . .
III
---------------------- Page: 3 ----------------------
ISO/IEC 8882-2: 1995(E)
0 lSO/IEC
Foreword

IS0 (the International Organization for Standardization) and IEC (the International Electrotechnical Commission)

form the specialized system for worldwide standardization. National bodies that are members of IS0 or IEC par-

ticipate in the development on International Standards through technical committees established by the respec-

Other international organizations, governmental
tive organization to deal with particular fields of mutual interest.
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 lSO/IEC JTCl. Draft Interna-

tional 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 O/o of the national bodies casting a vote.

International Standard lSO/lEC 8882-2 was prepared by Joint Technical Committee ISO/lEC JTCl, Information tech-

nology, Subcommittee SC 6, Telecommunications and information exchange between systems.

This second edition cancels and replaces the first edition (ISO/lEC 8882-2:1992), which has been technically

revised.

ISO/IEC 8882 consists of the following parts, under the general title lnformation technology -- Telecommunications

and information exchange between systems -- X.25 DTE conformance testing:
- Part I : General principles
- Part 2 : Data link layer conformance test suite
- Part 3 : Packet layer conformance test suite
Annex A of this part of IOWIEC 8882 is for information only.
---------------------- Page: 4 ----------------------
ISO/IEC 0
ISO/IEC 88822:1995(E)
Introduction

This part of lSO/IEC 8882 presents the X.25DTE Conformance Test Suite for Data Link Layer, described in Tree

and Tabular Combined Notation (TTCN).

Part 1 of ISO/IEC 8882 explains the objectives and usage of this part of lSO/lEC 8882.

Clause 1 of this part of lSO/lEC 8882 is the scope which provides an objective basis for the applicability of the

tests within this part of ISO/IEC 8882. Clauses 2 and 3 give the references, definitions and abbreviations used in

this part of lSO/lEC 8882. Clause 4 contains information relating to procedures performed in conformance testing.

The test suite structure is defined in terms of test groups and subgroups in Table 1. This clause also gives an

overview of the test suite. Clause 5 contains the abstract test suite for the X.25DTE LAPB Data Link Layer pro-

tocol. Finally, Annex A provides a conformance testing summary matrix.
---------------------- Page: 5 ----------------------
This page intentionally left blank
---------------------- Page: 6 ----------------------
INTERNATIONAL STANDARD @ lSO/IEC lSO/lEC 8882=2:1995(E)
Telecommunications and
Information technology -
- X.25 DTE
information exchange between systems
conformance testing -
Part 2:
Data link layer conformance test suite
operation of a DTE is included by implication because
1 Scope
of the need to communicate with X.25 DCEs. This part
of ISO/IEC 8882 excludes the testing of the LAP proce-
This part of ISO/IEC 8882 defines an abstract test
dures given in the CCITT Recommendations.
suite for testing the conformance of the Data Link
Layer of an IUT with respect to ISO/IEC 7776 or the
NOTE Test cases for extended mode operation (Modulo 128), multilink

CCITT Recommendation X.25 (1980, 1984). procedure and DTE-DIE operation as per ISOAEC 7776 are for further

study.
Conformance of a Data Terminal Equipment (DTE) to
The tests in this part of iSO/IEC 8882 are designed for
the above IS0 International Standard or CCITT
three possible interworking situations, shown in
Recommendations is tested using a dedicated circuit
Figure 1. This part specifies tests for ail three cases
between the tester and the DTE. it is noted that
shown in Figure 1, but recognizes that not every test
CCITT Recommendations X.25 (1980) and X.25 (1984)
may apply to a particular DTE. A test selection proce-
are written from the perspective of a DCE and there-
dure has to be performed to determine the applica-
fore do not always explicitly specify the DTE’s opera-
bility of a test to a particular DTE. Such selection wiil
tion. In such cases it is assumed that recommended
be based on the PKS and the PIXIT.
Local Station Remote Station
4------d
DTE DCE (X.25 LAPB 84)
(based on ISO/IEC 7776) DTE (ISO/IEC 7776)
DTE DCE
(X.25 LAPB 84)
(based 011 X.25 LAPB 84)
I -
DCE
DTE
(X.25 LAPB SO)
(based on X.25 LAPB 80)
Figure 1 - Testing X.25DTEIDCE and X.25DTE/DTE Interworking
International Standard ISO/IEC 7776, unless stated
In the rest of this part of tSO/IEC 8882, the term “X.25
standards” means all three of CCITT Recommendation otherwise.
X.25 (1980), CCITT Recommendation X.25 (1984), and
---------------------- Page: 7 ----------------------
ISO/IEC 8882-2 : 1995 (E) 0 ISOAEC
CCITT Recommendation X.25 (1980), Interface
2 Normative references
Between Data Terminating Equipment (DTE) and Data
Circuit- Terminating Equipment (DCE) for Terminals
The following standards contain provisions which,
Operating in the Packet Mode on the Public Data Net-
through reference in this text, constitute provisions of
works.
this part of lSO/lEC 8882 At the time of publication,
the editions indicated were valid. All standards are
CCITT Recommendation X.25 (1984), Interface
subject to revision, and parties to agreements based
Between Data Terminating Equipment (DTE) and Data
on this part of ISO/IEC 8882 are encouraged to inves-
Circuit-Terminating Equipment (DCE) for terminals
tigate the possibility of applying the most recent edi-
operating in the Packet Mode on the Public Data Net-
tions of the standards listed below. Members of IEC
works by Dedicated Circuit.
and IS0 maintain registers of currently valid Interna-
tional Standards.
lSO/IEC 7498-l : 1994, Information technology -- Open
Systems Interconnection -- Basic Reference Modei:
The Basic Modei (See a/so CCtTT Recommendation 3 Definitions and abbreviations
x *ZOO).
For the purposes of this part of ISO/IEC 8882, the defi-
lSO/IEC 7776: 1995, Information technology -- Tefe-
nitions given in 3.4 and in the following International
communications and information exchange between
Standards apply:
systems -- High-level data link contra/ procedures --
a) lSO/lEC 7498-l;
Description of the X.25 LAPB-compatible DTE data link
procedures.
b) ISO/IEC 9646;
c) ISOIIEC 8882-l.
ISO/IEC 8824: 1990, information technology -- Open
Systems Interconnection -- Specification of Abstract
Syntax Notation One (ASN.7) (See also CClTT Recom-
3.1 Reference model definitions
mendation X.680).
The following terms defined in lSO/lEC 7498-l are
lSO/IEC 8882-1:1993, Information technology -- Tele-
used:
communications and information exchange between
a) (N)-protocol data unit (N-PDU). In the context of
systems -- X.25-DTE conformance testing -- Part I,
this part of lSO/IEC 8882 (N) is layer 2 and so
General principles.
N-PDU is abbreviated to PDU. A PDU in the Data

ISO/IEC 9646-l : 1991, Information technology -- Open Link Layer is also referred to as a “frame”.

Systems Interconnection -- Conformance testing meth-
b) Data Link Layer
-- Part 1: General concepts.
odology and framework
(See also CClTT Recommendation X.290).
3.2 Conformance testing terms
ISO/IEC 9646-2: 1994, information technology -- Open
Systems Interconnection -- Conformance testing meth-
The following terms are used from the Conformance
Part 2: Abstract Test Suite
odology and framework --
Testing Methodology and Framework International
specification. (See also CCfTT Recommendation
Standard (lSO/lEC 9646):
X.291).
a) Conformance Testing
lSO/IEC 9646-3: 1992, Information technology -- Open
Conformance Test Suite
Systems Interconnection -- Conformance testing meth-
Implementation Under Test (IUT)
odology and framework -- Part 3: The Tree and
Tabular Combined Notation (TKN).
Protocol Implementation Conformance Statement
(PIGS)
lSO/lEC 9646-4: 1994, Information technology -- Open
Protocol Implementation Extra Information for
-- Conformance testing meth-
Systems Interconnection
Testing (PIXIT)
odology and framework -- Part 4: Test realization.
(See also CClTT Recommendation X.293).
f) Static Conformance Requirements (SCR)
g) Behavior Testing
lSO/IEC 9646-5: 1994, Information technology -- Open
Systems Interconnection -- Conformance testing meth-
h) Test Purpose
odology and framework -- Part 5: Requirements on
i) Tree and Tabular Combined Notation (TTCN)
test laboratories and clients for the conformance
assessment process. (See a/so CC177 Recommenda-
j) Preamble
tion X .294).
---------------------- Page: 8 ----------------------
0 lSO/IEC ISO/IEC 8882-2 : 1995 (E)
k) Test Body a) it is not properly bounded by two flags;
I) Test Step b) it contains fewer than 32 bits between flags;
m) Test Event c) it contains a Frame Check Sequence (FCS) error;

n) Abstract Service Primitive ASP) d) it contains an invalid address field encoding;

o) Test Group e) it contains a command or response control field
encoding that is undefined or not implemented in
p) Abstract Test Suite (ATS)
X.25DTE LAPB Data Link Layer protocol as speci-
Executable Test Suite (ETS fied in ISO/IEC 7776;
Test Verdicts f) it is an I frame exceeding the maximum estab-
lished frame length;
Lower Tester
g) it is an unnumbered or supervisory frame with an
Upper Tester
information field which is not permitted;
Test Methods
h) it is a frame with an invalid N(R).
Remote Single (layer) Test Method (RS method)
3.4.2 inopportune frame : A syntactically valid frame
Valid Test Event
arriving at a time (DTE’s state) when it should be con-
sidered irrelevant by the DTE. Syntactically valid
Invalid Test Event
frames are those that are allowed by the X.25 stand-
Inopportune Test Event
ards for a DTE using the LAPB procedure and are not
covered by 3.4.1.
z) Point of Control and Observation (PCO)
3.4.3 proper frame : A valid frame arriving at the
3.3 X.25DTE conformance testing terms
correct DTE’s state or phase and not covered by 3.4.1
or 3.4.2.
This part of ISO/IEC 8882 makes use of the following
terms defined in ISO/IEC 8882-l:
3.5 Abbreviations
a) Improper PDU
b) Proper PDU The abbreviation IUT is used in this part of ISO/IEC
8882 to refer to an X.25-DTE under test.
c) Test Case
d) Test Subgroup
e) Tester
4 Test suite information
3.4 Additional definitions
This test suite uses test subgroups for proper, 4.1 Test suite structure
improper and inopportune frames to test the IUT

behavior. These terms are defined below. The X.25-DTE Data Link Layer Conformance Test Suite

structure is outlined in Table 1.
3.4.1 improper : A frame that satisfies one or
frame
more of the fol lowing condi tions:
---------------------- Page: 9 ----------------------
ISWIEC 8882-2 : ‘9995 (E) 0 ISOAEC
Table I. Data link Bayer test suite structure
Data Link Test State Test Group Natne Current State of IUT
Abbreviation
Layer Test
Groups
DP Disconnect phase DISC received and UA or DM transmitted (see
DLI
clause 4.10)

DL2 LD Link Disconnection phase DISC transmitted from any phase (see clause 4.11)

Link Set-up phase SABM transmitted from DP (see clause 4.11)
DL3 LS
IT Information Transfer phase SABM received and UA transmitted, or SABM
DL4
transmitted and UA received, while in DP or IT
phase
DL5 FR Frame Reject condition FRMR transmitted from IT phase (see clause 4.10)
DL6 BY IUT Busy condition RNR transmitted from IT phase (see clause 4.10
and 4.11)
DL7 SR Sent Reject condition REJ transmitted from IT phase
DL8 SP System Parameters and Error See note below
Recovery
Note:
Test Group DL8 tests the setting of the system parameters:
11 - Retransmission timer;
N2 - Maximum number of attempts by IUT to complete a transmission.

The setting of maximum established length and k (window size) are tested under test group DL4.

4.4 Test case notation
4.2 Data link layer test groups and subgroups
Clause 5 describes the abstract test suite using the
The first seven test groups shown in Table 1, called
Tree and Tabular Combined Notation (TTCN). This
Data Link Layer Test Groups DLl to DL7, are pro-
abstract test suite complies with ISOllEC 9646-3 for
vided to test the interactive capability of the IUT in

every phase. The test groups are further divided into TTCN.GR. The test realizer shall comply with the

three subgroups according to the definitions in clause requirements of ISO/IEC 9646-4. In particular, these

3.4. These are as follows: concern the realization of an Executable Test Suite
(ETS) based on the Abstract Test Suite (ATS). Test
l Subgroup 1 involves those test cases where the
t aboratories running conformance test services for
tester transmits a proper frame.
this abstract test suite shall comply with ISO/IEC
l Subgroup 2 involves those test cases where the 9646-5.
tester transmits an improper frame.
The tests described in this test suite may be per-
l Subgroup 3 involves those test cases where the
formed in any order. Test cases are independent of
tester transmits an inopportune frame.
one another. Most of the test cases consist of a pre-
amble followed by a test body and ending with a ver-
The eighth test group (DL8) is designed to test the
ification sequence. The preamble consists of the
operational correctness of the IUT system parameters
initialization test steps described in clause
listed in Table 1.
“Preambles.” The verification sequences consists of
the final test step described in clause “Verification
sequences.” In some instances in the test steps, all
4,3 Method for conformance testing
the possible parameter alternatives for PDUs are not
verified, as they do not directly relate to the test
The method for conformance testing shall be as
purpose.
defined in ISO/IEC 8882-l.
The preambles shown in this part of lSO/lEC 8882 are
examples of how, for different situations, the tester
can get the IUT into the desired phase or state.
These preambles are not meant to be either a manda-
tory or exhaustive set of acceptable initialization
sequences for the IUT. Other possible preambles
may be negotiated between the test laboratory and
the client. Table 2 illustrates an abstract test case
written in TTCN:
---------------------- Page: 10 ----------------------
0 ISO/IEC ISO/IEC 8882-2 : 1995 (E)
Table 2. Test Step Dynamic Behavior
Test Step Name : TTCN-EXAMPLE
Group
: Example Test Case
Objective : An example test step illustrating an abstract test case in TTCN.
Default .
Comments .
Nr Label Behavior Description Constraints Ref Verdict Comments
1 -I- preamble-l [IUT-TYPE = option-l] 1
-I- preamble-n [IUT-TYPE = option-n] 2
-t- test-body-part-l
4 + verification-l
5 ! PDU-X
6 ? PDU Y [IUT-TYPE = option__:?] 6
(VARIABLE := 1) 7
8 + verification-2
9 -I- test-body-part-n
10 + verification-n
Detailed Comments:
The ’ +’ symbol indicates the attachment of a TTCN tree.
Trees attached at the same level of indentation are alternatives.
Event line starting with ‘!’ is a send event in TTCN.
Event line starting with ‘?’ is a receive event in TTCN.
The operation ‘: = ’ is an assignment in TTCN.
--__I_-
tion sequences to be used as a test conclusion
4.5 Preamble
sequence. Other valid verification sequences that
The Preamble of a test case consists of the steps
may be used are a matter of agreement between the
required to bring the IUT to the appropriate initial
test laboratory and its clients.
state or phase. There may be various alternative
sequences of test steps which can be performed in
order to initialize the WT. The preamble may depend
4.7 IlJT initiated actions
on the test method as well as specific IUT behavior
that can be controlled or observed using that method.
The general principles, with respect to IUT initiated
Therefore, preambles may be different for different
actions required by this test suite, are in accordance
1 UTs. In order to properly initialize a test case an
with lSO/lEC 8882-l. The ability of the IUT to perform
appropriate preamble has to be used for testing a
these actions, and its ability to initiate the tests con-
particular IUT. An inconclusive verdict in the pre-
taining the actions, are determined by the information
amble may be the result either of protocol violation or
provided in the PIXIT.
of the fact that the preamble is unsuitable for that
Clause “Preambles” gives examples
particular IUT.

of preambles to be used as a test initialization 4.8 Acceptable unexpected IUT frames

sequence. Other valid preambles that may be used

are a matter of agreement between the test labora- The test cases in this test suite indicate the frames

tory and its client. from the IUT required to satisfy the test purpose. In
some cases, particularly in the Information Transfer
phase, unexpected frames may be received from the
4.6 Verification sequence
IUT which do not affect the final test verdict.
The conclusion of a test case is conducted in the test
Acceptable unexpected frames are accepted by the
In most
sequence called a verification sequence.
tester without affecting the final test verdict. In the
cases the verification sequence depends on the final
case of RNR, the tester shall suspend the test until
state in which the IUT is expected to be as a result of
the busy condition is cleared (see Table 3, item 7b).
a test stimulus. A single test case may have more
than one possible verification sequence depending on
In a controlled environment, DISC and SABM com-
the actual IUT behavior. Also, like the preamble, the
mands and DM responses sent by the IUT are not
verification sequence may depend on the testing
considered to be acceptable unexpected frames
method used or may depend on the IUT. Clause
during information transfer tests.
‘Verification sequences” gives examples of verifica-
---------------------- Page: 11 ----------------------
ISO/IEC 8882-2 : 1995 (E)
0 lSO/IEC
4.9 Transient states 4.11 Declarations

A transient state is an unstable state that may pre- The purpose of TTCN declarations is to describe the

clude satisfactory conduct of tests contained in set of test events and all other attributes to be used

clauses “Verification of the disconnected phase,” in the test suite. For further information on TTCN

“Verification of frame reject condition” and “Verifica- declarations see lSO/IEC 9646-3.

tion of IUT busy condition.” To conduct tests in these

clauses the IUT must be capable of: For the X.25 Data Link Layer test suite, the declara-

tions are based on Protocol Data Units (PDUs) defined
l Being forced to establish a particular data link
in OSI Basic Reference Model [lSO/lEC 7498-l] are
condition or phase as part of the test preamble,
called “frames” in the X.25 standards. The PDUs are
by using the LAPB procedures as defined in X.25
declared with a set of PDU parameters that may be
standards.
assigned values for the purpose of testing. The PDU
* Maintaining the established condition for a period
constraints (specified in clause “ASN.l PDU constraint

of time sufficient for the tester to initiate and declarations”) are the list of values that the PDU

conduct the required test steps in an orderly and parameters must take in a particular test event.

observable manner.
The improper PDUs are declared only for the purpose
l Arriving at a prescribed, predictable condition or
of use within ISO/IEC 8882. It is recognized that many
phase for the verification of the test, and main-
variations are possible in an improper PDU, all of
taining that condition for a time sufficient to
which may cause the same reaction from the IUT. It is
record the results from the verification sequence.
not practical to exhaustively list all these variations.
To preserve the flexibility of improper PDU encoding,
lSO/IEC 8882 shows some typical examples.
4.10 Unreachable states
The FCS octets are not shown in the data type decla-
An unreachable state is a state never entered by
rations in this test suite.
some IUTs. This may preclude satisfactory conduct of
tests contained in clauses “Verification of the IUT link
disconnection phase,” “Verification of link setup
4.12 Order of bit transmission
phase” and “Verification of IUT busy condition.”
The order of bit transmission for the PDUs in the dec-
larations above shall be as defined in the X.25 stand-
ards. The order of bit transmission for PDUs in the
declarations for ABORT, HEX and FCS ERROR is illus-
trated in the example shown in Figure%
First bit transmitted Last bit transmitted
i-- c
12345678 12345678
12345678
11000000 11111100 10001000
='03'H
='3F'H ='Il'H
Most significant bits of Octets
Least significant bits of Octets

NOTE - This example does not show flags, FCS fields, and bits inserted for transparency.

Figure 2 - Example - Hex (String:=‘033Fll’H)
---------------------- Page: 12 ----------------------
0 lSO/IEC
ISO/IEC 8882-2 : 1995 (E)
tion Conformance Statement (PICS) proforma which is
4.13 PIXIT proforma
being developed as an amendment to ISO/IEC 7776.
It is essential that the client provide the test labora-
A mnemonic enclosed in parenthesis, e.g. (N2), indi-
tory with all the information (in addition to that given
cates the test suite parameter that maps to this PIXIT
in the PICS) that will enable the appropriate test
cases to be applied to the IUT. This information is question.
provided in the Protocol Implementation extra Infor-
mation for Testing (P1XlT). This PIXIT proforma is
related to and dependent on the Protocol Impiementa-

Table 3 (Page 1 of 2). Protocol Implementation extra Information for Testing (PIXIT)

Item General Information

1 Classification of IUT, select one of ISO-7776, X25-1980, X25-1984, if conformance is Value:

claimed to ISO/lEC 7776, X.25 1980 or 1984 respectively. (IUT-TYPE)
2 The value of k used by IUT. (k) Value:

3 The value of the maximum estabiished length of the information field of the received I Value:

frames. (MEL)
4 The value of N2 for IUT. (N2)
Value:
The value of Tl parameter, in milli-seconds, used by the IUT. (Tl-ONE)
5 Value:
Md Which MODULO base is used for these tests? (Md) Value:
Item Procedural Information Values

6 IUT will initiate transmission of I frames on entering information transfer tests. q Yes ONo

6a IUT acknowledges I frames immediately so that it can handle a full window of I q lYes L7No

frames within timer T1/2. (IUT-ACK)

7a IUT can be made to enter the busy condition when required for testing. UYes q lNo

(IUT SEND RNR)
- -

7al If yes to 7a, specify the time, in miili-seconds, the IUT will remain busy. Value:

7b Specify if IUT will send RNR after link set-up (e.g., this may correspond to a situation UYes ClNo

where RNR is used while higher level is being set up).

7bl If yes to 7b, enter the MAXIMUM time, in milli-seconds, the IUT will be in busy condi- Value:

tion. (Tb)

8 IUT can be made to initiate link disconnection when required for testing. CJYes LlNo

(IUT SEND DISC)
- -

8a Is manual intervention required to initiate link disconnection when required for IllYes ClNo

testing.
8al If yes to 8a, specify the time, in milli-seconds. Value:

9 State the time in milli-seconds the tester must wait before determining that the IUT Value:

will not respond to a tester stimulus. This value will be tester parameter Td. Note:

id < Tl. (Td)

IOa IUT can be made to set-up the link when required for testing. (IUT-SETUP-LINK) ClYes ClNo

IOal If yes to IOa, specify PIGS item under “Link set-up (reset) procedure” to be used. PIGS item:

IOb IUT can request the tester to set-up the link when required. (TEST-DM) ClYes ClNo

IUT can maintain the disconnected phase as a stable state for a period of time. q lYes L7No

(STABLE DP)

Ila If yes to 11, specify the time, in milli-seconds, IUT will remain in disconnected phase. Value:

During this time period the IUT will not unilaterally send a SABM, DISC, or DM frame.

12 The IUT can maintain the frame reject condition as a stable state for a period of time. UYes UNo

(STABLE-FRMR)

If yes to 12, specify the time, in milli-seconds, IUT will remain in frame reject condi- Value:

12a
tion.

13a Upon reaching the disconnected phase, will the HJT reply with DM response to all UYes UNo

commands received, and not set up the data link until some operator action is taken.

(DMRSP)
---------------------- Page: 13 ----------------------
ISO/IEC 8882-2 : 1995 (E) 0 lSO/IEC
Table 3
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.