Re: [tcpm] Faster application handshakes with SYN/ACK payloads

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stefanos,

Here's a more brief, self-contained reply:

Joe Touch wrote:
> Hi, Stefanos,
> 
> Stefanos Harhalakis wrote:
>> Hello Adam,
> 
...
>> I believe that this was not proposed before so here it goes:
> 
>> Add a generic 'user data' option for SYN fields that would carry user data. 

There are two reasons for doing this:

	1- to send an out-of-band signal

	2- to send a signal that the server acts on before the
	handshake completes

#2 violates TCP semantics, so the SYN-ACK cannot have application data
that depends on the SYN's user data option (which is the desired result
here). The signal can't be acted on at the application layer until the
handshake completes.

#1 changes TCP semantics as well, since TCP does not have an out-of-band
signal path, and this would add that. However, because it cannot be
acted on until after the handshake completes, it cannot modify
application behavior that isn't required to wait until the handshake
finishes - i.e., apps that can write to the socket before the handshake
completes (e.g., to write data available to a SYN-ACK) would never
change because of this signal. The utility of this feature depends on
application behavior, which cannot be known, and thus cannot be relied upon.

As a result, I cannot see how this feature can be used to extend TCP.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjV684ACgkQE5f5cImnZrubhACbBf4fbf2No0G1LfwUikcLg6+w
njoAn3a9wBkWD5ijcseuD2w/9I3lPyhv
=IjGv
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm