Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!VENERA.ISI.EDU!braden
From: braden@VENERA.ISI.EDU
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  Specification of Berkeley networking utilities
Message-ID: <8810262157.AA06640@braden.isi.edu>
Date: 26 Oct 88 21:57:29 GMT
Article-I.D.: braden.8810262157.AA06640
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 18


	
	Surely you jest!  Maybe once telnet can: (1) log you in without requiring
	a password in a file, (2) handle remote window size changes, (3) handle
	OOB data for (e.g.) SIGINT output flushing, and (4) have every machine
	handle raw octet data correctly, then I'll believe you. 
	
Phil,

   I believe that a properly implemented Telnet can handle all except (1)
   (note that RFC-1073 just got around to fixing (2)). Not everyone agrees
   that (1) is a good idea, although we obviously need a secure method
   to accomplish the same thing.

   It appears to me that the purported advantages of rlogin are due to
   poor Telnet implementations; do you disagree?
   
   Bob Braden