Loading AI tools
From Wikipedia, the free encyclopedia
This article lists communication protocols that are designed for file transfer over a telecommunications network.
Protocols for shared file systems—such as 9P and the Network File System—are beyond the scope of this article, as are file synchronization protocols.
A packet-switched network transmits data that is divided into units called packets. A packet comprises a header (which describes the packet) and a payload (the data). The Internet is a packet-switched network, and most of the protocols in this list are designed for its protocol stack, the IP protocol suite.
They use one of two transport layer protocols: the Transmission Control Protocol (TCP) or the User Datagram Protocol (UDP). In the tables below, the "Transport" column indicates which protocol(s) the transfer protocol uses at the transport layer. Some protocols designed to transmit data over UDP also use a TCP port for oversight.
The "Server port" column indicates the port from which the server transmits data. In the case of FTP, this port differs from the listening port. Some protocols—including FTP, FTP Secure, FASP, and Tsunami—listen on a "control port" or "command port", at which they receive commands from the client.
Similarly, the encryption scheme indicated in the "Encryption" column applies to transmitted data only, and not to the authentication system.
The "Managed" column indicates whether the protocol is designed for managed file transfer (MFT). MFT protocols prioritise secure transmission in industrial applications that require such features as auditable transaction records, monitoring, and end-to-end data security. Such protocols may be preferred for electronic data interchange.[38]
In the table below, the data port is the network port or range of ports through which the protocol transmits file data. The control port is the port used for the dialogue of commands and status updates between client and server.
The column "Assigned by IANA" indicates whether the port is listed in the Service Name and Transport Protocol Port Number Registry, which is curated by the Internet Assigned Numbers Authority (IANA). IANA devotes each port number in the registry to a specific service with a specific transport protocol. The table below lists the transport protocol in the "Transport" column.
Protocol | Data port | Control port | Assigned by IANA | Assignee | Refs | |||||
---|---|---|---|---|---|---|---|---|---|---|
Server | Client | Transport | Server | Client | Transport | |||||
BITS | 80/443[lower-alpha 1] / 137-139[lower-alpha 2] | TCP / UDP | No | — | ||||||
BitTorrent | 6881[lower-alpha 3] | 6881 | TCP | 6881 | 6881 | TCP | No | — | [92] | |
CCSDS File Delivery Protocol (CFDP) | ||||||||||
Cross File Transfer (CFT) | 1761[lower-alpha 4] | TCP / X.25 | [41][42] | |||||||
Ether File Transfer Protocol (EFTP) | — | — | None | — | — | None | — | — | ||
Fast and Secure Protocol (FASP) | ≥33001 | UDP | 22 | TCP | No | — | [92] | |||
File Delivery over Unidirectional Transport (FLUTE) | 4001 | UDP | No | — | [92] | |||||
File Service Protocol (FSP) | Chosen by user[lower-alpha 5] | UDP | No | — | [92] | |||||
File Transfer Access and Management (FTAM) | 4800 / 102 | TCP | [93] | |||||||
File Transfer Protocol (FTP) | Active mode | 20 | 20 | TCP[lower-alpha 6] | 21 | ≥1024 | TCP | Yes | Jon Postel | [92] |
Passive mode | ≥1024[lower-alpha 7] | ≥1024 | ||||||||
FTP Secure (FTPS) | 989 | TCP | 990 | TCP | Yes | Christopher Allen | [92] | |||
HTTP Secure (HTTPS) | 443 | TCP | TCP | Yes | IESG | [92] | ||||
Host Unix Linkage File Transfer (HULFT) | 30000 | TCP | TCP | No | — | [92] | ||||
Hypertext Transfer Protocol (HTTP) | 80 | TCP | TCP | Yes | Tim Berners-Lee | [92] | ||||
Micro Transport Protocol (μTP) | UDP | No | — | [92] | ||||||
Multicast Dissemination Protocol (MDP) | Chosen by user | UDP | [94][66] | |||||||
Multicast File Transfer Protocol (MFTP) | 5402 | UDP | Yes | Steve Bannister | [92] | |||||
NACK-Oriented Reliable Multicast Transport Protocol (NORM) | UDP | [69][70] | ||||||||
Odette File Transfer Protocol (OFTP) | 3305 | TCP / X.25 | TCP / X.25 | [19] | ||||||
Odette File Transfer Protocol 2 (OFTP2) | 6619 | TCP / X.25 | TCP / X.25 | [20] | ||||||
Reliable Blast UDP (RBUDP) | Chosen by user | UDP | No | — | [92] | |||||
Remote copy (rcp) | 514 | TCP | TCP | Yes | [92] | |||||
Secure copy (SCP) | 22 | TCP | TCP | Yes | [92] | |||||
Secure Hypertext Transfer Protocol (S-HTTP) | 80 | TCP | TCP | No | — | [92] | ||||
Simple Asynchronous File Transfer (SAFT) | 487 | TCP | Yes | Ulli Horlacher | [92] | |||||
Simple File Transfer Protocol (SFTP) | 115 | TCP | TCP | Yes | Mark Lottor | [92] | ||||
SSH file transfer protocol (SFTP) | 22 | TCP | TCP | Yes | [92] | |||||
T.127 | 1503 | TCP | TCP | Yes | Jim Johnston | [92] | ||||
Trivial File Transfer Protocol (TFTP) | 69 | UDP | Yes | David Clark | [92] | |||||
Tsunami UDP Protocol | Chosen by user | UDP | TCP | No | — | [92] | ||||
Tus open protocol for resumable file uploads (tus) | 80[lower-alpha 8] | TCP | TCP | No | — | [92] | ||||
UDP-based Data Transfer Protocol (UDT) | Chosen by server | UDP | No | — | [92] | |||||
UDP-based File Transfer Protocol (UFTP) | 1044 | UDP | No | — | [92] | |||||
Unix-to-Unix Copy (UUCP) | 540 | TCP | TCP | Yes | [92] | |||||
Warp Speed Data Transfer (WDT) | Chosen by server or by user | TCP | TCP | No | — | [92] |
The following protocols were designed for serial communication, mostly for the RS-232 standard. They are used for uploading and downloading computer files via modem or serial cable (e.g., by null modem or direct cable connection). UUCP is one protocol that can operate with either RS-232 or the Transmission Control Protocol as its transport. The Kermit protocol can operate over any computer-to-computer transport: direct serial, modem, or network (notably TCP/IP, including on connections secured by SSL, SSH, or Kerberos). OBject EXchange is a protocol for binary object wireless transfer via the Bluetooth standard. Bluetooth was conceived as a wireless replacement for RS-232.
Protocol | Author | First released | License | Description | Refs |
---|---|---|---|---|---|
BiModem | Erik Labs | 1989 | Bi-directional transfers. | ||
BLAST | Communications Research Group | 1981 | Powerful protocol originating on the Data General Nova minicomputer, and then ported to micros and mainframes. | [95] | |
C-MODEM | Lavio Pareschi | 1989 | Packet lengths from 32 to 4096 bytes, optional (but normally used) streaming mode. | ||
B protocol | CompuServe | 1981 | Offered file transfer as well as a command stream. | ||
JMODEM | Richard B. Johnson | ? | XMODEM derivative with blocks from 512 to 8192 bytes and RLE compression. | ||
HS/Link | Samuel H. Smith | 1991 | |||
Kermit | Frank da Cruz et al. | 1981 | Open Source (BSD) as of 2011 | Transport- and platform-independent transfer of text and binary files across full- or half-duplex connections with conversion of text file formats and character sets. | [96] |
LeechModem | Sam Brown | ? | Variations of X and Y that faked failed downloads in order to avoid BBS download quotas. | ||
Lynx | Matthew Thomas | 1989 | Similar to Kermit: 64-byte packets, 2 to 16 packets per window, CRC-32. Little or no support outside the Lynx program itself. | ||
NMODEM | L. B. Neal | 1990 | Essentially XMODEM-CRC with 2048 byte blocks. | ||
OBEX File Transfer Protocol | ? | ? | A synchronous file transfer protocol in the OBject EXchange (OBEX) Bluetooth profile. | ||
OBEX Push | ? | ? | An asynchronous file transfer protocol in the OBject EXchange (OBEX) Bluetooth profile. | [97] | |
Punter | Steve Punter | ? | Suite of similar-but-different XMODEM-like protocols for various Commodore machines. | ||
SEAlink | Thom Henderson | 1986 | A MODEM7/XMODEM-compatible protocol with sliding window support developed to avoid propagation delays in satellite transmissions and packet networks. | [98][99][100] | |
SMODEM | Arisoft | ? | |||
TMODEM | Mike Bryeans | ? | |||
UUCP | Mike Lesk | 1979 | Suite of protocols for copying files between Unix machines, used for many purposes including the distribution of email. Also allows commands to be sent, which led to the first internet worms. The file transfer protocol within UUCP is the "g" protocol. | [101] | |
MODEM7 | Mark M. Zeigler, James K. Mills | 1980 | Slight extension of XMODEM to add filename support and batch transfers. | [102] | |
XMODEM | Ward Christensen | 1977 | Public domain | Very simple protocol that saw widespread use and provided the pattern for many following protocols. | [103] |
WXMODEM | Peter Boswell | 1986 | Public domain | Version of XMODEM with sliding windows for higher performance. | [104][105] |
YMODEM | Chuck Forsberg | 1985 | Public domain | Series of optional expansions on XMODEM for higher performance. | [104] |
ZMax | Mike Bryeans | c. 1991 | Modifications to ZMODEM to allow packets up to 32 kB in length. | ||
ZMODEM | Chuck Forsberg | 1986 | Public domain | Streaming protocol that forsakes XMODEM compatibility but offers a wide variety of new features and improved performance. Became almost universal on BBS systems in the early 1990s. | [104] |
Protocol | Data block size (bytes) | Data compression | Error detection | Transfer resuming | Bidirectional | Sliding window | Refs |
---|---|---|---|---|---|---|---|
BiModem | Yes | ||||||
BLAST | 84 - 1024+ | RLE | CRC | Yes | Yes | Yes | [106] |
C-MODEM | 32–4096 | CRC | Yes | ||||
B protocol | 128–2048 | CRC32 / CRC16 / 8-bit checksum | Yes | Yes | |||
JMODEM | 64–8192 | RLE | |||||
HS/Link | CRC32 | Yes | Yes | ||||
Kermit | ≤9024 (negotiated) | RLE (run length encoding, negotiated) | Checksum or CRC16 (negotiated) | Yes (binary files only, negotiated) | No | Over full-duplex only (negotiated) | [107] |
LeechModem | |||||||
Lynx | RLE | CRC32 | Yes | ||||
NMODEM | 2048 | ||||||
OBject EXchange | |||||||
Punter | |||||||
SEAlink | Yes | Yes | |||||
SMODEM | Yes | ||||||
Tmodem | No | ||||||
UUCP "g" | ≤4096 | No | No | [108][109] | |||
MODEM7 | 128 | No | Checksum | Stop-and-wait ARQ | |||
XMODEM | 128 | No | Checksum | Stop-and-wait ARQ | |||
WXMODEM | ≤512 | Yes | |||||
YMODEM | 1024 | No | CRC16 | ||||
ZMax | ≤~32,768 | CRC32 | |||||
ZMODEM | 256 / 1024 | No | CRC32 | Yes | Yes |
Seamless Wikipedia browsing. On steroids.
Every time you click a link to Wikipedia, Wiktionary or Wikiquote in your browser's search results, it will show the modern Wikiwand interface.
Wikiwand extension is a five stars, simple, with minimum permission required to keep your browsing private, safe and transparent.