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, skipping that way 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.
The TFO proposal was originally presented in 2011[2] and was, as of February 2012[update], an IETF Internet Draft.[3] The specification was published as RFC 7413 in December 2014.[4] 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,[4] opening a path for vulnerabilities and failing to gain traction.
TFO implementations include the following:
- IPv4 support for TFO was merged into the Linux kernel mainline in kernel versions 3.6 (support for clients) and 3.7 (support for servers),[5][6] and was turned on by default in kernel version 3.13.[7] TFO support for IPv6 servers was merged in kernel version 3.16.[8]
- Google Chrome and Chromium browsers have support for TFO on Linux, including Chrome OS and Android.
- Apple's iOS 9 and OS X 10.11 both support TCP Fast Open, but it is not enabled for individual connections by default.[9]
- Microsoft Edge supports TCP Fast Open since Windows 10 Preview build 14352.[10]
See also
References
- ^ Kerrisk, Michael (2012-08-01). "TCP Fast Open: expediting web services". LWN.net.
- ^ Radhakrishnan S, Cheng Y, Chu J, Jain A, Raghavan B (2011-12-06). "TCP Fast Open" (PDF). ACM CoNEXT.
- ^ Cheng Y, Chu J, Radhakrishnan S, Jain A (2013-01-26). TCP Fast Open. IETF. I-D draft-ietf-tcpm-fastopen-06.
{{citation}}: CS1 maint: multiple names: authors list (link) - ^ a b Yuchung Cheng; Jerry Chu; Sivasankar Radhakrishnan; Arvind Jain (December 2014). "TCP Fast Open". IETF. Retrieved 10 January 2015.
{{cite web}}: Unknown parameter|last-author-amp=ignored (|name-list-style=suggested) (help) - ^ Kerrisk, Michael (2012-08-01). "TCP Fast Open: expediting web services". LWN.net.
The client-side support has been merged for Linux 3.6
- ^ 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
- ^ "Linux Kernel 3.13, Section 1.10. TCP Fast Open enabled by default". kernelnewbies.org. 19 January 2014. Retrieved 11 February 2014.
- ^ "Linux Kernel 3.16, Section 1.4. TCP Fast Open server mode on IPv6 support". kernelnewbies.org. 3 August 2014. Retrieved 14 September 2014.
- ^ "Your App and Next Generation Networks". Apple Inc. 2015.
- ^ "Windows 10 build 14352 - New web platform features". Microsoft. Retrieved 2016-05-27.
External links
- RFC 7413 specification
 | This computer networking article is a stub. You can help Wikipedia by expanding it. |