Comparison of file transfer protocols

From HandWiki - Reading time: 15 min


Short description: None

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.

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
CCSDS File Delivery Protocol CFDP 2002 N/A ISO 17355:2007 (v4)
CCSDS 727.0-B-5
Cross File Transfer CFT N/A No
Fast and Secure Protocol FASP Ying Xu, Michelle Munson, Serban Simu 2007 N/A No [1]
File Delivery over Unidirectional Transport FLUTE Internet Society 2004 N/A RFC 6726 [2]
File Service Protocol FSP Wen-King Su 1991 N/A No [3][4]
File Transfer Access and Management FTAM ISO 8571-4:1988
FTP Secure FTPS Internet Society 1997 Internet protocol suite RFC 2228, 4217 [5][6]
HTTP Secure HTTPS Taher Elgamal et al. 1995 Internet protocol suite RFC 7230 [7][8]
Host Unix Linkage File Transfer HULFT ? 1993 N/A No
Micro Transport Protocol μTP Ludvig Strigeus, Greg Hazel, Stanislav Shalunov, Arvid Norberg, Bram Cohen 2007 N/A No [9][10]
Multicast Dissemination Protocol MDP No
Multicast File Transfer Protocol MFTP C. Kenneth Miller et al. 1995 N/A IETF Draft (1998) [11]
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 [12]
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) [13]
Reliable Blast UDP RBUDP Eric He et al. 2002 N/A No [14]
Secure copy SCP Tatu Ylönen ? Secure Shell No [15]
Secure Hypertext Transfer Protocol S-HTTP IETF Web Transaction Security Working Group 1999 N/A RFC 2660 [16]
Simple Asynchronous File Transfer SAFT Ulli Horlacher 1995 N/A No [17][18]
Simple File Transfer Protocol SFTP Mark K. Lottor 1984 N/A RFC 913 [19]
SSH file transfer protocol SFTP Tatu Ylönen 1997 c. 1997 Secure Shell IETF Draft (2006) [20]
T.127 T.127 ITU[21] 1995 [22] N/A ITU T.127
Trivial File Transfer Protocol TFTP Noel Chiappa 1980 Internet protocol suite RFC 1350 [23]
Tsunami UDP Protocol Tsunami Mark Meiss et al. 2002 N/A No [24][25]
Tus open protocol for resumable file uploads tus Felix Geisendörfer, Marius Kleidl et al. 2014 N/A No [26][27]
UDP-based Data Transfer Protocol UDT Yunhong Gu 2004 N/A No
UDP-based File Transfer Protocol UFTP Dennis Bush 2001 N/A No [28]
Unix-to-Unix Copy UUCP Mike Lesk 1979 N/A No
Warp Speed Data Transfer WDT Laurent Demailly et al. 2015 N/A No [29]

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

Protocol Encryption
(data)
Transfer
resuming
Multicast
capable
Managed Refs
CCSDS File Delivery Protocol (CFDP) Yes No No
Cross File Transfer (CFT) TLS / SSL Yes [31][32]
Ether File Transfer Protocol (EFTP) None ? No No [33]
Fast and Secure Protocol (FASP) AES-256 / AES-192 / AES-128 Yes No [34][35][36]
File Delivery over Unidirectional Transport (FLUTE) Optional/Unspecified[lower-alpha 1] No Yes [37][38][39]
File Service Protocol (FSP) None Yes No No [40][41]
File Transfer Access and Management (FTAM) ?[lower-alpha 2] [42]
FTP Secure (FTPS) TLS / SSL Yes No No
Host Unix Linkage File Transfer (HULFT) AES ? No [43][44][45][46]
Micro Transport Protocol (μTP) None Yes Peer-to-peer No [9]
Multicast Dissemination Protocol (MDP) None Yes Yes [47][48]
Multicast File Transfer Protocol (MFTP) None Yes Yes No [49][50]
NACK-Oriented Reliable Multicast Transport Protocol (NORM) IPsec Yes Yes [51][52]
Odette File Transfer Protocol (OFTP) None Yes [12]
Odette File Transfer Protocol 2 (OFTP2) TLS Yes [13]
Remote copy (rcp) None No No No [53]
Secure copy (SCP) Secure Shell No No No
Secure Hypertext Transfer Protocol (S-HTTP) CMS / MOSS / other No No No [54]
Simple Asynchronous File Transfer (SAFT) PGP ? No No [17][18][55]
Simple File Transfer Protocol (SFTP) None Yes No No [56]
SSH file transfer protocol (SFTP) Secure Shell Yes No No [57]
T.127 None Yes Yes No [58][59][60]
Trivial File Transfer Protocol (TFTP) None No No No [61]
Tsunami UDP Protocol None No No No [62][63]
Tus open protocol for resumable file uploads (tus) Optional/Unspecified[lower-alpha 3] Yes No No [26][27]
UDP-based Data Transfer Protocol (UDT) Experimental No No No [63][64][65]
UDP-based File Transfer Protocol (UFTP) AES-256 / AES-128 / 3DES / DES[lower-alpha 4] Yes Yes No [63][28][66]
Unix-to-Unix Copy (UUCP) None Some[lower-alpha 5] No No [67][68]
Warp Speed Data Transfer (WDT) AES-128 (OFB / CTR) Yes No No [69][70][71]
  1. RFC 6726 suggests IPSec as one option.
  2. One implementation, Fujitsu openFT, applies AES.
  3. It's recommended to use HTTPS provided by a webserver, proxy, or SSL terminator.
  4. These are the options in the reference implementation, which uses OpenSSL.
  5. The BNU implementation of UUCP can resume an interrupted file transfer.
Cite error: <ref> tag with name "a" defined in <references> is not used in prior text.

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 [72]
CCSDS File Delivery Protocol (CFDP)
Cross File Transfer (CFT) 1761[lower-alpha 2] TCP / X.25 [31][32]
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 [72]
File Delivery over Unidirectional Transport (FLUTE) 4001 UDP No N/A [72]
File Service Protocol (FSP) Chosen by user[lower-alpha 3] UDP No N/A [72]
File Transfer Access and Management (FTAM) 4800 / 102 TCP [73]
File Transfer Protocol (FTP) Active mode 20 20 TCP[lower-alpha 4] 21 ≥1024 TCP Yes Jon Postel [72]
Passive mode ≥1024[lower-alpha 5] ≥1024
FTP Secure (FTPS) 989 TCP 990 TCP Yes Christopher Allen [72]
HTTP Secure (HTTPS) 443 TCP TCP Yes IESG [72]
Host Unix Linkage File Transfer (HULFT) 30000 TCP TCP No N/A [72]
Hypertext Transfer Protocol (HTTP) 80 TCP TCP Yes Tim Berners-Lee [72]
Micro Transport Protocol (μTP) UDP No N/A [72]
Multicast Dissemination Protocol (MDP) Chosen by user UDP [74][48]
Multicast File Transfer Protocol (MFTP) 5402 UDP Yes Steve Bannister [72]
NACK-Oriented Reliable Multicast Transport Protocol (NORM) UDP [51][52]
Odette File Transfer Protocol (OFTP) 3305 TCP / X.25 TCP / X.25 [12]
Odette File Transfer Protocol 2 (OFTP2) 6619 TCP / X.25 TCP / X.25 [13]
Reliable Blast UDP (RBUDP) Chosen by user UDP No N/A [72]
Remote copy (rcp) 514 TCP TCP Yes [72]
Secure copy (SCP) 22 TCP TCP Yes [72]
Secure Hypertext Transfer Protocol (S-HTTP) 80 TCP TCP No N/A [72]
Simple Asynchronous File Transfer (SAFT) 487 TCP Yes Ulli Horlacher [72]
Simple File Transfer Protocol (SFTP) 115 TCP TCP Yes Mark Lottor [72]
SSH file transfer protocol (SFTP) 22 TCP TCP Yes [72]
T.127 1503 TCP TCP Yes Jim Johnston [72]
Trivial File Transfer Protocol (TFTP) 69 UDP Yes David Clark [72]
Tsunami UDP Protocol Chosen by user UDP TCP No N/A [72]
Tus open protocol for resumable file uploads (tus) 80[lower-alpha 6] TCP TCP No N/A [72]
UDP-based Data Transfer Protocol (UDT) Chosen by server UDP No N/A [72]
UDP-based File Transfer Protocol (UFTP) 1044 UDP No N/A [72]
Unix-to-Unix Copy (UUCP) 540 TCP TCP Yes [72]
Warp Speed Data Transfer (WDT) Chosen by server or by user TCP TCP No N/A [72]
  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 1981 Powerful protocol originating on the Data General Nova minicomputer, and then ported to micros and mainframes. [75]
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. [76]
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. [77]
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. [78][79][80]
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. [81]
MODEM7 Mark M. Zeigler, James K. Mills 1980 Slight extension of XMODEM to add filename support and batch transfers. [82]
XMODEM Ward Christensen 1977 Public domain Very simple protocol that saw widespread use and provided the pattern for many following protocols. [83]
WXMODEM Peter Boswell 1986 Public domain Version of XMODEM with sliding windows for higher performance. [84][85]
YMODEM Chuck Forsberg 1985 Public domain Series of optional expansions on XMODEM for higher performance. [84]
ZMax Mike Bryeans 1991 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. [84]

Features

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 [86]
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) [87]
LeechModem
Lynx RLE CRC32 Yes
NMODEM 2048
OBject EXchange
Punter
SEAlink Yes Yes
SMODEM Yes
Tmodem No
UUCP "g" ≤4096 No No [88][89]
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

Notes

  1. Ying Xu, Michelle Christine Munson, Serban Simu, "Method and system for aggregate bandwith control [sic]", US patent 20090063698, issued 30 May 2017, assigned to Aspera, Inc.and IBM
  2. 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, https://tools.ietf.org/html/rfc3926, retrieved 2018-03-07 
  3. Petersen, Julie K., ed (2002). "File Service Protocol". The Telecommunications Illustrated Dictionary (2nd ed.). CRC Press. p. 357. ISBN 978-1-4200-4067-8. https://books.google.com/books?id=YH_LBQAAQBAJ&pg=PA357. 
  4. "File Service Protocol (FSP) Frequently Asked Questions [Part 2/2"]. 21 July 1995. Section: "Who writes and maintains FSP software?". http://www.faqs.org/faqs/fsp-faq/part2/. 
  5. Horowitz, M.; Lunt, S. (October 1997), FTP Security Extensions, IETF, doi:10.17487/RFC2228, RFC 2228, https://tools.ietf.org/html/rfc2228, retrieved 2018-03-03 
  6. Ford-Hutchinson, Paul (October 2005), Securing FTP with TLS, IETF, doi:10.17487/RFC4217, RFC 4217, https://tools.ietf.org/html/rfc4217, retrieved 2018-03-03 
  7. Sliwa, Carol (31 May 1999). "Secure Sockets Layer". Computerworld: 69. https://books.google.com/books?id=KQMeZfQuVxoC&pg=PT37. Retrieved 2018-03-01. 
  8. Hickman, Kipp E. B. (April 1995), The SSL Protocol, IETF, I-D draft-hickman-netscape-ssl-00, https://tools.ietf.org/html/draft-hickman-netscape-ssl-00, retrieved 2018-03-01 
  9. 9.0 9.1 Norberg, Arvid (22 June 2009). "uTorrent transport protocol". http://bittorrent.org/beps/bep_0029.html. 
  10. Klinker, Eric (16 May 2010). "Eric Klinker Presentation at Emerging Communication Conference & Awards 2010 America § Status of uTP". eCommConf. https://www.slideshare.net/eCommConf/eric-klinker-presentation-at-emerging-communication-conference-awards-2010-america/11. 
  11. 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", S7710961 U S patent 7710961, issued 20 December 2011, assigned to Darby and Mohaine LLC
  12. 12.0 12.1 12.2 Nash, David (September 1997), ODETTE File Transfer Protocol, IETF, doi:10.17487/RFC2204, RFC 2204, https://tools.ietf.org/html/rfc2204, retrieved 2018-02-22 
  13. 13.0 13.1 13.2 Friend, Ieuan (November 2007), ODETTE File Transfer Protocol 2, IETF, doi:10.17487/RFC5024, RFC 5024, https://tools.ietf.org/html/rfc5024, retrieved 2018-02-22 
  14. He, Eric; Leigh, Jason; Yu, Oliver; DeFanti, Thomas A. (September 2002). "Reliable Blast UDP: Predictable High Performance Bulk Data Transfer". IEEE Cluster Computing 2002. Chicago. pp. 317–24. OCLC 5942572037. https://www.evl.uic.edu/eric/papers/He-Cluster-02.pdf. Retrieved 2018-03-02. 
  15. Ylonen, Tatu (31 August 2017). "SSH: Secure Shell § History of the SSH Protocol". https://www.ssh.com/ssh/#sec-History-of-the-SSH-protocol. 
  16. Rescorla, Eric; Schiffman, Allan M. (August 1999), The Secure HyperText Transfer Protocol, IETF, doi:10.17487/RFC2660, RFC 2660, https://tools.ietf.org/html/rfc2660, retrieved 2018-03-09 
  17. 17.0 17.1 Horlacher, Ulli. "SAFT / sendfile". https://fex.belwue.de/saft/. 
  18. 18.0 18.1 Horlacher, Ulli. "sendfile(1)". http://manpages.org/sendfile. 
  19. Lottor (1984), pp. 1, 13
  20. 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).
    [yes|permanent dead link|dead link}}]
  21. "T.127: Multipoint binary file transfer protocol". ITU. https://www.itu.int/rec/T-REC-T.127. 
  22. "T.127 (08/95) Multipoint binary file transfer protocol". ITU. https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.127-199508-S!!PDF-E&type=items. 
  23. Sollins, Karen R. (January 1980), The TFTP Protocol, IETF, IEN 133, https://tools.ietf.org/rfcmarkup?url=https://www.ietf.org/rfc/ien/ien133.txt, retrieved 2018-02-24 
  24. Wagner, Jan. "Tsunami UDP Protocol". Jon Wagner. http://tsunami-udp.sourceforge.net/. 
  25. "Research". Pervasive Technology Labs at Indiana University. Section: "Tsunami". http://anml.iu.edu/research.shtml?prim=lab_research. 
  26. 26.0 26.1 on GitHub
  27. 27.0 27.1 "tus - resumable file uploads". https://tus.io. 
  28. 28.0 28.1 Bush, Dennis. "Changes". Dennis Bush. http://uftp-multicast.sourceforge.net/Changes.txt. 
  29. "wdt: Releases". https://github.com/facebook/wdt/releases. 
  30. Villanueva, John Carl (17 February 2015). "Managed File Transfer and Network Solutions". JSCAPE. http://www.jscape.com/blog/oftp-odette-file-transfer-protocol. 
  31. 31.0 31.1 "Transfer CFT 3.2.4 Users Guide § Configuring Transfer CFT". Axway Software. https://docs.axway.com/bundle/TransferCFT_324_UsersGuide_allOS_en_HTML5/page/Content/UNIX/UNIX_operations/Running_CFT/cft_installation_test_in_tcp_mode.htm. 
  32. 32.0 32.1 "Transfer CFT 3.2.2 Local Administration Guide § Transport Security". Axway Software. https://docs.axway.com/bundle/Transfer_CFT_322_UsersGuide_LocalAdministration_allOS_en_HTML5/page/Content/architecture/intro_security.htm#Transport_Security. 
  33. "Printing at PARC—Appendix: Glossary of Terms § EFTP". 4 August 1978. http://xeroxalto.computerhistory.org/Indigo/Spruce/documents/PrintingAtParc.dm!1_/.appprinting.bravo.html. "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." 
  34. Pott, Trevor (1 October 2015). "Aspera high speed file transfer: Let the cloud protocol wars begin". https://www.theregister.co.uk/2015/10/01/aspera/. 
  35. "FASP Security Model". Aspera. 2017. http://asperasoft.com/technology/transport/fasp/fasp-security-model/. 
  36. Campos, Andrea (2 June 2016). "Resuming file transfers with ascp". Aspera. https://support.asperasoft.com/hc/en-us/articles/216125578-Resuming-file-transfers-with-ascp. 
  37. 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, https://tools.ietf.org/html/rfc3926, retrieved 2018-03-07 
  38. Peltotalo, Jani; Peltotalo, Sami; Harju, Jarmo. "Analysis of the FLUTE Data Carousel". Tampere University of Technology. p. 1. http://mad.cs.tut.fi/doc/Analysis_of_the_FLUTE_Data_Carousel_paper.pdf. 
  39. Peltotalo, Jani; Peltotalo, Sami; Harju, Jarmo; Walsh, Rod (June 2007). "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. 
  40. "File Service Protocol (FSP) Frequently Asked Questions v1.1". 19 August 1996. http://www.faqs.org/faqs/fsp-faq/part1/. 
  41. "Common Ports". Red Hat Enterprise Linux 4: Security Guide. Red Hat. 2005. http://web.mit.edu/rhel-doc/4/RH-DOCS/rhel-sg-en-4/ch-ports.html. Retrieved 2018-03-02. 
  42. "openFT v11.0: Setting Up a Connection to Customs (Atlas) with openFT FTAM". Fujitsu. 2010. p. 2. https://sp.ts.fujitsu.com/dmsp/Publications/public/dp-openft-connection-to-customs-atlas-em-en.pdf. 
  43. "The Incredible HULFT – My Favorite B2B Network Protocol". OpenText. 27 August 2009. http://www.gxsblogs.com/keifers/2009/08/the-incredible-hulft-my-favorite-b2b-network-protocol.html. 
  44. "9.4.1. HULFT § Overview". NTT Communications. https://ecl.ntt.com/en/documents/service-descriptions/rsts/hulft/hulft.html#id7. 
  45. "9.4.1. HULFT § HULFT 8 Cipher Option". NTT Communications. https://ecl.ntt.com/en/documents/service-descriptions/rsts/hulft/hulft.html#hulft-8-cipher-option. 
  46. "導入サービス" (in ja). Saison Information Systems. Section: "前提事項、その他". https://www.hulft.com/support/introduce. 
  47. Adamson, Brian; Macker, Joe. "Multicast Dissemination Protocol (MDP) Developer's Guide". United States Naval Research Laboratory. https://downloads.pf.itd.nrl.navy.mil/docs/mdp/MdpDevGuide.html. 
  48. 48.0 48.1 "Multicast Dissemination Protocol History". United States Naval Research Laboratory. https://www.nrl.navy.mil/itd/ncs/products/mdp/history. 
  49. Miller, Kenneth; Robertson, Kary; Tweedly, Alex; White, Marc (April 1998), StarBurst Multicast File Transfer Protocol (MFTP) Specification, IETF, p. 10, I-D miller-mftp-spec-03, https://tools.ietf.org/html/miller-mftp-spec-03, retrieved 2018-02-18 
  50. "StarBurst MFTP Compared to Today's File Transfer Protocols: A White Paper". StarBurst Communications. 1996. https://www.ics.uci.edu/~ejw/hidden/mftp.htm. 
  51. 51.0 51.1 "NACK-Oriented Reliable Multicast (NORM)". United States Naval Research Laboratory. https://www.nrl.navy.mil/itd/ncs/products/norm. 
  52. 52.0 52.1 Adamson, Brian; Bormann, Carsten; Handley, Mark; Macker, Joe (November 2009), NACK-Oriented Reliable Multicast (NORM) Transport Protocol, IETF, doi:10.17487/RFC5740, RFC 5740, https://tools.ietf.org/html/rfc5740, retrieved 2018-02-22 
  53. "Rlogin, RSH, and RCP". http://sourcedaddy.com/networking/rlogin-rsh-and-rcp.html. 
  54. Rescorla, Eric; Schiffman, Allan M. (August 1999), The Secure HyperText Transfer Protocol, IETF, doi:10.17487/RFC2660, RFC 2660, https://tools.ietf.org/html/rfc2660, retrieved 2018-02-20 
  55. "Service Name and Transport Protocol Port Number Registry". Internet Assigned Numbers Authority. 21 February 2018. https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?&page=9. 
  56. Lottor (1984), p. 10
  57. Ylonen, Tatu (10 October 2017). "SFTP - SSH Secure File Transfer Protocol § SFTP Port Number". https://www.ssh.com/ssh/sftp/#sec-SFTP-Port-Number. 
  58. "ITU-T Rec. T.127 (08/2007) Multipoint binary file transfer protocol". International Telecommunication Union. 2008. p. 4. https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.127-200708-I!!PDF-E&type=items. 
  59. "A Primer on the T.120 Series". DataBeam Corporation. 1997. pp. 2, 4. https://www.packetizer.com/ipmc/t120/primer/t120_primer.pdf. 
  60. "T.120: Multipoint Data Conferencing and Real Time Communication Protocols". Network Protocols Handbook (2 ed.). Javvin Technologies. January 2005. p. 137. ISBN 9780974094526. https://books.google.com/books?id=D_GrQa2ZcLwC&pg=PA137. 
  61. Sollins, Karen R. (July 1992), The TFTP Protocol (Revision 2), IETF, doi:10.17487/RFC1350, RFC 1350, https://tools.ietf.org/html/rfc1350, retrieved 2018-02-22 
  62. "Tsunami UDP Protocol – Installation, Setup and Limitations". BluePi Consulting. 13 October 2015. https://www.bluepiit.com/blog/tsunami-udp-protocol-installation-setup-and-limitations/. 
  63. 63.0 63.1 63.2 Tkaczewski, John (18 June 2012). "Open Source Fast File Transfers". FileCatalyst. http://filecatalyst.com/open-source-fast-file-transfers/. 
  64. Valeros Bernardo, Danilo; Hoang, Doan B. (2010). "End-to-End Security Methods for UDT Data Transmissions". International Conference on Future Generation Information Technology. p. 383. doi:10.1007/978-3-642-17569-5_38. ISBN 978-3-642-17569-5. 
  65. 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 2018-02-21.
  66. "Encrypted UDP based FTP with multicast (UFTP)". 7 August 2016. https://wiki.wireshark.org/Protocols/uftp. 
  67. Reifschneider, Sean (8 January 2004). "Mobile Email with UUCP". O'Reilly Media. http://www.onlamp.com/pub/a/onlamp/2004/01/09/uucp.html. 
  68. Ravin, Ed (1996). Using & Managing UUCP (2nd ed.). O'Reilly & Associates. p. 70. ISBN 978-1-56592-153-5. 
  69. WDT RocksDB Dec 16 2016. Laurent Demailly. 23 December 2016. Archived from the original on 2021-12-12. Retrieved 2018-02-23 – via YouTube.
  70. Demailly, Laurent (17 October 2015). "Getting Started with the WDT command line". https://github.com/facebook/wdt/wiki/Getting-Started-with-the-WDT-command-line. 
  71. on GitHub
  72. 72.00 72.01 72.02 72.03 72.04 72.05 72.06 72.07 72.08 72.09 72.10 72.11 72.12 72.13 72.14 72.15 72.16 72.17 72.18 72.19 72.20 72.21 72.22 72.23 72.24 72.25 "Service Name and Transport Protocol Port Number Registry". Internet Assigned Numbers Authority. 28 February 2018. https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt. 
  73. "openFT v11.0: Setting Up a Connection to Customs (Atlas) with openFT FTAM". Fujitsu. 2010. p. 2. https://sp.ts.fujitsu.com/dmsp/Publications/public/dp-openft-connection-to-customs-atlas-em-en.pdf. 
  74. Adamson, Brian; Macker, Joe. "Multicast Dissemination Protocol (MDP) Developer's Guide". United States Naval Research Laboratory. https://downloads.pf.itd.nrl.navy.mil/docs/mdp/MdpDevGuide.html. 
  75. Magidson, Steve (15 May 1989). "Moving Files Can Be a BLAST". UNIX Today! (CMP Media). http://www.birds-of-the-air-press.com/bota/blast/unix_today.pdf. 
  76. da Cruz (1987) p. 3
  77. "OBEX (Object Exchange) Protocol". Infrared Data Association. 2011. http://www.irdajp.org/irdajp.info/obex.html. 
  78. on GitHub
  79. Held, Gilbert (1993). "SeaLink". Mastering PC Communications Software. Van Nostrand Reinhold. p. 74. 
  80. Woggon, Michele (1995). "SeaLink". Telecommunications Using ProComm & ProComm Plus Made Easy. Prentice Hall. p. 34. 
  81. "UUCP protocol internals". http://www.math.utah.edu/docs/info/uucp_5.html#SEC53. 
  82. Lucas, Jay (6 September 1982). "Freeware: Modem lets your computers communicate". InfoWorld (IDG): 53. https://books.google.com/books?id=CDAEAAAAMBAJ&pg=PA53. Retrieved 2018-02-18. 
  83. Glass (1988) p. 87
  84. 84.0 84.1 84.2 Glass (1988) p. 89
  85. Boswell, Peter (2007). How XModem, XModem CRC, and WXModem work. http://www.zoklet.net/totse/en/technology/telecommunications/wxmodem.html. 
  86. Magidson, Steve (15 May 1989). "Moving Files Can Be a BLAST". UNIX Today! (CMP Media). http://www.birds-of-the-air-press.com/bota/blast/unix_today.pdf. 
  87. da Cruz (1987) pp. 234, 253, 307
  88. Wells, Nicholas (2003). "Using UUCP for Remote Access". Guide to Linux Installation and Administration. Course Technology. p. 140. ISBN 978-0-619-00094-3. https://books.google.com/books?id=jQE-iUCjUKAC&pg=PA140. 
  89. Taylor, Ian Lance. "UUCP 'g' Protocol". The FreeBSD Project. https://docs.freebsd.org/info/uucp/uucp.info.g_Protocol.html. 

References

Further reading




Licensed under CC BY-SA 3.0 | Source: https://handwiki.org/wiki/Software:Comparison_of_file_transfer_protocols
1 | Status: cached on August 26 2024 18:38:49
↧ Download this article as ZWI file
Encyclosphere.org EncycloReader is supported by the EncyclosphereKSF