dg@lakart.UUCP (David Goodenough) (03/07/89)
I have been looking at the specs for how the two ends of a "g" protocol conversation get started, and what I don't see is how you solve the following situation: Site A Site B Send INITA Send INITA Recv INITA Recv INITA Send INITB Send INITB Recv -BAD- Recv INITB Send INITB Send INITC Recv INITC Recv INITB First pair of send receive (INITA) packets is OK. Both have sent and received INITA messages, so both now go to work on the INITB messages. Site A's INITB gets through OK, but Site B's INITB gets zapped by line noise. Site A has Not received an INITB, so he can't send an INITC yet. Site B has sent and received an INITB, so he starts sending INITC's. Site A will never get an INITB, so they just sit there and send INIT messages back and forth at each other. Site A _COULD_ ignore the missing message, send an INITC, and assume all is well, and I'd guess that this is why the packet size has to be fixed at 64, because Site A never saw site B's INITB packet. Comments???????????????? -- dg@lakart.UUCP - David Goodenough +---+ IHS | +-+-+ ....... !harvard!xait!lakart!dg +-+-+ | AKA: dg%lakart.uucp@xait.xerox.com +---+