EN ISP 10608-1:1994
(Main)Information technology - International Standardized Profile TAnnnn - Connection-mode Transport Service over Connectionless-mode Network Service - Part 1: General overview and subnetwork-independent requirements (ISO/IEC ISP 10608-1:1992)
Information technology - International Standardized Profile TAnnnn - Connection-mode Transport Service over Connectionless-mode Network Service - Part 1: General overview and subnetwork-independent requirements (ISO/IEC ISP 10608-1:1992)
Informationstechnik - Internationale Profilnorm TAnnnn - Verbindungsorientierter Transportdienst über verbindungslosem Vermittlungsdienst - Teil 1: Allgemeiner Überblick und Teilnetz-unabhängige Anforderungen (ISO/IEC ISP 10608-1:1992)
Technologies de l'information - Profil normalisé international TAnnnn - Service de transport en mode connexion sur le service de réseau en mode sans connexion - Partie 1: Introduction générale et spécifications indépendantes du sous-réseau (ISO/IEC ISP 10608-1:1992)
Information technology - International Standardized Profile TAnnnn - Connection-mode Transport Service over Connectionless-mode Network Service - Part 1: General overview and subnetwork-independent requirements (ISO/IEC ISP 10608-1:1992)
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN ISP 10608-1:1997
01-december-1997
Information technology - International Standardized Profile TAnnnn - Connection-
mode Transport Service over Connectionless-mode Network Service - Part 1:
General overview and subnetwork-independent requirements (ISO/IEC ISP 10608-
1:1992)
Information technology - International Standardized Profile TAnnnn - Connection-mode
Transport Service over Connectionless-mode Network Service - Part 1: General
overview and subnetwork-independent requirements (ISO/IEC ISP 10608-1:1992)
Informationstechnik - Internationale Profilnorm TAnnnn - Verbindungsorientierter
Transportdienst über verbindungslosem Vermittlungsdienst - Teil 1: Allgemeiner
Überblick und Teilnetz-unabhängige Anforderungen (ISO/IEC ISP 10608-1:1992)
Technologies de l'information - Profil normalisé international TAnnnn - Service de
transport en mode connexion sur le service de réseau en mode sans connexion - Partie
1: Introduction générale et spécifications indépendantes du sous-réseau (ISO/IEC ISP
10608-1:1992)
Ta slovenski standard je istoveten z: EN ISP 10608-1:1994
ICS:
33.040.40 Podatkovna komunikacijska Data communication
omrežja networks
35.100.01 Medsebojno povezovanje Open systems
odprtih sistemov na splošno interconnection in general
35.100.05 9HþVORMQHXSRUDEQLãNH Multilayer applications
UHãLWYH
SIST EN ISP 10608-1:1997 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST EN ISP 10608-1:1997
---------------------- Page: 2 ----------------------
SIST EN ISP 10608-1:1997
---------------------- Page: 3 ----------------------
SIST EN ISP 10608-1:1997
---------------------- Page: 4 ----------------------
SIST EN ISP 10608-1:1997
INTERNATIONAL ISO/IEC
STANDARDIZED
PROFILE
First edition
1992-12-15
Information technology - International
Standardized Profile TAnnnn -
Connection-mode Transport Service over
Connectionless-mode Network Service -
Part 1:
General overview and
subnetwork-independent requirements
Technologies de I ’information - Profil normalist+ in tema tional TAnnnn -
Service de transport en mode connexion sur Ie Service de rbseau en mode
sans connexion -
Partie 1: In troduction g&Grale et spkifica tions independan tes du
sous-rbseau
Reference number
ISO/IEC ISP 10608-1 :1992(E)
---------------------- Page: 5 ----------------------
SIST EN ISP 10608-1:1997
ISO/IEC ISP 1060&1:1992 (E)
. . .
Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . .~. Ill
iv
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .~. 1
Scope
. . . . . . . . .~. 1
Normative references
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*. 2
Def initions
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Subnetwork-type Independent Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*. 2
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Location of Subnetwork-type Specific
Annexes
A ISP Implementation Conformance Statement Requirements List (IPRL) . 5
B List of defect reports . 8
C ISP Implementation Conformance Statement Requirements List (IPRL) . 9
.......................................................................
D Recommendations on Transport Layer Interoperability 13
E Bibliography . 17
o ISO/IEC 1992
All rights reserved. No part of this publication may be reproduced or utilized in any form or
by any means, electronie or mechanical, including photocopying and microfilm, without per-
mission in writing from the publisher.
ISO/IEC Copyright Office l Case Postale 56 l CH-121 1 Geneve 20 l Switzerland
Printed in Switzerland
---------------------- Page: 6 ----------------------
SIST EN ISP 10608-1:1997
ISOAEC ISP 106084:1992 (E)
Foreword
ISO (the International Organization for Standardization) and IEC (the lnter-
national Electrotechnical Commission) form the specialized System for
worldwide standardization. National bodies that are members of ISO or
IEC participate in the development of International Standards through
technical committees established by the respective organization to deal
with particular fields of technical activity. ISO and IEC technical commit-
tees collaborate in fields of mutual interest. Other international organiza-
tions, governmental and non-governmental, in liaison with ISO and IEC,
also take part in the work.
In the field of information technology, ISO and IEC have established a joint
technical committee, lSO/IEC JTC 1. In addition to developing International
Standards, lSO/IEC JTC 1 has created a Special Group on Functional
Standardization for the elaboration of International Standardized Profiles.
An International Standardized Profile is an internationally agreed,
harmonized document which identifies a Standard or group of Standards,
together with Options and Parameters, necessary to accomplish a function
or set of functions.
Draft International Standardized Profiles are circulated to national bodies
for voting. Publication as an International Standardized Profile requires ap-
proval by at least 75 % of the national bodies casting a vote.
International Standardized Profile lSO/IEC ISP 10608-1 was prepared with
the collaboration of
- OSI Asia-Oceania Workshop (AOW);
- European Workshop for Open Systems (EWOS);
- OSI Implementors Workshop (OIW).
lSO/IEC ISP 10608 consists of the following Parts, under the general title
Information technology - International Standardized Profile TAnnnn -
Connection-mode Transport Service over Connectionless-mode Network
Service:
- Part 1: General overview and subnetwork-independent require-
men ts
- Part 2: TA5 1 Profile including subnetwork-dependent requirements
for CSMA/cD Local Area Networks (LANs)
- Part 4: Definition of Profile TA53 for Operation over a Token Ring
LAN subnetwork
- Part 5: TA? 11 l/TA 1121 profiles including subnetwork-dependent
requirements for X.25 packet-switched data networks using vrtual
calls
- Part 13: MAC sublayer and physical layer dependent requirements
for Token Ring local area network
Annexes A,’ B and C form an integral part of this patt of lSO/IEC
ISP 10608. Annexes D and E are for information only.
. . .
Ill
---------------------- Page: 7 ----------------------
SIST EN ISP 10608-1:1997
ISOAEC ISP 1060&1:1992 (E)
fntroduction
This part of ISO/IEC ISP 10608 (international Standardized Profile) is defined within the context of Func-
tional Standardization, in accordance with the principles specified by ISO/TR 10000-1 :1990. The context of
Functional Standardization is one patt of the Overall field of Information Technology (IT) standardization ac-
tivities, covering base Standards, profiles, and registration mechanisms. A Profile defines a combination of
base Standards that collectively perform a specific weil-defined IT function. Profiles standardize the use of
Options and other variations in the base Standards, and provide a basis for the development of uniform, in-
ternationally recognized System tests.
One of the most important roles for an ISP is to serve as the basis for the development (by organizations
other than ISO and IEC) of intemationally recognized tests and test Centers. ISPs are produced not simply
to legitimize a particular choice of base Standards and Options, but to promote real System interoperability.
The development and widespread acceptance of tests based on this and other ISPs is crucial to the suc-
cessful realization of this goal.
ISO/lEC ISP 10608 consists of several Parts, of which this is Part 1. ISO/IEC 10608-1 specifies subnetwork-
type independent requirements for Group TA profiles. ISO/IEC 10608-2 specifies subnetwork-type depen-
dent requirements for Profile TA51. ISO/IEC ISP 10608-3 specifies subnetwork-type dependent require-
ments for Profile TA52* ISO/lEC ISP 10608-4 specifies subnetwork-type dependent requirements for Profile
TA53. ISO/IEC ISP 10608-5 specifies subnetwork-type dependent requirements for Profiles TA1 111 and
TA1121.
iv
---------------------- Page: 8 ----------------------
SIST EN ISP 10608-1:1997
INTERNATIONAL STANDARDIZED PROFILE ISO/IEC ISP 106084 :1992 (E)
Information technology - International Standardized Profile TAnnnn -
Connection-mode Transport Service over Connectionless-mode Net-
work Service
Part 1: General overview and subnetwork-type independent require-
ments
1 Scope
This part of lSO/IEC ISP 10608 is applicable to end Systems concerned with operating in the Open Systems
Interconnection (OSI) environment. lt specifies a combination of OSI Standards, which collectively provide
the Connection-mode Transport Sewice using the Connectionless-mode Network Service.
This part of ISO/IEC ISP 10608 is applicable to the Provision of the Connection-mode Transport Service in
end Systems attached to, any type sf subnetwork from which the standardized Connectionless-mode Net-
work Service tan be made available.
Profiles of the Connection-mode Transport Service over Connectionless-mode Network Service are mem-
bers of a Single group, Group TA, and support a Single transport class, i.e., Class 4.
2 Normative References
The following documents contain provisions which, through reference in this text, constitute provisions of
this part of ISO/IEC ISP 10608. At the time of publication, the editions indicated were valid. All documents
are subject to revision, and Parties to agreements based on this part of ISWEC ISP 10608 are warned
against automatically applying any more recent editions of the documents listed below, since the nature of
references made by ISPs to such documents, is that they may be specific to a particular edition. Members
of IEC and ISO maintain registers of currently valid International Standards and ISPs, and the CCIlT main-
tains published editions of its current Recommendations.
ISO 8072:1986, Information processing Systems - Open Systems Interconnection - Transport Service defi-
nition.
(See also CCITT Recommendation X.214 -1988).
ISO/IEC 8073:1988, Information processing Systems - Open Systems Interconnection - Connection orient-
ed transport pro tocol specifica tion.
(See also CCITT Recommendation X.224 -1988).
ISO/IEC 8073:1988 /Add.2: 1989, Information processing Systems - Open Systems Interconnection - Con-
nection oriented transport protocol specification - Addendum 2: Class four Operation over cannectionless
network Service.
ISO/IEC 8073:1988 IAmd.3: 1992, Information processing Systems - Open Systems Interconnection - Con-
nection oriented transpori protocol specification - Amendment 3: Protocol implementation conformance
Statement (PICS) proforma.
ISOIIEC 8073: Kor.1 :1990, Information processing Systems - Open Systems Interconnection - Connection
orien ted transport pro tocol specification - Technical corrigendum 1.
ISOIIEC 8073: /Cor.2:1990, Information processing Systems - Open Systems Interconnection - Connection
orien ted transpo fl pro tocol specification - Technical corrigendum 2.
ISO/IEC 8073: /Cor.4:1991, Information processing Systems - Open Systems lnterconnection - Connection
oriented transport protocol specification - Technical corrigendum 4.
ISO/IEC 8073: /Cor.5:1991, lnformationprocessing Systems - Open Systems Interconnection - Connection
---------------------- Page: 9 ----------------------
SIST EN ISP 10608-1:1997
ISOAEC ISP 1060~1:1992 (E)
oriented transport protocol specification - Technical corrigendum 5.
ISO 8348: 1987, Information processing Systems - Data communications - Network sewice definition.
(See also CCITT Recommendation X.213 - 1988).
ISO 8348: /Add.l : 1987, Information processing Systems - Data communications - Network sewice defini-
tion - Addendum 1: Connectionless-mode transmission.
ISO 8348: IAdd.2: 1988, Information pracessing Systems - Data communications - Network sewice defini-
tion - Addendum 2: Network layer addressing.
ISO 8473: 1988, Information processing Systems - Data communications - Protocol for providing the con-
nectionless-mode netwotk sewice.
3 Definitions
All of the terms used in this part of ISO/IEC ISP 10608 are defined either in the referenced base Standards
(see clause 2) or in the International Standards listed in annex E.
4 Abbreviations
All of the abbreviations and acronyms used in this part of lSO/IEC ISP 10608 are defined either in the ref-
erenced base Standards (see clause 2) or in the International Standards listed in annex E.
5 Subnetwork-type Independent Requirements
5.1 General
The requirements stated in this clause apply uniformly to all conforming end Systems, without regard to the
type of subnetworks to which those end Systems might be attached. Additional requirements apply to end
Systems according to the type of subnetworks to which they are attached; these requirements are specified
in subsequent park of ISO/IEC ISP 10608.
5.2 Transport Layer Requirements
This part of ISO/IEC ISP 10608 specifies Provision of the connection-mode Transport Service, as defined
in ISO 8072, using class 4 of the connection-mode Transport Protocol, as defined in ISO 8073 and ISO
8073/Add.2 which defines Operation of class 4 over the connectionless-mode Network Service.
Additional requirements are given in annex A and C which define the IPRL for the Transport protocol. Annex
B contains defect reports related to ISO/lEC 8073 along with the Statement of any consequential require-
ments for implernentors of these profiles.
5.2.1 Static conformance requirements
A conforming implementation shall
a) satisfy the conformance requirements as stated in clause 14 of ISO 8073.
b) support of the mandatory features for class 4 over CLNS as defined in ISO 8073 and ISO 8073/Add.2.
c) if it Claims to be capable of initiating TC establishment, be capable of demonstrating the sending of a
CR TPDU with
1) class 4 as the preferred class.
d) if it Claims to be capable of responding to TC establishment, be capable of demonstrating the accep-
tance of a CR TPDU with class 4 as the preferred class.
e) if it Claims to be capable of initiating TC establishment, be capable of
1) transmitting a Called TSAP-ID field in a CR TPDU,
2) when necessary, transmitting a Calling TSAP-ID field in a CR TPDU that tan convey any one of the
Transport Selectors implemented by the System.
f) if it Claims to be capable of responding to a TC establishment attempt, be capable of
---------------------- Page: 10 ----------------------
SIST EN ISP 10608-1:1997
ISO/IEC ISP 106084 :1992 (E)
1) transmitting a Calling TSAP-ID field in a CC TPDU,
2) when necessary, transmitting a Called TSAP-ID field in a CC TPDU that tan convey any one of the
Transport Selectors implemented by the System.
g) be capable of configuring the initial values of the following Parameters:
Tl Local retransmission time
N Maximum number of retransmissions
I Inactivity time
W Window time
h) if an implementation is operating any policy which delays the transmission of AK TPDUs, the maximum
amount of time by which a Single AK TPDU tan be delayed shall be indicated to the remote transport
entity using the acknowledge time Parameter.
5.2.2 Dynamit conformance requirements
a) TSAP-ID
The implementation shall support remote TSAP-ID Parameters of variable size up to and including 32 octets
using any encoding and any value.
Local T-selectors shall not exceed 32 octets in length.
On receipt of a CR TPDU the absence of a Calling or a Called TSAP-ID Parameter shall be treated as equiv-
alent to a Zero length Calling or Called TSAP-ID Parameter.
The absence of the CC Calling TSAP-ID Parameter on receipt indicates that the value of the CC Calling
TSAP-ID Parameter is equivalent to the value of the CR Calling TSAP-ID Parameter.
The absence of the CC Called TSAP-ID Parameter on receipt indicates that the value of the CC Called
TSAP-ID Parameter is equivalent to the value of the CR Called TSAP-ID Parameter.
Figure 1 summarizes the handling of Called and Calling TSAP-ID Parameters in CR and CC TPDUs.
CR Called CR Calling
no param 0 len len>Q
no param 0 len len>O
I
.
Y
no no
NIL note 4
NIL NIL note 1 NIL
param
param
.
. / r
NIL NIL Invalid
NIL NIL Invalid
C%d o len Calkg O len
L I
1
len >O Invalid Invalid note 3
len >O Invalid Invalid note 2
,
4
Notes:
1 CC Called is equivalent to CR Called.
2 CC Cailed must match in length and value to CR Called.
3 CC CaJling must match in length and value to CR Calling.
4 CC Calling is equivalent to CR Calling.
Figure 1 - Handling of Called and Calling TSAP-ID Parameters
b) Option selection on connection establishment
A conforming implementation shall implement the “non-use of checksum” function. It is recommended that
3
---------------------- Page: 11 ----------------------
SIST EN ISP 10608-1:1997
ISO/IEC ISP 1060&1:1992 (E)
the initiator proposes the non-use of checksum.
c) Invalid values in known Parameters
Known Parameters with invalid lengths in a CR or CC TPDU shall be handled as a protocol error.
Known Parameters with valid lengths but invalid values in a CR TPDU shall be handled as follows:
AGtiQn
Called TSAP-I D send DR TPDU.
Checksum discard CR TPDU.
5.3 Network Layer requirements
ISO/lEC ISP 10608 specifies Provision of the connectionless-mode Network Service, as defined by ISO
8348 and ISO 8348/Add.l, using the connectionless-mode Network Protocol as defined by ISO 8473.
ISO/IEC ISP 10608 specifies the use of OSI network addresses according to ISO 8348/Add.2. Any NSAP
address, in any of the formats identified by ISO 8348/Add.2, may be used with ISO 8473.
ISO/lEC ISP 10608 specifies the use of an ES-IS protocol for the exchange of routing information between
end Systems and intermediate Systems attached to the same subnetwork. Slnce the implementation of the
ES-IS protocol varies from subnetwork to subnetwork, reference to a specific base Standard will be found
in the subnetwork-type dependent Parts of ISO/IEC ISP 10608.
Additional requirements are given in Annex C which defines the IPRL for the Network Layer protocol.
5.3.1 CLNP requirements
5.3.1 .l Inactive subset
An implementation shall not transmit PDUs encoded using the inactive subset. Received PDUs encoded
using the inactive subset may be discarded.
5.3.1.2 Non-segmenting subset
An implementation shall not generate data PDUs without a Segmentation part. However, an implementation
shall receive and correctly process PDUs which do not contain the Segmentation part to provide interoper-
ability with those Systems that have Chosen to transmit PDUs without a Segmentation Part, i.e., the segmen-
tation permitted flag set to Zero.
5.3.2 ES-B requirements
Additional subnetwork dependent requirements for the ES-IS protocol are defined in subsequent (subnet-
work dependent) Parts of ISO/IEC ISP 10608.
-w
6 Location of subnetwork-type specific requirements
Additional requirements that apply to end Systems according to the type(s) of subnetwork to which they are
attached are specified in subsequent Parts of ISO/IEC ISP 10608. The subnetwork-type specific require-
ments concern both the way in which specific subnetwork Services are provided by individual real subnet-
works and the way in which those specific subnetwork Services are used to provide the underlying Service
assumed by ISO 8473.
The following part numbers have been assigned in the expectation that they will be produced in the fore-
seeable future.
Pan 2 TA51 - CSMAICD LAN
TA52 - Token Bus LAN
Part 3
TA53 - Token Ring LAN
Part 4
Part 5 TA1 11 VTA1121 - X.25 subnetwork.
---------------------- Page: 12 ----------------------
SIST EN ISP 10608-1:1997
ISOAEC ISP 10608-1:1992 (E)
Annex A
(normative)
International Standardized Profile Implementation Conformance
Statement Requirements List (IPRL)
A.l lntroduction
The IPRL in this annex specifies the additional requirements for ISO 8073/Amd.3. The requirements of ISO
8073/Amd.3 apply to each item for which there is no entry in this IPRL.
The IPRL in this annex follows the proforma specified in ISO 8073/Amd.3. Since the TA Profile group uses
the transport protocol Class 4 exclusively, the items of the PICS for Classes 0 through 3 and Class 4 over
CONS do not need to be duplicated in the IPRL for the TA profiles. All references to transport classes 1
through 3 and Class 4 over CONS are out of the scope of ISOllEC ISP 10608.
A conforming implementation shall satisfy the mandatory conformance requirements of the base Standard
referenced in this patt of the Profile.
A.2 Notation
The following tables define the functions supported for which conformance is claimed, using the following
keys.
a) Base Standard Status notation
1) base Standard type or range
M ; mandatory.
0 ; optional.
O. ; optional, but support of at least one of the group of Options labeled by the same
numeral en> is required.
: ; this predicate Symbol means that the Status following it applies only when the
PICS states that one or more of the items identified by the index is supported. In
the simplest case, is the identifying tag of a Single PICS item.
may also be a Boolean expression composed of several Indices.
:: ; When this group predicate is true the associated clause should be completed.
Ib) IPRL Status notation
The Status column of Profile features entries use a one Character or a two Character notation. A one char-
acter notation indicates the static requirements only. If a two Character notation is used, the first Character
is the static requirement and the second Character is the dynamic requirement.
1) static
m ; Mandatory, mandatory to be implemented.
; Out of scope, not relevant to this Profile.
i
2) dynamic
m ; Mandatory (use is mandatory)
---------------------- Page: 13 ----------------------
SIST EN ISP 10608-1:1997
ISOAEC ISP 1060~1:1992 (E)
A.3 Transport Layer IPRL
A.3.1 NCMS functions
Profile Features
Base Standard Features
I I
ISP
References Status
Index Feature Status
References
I l
I 1
6.3.1 0 i
N2 Network connection management
I
r ,
Diagnostic 7.6.2, 7.7 0
N3
P I
Active network connection recovery 7.4.2 0
N4
A.3.2 Supported functions in Class 4 (C4 or C4L::)
Profile Features
Base Standard Features I I
ISP
References Status
Index Feature
References Status
I I l
1
T4F29 6.17 0 1 5.2.2 b) 1 m 1
Non-use of checksum
A.3.3 Supported Parameters of issued TPDUs
A.3.3.1 Supported Parameters for NCMS (Al::)
A.3.3.2 UN TPDU (SNI::)
Profile Features
Base Standard Features
I I
ISP
Values allowed Status
Index
Supported ParametersReferences
References
I
L 3
IUl Protocol Identifier 8.3.3 b) IS08073,IS08602,Private 1 ISO8073 1
I
---------------------- Page: 14 ----------------------
SIST EN ISP 10608-1:1997
ISOAEC ISP 106084 :1992 (E)
A.3.3.3 Supported Parameters for class 4 TPDUs (C4 or CL4::)
Base Standard Features
Profile Features
~~~~ --1
I
Index
Supported Parameters $$Fse Of 1 Status (
I I
l4CR7 Called TSAP ID 13.3.4 a) 0 m
l
r
14CRll Protection Parameters 13.3.4 d) 0 i
I
I
1 14CR12 1 Additional Option selection 13.3.4 f) 0 m
1
I I
1 14CR13 1 Throughput 1 13.3.4 j,Ir-ö---j i
1 14CR14 1 Residual error rate 1 13.3.4 k) 1 0 -1 i
1 14CR15 1 Priority 1 13.3.4 m) 1 0 1 i
1
1 14CR16 1 Transit delay 1 13.3.4 n) 1 0
i
I
l4CC7 1 13.4.4 1 0 1
Calling TSAP ID m
I
I I- 1
l4CC9 Protection Parameters 1 13.4.4-101
i
I I
1 14CClO 1 Additional Option selection 1 13.4.4 1 0 -1
Il4CC12 1 Throughput 1 13.4.4 1 0 1
1 MC13 1 Residual error rate 1 13.4.4 1 0-j i
1 14CC14 1 Priority 1 13.4.4 1 0 1
II4CC15 (Transit delay
1 13.4.4 IO i
l4DR4 Additional information 13.54 a)
0 i
A.3.4 Protocol Implementation
A.3.4.1 Classes Implemented
\
Base Standard Features
, 1
Index Feature References Status
L 1
C4L Class 4 Operation over CLNS 14 ISO:C2:0
.
A.3.4.2 Class negotiation - responder side
1 Profile Features
Base Standard Features
1
Al lowed
References
1 Index 1 Feature
1 Ref e
Responses
2,4 or conn. 4
RC4 What classes tan you respond with 6.5.4 h)
refused
if CR proposes only class 4 Table 3
depending
on classes
supported
*
7
---------------------- Page: 15 ----------------------
SIST EN ISP 10608-1:1997
ISOAEC ISP 1060&1:1992 (E)
Annex B
(normative)
List of defect reports
B.1 Introduction
Defect reports which affect technical contents of ISO/IEC 8073, its amendments, and technical corrigenda
(see clause 2) are listed in this annex. These defect reports are generated and authorized by ISO/IEC JTCl/
SC6, but not yet published as a technical corrigendum. The defect reports in this annex are included
because they contain relevant information about the significance and requirements of the base Standard.
Implernentations shall conform to the base Standard amended as proposed in these defect reports.
1 .
Defectport Number; 8073153
8. malifier; Technical
9. Reference in Document: subclause 12.2.4.2
.
10. N;aiYre of Detect,
Applying the retransmission procedure to the release Phase may lead to opening a new network con-
nection for retransmitting a DR. lt should also be possible in this case to release the transport con-
nection.
.
.
11 . jd bv
_ the Source,
Append to 12.2.4.2 the following:
“NOTE - Although the retransmission procedure also applies to the DR TPDU in the release Phase, it is however possible to
consider that the transport connection has been released if it would be necessary to open a new network connection for retrans-
mitting the DR TPDU ”.
12. Editor% Resrx>nse:
Append to 12.2.4.2 the following:
“Although the retransmission procedure also applies to the DR TPDU in the release Phase, the trans-
port entity may however consider that the transport connection has been released if it would be nec-
essary to open a new network connection in Order to retransmit the DR TPDU ”.
1 .
Defect Report Number; 8073164
8 . Qualifier: Technical
.
9 . ence In Dowment; subclause 6.1.3, Paragraph 3 and 5
10. Nature of Defect:
Clarification associated with Defect Report 8073163.
11 . Salut ion Propose- the Source; See item 12
Subclause 6.1.3, Paragraph 3:
Replace the term “a transport entity” with the term “the initiator ”.
Subclause 6.1.3, Paragraph 5 - add the following sentence to c):
“In this case, both initiator and responder become aware of the assignment ”.
.
12 . Editor% Response,
In subclause 6.1.3, Paragraph 3:
Replace the term “a transport entity” with the term “the initiator- “.
---------------------- Page: 16 ----------------------
SIST EN ISP 10608-1:1997
ISO/IEC ISP 106084 :1992 (E)
Annex C
(normative)
International Standardized Profile Implementation Conformance
Statement Requirements List (IPRL)
C.l Introduction
The IPRL in this annex specifies the additional requirements for ISO 8473. The requirements of ISO 8473
apply to each item for which there is no entry in this IPRL.
The IPRL in this annex is based on the working draft of the proforma that has not yet been reviewed by the
cognizant ISO technical committee.
This I PRL specifies full implementation of the Connectionless-mode Network Protocol for end Systems.
Nei-
ther of the two subsets identified in ISO 8473 is relevant. Intermediate System Operation is not specified.
A conforming implementation shall satisfy the mandatory conformance requirements of the base Standard
referenced in this part of the Profile.
C.2 Notation
The following tables define the functions supported for which conformance is claimed, using the following
keys.
a) Base Standard Status notation
1) base Standard type or range
M ; mandatory.
0 ; optional.
; not applicable.
.
O.
optional, but support of at least one of the group of Options labeled by the Same
#
numeral en> is required.
: ; this predicate Symbol means that the Status following it applies only when the
PICS states that one or more of the items identified by the index is supported. In
the simplest case, is the identifying tag of a Single PICS item.
may also be a Boolean expression composed of several lndices.
:: ; When this group predicate is true the associated clause should be completed.
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.