Editing UUCP (section)

===Other protocols===
UUCP implementations also include other transfer protocols for use over certain links.

'''f-protocol''' is designed to run over 7-bit error-corrected links. This was originally intended for use on [[X.25]] links, which were popular for a time in the 1980s. It does not packetize data, instead, the entire file is sent as a single long string followed by a whole-file checksum. The similar '''x-protocol''' appears to have seen little or no use. '''d-protocol''' was similar to x, but intended for use on [[Datakit]] networks that connected many of [[Bell Labs]] offices.<ref name=faq/>

'''t-protocol''' originated in the BSD versions of UUCP and like some similar ones, is designed to run over 8-bit error-free [[TCP/IP]] links. It has no error correction at all, and the protocol consists simply of breaking up command and file data into 512 or 1024-byte packets to easily fit within typical TCP frames.

'''e-protocol''' ("e" for Ethernet) was developed by Clem Cole at [[MASSCOMP]] and was widely released by Brian Redman in the later HoneyDanBer versions.  It was developed and released before the t-protocol, but the t-protocol was more commonly used because the BSD version of UUCP was the dominant implementation. The e-protocol differs from the t-protocol only in that commands are not packetized and are instead sent as normal strings, while files are padded to the nearest 20 bytes.<ref name=faq/><ref name=masscomp-uucpmgmt>{{Cite book | title=UUCP Management Guide, Rev C |first=Stephen |last=Talbot |date=February 1988  |series=User Manuals |number=M-UUCP-MG |publisher=Massachusetts Computer Corporation }}</ref>