Xref: utzoo comp.protocols.nfs:621 comp.protocols.tcp-ip:9651
Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!think!Think.COM!barmar
From: barmar@Think.COM
Newsgroups: comp.protocols.nfs,comp.protocols.tcp-ip
Subject: Re: Which gives best data integrity:  NFS, UUCP, or FTP?
Message-ID: <32380@news.Think.COM>
Date: 21 Dec 89 01:58:04 GMT
References: <1972@dover.sps.mot.com>
Sender: news@Think.COM
Followup-To: comp.protocols.nfs
Distribution: na
Organization: Thinking Machines Corporation, Cambridge MA
Lines: 12

FTP and NFS do no integrity checking of their own.  FTP is intended to be
used over a reliable byte-stream, normally TCP, which does perform
integrity checks (using a checksum by default).  NFS uses RPC, which
normally runs over UDP, which has an optional checksum (it's the sender's
option -- the receiver is required to check it if it's included).

Since UUCP is normally run over phone lines, which don't have high
integrity, it does its own integrity checks.
Barry Margolin, Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar