Re: [tcpm] WGLC: draft-ietf-tcpm-tcpsecure-10.txt

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

>> IMO, all the recent TCP connection robustness related drafts (port 
>> randomization, ICMP attacks etc.,) should have a reference to TCP
>> secure since most of these drafts were inspired by TCP secure!

Above Ananth is claiming that the recent burst of activity in this space
is due to his draft, though Watson (CanSec West, March 2004) is the
origin of the RST issue in public forums (tcpsecure-00 wasn't out until
April 2004).

Other solutions in this space were Larsen's port-randomisation-00 in
June 2004 (later Larsen and Gont), and Poon's timestamp-00 also in June
2004, though port-randomisation closely parallels Bellovin's ISN
randomization in RFC1948 from 1996. (and port randomization may have
been deployed before 2004 - does anyone recall?)

However, I would be glad to credit Ananth with the large number of
'attacks' on Postel's RFC793 design principle, "be liberal in what you
accept from others" from 1981. ;-)

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

iEYEARECAAYFAki4bGQACgkQE5f5cImnZrs5igCeKhNfbUiHweoYHQTvJDaxn/8L
s7QAoMQvLTK91Nxg95tPnccyYwGULhp9
=Ou+1
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm