[120144] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: More ASN collissions

daemon@ATHENA.MIT.EDU (Dobbins, Roland)
Thu Dec 10 13:52:46 2009

From: "Dobbins, Roland" <rdobbins@arbor.net>
To: NANOG list <nanog@nanog.org>
Date: Thu, 10 Dec 2009 18:51:29 +0000
In-Reply-To: <5D6184FD-CD87-4B5B-B016-504799C5AB70@puck.nether.net>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


On Dec 11, 2009, at 1:35 AM, Jared Mauch wrote:

> As always, good research by renesys.

What happens when an ASN is requested, and it's discovered that said ASN is=
 already in use by an unauthorized network, and that some proportion of the=
 Internet are accepting it due to a lack of appropriate routing policy?  Is=
 there a process to try and reclaim said ASN via persuasion, or some jurisd=
ictionally-appropriate legal action, or peer pressure (pardon the pun), or =
. . . ?

This is a different circumstance than either accidental or deliberate use o=
f an already-assigned and -utilized ASN; has this situation occurred in the=
 past, and if so, how was it resolved?  If the situation isn't resolved in =
a timely manner, is the ASN in question considered 'poisoned' until a resol=
ution is attained, and the next available ASN which isn't being utilized in=
 a rogue fashion issued in its place?

Apologies if this is a naive question; I've not run into this particular ci=
rcumstance before, nor have I found any reference to it in any of the vario=
us list archives.  I do believe that it may become a bit more common, given=
 some of the confusion and drama regarding the operationalization of 4-byte=
 ASNs.

-----------------------------------------------------------------------
Roland Dobbins <rdobbins@arbor.net> // <http://www.arbornetworks.com>

    Injustice is relatively easy to bear; what stings is justice.

                        -- H.L. Mencken





home help back first fref pref prev next nref lref last post