Networking Address Allocation for Private Internets Introduction This document is based upon RFC 1597 , and it will help you conserve IP address space by not allocating globally unique IP addresses to private hosts in your network. You can still permit full network layer connectivity between all hosts in the network and between all public hosts in the Internet. Hosts that use IP fall into three categories: Hosts that do not require access to hosts in other enterprises or the Internet at large. Many applications require connectivity only within one network and do not even need external connectivity for most internal hosts. A large airport which has its arrival and departure displays individually addressable via TCP/IP. Prerequisites Requirements There are no specific requirements for this document. Components Used This document is not restricted to specific software and hardware versions. Conventions For more information on document conventions, see the Cisco Technical Tips Conventions. Private Address Space Design Considerations Conclusion Conclusion
Enterprise Campus 3.0 Architecture: Overview and Framework Having a dedicated core layer allows the campus to accommodate this growth without compromising the design of the distribution blocks, the data center, and the rest of the network. This is particularly important as the size of the campus grows either in number of distribution blocks, geographical area or complexity. In a larger, more complex campus, the core provides the capacity and scaling capability for the campus as a whole. The question of when a separate physical core is necessary depends on multiple factors. The ability of a distinct core to allow the campus to solve physical design challenges is important. However, it should be remembered that a key purpose of having a distinct campus core is to provide scalability and to minimize the risk from (and simplify) moves, adds, and changes in the campus.