🚀 go-pugleaf

   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