[lir-wg] AS Number Policy

On Tue, 16 Jul 2002, Wolfgang Tremmel, WT5-RIPE wrote:

>> It should be *very* easy for RIPE to produce a list of AS numbers
>> assigned and not in the routing tables (of course only for the RIPE
>> area)

Kinda out of topic, but still wondering - I just downloaded:

ftp://ftp.ripe.net/ripe/dbase/split/ripe.db.aut-num.gz

Now, I know that unassigned AS numbers hanging around in the routing tables
are nothing new. However, if they are properly registered within RIPE DB
and noone notices the forgery - that's worrying:

After processing it I've got the list of 5656 AS numbers assigned by RIPE
NCC (not that difficult, agree). However, the list contacts two very
interesting entries: AS55000 and AS55555! IANA-reserved ASN range!

Let's examine the first one - it has an aut-num, route object and a proper
route in the global routing table. Appears to be single-homed.

aut-num:      AS55000
as-name:      MIPT-NET
descr:        MIPT-TELECOM-NET
[snip]

route:        81.5.64.0/20
descr:        MIPT-TELECOM-NET
origin:       AS55000
[snip]

* i81.5.64.0/20     134.222.249.118                80     50 3561 8342 8342 8810 8810 5467 55000 i

The other one was a bit more "honest" - they admitted they are "fake" and
they don't pollute the global routing table. They also don't have any route
objects. Still, an ugly entry exists in the RIPE DB:

aut-num:      AS55555
as-name:      AS55555
descr:        fake AS
descr:        Kiev, Ukraine
[snip]

Are we going to stick with the rule that RIPE NCC people cannot modify the
RIPE DB and tolerate the offenders? Just wondering ...

Regards,
Beri