[110653] in North American Network Operators' Group
Re: Anyone notice strange announcements for 174.128.31.0/24
daemon@ATHENA.MIT.EDU (John Payne)
Tue Jan 13 08:56:10 2009
From: John Payne <john@sackheads.org>
To: Paul Wall <pauldotwall@gmail.com>
In-Reply-To: <620fd17c0901122105jacd3aa3jaf88a5302503e52@mail.gmail.com>
Date: Tue, 13 Jan 2009 08:55:40 -0500
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Jan 13, 2009, at 12:05 AM, Paul Wall wrote:
> On Mon, Jan 12, 2009 at 7:29 PM, Leo Bicknell <bicknell@ufp.org>
> wrote:
>> You really should make some friends Randy.
>
> He is, on Second Life.
>
> Seriously though... I've not seen any discussion of the application of
> "allowas-in", a valid neighbor configuration under certain
> topologies/scenarios, as relates to impact today. Also, I'd agree
> announcing other peoples' ASNs, without their permission, is in bad
> form. It's okay he's doing it to you, but I bet Randy would be a lot
> less smiley if you were to announce random paths with 3130.
You should've seen the email storm and panic created when I prepended
an AS to avoid a blackhole. I got the right people interested in
talking to me at least, but boy-o-boy were people confused about what
I was doing.
I guess the problem is that AS PATH is overloaded and people forget
that the primary purpose is loop-avoidance. Everything else is
secondary and much like reading Received headers in SMTP mail, you
really should take everything after your direct neighbor's AS with a
grain of salt.
