TCP Fast Open

In computer networking, TCP Fast Open (TFO) is an extension to speed up the opening of successive Transmission Control Protocol (TCP) connections between two endpoints. It works by using a TFO cookie (a TCP option), which is a cryptographic cookie stored on the client and set upon the initial connection with the server.[1] When the client later reconnects, it sends the initial SYN packet along with the TFO cookie data to authenticate itself. If successful, the server may start sending data to the client even before the reception of the final ACK packet of the three-way handshake, thus skipping a round-trip delay and lowering the latency in the start of data transmission.

The cookie is generated by applying a block cipher keyed on a key held secret by the server to the client's IP address, generating an authentication tag that is difficult for third parties to spoof, even if they can forge a source IP address or make two-way connections to the same server from other IP addresses. Although it uses cryptographic techniques to generate the cookie, TFO is not intended to provide more security than the three-way handshake it replaces, and does not give any form of cryptographic protection to the resulting TCP connection, or provide identity assurance about either endpoint. It also is not intended to be resistant to man-in-the-middle attacks. If such resistance is required, it may be used in combination with a cryptographic protocol such as TLS or IPsec.

History

The TFO proposal was originally presented in 2011[2] and was published as the experimental RFC 7413 in December 2014.[3] TCP Fast Open shares the goal of bypassing the three-way handshake of TCP with an earlier proposal from 1994, called T/TCP (RFC 1644). In contrast to TCP Fast Open, T/TCP paid no attention to security,[3] opening a path for vulnerabilities and failing to gain traction.

Characteristics

TFO implementations include the following:

See also

References
  1. Kerrisk, Michael (2012-08-01). "TCP Fast Open: expediting web services". LWN.net.
  2. Radhakrishnan S, Cheng Y, Chu J, Jain A, Raghavan B (2011-12-06). "TCP Fast Open" (PDF). ACM CoNEXT.
  3. Yuchung Cheng; Jerry Chu; Sivasankar Radhakrishnan & Arvind Jain (December 2014). "TCP Fast Open". IETF. Retrieved 10 January 2015.
  4. Kerrisk, Michael (2012-08-01). "TCP Fast Open: expediting web services". LWN.net. The client-side support has been merged for Linux 3.6
  5. Vaughan-Nichols, Steven J (2012-12-11). "Linux 3.7 arrives, ARM developers rejoice". Linux and Open Source. ZDNet. Linux 3.7. TCP Fast Open will now be supported on servers
  6. "Linux Kernel 3.13, Section 1.10. TCP Fast Open enabled by default". kernelnewbies.org. 19 January 2014. Retrieved 11 February 2014.
  7. "Linux Kernel 3.16, Section 1.4. TCP Fast Open server mode on IPv6 support". kernelnewbies.org. 3 August 2014. Retrieved 14 September 2014.
  8. "Implementation of server-side TCP Fast Open (TFO) [RFC7413]: MFC into stable/10 branch". 2015-12-28.
  9. "This is an implementation of the client side of TCP Fast Open (TFO) [RFC7413]". 2018-02-26.
  10. "Enable TCP_FASTOPEN by default for FreeBSD 12". 2018-06-24.
  11. "1188435 - Support TCP Fast Open". 2017-05-05.
  12. "1398201 - Disable TCP Fast Open for 57". 2017-09-10.
  13. "Exim 4.88 released". 2016-12-25.
  14. "Unbound 1.5.10". Retrieved 2017-12-05.
  15. "Release Notes for BIND Version 9.11.0". 2016-10-05.
  16. "Knot DNS 2.6.0". 2017-09-29.
  17. "Your App and Next Generation Networks". Apple Inc. 2015.
  18. "Windows 10 build 14352 - New web platform features". Microsoft. Retrieved 2016-05-27.
  19. "Changelogs for 4.1.x". PowerDNS. 2017-12-04.
  20. Kelley, Simon (2019-03-10). "Support TCP fastopen on incoming and outgoing connections".
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.