Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!ucbvax!SDSC-SDS.ARPA!GKN
From: GKN@SDSC-SDS.ARPA.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: 4.3 BSD TELNET vs. 
Message-ID: <8612310209.AA03550@ucbvax.Berkeley.EDU>
Date: Mon, 29-Dec-86 13:18:08 EST
Article-I.D.: ucbvax.8612310209.AA03550
Posted: Mon Dec 29 13:18:08 1986
Date-Received: Wed, 31-Dec-86 01:50:02 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: San Diego Supercomputer Center
Lines: 30
Approved: tcp-ip@sri-nic.arpa

[apologies if this has been brought up before, or if this is the wrong list
 to direct this query to...]

It seems that when the TELNET client program for 4.3 BSD Unix is in character
at a time mode it substitutes a  for .  While this doesn't seem to be
in clear violation of RFC 854, it does seem a little strange to me.  RFC 854
simply says that a  should be inserted in the data stream after every 
character which would not be followed by a .

There are operating systems out there where the  character is important,
VMS and CTSS being two examples I have locally.  The  character has a
legitimate, non-end-of-line use on each system.

Reading the manual page for 4.3 BSD TELNET doesn't seem to indicate that there
is any way to supress this behavior except to operate in line-at-a-time mode.

Is there someone out there who can tell me how to cause 4.3 BSD TELNET to
transmit a  (or  a la RFC 854) when I type a ?

gkn
--------------------------------------
Arpa:	GKN@SDSC.ARPA
Bitnet:	GKN@SDSC
Span:	SDSC::GKN (5.600)
USPS:	Gerard K. Newman
	San Diego Supercomputer Center
	P.O. Box 85608
	San Diego, CA 92138
AT&T:	619.534.5076
-------