Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site yetti.UUCP
Path: utzoo!utcs!mnetor!yetti!oz
From: oz@yetti.UUCP (Ozan Yigit)
Newsgroups: net.micro
Subject: Re: Kermit protocol in a nutshell (A bug?)
Message-ID: <193@yetti.UUCP>
Date: Mon, 3-Jun-85 20:23:29 EDT
Article-I.D.: yetti.193
Posted: Mon Jun  3 20:23:29 1985
Date-Received: Mon, 3-Jun-85 22:28:42 EDT
References: <189@yetti.UUCP> <277@spar.UUCP>
Reply-To: oz@yetti.UUCP (Ozan Yigit)
Organization: York University Computer Science
Lines: 18
Summary: 

In article <277@spar.UUCP>  kissell@spar.UUCP (Kevin Kissell) writes:
>I'm not sure whether this is a bug in the protocol or in the 
>document, but it would appear that there is no way to send an ASCII
>ETX (0x03) through kermit, since the encoding "##" is specified to mean '#' 
>rather than '^#'.  Does anyone know if this is handled, and how?
>
	No error in the protocol.. If you complement the 7th bit (6th
	if you index with 0), you get #C. In fact, all control chars
	map into valid ALPHANUMERIC characters this way.. (Remember
	the example ? If 0x01 (^A) maps to #A, naturally, 0x03 (^C) maps
	to #C..).

Oz	(All wizardesque side effects are unintentional, unless stated
	otherwise..)

	Usenet: {decvax|ihnp4|allegra|linus}!utzoo!yetti!oz
	Bitnet: oz@yuleo | oz@yuyetti