|  | 6.5 | Named ACLs
| 6.5.1 | Configuring named ACLs

Named ACLs allow standard and extended IP ACLs to be identified with an alphanumeric string (name) instead of the current numeric (1 to 199) representation. Named ACLs can be used to delete individual entries from a specific ACL. This enables you to modify your ACLs without deleting and then reconfiguring them. Use named ACLs when: You want to intuitively identify ACLs using an alphanumeric name. You have more than 99 simple and 100 extended ACLs to be configured in a router for a given protocol. Consider the following before implementing named ACLs: Named ACLs are not compatible with Cisco IOS releases prior to Release 11.2. You cannot use the same name for multiple ACLs. In addition, ACLs of different types cannot have the same name. For example, it is illegal to specify a standard ACL named George and an extended ACL with the same name. To name the ACL, use the following command: Router(config)# ip access-list {standard | extended} name In ACL configuration mode, specify one or more conditions permitted or denied. This determines whether the packet is passed or dropped: Router(config {std- | ext-}nacl)# deny {source [source-wildcard] | any} or Router(config {std- | ext-}nacl)# permit {source [source-wildcard] | any}. The configuration shown in the Figure creates a standard ACL named Internetfilter and an extended ACL named marketing_group.