[119619] in North American Network Operators' Group
Re: Who has AS 1712?
daemon@ATHENA.MIT.EDU (Jon Lewis)
Wed Nov 25 00:10:34 2009
Date: Wed, 25 Nov 2009 00:08:52 -0500 (EST)
From: Jon Lewis <jlewis@lewis.org>
To: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <EB512968-753D-4838-9196-D978D78D2A23@hopcount.ca>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Tue, 24 Nov 2009, Joe Abley wrote:
>
> On 2009-11-23, at 21:32, Jon Lewis wrote:
>
>> Checking "global BGP" only works if the ASN is being announced at that instant.
>
> How do you announce an ASN?
Ok...bad wording. s/announced/used to announce or propagate one or more
routes/
> Are you suggesting that I should be able to block the assignment of
> particular ASNs by simply including them in an AS_PATH attribute on a
> route I originate, and making sure that route shows up in route-views?
No...but that would hopefully be cause for further investigation before an
ASN is assigned.
With multiple orgs assigning from the same small pool of numbers, and an
early history of, shall we say, incomplete record keeping, a little extra
caution could avoid a lot of pain.
I would hope the number of orgs that would pollute the global table with
bogus AS Paths for the purpose of making more work for
ARIN/RIPE/APNIC/etc. is not very large. If you want to announce certain
routes with "bogus" AS Paths to keep certain networks from seeing them,
that's one thing, but why would you do this with ASNs not currently
assigned?
----------------------------------------------------------------------
Jon Lewis | I route
Senior Network Engineer | therefore you are
Atlantic Net |
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
