Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!ucsd!ucbvax!gui.consumers.com!Isaac
From: Isaac@gui.consumers.com
Newsgroups: comp.protocols.iso
Subject: Re: X.224 (Transport) state table questi
Message-ID: <26C05D91@gui.consumers.com>
Date: 8 Aug 90 18:44:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 23

I think we can look at Note 4 in 6.7.5 for guidance here.

  Execpt in Class 4, it is suggested that if a transport entity does not 
  receive acknowledgment of a DR TPDU within time TS2, it should either reset 
  or disconnect the network connection, ...

Also, according to Note 3 in 6.1.3,

  It is suggested that only the owner of ... a network connection should 
  release it.

Therefore, it is up to the sender of the CR TPDU to disconnect the network 
connection after receiving the DR TPDU.  But if the network connection is not 
release after TS2 time, the sender of the DR TPDU can release it.

I think the transport spec is the way it is because it was written with 
multiplexing and splitting in mind.  These elements of procedure, of course,
do not apply in the Class 0 case so you will have to read between the lines
sometime.


Isaac Chan, Consumers Software Inc.
isaac@gui.consumers.com