1 and 2 are what's called object-groups, new in v6.2 code. These are used to group ports, networks or host address into one name, that can then be used in an access-list. For example, before 6.2, to reference all those TCP ports in Part 1 in an access-list you'd have to have something like:
> access-list 100 permit tcp host x.x.x.x host y.y.y.y range 4440 4447
> access-list 100 permit tcp host x.x.x.x host y.y.y.y eq 2000
> access-list 100 permit tcp host x.x.x.x host y.y.y.y eq 4999
> access-list 100 permit tcp host x.x.x.x host y.y.y.y eq 4600
> access-list 100 permit tcp host x.x.x.x host y.y.y.y eq 1030
> access-list 100 permit tcp host x.x.x.x host y.y.y.y eq 8080
> access-list 100 permit tcp host x.x.x.x host y.y.y.y eq www
If you wanted to open up those ports for a bunch of hosts or networks, you're access-list could get very large very quickly. Now with object-groups, you can do the following (check your config cause you probably have something like this):
> access-list 100 permit tcp host x.x.x.x object-group innovative object-group webopac_services
The "innovative" object group specifies a group of networks, and the "webopac_services" specifies the ports that they can come in on. You can see that without object-groups, you would need around 64 lines in your access-list just to allow this same access. You can see http://www.cisco.com/warp/public/707/pix_obj_grp.html for more information on these.
3 is simply an access-list called acl_in that'll be applied to one of your interfaces with a corresponding "access-group" command further down in your configuration.
