RFC 76 (rfc76) - Page 4 of 15
Connection by name: User oriented protocol
Alternative Format: Original Text Document
RFC 76 Connection-By-Name: User-Oriented Protocol October 1970 III. Example of User Dialogue Assume a user residing at CAC, whose site code is URBANA. His terminal is an alphanumeric CRT terminal and we assume solution of code conversion problems for network communications. The sample user session will involve the setting up of two processes at two host sites with control from the third host site. All operations can be accomplished with the current protocol plus the proposed extensions. In addition, we also assume that some form of standard user code is in use for all host sites uniquely identifying every network user when he is present. Output keyed by systems will be underlined. Comments are offset to the right for legibility. All statements about the UTAH system are purely hypothetical. User Dialogue Comments The user moves to the terminal, applies power and types: HELLO The CAC system responds for login purposes with: USER= GROSSMAN ------ for the user's code. 1437 TR7/GROSSMAN LOGGED IN ___________________________ LINE PRINTER DOWN TILL 1600 ___________________________ This acknowledges proper usercode and sends any appropriate notes on system status. ! LINK TO ILLIAC The exclamation point (!) is the escape character which flags direct input to the PDP-11 OS: User requests connection to the ILLIAC IV node. NCP operations establish link from user terminal to B6500 MCP. Bouknight, et al.
