Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ames!ucbcad!ucbvax!RADC-MULTICS.ARPA!Ata
From: Ata@RADC-MULTICS.ARPA ("John G. Ata")
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Telnet, <CR><LF>, etc.
Message-ID: <870803162359.017191@RADC-MULTICS.ARPA>
Date: Mon, 3-Aug-87 12:23:00 EDT
Article-I.D.: RADC-MUL.870803162359.017191
Posted: Mon Aug  3 12:23:00 1987
Date-Received: Tue, 4-Aug-87 03:50:13 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 18


Greg,
          I have to disagree with your TELNET sending a <CR><NL> if the
user types a <CR> with local echoing and sending a <CR><NUL> if remote
echoing takes place.  While this may be useful in some UNIX
applications, who expect this convention, it certainly confuses some of
us non-UNIX hosts out there trying to talk to you.  For example, we use
remote echoing to supress the local echo of a password.  Thus, when a
user types her password, remote echoing takes place and the <CR> typed
at the end of the password gets sent as a <CR><NUL>.  This gets
interpreted at our end as a <CR> which is NOT our end-of-line character.
Of course, this causes a hang which can be very frustrating.  Please, do
not confuse local/remote echoing with some sort of private mode where
TELNET ASCII characters get interpreted differently.  I realize that
this may be convenient for you, but it makes talking to different
machines on the network, much more difficult.

                    John G. Ata