North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
RE: Best practice ACLs for a internet facing border router?
- From: Barry Greene (bgreene)
- Date: Mon Jun 13 17:27:31 2005
I do not think there is a "best practice." In fact, "Operational
Entropy"(1) has a big factor with packet filtering ACLs on the
interconnect side of an SP. So you are not going to find a lot of packet
filtering on SP-SP links.
There are links and presentations you can refer to help build a iACL
(Infrastructure protecting ACL).
Whitepaper on Infrastructure ACLs (iACLs)
(principles in this one can be converted to any packet filter)
Team CYMRU's Secure Templates:
Next Gen Peering Architectures and Tools
(1) Operational Entropy is the process of natural decay that starts the
moment the policy gets applied. OPEX resources need to be allocated to
insure the entropy does not lead to operational consequence (i.e. the
decayed policy breaks things).
> -----Original Message-----
> From: email@example.com [mailto:firstname.lastname@example.org] On
> Behalf Of Drew Weaver
> Sent: Monday, June 13, 2005 7:28 AM
> To: email@example.com
> Subject: Best practice ACLs for a internet facing border router?
> I'm just curious if anyone has ever published a list of
> what is an agreed upon best practice list of ACLs for an
> internet facing border router. I'm talking about things like
> bogons, private Ip addresses, et cetera. If anyone is aware
> of anything like this I'd like to see it.