ISO 8327:1987/Amd 3:1992
(Amendment)Information processing systems — Open Systems Interconnection — Basic connection oriented session protocol specification — Amendment 3
Information processing systems — Open Systems Interconnection — Basic connection oriented session protocol specification — Amendment 3
Systèmes de traitement de l'information — Interconnexion de systèmes ouverts — Protocole de session en mode connexion — Amendement 3
General Information
Relations
Standards Content (Sample)
IS0
INTERNATIONAL
8327
STANDARD
First edition
1987-08-1 5
AMENDMENT 3
1992-12-15
Information processing systems - Open
Systems Interconnection - Basic connection
oriented session protocol specification
AMENDMENT 3: Additiona I synchronization
fu nctiona I ity
Systèmes de traitement de l'information - Interconnexion de systèmes
ouverts -Protocole de session en mode connexion
3: Fonction de synchronisation supplémentaire
AMENDEMENT
Reference number
IS0 8327:1987/Amd. 3:1992 (E)
---------------------- Page: 1 ----------------------
IS0 8327:1987/Amd. 3:1992 (E)
Foreword
IS0 (the International Organization for Standardization) and IEC (the International
Electrotechnical Commission) form the specialized system for worldwide
IS0 or IEC participate in the
standardization. National bodies that are members of
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
for voting. Publication as an
technical committee are circulated to national bodies
by at least 75 96 of the national bodies casting
International Standard requires approval
a vote.
Amendment 3 to International Standard IS0 8327: 1987 was prepared by Joint
Technical Committee ISO/IEC JTC 1, Informution technology.
O ISOllEC 1992
All rights reserved. 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.
Internationai Organization for Standardization
Case postale 56 . CH-121 I Genève 20 . Switzerland
Printed in Switzerland
ii
---------------------- Page: 2 ----------------------
IS0 8327:1987/Amd. 3:1992 (E)
Information processing systems - Open Systems
Interconnection - Basic connection oriented session
protocol specification
AMENDMENT 3: Additional synchronization
functionality
Introduction to this Amendment
This Amendment introduces the data separation functional unit into the Session Protocol Specification. The
data separation functional unit supports the additional functionality of separation of data before and after a
minor synchronization point. It should be noted that the page and clause numbering in this Amendment
relate to SC 21 N4656 “Revised version of IS0 8327”, which is planned to be submitted for publication later
0 this year. This is because this Amendment affects changes introduced by earlier Amendments and Addenda.
This Amendment makes no change to any other part of the Session Protocol.
Page 4
Subclause 4.5 Local variables
Insert new items in the list after Vsc as follows
I “ V(Ado) see 5.8.3.5
L V(Adi) see 5.8.3.6”
I
1
I
I
Page 8
i
Subclause 5.4.3 Data transfer phase
Insert a new item after 5.4.3 f) as follows and re-letter the subsequent items g) to k) as h) to 1)
e
“g) data separation is used in association with either minor synchronization or symmetric
synchronization. This allows the user to set specific minor synchronization points which have
the property of protecting the flow sent before these points from being purged by a subsequent
resynchronize. When such a point is set in the data flow, SPDUs received by the requesting
SPM before this point has been acknowledged will not be discarded by a subsequent
resynchronize.”
Page 9
Table 3 - Functional units
Insert a new entry after Symmetric Synchronize as follows
Functional unit SPDU code SPDU name Reference
No additional associated SPDUs
Data separation
I
1
---------------------- Page: 3 ----------------------
IS0 8327:1987/Amd. 3:1992 (E)
Page II
Subclause 5.5 Functional units
Insert a new subclause after subclause 5.5.9 and re-number subsequent subclauses 5.5.10 to 5.5.13 as 5.5.11
to 5.5.14:
“5.5.10 Data separation functional unit
The data separation functional unit is always associated with either the minor synchronize
functional unit or the symmetric synchronize functional unit. It allows the user to define
minor synchronization points which clearly separate the normal flow before and after these
points and which are protected against possible discard by a subsequent resynchronize. It is
not valid to select both this functional unit and the activity management functional unit for
use on the same session connection.”
Page II
Negotiation of functional units
Subclause 5.7.1
Insert a new paragraph at the end of subclause 5.7.1 as follows
“The data separation functional unit can only be proposed if the minor synchronize
functional unit or the symmetric synchronize functional unit is proposed.”
Page I2
Subclause 5.8.3 Synchronization point variables for use without the symmetric synchronize
functional unit
Insert two new subclauses after subclause 5.8.3.4
“5.8.3.5 V(Ado)
V(Ado) is used by the SPM and is the highest synchronization point serial number which O
was sent in a MINOR SYNCHRONIZATION POINT SPDU with the data separation
parameter set to true. Received SPDUs cannot be discarded in case of resynchronization
when V(Ado) is greater than or equal to V(A).
5.83.6 V(Adi)
V(Adi) is used by the SPM and is the highest synchronization point serial number which was
received in a MINOR SYNCHRONIZAmON POINT SPDU with the data separation
parameter set to true.”
---------------------- Page: 4 ----------------------
ISO 8327:1987iAmd. 3:1992 (E)
Page 29
Subclause 7.20.1 Content of the MINOR SYNC SPDU
Replace item a) by the following
“a) a Sync Type item which is used to indicate :
if an explicit confirmation is required;
1)
if the data separation is requested.”
2)
Page 29
Subclause 7.20.2 Sending the MINOR SYNC SPDU
Add the following before the last sentence
“If the Sync Type parameter has the value “data separation”, V(Ado) is set to V(M).”
Page 32
Subclause 7.24.2.1 Sending the RESYNCHRONIZE SPDU without symmetric synchronization
Replace the last sentence of the first paragraph with the following
“If the transport expedited flow is available to this session connection and the Data
Separation functional unit has not been selected, a PREPARE (RESYNCHRONIZE) SPDU
is sent simultaneously, or earlier, on the transport expedited flow. If the transport expedited
flow is available to this session connection and the Data Separation functional unit has been
selected, one of the following applies:
a) if a previously sent MINOR SYNCHRO”i0N POINT, SPDU with the
Sync Type Item having the value “data separation” has not been acknowledged,
then a PREPARE (RESYNCHRONIZE) SPDU shall not be sent;
a
b) otherwise, a PREPARE (RESYNCHRONIZE) SPDU may be sent, as a local
matter.”
3
---------------------- Page: 5 ----------------------
IS0 8327: 1987/Amd. 3:1992 (E)
Page 32
Subclause 7.24.2.1 Sending the RESYNCHRONIZE SPDU without symmetric synchronization
I
Replace the second paragraph with the following
“The SPM goes into a state where incoming SPDUs are discarded in the following way :
I
a) if the Data Separation functional unit is not selected or if there is no
unacknowledged minor synchronization point with the Sync Type item having the
value “data separation’’ (previously sent by the local SPM), all SPDUs are
discarded except : PREPARE (RESYNCHRONIZE), RESYNCHRONIZE,
PREPARE (RESYNCHRONIZE ACK), RESYNCHRONIZE ACK, ACTIVITY
DISCARD, ACTIVITY INTERRUPT and ABORT SPDUs.
b) if the Data Separation functional unit is selected and there are
unacknowledged minor synchronization points with the Sync Type item having the
value “data separation” (previously sent by the local SPM), only the following
(I
SPDUs are discarded : PREPARE (MAJOR SYNC ACK) SPDUs, MAJOR SYNC
ACK SPDUs (see the note).
NOTE - The MAJOR SYNC ACK SPDU is discarded (and therefore does not result in an
S-SYNC-MAJOR confirm) because the previously issued S-RESYNC request prevented the
completion of the dialogue unit. It is not possible to deliver the S-SYNC-MAJOR confirm
because this would cause V(R) to be updated and this may be a later value than that to which the
resynchronize is occurring.”
Page 32
Subclause 7.24.2.2 Receiving the RESYNCHRONIZE SPDU without symmetric synchronization
Replace the second paragraph with the following
“When the PREPARE(RESYNCHR0NZE) SPDU is received, the SPM goes into a state
where incoming SPDUs are discarded in the following way :
a) if the Data Separation functional unit is not selected or if there is no
d
outstanding minor synchronization point with the Sync ï3qx item having the value
“data separation”, all SPDUs are discarded, until the RESYNCHRONIZE SPDU is
received, except for ABORT SPDUs.
b) if the Data Separation functional unit is selected and there are one or more
outstanding minor synchronization points with the Sync Type item having the value
“data separation’’ (previously sent by the SPM), only the following SPDUs are
discarded, until the RESYNCHRONIZE SPDU is received : PREPARE (MAJOR
SYNC ACK) SPDUs, MAJOR SYNC ACK SPDUs (see the note).
NOTE - The MAJOR SYNC ACK SPDU is discarded (and therefore does not result in an
S-SYNC-MAJOR confirm) because the previously issued S-RESYNC request prevented the
completion of the dialogue unit. It is not possible to deliver the S-SYNC-MAJOR confkn because
this would cause V(R) to be updated and this may be a later value than that to which the
resynchronize is occurring.”
4
---------------------- Page: 6 ----------------------
IS0 8327:1987/Amd. 3:1992 (E)
Page 35
Subclause 7.25.2.1 Sending the RESYNCHRONIZE ACK SPDU without symmetric
synchronization
Add a new paragraph at the end of 7.25.2.1 as follows
“If the Data Separation functional unit has been selected, V(Ado) is set to -1 .”
Page 35
Subclause 7.25.2.2 Receiving the RESYNCHRONIZE ACK SPDU without symmetric
synchronization
Add a new paragraph at the end of 7.25.2.2 as follows
“If the Data Separation functional unit has been selected, V(Adi) is set to - 1 .”
e
Page 47
Subclause 8.3.1.13
Insert a new item after 8.3.1.13 1) as follows and re-letter the subsequent items m) and n) as n) and O)
“m) bit 13 : data separation functional unit”
Replace “Bits 13-16 are reserved” with “Bits 14-16 are reserved”
Page 56
Subclause 8.3.20.3
Replace the subclause as follows
“8.3.20.3 The Sync Type item PV field, if present, shall indicate the following
a) bit 1 = 1 : explicit confirmation not required
bit 1 = O : explicit confirmation required
b) bit 2 = 1 : data separation required
bit 2 = O : data separation not required
Bits 3-8 are reserved.
This parameter field shall be absent if an explicit confirmation is required and data
separation is not required.”
5
---------------------- Page: 7 ----------------------
IS0 8327:1987/Amd. 3:1992 (E)
Page 70
Subclause A.5.1 Functional units
Replace the fu-dom expression as follows
=
“ fu-dom (FD, HD, EXCEP, TD, NR, SY, SS, DS, MA, RESYN, EX, ACT,
CD)”
Add the following to the list of functional units after “SS = Symmetric synchronize functional unit”
“DS = Data separation functional unit”
Page 73
Subclause A.5.4 Variables
Insert two subclauses after subclause A.5.4.14 and renumber subsequent subclauses A.5.4.15 to A.5.4.18 as e
A.5.4.17 to A5.4.20
“A.5.4.15 V(Ado)
V(Ado) is used by the SPM and is the highest synchronization point serial number which
was sent in a MINOR SYNCHRONIZATION POINT SPDU with the data separation
parameter set to true. Received SPDUs cannot be discarded in caSe of resynchronization
when V(Ado) is greater than or equal to V(A).
A.5.4.16 V(Adi)
V(Adi) is used by the SPM and is the highest synchronization point serial number which was
received in a MINOR SYNCHRONIZATION POINT SPDU with the data separation
parameter set to true.”
Page 75
Table 47 -Incoming events
Insert a new entq after SSYNmreq as follows
Abbreviated name Category Name and description
ISSYNmdreq I SS-user I S-SYNC-MINOR (data separation) request primitive I
6
---------------------- Page: 8 ----------------------
IS0 8327:1987/Amd. 3:1992 (E)
Page 76
Table 47 - Incoming events
Insert a new entry after MIP as follows
Abbreviated name Category Name and description
MIP-d SPDU MINOR SYNC POINT (data separation) SPDU
Page 78
Table 49 - Outgoing events
Insert a new entry after SSYNmind as follows
e
Abbreviated name Category Name and description
SSYNmdind SS-user S-SYNC-MINOR (data separation) indication
primitive
Page 79
Table 49 - Outgoing events
Insert a new entry after MIP as follows
Abbreviated name Category Name and description
MIP-d SPDU MINOR SYNC POINT (data separation) SPDU ,
7
---------------------- Page: 9 ----------------------
IS0 8327:1987/Amd. 3:1992 (E)
Pages 82,83
Table 52 - Specific actions
Change the following actions
[SI insert
Set V(Ado) = -1
Set V(Adi) = -1
1281 insert
Set V(Ado) = -1
Set V(Adi) = -1
1681 insert
Set V(Ado) = -1
Set V(Adi) = -1
1711 insert Set V(Ado) = -1
Set V(Adi) = -1
Insert new actions as follows
Set V(Ado) = V(M)
1411
Set V(Ado) = V(Ms)
1421
Set V(Ado) = -1
1431
Set V(Adi) = -1
Set V(Adi) = V(M)
1441
Set V(Adi) = V(Mr)
WI
Pages 84,235
Table 53 - Predicates
Replace predicate p35 as follows
FU(RESYN) & ririeXp OR F'U(DS)]
P35
p185 as follows
Replace predicate
p185
discard-rcv-flow & 38 1
Insert new predicates as follows
-'FU(DS)
P80
OR rFU(SS) & V(Adi) c V(A) ]
OR [FU(SS) & V(Adi) c V(Ar) ]
rFU(SS) & V(Ado) 2 V(A) ]
OR [FU(SS) & V(Ado) 2 V(As) ]
WDS)
8
---------------------- Page: 10 ----------------------
IS0 8327:1987/Amd. 3:1992 (E)
After the table insert new note 5 as follows
“5 PR is not sent if p8 1 is true, or TEXP is false, or, as a local choice, if the data separation functional
unit is selected.”
Pages 86-1 to 86-44
Tables 54 to 71 - State tables
Replace the state tables with the following pages.
Editorial note: Any transitions which are possibly missing from the 1990 text are not
included. The changes are made to both the state tables without the symmetric synchronize
functional unit and the state tables with the symmetric synchronize functional unit. However,
a number of errors have been discovered in the second set of state tables. No attempt has
been made to correct these errors in this Amendment, so the first set of state tables should be
regarded as more complete and correct.
e
Cells which have been altered are shaded.
9
---------------------- Page: 11 ----------------------
IS0 8327: 1987/Amd. 3: 1992 (E)
Table 54 -Connection establishment state table without the symmetric synchronize functional unit
-
State STAOl irIAO1A STAOlB STAOlC
STAOlD STAOZA STA02B
idle await await idle
await await await await wait await
Event
no TC AA i'CONca TC con
CDO I AC SCONrsp afterPR-AB TDLTin
AC
XAOlA TDISreq
Il Il SCONcnf+ 1 OA STA15D STAlC
STAOl
CDO
TDISreq
Il Il STA15D
STAOl 1 I
S AOlD
CN
I1)ISreq lpOl&- 76&p204
Il TDISre,
8A
s4201
p01 SlBl
S AOlD
y1&- 768~~~204
SCBNind
STAO8
'pOl& 76&'pO2
&-tlr
S'i[;z116
-(Pol& 76âp02
&-r
STAOlC
STAOl
OA
Il TDISreq CDO STAlSD
STAOl
p 11
S A02A t
RF-nr TAOlA TDISreq
Il Il SCONcnf- SCONcnf. STAl6
STAOl
TDISreq TDISreq
STAOl STAOl
RF-r
TAOlA TDISreq
Il Il -I- STAl6
STAOl
SCEnf- scxnf.
I
TDISnq TDISnq
STAOl STAOl
sc8Ecnf- sc8Ecnf-
STAOlC STAOIC
SCONnq
'CONreq pol& 204
&
;T62diB I
STA02B
po132w
STAO2A
SCONrspt
t STA15D
SCONrsp
S'r[A]l6
7-
ïCONcnf
Il Il Il Il
PE Il
iTAO2B
$F STA02A
i'CONind 4 CONrsp
Il Il Il
Il
10
---------------------- Page: 12 ----------------------
IS0 8327:1987/Amd. 3:1992 (E)
Table 55 -
-
STAOlC
await idle
TC con
Event
STAOlA TDISnq
STAOl
STAOlA TDISnq
STAOl
T
TDISnq
STAOl
Table 55 (continued)
11
---------------------- Page: 13 ----------------------
IS0 8327:1987/Amd. 3:1992 (E)
Table SS (concluded)
State] STAlSC STA15D I STA16
STA18 STA19 STA20
STA21 STA713
await await
await await data
GTA recovery(init)
recovery CDA transfer
~
y:.:.:.:.:.:.:.: :.: 1 STA16
STA19
. . . . . . . . . ,
. . . . . . . . . .
,.:.:.:.:.::. .
S8T?nd
SPA0 S&:d Sl%?nd
STA18 STA21 STA713
Sgnd s.FoA8i9
SEO Sgd Sad
STA18
STA21 STA713
SiEnd SG9 SEO Sgnd Sgd
STA18
STA21 STA713
sDTreq I I STA15D I
STA15D
STA15D
12
---------------------- Page: 14 ----------------------
IS0 8327:1987/Amd. 3:1992 (E)
Table 56 (concluded)
I I I
STA16 1
13
---------------------- Page: 15 ----------------------
IS0 8327:1987/Amd. 3:1992 (E)
Table 56 (continued)
State
STAOlD STA03 STA04A
STA04B STAOSA STAOSB
await await await
await await await
Event
CDO DN PR or MAA
PR or AEA PR or RA PR or AL!
AE STAOlA TDISreq
TDISreq
STAOl STAOl
MIA TDISreq
STAOlA TDISreq 17&p21 p17& 20&p21
STAOl STAOl &YNmcnf SS 24 mcnf
SA3 kz5k S’#%A
MIP
STAOlA TDISreq
jlj
MlP-d
SSYNmrsp
14
---------------------- Page: 16 ----------------------
IS0 8327:1987/Amd. 3:1992 (E)
Table 56 (continued)
STAlSA
STAlOB
STAW STAlOA
STAO6
STAOSC
await wait
await
await
await RS
await
after PR-MAA
SACTErsp
PR or ADA aft er COU SRELrsp SSYNMrsp
~72
II
15
---------------------- Page: 17 ----------------------
IS0 8327:1987/Amd. 3:1992 (E)
Table 56 (concluded)
-
stat
STAlSB STAlSC STAlSD
STA16 STAU
STA20 STA7
wait
wait wait await
await await datr
Event
after PR-RS
after PR-RA after PR-AB IDISilIC
recovery(init1 recovery transl
AJ.3
STA16
MIA
STA16
p17& 21
STJO
p1Ff21 SA9
MnJ
STA16
plFflg SA9
___1___
MIP-d
82
SACïEkeq
STAlSD-
SACTErF
SSYNmdreq
SSYNmItq
I STA15D
SSYNmrsp
STAlSD
%!!I%
---------------------- Page: 18 ----------------------
IS0 8327:1987lAmd. 3:1992 (E)
Table 57 - Resynchronization state table without the symmetric synchronize functional Unit
-
STAOPA I STA04B 1 STAOSA
- -. - . . -
STA03
jTAOlC
state I X'AOIA
await
await
await
await idle
PR or RA
TC con
hent AA
STA15C
[aisrno I I
DISreq
'R-RA ITAOlA
STAO1
DISreq
'R-RS iTAO1A
STAO1
iTAOlA DISnq
STAOl
24& 35
iTAOlA DISreq rDISreq
RS-a
~TAOQA
STAOl STAOl
4'61
S AllA
$161
S AllA
324& 328~~35
RS-r STAOlA rDISreq
STlO5A
&%% 4'61 &%?:d 4161
STAOl
S AllA p24& 32&p35
S AllA
SRfYNind
$161
S AllA
35
STAOlA rDISreq
RS-s
1824ei TAOSA 35
SRdkNind SRd%ind
STAOl
S $161 AllA d8lA
&t%?d
$161
S AllA
SRSYNreq(a)
SRSYNreq(r)
SRSYNreq(s)
SRSYNrso
17
---------------------- Page: 19 ----------------------
IS0 8327:1987/Amd, 3:1992 (E)
Table 57 (continued)
State1 STAOSB
STAW
await
await
Event PR or AL
SRELrsp
STAlSC
PR-RS
STAOSC
I S.i.Al6
S&&B
7
SRSYNEq(a)
iRSïNreq(r)
IRSïNnq(s)
---I---
+
18
---------------------- Page: 20 ----------------------
IS0 8327:1987/Amd. 3:1992 (E)
Table 57 (concluded)
STA713
State STAlSB STAlSC STAlSD
await
await
wait wait wait
recove transfer
Event after PR-RS after PR-RA after PR-AB
PR-RA
PR-RS $101
S A15C
sTA16 I
I
l
STA16
..
$161
$161
S AllA
S AllA
STA16
STAlSD
RS-r
&%%?:d
&;%%
$161
rim
S AllA
e
35
STA16
SRIfYNind
$161
S AllA
19
---------------------- Page: 21 ----------------------
IS0 8327:1987/Amd. 3:1992 (E)
Table 58 - Activity interrupt and discard state table without the symmetric synchronize functional unit
State
STAOlA STAOlC
Event
TC con
AD
STAOlA TDISreq
STAOl
ADA
AI
AIA TDISkq
STAOlA
STAOl
SACIllreq
SACïDrsp
SAcTlreq
E%$ P39
PR-RS( 1)
AI AI
$161 $161
S A05B S A05B
SACllrsp T
STAl5B
wait y
after PR-RS
20
---------------------- Page: 22 ----------------------
IS0 8327:1987/Amd. 3:1992 (E)
Table 58 (concluded)
STA21 sTA22 STA713
STAlSD STA16 STAl9 STA20
State STAlSC
await data
wait await await await await
wait
SCDrsp transfer
CDA
Event after PR-RA after PR-AB TDISind recovery(init) recovery
STAlSD STA16
AD
&xd
&xd &xd
4161 $161
S AllC d2lC
S AllC
STAlSD STA16
ADA
STAlSD STA16
AI
SA%d &'=d
[i8xd 8A8x!
S $161 AllB
4'61
$161
4161
S AllB
S AllB S AllB
STAlSD S
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.