North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical RE: rfc 1918 (why filtering is a good idea for non-transit organizations)
Title: RE: rfc 1918 (why filtering is a good idea for non-transit organizations) Actually, if memory serves me correctly (for once), there was a situation several years ago where a transit provider ran out of bandwidth and started shunting traffic through a (better-connected) customer's network. If filtering had been operating properly at that time (if there had been enough CPU muscle in the routers) as specified below, then this could NOT have happened -- the customer's network would have recognized the destination IP as not being within its address range, and filtered it on ingress. (Or, it could have checked the source IP, and if it wasn't in its address range, filtered it on egress. My personal opinion is that both are necessary and desirable, for different reasons.) -Mat Butler -----Original Message-----
This only can apply to small networks, specifically stub networks, if
But i think you have the right idea, filters should be applied at the
Oh, and I dont think I showed my opinion on my last mail, i think use of
Steve On Thu, 22 Feb 2001, Mark Radabaugh wrote: > It is my intention to avoid having 1918 addresses leaving my network.
|