Date: 04 Dec 86 11:42:22 From: Mike Borsetti on 124/102, Inside Track of Dallas Metrop, Plano TX To: All on 105/6, PSG Portland of VanPort Area, Portland OR Subj: This was uploaded here by Eric Larson Telenet PC-Pursuit Dial-up Host description and protocol and server info Version 1.1.0, October 25, 1986 Supercedes version 1.0.0, September 28 1986 H.R. "Jim" Dixonr This document describes the protocol existing between a Telenet Dial-up host and the Telenet Network Interface. It also specifies the method existing at this time for users to properly access a host throught the Telenet network. A dial-up host is a system that calls into the Telenet network using this protocol and is thereby made available to PC-Pursuit users to connect to. A host is given a pre-assigned unique Network address, corresponding to the physical address of the port to which it dials up. This port will only be assigned to one particular host, and will be its identification number. There is a system provided for keeping track of and providing information about such dialed-up hosts. Its called the HOIST (Host Online Information System for Telenet). Its purpose is to keep a list of hosts that can be online and to keep track of which are online at a given time. Also, it is the means by which mail gets passed from host to host over this system. A user wanting to know what hosts exist and/or what hosts are available would open a connection to the HOIST and get the appropriate listings. The following is the protocol existing between a dial-up host and a Telenet Interface: The host dials in to the system at an appropriate speed with 8 bits, no parity. In the following list, the 'T:' is telenet's response and 'H:' is the Dialing host's response: Carrier Received. H: T: TELENET XXXYYY.ZZ TERMINAL= H: D1 T: @ H: SET? 2:0,4:2,7:8,10:0,0:0,57:1,63:0 (note: allowing network escape) T: PAR2:0,4:2,7:8,10:0,0:0,57:1,63:0 @ H: Magic-Command T: @ The following section describes the method of connecting the the HOIST using the SIGNON server. To use the signoff server, simply duplicate this section replacing 'SIGNON' with 'SIGNOFF'. H: Hoist-Address,Telenet-username T: PASSWORD = (note trailing space) H: Telenet-password T: Hoist-Address CONNECTED H: @ (escape sequence) T: TELENET @ H: SET? 2:0,4:2,7:8,10:0,0:0,57:1,63:0 (note: allowing network escape) T: PAR2:0,4:2,7:8,10:0,0:0,57:1,63:0 @ H: CONT (At least 1 second pause recommended here) H: SIGNON Server-password T (hoist): 250 operation successful (or other valid messages) (See Signon server specification for full list of messages) (Hoist will now disconnect) T: Hoist-Address DISCONNECTED 00 00 Blah Blah.. @ (End of Hoist Connection section) H: SET? 1:0,2:0,4:2,7:8,10:0,0:0,57:1,63:0 (not allowing network escape) T: PAR1:0,2:0,4:2,7:8,10:0,0:0,57:1,63:0 @ H: Magic-command T: @ The host is now ready to receive the connection message. When a user connects from a distant port the system will respond: CONNECTION FROM XXX YYY.ZZ The distant user is then connected to the port and the normal host/user dialog may begin. If the user disconnects at any time hereafter, the system will respond AT ANY TIME with: XXX YYY.ZZ DISCONNECTED VV WW The host software MUST be FULLY READY to process this string AT ALL TIMES. This may come at ANY time during the connection. If the host needs to disconnect, it must do the following: Send a break. T: TELENET @ H: D T: XXX YYY.ZZ DISCONNECTED VV WW @ It is recommended that during host/telenet dialogs, each step of Telenet's response be monitored and verified. If a verification does not occur, the host should hang up on the connection. Hanging up is not an acceptable way of the host terminating a normal connection. For this, the procedure above must be followed. NOTE: ALL types of implementations MUST at the least support the VERIFY server, and be able to talk to the SIGNON and SIGNOFF server on the HOIST. After the disconnect takes place, the host should then Hang the connection up and recycle itself. NOTE: IMPORTANT: After the connect message is received you MUST wait for another line terminated by a carriage return. On the user end,normal users must simply hit a carriage return here. A machine connecting to a server on another machine sends the Server-name (and the Server-password, if its a protected server running on the HOIST, like Signon, Signoff and Mail). For example if a machine is connected and wants to invoke the 'FOOBAR' server, its simply outputs FOOBAR at this time. These are the specified servers at this time: SIGNON - (Only exsists on HOIST) Tells the Network that the host is online and available. Each host must do this at least once every 2 hours during normal hours that it is available. SIGNOFF - (Only exsists on HOIST) Tells the Network that the host is going offline and will no longer be available. HOSTNAME - (Only exsists on HOIST) Gives various types of information about hosts on the PC-Pursuit system. VERIFY - (MUST exsist on all systems, requests ONLY valid originating from HOIST) Verifies that Host on a given port is operational and responding. FINGER - (optional) Gives various types of user (both on and off line) information. MAIL - (optional) Allows the users of multiple systems to send both online and offline messages to each other. A server has a set of commands and responses. See each seperate server specificaiton for a full list of these. Generally speaking, you invoke the server and it signs on. You then give it various commands, and it gives you various responses. The command consists of a keyword and optional parameters. A response consists of a 3 digit code followed by a text description of the meaning of the response. For example, 250 OK might be a valid response. The QUIT command is generaly used to shut down the server. It will respond with a shutdown message and terminate the connection. The SIGNON and SIGNOFF server have no commands. You invoke them with the Server-name Server-Password and they Simply take action, give one response and close the connection. The following are the possible responses: 250 - operation successful 551 - bad password 591 - Internal error - unable to process Similarly the VERIFY server also has no commands. The hoist (and only the hoist should be allowed to. You MUST check to make sure that only the known valid HOIST address is given access to this) invokes the server, and it responds with the Server-Password, and closes the Connection. Finger server protocol version 1.0 8-10-86 Commands: BRIEF [username specification] - List only online info about online users FULL [username specification] - List all info about online users WHOIS [username specification] - List all info about all users MAIL - Output in form of mail (not implemented) QUIT - Close session Responses: 211 - Text information output (non-machine readable) 212 - Username output 220 - Finger service ready 221 - Finger service closing connection 250 - Transaction completed, mail request submitted 311 - End of information 451 - No users match specification 500 - Unrecognized command 501 - Command parameter syntax error 502 - Unimplemented command 550 - Cannot request mail - Allocation exceeded 551 - Invalid mailbox specification Possible replies: Brief,Full,Whois: 211,212,311,451,501 Mail: 502 Quit: 221 Hostname server version 1.1 9/20/86 Commands: BRIEF - Gives the name address and location of matching hosts HOST - Gives full info on matching hosts Quit - End transactions Distributed in part by: Skeleton Crue 415-376-8060 located out of Moraga, California. !!Get on the band wagon before it RUNS YOU DOWN!! The very LAST bastion of Abusive Thought in all of the Suburbian West Coast... (CH&AOS)