[180693] in North American Network Operators' Group
Re: Routing Insecurity (Re: BGP in the Washington Post)
daemon@ATHENA.MIT.EDU (Valdis.Kletnieks@vt.edu)
Tue Jun 9 21:29:13 2015
X-Original-To: nanog@nanog.org
To: nanog@nanog.org
In-Reply-To: Your message of "Tue, 09 Jun 2015 21:19:23 -0400."
<39758.1433899163@turing-police.cc.vt.edu>
From: Valdis.Kletnieks@vt.edu
Date: Tue, 09 Jun 2015 21:29:05 -0400
Errors-To: nanog-bounces@nanog.org
--==_Exmh_1433899745_28792P
Content-Type: text/plain; charset=us-ascii
On Tue, 09 Jun 2015 21:19:23 -0400, Valdis.Kletnieks@vt.edu said:
> Didn't we have a very amusing afternoon a number of years ago when $VENDOR
> did exactly that with some invalid routing data? Or am I mis-remembering
> history, and therefor doomed to mis-repeat it?
Actually, it was collusion. $VENDOR-A forwarded the bad data all over, and every
$VENDOR-B router that saw it went walkies...
It's the memory that goes first. I can't remember what goes second....
--==_Exmh_1433899745_28792P
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Exmh version 2.5 07/13/2001
iQIVAwUBVXeS4AdmEQWDXROgAQLv/Q/9GngU4TSrAt2zhKROiWpspgkzXG+1nxIO
0+lfuks/DVprB9YxTNdCU7DIGnAhjg0r1dToEHo4LRvpfJx7VjiPXfjGu6PsFDRl
LMggf0JURYslrKPIs2rNnjXzBkfTS3fDZFp84bS2BnddxAXLnYjyCRfW1mcH05Ab
1tDjyklA394xezjDg4klCHe7caub+fT3/eLDL03McL5v08XJR8LIMwWR8huDfsP4
6tEx+eYlmphw5bbcyxVGWvdb5kDG9bqTipDEox55VAgg3jjyhk19QyRYx5b5ZXxD
VjytI5ZsklUo9Qg9ArFnMHqN2C7F8uOfK6lejUkAEvFI8uLdB/V7MIqiy1ltu2BP
DO4T6vjZDXmc0195jQPwylhgYR+EqZGBj23mwu9tltBM4YJHPP3H7nx361eczZXx
dlT8laX35ChyX5ltxO6MQigLd9rGr8h+OJg+D0JDkeN1O98O1O+nQznCzD230KYS
bvzfZ6bjZ9rTWaae6S+EMZo9+TcmLxcVC7Kr/Nj15eCS7fPQe9KxjSIPA/KKjUAx
w0CDGyA1jAgivU/Fb8AxUm7gCdb+SMCjo5cmyP5FK1TU7eqeWaSiltCrq5SJwtQE
GrtJp2xrJcUdFAyR/IpDi/jf1F1rY2/x1Ss9CNBUzbswr02sCPDfd/jmIiEUZbxP
i1ZHJWD9gd8=
=mZEV
-----END PGP SIGNATURE-----
--==_Exmh_1433899745_28792P--
