Dear Pieterjan d'Hertog,
D'HERTOG Pieterjan wrote:
Look what I discovered in the RIPE DB...
aut-num: AS1 as-name: NETS-AS descr: NetServices Autonomous System Number admin-c: TBNS1-RIPE tech-c: MK2488-RIPE notify: hostmaster@switchworld.nl mnt-lower: NETS-MNT mnt-routes: NETS-MNT mnt-by: NETS-MNT changed: hostmaster@switchworld.nl 20020814 source: RIPE
Should be bbn planet no ?
Well, we're called Genuity now but yes it's our North American ASN. Around Europe we're better known as AS7176.
This ASN space is allocated to ARIN as indicated by the as-block AS1 - AS6. Data in the RIPE Database registered within this block is not authoritative.
Unfortunately at the moment we cannot protect ASN space allocated to ARIN and APNIC as this will make impossible creation of route objects with originating AS from this space. We are working on implementation of cross-registry authorisation in the RIPE Database, which will allow us to lock this space.
Would it be worth registering AS1 correctly in the RIPE db as well as ARIN (and RADB) or will this simply cause confusion?
This aut-num, AS1, should not be in the RIPE Database. We will contact the owners of this object and ask them to delete it.
Many thanks for this, I'll pop the lawyers back in their cage for the moment ;-) Kind regards Matthew