ISO/IEC 8327-2:1996
(Main)Information technology — Open Systems Interconnection — Connection-oriented Session protocol: Protocol Implementation Conformance Statement (PICS) proforma
Information technology — Open Systems Interconnection — Connection-oriented Session protocol: Protocol Implementation Conformance Statement (PICS) proforma
Technologies de l'information — Interconnexion de systèmes ouverts (OSI) — Protocole de session en mode connexion: Formulaire de déclaration de conformité d'instance de protocole (PICS)
General Information
Standards Content (Sample)
INTERNATIONAL lSO/IEC
8327-2
STANDARD
First edition
1996-I O-01
Information technology - Open Systems
interconnection - Connection-oriented
Session protocol: Protocol Implementation
Conformance Statement (PIGS) proforma
Technologies de /‘information - lnterconnexion de syst&mes
Protocole de session en mode orien t4 connexion:
ouverts (OS/) -
Formulaire de dbclaration de conformit de la mise en euvre du protocole
(PIG)
Reference number
&O/I EC 8327-2: 1996(E)
ISO/IEC 8327-2: 1996(E)
Contents
Page
1 Scope .
.....................................................................................................................................
2 Normative references
........................................................................
Identical Recommendations I International Standards
2.1
..........................
Paired Recommendations I International Standards equivalent in technical content
2.2
Definitions .
.................................................................................................................................................
4 Abbreviations
..................................................................................................................................................
5 Conformance
Annex A - Protocol Implementation Conformance Statement (PICS) Proforma for the Connection-Oriented
......................................................................................................................................
Session Protocol
.......................................................................................
A.1 Identification of PICS proforma corrigenda
..........................................................................................................................................
A.2 Instructions
..............................................................................
A.2.1 Purpose and structure of the proforma
....................................................................................
Symbols, terms and abbreviations
A.2.2
Introduction .
A.2.2.1
...............................................................................................
A.2.2.2 Item numbering
Status column .
A.2.2.3
...............................................................................................
A.2.2.4 Support column
Value column .
A.2.2.5
Mnemonic column .
A.2.2.6
A.2.2.7 Length column .
...............................................................................................
A.2.3 Instructions for completion
...................................................................................................
A.3 Identification of the implementation
..............................................................................................................
Date of statement
A.3.1
......................................................................................................
A.3.2 Implementation details
........................................................................................................................
A.4 Protocol Identification
......................................................
ITU-T Rec. X.225 I ISOAEC 8327-l protocol details
A.4.1
...................................................
A.4.2 ITU-T Rec. X.225 I ISOLIEC 8327-l protocol versions
technical corrigenda implemented. .
A.4.3 ITU-T Rec. X.225 I ISO/IEC 8327-l
.......................................................................................................
A.5 Global statement of conformance
........................................................................
A.6 Supported functional units and protocol mechanisms
.................................................................................................................
A.6.1 Functional units
Protocol mechanisms .
A.6.2
0 ISO/IEC 1996
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 l Case postale 56 l CH-1211 Gen&ve 20 l Switzerland
Printed in Switzerland
ii
ISO/IEC 8327-2: 1996(E)
0 ISO/IEC
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.7 Supported SPDUs
....................................................................................................... 10
A.7.1 Kernel functional unit
A.7.1.1 Supported roles .
.............. 11
A.7.1.2 Support for the SPDUs associated with the Kernel functional unit.
.............................. 11
A.7.1.3 Support for the SPDUs associated with Token Exchange
................................................................................... 11
A.7.2 Negotiated Release functional unit
A.7.2.1 Supported roles .
A.7.2.2 Support for the SPDUs associated with the Negotiated Release functional
unit .
.............................................................................................. 12
A.7.3 Half Duplex functional unit
A.7.3.1 Supported roles .
..... 12
A.7.3.2 Support for the SPDUs associated with the Half Duplex functional unit.
A.7.4 Duplex functional unit .
.........................................................................................
A.7.5 Expedited Data functional unit
Supported roles .
A.7.5.1
..
A.7.5.2 Support for the SPDU associated with the Expedited Data functional unit.
...............................................................................................
A.7.6 Typed Data functional unit
Supported roles .
A.7.6.1
........
Support for the SPDU associated with the Typed Data functional unit.
A.7.6.2
.........................................................................................
Capability Data functional unit
A.7.7
...............................................................................................
A.7.7.1 Supported roles
Support for the SPDUs associated with the Capability Data functional unit.
A.7.7.2
....................................................................................
Minor synchronize functional unit
A.7.8
...............................................................................................
A.7.8.1 Supported roles
Support for the SPDUs associated with the Minor synchronize functional
A.7.8.2
unit .
............................................................................
A.7.9 Symmetric synchronize functional unit
Supported roles .
A.7.9.1
A.7.9.2 Support for the SPDUs associated with the Symmetric synchronize
.................................................................................................
functional unit
..........................................................................................
A.7.10 Data separation functional unit
....................................................................................
A.7.11 Major synchronize functional unit
...............................................................................................
A.7.11.1 Supported roles
A.7.11.2 Support for the SPDUs associated with the Major synchronize functional
..................................................................................................................
unit
..........................................................................................
A.7.12 Resynchronize functional unit
A.7.12.1 Supported roles .
.......................................................................
A.7.12.2 Supported resynchronize types
. 15
A.7.12.3 Support for the SPDUs associated with the Resynchronize functional unit.
................................................................................................
Exceptions functional unit
A.7.13
...............................................................................................
A.7.13.1 Supported roles
......... 16
A.7.13.2 Support for the SPDUs associated with the Exceptions functional unit
................................................................................
A.7.14 Activity management functional unit
A.7.14.1 Supported roles .
A.7.14.2 Support for the SPDUs associated with the Activity management functional
unit .
..............................................................................................................
A.8 Supported SPDU-parameters
.........................................................................................................
A.8.1 Connect (CN) SPDU
......................................................................................
Connection Identifier
A.8.1.1
.......................................................................................
A.8.1.2 Connect/Accept Item
Single Items .
A.8.1.3
..........................................................................................
Overflow Accept (OA) SPDU
A.8.2
.............................................................................
A.8.3 Connect Data Overflow (CDO) SPDU
..e
ISOiIEC 8327-2: 1996(E)
o ISO/IEC
A.8.4 Accept (AC) SPDU . 20
...................................................................................... 20
A.8.4.1 Connection Identifier
A.8.4.2 Connect/Accept Item . 20
A.8.4.3 Single Items .
............................................................................................................ 21
A.8.5 Refuse (RF) SPDU
21 .
A.8.5.1 Connection Identifier .
.................................................................................................... 22
A.8.5.2 Single Items
A.8.6 Finish (FN) SPDU . 22
A.8.7 . 22
Disconnect (DN) SPDU
A.8.8 Not Finish (NF) SPDU .
A.8.9 Abort (AB) SPDU .
A.8.10 Abort Accept (AA) SPDU . 23
A.8.11 Data Transfer (DT) GPDU . 23
A.8.12 . 23
Expedited Data (EX) SPDU
A.8.13 Typed Data (TD) SPDU .
A.& 14 Capability Data (CD) SPDU .
A.8.15 Capability Data Ack (CDA) SPDU . 24
..................................................................................................
A.8.16 Give Tokens (GT) SPDU
................................................................................................
A.8.17 Please Tokens (PT) SPDU
A.8.18 Minor Sync Point (MIP) SPDU .
......................................................................................... 25
A.8.19 Minor Sync Ack (MIA) SPDU
.......................................................................................
A.8.20 Major Sync Point (MAP) SPDU
........................................................................................
A.8.21 Major Sync Ack (MAA) SPDU
Resynchronize (RS) SPDU .
A.8.22
A.&23 Resynchronize Ack (RA) SPDU .
A.8.24 Prepare (PR) SPDU .
........................................................................................... 27
A.8.25 Exception Report (ER) SPDU
..............................................................................................
A.8.26 Exception Data (ED) SPDU
.................................................................................
A.8.27 Give Tokens Confirm (GTC) SPDU
Give Tokens Ack (GTA) SPDU .
A.8.28
A.8.29 Activity Start (AS) SPDU .
A.8.30 Activity Resume (AR) SPDU .
........................................................................................ 28
A.8.30.1 Linking Information
....................................................................................................
A.8.30.2 Single Items
...........................................................................................
A.8.3 1 Activity Interrupt (AI) SPDU
.................................................................................
A.8.32 Activity Interrupt Ack (AIA) SPDU
........................................................................................... 29 k
Activity Discard (AD) SPDU
A.8.33
................................................................................. 30
Activity Discard Ack (ADA) SPDU
A.8.34
.................................................................................................. 30
A.8.35 Activity End (AE) SPDU
....................................................................................... 30
A.8.36 Activity End Ack (AEA) SPDU
.................................................................................................................
Annex B - List of conditional statements
....................................................... 36
Annex C - List of mnemonics used in the conditional and optional statements
iv
0 ISO/IEC ISO/IEC 8327-2: 1996(E)
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 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.
International Standard ISO/IEC 8327-2 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information
technology, Subcommittee SC 21, Open Systems Interconnection, data management and open distributed processing, in
collaboration with ITU-T. The identical text is published as ITU-T Recommendation X.245.
ISO/IEC 8327 consists of the following parts, under the general title Information technology - Open Systems
Znterconnection - Connection-oriented Session protocol:
- Part 1: Protocol specification
- Part 2: Protocol Implementation Conformance Statement (PIGS) proforma
Annex A forms an integral part of this part of ISO/IEC 8327. Annexes B and C are for information only.
ISO/IEC 8327-2: 1996(E)
o ISO/IEC
Introduction
This Recommendation I International Standard is one of a set of Recommendations I International Standards produced to
facilitate the interconnection of information processing systems. It is related to other Recommendations and International
Standards in the set as defined by the Reference Model for Open Systems Interconnection (see ITU-T Rec. X.200 I
ISOLIEC 7498-l). The Reference Model subdivides the area of standardization for interconnection into a series of layers
of specification, each of manageable size.
of technical agreement outside the
The goal of Open Systems Interconnection is to allow, with a minimum
interconnection standards, the interconnection of information processing systems:
from different manufacturers;
-
under different managements;
- of different levels of complexity; and
- of different technologies.
ITU-T Rec. X.225 I ISO/IEC 8327-l specifies the Connection-Oriented Session Protocol.
To evaluate the conformance of a particular implementation, it is necessary to have a description of the capabilities and
options which have been implemented. Such a description is called a Protocol Implementation Conformance Statement
(PIGS).
This Recommendation I International Standard includes the PICS proforma for the Connection-Oriented Session
Protocol as defined in ITLJ-T Rec. X.225 I ISO/IEC 8327-l.
vi
ISOAEC 8327-2 : 1996 (E)
INTERNATIONAL STANDARD
ITU-T RECOMMENDATION
OPEN SYSTEMS INTERCONNECTION -
INFORMATION TECHNOLOGY -
CONNECTION-ORIENTED SESSION PROTOCOL: PROTOCOL IMPLEMENTATION
CONFORMANCE STATEMENT (PICS) PROFORhIA
Scope
This Recommendation I International Standard provides the Protocol Implementation Conformance Statement (PICS)
proforma for the connection-oriented Session protocol specification KU-T Rec. X.225 I ISO/IEC 8327-l. This PICS
proforma is in compliance with the relevant requirements, and in accordance with the relevant guidance for a PIGS
proforma, given in KU-T Rec. X.296 I ISOLIEC 9646-7. Detail of the use of this proforma is provided in this
Recommendation I International Standard.
The supplier of an implementation which is claimed to conform to ITU-T Rec. X.225 I ISOLIEC 8327-l is required to
complete a copy of the PICS proforma provided in Annex A, and is required to provide the information necessary to
uniquely identify both the supplier and the implementation.
2 Normative references
The following Recommendations and International Standards contain provisions which, through reference in this text,
constitute provisions of this Recommendation I International Standard. At the time of publication, the editions indicated
were valid. All Recommendations and Standards are subject to revision, and the parties to agreement based on this
Recommendation I International Standard are encouraged to investigate the possibility of applying the most recent
edition of the Recommendations and Standards indicated below. Members of IEC and IS0 maintain registers of
currently valid International Standards. The Telecommunications Standardization Bureau of the ITU maintains a list of
currently valid ITU-T Recommendations.
21 . Identical Recommendations I International Standards
-
ITU-T Recommendation X.200 (1994) I ISOLIEC 7498-l : 1994, Infomzation technotogy - Open Systems
Interconnection - Basic Reference Model: The Basic Model.
-
ITU-T Recommendation X.214 (1993) I ISO/IEC 8072:1994, Information technozogy - Open Systems
Interconnection - Transport service definition.
-
ITU-T Recommendation X.215 (1995) I ISO/IEC 8326: 1996, Information technology - Open Systems
Interconnection - Session service definition.
-
ITU-T Recommendation X.225 (1995) I ISOLIEC 8327-l : 1996, Information technology - Open Systems
Interconnection - Connection-oriented Session protocol - Protocol specification.
22 . Paired Recommendations I International Standards equivalent in technical content
-
ITU-T Recommendation X.290 (1995), OSI conformunce testing methodology and framework for
protocol Recommendations for ITU-T applications - General concepts.
ISO/IEC 9646- 1: 1994, Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 1: General concepts.
ITU-T Rec. X.245 (1995 E)
ISO/IEC 8327-2 : 1996 (E)
- ITU-T Recommendation X.296 (1995), OSI conformunce testing methodology and framework for
protocol Recommendations for ITU-T applications - Implementation conformance statements.
ISO/IEC 9646-711995, Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 7: Implementation Conformance Statements.
3 Definitions
For the purposes of this Recommendation I International Standard, the following definitions apply.
31 . Terms defined in ITU-T Rec. X.225 I ISO/IEC 8327-l.
32 . The following terms defined in ITU-T Rec. X.290 I ISOLIEC 9646-l:
a) Protocol Implementation Conformance Statement (PIGS);
b) PICS proforma.
33 . Additional terms:
- Requestor: the SPM that initiates a particular action;
- Acceptor: the SPM that accepts a particular action.
4 Abbreviations
41 l Abbreviations are given in ITU-T Rec. X.225 I ISOAEC 8327-l and in clause 8.
This Recommendation I International Standard makes use of the following abbreviation given in KU-T
iec. X.290 I ISOAEC 9646-l:
-
PIGS.
43 . For the purposes of this Recommendation I International Standard, the following abbreviations also apply:
StS Status column
Support column
SPt
Sdr Sender
Rev Receiver
5 Conformance
A conforming PICS shall be technically equivalent to the ITU I ISOLIEC published PICS proforma and shall preserve the
numbering and ordering of the items in the ITU I ISOLIEC PICS proforma.
A PICS which conforms to this Recommendation I International Standard shall:
a) describe an implementation which conforms to ITU-T Rec. X.225 I ISO/IEC 8327-l;
b) be a conforming PICS proforma, which has been completed in accordance with the instructions for
completion given in A.2;
include the information necessary to uniquely identify both the supplier and the implementation.
C)
2 ITU-T Rec. X.245 (1995 E)
ISO/IEC 8327-2 : 1996 (E)
Annex A
Protocol Implementation Conformance Statement (PICS) Proforma
for the Connection-Oriented Session Protocol’)
(This annex forms an integral part of this Recommendation I International Standard)
Al 0 Identification of PICS proforma corrigenda
The supplier of the PICS proforma shall identify any corrigenda (i.e. Technical Corrigenda or equivalent) to the
published proforma that have been applied. Suppliers of the proforma should modify the proforma, or attach relevant
additional pages in order to apply the corrigenda, and then record the application of the corrigenda in the table below.
ITU-T Rec. X.245 (1995) I ISO/IEC 8327-2: 1996
Identification of corrigenda applied to this PICS proforma
corr:
cot-r:
con-:
A2 l Instructions
A.2.1 Purpose and structure of the proforma
The purpose of this PICS proforma is to provide suppliers of implementation of ITU-T Rec. X.225 I ISOLIEC 8327-l
with a consistent means of stating which capabilities have been implemented.
The proforma is in form of a questionnaire and consists of a set of items. An item is provided for each capability for
which an implementation choice is allowed. Items are also provided for major mandatory capabilities for which no
implementation choice is allowed. Each item includes an item number, an item description, a status value specifying the
support requirement, and room for a support answer to be provided by the supplier.
This clause provides general information and instructions for completion of the proforma.
Subclause A.3 is for identification of the implementation.
Subclause A.4 contains the means of specifying, at high level, the protocol and corrigenda that have been implemented.
Subclause A.5 contains the global statement of conformance.
Subclauses A.6 onwards contain tables in which the supplier specifies details of the implementation options chosen.
NOTE - Throughout the PICS proforma, tables specifying Requestor and Accpetor roles are inserted as required for
precise definition of the status of SPDUs and SPDU parameters, but these tables shall not be used for static conformance review nor
for test case selection.
A.2.2 Symbols, terms and abbreviations
A.2.2.1 Introduction
Notations have been introduced in order to reduce the size of tables in the PICS proforma. These have allowed the use of
‘Support’, ‘Value’, ‘Mnemonic’ and ‘Length’. The definition of
multi-column layout where the colums are headed ‘Status’,
each are given below.
Additionally, the following definitions apply.
A.2.2.1.1 (PICS) item: A row in a PICS proforma table.
‘) Copyright release f o r PICS proformas: Users of this Recommendation I International Standard may freely reproduce the PICS proforma in this
annex so that it can be used for its intended purpose and may further publish the completed PICS.
IT&T Rec. X.245 (1995 E)
ISO/IEC 8327-2 : 1996 (E)
A.2.2.1.2 (PICS) question: The question to be answered in the intersection of a PICS item and either a support column
(i.e. “Is this item supported in the context applying to this table and column”) or supported values column (i.e. “What
values are supported for this item in the context applying to this table and column”) in a PICS proforma table.
A.2.2.1.3 status (value): An allowed entry in the status column for an item in a PICS proforma table.
A.2.2.1.4 (support) answer: An allowed entry in the support or supported values columns for an item in a PICS, in
answer to a PICS question.
A.2.2.2 Item numbering
Each line within the PICS proforma which requires implementation detail to be entered is given an item number in the
first column. The item number column provides a means of uniquely referencing each possible answer within the PICS
proforma. Such referencing is necessary for specifying predicates, conditional expressions, test suite parameters, and test
suite selection expressions.
The means of referencing individual answers is to specify the following sequence:
if, and only if, the reference is being made from another Specification, then start with an unambiguous
a)
identifier for the relevant ICS proforma specification, enclosed in parentheses - this identifier is stated in
the PICS proforma specification and is updated whenever the PICS proforma is updated - it is
recommended that this identifier should be relevant Specification number and year of publication, as is
used in a Normative References clause, and this is the default for such identifiers;
the number of the relevant table or, if the tables are not numbered, of the smallest subclause enclosing the
b)
relevant table;
a solidus character, “/“;
c)
d) the item number or mnemonic reference to the item, to identify the row in which the answer appears;
if, and only if, more than one question occurs in the row identified by the item number or mnemonic
e)
from left to right, and this letter is
reference, then each possible answer is implicitly labelled a, b, c, etc.,
appended to the sequence, prefixed by a solidus character (“/“) if a mnemonic reference is used.
If mnemonic references are specified and each uniquely identify an item in the PICS proforma, then
entries b) and c) in the above sequence may be omitted.
A.2.2.3 Status column
This column indicates the level of support required for conformance to ITU-T Rec. X225 I ISO/IEC 8327-l) the given
values are taken from the Session Protocol Specification (see ITU-T Rec. X.225 I ISO/IEC 8327-l).
A.2.2.3.1 Deftitions applying to the tables in clauses A.4 to A.6
The values are as follows:
- ‘m’ Mandatory support is required. The implementation shall support the functionalities described in
ITU-T Rec. X.225 I ISO/IEC 8327-l for the specified item.
t t
-
0 Optional support is permitted for conformance to ITU-T Rec. X.225 I ISO/IEC 8327-l. According
to some specific reason, the implementation is not obliged to support the specified item. If
implemented, it shall conform to the specifications and restrictions contained in ITU-T Rec. X.225 I
ISO/IEC 8327-l. Therefore the constraints described for the mandatory support above also apply.
- ‘o.lt’ Selectable options among a set of items (where yt is the number which identifies the group of
optionals which are linked together). The implementation shall support at least one of the given
items. [For the selected item(s), the constraints described for the mandatory support above also
aPPlY*l
-
The item is conditional (where it is the number which identifies the condition which is applicable).
‘cd
The definitions for the conditional statements used in Annex A are written under the table where
they are used, and indexed in Annex B.
-
‘n/a’ The item is not applicable.
4 IT&T Rec. X.245 (1995 E)
ISOAEC 8327-2 : 1996 (E)
A.2.2.3.2 Definitions applying to the tables in clause A.7 (Supported SPDUs)
The values are as follows:
Sender item:
-
‘m’ Mandatory support is required. The implementation shall be able:
to build the SPDU (i.e. to build correctly the heading and all the mandatory parameters within
the SPDU) in the situations required by the Protocol Machine; and
to encode the SPDU into the TSDU, according to a valid encoding format.
-
‘0’ Optional support is permitted for conformance to ITU-T Rec. X.225 I ISO/IEC 8327-l. According
to some specific reason, the implementation is not obliged to be able to build the SPDU. If
implemented, it shall conform to the specifications and restrictions contained in ITU-T Rec. X.225 I
ISO/IEC 8327-l. Therefore the constraints described for the mandatory support above also apply.
-
‘O.IZ’ Selectable options among a set of items (where n is the number which identifies the group of
optionals which are linked together). The implementation shall support at least one of the given
items. [For the selected item(s), the constraints described for the mandatory support above also
apply*1
-
‘cn’ The item is conditional (where n is the number which identifies the condition which is applicable).
The definitions for the conditional statements used in Annex A are written under the table where
they are used, and indexed in Annex B. Resolution of the condition (e.g. depending on protocol
version, protocol mechanism, etc.) yields to ‘m’, ‘0’ or ‘n/a’.
-
‘n/a’
The item is not applicable.
Receiver item:
-
Mandatory support is required. The implementation shall be able:
‘m’
to syntactically identify the SPDU [i.e. to decode the heading and all of the parameters which are
present (Type and Length in TLV coding scheme)]; and
to process it correctly.
-
‘0’ Optional support is permitted for conformance to ITU-T Rec. X.225 I ISO/IEC 8327-l. If
implemented, it shall conform to the specifications and restrictions contained in KU-T Rec. X.225 I
ISO/IEC 8327- 1. Therefore the constraints described for the mandatory support above also apply.
-
‘0.11’
Selectable options among a set of items (where n is the number which identifies the group of
optionals which are linked together). The implementation shall support at least one of the given
items. [For the selected item(s), the constraints described for the mandatory support above also
aPPlY*l
-
‘cn’ The item is conditional (where n is the number which identifies the condition which is applicable).
The definitions for the conditional statements used in Annex A are written under the table where
they are used, and indexed in Annex B. Resolution of the condition (e.g. depending on protocol
version, protocol mechanism, etc.) yields to ‘m’, ‘0’ or ‘n/a’.
-
‘n/a’ The item is not applicable.
A.2.2.3.3 Definitions applying to the tables in clause A.8 (Supported SPDU parameters)
NOTE - The status indicated for the parameters reflects static conformance requirements. The details about the use of
these parameters in specific instances of communications (i.e. dynamic conformance) are to be found in the Session protocol standard
(ITU-T Rec. X.225 I ISO/IEC 8327-l). It is reminded that a parameter with the Length equal to zero shall be considered as absent.
The values are as follows:
Sender item:
-
‘m’ is required. The implementation encode
Mandatory support shall be able to build and to this
parameter within the appropriate SPDU.
-
‘0’ Optional support is permitted for conformance to ITU-T Rec. X.225 I ISO/IEC 8327-l. According
to some specific reason, the implementation is not obliged to be able to build the parameter. If
implemented, it shall conform to the specifications and restrictions contained in ITU-T Rec. X.225 I
ISO/IEC 8327-l. Therefore the constraints described for the mandatory support above also apply.
ITU-T Rec. X.245 (1995 E)
ISO/IEC 8327-2 : 1996 (E)
-
‘cn’ The item is conditional (where n is the number which identifies the condition which is applicable).
The definitions for the conditional statements used in Annex A are written under the table where
they are used, and indexed in Annex B. Resolution of the condition (e.g. depending on protocol
version, protocol mechanism, etc.) yields to ‘m’, ‘0’ or ‘n/a’.
- ‘n/a’ The item is not applicable.
Receiver item:
- ‘m’ Mandatory support is required. The implementation shall be able to syntactically and semantically
identify the SPDU parameter and to process it correctly.
I I
-
Optional support is permitted for conformance to KU-T Rec. X.225 I ISO/IEC 8327-l. If
implemented, it shall conform to the specifications and restrictions contained in ITU-T Rec. X.225 I
ISO/IEC 8327-l. Therefore the constraints described for the mandatory support above also apply.
-
‘cn’ The item is conditional (where n is the number which identifies the condition which is applicable).
The definitions for the conditional statements used in Annex A are written under the table where
they are used, and indexed in Annex B. Resolution of the condition (e.g. -depending on protocol
version, protocol mechanism, etc.) yields to ‘m’, ‘0’ or ‘n/a’.
- ‘n/a’ The item is not applicable.
A.2.2.4 Support column
shall be completed by the supplier or implementor to indicate the level of implementation of each
The ‘Support’ column
feature. The proforma has been designed such that the only entries required in the ‘Support’ column are:
If the Status column yields to ‘m’ or ‘o’, the following answers are valid:
‘Y’ Yes, the feature has been implemented.
'N No, the feature has not been implemented.
If the Status column yields to ‘n/a’, the unique following answer is valid:
‘-’ Not applicable.
A.2.2.5 Value column
The ‘Value’ column requires the specification of the range of values implemented for a feature, where relevant.
A.2.2.6 Mnemonic column
The ‘Mnemonic’ column is given to facilitate the interpretation of the conditional statements throughout the PICS
proforma.
The mnemonics are designed so that the implementor should easily understand their contents. Their names are generated
as follows:
a character identifying the Session layer (S);
b) an hyphen character;
a sequence of character which is derived, where possible, from the abbreviations used in the Session
C)
protocol specification.
A full alphanumerical list of all the defined ‘Mnemonics’ is given in Annex C.
A.2.2.7 Length column
The ‘Length’ column is given for information only in A.8, in order to indicate a specific length requirement for a
parameter. Otherwise, it is recommended not to fill in this column.
If values are given in the ‘Support’ columns (Sender and/or Receiver), they shall conform to the value(s) given in the
‘Status’ column.
6 ITU-T Rec. X.245 (1995 E)
ISO/IEC 8327-2 : 1996 (E)
The values are as follows:
I I
-
X A specific number of octets is given in ITU-T Rec. X.225 I ISO/IEC 8327-l.
-
‘O-y’ A range of number of octets is given in ITU-T Rec. X.225 I ISOLIEC 8327-l.
-
For a specific reason (total length of the SPDU), an explicit range of number of octets can
‘see Ref.’
not be given in the PICS proforma. For more details, the implementor shall refer to ITU-T
Rec. X.225 I ISO/IEC 8327-l.
A.2.3 Instructions for completion
The supplier shall complete all entries in the column marked ‘Support’. In certain clauses of the PICS proforma further
guidance for completion may be necessary. Such guidance shall supplement the guidance given in this clause and shall
have a scope restricted to the clause in which it appears. In addition, other specifically identified information shall be
provided by the implementor where requested. No changes shall be made to the proforma except the completion as
required. Recognising that the level of detail required may, in some instances, exceed the space available for responses a
number of responses specifically allow for the addition of appendices to the PICS.
A3 . Identification of the implementation
A.3.1 Date of statement
1 1 1 Date of statement? (yy-mm-dd)
I
Implementation details
A.3.2
The supplier of the protocol implementation shall specify the information necessary to uniquely identify the
implementation and the system in which it may reside. This may include details of:
supplier, implementation name, operating system, suitable hardware;
a>
b) system supplier and/or client of the test laboratory that is to test the implementation;
c) information on whom to contact if there are queries concerning the content of the PICS.
ITU-T Rec. X.245 (1995 E)
ISO/IEC 8327-2 : 1996 (E)
Protocol Identification
A4 0
A.4.1 IT&T Rec. X.225 I ISO/IEC 8327-l protocol details
Identification of Protocol Specification support Comment
I
ITU-T Rec. X.225 (1994) I ISOLIEC 8327-l: 1996
A.4.2 IT&T Rec. X.225 I ISO/IEC 8327-l protocol versions
Which version of the Session Protocol is described in this PICS?
1 Status 1 Support 1 Mnemonic Comment
1 Version 1 0.1 s-v1
2 Version 2 0.1
o. 1: the implementation of one, and only one, version of the protocol shall be described in this proforma (see below).
I
An implementation shall be described by completing a separate PICS proforma for each supported protocol version.
PICS document for all versions of the protocol for which conformance is claimed should be attached to each other, and
used together.
Which other versions of the Session Protocol does the implementation support?
1 Status 1 Support 1 Comment
3 Version 1 0
4 Version 2 0
A.4.3 IT&T Rec. X.225 I ISOAEC 8327-l technical corrigenda implemented
Identification of corrigenda applied to the implementation IN-T Rec. X.225 (1994) I ISOAEC 8327-l: 1996
Corr:
con-:
con-:
con-:
corr:
A5 0 Global statement of conformance
1 1 Are all mandatory features implemented? (yes or no)
NOTE - If a positive response is not given to this box, then the implementation does not conform to ITU-T Rec. X.225 I
ISOLIEC 8327- 1.
8 IT&T Rec. X.245 (1995 E)
ISO/IEC 8327-2 : 1996 (E)
A.6 Supported functional units and protocol mechanisms
A.6.1 Functional units
Functional Unit 1 Status 1 SupportI- Mnemonic Comment
~~~
m
I 1
I I I
I 2 I Negotiated Release 1 S-FWNR) I 1
I 0 I
I 3 I Half DuDlex 0.2 1 1 S-FU(HD) -7
I I
I 4 I Duplex 0.2 1
I s-Fww I I
I
0 ~ 1 S-FU(EX)
1 5 1 Expedited Data (Note) -1
I I I
r 6 TvPed Data 1 S-FU(TD) I 1
I 0 I
I 7 I Canabilitv Data Exchange 1 S-FUKD) -7
I cl I I
I 8 I Minor Svnchronize I s-Fu(SY) I I
I 0 I
9 Symmetric Synchronize 0 s-Fu(SS)
Data Separation c2 S-FU(DS)
1 11 1 Maior Synchronize 0 ~ -1 S-FU(MA)
I I I
12 I Resvnchronize 1 S-FWRESYN) I 1
I 0 I
I 13 I ExceWions I S-FWEXCEP) I
I c3 I I
I 14 I Activity management 1 S-FU(ACT)
I I
I 0 I
units Duplex and Half Duplex shall be implemented.
if [ S-FU(ACT) ] then o else n/a.
if [ S-FU(SY) or S-FU(SS) ] then 0 else n/a.
if [ S-FU(HD) ] then o else n/a.
NOTE - The TRANSPORT Expedited data service is reauired to SUDDOI-~ the SESSION ExDedited data functional unit.
A.6.2 Protocol mechanisms
Range of
Mechanism Status support Mnemonic Comment
values
1 Use of transport expedited data c4 S-EXP-T
(Extended control Quality of Service)
2 Reuse of transport connection 0
S-REUSE-T
3 Basic concatenation m
4 Extended concatenation
(sending) 0
5 Extended concatenation (receiving) 0 S-XCONC-RCV
6 Segmenting (sending) 0
S-SEG-SDR
-
Segmenting
7 (receiving) 0 S-SEG-RCV
8 Max size of
SS-user-data (S-CONNECT) > 512 0 S-MAXSIZE - 5 12
9 Max size of SS-user-data (S-CONNECT) > 10240 0 S-MAXSIZE - 10 240
101 M ax size of SS-user-data (S-ABORT) > 9
F- 1 1 1 S-MAXSIZE- 1 -
-
c4: if [ S-FU(EX) ] then m else o.
NOTES
1 The use of the TRANSPORT Expedited data service is mandatory in order to support the SESSION Expedited data functional
unit, but is also related to the Extended Control of Quality of Service.
2 Two kinds of segmentation exist in the Session protocol. Lines 6 and 7 address the segmentation of SPDUs into several
TSDUs. Lines 8, 9 and 10 adress Session Version 2 (Unlimited User Data and Enclosure Item) with segmentation of an SSDU
into seve
...
lSO/CEI
NORME
8327-2
INTERNATIONALE
Première édition
1996-I O-OI
Technologies de l’information -
Interconnexion de systèmes ouverts
Protocole de session en mode
(OSI) -
connexion: Formulaire de déclaration de
conformité d’instance de protocole (PICS)
Information technology - Open Systems Interconnection - Connection-
orien ted Session pro tocol: Pro tocol Implemen ta tion Con formance
Sta temen t (PICS) pro forma
ISOICEI 8327-2: 1996(F)
Sommaire
Page
1 Domaine d’application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Références normatives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recommandations 1 Normes internationales identiques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1
2.2 Paires de Recommandations 1 Normes internationales équivalentes par leur contenu technique . . . . . . .
Définitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
4 Abréviations
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
5 Conformité
Annexe A - Formulaire de déclaration de conformité d’instance de protocole (PICS) pour le protocole de
................................................................................................................. 3
session en mode connexion
A.1 Identification of PICS proforma corrigenda . 3
Instructions . 3
A.2
A.2.1 Purpose and structure of the proforma . 3
A.2.2 Symbols, terms and abbreviations . 3
Introduction . 3
A.2.2.1
A.2.2.2 Item numbering . 4
A.2.2.3 Status column . 4
A.2.2.4 Support column . 6
A.2.2.5 Value column .
Mnemonic column . 6
A.2.2.6
A.2.2.7 Length column . 6
A.2.3 Instructions for completion . 7
Identification of the implementation . 7
A.3
A.3.1 Date of statement . 7
A.3.2 Implementation details . 7
Protocol Identification . 8
A.4
A.4.1 ITU-T Rec. X.225 1 ISO/IEC 8327-l protocol details . 8
A.4.2 ITU-T Rec. X.225 1 ISO/IEC 8327-l protocol versions .
....................... 8
A.4.3 ITU-T Rec. X.225 1 ISO/IEC 8327-l technical corrigenda implemented.
Global statement of conformance . 8
A.5
Supported functional units and protocol mechanisms . 9
A.6
Functional units . 9
A.6 1
Protocol mechanisms . 9
A.6.2
0 ISOKEI 1996
Droits de reproduction réservés. Sauf prescription différente, aucune partie de cette publication ne
peut être reproduite ni utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou
mécanique, y compris la photocopie et Ies microfilms, sans I’accord écrit de I’éditeur.
ISOKEI Copyright Office l Case postale 56 l CH-121 1 Genève 20 l Suisse
Version française tirée en 1997
Imprimé en Suisse
ii
ISOKEI 8327-2: 1996(F)
0 ISO/CEI
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.7 Supported SPDUs
.......................................................................................................
Kemel functional unit
A.7.1
............................................................................................... 10
A.7.1.1 Supported roles
Support for the SPDUs associated with the Kemel fùnctional unit. .
A.7.1.2
Support for the SPDUs associated with Token Exchange . 11
A.7.1.3
...................................................................................
A.7.2 Negotiated Release functional unit
............................................................................................... 11
A.7.2.1 Supported roles
Support for the SPDUs associated with the Negotiated Release functional
A.7.2.2
unit .
Half Duplex functional unit .
A.7.3
Supported roles .
A.7.3.1
....... 12
Support for the SPDUs associated with the Half Duplex functional unit
A.7.3.2
...................................................................................................... 12
Duplex functional unit
A.7.4
A.7.5 Expedited Data functional unit . 12
A.7.5.1 Supported roles .
.. 12
A.7.5.2 Support for the SPDU associated with the Expedited Data functional unit.
............................................................................................... 12
A.7.6 Typed Data functional unit
Supported roles . 12
A.7.6.1
A.7.6.2 Support for the SPDU associated with the Typed Data functional unit. . 13
Capability Data functional unit . 13
A.7.7
A.7.7.1 Supported roles . 13
A.7.7.2 Support for the SPDUs associated with the Capability Data functional unit.
A.7.8 Minor synchronize functional unit .
A.7.8.1 Supported roles .
Support for the SPDUs associated with the Minor synchronize functional
A.7.8.2
unit . 13
A.7.9 Symmetric synchronize functional unit . 14
A.7.9.1 Supported roles .
Support for the SPDUs associated with the Symmetric synchronize
A.7.9.2
functional unit . 14
A.7.10 Data separation functional unit . 14
A.7.11 Major synchronize functional unit .
A.7.11.1 Supported roles . 14
A.7.11.2 Support for the SPDUs associated with the Major synchronize functional
unit .
.......................................................................................... 15
A.7.12 Resynchronize functional unit
A.7.12.1 Supported roles . 15
A.7.12.2 Supported resynchronize types .
A.7.12.3 Support for the SPDUs associated with the Resynchronize functional unit. . 15
A.7.13 Exceptions functional unit . 15
............................................................................................... 15
A.7.13.1 Supported roles
A.7.13.2 Support for the SPDUs associated with the Exceptions functional unit. . 16
................................................................................ 16
A.7.14 Activity management functional unit
A.7.14.1 Supported roles . 16
A.7.14.2 Support for the SPDUs associated with the Activity management fùnctional
unit . 17
.............................................................................................................. 18
A.8 Supported SPDU-parameters
Connect (CN) SPDU . 18
A.8.1
A.8.1.1 Connection Identifier . 18
....................................................................................... 18
A.8.1.2 Connect/Accept Item
A.8.1.3 Single Items . 19
A.8.2 Overflow Accept (OA) SPDU . 19
Connect Data Overflow (CDO) SPDU . 19
A.8.3
. . .
ISOKEI 8327-2: 1996(F) @ ISOKEI
A.8.4 Accept (AC) SPDU .
A.8.4.1 Connection Identifier
...................................................................................... 20
A.8.4.2 Connect/Accept Item
....................................................................................... 20
A.8.4.3 Single Items .
A.8.5 Refuse (RF) SPDU .
A.8.5.1 Connection Identifier
...................................................................................... 21
A.8.5.2 Single Items .
A.8.6 Finish (FN) SPDU .
A.8.7 Disconnect (DN) SPDU . 22
A.8.8
Not Finish (NF) SPDU. 23
A.8.9 Abort (AB) SPDU
............................................................................................................. 23
A.8.10 Abort Accept (AA) SPDU
................................................................................................ 23
A.8.11 Data Transfer (DT) SPDU .
A.8.12 Expedited Data (EX) SPDU . 23
A.8.13
Typed Data (TD) SPDU. 24
A.8.14 Capability Data (CD) SPDU
............................................................................................. 24
A.8.15 Capability Data Ack (CDA) SPDU .
.................................................................................................. 24
A.8.16 Give Tokens (GT) SPDU
A.8.17 Please Tokens (PT) SPDU . 25
........................................................................................ 25
A.8.18 Minor Sync Point (MIP) SPDU
Minor Sync Ack (MIA) SPDU . 25
A.8.19
....................................................................................... 26
A.8.20 Major Sync Point (MAP) SPDU
A.8.2 1 Major Sync Ack (MAA) SPDU . 26
A.8.22 Resynchronize (RS) SPDU .
Resynchronize Ack (RA) SPDU . 27
A.8.23
........................................................................................................... 27
A.8.24 Prepare (PR) SPDU
Exception Report (ER) SPDU . 27
A.8.25
A.8.26 Exception Data (ED) SPDU.
................................................................................. 28
A.8.27 Give Tokens Confïrm (GTC) SPDU
A.8.28 Give Tokens Ack (GTA) SPDU . 28
................................................................................................. 28
A.8.29 Activity Start (AS) SPDU
A.8.30 Activity Resume (AR) SPDU . 28
........................................................................................ 28
A.8.30.1 Linking Information
A.8.30.2 Single Items . 29
Activity Interrupt (AI) SPDU . 29
A.8.3 1
................................................................................. 29
A.8.32 Activity Interrupt Ack (AIA) SPDU
A.8.33 Activity Discard (AD) SPDU . 29
................................................................................. 30
A.8.34 Activity Discard Ack (ADA) SPDU
.................................................................................................. 30
A.8.35 Activity End (AE) SPDU
A.8.36 Activity End Ack (AEA) SPDU . 30
Annexe B - Liste des déclarations conditionnelles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Annexe C - Liste des mnémoniques utilisés dans les déclarations conditionnelles et optionnelles. . . . . . . . . . . . . . . . . . . . . . .
@ ISOKEI ISOKEI 8327-2: 1996(F)
Avant-propos
L’ISO (Organisation internationale de normalisation) et la CE1 (Commission
électrotechnique internationale) forment ensemble un système consacré à la
normalisation internationale considérée comme un tout. Les organismes nationaux
membres de I’ISO ou de la CE1 participent au développement de Normes inter-
nationales par l’intermédiaire des comités techniques créés par l’organisation
concernée afin de s’occuper des différents domaines particuliers de l’activité
technique. Les comités techniques de I’ISO et de la CE1 collaborent dans des
domaines d’intérêt commun. D’autres organisations internationales, gouverne-
mentales et non gouvernementales, en liaison avec 1’ISO et la CE1 participent
également aux travaux.
Dans le domaine des technologies de l’information, 1’ISO et la CE1 ont créé un
comité technique mixte, I’ISOKEI JTC 1. Les projets de Normes internationales
adoptés par le comité technique mixte sont soumis aux organismes nationaux pour
approbation, avant leur acceptation comme Normes internationales. Les Normes
internationales sont approuvées conformément aux procédures qui requièrent
l’approbation de 75 % au moins des organismes nationaux votants.
La Norme internationale ISO/CEI 8327 a été élaborée par le comité technique
mixte ISOKEI JTC 1, Technologies de I?nformation, sous-comité SC 21,
Interconnexion des systèmes ouverts, gestion des données et traitement distribué
ouvert, en collaboration avec I’UIT-T. Le texte identique est publié en tant que
Recommandation UIT-T X.245.
L’ISOKEI 8327 comprend les parties suivantes, présentées sous le titre général
Technologies de 1 ‘information - Interconnexion de systèmes ouverts (OSI) -
Protocole de session en mode connexion:
Partie I: Spécification du protocole
- Partie 2: Formulaire de déclaration de conformité d’instance de protocole
(PICS)
L’annexe A fait partie intégrante de la présente partie de I’ISOKEI 8327. Les
annexes B et C sont données uniquement à titre d’information.
V
ISOKEI 8327-2: 1996(F)
@ ISOKEI
Introduction
La présente Recommandation 1 Norme internationale fait partie d’un ensemble de Recommandations 1 Normes intematio-
nales élaborées pour faciliter l’interconnexion des équipements informatiques. Les relations entre la présente Recomman-
dation 1 Norme internationale et les autres Recommandations et Normes internationales de l’ensemble sont définies par le
modèle de référence pour l’interconnexion des systèmes ouverts (Rec. UIT-T X.200 1 ISO/CEI 7498-l). Le modèle de
référence subdivise le domaine de la normalisation en vue de l’interconnexion en une série de couches de spécification,
chaque couche étant de taille gérable.
L’interconnexion des systèmes ouverts vise à permettre, moyennant un minimum d’accords techniques en dehors des
normes d’interconnexion, l’interconnexion des équipements informatiques:
-
provenant de divers fabricants;
-
gérés différemment;
-
de niveaux de complexité différents;
-
s’appuyant sur diverses technologies.
La Rec. UIT-T X.225 1 ISO/CEI 8327-l spécifie le protocole de session en mode connexion.
Pour évaluer la conformité d’une application particulière, il est nécessaire de disposer d’une description des capacités
et des options qui ont été incluses. Une telle description est appelée déclaration de conformité d’instance de protocole
(PICS).
La présente Recommandation 1 Norme internationale contient le formulaire PICS pour le protocole de session en mode
connexion, tel qu’il est défini dans la Rec. UIT-T X.225 1 ISO/CEI 8327-l.
ISOKEI 8327-2 : 1996 (F)
NORME INTERNATIONALE
RECOMMANDATION UIT-T
TECHNOLOGIE$ DE L”INFORMATION - INTERCONNEXION
DE SYSTÈMES OUVERTS (OSI) - PROTOCOLE DE SESSION
EN MODE CONNEXION: FORMULAIRE DE DÉCLARATION
DE CONFORMITÉ D’INSTANCE DE PROTOCOLE (PICS)
Domaine d’application
La présente Recommandation 1 Norme internationale décrit le formulaire de déclaration de conformité d’instance de
tel qu’il est spécifié dans la Rec. UIT-T X.225 1 ISO/CEI 8327-1,
protocole (PICS) de session en mode connexion,
conformément aux prescriptions et directives pertinentes de la Rec. UIT-T X.296 1 ISOKEI 9646-7. L’utilisation
détaillée de ce formulaire est décrite dans la présente Recommandation 1 Norme internationale.
Le fournisseur d‘une réalisation déclarée conforme à la Rec. UIT-T X.225 1 ISO/CEI 8327-l est tenu de remplir un
exemplaire du formulaire PICS fourni en Annexe A; il doit également fournir les informations nécessaires pour identifier
ladite réalisation et ledit fournisseur.
Références normatives
Les Recommandations et Normes internationales suivantes contiennent des dispositions qui, par suite de la référence qui
y est faite, constituent des dispositions valables pour la présente Recommandation 1 Norme internationale. Au moment de
la publication, les éditions indiquées étaient en vigueur. Toutes Recommandations et Normes sont sujettes à révision et
les parties prenantes aux accords fondés sur la présente Recommandation 1 Norme internationale sont invitées à
rechercher la possibilité d’appliquer les éditions les plus récentes des Recommandations et Normes indiquées ci-après.
Les membres de la CE1 et de 1’ISO possèdent le registre des Normes internationales en vigueur. Le Bureau de la
normalisation des télécommunications de 1’UIT tient à jour une liste des Recommandations de I’UIT-T en vigueur.
21. Recommandations 1 Normes internationales identiques
-
Recommandation UIT-T X.200 (1994) 1 ISO/CEI 7498-l :1994, Technologies de Z’information -
Interconnexion des systèmes ouverts - Modèle de référence de base: le modèle de référence de base.
-
Recommandation UIT-T X.2 14 (1993) 1 ISO/CEI 8072: 1994, Technologies de Z’information -
Interconnexion des systèmes ouverts - Définition du service de transport.
-
Recommandation UIT-T X.215 (1995) 1 ISOKEI 8326: 1996, Technologies de Z’information -
Interconnexion des systèmes ouverts - Définition du service de session.
-
Recommandation UIT-T X.225 (1995) 1 ISOKEI 8327.1:1996, Technologies de Z’information -
Interconnexion des systèmes ouverts - Protocole de session en mode connexion: spéczjkation.
Paires de Recommandations 1 Normes internationales équivalentes par leur contenu technique
22.
-
Recommandation UIT-T X.290 (1995), Cadre général et méthodologie des tests de conformité
d’interconnexion des systèmes ouverts pour les Recommandations sur les protocoles pour les applications
de Z’UIT-T - Concepts généraux.
ISOKEI 9646-l : 1994, Technologies de l’information - Interconnexion des systèmes ouverts - Cadre
général et méthodologie des tests de conformité OSI - Partie 1: Concepts généraux.
Rec. UIT-T X.245 (1995 F)
ISOKEI 8327-2 : 1996 (F)
-
Recommandation UIT-T X.296 (1995), Cadre général et méthodologie des tests de conformité OSI pour
les Recommandations sur les protocoles pour les applications de ZUT-T - Déclarations de conformité
d’instance.
ISOICEI 9646-7: 1995, Technologies de I?nformation
- Interconnexion des systèmes ouverts (OSI) -
Essais de conformité - Méthodologie générale et procédures
- Partie 7: Déclaration de conformité des
mises en œuvre.
3 Définitions
Pour les besoins de la présente Recommandation 1 Norme internationale, les définitions suivantes s’appliquent.
3.1 Les termes définis dans la Rec. UIT-T X.225 1 ISOKEI 8327-l.
3.2 Les termes suivants, définis dans la Rec. UIT-T X.290 1 ISOKEI 9646-l:
a) déclaration de conformité d’instance de protocole (PICS);
b) formulaire PICS.
3.3 Termes additionnels:
-
demandeur: machine SPM qui lance une action particulière;
-
accepteur: machine SPM qui accepte une action particulière.
,
Abréviations
4.1 Les abréviations sont données dans la Rec. UIT-T X.225 1 ISOKEI 8327-l et dans l’article 8.
4.2 La présente Recommandation 1 Norme internationale utilise l’abréviation suivante définie dans la
Rec. UIT-T X.290 1 ISOKEI 9646-l :
-
PICS Déclaration de conformité d’instance de
protocole (protocol implementation conformance
statement).
4.3 Pour les besoins de la présente Recommandation 1 Norme internationale, les abréviations suivantes
s’appliquent également:
Sts Colonne «Status»
Colonne «Support»
SPt
Str Emetteur
Rcv Récepteur
5 Conformité
Une déclaration PICS conforme doit être techniquement équivalente au formulaire PICS publié par l’UIT-T 1 ISO/CEI
dont elle doit conserver la numérotation et l’ordre des items.
Une déclaration PICS conforme à la présente Recommandation 1 Norme internationale doit:
a) décrire une réalisation qui est conforme à la Rec. UIT-T X.225 1 ISO/CEI 8327-l;
être établie selon un fornmlaire PICS conforme, rempli conformément aux directives indiquées en A.2;
b)
inclure les informations nécessaires pour identifier sans ambiguïté le fournisseur et la réalisation.
Cl
Rec. UIT-T X.245 (1995 F)
ISOKEI 8327-2 : 1996 (F)
Annexe A
Formulaire de déclaration de conformité d’instance de protocole (PICS)
pour le protocole de session en mode connexion’)
(Cette annexe fait partie intégrante de la présente Recommandation 1 Norme internationale)
Identification of PICS proforma corrigenda
Al.
The supplier of the PICS proforma shall identifl any corrigenda (i.e. Technical Corrigenda or equivalent) to the
published proforma that have been applied. Suppliers of the proforma should modify the proforma, or attach relevant
additional pages in order to apply the corrigenda, and then record the application of the corrigenda in the table below.
Identification of corrigenda applied to this PICS proforma ITU-T Rec. X.245 (1995) 1 ISO/IEC 8327.2:1996
con-:
col-r:
con-:
Instructions
A.2
Purpose and structure of the proforma
A.2.1
The purpose of this PICS proforma is to provide suppliers of implementation of ITU-T Rec. X.225 1 ISO/IEC 8327-l
with a consistent means of stating which capabilities have been implemented.
The proforma is in form of a questionnaire and consists of a set of items. An item is provided for each capability for
which an implementation choice is allowed. Items are also provided for major mandatory capabilities for which no
implementation choice is allowed. Each item includes an item number, an item description, a status value specifying the
support requirement, and room for a support answer to be provided by the supplier.
This clause provides general information and instructions for completion of the proforma.
Subclause A.3 is for identification of the implementation.
Subclause A.4 contains the means of specifling, at high level, the protocol and corrigenda that have been implemented.
Subclause A.5 contains the global statement of conformance.
Subclauses A.6 onwards contain tables in which the supplier specifïes details of the implementation options chosen.
NOTE - Throughout the PICS proforma, tables specifling Requestor and Accpetor roles are inserted as required for
precise definition of the status of SPDUs and SPDU parameters, but these tables shall not be used for static conformance review nor
for test case selection.
A.2.2 Symbols, terms and abbreviations
A.2.2.1 Introduction
Notations have been introduced in order to reduce the size of tables in the PICS proforma. These have allowed the use of
multi-column layout where the colums are headed ‘Statu$ ‘Support’, ‘Value’, ‘Mnemonic’ and ‘Length’. The definition of
each are given below.
Additionally, the following definitions apply.
A.2.2.1.1 (PICS) item: A row in a PICS proforma table.
I) Droits de reproduction du formulaire PICS: Les utilisateurs de la présente Recommandation 1 Norme internationale sont autorisés à reproduire le
formulaire PICS de la présente annexe pour utiliser celui-ci conformément à son objet. Ils sont également autorisés à publier le formulaire une fois
celui-ci complété.
Rec. UIT-T X.245 (1995 F) 3
ISO/CEI 8327-2 : 1996 (F)
A.2.2.1.2 (PICS) question: The question to be answered in the intersection of a PICS item and either a support column
(i.e. “1s this item supported in the context applying to this table and column”) or supported values column (i.e. “What
values are supported for this item in the context applying to this table and column”) in a PICS proforma table.
A.2.2.1.3 status (value): An allowed entry in the status column for an item in a PICS proforma table.
A.2.2.1.4 (support) answer: An allowed entry in the support or supported values columns for an item in a PICS, in
answer to a PICS question.
A.2.2.2 Item numbering
Each line within the PICS proforma which requires implementation detail to be entered is given an item number in the
first column. The item number column provides a means of uniquely referencing each possible answer within the PICS
proforma. Such referencing is necessary for specifling predicates, conditional expressions, test suite parameters, and test
suite selection expressions.
The means of referencing individual answers is to specify the following sequence:
if, and only if, the reference is being made fkom another Specification, then start with an unambiguous
a)
identifier for the relevant ICS proforma specification, enclosed in parentheses - this identifier is stated in
the PICS proforma specification and is updated whenever the PICS proforma is updated - it is
recommended that this identifier should be relevant Specifïcation number and year of publication, as is
used in a Normative References clause, and this is the default for such identifïers;
b) the number of the relevant table or, if the tables are not numbered, of the smallest subclause enclosing the
relevant table;
a solidus character, “/“;
C)
d) the item number or mnemonic reference to the item, to identify the row in which the answer appears;
if, and only if, more than one question occurs in the row identified by the item number or mnemonic
e)
reference, then each possible answer is implicitly labelled a, b, c, etc., from left to right, and this letter is
appended to the sequence, prefixed by a solidus character (V’) if a mnemonic reference is used.
If mnemonic references are specified and each uniquely identify an item in the PICS proforma, then
entries b) and c) in the above sequence may be omitted.
A.2.2.3 Status column
This column indicates the level of support required for conformance to ITU-T Rec. X225 1 ISO/IEC 8327-1, the given
values are taken firom the Session Protocol Specification (see ITU-T Rec. X.225 1 ISO/IEC 8327-l).
A.2.2.3.1 Definitions applying to the tables in clauses A.4 to A.6
The values are as follows:
-
‘m’ Mandatory support is required. The implementation shall support the functionalities described in
ITU-T Rec. X.225 1 ISO/IEC 8327-l for the specified item.
t 1
-
0 Optional support is permitted for conformance to ITU-T Rec. X.225 1 ISO/IEC 8327-l. According
to some specifïc reason, the implementation is not obliged to support the specifïed item. If
implemented, it shall conform to the specifïcations and restrictions contained in ITU-T Rec. X.225 1
ISO/IEC 8327-l. Therefore the constraints described for the mandatory support above also apply.
-
'0.d Selectable options among a set of items (where n is the number which identifies the group of
optionals which are linked together). The implementation shall support at least one of the given
items. [For the selected item(s), the constraints described for the mandatory support above also
aPPlYl l
-
The item is conditional (where n is the number which identifies the condition which is applicable).
‘cn’
The definitions for the conditional statements used in Annex A are written under the table where
they are used, and indexed in Annex B.
1 1
-
nla The item is not applicable.
4 Rec. UIT-T X.245 (1995 F)
ISOKEI 8327-2 : 1996 (F)
A.2.2.3.2 Definitions applying to the tables in clause A.7 (Supported SPDUs)
The values are as follows:
Sender item:
-
Mandatory support is required. The implementation shall be able:
‘m’
to build the SPDU (i.e. to build correctly the heading and a11 the mandatory parameters within
the SPDU) in the situations required by the Protocol Machine; and
to encode the SPDU into the TSDU, according to a valid encoding format.
1 1
-
Optional support is permitted for conformance to ITU-T Rec. X.225 1 ISO/IEC 83274. According
to some specifïc reason, the implementation is not obliged to be able to build the SPDU. If
implemented, it shall conform to the specifications and restrictions contained in ITU-T Rec. X.225 1
ISO/IEC 8327-l. Therefore the constraints described for the mandatory support above also apply.
-
Selectable options among a set of items (where n is the number which identifies the group of
‘0.n’
optionals which are linked together). The implementation shall support at least one of the given
items. [For the selected item(s), the constraints described for the mandatory support above also
aPPlY -1
-
The item is conditional (where n is the number which identifies the condition which is applicable).
‘cn’
The definitions for the conditional statements used in Annex A are written under the table where
they are used, and indexed in Annex B. Resolution of the condition (e.g. depending on protocol
version, protocol mechanism, etc.) yields to ‘m’, ‘0’ or Wa’.
1 1
-
n/a The item is not applicable.
Receiver item:
Mandatory support is required. The implementation shall be able:
- ‘m’
to syntactically identify the SPDU [i.e. to decode the heading and a11 of the parameters which are
present (Type and Length in TLV coding scheme)]; and
to process it correctly.
1 1
Optional support is permitted for conformance to ITU-T Rec. X.225 1 ISO/IEC 8327-l. If
- 0
implemented, it shall conform to the specifications and restrictions contained in ITU-T Rec. X.225 1
ISO/IEC 8327-l. Therefore the constraints described for the mandatory support above also apply.
- ‘0.n’ Selectable options among a set of items (where n is the number which identifies the group of
optionals which are linked together). The implementation shall support at least one of the given
items. [For the selected item(s), the constraints described for the mandatory support above also
aPPlYl l
The item is conditional (where n is the number which identifies the condition which is applicable).
- ‘cn’
The definitions for the conditional statements used in Annex A are written under the table where
they are used, and indexed in Annex B. Resolution of the condition (e.g. depending on protocol
version, protocol mechanism, etc.) yields to ‘m’, ‘0’ or Wa’.
1 1
- nla The item is not applicable.
A.2.2.3.3 Definitions applying to the tables in clause A.8 (Supported SPDU parameters)
NOTE - The statu indicated for the parameters reflects static conformance requirements. The details about the use of
these parameters in specifïc instances of communications (i.e. dynamic conformance) are to be found in the Session protocol standard
(ITU-T Rec. X.225 1 ISO/IEC 8327-l). It is reminded that a parameter with the Length equal to zero shall be considered as absent.
The values are as follows:
Sender item:
-
Mandatory support is required. The implementation shall be able to build and to encode this
‘m’
parameter within the appropriate SPDU.
1 1
-
0 Optional support is permitted for conformance to ITU-T Rec. X.225 1 ISO/IEC 8327-l. According
to some specific reason, the implementation is not obliged to be able to build the parameter. If
implemented, it shall conform to the specifïcations and restrictions contained in ITU-T Rec. X.225 1
ISO/IEC 8327-l. Therefore the constraints described for the mandatory support above also apply.
Rec. UIT-T X.245 (1995 F) 5
ISOKEI 8327-2 : 1996 (F)
-
‘cn’ The item is conditional (where n is the number which identifies the condition which is applicable).
The definitions for the conditional statements used in Annex A are written under the table where
they are used, and indexed in Annex B. Resolution of the condition (e.g. depending on protocol
version, protocol mechanism, etc.) yields to ‘m’, ‘0’ or Wa’.
-
‘n/a’ The item is not applicable.
Receiver item:
-
‘m’ Mandatory support is required. The implementation shall
be able to syntactically and semantically
identify the SPDU parameter and to process it correctly.
1 1
-
0 Optional support is permitted for conformance to ITU-T Rec. X.225 1 ISO/IEC 8327-l. If
implemented, it shall conform to the specifications and restrictions contained in ITU-T Rec. X.225 1
ISO/IEC 8327-l. Therefore the constraints described for the mandatory support above also apply.
-
‘cn’ The item is conditional (where n is the number which identifies the condition which is applicable).
The definitions for the conditional statements used in Annex A are written under the table where
they are used, and indexed in Annex B. Resolution of the condition (e.g. depending on protocol
version, protocol mechanism, etc.) yields to ‘m’, ‘0’ or Wa’.
-
‘n/a’ The item is not applicable.
A.2.2.4 Support column
.l be completed by the supplier or implementor to indicate the level of implementation
The ‘Support’ column shal of each
feature. The proforma has been designed such that the only entries required in the ‘Support’ column are:
If the Status column yields to ‘m’ or ‘o’, the following answers are valid:
Yes, the feature has been implemented.
‘Y’
PJ’ No, the feature has not been implemented.
If the Status column yields to Wa’, the unique following answer is valid:
‘-’ Not applicable.
A.2.2.5 Value column
The ‘Value’ column requires the specifïcation of the range of values implemented for a feature, where relevant.
A.2.2.6 Mnemonic column
The ‘Mnemonic’ column is given to facilitate the interpretation of the conditional statements throughout the PICS
proforma.
The mnemonics are designed SO that the implementor should easily understand their contents. Their names are generated
as follows:
a character identifling the Session layer (S);
a)
an hyphen character;
b)
a sequence of character which is derived, where possible, from the abbreviations used in the Session
Cl
protocol specifïcation.
A full alphanumerical list of a11 the defïned ‘Mnemonics’ is given in Annex C.
A.2.2.7 Length column
The ‘Length’ column is given for information only in A.8, in order to indicate a specific length requirement for a
parameter. Otherwise, it is recommended not to fil1 in this column.
in the ‘Support’ columns (Sender and/or Receiver), they shall conform to the value(s) given in the
If values are given
‘Status’ column.
6 Rec. UIT-T X.245 (1995 F)
ISOKEI 8327-2 : 1996 (F)
The values are as follows:
1 1
-
A specific number of octets is given in ITU-T Rec. X.225 1 ISO/IEC 8327-l.
X
-
‘O-y’ A range of number of octets is given in ITU-T Rec. X.225 1 ISO/IEC 8327-l.
-
For a specific reason (total length of the SPDU), an explicit range of number of octets cari
‘see Ref.’
not be given in the PICS proforma. For more details, the implementor shall refer to ITU-T
Rec. X.225 ) ISO/IEC 8327-l.
A.2.3 Instructions for completion
The supplier shall complete a11 entries in the column marked ‘Support’. In certain clauses of the PICS proforma further
guidance for completion may be necessary. Such guidance shall supplement the guidance given in this clause and shall
have a scope restricted to the clause in which it appears. In addition, other specifically identified information shall be
provided by the implementor where requested. No changes shall be made to the proforma except the completion as
required. Recognising that the level of detail required may, in some instances, exceed the space available for responses a
number of responses specifically allow for the addition of appendices to the PICS.
A.3 Identification of the implementation
Date of statement
A.3.1
1 1 1 Date of statement? (yy-mm-dd)
A.3.2 Implementation details
The supplier of the protocol implementation shall specify the information necessary to uniquely identify the
implementation and the system in which it may reside. This may include details of:
supplier, implementation name, operating system, suitable hardware;
a>
b) system supplier and/or client of the test laboratory that is to test the implementation;
c) information on whom to contact if there are queries conceming the content of the PICS.
Rec. UIT-T X.245 (1995 F)
ISO/CEI 8327-2 : 1996 (F)
A.4 Protocol Identification
A.4.1 ITU-T Rec. X.225 1 ISO/IEC 8327-1 protocol details
Identification of Protocol Specification support Comment
-
ITU-T Rec. X.225 (1994) 1 ISO/IEC 8327-l : 1996
,
c
A.4.2 ITU-T Rec. X.225 1 ISO/IEC 8327-1 protocol versions
Which version of the Session Protocol is described in this PICS?
1 Statu 1 Support 1 Mnemonic Comment
1 0.1 S-VI
1 Version
2 Version 2 0.1
0.1: the implementation of one, and only one, version of the protocol shall be described in this proforma (see below).
An implementation shall be described by completing a separate PICS proforma for each supported protocol version.
PICS document for a11 versions of the protocol for which conformance is claimed should be attached to each other, and
used together.
Which other versions of the Session Protocol does the implementation support?
1 status 1 support 1
Comment
3 Version 1
4 Version 2
A.4.3 ITU-T Rec. X.225 1 ISO/IEC 8327-1 technical corrigenda implemented
Identification of corrigenda applied to the implementation ITU-T Rec. X.225 (1994) 1 ISO/IEC 8327-l : 1996
col-r:
con-:
col-r:
col-r:
con-:
A.5 Global statement of conformance
1 1 Are a11 mandatory features implemented? (yes or no)
NOTE - If a positive response is not given to this box, then the implementation does not conform to ITU-T Rec. X.225 1
ISO/IEC 8327- 1.
8 Rec. UIT-T X.245 (1995 F)
ISOKEI 8327-2 : 1996 (F)
A.6 Supported functional units and protocol mechanisms
A.6.1 Functional units
support
Functional Unit Status Mnemonic Comment
m
1 Kernel
0 S-FU(NR)
2 Negotiated Release
3 Half Duplex 0.2 S-FU(HD)
4 Duplex 0.2 S-FU(FD)
5 Expedited Data (Note) 0 S-FU(EX)
6 Typed Data 0 S-FU(TD)
cl S-FU(CD)
7 Capability Data Exchange
8 Minor Synchronize 0 S-FU(SY)
9 Symmetric Synchronize 0 S-FU(SS)
L
c2 S-FU(DS)
10 Data Separation
11 Major Synchronize 0 S-FU(MA)
.
12 Resynchronize 0 S-FU(RESYN)
1 S-FU(EXCEP)
13 1 Exceptions
1 S-FU(ACT)
1 14 1 Activity management I 0 I I
one of the functional units Duplex and Half Duplex shall be implemented.
if [ S-FU(ACT) ] then o else n/a.
if [ S-FU(SY) or S-FU(SS) ] then o else n/a.
if [ S-FU(HD) ] then o else n/a.
NOTE - The TRANSPORT Expedited data service is required to support the SESSION Expedited data fùnctional unit.
Protocol mechanisms
A.6.2
Range of
Status support Mnemonic Comment
Mechanism
values I
-
c4 S-EXP T
1 Use of transport expedited data
-
(Extended control Quality of Service)
2 Reuse of transport connection 0 -
S-REUSE T
...
lSO/CEI
NORME
8327-2
INTERNATIONALE
Première édition
1996-I O-OI
Technologies de l’information -
Interconnexion de systèmes ouverts
Protocole de session en mode
(OSI) -
connexion: Formulaire de déclaration de
conformité d’instance de protocole (PICS)
Information technology - Open Systems Interconnection - Connection-
orien ted Session pro tocol: Pro tocol Implemen ta tion Con formance
Sta temen t (PICS) pro forma
ISOICEI 8327-2: 1996(F)
Sommaire
Page
1 Domaine d’application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Références normatives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recommandations 1 Normes internationales identiques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1
2.2 Paires de Recommandations 1 Normes internationales équivalentes par leur contenu technique . . . . . . .
Définitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
4 Abréviations
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
5 Conformité
Annexe A - Formulaire de déclaration de conformité d’instance de protocole (PICS) pour le protocole de
................................................................................................................. 3
session en mode connexion
A.1 Identification of PICS proforma corrigenda . 3
Instructions . 3
A.2
A.2.1 Purpose and structure of the proforma . 3
A.2.2 Symbols, terms and abbreviations . 3
Introduction . 3
A.2.2.1
A.2.2.2 Item numbering . 4
A.2.2.3 Status column . 4
A.2.2.4 Support column . 6
A.2.2.5 Value column .
Mnemonic column . 6
A.2.2.6
A.2.2.7 Length column . 6
A.2.3 Instructions for completion . 7
Identification of the implementation . 7
A.3
A.3.1 Date of statement . 7
A.3.2 Implementation details . 7
Protocol Identification . 8
A.4
A.4.1 ITU-T Rec. X.225 1 ISO/IEC 8327-l protocol details . 8
A.4.2 ITU-T Rec. X.225 1 ISO/IEC 8327-l protocol versions .
....................... 8
A.4.3 ITU-T Rec. X.225 1 ISO/IEC 8327-l technical corrigenda implemented.
Global statement of conformance . 8
A.5
Supported functional units and protocol mechanisms . 9
A.6
Functional units . 9
A.6 1
Protocol mechanisms . 9
A.6.2
0 ISOKEI 1996
Droits de reproduction réservés. Sauf prescription différente, aucune partie de cette publication ne
peut être reproduite ni utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou
mécanique, y compris la photocopie et Ies microfilms, sans I’accord écrit de I’éditeur.
ISOKEI Copyright Office l Case postale 56 l CH-121 1 Genève 20 l Suisse
Version française tirée en 1997
Imprimé en Suisse
ii
ISOKEI 8327-2: 1996(F)
0 ISO/CEI
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.7 Supported SPDUs
.......................................................................................................
Kemel functional unit
A.7.1
............................................................................................... 10
A.7.1.1 Supported roles
Support for the SPDUs associated with the Kemel fùnctional unit. .
A.7.1.2
Support for the SPDUs associated with Token Exchange . 11
A.7.1.3
...................................................................................
A.7.2 Negotiated Release functional unit
............................................................................................... 11
A.7.2.1 Supported roles
Support for the SPDUs associated with the Negotiated Release functional
A.7.2.2
unit .
Half Duplex functional unit .
A.7.3
Supported roles .
A.7.3.1
....... 12
Support for the SPDUs associated with the Half Duplex functional unit
A.7.3.2
...................................................................................................... 12
Duplex functional unit
A.7.4
A.7.5 Expedited Data functional unit . 12
A.7.5.1 Supported roles .
.. 12
A.7.5.2 Support for the SPDU associated with the Expedited Data functional unit.
............................................................................................... 12
A.7.6 Typed Data functional unit
Supported roles . 12
A.7.6.1
A.7.6.2 Support for the SPDU associated with the Typed Data functional unit. . 13
Capability Data functional unit . 13
A.7.7
A.7.7.1 Supported roles . 13
A.7.7.2 Support for the SPDUs associated with the Capability Data functional unit.
A.7.8 Minor synchronize functional unit .
A.7.8.1 Supported roles .
Support for the SPDUs associated with the Minor synchronize functional
A.7.8.2
unit . 13
A.7.9 Symmetric synchronize functional unit . 14
A.7.9.1 Supported roles .
Support for the SPDUs associated with the Symmetric synchronize
A.7.9.2
functional unit . 14
A.7.10 Data separation functional unit . 14
A.7.11 Major synchronize functional unit .
A.7.11.1 Supported roles . 14
A.7.11.2 Support for the SPDUs associated with the Major synchronize functional
unit .
.......................................................................................... 15
A.7.12 Resynchronize functional unit
A.7.12.1 Supported roles . 15
A.7.12.2 Supported resynchronize types .
A.7.12.3 Support for the SPDUs associated with the Resynchronize functional unit. . 15
A.7.13 Exceptions functional unit . 15
............................................................................................... 15
A.7.13.1 Supported roles
A.7.13.2 Support for the SPDUs associated with the Exceptions functional unit. . 16
................................................................................ 16
A.7.14 Activity management functional unit
A.7.14.1 Supported roles . 16
A.7.14.2 Support for the SPDUs associated with the Activity management fùnctional
unit . 17
.............................................................................................................. 18
A.8 Supported SPDU-parameters
Connect (CN) SPDU . 18
A.8.1
A.8.1.1 Connection Identifier . 18
....................................................................................... 18
A.8.1.2 Connect/Accept Item
A.8.1.3 Single Items . 19
A.8.2 Overflow Accept (OA) SPDU . 19
Connect Data Overflow (CDO) SPDU . 19
A.8.3
. . .
ISOKEI 8327-2: 1996(F) @ ISOKEI
A.8.4 Accept (AC) SPDU .
A.8.4.1 Connection Identifier
...................................................................................... 20
A.8.4.2 Connect/Accept Item
....................................................................................... 20
A.8.4.3 Single Items .
A.8.5 Refuse (RF) SPDU .
A.8.5.1 Connection Identifier
...................................................................................... 21
A.8.5.2 Single Items .
A.8.6 Finish (FN) SPDU .
A.8.7 Disconnect (DN) SPDU . 22
A.8.8
Not Finish (NF) SPDU. 23
A.8.9 Abort (AB) SPDU
............................................................................................................. 23
A.8.10 Abort Accept (AA) SPDU
................................................................................................ 23
A.8.11 Data Transfer (DT) SPDU .
A.8.12 Expedited Data (EX) SPDU . 23
A.8.13
Typed Data (TD) SPDU. 24
A.8.14 Capability Data (CD) SPDU
............................................................................................. 24
A.8.15 Capability Data Ack (CDA) SPDU .
.................................................................................................. 24
A.8.16 Give Tokens (GT) SPDU
A.8.17 Please Tokens (PT) SPDU . 25
........................................................................................ 25
A.8.18 Minor Sync Point (MIP) SPDU
Minor Sync Ack (MIA) SPDU . 25
A.8.19
....................................................................................... 26
A.8.20 Major Sync Point (MAP) SPDU
A.8.2 1 Major Sync Ack (MAA) SPDU . 26
A.8.22 Resynchronize (RS) SPDU .
Resynchronize Ack (RA) SPDU . 27
A.8.23
........................................................................................................... 27
A.8.24 Prepare (PR) SPDU
Exception Report (ER) SPDU . 27
A.8.25
A.8.26 Exception Data (ED) SPDU.
................................................................................. 28
A.8.27 Give Tokens Confïrm (GTC) SPDU
A.8.28 Give Tokens Ack (GTA) SPDU . 28
................................................................................................. 28
A.8.29 Activity Start (AS) SPDU
A.8.30 Activity Resume (AR) SPDU . 28
........................................................................................ 28
A.8.30.1 Linking Information
A.8.30.2 Single Items . 29
Activity Interrupt (AI) SPDU . 29
A.8.3 1
................................................................................. 29
A.8.32 Activity Interrupt Ack (AIA) SPDU
A.8.33 Activity Discard (AD) SPDU . 29
................................................................................. 30
A.8.34 Activity Discard Ack (ADA) SPDU
.................................................................................................. 30
A.8.35 Activity End (AE) SPDU
A.8.36 Activity End Ack (AEA) SPDU . 30
Annexe B - Liste des déclarations conditionnelles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Annexe C - Liste des mnémoniques utilisés dans les déclarations conditionnelles et optionnelles. . . . . . . . . . . . . . . . . . . . . . .
@ ISOKEI ISOKEI 8327-2: 1996(F)
Avant-propos
L’ISO (Organisation internationale de normalisation) et la CE1 (Commission
électrotechnique internationale) forment ensemble un système consacré à la
normalisation internationale considérée comme un tout. Les organismes nationaux
membres de I’ISO ou de la CE1 participent au développement de Normes inter-
nationales par l’intermédiaire des comités techniques créés par l’organisation
concernée afin de s’occuper des différents domaines particuliers de l’activité
technique. Les comités techniques de I’ISO et de la CE1 collaborent dans des
domaines d’intérêt commun. D’autres organisations internationales, gouverne-
mentales et non gouvernementales, en liaison avec 1’ISO et la CE1 participent
également aux travaux.
Dans le domaine des technologies de l’information, 1’ISO et la CE1 ont créé un
comité technique mixte, I’ISOKEI JTC 1. Les projets de Normes internationales
adoptés par le comité technique mixte sont soumis aux organismes nationaux pour
approbation, avant leur acceptation comme Normes internationales. Les Normes
internationales sont approuvées conformément aux procédures qui requièrent
l’approbation de 75 % au moins des organismes nationaux votants.
La Norme internationale ISO/CEI 8327 a été élaborée par le comité technique
mixte ISOKEI JTC 1, Technologies de I?nformation, sous-comité SC 21,
Interconnexion des systèmes ouverts, gestion des données et traitement distribué
ouvert, en collaboration avec I’UIT-T. Le texte identique est publié en tant que
Recommandation UIT-T X.245.
L’ISOKEI 8327 comprend les parties suivantes, présentées sous le titre général
Technologies de 1 ‘information - Interconnexion de systèmes ouverts (OSI) -
Protocole de session en mode connexion:
Partie I: Spécification du protocole
- Partie 2: Formulaire de déclaration de conformité d’instance de protocole
(PICS)
L’annexe A fait partie intégrante de la présente partie de I’ISOKEI 8327. Les
annexes B et C sont données uniquement à titre d’information.
V
ISOKEI 8327-2: 1996(F)
@ ISOKEI
Introduction
La présente Recommandation 1 Norme internationale fait partie d’un ensemble de Recommandations 1 Normes intematio-
nales élaborées pour faciliter l’interconnexion des équipements informatiques. Les relations entre la présente Recomman-
dation 1 Norme internationale et les autres Recommandations et Normes internationales de l’ensemble sont définies par le
modèle de référence pour l’interconnexion des systèmes ouverts (Rec. UIT-T X.200 1 ISO/CEI 7498-l). Le modèle de
référence subdivise le domaine de la normalisation en vue de l’interconnexion en une série de couches de spécification,
chaque couche étant de taille gérable.
L’interconnexion des systèmes ouverts vise à permettre, moyennant un minimum d’accords techniques en dehors des
normes d’interconnexion, l’interconnexion des équipements informatiques:
-
provenant de divers fabricants;
-
gérés différemment;
-
de niveaux de complexité différents;
-
s’appuyant sur diverses technologies.
La Rec. UIT-T X.225 1 ISO/CEI 8327-l spécifie le protocole de session en mode connexion.
Pour évaluer la conformité d’une application particulière, il est nécessaire de disposer d’une description des capacités
et des options qui ont été incluses. Une telle description est appelée déclaration de conformité d’instance de protocole
(PICS).
La présente Recommandation 1 Norme internationale contient le formulaire PICS pour le protocole de session en mode
connexion, tel qu’il est défini dans la Rec. UIT-T X.225 1 ISO/CEI 8327-l.
ISOKEI 8327-2 : 1996 (F)
NORME INTERNATIONALE
RECOMMANDATION UIT-T
TECHNOLOGIE$ DE L”INFORMATION - INTERCONNEXION
DE SYSTÈMES OUVERTS (OSI) - PROTOCOLE DE SESSION
EN MODE CONNEXION: FORMULAIRE DE DÉCLARATION
DE CONFORMITÉ D’INSTANCE DE PROTOCOLE (PICS)
Domaine d’application
La présente Recommandation 1 Norme internationale décrit le formulaire de déclaration de conformité d’instance de
tel qu’il est spécifié dans la Rec. UIT-T X.225 1 ISO/CEI 8327-1,
protocole (PICS) de session en mode connexion,
conformément aux prescriptions et directives pertinentes de la Rec. UIT-T X.296 1 ISOKEI 9646-7. L’utilisation
détaillée de ce formulaire est décrite dans la présente Recommandation 1 Norme internationale.
Le fournisseur d‘une réalisation déclarée conforme à la Rec. UIT-T X.225 1 ISO/CEI 8327-l est tenu de remplir un
exemplaire du formulaire PICS fourni en Annexe A; il doit également fournir les informations nécessaires pour identifier
ladite réalisation et ledit fournisseur.
Références normatives
Les Recommandations et Normes internationales suivantes contiennent des dispositions qui, par suite de la référence qui
y est faite, constituent des dispositions valables pour la présente Recommandation 1 Norme internationale. Au moment de
la publication, les éditions indiquées étaient en vigueur. Toutes Recommandations et Normes sont sujettes à révision et
les parties prenantes aux accords fondés sur la présente Recommandation 1 Norme internationale sont invitées à
rechercher la possibilité d’appliquer les éditions les plus récentes des Recommandations et Normes indiquées ci-après.
Les membres de la CE1 et de 1’ISO possèdent le registre des Normes internationales en vigueur. Le Bureau de la
normalisation des télécommunications de 1’UIT tient à jour une liste des Recommandations de I’UIT-T en vigueur.
21. Recommandations 1 Normes internationales identiques
-
Recommandation UIT-T X.200 (1994) 1 ISO/CEI 7498-l :1994, Technologies de Z’information -
Interconnexion des systèmes ouverts - Modèle de référence de base: le modèle de référence de base.
-
Recommandation UIT-T X.2 14 (1993) 1 ISO/CEI 8072: 1994, Technologies de Z’information -
Interconnexion des systèmes ouverts - Définition du service de transport.
-
Recommandation UIT-T X.215 (1995) 1 ISOKEI 8326: 1996, Technologies de Z’information -
Interconnexion des systèmes ouverts - Définition du service de session.
-
Recommandation UIT-T X.225 (1995) 1 ISOKEI 8327.1:1996, Technologies de Z’information -
Interconnexion des systèmes ouverts - Protocole de session en mode connexion: spéczjkation.
Paires de Recommandations 1 Normes internationales équivalentes par leur contenu technique
22.
-
Recommandation UIT-T X.290 (1995), Cadre général et méthodologie des tests de conformité
d’interconnexion des systèmes ouverts pour les Recommandations sur les protocoles pour les applications
de Z’UIT-T - Concepts généraux.
ISOKEI 9646-l : 1994, Technologies de l’information - Interconnexion des systèmes ouverts - Cadre
général et méthodologie des tests de conformité OSI - Partie 1: Concepts généraux.
Rec. UIT-T X.245 (1995 F)
ISOKEI 8327-2 : 1996 (F)
-
Recommandation UIT-T X.296 (1995), Cadre général et méthodologie des tests de conformité OSI pour
les Recommandations sur les protocoles pour les applications de ZUT-T - Déclarations de conformité
d’instance.
ISOICEI 9646-7: 1995, Technologies de I?nformation
- Interconnexion des systèmes ouverts (OSI) -
Essais de conformité - Méthodologie générale et procédures
- Partie 7: Déclaration de conformité des
mises en œuvre.
3 Définitions
Pour les besoins de la présente Recommandation 1 Norme internationale, les définitions suivantes s’appliquent.
3.1 Les termes définis dans la Rec. UIT-T X.225 1 ISOKEI 8327-l.
3.2 Les termes suivants, définis dans la Rec. UIT-T X.290 1 ISOKEI 9646-l:
a) déclaration de conformité d’instance de protocole (PICS);
b) formulaire PICS.
3.3 Termes additionnels:
-
demandeur: machine SPM qui lance une action particulière;
-
accepteur: machine SPM qui accepte une action particulière.
,
Abréviations
4.1 Les abréviations sont données dans la Rec. UIT-T X.225 1 ISOKEI 8327-l et dans l’article 8.
4.2 La présente Recommandation 1 Norme internationale utilise l’abréviation suivante définie dans la
Rec. UIT-T X.290 1 ISOKEI 9646-l :
-
PICS Déclaration de conformité d’instance de
protocole (protocol implementation conformance
statement).
4.3 Pour les besoins de la présente Recommandation 1 Norme internationale, les abréviations suivantes
s’appliquent également:
Sts Colonne «Status»
Colonne «Support»
SPt
Str Emetteur
Rcv Récepteur
5 Conformité
Une déclaration PICS conforme doit être techniquement équivalente au formulaire PICS publié par l’UIT-T 1 ISO/CEI
dont elle doit conserver la numérotation et l’ordre des items.
Une déclaration PICS conforme à la présente Recommandation 1 Norme internationale doit:
a) décrire une réalisation qui est conforme à la Rec. UIT-T X.225 1 ISO/CEI 8327-l;
être établie selon un fornmlaire PICS conforme, rempli conformément aux directives indiquées en A.2;
b)
inclure les informations nécessaires pour identifier sans ambiguïté le fournisseur et la réalisation.
Cl
Rec. UIT-T X.245 (1995 F)
ISOKEI 8327-2 : 1996 (F)
Annexe A
Formulaire de déclaration de conformité d’instance de protocole (PICS)
pour le protocole de session en mode connexion’)
(Cette annexe fait partie intégrante de la présente Recommandation 1 Norme internationale)
Identification of PICS proforma corrigenda
Al.
The supplier of the PICS proforma shall identifl any corrigenda (i.e. Technical Corrigenda or equivalent) to the
published proforma that have been applied. Suppliers of the proforma should modify the proforma, or attach relevant
additional pages in order to apply the corrigenda, and then record the application of the corrigenda in the table below.
Identification of corrigenda applied to this PICS proforma ITU-T Rec. X.245 (1995) 1 ISO/IEC 8327.2:1996
con-:
col-r:
con-:
Instructions
A.2
Purpose and structure of the proforma
A.2.1
The purpose of this PICS proforma is to provide suppliers of implementation of ITU-T Rec. X.225 1 ISO/IEC 8327-l
with a consistent means of stating which capabilities have been implemented.
The proforma is in form of a questionnaire and consists of a set of items. An item is provided for each capability for
which an implementation choice is allowed. Items are also provided for major mandatory capabilities for which no
implementation choice is allowed. Each item includes an item number, an item description, a status value specifying the
support requirement, and room for a support answer to be provided by the supplier.
This clause provides general information and instructions for completion of the proforma.
Subclause A.3 is for identification of the implementation.
Subclause A.4 contains the means of specifling, at high level, the protocol and corrigenda that have been implemented.
Subclause A.5 contains the global statement of conformance.
Subclauses A.6 onwards contain tables in which the supplier specifïes details of the implementation options chosen.
NOTE - Throughout the PICS proforma, tables specifling Requestor and Accpetor roles are inserted as required for
precise definition of the status of SPDUs and SPDU parameters, but these tables shall not be used for static conformance review nor
for test case selection.
A.2.2 Symbols, terms and abbreviations
A.2.2.1 Introduction
Notations have been introduced in order to reduce the size of tables in the PICS proforma. These have allowed the use of
multi-column layout where the colums are headed ‘Statu$ ‘Support’, ‘Value’, ‘Mnemonic’ and ‘Length’. The definition of
each are given below.
Additionally, the following definitions apply.
A.2.2.1.1 (PICS) item: A row in a PICS proforma table.
I) Droits de reproduction du formulaire PICS: Les utilisateurs de la présente Recommandation 1 Norme internationale sont autorisés à reproduire le
formulaire PICS de la présente annexe pour utiliser celui-ci conformément à son objet. Ils sont également autorisés à publier le formulaire une fois
celui-ci complété.
Rec. UIT-T X.245 (1995 F) 3
ISO/CEI 8327-2 : 1996 (F)
A.2.2.1.2 (PICS) question: The question to be answered in the intersection of a PICS item and either a support column
(i.e. “1s this item supported in the context applying to this table and column”) or supported values column (i.e. “What
values are supported for this item in the context applying to this table and column”) in a PICS proforma table.
A.2.2.1.3 status (value): An allowed entry in the status column for an item in a PICS proforma table.
A.2.2.1.4 (support) answer: An allowed entry in the support or supported values columns for an item in a PICS, in
answer to a PICS question.
A.2.2.2 Item numbering
Each line within the PICS proforma which requires implementation detail to be entered is given an item number in the
first column. The item number column provides a means of uniquely referencing each possible answer within the PICS
proforma. Such referencing is necessary for specifling predicates, conditional expressions, test suite parameters, and test
suite selection expressions.
The means of referencing individual answers is to specify the following sequence:
if, and only if, the reference is being made fkom another Specification, then start with an unambiguous
a)
identifier for the relevant ICS proforma specification, enclosed in parentheses - this identifier is stated in
the PICS proforma specification and is updated whenever the PICS proforma is updated - it is
recommended that this identifier should be relevant Specifïcation number and year of publication, as is
used in a Normative References clause, and this is the default for such identifïers;
b) the number of the relevant table or, if the tables are not numbered, of the smallest subclause enclosing the
relevant table;
a solidus character, “/“;
C)
d) the item number or mnemonic reference to the item, to identify the row in which the answer appears;
if, and only if, more than one question occurs in the row identified by the item number or mnemonic
e)
reference, then each possible answer is implicitly labelled a, b, c, etc., from left to right, and this letter is
appended to the sequence, prefixed by a solidus character (V’) if a mnemonic reference is used.
If mnemonic references are specified and each uniquely identify an item in the PICS proforma, then
entries b) and c) in the above sequence may be omitted.
A.2.2.3 Status column
This column indicates the level of support required for conformance to ITU-T Rec. X225 1 ISO/IEC 8327-1, the given
values are taken firom the Session Protocol Specification (see ITU-T Rec. X.225 1 ISO/IEC 8327-l).
A.2.2.3.1 Definitions applying to the tables in clauses A.4 to A.6
The values are as follows:
-
‘m’ Mandatory support is required. The implementation shall support the functionalities described in
ITU-T Rec. X.225 1 ISO/IEC 8327-l for the specified item.
t 1
-
0 Optional support is permitted for conformance to ITU-T Rec. X.225 1 ISO/IEC 8327-l. According
to some specifïc reason, the implementation is not obliged to support the specifïed item. If
implemented, it shall conform to the specifïcations and restrictions contained in ITU-T Rec. X.225 1
ISO/IEC 8327-l. Therefore the constraints described for the mandatory support above also apply.
-
'0.d Selectable options among a set of items (where n is the number which identifies the group of
optionals which are linked together). The implementation shall support at least one of the given
items. [For the selected item(s), the constraints described for the mandatory support above also
aPPlYl l
-
The item is conditional (where n is the number which identifies the condition which is applicable).
‘cn’
The definitions for the conditional statements used in Annex A are written under the table where
they are used, and indexed in Annex B.
1 1
-
nla The item is not applicable.
4 Rec. UIT-T X.245 (1995 F)
ISOKEI 8327-2 : 1996 (F)
A.2.2.3.2 Definitions applying to the tables in clause A.7 (Supported SPDUs)
The values are as follows:
Sender item:
-
Mandatory support is required. The implementation shall be able:
‘m’
to build the SPDU (i.e. to build correctly the heading and a11 the mandatory parameters within
the SPDU) in the situations required by the Protocol Machine; and
to encode the SPDU into the TSDU, according to a valid encoding format.
1 1
-
Optional support is permitted for conformance to ITU-T Rec. X.225 1 ISO/IEC 83274. According
to some specifïc reason, the implementation is not obliged to be able to build the SPDU. If
implemented, it shall conform to the specifications and restrictions contained in ITU-T Rec. X.225 1
ISO/IEC 8327-l. Therefore the constraints described for the mandatory support above also apply.
-
Selectable options among a set of items (where n is the number which identifies the group of
‘0.n’
optionals which are linked together). The implementation shall support at least one of the given
items. [For the selected item(s), the constraints described for the mandatory support above also
aPPlY -1
-
The item is conditional (where n is the number which identifies the condition which is applicable).
‘cn’
The definitions for the conditional statements used in Annex A are written under the table where
they are used, and indexed in Annex B. Resolution of the condition (e.g. depending on protocol
version, protocol mechanism, etc.) yields to ‘m’, ‘0’ or Wa’.
1 1
-
n/a The item is not applicable.
Receiver item:
Mandatory support is required. The implementation shall be able:
- ‘m’
to syntactically identify the SPDU [i.e. to decode the heading and a11 of the parameters which are
present (Type and Length in TLV coding scheme)]; and
to process it correctly.
1 1
Optional support is permitted for conformance to ITU-T Rec. X.225 1 ISO/IEC 8327-l. If
- 0
implemented, it shall conform to the specifications and restrictions contained in ITU-T Rec. X.225 1
ISO/IEC 8327-l. Therefore the constraints described for the mandatory support above also apply.
- ‘0.n’ Selectable options among a set of items (where n is the number which identifies the group of
optionals which are linked together). The implementation shall support at least one of the given
items. [For the selected item(s), the constraints described for the mandatory support above also
aPPlYl l
The item is conditional (where n is the number which identifies the condition which is applicable).
- ‘cn’
The definitions for the conditional statements used in Annex A are written under the table where
they are used, and indexed in Annex B. Resolution of the condition (e.g. depending on protocol
version, protocol mechanism, etc.) yields to ‘m’, ‘0’ or Wa’.
1 1
- nla The item is not applicable.
A.2.2.3.3 Definitions applying to the tables in clause A.8 (Supported SPDU parameters)
NOTE - The statu indicated for the parameters reflects static conformance requirements. The details about the use of
these parameters in specifïc instances of communications (i.e. dynamic conformance) are to be found in the Session protocol standard
(ITU-T Rec. X.225 1 ISO/IEC 8327-l). It is reminded that a parameter with the Length equal to zero shall be considered as absent.
The values are as follows:
Sender item:
-
Mandatory support is required. The implementation shall be able to build and to encode this
‘m’
parameter within the appropriate SPDU.
1 1
-
0 Optional support is permitted for conformance to ITU-T Rec. X.225 1 ISO/IEC 8327-l. According
to some specific reason, the implementation is not obliged to be able to build the parameter. If
implemented, it shall conform to the specifïcations and restrictions contained in ITU-T Rec. X.225 1
ISO/IEC 8327-l. Therefore the constraints described for the mandatory support above also apply.
Rec. UIT-T X.245 (1995 F) 5
ISOKEI 8327-2 : 1996 (F)
-
‘cn’ The item is conditional (where n is the number which identifies the condition which is applicable).
The definitions for the conditional statements used in Annex A are written under the table where
they are used, and indexed in Annex B. Resolution of the condition (e.g. depending on protocol
version, protocol mechanism, etc.) yields to ‘m’, ‘0’ or Wa’.
-
‘n/a’ The item is not applicable.
Receiver item:
-
‘m’ Mandatory support is required. The implementation shall
be able to syntactically and semantically
identify the SPDU parameter and to process it correctly.
1 1
-
0 Optional support is permitted for conformance to ITU-T Rec. X.225 1 ISO/IEC 8327-l. If
implemented, it shall conform to the specifications and restrictions contained in ITU-T Rec. X.225 1
ISO/IEC 8327-l. Therefore the constraints described for the mandatory support above also apply.
-
‘cn’ The item is conditional (where n is the number which identifies the condition which is applicable).
The definitions for the conditional statements used in Annex A are written under the table where
they are used, and indexed in Annex B. Resolution of the condition (e.g. depending on protocol
version, protocol mechanism, etc.) yields to ‘m’, ‘0’ or Wa’.
-
‘n/a’ The item is not applicable.
A.2.2.4 Support column
.l be completed by the supplier or implementor to indicate the level of implementation
The ‘Support’ column shal of each
feature. The proforma has been designed such that the only entries required in the ‘Support’ column are:
If the Status column yields to ‘m’ or ‘o’, the following answers are valid:
Yes, the feature has been implemented.
‘Y’
PJ’ No, the feature has not been implemented.
If the Status column yields to Wa’, the unique following answer is valid:
‘-’ Not applicable.
A.2.2.5 Value column
The ‘Value’ column requires the specifïcation of the range of values implemented for a feature, where relevant.
A.2.2.6 Mnemonic column
The ‘Mnemonic’ column is given to facilitate the interpretation of the conditional statements throughout the PICS
proforma.
The mnemonics are designed SO that the implementor should easily understand their contents. Their names are generated
as follows:
a character identifling the Session layer (S);
a)
an hyphen character;
b)
a sequence of character which is derived, where possible, from the abbreviations used in the Session
Cl
protocol specifïcation.
A full alphanumerical list of a11 the defïned ‘Mnemonics’ is given in Annex C.
A.2.2.7 Length column
The ‘Length’ column is given for information only in A.8, in order to indicate a specific length requirement for a
parameter. Otherwise, it is recommended not to fil1 in this column.
in the ‘Support’ columns (Sender and/or Receiver), they shall conform to the value(s) given in the
If values are given
‘Status’ column.
6 Rec. UIT-T X.245 (1995 F)
ISOKEI 8327-2 : 1996 (F)
The values are as follows:
1 1
-
A specific number of octets is given in ITU-T Rec. X.225 1 ISO/IEC 8327-l.
X
-
‘O-y’ A range of number of octets is given in ITU-T Rec. X.225 1 ISO/IEC 8327-l.
-
For a specific reason (total length of the SPDU), an explicit range of number of octets cari
‘see Ref.’
not be given in the PICS proforma. For more details, the implementor shall refer to ITU-T
Rec. X.225 ) ISO/IEC 8327-l.
A.2.3 Instructions for completion
The supplier shall complete a11 entries in the column marked ‘Support’. In certain clauses of the PICS proforma further
guidance for completion may be necessary. Such guidance shall supplement the guidance given in this clause and shall
have a scope restricted to the clause in which it appears. In addition, other specifically identified information shall be
provided by the implementor where requested. No changes shall be made to the proforma except the completion as
required. Recognising that the level of detail required may, in some instances, exceed the space available for responses a
number of responses specifically allow for the addition of appendices to the PICS.
A.3 Identification of the implementation
Date of statement
A.3.1
1 1 1 Date of statement? (yy-mm-dd)
A.3.2 Implementation details
The supplier of the protocol implementation shall specify the information necessary to uniquely identify the
implementation and the system in which it may reside. This may include details of:
supplier, implementation name, operating system, suitable hardware;
a>
b) system supplier and/or client of the test laboratory that is to test the implementation;
c) information on whom to contact if there are queries conceming the content of the PICS.
Rec. UIT-T X.245 (1995 F)
ISO/CEI 8327-2 : 1996 (F)
A.4 Protocol Identification
A.4.1 ITU-T Rec. X.225 1 ISO/IEC 8327-1 protocol details
Identification of Protocol Specification support Comment
-
ITU-T Rec. X.225 (1994) 1 ISO/IEC 8327-l : 1996
,
c
A.4.2 ITU-T Rec. X.225 1 ISO/IEC 8327-1 protocol versions
Which version of the Session Protocol is described in this PICS?
1 Statu 1 Support 1 Mnemonic Comment
1 0.1 S-VI
1 Version
2 Version 2 0.1
0.1: the implementation of one, and only one, version of the protocol shall be described in this proforma (see below).
An implementation shall be described by completing a separate PICS proforma for each supported protocol version.
PICS document for a11 versions of the protocol for which conformance is claimed should be attached to each other, and
used together.
Which other versions of the Session Protocol does the implementation support?
1 status 1 support 1
Comment
3 Version 1
4 Version 2
A.4.3 ITU-T Rec. X.225 1 ISO/IEC 8327-1 technical corrigenda implemented
Identification of corrigenda applied to the implementation ITU-T Rec. X.225 (1994) 1 ISO/IEC 8327-l : 1996
col-r:
con-:
col-r:
col-r:
con-:
A.5 Global statement of conformance
1 1 Are a11 mandatory features implemented? (yes or no)
NOTE - If a positive response is not given to this box, then the implementation does not conform to ITU-T Rec. X.225 1
ISO/IEC 8327- 1.
8 Rec. UIT-T X.245 (1995 F)
ISOKEI 8327-2 : 1996 (F)
A.6 Supported functional units and protocol mechanisms
A.6.1 Functional units
support
Functional Unit Status Mnemonic Comment
m
1 Kernel
0 S-FU(NR)
2 Negotiated Release
3 Half Duplex 0.2 S-FU(HD)
4 Duplex 0.2 S-FU(FD)
5 Expedited Data (Note) 0 S-FU(EX)
6 Typed Data 0 S-FU(TD)
cl S-FU(CD)
7 Capability Data Exchange
8 Minor Synchronize 0 S-FU(SY)
9 Symmetric Synchronize 0 S-FU(SS)
L
c2 S-FU(DS)
10 Data Separation
11 Major Synchronize 0 S-FU(MA)
.
12 Resynchronize 0 S-FU(RESYN)
1 S-FU(EXCEP)
13 1 Exceptions
1 S-FU(ACT)
1 14 1 Activity management I 0 I I
one of the functional units Duplex and Half Duplex shall be implemented.
if [ S-FU(ACT) ] then o else n/a.
if [ S-FU(SY) or S-FU(SS) ] then o else n/a.
if [ S-FU(HD) ] then o else n/a.
NOTE - The TRANSPORT Expedited data service is required to support the SESSION Expedited data fùnctional unit.
Protocol mechanisms
A.6.2
Range of
Status support Mnemonic Comment
Mechanism
values I
-
c4 S-EXP T
1 Use of transport expedited data
-
(Extended control Quality of Service)
2 Reuse of transport connection 0 -
S-REUSE T
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...