2001:590::/32 announced by both AS4436 (nLayer) and AS4474 (Global Village, no contact in whois, but seems to be nLayer...)

Tue Mar 16 22:14:47 UTC 2004

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard A Steenbergen [mailto:ras at e-gerbil.net] wrote:

> On Tue, Mar 16, 2004 at 06:12:22PM +0100, Jeroen Massar wrote:
> > 
> > 2001:590::/32 _is_ being announced by both AS4436 *and* AS4474.
> > Trying to contact these ASN's to inquire why that is happening
> > and maybe finding out if it was an erronous configuration I
> > tried to find the contacts which lead to AS4474 not having any
> > contact information available per ARIN registry.
> > Thus who do you call then when AS4436 doesn't seem home?
> > Indeed: ARIN, which also didn't seem home thus: NANOG.
> 
> Next time you want to contact a noc, you might want to try 
> not doing it as a cc: to an e-mail encouraging random peers
> to depeer someone because of an inconsistant origin AS
> caused by the use of local-as. Actions like that
> (and these for that matter) tend to get one branded a net kook... And
> feedings the kooks is never productive. :)

The issue has been explained by a certain 'representative'
in a seperate mail. Apparently they have acquired a number
of networks amongst which they also AS4474 to/from which
they are migrating requiring the above setup.

Now let's hope that they will finish this migration soon
without problems and update the registry objects in question
so that in the future there can be no doubt about this even
when you are on the other side of the world and nothing
about such a migration is documented anywhere.

Greets,
 Jeroen

-----BEGIN PGP SIGNATURE-----
Version: Unfix PGP for Outlook
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iQBGBAERAgAQCRApqihSMz58IwUCQFd8VgAADnoAnRGvrYWKggDeZndSak1Pp38y
SWnAAJ4x/yhN6Mf6SF7iG6mdzfTsKL16Ig==
=1REM
-----END PGP SIGNATURE-----