[120092] in North American Network Operators' Group
Followup regarding Joint Statement on ASN Assignment Discrepancies
daemon@ATHENA.MIT.EDU (John Curran)
Wed Dec 9 12:52:00 2009
From: John Curran <jcurran@arin.net>
To: "nanog@nanog.org" <nanog@nanog.org>
Date: Wed, 9 Dec 2009 12:51:09 -0500
In-Reply-To: <AE013B1B-35F8-4402-A7D3-4DB111542CFB@arin.net>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
ARIN would like to report that it has worked with all its customers who rec=
eived ASNs from the AS1707-AS1726 range and has provided them with replacem=
ent ASNs. =20
Additionally, ARIN is now checking the other RIR databases and global routi=
ng tables just prior to issuance of any number resources (ASNs or IP addres=
s blocks) to ensure that there are no conflicts in issued resources.
FYI,
/John
John Curran
President and CEO
ARIN
On Nov 26, 2009, at 11:31 AM, John Curran wrote:
> ARIN and the RIPE NCC have worked together to research the issues with
> the Autonomous System Number (ASN) range AS1707-AS1726. Below is our
> analysis of what happened and a plan to resolve these issues.
>=20
> It appears that prior to 1993, Renater was issued AS1707 with an AS
> name of "ASNBLOCKA". This is the name format used to assign a block
> of ASNs, but the DDN NIC (the Defense Data Network Network Information
> Center, which was responsible for ASN assignments until 1993) recorded
> only a single assignment of AS1707, rather than the entire block of 20
> ASNs (AS1707-AS1726), as would have been expected. AS1712 was never
> registered in the DDN NIC database.
>=20
> Since the proper registration was never recorded, this mistake carried
> over from the InterNIC database into ARIN's database at ARIN=92s inceptio=
n
> in 1997. The ASN range was not transferred to the RIPE NCC along with
> AS1707 because AS1708-AS1726 appeared to be unassigned, and thus
> remained with ARIN.
>=20
> Because this is simply an error in registry data and Renater is the
> actual registrant of this entire range of ASNs (AS1707-AS1726), ARIN
> will work with its customers who received ASNs from this range in July
> and August of 2009 to provide them with replacement ASNs. While we
> understand that this may cause some difficulty for these customers, we
> feel that this is the best path forward given the circumstances.
>=20
> RIPE NCC and ARIN will update their respective databases and work with
> the IANA to ensure that the ASN registry data is properly updated for
> this range.
>=20
> To prevent future issues, ARIN and RIPE NCC will implement two new
> processes for issuing new ASNs: checking all other RIR databases to
> ensure that the ASN is not previously registered, and checking BGP
> routing tables to ensure the ASN is not already found in an announced
> AS-path. ASNs that fail either of these conditions will not be issued
> until the discrepancy has been addressed.
>=20
> Regards,
> John Curran, President and CEO, ARIN
> Axek Pawlik, Managing Director, RIPE NCC
>=20
