[34978] in North American Network Operators' Group
RE: rfc 1918?
daemon@ATHENA.MIT.EDU (Mark Radabaugh)
Thu Feb 22 19:31:03 2001
From: "Mark Radabaugh" <mark@amplex.net>
To: "North America Network Operators Group Mailing List" <nanog@merit.edu>
Date: Thu, 22 Feb 2001 19:12:14 -0500
Message-ID: <OJEIKHIHKAKFFKDPLLLLIEDHEPAA.mark@amplex.net>
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20010222231552.C2BB58B@proven.weird.com>
Errors-To: owner-nanog-outgoing@merit.edu
It is my intention to avoid having 1918 addresses leaving my network.
At our egress points the filters are fairly short -- they allow only traffic
with our IP source addresses to leave. This was my interpretation of the RFC's.
Some in this discussion seem to be saying that we should also filter for RFC1918
destinations. Am I reading this correctly?
I can see that packets destined for RFC1918 addresses will leave our network
(due to default routes) but are promptly dropped at the first BGP speaking
router they encounter. Is it worth the extra router processing time to check
all outgoing packet destinations as well? I can't see where this extra
filtering is worth the trouble.
Mark Radabaugh
VP, Amplex
(419)833-3635
mark@amplex.net
