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

[Michael Scharf <[e-mail]>]

Hi Adam,

On Tue, 15 Jul 2008 at 14:15:13, Adam Langley wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Data could *always* come in the SYN/ACK (i.e., in a SYN), but often it's
> > just ignored. So this option is just a hint to the server that the
> > client won't ignore that data. It doesn't change any rules about data
> > delivery; once the SYN/ACK arrives, the client can send that data up to
> > the user as per conventional rules, AFAICT.
> 
> Although I've not tested it, I suspect that you're correct here. I
> should reword that section of the draft.

sorry for asking once again "stupid" questions: Wouldn't it be a
simple solution if the server just sent the data in a normal packet
immediately after the SYN/ACK?

The resulting sequence would be:

  Client     Server
   ------SYN---->
   <---SYN/ACK---
   <====Data=====
   ------ACK---->

I think that this would be compliant to RFC 793. I would also expect
that many clients would accept this data packet if it arrives after
the SYN/ACK, i. e., if there is no reordering. This could also save
one RTT of latency, and the overhead of one packet would not be that
large.

Do I miss something?

Michael
_______________________________________________
tcpm mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/tcpm