Content deleted Content added
mNo edit summary |
|||
Line 1:
[[File:FTP vs Aspera Comparison.webm|thumb|A screencast showing downloading the same file from the European Sequence Read Archive via wget/FTP and ascp/Aspera/FASP
{{IPstack}}
Line 7:
Similar to the [[Connectionless communication|connectionless]] [[User Datagram Protocol|UDP]] protocol, FASP does not expect any feedback on every [[Network packet|packet]] sent. Only the packets marked as really lost must be requested again by the recipient. As a result, it does not suffer as much loss of throughput as [[Transmission Control Protocol|TCP]] does on networks with high [[Latency (engineering)|latency]] or high [[packet loss]].<ref>{{cite web|url=http://downloads.asperasoft.com/en/technology/shortcomings_of_TCP_2/the_shortcomings_of_TCP_file_transfer_2|title=Aspera - High-speed file transfer software -|website=downloads.asperasoft.com}}</ref><ref>{{cite web|url=https://gcn.com/Articles/2014/05/15/FOSE-Data-transfer-protocol.aspx|title=FASP transfer protocol speeds data transmission to the cloud}}</ref>
Large organizations like [[IBM]],{{cn|date=January 2018}}
==Security{{cn|date=July 2018}}==
FASP has built-in security mechanisms that do not affect the transmission speed. The [[encryption]] [[Algorithm|algorithms]] used are based exclusively on [[Open standard|open standards]]. Before the transfer, [[SSH]] is used for [[key exchange]] for [[authentication]]. These randomly generated, one-way keys are discarded at the end of the transmission.
Line 16 ⟶ 15:
==Protocol==
FASP's control [[
▲FASP's control [[Port (computer networking)|Port]] is TCP port 33001 — the same port that SSH uses. For data transfer, it begins at UDP port 33001, which increments with each additional connection thread.<ref name="register"/>
==See Also==
|