[34603] in North American Network Operators' Group
RE: Using unallocated address space
daemon@ATHENA.MIT.EDU (Sean Donelan)
Wed Feb 14 00:50:28 2001
Date: 13 Feb 2001 21:47:15 -0800
Message-ID: <20010214054715.5699.cpmta@c004.sfo.cp.net>
Content-Type: text/plain
Content-Disposition: inline
Mime-Version: 1.0
To: brett.hawn@rcn.com
From: Sean Donelan <sean@donelan.com>
Cc: nanog@merit.edu
Errors-To: owner-nanog-outgoing@merit.edu
On Tue, 13 February 2001, "Brett L. Hawn" wrote:
> Here I go being silly again, but how about people take responsability for
> their own networks and filter properly at their borders? All this talk of
> how to enforce things is pretty meaningless when you have countless members
> of NANOG itself half-assing their own networks and complaining about other
> people's.
Because this is only half the answer.
I always filtered my announcements, was careful to register all the
address blocks I used, and was very responsible for my own network.
It had no effect on someone else hijacking one of my addresses and
announcing it through a large ISP's route tables.
I was effectively cut off the network not because of anything I did, or
could control. Worse there was little I could do to fix it. I had to
wait three days for the large ISP (with whom I had no direct relationship)
engineer's to decide it was worth their effort to stop the source
of the false announcement.
Unfortunately this is not a unique occurance. Cable&Wireless, Sprint,
AT&T and UUNET have all had portions of their service knocked off the
Internet for various periods of time due to bogus announcements. Until
other ISPs fix their policies, I can knock your network off most of the
Internet, and there is nothing you can do to prevent it.