Content deleted Content added
m →Protocol: reference added |
→See also: add portal |
||
(5 intermediate revisions by 4 users not shown) | |||
Line 1:
{{Short description|Terminal command scheme used to transfer data}}
{{Infobox networking protocol
[[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]]▼
| title = Fast and Secure Protocol
| logo =
| logo alt =
| image =
| image alt =
| caption =
| is stack = No
| abbreviation = FASP
| purpose = Data transfer
| developer = Michelle C. Munson and Serban Simu
| date = {{Start date and age| | | }}<!--Fill in: Year (4 digits), month and day (2 digits)-->
| based on = [[User Datagram Protocol|UDP]]
| influenced =
| osilayer =
| ports = tcp/22, udp/33001
| rfcs =
| hardware =
}}
▲[[File:FTP vs Aspera Comparison.webm|thumb|A screencast showing downloading the same file from the European Sequence Read Archive via [[wget]]/[[File Transfer Protocol|FTP]] and ascp/Aspera/FASP]]
{{Internet protocol suite|transport=FASP}}
The '''Fast Adaptive and Secure Protocol''' ('''FASP''') is a [[Proprietary software|proprietary]] data transfer [[Communication protocol|protocol]]. FASP is a network-optimized network protocol created by Michelle C. Munson and Serban Simu, productized by [[Aspera (company)|Aspera]], and now owned by [[IBM]] subsequent to its acquisition of Aspera. The associated client/server software packages are also commonly called Aspera.<ref name="register">{{cite web|url=https://www.theregister.co.uk/2015/10/01/aspera/|title=Aspera high speed file transfer: Let the cloud protocol wars begin|website=[[The Register]]}}</ref><ref name="ena">{{cite web|url=https://www.ebi.ac.uk/ena/browse/read-download#downloading_files_aspera|title=European Nucleotide Archive: Downloading using Aspera}}</ref> The technology is [[patented]] under US Patent #8085781, ''Bulk Data Transfer'', #20090063698, ''Method and system for aggregate bandwidth control''.<ref>{{cite web|url=https://
Built upon the [[Connectionless communication|connectionless]] [[User Datagram Protocol|UDP]] protocol, FASP does not expect any feedback on every [[Network packet|packet]] sent, and yet provides fully reliable data transfer over best effort IP networks. 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]] and avoids the overhead of naive "UDP data blaster" protocols.<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> The protocol innovates upon naive "data blaster" protocols through an optimal control-theoretic retransmission algorithm and implementation that achieves maximum [[goodput]] and avoids redundant retransmission of data. Its control model is designed to fill the available bandwidth of the end-to-end path over which the transfer occurs with only "good" and needed data.
Line 12 ⟶ 31:
==Security==
{{Unreferenced section|date=July 2018}}
FASP has built-in security mechanisms that do not affect the transmission speed. The [[encryption]] [[algorithm]]s used are based exclusively on [[open standard]]s. Some product implementation use secure key exchange and authentication such as [[SSH]].
The data is optionally 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 random, public [[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.
Line 24 ⟶ 43:
==See also==
{{Portal|Internet}}
* [[Tsunami UDP Protocol]]
* [[UDP-based Data Transfer Protocol|UDP-based Data Transfer Protocol (UDT)]]
|