[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
BCP38 [Was: Re: TWC (AS11351) blocking all NTP?]
- Subject: BCP38 [Was: Re: TWC (AS11351) blocking all NTP?]
- From: fergdawgster at mykolab.com (Paul Ferguson)
- Date: Mon, 03 Feb 2014 10:23:03 -0800
- In-reply-to: <CAD6AjGTYMM8TSfSmFSh96OHxW6-HJWTGQsU=2KBxbOGxjM44pQ@mail.gmail.com>
- References: <[email protected]> <[email protected]> <CAD6AjGTYMM8TSfSmFSh96OHxW6-HJWTGQsU=2KBxbOGxjM44pQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 2/2/2014 2:17 PM, Cb B wrote:
> And, i agree bcp38 would help but that was published 14 years ago.
But what? Are you somehow implying that because BCP38 was
"...published 14 years ago" (RFC2267 was initially published in 1998,
and it was subsequently replaced by RFC2827)?
I hope not, because BCP38 filtering would still help stop spoofed
traffic now perpetuating these attacks, 14 years after BCP38 was
published, because spoofing is at the root of this problem
(reflection/amplification attacks).
This horse is not dead, and still deserves a lot of kicking.
$.02,
- - ferg (co-author of BCP38)
- --
Paul Ferguson
VP Threat Intelligence, IID
PGP Public Key ID: 0x54DC85B2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iF4EAREIAAYFAlLv3ocACgkQKJasdVTchbLhowEAuO9DSQiRswVeqpHSccHo060h
cqmIB8XlaNkzEPQw1w0A/0G6cjvtWBiJfwWbWoTY7X3RRMHeN36RkYR+2TonyNBi
=W2wU
-----END PGP SIGNATURE-----