Comparison of file transfer protocols: Difference between revisions

Content deleted Content added
QuaTaC (talk | contribs)
m Change "OFTP2" to "Proposed Standard"; From IETF Datatracker: "This RFC was published on the Independent Submission stream. This RFC is not endorsed by the IETF and has no formal standing in the IETF standards process."
Bender the Bot (talk | contribs)
m Overview: HTTP to HTTPS for SourceForge
 
(6 intermediate revisions by 4 users not shown)
Line 29:
| style="text-align:left" | [[CCSDS File Delivery Protocol]] || [[CCSDS File Delivery Protocol|CFDP]] || || 2002|| {{n/a}} || {{operational|[[ISO]] [https://www.iso.org/standard/43829.html 17355:2007 (v4)]<br/>[[CCSDS]] [https://public.ccsds.org/Pubs/727x0b5.pdf 727.0-B-5]}} ||
|-
| style="text-align:left" | [[Cross File Transfer]] || [[Cross File Transfer|CFT]] || || || {{n/a}} || {{nonpartisan|No}} ||
|-
| style="text-align:left" | [[Ether File Transfer Protocol]] || [[EFTP]] || [[John Shoch]] || 1979 || [[PARC Universal Packet]] || {{nonpartisan|No}} || <ref>{{cite book |title=EFTP: A PUP-based Ether File Transfer Protocol |last=Shoch |first=John |author-link=John Shoch |year=1979}}</ref><ref>{{cite book |title=A Relational Approach to Monitoring Complex Systems |last=Snodgrass |first=Richard |author-link=Richard T. Snodgrass |date=December 1982 |pages=[https://archive.org/details/DTIC_ADA125988/page/n129 119], 149 |url=https://archive.org/details/DTIC_ADA125988 |access-date=2018-03-03}}</ref>
Line 45:
| style="text-align:left" | [[FTP Secure]] || [[FTPS]] || [[Internet Society]] || 1997 || Internet protocol suite || {{partial|{{IETF RFC|2228|4217}}}} || <ref>{{cite IETF |title=FTP Security Extensions |rfc=2228 |last=Horowitz |first=M. |last2=Lunt |first2=S. |date=October 1997 |publisher=[[Internet Engineering Task Force|IETF]] |accessdate=2018-03-03}}</ref><ref>{{cite IETF |title=Securing FTP with TLS |rfc=4217 |last=Ford-Hutchinson |first=Paul |date=October 2005 |publisher=[[Internet Engineering Task Force|IETF]] |accessdate=2018-03-03}}</ref>
|-
| style="text-align:left" | [[HTTP Secure]] || [[HTTPS]] || [[Taher Elgamal]] et al. || 1995 || Internet protocol suite || {{partialya|text={{IETF RFC|72309110}}}} || <ref>{{cite magazine |title=Secure Sockets Layer |last=Sliwa |first=Carol |date=31 May 1999 |magazine=[[Computerworld]] |access-date=2018-03-01 |page=69 |via=Google Books |url=https://books.google.com/books?id=KQMeZfQuVxoC&pg=PT37}}</ref><ref>{{cite IETF |title=The SSL Protocol |draft=draft-hickman-netscape-ssl-00 |last=Hickman |first=Kipp E. B. |date=April 1995 |publisher=[[Internet Engineering Task Force|IETF]] |accessdate=2018-03-01}}</ref>
|-
| style="text-align:left" | Host Unix Linkage File Transfer || HULFT || {{dunno}} || 1993 || {{n/a}} || {{nonpartisan|No}} ||
|-
| style="text-align:left" | [[Hypertext Transfer Protocol]] || [[HTTP]] || [[Tim Berners-Lee]] et al. || 1991 || Internet protocol suite || {{partialya|text={{IETF RFC|72319110}}}} || <ref>{{cite web |url=https://www.w3.org/Protocols/HTTP/AsImplemented.html |title= The Original HTTP as defined in 1991 |last=Berners-Lee |first=Tim |author-link=Tim Berners-Lee |website=W3.org |access-date=2018-03-03}}</ref><ref name="Iwaya">{{cite web |url=https://www.howtogeek.com/233383/why-was-80-chosen-as-the-default-http-port-and-443-as-the-default-https-port/ |title=Why was 80 Chosen as the Default HTTP Port and 443 as the Default HTTPS Port? |last=Iwaya |first=Akemi |date=10 November 2015 |website=How-To Geek |access-date=2018-03-03}}</ref>
|-
| style="text-align:left" | [[Micro Transport Protocol]] || [[μTP]] || [[Ludvig Strigeus]], Greg Hazel, [[Stanislav Shalunov]], Arvid Norberg, [[Bram Cohen]] || 2007 || {{n/a}} || {{nonpartisan|No}} || <ref name="Norberg">{{cite web |url=http://bittorrent.org/beps/bep_0029.html |title=uTorrent transport protocol |last=Norberg |first=Arvid |date=22 June 2009 |website=BitTorrent.org |access-date=2018-03-10}}</ref><ref>{{cite web |url=https://www.slideshare.net/eCommConf/eric-klinker-presentation-at-emerging-communication-conference-awards-2010-america/11 |title=Eric Klinker Presentation at Emerging Communication Conference & Awards 2010 America § Status of uTP |last=Klinker |first=Eric |date=16 May 2010 |publisher=eCommConf |access-date=2018-03-10}}</ref>
Line 73:
| style="text-align:left" | [[Simple Asynchronous File Transfer]] || [[Simple Asynchronous File Transfer|SAFT]] || Ulli Horlacher || 1995 || {{n/a}} || {{nonpartisan|No}} || <ref name="fex">{{cite web |url=https://fex.belwue.de/saft/ |title=SAFT / sendfile |last=Horlacher |first=Ulli |website=fex.belwue.de |access-date=2018-03-03}}</ref><ref name="sendfile">{{cite web |url=http://manpages.org/sendfile |title=sendfile(1) |last=Horlacher |first=Ulli |website=manpages.org |access-date=2018-03-03}}</ref>
|-
| style="text-align:left" | [[Simple File Transfer Protocol]] || [[Simple File Transfer Protocol|SFTP]] || Mark K. Lottor || 1984 || {{n/a}} || {{yapartial|text={{IETF RFC|913}}}} || <ref>Lottor (1984), pp. 1, 13</ref>
|-
| style="text-align:left" | [[SSH file transfer protocol]] || [[SSH file transfer protocol|SFTP]] || Tatu Ylönen || {{sort|1997|c. 1997}} || Secure Shell || {{partial failure|[https://tools.ietf.org/html/draft-ietf-secsh-filexfer-13 IETF Draft] {{small|(2006)}}}} || <ref>{{cite mailing list |url=ftp://ftp.ietf.org/ietf-mail-archive/secsh/2012-09.mail |title=Re: where are SFTP v0 - 2 defined? |date=30 September 2012 |access-date=9 March 2018 |mailing-list=secsh |last=Ylönen |first=Tatu |quote=I designed and implemented the original SFTP protocol for SSH 2.0 back around 1997. Sami Lehtinen did further development on it.{{pb}}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). }}{{Dead link|date=December 2023 |bot=InternetArchiveBot |fix-attempted=yes }}</ref>
Line 81:
| style="text-align:left" | [[Trivial File Transfer Protocol]] || [[TFTP]] || [[Noel Chiappa]] || 1980 || Internet protocol suite || {{ya|text={{IETF RFC|1350}}}} || <ref>{{cite IETF |title=The TFTP Protocol |ien=133 |last=Sollins |first=Karen R. |date=January 1980 |publisher=[[Internet Engineering Task Force|IETF]] |accessdate=2018-02-24}}</ref>
|-
| style="text-align:left" | [[Tsunami UDP Protocol]] || [[Tsunami UDP Protocol|Tsunami]] || Mark Meiss et al. || 2002 || {{n/a}} || {{nonpartisan|No}} || <ref>{{cite web |url=httphttps://tsunami-udp.sourceforge.net/ |title=Tsunami UDP Protocol |last=Wagner |first=Jan |website=tsunami-udp.sourceforge.net |publisher=Jon Wagner |via=SourceForge}}</ref><ref>{{cite web |url=http://anml.iu.edu/research.shtml?prim=lab_research |title=Research |archive-url=https://web.archive.org/web/20100729055331/http://anml.iu.edu/research.shtml?prim=lab_research |at=Section: "Tsunami" |website=anml.iu.edu |publisher=Pervasive Technology Labs at [[Indiana University]] |archive-date=2010-07-29}}</ref>
|-
| style="text-align:left" | [[Tus open protocol for resumable file uploads]] || [[Tus open protocol for resumable file uploads|tus]] || Felix Geisendörfer, Marius Kleidl et al. || 2014 || {{n/a}} || {{nonpartisan|No}} || <ref name="github">{{GitHub|tus/tus-resumable-upload-protocol/blob/master/protocol.md}}</ref><ref name="tusio">{{cite web |url=https://tus.io |title=tus - resumable file uploads}}</ref>
Line 87:
| style="text-align:left" | [[UDP-based Data Transfer Protocol]] || [[UDP-based Data Transfer Protocol|UDT]] || Yunhong Gu || 2004 || {{n/a}} || {{nonpartisan|No}} ||
|-
| style="text-align:left" | [[UDP-based File Transfer Protocol]] || [[UFTP]] || Dennis Bush || 2001 || {{n/a}} || {{nonpartisan|No}} || <ref name="UFTP changes">{{cite web |url=httphttps://uftp-multicast.sourceforge.net/Changes.txt |title=Changes |website=uftp-multicast.sourceforge.net |last=Bush |first=Dennis |publisher=Dennis Bush |via=SourceForge |access-date=2018-03-09}}</ref>
|-
| style="text-align:left" | [[Unix-to-Unix Copy]] || [[UUCP]] || [[Mike Lesk]] || 1979 || {{n/a}} || {{nonpartisan|No}} ||
Line 106:
| style="text-align:left" | CCSDS File Delivery Protocol (CFDP) || {{None}} || {{yes}} || {{no}} || {{no}} ||
|-
| style="text-align:left" | [[Cross File Transfer]] ([[Cross File Transfer|CFT]]) || {{ya|text=[[Transport Layer Security|TLS]] / [[Secure Sockets Layer|SSL]]}} || || || || {{yes}} <ref name="Axway Software">{{cite web |url=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 |title=Transfer CFT 3.2.4 Users Guide § Configuring Transfer CFT |website=Axway.com |publisher=[[Axway Software]] |access-date=2018-02-18 |archive-url=https://web.archive.org/web/20180219090305/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 |archive-date=19 February 2018 |url-status=dead }}</ref><ref name="docs.axway.com">{{cite web |url=https://docs.axway.com/bundle/Transfer_CFT_322_UsersGuide_LocalAdministration_allOS_en_HTML5/page/Content/architecture/intro_security.htm#Transport_Security |title=Transfer CFT 3.2.2 Local Administration Guide § Transport Security |website=Axway.com |publisher=[[Axway Software]] |access-date=2018-02-22}}</ref>
|-
| style="text-align:left" | [[Ether File Transfer Protocol]] ([[EFTP]]) || {{n/a|None}} || {{dunno}} || {{no}} || {{no}} || <ref>{{cite web |url=http://xeroxalto.computerhistory.org/Indigo/Spruce/documents/PrintingAtParc.dm!1_/.appprinting.bravo.html |title=Printing at PARC—Appendix: Glossary of Terms § EFTP |quote=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. |date=4 August 1978 |access-date=2018-03-03}}</ref>
Line 188:
! scope="col" | [[Server (computing)|Server]] !! scope="col" | [[Client (computing)|Client]] !! scope="col" | [[Transport layer|Transport]]
|-
| style="text-align:left" colspan="2" | [[Background Intelligent Transfer Service|BITS]] || 80/443{{efn|When used with HTTP/HTTPS, configurable}} / 137-139137–139{{efn|When used with SMB}} || || TCP / UDP || || || || {{no}} || {{n/a}} ||
|-
| style="text-align:left" colspan="2" | [[BitTorrent]] || 6881{{efn|name=BT_port}} || 6881 || TCP || 6881 || 6881 || TCP || {{no}} || {{n/a}} || <ref name="IANA">{{cite web |url=https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt |title=Service Name and Transport Protocol Port Number Registry |date=28 February 2018 |website=IANA.org |publisher=[[Internet Assigned Numbers Authority]] |access-date=2018-03-17}}</ref>
Line 194:
| style="text-align:left" colspan="2" | [[CCSDS File Delivery Protocol]] ([[CCSDS File Delivery Protocol|CFDP]]) || || || || || || || || ||
|-
| style="text-align:left" colspan="2" | [[Cross File Transfer]] ([[Cross File Transfer|CFT]]) || 1761{{efn|name=i}} || || TCP / [[X.25]] || || || || || <ref name="Axway Software"/><ref name="docs.axway.com"/> ||
|-
| style="text-align:left" colspan="2" | [[Ether File Transfer Protocol]] ([[EFTP]]) || {{n/a}} || {{n/a}} || {{n/a|None}} || {{n/a}} || {{n/a}} || {{n/a|None}} || {{n/a}} || {{n/a}} ||
Line 331:
| style="text-align:left" | [[BiModem]] || || || || || {{yes}} || ||
|-
| style="text-align:left" | [[BLAST (protocol)|BLAST]] || 84 - 102484–1024+ || [[Run-length encoding|RLE]] || [[Cyclic redundancy check|CRC]] || {{yes}} || {{yes}} || {{yes}} || <ref>{{cite news |url=http://www.birds-of-the-air-press.com/bota/blast/unix_today.pdf |title=Moving Files Can Be a BLAST |last=Magidson |first=Steve |date=15 May 1989 |newspaper=UNIX Today! |publisher=CMP Media |access-date=2018-02-18}}</ref>
|-
| style="text-align:left" | [[C-MODEM]] || 32–4096 || || CRC || {{yes}} || ||
|-
| style="text-align:left" | [[B protocol]] || 128–2048 || || CRC32CRC-32 / CRC16CRC-16 / 8-bit checksum || {{yes}} || || {{yes}} ||
|-
| style="text-align:left" | [[JMODEM]] || 64–8192 || [[Run-length encoding|RLE]] || || || ||
|-
| style="text-align:left" | [[HS/Link]] || || || [[CRC32CRC-32]] || {{yes}} || {{yes}} || ||
|-
| style="text-align:left" | [[Kermit (protocol)|Kermit]] || ≤9024 (negotiated) || [[Run-length encoding|RLE]] (run length encoding, negotiated) || [[Checksum]] or [[CRC16CRC-16]] (negotiated) || {{yes}} (binary files only, negotiated) || {{no}} || {{optional|Over [[full-duplex]] only (negotiated)}} || <ref>da Cruz (1987) pp. [https://books.google.com/books?id=_FEvBQAAQBAJ&pg=PA234 234], [https://books.google.com/books?id=_FEvBQAAQBAJ&pg=PA253 253], [https://books.google.com/books?id=_FEvBQAAQBAJ&pg=PA307 307]</ref>
|-
| style="text-align:left" | LeechModem || || || || || || ||
|-
| style="text-align:left" | [[Lynx (protocol)|Lynx]] || || RLE || CRC32CRC-32 || {{yes}} || || ||
|-
| style="text-align:left" | [[NMODEM]] || 2048 || || || || || ||
Line 367:
| style="text-align:left" | [[WXMODEM]] || ≤512 || || || || || {{yes}} ||
|-
| style="text-align:left" | [[YMODEM]] || 1024 || {{no}} || [[CRC16CRC-16]] || || || ||
|-
| style="text-align:left" | [[ZMax]] || ≤~32,768 || || CRC32CRC-32 || || || ||
|-
| style="text-align:left" | [[ZMODEM]] || 256 / 1024 || {{no}} || CRC32CRC-32 || {{yes}} || || {{yes}} ||
|}