Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!VAX.FTP.COM!jbvb
From: jbvb@VAX.FTP.COM (James B. Van Bokkelen)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: SLIP reliability
Message-ID: <9006141305.AA22966@vax.ftp.com>
Date: 14 Jun 90 13:05:38 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: jbvb@vax.ftp.com
Organization: The Internet
Lines: 14

Normally I know better than to say CRC-16, but...  Sorry.

In my personal experience (which includes supporting a lot of TCP/IP
nodes), I have only had one report of undetected data corruption in
TCP (a transposition caused by a device driver bug while transferring
a very repetitive raster file).  The combination of TCP and IP on
SLIP seems fairly robust in practice: For two years our Internet link
was leased-line SLIP, and I am using dial-up SLIP to send this, and
I've never seen an error that got past the checksum.  This may be
because there is a good match between the errors asynch lines tend to
generate and those the checksum is likely to detect.

James B. VanBokkelen				FTP Software Inc.
jbvb@ftp.com					617-246-0900