On Sun, Nov 28, 2004 at 11:40:59PM +0100, Iljitsch van Beijnum wrote:
I think it's not. The problem will not go away then, it will just take longer before it appears again. The policies have to get stricter, there is no point in 'fixing' your problems by not fixing the issue that created them in the first place.
Well, how many AS numbers would you like to give out? 30000 in 20 years? 100k a year? A million in a month? 32 bits will then give you 2863 millennia, 429 centuries or 357 years, respectively.
First one should investigate how many ASN's can be recovered. If this is substantial one could probably last current ASN span till 2030.
Oh, and just for fun: tell me if you see AS12945 in your routing table. I can assure you that this AS number was assigned and is still used in full compliance with RIPE policies.
* 195.193.163.0/24 195.69.144.125 12945 I
As you can see there is evidence to substantiate your claim. That you have no route: object and are advertising UUNet space under another ASN to specific peers is something else.
This AS is only visible to around 20 peers. :-) Apparently you're one of them although I have no idea which one. The other peculiarities are to avoid taking up space in the global routing table, which would be more work but provide no benefits.
This has been taken from the BIT looking glass, as this is one of the peers present in the aut-num. As I said before an ASN doesn't have to appear in the global routing table, but there has to be viable evidence of the use of the ASN. -- Cliff Albert <cliff@oisec.net>