Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!nuug!sigyn.idt.unit.no!lear!hta
From: harald.alvestrand@elab-runit.sintef.no
Newsgroups: comp.protocols.iso
Subject: X.224 (Transport) state table question
Keywords: TP0
Message-ID: <1990Aug6.111420.13755@idt.unit.no>
Date: 6 Aug 90 11:14:20 GMT
Sender: news@idt.unit.no (Usenet news admin)
Reply-To: harald.alvestrand@elab-runit.sintef.no
Organization: ELAB-RUNIT, SINTEF, Norway
Lines: 28

Can someone help me out on this one?
I have tried to make a "robust" TP0 server that functions according to the spec
(well, actually it is RFC1006....)
The standard (X.224, Blue book version) claims that Appendix A, the
state tables,
gives "a more concise definition....".
A bit too concise for me, it seems. Watch this:

- A network connection is set up.
- A CR TPDU arrives. Transition: CLOSED to WFTRESP, indicate TCONind to user.
- The user refuser using TDISreq. Transition: WFTRESP to CLOSED, send a DR.

Now what?
I cannot close the connection, because that will likely eat the DR.
Besides, there
is no close indicated in the table.
An NDISind on this connection (Transport connection is identifiable
because I am
in class zero) will hit the empty field where CLOSED and NDISind meet in
the matrix, indicating a protocol error.

There is no timeout given, so I cannot close the connection after a timeout.
What is the opinion of the standards writers on when the network
connection should
be closed, if the sender part does not take proper action and closes it?

                    Harald Tveit Alvestrand
                    Hacker of ISO-everything