RFC 426 Reconnection Protocol January 1973 If the user doesn't trust the Host and is afraid that it might read his password rather than pass him off to the authenticator he could connect directly to the authentication service. After authentication, the Authenticator can pass him off to the Host. C. The McROSS air traffic simulation system (see 1972 SJCC paper) already supports reconnection. It permits an on-going simulation to reconfigure itself by allowing parts to move from computer to computer. For example, in a simulation of air traffic in the Northeast the program fragment simulating the New York Enroute air space could move from Host2 to Host5 (see Figure 3). As part of the reconfiguration process the New York Terminal area simulator and Boston Enroute area simulators break their connections with New York Enroute simulator at Host2 and reconnect to it at Host5. NY Terminal NY Enroute Boston Enroute Boston Terminal _____ _____ _____ _____ | | / | | \ | | | | |Host1|<----/--->|Host2|<---\---->|Host3|<----->|Host4| |_____| \ / |_____| \ / |_____| |_____| X move X / \ | / \ | \ V / | V \ _____ / V reconnect \ | | / reconnect ->|Host5|<- |_____| NY Enroute Figure 3 2. A Reconnection Mechanism The mechanism proposed here could be added to the existing Host-Host protocol or to the TELNET protocol. The mechanism is first described and then its adaptation to each of the protocols is discussed. The reconnection mechanism includes four commands: Reconnect Request: RRQ Reconnect OK: ROK Reconnect No: RNO Reconnect Do: RDO where is the communication path to be redirected to . Assume that H1 wants to move its end of communication path A-C from itself to port D at H3 (See figure 4). Thomas