Re: [tcpm] SYN/ACK Payloads, draft 01

["Adam Langley" <agl at imperialviolet.org>]

On Thu, Aug 14, 2008 at 10:44 AM, Caitlin Bestler
<Caitlin.Bestler at neterion.com> wrote:
> And experience has taught me that when something looks really
> bad from a "purely theoretical" viewpoint it merely means that
> I have not yet identified the specific case where it *will*
> cause problems. So at the minimum I like to come up with
> a strong reason why something is intrinsically safe, not
> just "So far, I haven't thought of how it goes wrong."

I haven't been able to think of any case where it goes horribly wrong yet ;)

So, we're considering the case where there are no options in play.
This is a pure implementation trick.

To make it concrete, we have an SMTP server which puts "220
example.com ESMTP\r\n" in the SYN/ACK.

If the client ACKs less than the full payload, we retransmit the
remaining bytes in the next packet.

That's not a strong reason, but I'll ponder how it could go wrong
again tonight. If you think of anything, please do say.


Cheers

AGL

-- 
Adam Langley agl at imperialviolet.org http://www.imperialviolet.org
_______________________________________________
tcpm mailing list
tcpm at ietf.org
https://www.ietf.org/mailman/listinfo/tcpm