NWG/RFC #295 JBP 2-JAN-72 15:35 8355 Protocol Workshop Report The problem of unmatched CLS commands are discussed and four "solutions" were proposed: Hold forever Send a RST and clear the entry Clear the entry and possibly mess up a future connection Assign socket numbers in a sequential fashion to reduce the possibility of confusion and clear the entry. Note that the first two suggestions follow the protocol while the last two do not. The idea of flow control on the control link was suggested. A Request for Comments is to be prepared exploring this idea more fully. The usefulness of the ERR command is compromised if the receiver mearly throws it out. Thus ERR's are to be logged, if at all possible, and checked out with the sending site. The NCP document should make clear the implications of queueing or not queueing STR & RTS commands. Initial Connection Protocol The Initial Connection Protocol (ICP) was discussed and found to be satisfactory however the following points were stressed: The socket number sent by the logger (S) must be in agreement with the socket numbers used in the STR & RTS sent by the logger. The implications of queueing or not queueing of RTS & STR commands should be made clear in the ICP document. This is particularly important if the user chooses the "listen" option.