Comparison of file transfer protocols - Biblioteka.sk

Upozornenie: Prezeranie týchto stránok je určené len pre návštevníkov nad 18 rokov!
Zásady ochrany osobných údajov.
Používaním tohto webu súhlasíte s uchovávaním cookies, ktoré slúžia na poskytovanie služieb, nastavenie reklám a analýzu návštevnosti. OK, súhlasím


Panta Rhei Doprava Zadarmo
...
...


A | B | C | D | E | F | G | H | CH | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9

Comparison of file transfer protocols
 ...

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
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 Simu 2007 No [5]
File Delivery over Unidirectional Transport FLUTE Internet Society 2004 RFC 6726 [6]
File Service Protocol FSP Wen-King Su 1991 No [7][8]
File Transfer Access and Management FTAM ISO 8571-4:1988
File Transfer Protocol FTP Abhay Bhushan 1971 Internet protocol suite RFC 959 [9]
FTP Secure FTPS Internet Society 1997 Internet protocol suite RFC 2228, 4217 [10][11]
HTTP Secure HTTPS Taher Elgamal et al. 1995 Internet protocol suite RFC 7230 [12][13]
Host Unix Linkage File Transfer HULFT ? 1993 No
Hypertext Transfer Protocol HTTP Tim Berners-Lee et al. 1991 Internet 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 Protocol MDP No
Multicast File Transfer Protocol MFTP C. Kenneth Miller et al. 1995 IETF Draft (1998) [18]
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 [19]
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) [20]
Reliable Blast UDP RBUDP Eric He et al. 2002 No [21]
Remote copy rcp ? 1982 Internet protocol suite No [22]
Secure copy SCP Tatu Ylönen ? Secure Shell No [23]
Secure Hypertext Transfer Protocol S-HTTP IETF Web Transaction Security Working Group 1999 RFC 2660 [24]
Simple Asynchronous File Transfer SAFT Ulli Horlacher 1995 No [25][26]
Simple File Transfer Protocol SFTP Mark K. Lottor 1984 RFC 913 [27]
SSH file transfer protocol SFTP Tatu Ylönen c. 1997 Secure Shell IETF Draft (2006) [28]
T.127 T.127 ITU[29] 1995 [30] ITU T.127
Trivial File Transfer Protocol TFTP Noel Chiappa 1980 Internet 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 Gu 2004 No
UDP-based File Transfer Protocol UFTP Dennis Bush 2001 No [36]
Unix-to-Unix Copy UUCP Mike Lesk 1979 No
Warp Speed Data Transfer WDT Laurent 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]

Protocol Encryption
(data)
Transfer
resuming
Multicast
capable
Managed Refs
BITS Optional TLS / AES-128[a] Yes No No
BitTorrent None[b] Yes Peer-to-peer No [39][40]
CCSDS File Delivery Protocol (CFDP) Yes No No
Cross File Transfer (CFT) TLS / SSL Yes [41][42]
Ether File Transfer Protocol (EFTP) None ? No No [43]
Fast and Secure Protocol (FASP) AES-256 / AES-192 / AES-128 Yes No [44][45][46]
File Delivery over Unidirectional Transport (FLUTE) Optional/Unspecified[c] No Yes [47][48][49]
File Service Protocol (FSP) None Yes No No [50][51]
File Transfer Access and Management (FTAM) ?[d] [52]
File Transfer Protocol (FTP) None Yes[e] No No [53][54][55][56][57]
FTP Secure (FTPS) TLS / SSL Yes No No
HTTP Secure (HTTPS) TLS / SSL Yes No No [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)
Yes No No [15][64]
Micro Transport Protocol (μTP) None Yes Peer-to-peer No [16]
Multicast Dissemination Protocol (MDP) None Yes Yes [65][66]
Multicast File Transfer Protocol (MFTP) None Yes Yes No [67][68]
NACK-Oriented Reliable Multicast Transport Protocol (NORM) IPsec Yes Yes [69][70]
Odette File Transfer Protocol (OFTP) None Yes [19]
Odette File Transfer Protocol 2 (OFTP2) TLS Yes [20]
Reliable Blast UDP (RBUDP) None No No [21][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 [25][26][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[f] Yes No No [34][35]
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[g] Yes Yes No [83][36][86]
Unix-to-Unix Copy (UUCP) None Some[h] No No [87][88]
Warp Speed Data Transfer (WDT) AES-128 (OFB / CTR) Yes No No [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.

Zdroj:https://en.wikipedia.org?pojem=Comparison_of_file_transfer_protocols
Text je dostupný za podmienok Creative Commons Attribution/Share-Alike License 3.0 Unported; prípadne za ďalších podmienok. Podrobnejšie informácie nájdete na stránke Podmienky použitia.






Text je dostupný za podmienok Creative Commons Attribution/Share-Alike License 3.0 Unported; prípadne za ďalších podmienok.
Podrobnejšie informácie nájdete na stránke Podmienky použitia.

Your browser doesn’t support the object tag.

www.astronomia.sk | www.biologia.sk | www.botanika.sk | www.dejiny.sk | www.economy.sk | www.elektrotechnika.sk | www.estetika.sk | www.farmakologia.sk | www.filozofia.sk | Fyzika | www.futurologia.sk | www.genetika.sk | www.chemia.sk | www.lingvistika.sk | www.politologia.sk | www.psychologia.sk | www.sexuologia.sk | www.sociologia.sk | www.veda.sk I www.zoologia.sk


Protocol Data port Control port Assigned
by IANA
Assignee Refs
Server Client Transport Server Client Transport
BITS 80/443[a] / 137-139[b] TCP / UDP No
BitTorrent 6881[c] 6881 TCP 6881 6881 TCP No [92]
CCSDS File Delivery Protocol (CFDP)
Cross File Transfer (CFT) 1761[d] TCP / X.25 [41][42]
Ether File Transfer Protocol (EFTP) None