[68757] in North American Network Operators' Group

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

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

daemon@ATHENA.MIT.EDU (bill)
Tue Mar 16 12:06:26 2004

From: bill <bmanning@karoshi.com>
To: jeroen@unfix.org (Jeroen Massar)
Date: Tue, 16 Mar 2004 09:03:21 -0800 (PST)
Cc: nanog@merit.edu, hostmaster@arin.net
In-Reply-To: <20040316125235.CB1558722@purgatory.unfix.org> from "Jeroen Massar" at Mar 16, 2004 01:51:38 PM
Errors-To: owner-nanog-outgoing@merit.edu


 so... the subject is somewhat disingenious.  there is no problem with a prefix being
 announced by more than one ASN. Per the original subject, this seemed to be your gripe.
 however, the thread has devolved into someone using network resources w/o registration...
 which is different.  


> 
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> [cc: to hostmaster@arin.net, maybe now it will get their
> attention instead of going into /dev/null]
> 
> Hi,
> 
> Here is some operational content, instead of Packet Kiddies
> trying to rape each other verbally ;)
> 
> According to Toshikazu Saito (Powerdcom):
> 
> > I know both ASs, 4436 and 4474 are yours, so
> > nlayer should resolve this problem or respond to this.
> 
> But:
> 
> OrgName:    Global Village Communication, Inc.
> OrgID:      GVC-8
> Address:    1144 East Arques Avenue
> City:       Sunnyvale
> StateProv:  CA
> PostalCode: 94086
> Country:    US
> 
> ASNumber:   4474
> ASName:     GVIL1
> ASHandle:   AS4474
> Comment:    The information for this ASN has been reported to
> Comment:    be invalid. ARIN has attempted to obtain updated data, but has
> Comment:    been unsuccessful. To provide current contact information,
> Comment:    please e-mail hostmaster@arin.net.
> RegDate:    1995-03-08
> Updated:    2003-07-31
> 
> The reason for the above was that we are currently seeing
> 2001:590::/32 announced by both AS4436 (nLayer) and AS4474
> (Global Village Communication) but apparently this is the
> same company and apparently they are using the bogus ASN.
> Bogus as it has no valid contact information
> 
> See telnet://grh.sixxs.net
> or http://www.sixxs.net/tools/grh/lg/?find=2001:590::/32
> for the odd routes and who it goes over.
> 
> As nLayer seems to be able to only send ticket responses
> but there seems to be no real user alive maybe it is time
> to start letting their peers ask them what to do with this
> and if they can't contact them to just start depeering?
> Unresponsive "NOC"'s is a real nightmare.
> 
> Greets,
>  Jeroen
> 
> -----BEGIN PGP SIGNATURE-----
> Version: Unfix PGP for Outlook
> Comment: Jeroen Massar / http://unfix.org/~jeroen/
> 
> iQBGBAERAgAQCRApqihSMz58IwUCQFb4WAAAoTsAniiZQnM0LhXbVJD7keZCNu6f
> CM2OAKCPs2tdOfwt49m8/xLnugqyGRMnGA==
> =ePKi
> -----END PGP SIGNATURE-----
> 


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