[91268] in North American Network Operators' Group
Re: Best practices inquiry: filtering 128/1
daemon@ATHENA.MIT.EDU (Christopher L. Morrow)
Tue Jul 11 14:14:33 2006
Date: Tue, 11 Jul 2006 18:14:03 +0000 (GMT)
From: "Christopher L. Morrow" <christopher.morrow@verizonbusiness.com>
In-reply-to: <F6EA7F9A7FE80C409B346B0B9FDC564901FB7637@hkghhtmsx01.in.reach.com>
To: "WONG, Yuen-Fung" <Yuen-Fung.WONG@reach.com>
Cc: nanog@nanog.org
Errors-To: owner-nanog@merit.edu
On Tue, 11 Jul 2006, WONG, Yuen-Fung wrote:
>
> Sometimes earlier this year someone announced this 128/1 and caused
> heavy loading to our routers to rebuild the CEF. Would anyone filter
> out this route (and other similar routes such as 0/1, 128/1, 0/2, 64/2,
> .... up to /4, for example) as bogus routes?
Do you not prefix-list customers? That'd have solved this, eh?
