On 28-nov-04, at 20:56, Cliff Albert wrote:
I am looking from a RIPE point of view. Lately I see ISPs popping out of the ground requesting ASNs and having actually only 1 upstream (there are 2 upstreams in the routing database, but in the real world there is only 1 upstream).
RIPE wants to see (email) contact info for two peers / upstreams. AS numbers are invariably easier than getting IP addresses. (Except IPv6 address blocks, those have the fastest turnaround of any type of request, but you have to include a network diagram.)
RIPE checks new ASN assignments after 6 months for evidence of adherence to the rules. I've personally seen this happen for a customer ASN.
This is good, but it should also happen for ASN's that are already active. An check for active use of the ASN and conforming to the current rules every 6 months should be a nice thing.
Good luck trying to get those AS numbers back when they are ok by the rules as per the assignment, just not the current ones. This kind of stuff is why parents want their kids to go to law school. Reclaiming AS numbers is a waste of time. We need to move beyond 16 bits at some point anyway. 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.