Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!CS.UCL.AC.UK!S.Walton
From: S.Walton@CS.UCL.AC.UK (Simon Walton)
Newsgroups: comp.protocols.iso
Subject: Re: X.224 (Transport) state table question
Message-ID: <3652.650130431@UK.AC.UCL.CS>
Date: 8 Aug 90 15:47:11 GMT
References: <1990Aug6.111420.13755@idt.unit.no>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 14


   The network connection will normally be closed by the
initiating entity when it receives the DR-TPDU. Table A-6
says that when in state `waiting for CC' event DR happens one
should take action [1], which table A-5 defines as `If the
network connection is not used by another transport connection
assigned to it, it may be released.' The situation is similar
to that if a TP1-3 connection is disconnected normally, the
transport entity may keep the network connection for future
use, or may close it - the decision is a local matter.
   I agree that the protocol error for event NDISind in state
`closed' is a bit strange. I suspect this is an error.

Simon