Brief Discussion

The PDP-10 space required to implement the above protocol is about 400 instructions, divided equally between the input and the output side. Enough experimental coding has been done to confirm the feasibility of this basic strategy, taken together with experience with implementation and use of the SOS buffering system.

The above does not touch the question of LOGON protocol, except indirectly. My belief is that it can be accommodated in the framework of this proposal, but I have not tested this theory as yet. As indicated further above, I would be tempted to handle the matter with the SYS flag, given that SYS data is interpreted directly by the system (in our system, we would use the RUN UUO to run the LOGON CUSP, which would, in turn handshake using ASCII data over the link). In this way, I think we might be able to dispense with the notion of dedicated sockets and the reconnection morass.

One other point that needs thought is the question of how to handle the interrupt on link facility. Should it have any direct relation to the GET/PUT UUO's, or be handled on the side? I am inclined to think that it should be treated qua interrupt of the user process, quite independently of the matter of data transmission over the link. Some of our current work on the PDP-10 monitor would lend itself rather easily to implementation as a true interrupt.