Just to satisfy my curiosity, how did this work (or did it?) with TCP SYN Cookies?
I can imagine a tcp listener which was implementing SYN Cookies only ACKing the initial SYN sequence number and not the data which it discarded, then the application retransmitting that data either on the subsequent ACK or the next data packet. Does that generally just work with most/all tcp implementations on the other side? I suppose it ought to? Gavin On Wed, Jul 27, 2016 at 11:37 PM, Derek Fawcus < [email protected]> wrote: > On Thu, Jul 28, 2016 at 12:24:19am +0100, Derek Fawcus wrote: > > > > Implying that a passive opener which chose to ack such data bytes would > > have to buffer such data until the handshake completes; but I'm not > > aware of any stack which actually works that way. > > Except the old KA9Q NOS, which was tickling my memory... > > It did have the ability to send such SYN data. > > DF > > _______________________________________________ > tcpm mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/tcpm >
_______________________________________________ Tcpinc mailing list [email protected] https://www.ietf.org/mailman/listinfo/tcpinc
