Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!utcs!mnetor!lsuc!pesnta!hplabs!ucbvax!tcp-ip
From: MILLS@USC-ISID.ARPA
Newsgroups: mod.protocols.tcp-ip
Subject: Re: IP over synchronous links
Message-ID: <8601210125.AA01159@ucbvax.berkeley.edu>
Date: Sun, 19-Jan-86 16:06:56 EST
Article-I.D.: ucbvax.8601210125.AA01159
Posted: Sun Jan 19 16:06:56 1986
Date-Received: Wed, 22-Jan-86 00:26:00 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 19
Approved: tcp-ip@sri-nic.arpa

In response to the message sent  Fri 17 Jan 86 07:05:22-MST from MRC@SIMTEL20.ARPA

Mark,

I know of several ad-hoc synchronous gizmos used to pipe IP grams from one
host/gateway to another, including one suggested in RFC-892 which has been used
for several years around here. However, we have found DDCMP most popular, primarily
because DMA hardware is readily available for the PDP11 (DMV11 for the Q bus).
The U Michigan folk also have a nifty interface board for the Q bus that runs
LAPB. I suspect several other folk have done similar things.

TCP/IP is completely reasonable with most (but not all) implementations known
to me at 1200 bps. In fact, I have used these protocols over amateur AX.25
packet-radio links at 1200 bps when one packet in four died. However, some
famous TCP implementations croak dismally via such paths, especially when the
implementor has not read RFC-889.

Dave
-------