Date: Saturday, 1 January 1983  15:45-EST
Sender: DCP @ MIT-OZ
From: DCP @ MIT-MC
To:   info-oz @ MIT-OZ
Subject: TCP

My private version of the SUPDUP protocol user program
(<DCP>DUP.EXE) knows how to use the TCP gateway of a chaos site
that supports it.  This may not make much difference, since ITS
may be the only current sites with SERVER SUPDUP, but...  The
program uses VTS (a la VCHTN).  Various arguments can be given to
specify the route.

ARPA	use MC as a gateway to the arpanet (assumes TCP).
TCP	force the use of TCP and the ARPAnet
NCP	force the use of NCP and the ARPAnet
VIA <machine> as the chaos-arpa gateway (defaults to MC when the
	arpanet is selected.

Examples:
	DUP MC			;does the obvious
	DUP SAIL NCP		;use MC as chaos-ncp gateway to
				;get to sail
	DUP SAIL VIA ML		;use ML as chaos-TCP gateway to
				;get to sail

The program probably has bugs, which I prefer not to hear about
until I decide to really fix up the program and support it.
It is probably at least as usable as VCHTN.

DCP@MIT-MC 12/30/82 05:34:58
Changes:

MMcM;ARPA > (ARPA/TCP gateway)
	Dispatches on SNAME (contact name) in order to determine
	contact name and protocol.  It works just like the ARPA
	gateway except the contact name can also be TCP.  I
	assembled this directly into DEVICE;CHAOS TCP.  You
	should delete the bin in DEVICE; if you're paranoid.  The
	correct installation is to put the binary in MMcM's
	directory (well, the right thing to do is put it on a sys
	directory), and create links to it (the ARPA link already
	exists). 

TELSER
	No modification needed for SUPDUP.  Just create the link
	from SYN137.

SYSENG;NETWRK >
	The $$TCP switch turns on very minimal things.  It makes
	sure $$ARPA is turned on.  It requires that the variables
	USETCP and USENCP are defined.  When parsing a host name,
	/NCP will set USENCP to -1 and USETCP to 0, and /TCP will
	do the opposite.  Both switches set the network type to
	ARPA.  /ARPA leaves these variables undistrurbed.

SYSENG;SUPDUP >
	Modified to use the new NETWRK.  Actually NETWRK was
	modified to make SUPDUP work.  Oh well.  /NCP and /TCP
	should work.  Error reporting will probably get confused
	because NETWRK knows so little about TCP.  The new source
	and binary are in the installed places.  If you don't
	tell anybody, you can probably leave it this way.