157.112.0.0/16 ARIN info updated, AT&T still announcing /16

Thu Sep 11 15:52:48 UTC 2003

>From the [Hijacked] list:

> The ARIN information has been updated to have up-to-date contact info for
> the original owner, the original owners' ISP is announcing 4 /18s but AT&T
> is still announcing 157.112.0.0/16. Can whoever's been bugging AT&T to stop
> announcing it to bug them some more?

abuse at att.net seems to be a dead horse - demands from numerous parties,
including the owner of this /16 (the true source of records is JPNIC:
whois -h whois.nic.ad.jp "157.112.0.0 /e" , ARIN has not proceeded with
'early registration' transfer of this group of records to JPNIC, it
seems) that have been mailed there and to various other @att.net addresses,
including their so-called "legal demands center" (that is reportedly hard
to reach via email) have been summarily ignored, and we mean "/dev/null'd".

AT&T, for lack of presenting any TRO forcing them to keep routing this,
appears to willingly conspire with the Empire Towers IP space hijackers
while presented with overwhelming evidence that whatever forged documents
Empire Towers and Thomas Cowles may have presented to them are indeed that
- forged.

ARIN zapping the legacy record for this block apparently isn't
convincing enough for them to stop announcing this route.

The ISP for Systems Clipper Inc. (AS 23720) had started announcing a competing
/16 almost 2 weeks ago, but for reasons obvious to nearly all members of
this list, that of course wasn't good enough: it's four /18's now,
and AT&T should be seeing none of the traffic just about now.

If you are peering with AS 7018, a nicely worded email to your peering
contacts expressing your concern with AT&T's non-existent cooperation
in IP space hijacking cases would be appreciated.

Thank you.
bye,Kai

ps: and this says nothing about the amount and nature of actual abuse that's
  been reported from this /16 while it originated from AS 7018.