[120250] in North American Network Operators' Group
Re: More ASN collissions
daemon@ATHENA.MIT.EDU (Rene Wilhelm)
Sun Dec 13 19:27:40 2009
Date: Mon, 14 Dec 2009 01:26:45 +0100
From: Rene Wilhelm <wilhelm@ripe.net>
To: Florian Weimer <fweimer@bfk.de>
In-Reply-To: <82638dhn8l.fsf@mid.bfk.de>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Florian Weimer wrote:
> * Rene Wilhelm:
>
>> AS3745 is not a duplicate ASN assignment either. Like AS35868 the entry at
>> whois.ripe.net is a user created object in the RIPE routing registry, not
>> an assignment by RIPE NCC.
>
> How can you tell one from the other? Is the lack of an org: attribute
> reliable?
>
The info is in the as-block object which whois.ripe.net returns in
addition to the
aut-num object when you do a default query for an AS number.
For example for as43210 you get this:
as-block: AS43008 - AS44031
descr: RIPE NCC ASN block
remarks: These AS Numbers are further assigned to network
remarks: operators in the RIPE NCC service region. AS
remarks: assignment policy is documented in:
remarks: <http://www.ripe.net/ripe/docs/asn-assignment.html>
remarks: RIPE NCC members can request AS Numbers using the
remarks: form available in the LIR Portal or at:
remarks: <http://www.ripe.net/ripe/docs/asnrequestform.html>
org: ORG-NCC1-RIPE
admin-c: CREW-RIPE
tech-c: RD132-RIPE
mnt-by: RIPE-DBM-MNT
mnt-lower: RIPE-NCC-HM-MNT
source: RIPE # Filtered
[...]
Only AS numbers which are covered by "RIPE NCC ASN blocks" have been
assigned by RIPE NCC or transferred to RIPE NCC (like AS1707).
-- Rene
