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

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

Adam Langley wrote:
> On Fri, Aug 15, 2008 at 4:09 AM, Anders Waldenborg <anders@0x63.nu> wrote:
>> Doesn't SA payloads open up for DoS-amplification (attacker would send SYN
>> packets to your SMTP server with spoofed source address to send more data to
>> victim then would be possible by sending them directly to victim)?
> 
> It's certainly a consideration, which is why the draft recommended
> that 64 bytes be the maximum payload size. At this size there are more
> juicy targets for amplification, like DNS servers.

FWIW, since this is payload data, the size of the data is an
implementation detail - unless, as I've noted, you're changing the
semantics of TCP from a byte stream to delineated messages.

(yes, you're already changing the semantics from one where connection
info is available only after TWHS to one that allows info to be used by
the app before the TWHS completes, which is a different issue)

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

iEYEARECAAYFAkilsAMACgkQE5f5cImnZrukEgCgmJ8EMS2Ok5wrxzMl9IpziV9w
tGgAnj2Lc1kNceJVbamjJvUMnP21TRzH
=G70K
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm