Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!cbatt!ucbvax!QUABBIN.SCRC.SYMBOLICS.COM!DCP From: DCP@QUABBIN.SCRC.SYMBOLICS.COM.UUCP Newsgroups: mod.protocols.tcp-ip Subject: Telnet Wish List Message-ID: <870210101628.9.DCP@KOYAANISQATSI.S4CC.Symbolics.COM> Date: Tue, 10-Feb-87 10:16:00 EST Article-I.D.: KOYAANIS.870210101628.9.DCP Posted: Tue Feb 10 10:16:00 1987 Date-Received: Wed, 11-Feb-87 07:46:39 EST References: <8702100550.AA27790@emory.eu> Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 13 Approved: tcp-ip@sri-nic.arpa Date: Tue, 10 Feb 87 00:50:20 EST From: Ken Mandelberg One specific point for comment is the advisability of telnet instead of rlogin. Can a well implemented telnet work as well as rlogin? Is the rlogin protocol documented, or is the protocol just what the code does? Yearly TELNET flame: TELNET is a piece of junk designed for ASR33s and later tried to get improved as terminals entered a more modern age. Use SUPDUP (RFC 734). If you also want to do graphics, see the SUPDUP graphics protocol (RFC 746).