[7464] in North American Network Operators' Group
Re: RFC1918 conformance
daemon@ATHENA.MIT.EDU (Bill Manning)
Tue Feb 11 12:18:54 1997
From: bmanning@isi.edu (Bill Manning)
To: asp@partan.com (Andrew Partan)
Date: Tue, 11 Feb 1997 08:16:21 -0800 (PST)
Cc: prt@Teleglobe.CA, amilutin@infocom.kiev.ua, bgp4-adm@sprint.net,
hostmaster@ripe.net, nanog@merit.edu, rr-admin@Teleglobe.net
In-Reply-To: <199702110015.TAA27159@home.partan.com> from "Andrew Partan" at Feb 10, 97 07:15:03 pm
> My standard in & out route filters are attached.
> Everyone should use something like this.
> --asp@partan.com (Andrew Partan)
>
> ! Deny martian routes
> ! 1st and last classical B and C nets (guard nets).
> access-list 180 deny ip 128.0.0.0 0.0.255.255 255.255.0.0 0.0.255.255
> access-list 180 deny ip 191.255.0.0 0.0.255.255 255.255.0.0 0.0.255.255
> access-list 180 deny ip 192.0.0.0 0.0.0.255 255.255.255.0 0.0.0.255
> access-list 180 deny ip 223.255.255.0 0.0.0.255 255.255.255.0 0.0.0.255
In a classless environment, these prefixes are legitimate.
Correct behaviour is now known for these subnets and so I
wonder why you still have them in your standard list.
--
--bill
