A recent question from Craig Constantine pertained to IPv6, but many people are not on the leading edge with IPv6 yet and are still responsible for new or improved IPv4 deployments.
I would like to validate my own enterprise IPv4 address space planning against any public documents or guidance given directly here. Addressing has some unique needs between the DC and Campus that would ideally be considered.
I'm specifically looking to see what best practices exist for planning out private (RFC1918) IP space assignments for regions, cities, campus, buildings, floors, uplinks, WAN links, loopbacks, etc. Wired vs wireless. Internal networks vs. guest networks. *I know this on its own can be a bit of an open-ended question, so I'm looking for specific references or examples to proven and well-thought out plans in a similar way as to the IPv6 answers. Suggested CIDR blocks would be helpful as the space gets allocated.
Aggregation for routing, of course, is desired, and so is the ability to have simplified ACLs. There's a trade-off in ACLs on with the desire to aggregate all employee subnets, for example, whether wired or wireless vs aggregating all wireless users regardless if they are employees, contractors, or guests.