[119594] in North American Network Operators' Group
Re: Who has AS 1712?
daemon@ATHENA.MIT.EDU (Justin Shore)
Tue Nov 24 16:01:48 2009
Date: Tue, 24 Nov 2009 14:58:07 -0600
From: Justin Shore <justin@justinshore.com>
To: Hank Nussbacher <hank@efes.iucc.ac.il>
In-Reply-To: <5.1.0.14.2.20091124113919.00c47098@efes.iucc.ac.il>
Cc: Daniel Karrenberg <daniel.karrenberg@ripe.net>, nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Hank Nussbacher wrote:
> At 18:29 24/11/2009 +0900, Randy Bush wrote:
>> > RIS Routing History for AS1712 since 2001:
>>
>> on what date was AS1712 assigned to the current RIPE holder?
>
> Based on:
> ftp://ftp.ripe.net/pub/stats/ripencc/delegated-ripencc-latest
> it doesn't show AS1712 ever being allocated to Renater (probably why the
> inter-RIR mistake happened) but the surrounding ASNs give you an idea of
> the timeframe:
>
> ripencc|IL|asn|1680|1|19930901|allocated
> ripencc|EU|asn|1707|1|19930901|allocated
> ripencc|EU|asn|1729|1|19930901|allocated
> ripencc|EU|asn|1732|1|19930901|allocated
Since IANA says that the ASN is ARIN's to assign wouldn't that preclude
another RIR from assigning it?
http://www.iana.org/assignments/as-numbers/
Of course if it was already assigned when IANA said that (no dates on
the link above) then maybe the fault is more IANA's for telling another
RIR that they could allocate an ASN that another RIR already allocated.
Who knows. It should be an interesting one to watch play out though.
Justin
