North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Where are static bogon filters appropriate? was: 96.2.0.0/16 Bogons

  • From: Peter Thoenen
  • Date: Thu Mar 01 10:18:32 2007
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=Wzsd9am5UAMBLAsOAvL7R4Motp6RHtp1pmaTCIXD6QWl7qEmmSyqMnj6YBqzytjt0TtHOci2fQlBr7FtjUzJpn3JXbCm0q+a++kESnlIOsDpW3pG2v2xOo/klDQW2zVs2zWXjvGSrbGkCb547WlSBroqgoe3IiXjqT015Jf8QeY=;
> Perhaps,  
> bogon acls  are helpful when they are configured on backbone, but not
> 
> everywhere.

And if ever major backbones (read tier 2/3) would do so all us little
guys wouldn't have to (yet for some reason I keep getting the odd hit
in my acl logs from bogon space daily).

Yes I know they will defend this with "we sell unfiltered service"
(which of course isn't true); I am just not convinced filtering bogon's
would invalidate this any more than their MPLS QoS clouds do.