Comparison of file transfer protocols

Last updated

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

Contents

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
ProtocolOriginal authorFirst publishedProtocol suiteStandardRefs
Full nameAbbreviation
Background Intelligent Transfer Service BITS Microsoft 2001—No [1]
BitTorrent BT Bram Cohen 2001—No [2]
CCSDS File Delivery Protocol CFDP 2002— ISO 17355:2007 (v4)
CCSDS 727.0-B-5
Cross File Transfer CFT —No
Ether File Transfer Protocol EFTP John Shoch 1979 PARC Universal Packet No [3] [4]
Fast and Secure Protocol FASP Ying Xu, Michelle Munson, Serban Simu2007—No [5]
File Delivery over Unidirectional Transport FLUTE Internet Society 2004— RFC 6726 [6]
File Service Protocol FSP Wen-King Su1991—No [7] [8]
File Transfer Access and Management FTAM 1988 ISO 8571-4:1988
File Transfer Protocol FTP Abhay Bhushan 1971 Internet protocol suite RFC 959 [9]
FTP Secure FTPS Internet Society 1997Internet protocol suite RFC 2228, 4217 [10] [11]
HTTP Secure HTTPS Taher Elgamal et al.1995Internet protocol suite RFC 7230 [12] [13]
Host Unix Linkage File TransferHULFT ?1993—No
Hypertext Transfer Protocol HTTP Tim Berners-Lee et al.1991Internet protocol suite RFC 7231 [14] [15]
Micro Transport Protocol μTP Ludvig Strigeus, Greg Hazel, Stanislav Shalunov, Arvid Norberg, Bram Cohen 2007—No [16] [17]
Multicast Dissemination ProtocolMDP1993No
Multicast File Transfer Protocol MFTP C. Kenneth Miller et al.1995— IETF Draft (1998) [18]
NACK-Oriented Reliable Multicast Transport ProtocolNORM2000 RFC 5740
Odette File Transfer Protocol OFTP Organisation for Data Exchange by Tele Transmission in Europe1986 X.25 RFC 6726 [19]
Odette File Transfer Protocol 2 OFTP2 Organisation for Data Exchange by Tele Transmission in Europe2007X.25, Internet protocol suite RFC 5024 (V1.3) [20]
Reliable Blast UDP RBUDP Eric He et al.2002—No [21]
Remote copy rcp  ?1982Internet protocol suiteNo [22]
Secure copy SCP Tatu Ylönen1995 Secure Shell No [23]
Secure Hypertext Transfer Protocol S-HTTP IETF Web Transaction Security Working Group1999— RFC 2660 [24]
Simple Asynchronous File Transfer SAFT Ulli Horlacher1995—No [25] [26]
Simple File Transfer Protocol SFTP Mark K. Lottor1984— RFC 913 [27]
SSH file transfer protocol SFTP Tatu Ylönenc. 1997Secure Shell IETF Draft (2006) [28]
T.127 T.127 ITU [29] 1995 [30] — ITU T.127
Trivial File Transfer Protocol TFTP Noel Chiappa 1980Internet protocol suite RFC 1350 [31]
Tsunami UDP Protocol Tsunami Mark Meiss et al.2002—No [32] [33]
Tus open protocol for resumable file uploads tus Felix Geisendörfer, Marius Kleidl et al.2014—No [34] [35]
UDP-based Data Transfer Protocol UDT Yunhong Gu2004—No
UDP-based File Transfer Protocol UFTP Dennis Bush2001—No [36]
Unix-to-Unix Copy UUCP Mike Lesk 1979—No
Warp Speed Data TransferWDTLaurent Demailly et al.2015—No [37]

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

ProtocolEncryption
(data)		Transfer
resuming		 Multicast
capable		 Managed Refs
BITS Optional TLS / AES-128 [a] YesNoNo
BitTorrent None [b] Yes Peer-to-peer No [39] [40]
CCSDS File Delivery Protocol (CFDP)YesNoNo
Cross File Transfer (CFT) TLS / SSL Yes [41] [42]
Ether File Transfer Protocol (EFTP)None ?NoNo [43]
Fast and Secure Protocol (FASP) AES-256 / AES-192 / AES-128 YesNo [44] [45] [46]
File Delivery over Unidirectional Transport (FLUTE)Optional/Unspecified [c] NoYes [47] [48] [49]
File Service Protocol (FSP)NoneYesNoNo [50] [51]
File Transfer Access and Management (FTAM) ? [d] [52]
File Transfer Protocol (FTP)NoneYes [e] NoNo [53] [54] [55] [56] [57]
FTP Secure (FTPS) TLS / SSL YesNoNo
HTTP Secure (HTTPS) TLS / SSL YesNoNo [15] [58] [59]
Host Unix Linkage File Transfer (HULFT) AES  ?No [60] [61] [62] [63]
Hypertext Transfer Protocol (HTTP)None
(see HTTPS and S-HTTP)		YesNoNo [15] [64]
Micro Transport Protocol (μTP)NoneYes Peer-to-peer No [16]
Multicast Dissemination Protocol (MDP)NoneYesYes [65] [66]
Multicast File Transfer Protocol (MFTP)NoneYesYesNo [67] [68]
NACK-Oriented Reliable Multicast Transport Protocol (NORM) IPsec YesYes [69] [70]
Odette File Transfer Protocol (OFTP)NoneYes [19]
Odette File Transfer Protocol 2 (OFTP2) TLS Yes [20]
Reliable Blast UDP (RBUDP)NoneNoNo [21] [71] [72]
Remote copy (rcp)NoneNoNoNo [73]
Secure copy (SCP) Secure Shell NoNoNo
Secure Hypertext Transfer Protocol (S-HTTP) CMS / MOSS / otherNoNoNo [74]
Simple Asynchronous File Transfer (SAFT) PGP  ?NoNo [25] [26] [75]
Simple File Transfer Protocol (SFTP)NoneYesNoNo [76]
SSH file transfer protocol (SFTP) Secure Shell YesNoNo [77]
T.127 NoneYesYesNo [78] [79] [80]
Trivial File Transfer Protocol (TFTP)NoneNoNoNo [81]
Tsunami UDP Protocol NoneNoNoNo [82] [83]
Tus open protocol for resumable file uploads (tus)Optional/Unspecified [f] YesNoNo [34] [35]
UDP-based Data Transfer Protocol (UDT)ExperimentalNoNoNo [83] [84] [85]
UDP-based File Transfer Protocol (UFTP) AES-256 / AES-128 / 3DES / DES [g] YesYesNo [83] [36] [86]
Unix-to-Unix Copy (UUCP)NoneSome [h] NoNo [87] [88]
Warp Speed Data Transfer (WDT) AES-128 (OFB / CTR)YesNoNo [89] [90] [91]
  1. ↑ TLS when BITS is used with HTTPS, AES-128 when used with SMB 3, none with HTTP or SMB version below 3.0
  2. ↑ Some implementations can obfuscate traffic using RC4 et al. See BitTorrent protocol encryption.
  3. ↑ RFC 6726 suggests IPSec as one option.
  4. ↑ One implementation, Fujitsu openFT, applies AES.
  5. ↑ 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.
  6. ↑ It's recommended to use HTTPS provided by a webserver, proxy, or SSL terminator.
  7. ↑ These are the options in the reference implementation, which uses OpenSSL.
  8. ↑ 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.

ProtocolData port Control port Assigned
by IANA 		AssigneeRefs
Server Client Transport Server Client Transport
BITS 80/443 [a] / 137-139 [b] TCP / UDPNo—
BitTorrent 6881 [c] 6881TCP68816881TCPNo— [92]
CCSDS File Delivery Protocol (CFDP)
Cross File Transfer (CFT)1761 [d] TCP / X.25 [41] [42]
Ether File Transfer Protocol (EFTP)——None——None——
Fast and Secure Protocol (FASP)≥33001UDP22TCPNo— [92]
File Delivery over Unidirectional Transport (FLUTE)4001UDPNo— [92]
File Service Protocol (FSP)Chosen by user [e] UDPNo— [92]
File Transfer Access and Management (FTAM)4800 / 102TCP [93]
File Transfer Protocol (FTP)Active mode2020TCP [f] 21≥1024TCPYes Jon Postel [92]
Passive mode≥1024 [g] ≥1024
FTP Secure (FTPS)989TCP990TCPYesChristopher Allen [92]
HTTP Secure (HTTPS)443TCPTCPYes IESG [92]
Host Unix Linkage File Transfer (HULFT)30000TCPTCPNo— [92]
Hypertext Transfer Protocol (HTTP)80TCPTCPYes Tim Berners-Lee [92]
Micro Transport Protocol (μTP)UDPNo— [92]
Multicast Dissemination Protocol (MDP)Chosen by userUDP [94] [66]
Multicast File Transfer Protocol (MFTP)5402UDPYesSteve Bannister [92]
NACK-Oriented Reliable Multicast Transport Protocol (NORM)UDP [69] [70]
Odette File Transfer Protocol (OFTP)3305TCP / X.25TCP / X.25 [19]
Odette File Transfer Protocol 2 (OFTP2)6619TCP / X.25TCP / X.25 [20]
Reliable Blast UDP (RBUDP)Chosen by userUDPNo— [92]
Remote copy (rcp)514TCPTCPYes [92]
Secure copy (SCP)22TCPTCPYes [92]
Secure Hypertext Transfer Protocol (S-HTTP)80TCPTCPNo— [92]
Simple Asynchronous File Transfer (SAFT)487TCPYesUlli Horlacher [92]
Simple File Transfer Protocol (SFTP)115TCPTCPYesMark Lottor [92]
SSH file transfer protocol (SFTP)22TCPTCPYes [92]
T.127 1503TCPTCPYesJim Johnston [92]
Trivial File Transfer Protocol (TFTP)69UDPYes David Clark [92]
Tsunami UDP Protocol Chosen by userUDPTCPNo— [92]
Tus open protocol for resumable file uploads (tus)80 [h] TCPTCPNo— [92]
UDP-based Data Transfer Protocol (UDT)Chosen by serverUDPNo— [92]
UDP-based File Transfer Protocol (UFTP)1044UDPNo— [92]
Unix-to-Unix Copy (UUCP)540TCPTCPYes [92]
Warp Speed Data Transfer (WDT)Chosen by server or by userTCPTCPNo— [92]
  1. ↑ When used with HTTP/HTTPS, configurable
  2. ↑ When used with SMB
  3. ↑ Typically, if port 6881 is unavailable as a listening port, the peer incrementally tries 6882–6889. Another port may be specified in software.
  4. ↑ 1761 is the default port, but 1761–1768 are allocated by IANA.
  5. ↑ UDP port 21 is sometimes chosen for FSP.
  6. ↑ 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.
  7. ↑ 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.
  8. ↑ 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 RS-232-Cable-9-25.jpg
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

ProtocolAuthorFirst releasedLicenseDescriptionRefs
BiModem Erik Labs1989Bi-directional transfers.
BLAST Communications Research Group 1981Powerful protocol originating on the Data General Nova minicomputer, and then ported to micros and mainframes. [95]
C-MODEM Lavio Pareschi1989Packet lengths from 32 to 4096 bytes, optional (but normally used) streaming mode.
B protocol CompuServe 1981Offered 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. Smith1991
Kermit Frank da Cruz et al.1981Open Source (BSD) as of 2011Transport- 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]
LeechModemSam Brown ?Variations of X and Y that faked failed downloads in order to avoid BBS download quotas.
Lynx Matthew Thomas1989Similar 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. Neal1990Essentially 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 Henderson1986A 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 1979Suite 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. Mills1980Slight extension of XMODEM to add filename support and batch transfers. [102]
XMODEM Ward Christensen 1977Public domainVery simple protocol that saw widespread use and provided the pattern for many following protocols. [103]
WXMODEM Peter Boswell1986Public domainVersion of XMODEM with sliding windows for higher performance. [104] [105]
YMODEM Chuck Forsberg 1985Public domainSeries of optional expansions on XMODEM for higher performance. [104]
ZMax Mike Bryeansc. 1991Modifications to ZMODEM to allow packets up to 32 kB in length.
ZMODEM Chuck Forsberg 1986Public domainStreaming 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]

Features

ProtocolData block size
(bytes)		 Data
compression 		Error detection Transfer
resuming		Bidirectional Sliding window Refs
BiModem Yes
BLAST 84 - 1024+ RLE CRC YesYesYes [106]
C-MODEM 32–4096CRCYes
B protocol 128–2048CRC32 / CRC16 / 8-bit checksumYesYes
JMODEM 64–8192 RLE
HS/Link CRC32 YesYes
Kermit ≤9024 (negotiated) RLE (run length encoding, negotiated) Checksum or CRC16 (negotiated)Yes (binary files only, negotiated)NoOver full-duplex only (negotiated) [107]
LeechModem
Lynx RLECRC32Yes
NMODEM 2048
OBject EXchange
Punter
SEAlink YesYes
SMODEM Yes
Tmodem No
UUCP "g"≤4096NoNo [108] [109]
MODEM7 128NoChecksum Stop-and-wait ARQ
XMODEM 128NoChecksumStop-and-wait ARQ
WXMODEM ≤512Yes
YMODEM 1024No CRC16
ZMax ≤~32,768CRC32
ZMODEM 256 / 1024NoCRC32YesYes

See also

Notes

  1. ↑ "Background_Intelligent Transfer Service". Microsoft Learn . 25 May 2021.
  2. ↑ Cohen, Bram (2 July 2001). "The BitTorrent Protocol Specification". Yahoo! Finance Groups . Archived from the original on 16 December 2008. Retrieved 23 February 2018.
  3. ↑ Shoch, John (1979). EFTP: A PUP-based Ether File Transfer Protocol.
  4. ↑ Snodgrass, Richard (December 1982). A Relational Approach to Monitoring Complex Systems. pp.  119, 149. Retrieved 3 March 2018.
  5. ↑ USpatent 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
  6. ↑ 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.
  7. ↑ 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.
  8. ↑ "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.
  9. ↑ Bhushan, Abhay (April 1971). A File Transfer Protocol. IETF. doi: 10.17487/RFC0114 . RFC 114 . Retrieved 24 February 2018.
  10. ↑ Horowitz, M.; Lunt, S. (October 1997). FTP Security Extensions. IETF. doi: 10.17487/RFC2228 . RFC 2228 . Retrieved 3 March 2018.
  11. ↑ Ford-Hutchinson, Paul (October 2005). Securing FTP with TLS. IETF. doi: 10.17487/RFC4217 . RFC 4217 . Retrieved 3 March 2018.
  12. ↑ Sliwa, Carol (31 May 1999). "Secure Sockets Layer". Computerworld . p. 69. Retrieved 1 March 2018– via Google Books.
  13. ↑ Hickman, Kipp E. B. (April 1995). The SSL Protocol. IETF. I-D draft-hickman-netscape-ssl-00. Retrieved 1 March 2018.
  14. ↑ Berners-Lee, Tim. "The Original HTTP as defined in 1991". W3.org. Retrieved 3 March 2018.
  15. 1 2 3 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.
  16. 1 2 Norberg, Arvid (22 June 2009). "uTorrent transport protocol". BitTorrent.org. Retrieved 10 March 2018.
  17. ↑ Klinker, Eric (16 May 2010). "Eric Klinker Presentation at Emerging Communication Conference & Awards 2010 America § Status of uTP". eCommConf. Retrieved 10 March 2018.
  18. ↑ U Spatent 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
  19. 1 2 3 Nash, David (September 1997). ODETTE File Transfer Protocol. IETF. doi: 10.17487/RFC2204 . RFC 2204 . Retrieved 22 February 2018.
  20. 1 2 3 Friend, Ieuan (November 2007). ODETTE File Transfer Protocol 2. IETF. doi: 10.17487/RFC5024 . RFC 5024 . Retrieved 22 February 2018.
  21. 1 2 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.
  22. ↑ 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.
  23. ↑ Ylonen, Tatu (31 August 2017). "SSH: Secure Shell § History of the SSH Protocol". SSH.com. Retrieved 3 March 2018.
  24. ↑ Rescorla, Eric; Schiffman, Allan M. (August 1999). The Secure HyperText Transfer Protocol. IETF. doi: 10.17487/RFC2660 . RFC 2660 . Retrieved 9 March 2018.
  25. 1 2 Horlacher, Ulli. "SAFT / sendfile". fex.belwue.de. Retrieved 3 March 2018.
  26. 1 2 Horlacher, Ulli. "sendfile(1)". manpages.org. Retrieved 3 March 2018.
  27. ↑ Lottor (1984), pp. 1, 13
  28. ↑ 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).[ permanent dead link ]
  29. ↑ "T.127: Multipoint binary file transfer protocol". ITU . Retrieved 23 March 2021.
  30. ↑ "T.127 (08/95) Multipoint binary file transfer protocol". ITU . Retrieved 23 March 2021.
  31. ↑ Sollins, Karen R. (January 1980). The TFTP Protocol. IETF. IEN 133. Retrieved 24 February 2018.
  32. ↑ Wagner, Jan. "Tsunami UDP Protocol". tsunami-udp.sourceforge.net. Jon Wagner – via SourceForge.
  33. ↑ "Research". anml.iu.edu. Pervasive Technology Labs at Indiana University. Section: "Tsunami". Archived from the original on 29 July 2010.
  34. 1 2 protocol.md on GitHub
  35. 1 2 "tus - resumable file uploads".
  36. 1 2 Bush, Dennis. "Changes". uftp-multicast.sourceforge.net. Dennis Bush. Retrieved 9 March 2018– via SourceForge.
  37. ↑ "wdt: Releases". GitHub. Retrieved 7 April 2023.
  38. ↑ Villanueva, John Carl (17 February 2015). "Managed File Transfer and Network Solutions". JSCAPE.com. JSCAPE.
  39. ↑ Cohen, Bram (4 February 2017) [2008]. "The BitTorrent Protocol Specification". BitTorrent.org. Section: "Trackers". Retrieved 22 February 2018.
  40. ↑ "Message Stream Encryption". Vuze Wiki. Azureus Software. 1 December 2007 [2006]. Retrieved 10 March 2018.
  41. 1 2 "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.
  42. 1 2 "Transfer CFT 3.2.2 Local Administration Guide § Transport Security". Axway.com. Axway Software . Retrieved 22 February 2018.
  43. ↑ "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.
  44. ↑ Pott, Trevor (1 October 2015). "Aspera high speed file transfer: Let the cloud protocol wars begin". The Register . Retrieved 18 February 2018.
  45. ↑ "FASP Security Model". AsperaSoft.com. Aspera. 2017. Retrieved 18 February 2018.
  46. ↑ Campos, Andrea (2 June 2016). "Resuming file transfers with ascp". AsperaSoft.com. Aspera. Retrieved 2 March 2018.
  47. ↑ 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.
  48. ↑ 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.
  49. ↑ 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. S2CID   260426266.
  50. ↑ "File Service Protocol (FSP) Frequently Asked Questions v1.1". FAQs.org. 19 August 1996. Retrieved 18 February 2018.
  51. ↑ "Common Ports". Red Hat Enterprise Linux 4: Security Guide. Red Hat. 2005. Retrieved 2 March 2018.
  52. ↑ "openFT v11.0: Setting Up a Connection to Customs (Atlas) with openFT FTAM" (PDF). Fujitsu. 2010. p. 2. Retrieved 18 February 2018.
  53. ↑ Postel, Jon; Reynolds, Joyce (October 1985). File Transfer Protocol (FTP). IETF. doi: 10.17487/RFC0959 . RFC 959 . Retrieved 22 February 2018.
  54. ↑ Kozierok, Charles M. (20 September 2005). "FTP Overview, History and Standards". The TCP/IP Guide (v3.0 ed.). Retrieved 21 February 2018.
  55. ↑ Bhushan, Abhay (April 1971). A File Transfer Protocol. IETF. doi: 10.17487/RFC0114 . RFC 114 . Retrieved 22 February 2018.
  56. ↑ 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.
  57. ↑ 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.
  58. ↑ Rescorla, Eric (May 2000). HTTP Over TLS. IETF. doi: 10.17487/RFC2818 . RFC 2818 . Retrieved 20 February 2018.
  59. ↑ Reynolds, Joyce; Postel, Jon (October 1994). Assigned Numbers. IETF. p. 34. doi: 10.17487/RFC1700 . RFC 1700 . Retrieved 3 March 2018.
  60. ↑ "The Incredible HULFT – My Favorite B2B Network Protocol". OpenText Blogs. OpenText. 27 August 2009. Retrieved 18 February 2018.
  61. ↑ "9.4.1. HULFT § Overview". Enterprise Cloud Knowledge Center. NTT Communications . Retrieved 2 March 2018.
  62. ↑ "9.4.1. HULFT § HULFT 8 Cipher Option". Enterprise Cloud Knowledge Center. NTT Communications . Retrieved 18 February 2018.
  63. ↑ "導入サービス". HULFT.com (in Japanese). Saison Information Systems. Section: "前提事項、その他". Retrieved 21 February 2018.
  64. ↑ Reynolds, Joyce; Postel, Jon (July 1992). Assigned Numbers. IETF. p. 12. doi: 10.17487/RFC1340 . RFC 1340 . Retrieved 3 March 2018.
  65. ↑ Adamson, Brian; Macker, Joe. "Multicast Dissemination Protocol (MDP) Developer's Guide". nrl.navy.mil. United States Naval Research Laboratory . Retrieved 22 February 2018.
  66. 1 2 "Multicast Dissemination Protocol History". nrl.navy.mil. United States Naval Research Laboratory. Retrieved 22 February 2018.
  67. ↑ 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.
  68. ↑ "StarBurst MFTP Compared to Today's File Transfer Protocols: A White Paper". StarBurst Communications. 1996 – via University of California, Irvine.
  69. 1 2 "NACK-Oriented Reliable Multicast (NORM)". nrl.navy.mil. United States Naval Research Laboratory . Retrieved 22 February 2018.
  70. 1 2 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.
  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. January 2005. p. 137. ISBN   9780974094526.
  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. 1 2 3 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. Archived from the original on 10 December 2017. 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. Archived from the original on 12 December 2021. 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. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 "Service Name and Transport Protocol Port Number Registry". IANA.org. Internet Assigned Numbers Authority. 28 February 2018. Retrieved 17 March 2018.
  93. ↑ "openFT v11.0: Setting Up a Connection to Customs (Atlas) with openFT FTAM" (PDF). Fujitsu. 2010. p. 2. Retrieved 18 February 2018.
  94. ↑ Adamson, Brian; Macker, Joe. "Multicast Dissemination Protocol (MDP) Developer's Guide". nrl.navy.mil. United States Naval Research Laboratory . Retrieved 22 February 2018.
  95. ↑ Magidson, Steve (15 May 1989). "Moving Files Can Be a BLAST" (PDF). UNIX Today!. CMP Media. Retrieved 18 February 2018.
  96. ↑ da Cruz (1987) p. 3
  97. ↑ "OBEX (Object Exchange) Protocol". irdajp.org. Infrared Data Association. 2011. Archived from the original on 21 February 2018. Retrieved 20 February 2018.
  98. ↑ sealink.c on GitHub
  99. ↑ Held, Gilbert (1993). "SeaLink". Mastering PC Communications Software. Van Nostrand Reinhold. p. 74.
  100. ↑ Woggon, Michele (1995). "SeaLink". Telecommunications Using ProComm & ProComm Plus Made Easy. Prentice Hall. p. 34.
  101. ↑ "UUCP protocol internals". University of Utah.
  102. ↑ Lucas, Jay (6 September 1982). "Freeware: Modem lets your computers communicate". InfoWorld . IDG. p. 53. Retrieved 18 February 2018.
  103. ↑ Glass (1988) p. 87
  104. 1 2 3 Glass (1988) p. 89
  105. ↑ Boswell, Peter (2007) [1986]. How XModem, XModem CRC, and WXModem work. Archived from the original on 23 September 2014 – via Totse.com.
  106. ↑ Magidson, Steve (15 May 1989). "Moving Files Can Be a BLAST" (PDF). UNIX Today!. CMP Media. Retrieved 18 February 2018.
  107. ↑ da Cruz (1987) pp. 234, 253, 307
  108. ↑ 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.
  109. ↑ Taylor, Ian Lance. "UUCP 'g' Protocol". FreeBSD Documentation Server. The FreeBSD Project. Retrieved 8 March 2018.

Related Research Articles

<span class="mw-page-title-main">HTTP</span> Application protocol for distributed, collaborative, hypermedia information systems

HTTP is an application layer protocol in the Internet protocol suite model for distributed, collaborative, hypermedia information systems. HTTP is the foundation of data communication for the World Wide Web, where hypertext documents include hyperlinks to other resources that the user can easily access, for example by a mouse click or by tapping the screen in a web browser.

The Internet protocol suite, commonly known as TCP/IP, is a framework for organizing the set of communication protocols used in the Internet and similar computer networks according to functional criteria. The foundational protocols in the suite are the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP). Early versions of this networking model were known as the Department of Defense (DoD) model because the research and development were funded by the United States Department of Defense through DARPA.

The Secure Shell Protocol is a cryptographic network protocol for operating network services securely over an unsecured network. Its most notable applications are remote login and command-line execution.

The Transmission Control Protocol (TCP) is one of the main protocols of the Internet protocol suite. It originated in the initial network implementation in which it complemented the Internet Protocol (IP). Therefore, the entire suite is commonly referred to as TCP/IP. TCP provides reliable, ordered, and error-checked delivery of a stream of octets (bytes) between applications running on hosts communicating via an IP network. Major internet applications such as the World Wide Web, email, remote administration, and file transfer rely on TCP, which is part of the transport layer of the TCP/IP suite. SSL/TLS often runs on top of TCP.

Telnet is a client/server application protocol that provides access to virtual terminals of remote systems on local area networks or the Internet. It is a protocol for bidirectional 8-bit communications. Its main goal was to connect terminal devices and terminal-oriented processes.

In computer networking, the User Datagram Protocol (UDP) is one of the core communication protocols of the Internet protocol suite used to send messages to other hosts on an Internet Protocol (IP) network. Within an IP network, UDP does not require prior communication to set up communication channels or data paths.

A multicast address is a logical identifier for a group of hosts in a computer network that are available to process datagrams or frames intended to be multicast for a designated network service. Multicast addressing can be used in the link layer, such as Ethernet multicast, and at the internet layer for Internet Protocol Version 4 (IPv4) or Version 6 (IPv6) multicast.

The File Transfer Protocol (FTP) is a standard communication protocol used for the transfer of computer files from a server to a client on a computer network. FTP is built on a client–server model architecture using separate control and data connections between the client and the server. FTP users may authenticate themselves with a plain-text sign-in protocol, normally in the form of a username and password, but can connect anonymously if the server is configured to allow it. For secure transmission that protects the username and password, and encrypts the content, FTP is often secured with SSL/TLS (FTPS) or replaced with SSH File Transfer Protocol (SFTP).

An ephemeral port is a communications endpoint (port) of a transport layer protocol of the Internet protocol suite that is used for only a short period of time for the duration of a communication session. Such short-lived ports are allocated automatically within a predefined range of port numbers by the IP stack software of a computer operating system. The Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Stream Control Transmission Protocol (SCTP) typically use an ephemeral port for the client-end of a client–server communication. At the server end of the communication session, ephemeral ports may also be used for continuation of communications with a client that initially connected to one of the services listening with a well-known port. For example, the Trivial File Transfer Protocol (TFTP) and Remote Procedure Call (RPC) applications can behave in this manner.

SOCKS is an Internet protocol that exchanges network packets between a client and server through a proxy server. SOCKS5 optionally provides authentication so only authorized users may access a server. Practically, a SOCKS server proxies TCP connections to an arbitrary IP address, and provides a means for UDP packets to be forwarded. A SOCKS server accepts incoming client connection on TCP port 1080, as defined in RFC 1928.

In computing, the SSH File Transfer Protocol, also known as Secure File Transfer Protocol (SFTP), is a network protocol that provides file access, file transfer, and file management over any reliable data stream. It was designed by the Internet Engineering Task Force (IETF) as an extension of the Secure Shell protocol (SSH) version 2.0 to provide secure file transfer capabilities, and is seen as a replacement of File Transfer Protocol (FTP) due to superior security. The IETF Internet Draft states that, even though this protocol is described in the context of the SSH-2 protocol, it could be used in a number of different applications, such as secure file transfer over Transport Layer Security (TLS) and transfer of management information in VPN applications.

A Service record is a specification of data in the Domain Name System defining the location, i.e., the hostname and port number, of servers for specified services. It is defined in RFC 2782, and its type code is 33. Some Internet protocols such as the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP) often require SRV support by network elements.

FTPS is an extension to the commonly used File Transfer Protocol (FTP) that adds support for the Transport Layer Security (TLS) and, formerly, the Secure Sockets Layer cryptographic protocols.

In computing, syslog is a standard for message logging. It allows separation of the software that generates messages, the system that stores them, and the software that reports and analyzes them. Each message is labeled with a facility code, indicating the type of system generating the message, and is assigned a severity level.

In computer networking, a port or port number is a number assigned to uniquely identify a connection endpoint and to direct data to a specific service. At the software level, within an operating system, a port is a logical construct that identifies a specific process or a type of network service. A port at the software level is identified for each transport protocol and address combination by the port number assigned to it. The most common transport protocols that use port numbers are the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP); those port numbers are 16-bit unsigned numbers.

The Stream Control Transmission Protocol (SCTP) is a computer networking communications protocol in the transport layer of the Internet protocol suite. Originally intended for Signaling System 7 (SS7) message transport in telecommunication, the protocol provides the message-oriented feature of the User Datagram Protocol (UDP), while ensuring reliable, in-sequence transport of messages with congestion control like the Transmission Control Protocol (TCP). Unlike UDP and TCP, the protocol supports multihoming and redundant paths to increase resilience and reliability.

RDMA over Converged Ethernet (RoCE) is a network protocol which allows remote direct memory access (RDMA) over an Ethernet network. There are multiple RoCE versions. RoCE v1 is an Ethernet link layer protocol and hence allows communication between any two hosts in the same Ethernet broadcast domain. RoCE v2 is an internet layer protocol which means that RoCE v2 packets can be routed. Although the RoCE protocol benefits from the characteristics of a converged Ethernet network, the protocol can also be used on a traditional or non-converged Ethernet network.

QUIC is a general-purpose transport layer network protocol initially designed by Jim Roskind at Google. It was first implemented and deployed in 2012 and was publicly announced in 2013 as experimentation broadened. It was also described at an IETF meeting. The Chrome web browser, Microsoft Edge, Firefox, and Safari all support it. In Chrome, QUIC is used by more than half of all connections to Google's servers.

<span class="mw-page-title-main">Fast and Secure Protocol</span> Terminal command scheme used to transfer data

The Fast Adaptive and Secure Protocol (FASP) is a proprietary data transfer protocol. FASP is a network-optimized network protocol created by Michelle C. Munson and Serban Simu, productized by Aspera, and now owned by IBM subsequent to its acquisition of Aspera. The associated client/server software packages are also commonly called Aspera. The technology is patented under US Patent #8085781, Bulk Data Transfer, #20090063698, Method and system for aggregate bandwidth control. and others.

References

Further reading

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.