[170657] in North American Network Operators' Group
Re: BGPMON Alert Questions
daemon@ATHENA.MIT.EDU (joel jaeggli)
Wed Apr 2 18:22:04 2014
Date: Wed, 02 Apr 2014 15:21:23 -0700
From: joel jaeggli <joelja@bogus.com>
To: "Justin M. Streiner" <streiner@cluebyfour.org>,
"nanog@nanog.org list" <nanog@nanog.org>
In-Reply-To: <Pine.LNX.4.64.1404021453410.8170@whammy.cluebyfour.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--t3e7TjnhM29WFddq1dcbh50TTDgs5BcC9
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
On 4/2/14, 11:59 AM, Justin M. Streiner wrote:
> Two things need to happen:
> 1. Indosat needs to clean their mess up.
> 2. Indosat's upstreams need to apply some BGP clue to Indosat's
> announcements.
>=20
> It's pretty clear that both parties have dropped the ball in a big way,=
> in terms of sane BGP filtering practices.
actually that's no at all clear.
https://twitter.com/renesys/status/451456391656796161
it looked like the filtering worked rather well. certainly as a customer
of many of 4761s transit providers I did not see any of them pick up
this advertisement in asia.
the impact was limited even when it began, and it should be largely over.=
One of the things it says as that this sort of announcement is highly
visible to the monitoring infrastructure, which is rather good to know.
> jms
>=20
--t3e7TjnhM29WFddq1dcbh50TTDgs5BcC9
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlM8jWMACgkQ8AA1q7Z/VrJ5kwCfaq6hipwRHwDY91edE0NthJCK
7OUAn2YDc6pwh6MdeP1IsXmbC+xQo3lU
=BLeY
-----END PGP SIGNATURE-----
--t3e7TjnhM29WFddq1dcbh50TTDgs5BcC9--
