3 ms·
I wonder why client and server software needs to opt-in to TFO and it isn't just handled transparently by the kernel? Perhaps with a sysctl flag to enable or d
by rwmj 5y ago
I wonder why client and server software needs to opt-in to TFO and it isn't just handled transparently by the kernel? Perhaps with a sysctl flag to enable or disable it globally.
- mkj 5y agoThere's a chance of a server receiving duplicate data from SYN packets, which some applications won't tolerate. https://datatracker.ietf.org/doc/html/rfc7413#section-2.1 https://datatracker.ietf.org/doc/html/rfc7413#section-2.1 There are some extra tcp_fastopen sysctl values that do enable it transparently.
- caf 5y agoOn the client side, unless the client knows about TFO it's not going to be set up to send data with the initial connection - it's going to use the standard BSD sockets flow of connect(); send();. To usefully use TFO you need to replace the connect() with a sendto() using MSG_FASTOPEN that requests sending of the data you want to send with the SYN.
- caf 5y agoIt occurs to me that using TFO effectively with a TLS library like OpenSSL would be difficult.