[35032] in North American Network Operators' Group
Re: rfc 1918?
daemon@ATHENA.MIT.EDU (bill manning)
Fri Feb 23 15:16:19 2001
Message-ID: <3A96BECC.D96FDB60@localhost.localdomain>
Date: Fri, 23 Feb 2001 11:49:32 -0800
From: bill manning <bmanning@localhost.localdomain>
Reply-To: bmanning@karoshi.com
MIME-Version: 1.0
To: nanog@merit.edu
Cc: Valdis.Kletnieks@vt.edu
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu
SMcGrath@dhhs.state.nh.us wrote:
>
> Agreed Valdis,
>
> Our upstream's use 1918 addresses internally so that 1918 addresses are
> constantly bouncing off our filters
> we have an aggressive egress filter which makes sure no 1918's leak and
> pollute the internet ;-} and filtering on core routers is a suboptimal
> solution RFC 1819 addresses (10 points to the person who knows the
> predecessor) NEED to be filtered at the border IMHO.
>
> Scott
>
AS long as you are filtering, could you -PLEASE- add the SMTP filter to
prevent email w/ RFC 1918 addresses in the headers from leaking out of
your networks?
RFC 1597.
--bill
