[143909] in North American Network Operators' Group
resolving prefix hijacks (was Re: Prefix hijacking by Michael
daemon@ATHENA.MIT.EDU (Ken Chase)
Sun Aug 21 15:00:12 2011
Date: Sun, 21 Aug 2011 14:59:36 -0400
From: Ken Chase <ken@sizone.org>
To: nanog@nanog.org
In-Reply-To: <8C26A4FDAE599041A13EB499117D3C286B5322EC@ex-mb-1.corp.atlasnetworks.us>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Sun, Aug 21, 2011 at 05:26:46PM +0000, Nathan Eisenberg said:
>John Curran appears to be completely open to constructive suggestions, so
if you have real and substantive input, why not contribute your intellect to
the problem and talk to him? Every organization has things they could be
doing better, but as in physics, it often requires some new outside force to
make it happen.
Well written.
That said, what is the de jure responce when a prefix is hijacked? Does
anyone have a 'best practices' guide? I am sure some of the most effective
vs legal practices are not in fact concomittant.
/kc
--
Ken Chase - ken@heavycomputing.ca skype:kenchase23 +1 416 897 6284 Toronto Canada
Heavy Computing - Clued bandwidth, colocation and managed linux VPS @151 Front St. W.
