Content deleted Content added
No edit summary |
m clean up, fmt |
||
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]],{{
==Security{{
FASP has built-in security mechanisms that do not affect the transmission speed. The [[encryption]] [[
The data is encrypted or decrypted immediately before sending and receiving with the [[Advanced Encryption Standard|AES-128]]. To counteract attacks by monitoring the encrypted information during long transfers, the AES is operated in [[cipher feedback mode]] with a secret [[initialization vector]] for each block. In addition, an integrity check of each [[Block (data storage)|data block]] takes place, in which case, for example, a [[man-in-the-middle attack]] would be noticed.
==Protocol==
FASP's control [[port (computer networking)|port]] is TCP port 22{{snd}} 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
* [[Tsunami UDP Protocol]]
* [[UDP-based Data Transfer Protocol|UDP-based Data Transfer Protocol (UDT)]]
|