Comparison of file transfer protocols

This article lists communication protocols that are designed for file transfer over a telecommunications network.

For file sharing software, see Comparison of file sharing applications. For file synchronization software, see Comparison of file synchronization software.

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.

Protocols for packet-switched networks

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.

Overview

Color key:     International standard     Internet Standard     Proposed Standard     Internet Draft

Protocol		Original author	First published	Protocol suite	Standard	Refs
Full name	Abbreviation
BitTorrent	BT	Bram Cohen	2001	N/A	No	[1]
CCSDS File Delivery Protocol	CFDP			N/A	ISO 17355:2007 CCSDS 727.0-B-4
Cross File Transfer	CFT			N/A	No
EForward	N/A				No
Ether File Transfer Protocol	EFTP	John Shoch	1979	PARC Universal Packet	No	[2][3]
Fast and Secure Protocol	FASP	Ying Xu, Michelle Munson, Serban Simu	2007	N/A	No	[4]
File Delivery over Unidirectional Transport	FLUTE	Internet Society	2004	N/A	RFC 6726	[5]
File Service Protocol	FSP	Wen-King Su	1991	N/A	No	[6][7]
File Transfer Access and Management	FTAM				ISO 8571-4:1988
File Transfer Protocol	FTP	Abhay Bhushan	1971	Internet protocol suite	RFC 959	[8]
FTP Secure	FTPS	Internet Society	1997	Internet protocol suite	RFC 2228, 4217	[9][10]
HTTP Secure	HTTPS	Taher Elgamal et al.	1995	Internet protocol suite	RFC 7230	[11][12]
Host Unix Linkage File Transfer	HULFT	?	?	N/A	No
Hypertext Transfer Protocol	HTTP	Tim Berners-Lee et al.	1991	Internet protocol suite	RFC 7231	[13][14]
Micro Transport Protocol	µTP	Ludvig Strigeus, Greg Hazel, Stanislav Shalunov, Arvid Norberg, Bram Cohen	2007	N/A	No	[15][16]
Multicast Dissemination Protocol	MDP				No
Multicast File Transfer Protocol	MFTP	C. Kenneth Miller et al.	1995	N/A	IETF Draft (1998)	[17]
NACK-Oriented Reliable Multicast Transport Protocol	NORM				RFC 5740
Odette File Transfer Protocol	OFTP	Organisation for Data Exchange by Tele Transmission in Europe	1986	X.25	RFC 6726	[18]
Odette File Transfer Protocol 2	OFTP2	Organisation for Data Exchange by Tele Transmission in Europe	2007	X.25, Internet protocol suite	RFC 5024 (V1.3)	[19]
Reliable Blast UDP	RBUDP	Eric He et al.	2002	N/A	No	[20]
Remote copy	rcp	?	1982	Internet protocol suite	No	[21]
Secure copy	SCP	Tatu Ylönen	?	Secure Shell	No	[22]
Secure Hypertext Transfer Protocol	S-HTTP	IETF Web Transaction Security Working Group	1999	N/A	RFC 2660	[23]
Simple Asynchronous File Transfer	SAFT	Ulli Horlacher	1995	N/A	No	[24][25]
Simple File Transfer Protocol	SFTP	Mark K. Lottor	1984	N/A	RFC 913	[26]
SSH file transfer protocol	SFTP	Tatu Ylönen	c. 1997	Secure Shell	IETF Draft (2006)	[27]
T.127	T.127	?	?	N/A	ITU T.127
Trivial File Transfer Protocol	TFTP	Noel Chiappa	1980	Internet protocol suite	RFC 1350	[28]
Tsunami UDP Protocol	Tsunami	Mark Meiss et al.	2002	N/A	No	[29][30]
Tus open protocol for resumable file uploads	tus	Felix Geisendörfer, Marius Kleidl et al.	2014	N/A	No	[31][32]
UDP-based Data Transfer Protocol	UDT	Yunhong Gu	2004	N/A	No
UDP-based File Transfer Protocol	UFTP	Dennis Bush	2001	N/A	No	[33]
Unix-to-Unix Copy	UUCP	Mike Lesk	1979	N/A	No
Warp Speed Data Transfer	WDT	Laurent Demailly et al.	2015	N/A	No	[34]

Features

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.[35]

Protocol	Encryption (data)	Transfer resuming	Multicast capable	Managed	Refs
BitTorrent	None[lower-alpha 1]	Yes	Peer-to-peer	No	[36][37]
Cross File Transfer (CFT)	TLS / SSL				Yes [38][39]
EForward	Proprietary			Yes	[40]
Ether File Transfer Protocol (EFTP)	None	?	No	No	[41]
Fast and Secure Protocol (FASP)	AES-256 / AES-192 / AES-128	Yes	No		[42][43][44]
File Delivery over Unidirectional Transport (FLUTE)	Optional/Unspecified[lower-alpha 2]	No	Yes		[45][46][47]
File Service Protocol (FSP)	None	Yes	No	No	[48][49]
File Transfer Access and Management (FTAM)	?[lower-alpha 3]				[50]
File Transfer Protocol (FTP)	None	Yes[lower-alpha 4]	No	No	[51][52][53][54][55]
FTP Secure (FTPS)	TLS / SSL	Yes	No	No
HTTP Secure (HTTPS)	TLS / SSL	Yes	No	No	[14][56][57]
Host Unix Linkage File Transfer (HULFT)	AES	?	No		[58][59][60][61]
Hypertext Transfer Protocol (HTTP)	None (see HTTPS and S-HTTP)	Yes	No	No	[14][62]
Micro Transport Protocol (µTP)	None	Yes	Peer-to-peer	No	[15]
Multicast Dissemination Protocol (MDP)	None		Yes	Yes	[63][64]
Multicast File Transfer Protocol (MFTP)	None	Yes	Yes	No	[65][66]
NACK-Oriented Reliable Multicast Transport Protocol (NORM)	IPsec		Yes	Yes	[67][68]
Odette File Transfer Protocol (OFTP)	None			Yes	[69]
Odette File Transfer Protocol 2 (OFTP2)	TLS			Yes	[70]
Reliable Blast UDP (RBUDP)	None	No	No		[20][71][72]
Remote copy (rcp)	None	No	No	No	[73]
Secure copy (SCP)	Secure Shell	No	No	No
Secure Hypertext Transfer Protocol (S-HTTP)	CMS / MOSS / other	No	No	No	[74]
Simple Asynchronous File Transfer (SAFT)	PGP	?	No	No	[24][25][75]
Simple File Transfer Protocol (SFTP)	None	Yes	No	No	[76]
SSH file transfer protocol (SFTP)	Secure Shell	Yes	No	No	[77]
T.127	None	Yes	Yes	No	[78][79][80]
Trivial File Transfer Protocol (TFTP)	None	No	No	No	[81]
Tsunami UDP Protocol	None	No	No	No	[82][83]
Tus open protocol for resumable file uploads (tus)	Optional/Unspecified[lower-alpha 5]	Yes	No	No	[31][32]
UDP-based Data Transfer Protocol (UDT)	Experimental	No	No	No	[83][84][85]
UDP-based File Transfer Protocol (UFTP)	AES-256 / AES-128 / 3DES / DES[lower-alpha 6]	Yes	Yes	No	[83][33][86]
Unix-to-Unix Copy (UUCP)	None	Some[lower-alpha 7]	No	No	[87][88]
Warp Speed Data Transfer (WDT)	AES-128 (OFB / CTR)	Yes	No	No	[89][90][91]

1. Some implementations can obfuscate traffic using RC4 et al. See BitTorrent protocol encryption.
2. RFC 6726 suggests IPSec as one option.
3. One implementation, Fujitsu openFT, applies AES.
4. RFC 1123 (1989) extends and corrects the provisions for restart/resume that were published in RFC 959 (1985). RFC 3659 (2007) provides for resuming in stream mode.
5. It's recommended to use HTTPS provided by a webserver, proxy, or SSL terminator.
6. These are the options in the reference implementation, which uses OpenSSL.
7. The BNU implementation of UUCP can resume an interrupted file transfer.

Ports

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
BitTorrent		6881[lower-alpha 1]	6881	TCP	6881	6881	TCP	No	N/A	[92]
CCSDS File Delivery Protocol (CFDP)
Cross File Transfer (CFT)		1761[lower-alpha 2]		TCP / X.25					[93][94]
EForward		2181		TCP / UDP						[95]
Ether File Transfer Protocol (EFTP)		N/A	N/A	None	N/A	N/A	None	N/A	N/A
Fast and Secure Protocol (FASP)		≥33001		UDP	22		TCP	No	N/A	[92]
File Delivery over Unidirectional Transport (FLUTE)		4001		UDP				No	N/A	[92]
File Service Protocol (FSP)		Chosen by user[lower-alpha 3]		UDP				No	N/A	[92]
File Transfer Access and Management (FTAM)		4800 / 102		TCP						[96]
File Transfer Protocol (FTP)	Active mode	20	20	TCP[lower-alpha 4]	21	≥1024	TCP	Yes	Jon Postel	[92]
	Passive mode	≥1024[lower-alpha 5]	≥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	N/A	[92]
Hypertext Transfer Protocol (HTTP)		80		TCP			TCP	Yes	Tim Berners-Lee	[92]
Micro Transport Protocol (µTP)				UDP				No	N/A	[92]
Multicast Dissemination Protocol (MDP)		Chosen by user		UDP						[97][98]
Multicast File Transfer Protocol (MFTP)		5402		UDP				Yes	Steve Bannister	[92]
NACK-Oriented Reliable Multicast Transport Protocol (NORM)				UDP						[99][100]
Odette File Transfer Protocol (OFTP)		3305		TCP / X.25			TCP / X.25			[101]
Odette File Transfer Protocol 2 (OFTP2)		6619		TCP / X.25			TCP / X.25			[102]
Reliable Blast UDP (RBUDP)		Chosen by user		UDP				No	N/A	[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	N/A	[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	N/A	[92]
Tus open protocol for resumable file uploads (tus)		80[lower-alpha 6]		TCP			TCP	No	N/A	[92]
UDP-based Data Transfer Protocol (UDT)		Chosen by server		UDP				No	N/A	[92]
UDP-based File Transfer Protocol (UFTP)		1044		UDP				No	N/A	[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	N/A	[92]

1. Typically, if port 6881 is unavailable as a listening port, the peer incrementally tries 6882–6889. Another port may be specified in software.
2. 1761 is the default port, but 1761–1768 are allocated by IANA.
3. UDP port 21 is sometimes chosen for FSP.
4. FTP was originally designed for NCP, a protocol used on ARPANET before the advent of TCP. The TCP implementation of FTP was standardized in RFC 959.
5. The server listens on TCP port 21 (the control port), and the client sends commands to this port from a random port above 1023. To transfer data in active mode, the server initiates a connection from port 20 to the client at the randomly selected port number.
   In passive mode, the client uses a random port above 1023 as a control port, and from this initiates file transfer. The server sends or receives data from a randomly selected port above 1023, and the client sends or receives data from one port number above its own randomly selected control port.
6. Can be chosen by user, but layers on top of HTTP(S) so often 80/443

Serial protocols

A 9-pin to 25-pin RS-232 adapter cable

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.

Overview

Protocol	Author	First released	License	Description	Refs
BiModem	Erik Labs	1989		Bi-directional transfers.
BLAST	Communications Research Group	?		Powerful protocol originating on minicomputers for telemetry purposes. Later found use on micros.	[103]
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.	[104]
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.	[105]
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.	[106][107][108]
SMODEM	Arisoft	?
Tmodem	Mike Bryeans	?
UUCP	Mike Lesk	1979		Suite of protocols for copying files between Unix machines, used for many purposes including the distriubtion 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.	[109]
MODEM7	Mark M. Zeigler, James K. Mills	1980		Slight extension of XMODEM to add filename support and batch transfers.	[110]
XMODEM	Ward Christensen	1977	Public domain	Very simple protocol that saw widespread use and provided the pattern for many following protocols.	[111]
WXMODEM	Peter Boswell	1986	Public domain	Version of XMODEM with sliding windows for higher performance.	[112][113]
YMODEM	Chuck Forsberg	1985	Public domain	Series of optional expansions on XMODEM for higher performance.	[112]
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.	[112]

Features

Protocol	Data block size (bytes)	Data compression	Error detection	Transfer resuming	Bidirectional	Sliding window	Refs
BiModem					Yes
BLAST			CRC		Yes	Yes
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)	[114]
LeechModem
Lynx		RLE	CRC32	Yes
NMODEM	2048
OBject EXchange
Punter
SEAlink				Yes		Yes
SMODEM					Yes
Tmodem				No
UUCP "g"	≤4096	No		No			[115][116]
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

See also

• Comparison of file sharing applications
• Comparison of file synchronization software
• Comparison of distributed file systems
• Lists of network protocols
• List of TCP and UDP port numbers
• List of backup software
• AS2
• Connect:Direct
• Files transferred over shell protocol (FISH)
• Pragmatic General Multicast
• Sendfile
• Waarp

Notes

1. Cohen, Bram (2 July 2001). "The BitTorrent Protocol Specification". Yahoo! Finance Groups. Archived from the original on 16 December 2008. Retrieved 23 February 2018.
2. Shoch, John (1979). EFTP: A PUP-based Ether File Transfer Protocol.
3. Snodgrass, Richard (December 1982). A Relational Approach to Monitoring Complex Systems. pp. 119, 149. Retrieved 3 March 2018.
4. United States patent 20090063698, Ying Xu, Michelle Christine Munson, Serban Simu, "Method and system for aggregate bandwith control [sic]", issued 30 May 2017, assigned to Aspera, Inc. and IBM
5. Paila, Toni; Luby, Michael; Lehtonen, Rami; Roca, Vincent; Walsh, Rod (October 2004). FLUTE - File Delivery over Unidirectional Transport. IETF. doi:10.17487/RFC3926. RFC 3926. Retrieved 7 March 2018.
6. Petersen, Julie K., ed. (2002). "File Service Protocol". The Telecommunications Illustrated Dictionary (2nd ed.). CRC Press. p. 357. ISBN 978-1-4200-4067-8 – via Google Books.
7. "File Service Protocol (FSP) Frequently Asked Questions [Part 2/2]". FAQs.org. 21 July 1995. Section: "Who writes and maintains FSP software?". Retrieved 3 March 2018.
8. Bhushan, Abhay (April 1971). A File Transfer Protocol. IETF. doi:10.17487/RFC0114. RFC 114. Retrieved 24 February 2018.
9. Horowitz, M.; Lunt, S. (October 1997). FTP Security Extensions. IETF. doi:10.17487/RFC2228. RFC 2228. Retrieved 3 March 2018.
10. Ford-Hutchinson, Paul (October 2005). Securing FTP with TLS. IETF. doi:10.17487/RFC4217. RFC 4217. Retrieved 3 March 2018.
11. Sliwa, Carol (31 May 1999). "Secure Sockets Layer". Computerworld. p. 69. Retrieved 1 March 2018 – via Google Books.
12. Hickman, Kipp E. B. (April 1995). The SSL Protocol. IETF. I-D draft-hickman-netscape-ssl-00. Retrieved 1 March 2018.
13. Berners-Lee, Tim. "The Original HTTP as defined in 1991". W3.org. Retrieved 3 March 2018.
14. Iwaya, Akemi (10 November 2015). "Why was 80 Chosen as the Default HTTP Port and 443 as the Default HTTPS Port?". How-To Geek. Retrieved 3 March 2018.
15. Norberg, Arvid (22 June 2009). "uTorrent transport protocol". BitTorrent.org. Retrieved 10 March 2018.
16. Klinker, Eric (16 May 2010). "Eric Klinker Presentation at Emerging Communication Conference & Awards 2010 America § Status of uTP". eCommConf. Retrieved 10 March 2018.
17. United States patent 7710961, C. Kenneth Miller, Thomas Andresen, Thomas Gardner, Craig Michelson, Kenneth Cates, Marc White, Kary Robertson, "System and method for sending packets over a computer network", issued 20 December 2011, assigned to Darby and Mohaine LLC
18. Nash, David (September 1997). ODETTE File Transfer Protocol. IETF. doi:10.17487/RFC2204. RFC 2204. Retrieved 22 February 2018.
19. Friend, Ieuan (November 2007). ODETTE File Transfer Protocol 2. IETF. doi:10.17487/RFC5024. RFC 5024. Retrieved 22 February 2018.
20. He, Eric; Leigh, Jason; Yu, Oliver; DeFanti, Thomas A. (September 2002). "Reliable Blast UDP: Predictable High Performance Bulk Data Transfer" (PDF). Proceedings: IEEE International Conference on Cluster Computing, ICCC (January 2002). IEEE Cluster Computing 2002. Chicago. pp. 317–24. ISSN 1552-5244. OCLC 5942572037. Retrieved 2 March 2018.
21. McKusick, Marshall Kirk (1999). "Twenty Years of Berkeley Unix: From AT&T-Owned to Freely Redistributable". Open Sources: Voices from the Open Source Revolution. O'Reilly & Associates. Section: "4.2BSD". ISBN 978-1-56592-582-3.
22. Ylonen, Tatu (31 August 2017). "SSH: Secure Shell § History of the SSH Protocol". SSH.com. Retrieved 3 March 2018.
23. Rescorla, Eric; Schiffman, Allan M. (August 1999). The Secure HyperText Transfer Protocol. IETF. doi:10.17487/RFC2660. RFC 2660. Retrieved 9 March 2018.
24. Horlacher, Ulli. "SAFT / sendfile". fex.belwue.de. Retrieved 3 March 2018.
25. Horlacher, Ulli. "sendfile(1)". manpages.org. Retrieved 3 March 2018.
26. Lottor (1984), pp. 1, 13
27. Ylönen, Tatu (30 September 2012). "Re: where are SFTP v0 - 2 defined?". secsh (Mailing list). Retrieved 9 March 2018. I designed and implemented the original SFTP protocol for SSH 2.0 back around 1997. Sami Lehtinen did further development on it.
    It was originally a proprietary protocol at SSH Communications Security (www.ssh.com), though source code was publicly available. It took a while [sic] before we wrote the draft and brought it to the IETF for standardization (seems to have been January 2001).
28. Sollins, Karen R. (January 1980). The TFTP Protocol. IETF. IEN 133. Retrieved 24 February 2018.
29. Wagner, Jan. "Tsunami UDP Protocol". tsunami-udp.sourceforge.net. Jon Wagner – via SourceForge.
30. "Research". anml.iu.edu. Pervasive Technology Labs at Indiana University. Section: "Tsunami". Archived from the original on 29 July 2010.
31. protocol.md on GitHub
32. "tus - resumable file uploads".
33. Bush, Dennis. "Changes". uftp-multicast.sourceforge.net. Dennis Bush. Retrieved 9 March 2018 – via SourceForge.
34. "wdt: Releases". GitHub. Retrieved 23 February 2018.
35. Villanueva, John Carl (17 February 2015). "Managed File Transfer and Network Solutions". JSCAPE.com. JSCAPE.
36. Cohen, Bram (4 February 2017) [2008]. "The BitTorrent Protocol Specification". BitTorrent.org. Section: "Trackers". Retrieved 22 February 2018.
37. "Message Stream Encryption". Vuze Wiki. Azureus Software. 1 December 2007 [2006]. Retrieved 10 March 2018.
38. "Transfer CFT 3.2.4 Users Guide § Configuring Transfer CFT". Axway.com. Axway Software. Archived from the original on 19 February 2018. Retrieved 18 February 2018.
39. "Transfer CFT 3.2.2 Local Administration Guide § Transport Security". Axway.com. Axway Software. Retrieved 22 February 2018.
40. Sosinsky, Barrie (15 September 2009). "TCP - UDP Port Assignments". Networking Bible. Wiley Publishing. p. 851. ISBN 978-0-470-43131-3. OCLC 471462746 – via Google Books.
41. "Printing at PARC—Appendix: Glossary of Terms § EFTP". 4 August 1978. Retrieved 3 March 2018. A simple, PUP-oriented protocol, designed for file transmission from user programs to servers (especially printing servers). The server must acknowledge each packet before the next is sent. This protocol admits to compact implementation in user programs, offset by some redunction in bandwidth.
42. Pott, Trevor (1 October 2015). "Aspera high speed file transfer: Let the cloud protocol wars begin". The Register. Retrieved 18 February 2018.
43. "FASP Security Model". AsperaSoft.com. Aspera. 2017. Retrieved 18 February 2018.
44. Campos, Andrea (2 June 2016). "Resuming file transfers with ascp". AsperaSoft.com. Aspera. Retrieved 2 March 2018.
45. Paila, Toni; Walsh, Rod; Luby, Michael; Roca, Vincent; Lehtonen, Rami (November 2012). FLUTE - File Delivery over Unidirectional Transport. IETF. doi:10.17487/RFC3926. RFC 3926. Retrieved 7 March 2018.
46. Peltotalo, Jani; Peltotalo, Sami; Harju, Jarmo. "Analysis of the FLUTE Data Carousel" (PDF). mad.cs.tut.fi. Tampere University of Technology. p. 1. Retrieved 9 March 2018.
47. Peltotalo, Jani; Peltotalo, Sami; Harju, Jarmo; Walsh, Rod (June 2007) [2006]. "Performance analysis of a file delivery system based on the FLUTE protocol". International Journal of Communication Systems. 20 (6): 633. doi:10.1002/dac.835.
48. "File Service Protocol (FSP) Frequently Asked Questions v1.1". FAQs.org. 19 August 1996. Retrieved 18 February 2018.
49. "Common Ports". Red Hat Enterprise Linux 4: Security Guide. Red Hat. 2005. Retrieved 2 March 2018.
50. "openFT v11.0: Setting Up a Connection to Customs (Atlas) with openFT FTAM" (PDF). Fujitsu. 2010. p. 2. Retrieved 18 February 2018.
51. Postel, Jon; Reynolds, Joyce (October 1985). File Transfer Protocol (FTP). IETF. doi:10.17487/RFC0959. RFC 959. Retrieved 22 February 2018.
52. Kozierok, Charles M. (20 September 2005). "FTP Overview, History and Standards". The TCP/IP Guide (v3.0 ed.). Retrieved 21 February 2018.
53. Bhushan, Abhay (April 1971). A File Transfer Protocol. IETF. doi:10.17487/RFC0114. RFC 114. Retrieved 22 February 2018.
54. Braden, Robert (October 1989). "FTP Restart Mechanism". Requirements for Internet Hosts—Application and Support. IETF. pp. 36–7. sec. 4.1.3.4. doi:10.17487/RFC1123. RFC 1123. Retrieved 13 March 2018.
55. Hethmon, Paul (March 2007). "Restarting in STREAM Mode". Extensions to FTP. IETF. sec. 5.1. doi:10.17487/RFC3659. RFC 3659. Retrieved 13 March 2018.
56. Rescorla, Eric (May 2000). HTTP Over TLS. IETF. doi:10.17487/RFC2818. RFC 2818. Retrieved 20 February 2018.
57. Reynolds, Joyce; Postel, Jon (October 1994). Assigned Numbers. IETF. p. 34. doi:10.17487/RFC1700. RFC 1700. Retrieved 3 March 2018.
58. "The Incredible HULFT – My Favorite B2B Network Protocol". OpenText Blogs. OpenText. 27 August 2009. Retrieved 18 February 2018.
59. "9.4.1. HULFT § Overview". Enterprise Cloud Knowledge Center. NTT Communications. Retrieved 2 March 2018.
60. "9.4.1. HULFT § HULFT 8 Cipher Option". Enterprise Cloud Knowledge Center. NTT Communications. Retrieved 18 February 2018.
61. "導入サービス". HULFT.com (in Japanese). Saison Information Systems. Section: "前提事項、その他". Retrieved 21 February 2018.
62. Reynolds, Joyce; Postel, Jon (July 1992). Assigned Numbers. IETF. p. 12. doi:10.17487/RFC1340. RFC 1340. Retrieved 3 March 2018.
63. Adamson, Brian; Macker, Joe. "Multicast Dissemination Protocol (MDP) Developer's Guide". nrl.navy.mil. United States Naval Research Laboratory. Retrieved 22 February 2018.
64. "Multicast Dissemination Protocol History". nrl.navy.mil. United States Naval Research Laboratory. Retrieved 22 February 2018.
65. Miller, Kenneth; Robertson, Kary; Tweedly, Alex; White, Marc (April 1998). "IANA Assigned UDP Port". StarBurst Multicast File Transfer Protocol (MFTP) Specification. IETF. p. 10. I-D miller-mftp-spec-03. Retrieved 18 February 2018.
66. "StarBurst MFTP™ Compared to Today's File Transfer Protocols: A White Paper". StarBurst Communications. 1996 – via University of California, Irvine.
67. "NACK-Oriented Reliable Multicast (NORM)". nrl.navy.mil. United States Naval Research Laboratory. Retrieved 22 February 2018.
68. Adamson, Brian; Bormann, Carsten; Handley, Mark; Macker, Joe (November 2009). NACK-Oriented Reliable Multicast (NORM) Transport Protocol. IETF. doi:10.17487/RFC5740. RFC 5740. Retrieved 22 February 2018.
69. Nash, David (September 1997). ODETTE File Transfer Protocol. IETF. doi:10.17487/RFC2204. RFC 2204. Retrieved 22 February 2018.
70. Friend, Ieuan (November 2007). ODETTE File Transfer Protocol 2. IETF. doi:10.17487/RFC5024. RFC 5024. Retrieved 22 February 2018.
71. Li, Jie; Veeraraghavan, Malathi (2012). A Reliable Message Multicast Transport Protocol for Virtual Circuits (PDF). 4th International Conference on Communications, Mobility, and Computing (CMC 2012). p. 120. Retrieved 2 March 2018.
72. RBUDP on GitHub
73. "Rlogin, RSH, and RCP". SourceDaddy. Retrieved 18 February 2018.
74. Rescorla, Eric; Schiffman, Allan M. (August 1999). The Secure HyperText Transfer Protocol. IETF. doi:10.17487/RFC2660. RFC 2660. Retrieved 20 February 2018.
75. "Service Name and Transport Protocol Port Number Registry". IANA.org. Internet Assigned Numbers Authority. 21 February 2018. Retrieved 22 February 2018.
76. Lottor (1984), p. 10
77. Ylonen, Tatu (10 October 2017). "SFTP - SSH Secure File Transfer Protocol § SFTP Port Number". SSH.com. Retrieved 3 March 2018.
78. "ITU-T Rec. T.127 (08/2007) Multipoint binary file transfer protocol". International Telecommunication Union. 2008. p. 4.
79. "A Primer on the T.120 Series" (PDF). DataBeam Corporation. 1997 [1995]. pp. 2, 4. Retrieved 2 March 2018.
80. "T.120: Multipoint Data Conferencing and Real Time Communication Protocols". Network Protocols Handbook (2 ed.). Javvin Technologies. p. 137.
81. Sollins, Karen R. (July 1992). The TFTP Protocol (Revision 2). IETF. doi:10.17487/RFC1350. RFC 1350. Retrieved 22 February 2018.
82. "Tsunami UDP Protocol – Installation, Setup and Limitations". BluePiIT.com. BluePi Consulting. 13 October 2015. Retrieved 20 February 2018.
83. Tkaczewski, John (18 June 2012). "Open Source Fast File Transfers". FileCatalyst.com. FileCatalyst. Retrieved 24 February 2018.
84. Valeros Bernardo, Danilo; Hoang, Doan B. (2010). "End-to-End Security Methods for UDT Data Transmissions". Future Generation Information Technology. International Conference on Future Generation Information Technology. p. 383. doi:10.1007/978-3-642-17569-5_38. ISBN 978-3-642-17569-5.
85. Valeros Bernardo, Danilo (2012). Network Security Mechanisms and Implementations for the Next Generation Reliable Fast Data Transfer Protocol—UDT (PDF) (Ph.D. thesis). University of Technology Sydney. pp. 22, 91–102. OCLC 830759422. Retrieved 21 February 2018.
86. "Encrypted UDP based FTP with multicast (UFTP)". Wireshark Wiki. 7 August 2016. Retrieved 21 February 2018.
87. Reifschneider, Sean (8 January 2004). "Mobile Email with UUCP". ONLamp. O'Reilly Media. Retrieved 20 February 2018.
88. Ravin, Ed (1996). Using & Managing UUCP (2nd ed.). O'Reilly & Associates. p. 70. ISBN 978-1-56592-153-5.
89. WDT RocksDB Dec 16 2016. Laurent Demailly. 23 December 2016. Retrieved 23 February 2018 – via YouTube.
90. Demailly, Laurent (17 October 2015). "Getting Started with the WDT command line". GitHub. Retrieved 1 March 2018.
91. wdt on GitHub
92. "Service Name and Transport Protocol Port Number Registry". IANA.org. Internet Assigned Numbers Authority. 28 February 2018. Retrieved 17 March 2018.
93. "Transfer CFT 3.2.4 Users Guide § Configuring Transfer CFT". Axway.com. Axway Software. Archived from the original on 19 February 2018. Retrieved 18 February 2018.
94. "Transfer CFT 3.2.2 Local Administration Guide § Transport Security". Axway.com. Axway Software. Retrieved 22 February 2018.
95. Sosinsky, Barrie (15 September 2009). "TCP - UDP Port Assignments". Networking Bible. Wiley Publishing. p. 851. ISBN 978-0-470-43131-3. OCLC 471462746 – via Google Books.
96. "openFT v11.0: Setting Up a Connection to Customs (Atlas) with openFT FTAM" (PDF). Fujitsu. 2010. p. 2. Retrieved 18 February 2018.
97. Adamson, Brian; Macker, Joe. "Multicast Dissemination Protocol (MDP) Developer's Guide". nrl.navy.mil. United States Naval Research Laboratory. Retrieved 22 February 2018.
98. "Multicast Dissemination Protocol History". nrl.navy.mil. United States Naval Research Laboratory. Retrieved 22 February 2018.
99. "NACK-Oriented Reliable Multicast (NORM)". nrl.navy.mil. United States Naval Research Laboratory. Retrieved 22 February 2018.
100. Adamson, Brian; Bormann, Carsten; Handley, Mark; Macker, Joe (November 2009). NACK-Oriented Reliable Multicast (NORM) Transport Protocol. IETF. doi:10.17487/RFC5740. RFC 5740. Retrieved 22 February 2018.
101. Nash, David (September 1997). ODETTE File Transfer Protocol. IETF. doi:10.17487/RFC2204. RFC 2204. Retrieved 22 February 2018.
102. Friend, Ieuan (November 2007). ODETTE File Transfer Protocol 2. IETF. doi:10.17487/RFC5024. RFC 5024. Retrieved 22 February 2018.
103. Magidson, Steve (15 May 1989). "Moving Files Can Be a BLAST" (PDF). UNIX Today!. CMP Media. Retrieved 18 February 2018.
104. da Cruz (1987) p. 3
105. "OBEX (Object Exchange) Protocol". irdajp.org. Infrared Data Association. 2011. Archived from the original on 21 February 2018. Retrieved 20 February 2018.
106. sealink.c on GitHub
107. Held, Gilbert (1993). "SeaLink". Mastering PC Communications Software. Van Nostrand Reinhold. p. 74.
108. Woggon, Michele (1995). "SeaLink". Telecommunications Using ProComm & ProComm Plus Made Easy. Prentice Hall. p. 34.
109. "UUCP protocol internals". University of Utah.
110. Lucas, Jay (6 September 1982). "Freeware: Modem lets your computers communicate". InfoWorld. IDG. p. 53. Retrieved 18 February 2018.
111. Glass (1988) p. 87
112. Glass (1988) p. 89
113. Boswell, Peter (2007) [1986]. How XModem, XModem CRC, and WXModem work. Archived from the original on 23 September 2014 – via Totse.com.
114. da Cruz (1987) pp. 234, 253, 307
115. Wells, Nicholas (2003). "Using UUCP for Remote Access". Guide to Linux Installation and Administration. Course Technology. p. 140. ISBN 978-0-619-00094-3 – via Google Books.
116. Taylor, Ian Lance. "UUCP 'g' Protocol". FreeBSD Documentation Server. The FreeBSD Project. Retrieved 8 March 2018.

References

• da Cruz, Frank (1987). Kermit: A File Transfer Protocol. Bedford: Digital Press. ISBN 978-0-932376-88-6. OCLC 751527576 – via Google Books.
• da Cruz, Frank (June 1986). "Kermit Protocol Manual" (PDF). KermitProject.org. The Kermit Project.
• Glass, Brett (30 May 1988). "Xmodem Popular for Its Simplicity, Public Domain Status". InfoWorld – via Google Books.
• Lottor, Mark K. (September 1984). Simple File Transfer Protocol. IETF. doi:10.17487/RFC0913. RFC 913. Retrieved 1 March 2018.

Further reading

• de Goyeneche, Juan-Mariano (20 March 1998). "Multicast Transport Protocols". Multicast over TCP/IP HOWTO – via The Linux Documentation Project.
• He, Eric; Kettimuthu, Rajkumar; Gu, Yunhong; et al., "Reliable UDP Variants" (PDF), Survey of Protocols and Mechanisms for Enhanced Transport over LONG FAT PIPES, pp. 6–11
• Kaplan, Ali (2009). "Literature Survey". Collaborative Framework for High-Performance P2P-based Data Transfer in Scientific Computing (DOCX) (Ph.D. thesis). Indiana University Bloomington. pp. 12–39. ISBN 978-1-109-50327-2. OCLC 648765323.
• Kientzle, Tim (1995). The Working Programmer's Guide to Serial Protocols. Coriolis Group Books. ISBN 978-1-883577-20-9. OCLC 441637109.
• "About Kermit". KermitProject.org. The Kermit Project.
• "The Kermit Software Archive". KermitProject.org. The Kermit Project.