4. Addressing and Routing Architecture
Addressing Mechanisms
Private Addressing and NAT
โข Private IP addresses are those that cannot be advertised and forwarded by
network devices in the public domain.
โข This was originally established to help with address space depletion in the
Internet, for if networks that would normally be allocated public address
space instead use private address space, those public addresses would remain
available.
5. Addressing and Routing Architecture
Addressing Mechanisms
Private Addressing and NAT
There is a side benefit of using private addresses.
๏ It turns out that because these addresses are not advertised and forwarded in the Internet, they have an
additional degree of security.
โข NAT maps IP addresses between public and private spaces.
โข In translating between public and private address spaces, NAT creates bindings between
addresses.
โข These can be one-to-one address bindings (known as static NAT), one-to-many address bindings
(known as dynamic NAT), and address and port bindings (known as network address port
translation, or NAPT).
โข Often combinations of static, dynamic, and NAPT bindings are used in a network. For example,
dynamic NAT is often used for user devices, and static NAT for servers.
7. Addressing and Routing Architecture
Routing Mechanisms
Establishing Routing Flows
โข In preparing to discuss boundaries and route manipulation, we want to understand
how flows will likely be routed through the network.
โข Determining routing flows begins with the flow analysis process.
โข Functional areas (FA) are groups within the system that share a similar function.
โข Groups may be of users (workgroups), applications, devices, or combinations of
these, and they may share similar jobs/tasks, physical locations, or functions within
the network (e.g., backbone routing).
โข Workgroups (WG) are groups of users that have common locations, applications, and
requirements, or that belong to the same organization.
8. Addressing and Routing Architecture
Routing Mechanisms
Establishing Routing Flows
โข The purpose of functional areas is to simplify the routing architecture. They
can cross physical boundaries, such as rooms, floors, and buildings. A
workgroup is similar to a functional area, but one level lower in hierarchy.
โข Consider Figure 6.12. In this figure there are multiple workgroups, in this
case based on organizations within a company. Functional areas are created:
the Scientists and Accounting groups in Building C, the two Management
workgroups in Building B, the Scientists groups across Buildings A and C,
and the backbone between the buildings. Notice that functional areas are
connected with routers.
10. Addressing and Routing Architecture
Routing Mechanisms
Identifying and Classifying Routing Boundaries
โข Routing boundaries are physical or logical separations of a network, based on
requirements for or administration of that network.
โข Physical boundaries can be identified by isolation LANs or demilitarized
zones (DMZs); physical interfaces on network equipment; or physical
security.
โข Logical boundaries can be identified by functional areas, workgroups,
administrative domains, such as autonomous systems (ASs), and routing
management domains.
11. Addressing and Routing Architecture
Routing Mechanisms
Identifying and Classifying Routing Boundaries
12. Addressing and Routing Architecture
Routing Mechanisms
Identifying and Classifying Routing Boundaries
13. Addressing and Routing Architecture
Routing Mechanisms
Identifying and Classifying Routing Boundaries
14. Addressing and Routing Architecture
Routing Mechanisms
Manipulating Routing Flows
โข Manipulating (i.e., controlling) routing flows within the network is vital to the
proper operation and performance of the network.
โข The right combination of addressing and routing is important in this
process, to localize routing flows whenever possible.
โข There are several techniques for manipulating routing flows at hard and soft
boundaries.
โข A default route is the route used when there is no other route for that
destination.
15. Addressing and Routing Architecture
Routing Mechanisms
Manipulating Routing Flows
โข Route filtering is the technique of applying route filters to hide networks from the rest
of an AS, or to add, delete, or modify routes in the routing table.
โข A route filter is a statement, configured in one or more routers, that identifies one or
more IP parameters (e.g., an IP source or destination address) and an action (e.g.,
drop or forward) to be taken when traffic matches these parameters.
โข Route aggregation is the technique exchanging of routing information between ASs,
usually between service providers with transit networks, and between large customer
networks.
16. Addressing and Routing Architecture
Routing Mechanisms
Manipulating Routing Flows
โข Policies are higher-level abstractions of the route filter technique described previously. Just as a route
filter takes an action (e.g., drop, accept, modify) on traffic that matches one or more parameters (e.g.,
IP addresses), a policy takes a similar action on traffic that matches one or more AS parameters (e.g.,
AS number or list of AS numbers and metrics, time of day, cost).
20. Addressing and Routing Architecture
Addressing Strategies
โข During the requirements analysis process, it is important to gather
information about device growth expectations, so that you can avoid having
to change addressing schemes and reconfigure device addresses during the
life cycle of the network.
โข When applying subnetting, variable-length subnetting, classful addressing,
supernetting, private addressing and NAT, and dynamic addressing, we want
to make sure that our network addresses and masks will scale to the sizes of
the areas they will be assigned to. We also want to establish the degrees of
hierarchy in the network.
21. Addressing and Routing Architecture
Addressing Strategies
To scale the network addressing, we will use the numbers of
๏ Functional areas within the network
๏ Workgroups within each functional area
๏ Subnets within each workgroup
๏ Total numbers of subnets (current and future) in the organization
๏ Total numbers of devices (current and future) within each subnet
25. Addressing and Routing Architecture
Routing Strategies
โข Evaluating Routing Protocols
โข Choosing and Applying Routing Protocols
26. Addressing and Routing Architecture
Routing Strategies
Evaluating Routing Protocols
โข Now we briefly examine and compare some popular IGPs and EGP:
๏ The routing information protocol (RIP and RIPv2)
๏ The open shortest-path first (OSPF) routing protocol
๏ The border gateway protocol version 4 (BGPv4)
โข We also consider the limited use of static routes in the network.
๏ Static routes are routes that are configured manually, by network personnel or scripts, in
network devices, and that do not change until manually deleted or modified.
27. Addressing and Routing Architecture
Routing Strategies
Evaluating Routing Protocols
โข A stub network is a network with only one path into or out of it, as in Figure 6.23.
28. Addressing and Routing Architecture
Routing Strategies
Evaluating Routing Protocols
โข RIP and RIPv2 are IGPs that are based on a distance-vector routing
algorithm.
โข This implies some characteristics of the dynamic behavior of RIP/RIPv2-
routed networks. RIP and, to a lesser degree, RIPv2 are relatively
straightforward to implement and maintain.
โข RIP/RIPv2 should be considered when there is low to medium hierarchy
and diversity in the network. Degrees of hierarchy and diversity are shown in
Figure 6.24.
30. Addressing and Routing Architecture
Routing Strategies
Evaluating Routing Protocols
โข OSPF is an IGP that is based on a link-state algorithm. Like RIP/RIPv2, the
choice of routing algorithm affects the characteristics of the protocol.
โข In the case of OSPF, the use of a link-state algorithm results in a faster
convergence time when changes in the routing topology occur.
โข OSPF also supports an area abstraction, which provides a hierarchy for
routing information.
โข OSPF should be considered when there is high hierarchy and diversity in the
network, as shown in Figure 6.24.
32. Addressing and Routing Architecture
Routing Strategies
Evaluating Routing Protocols
โข BGPv4 (or BGP) is a path-vector-based EGP. A path-vector algorithm is
similar to a distance-vector algorithm, such as that used in RIP; however, it
operates on ASs or lists of ASs (paths). In addition, BGP can use policies to
determine actions to be taken on paths.
โข BGP exchanges routing information by establishing peering connections
using TCP with a user-defined list. BGP is used to enforce network transport
policies for an AS, such as allowing all routes from a certain AS to use this
AS as a transit route; rejecting all routes that have been learned from a
certain AS; and only announcing certain routes from this AS to other peers.
33. Addressing and Routing Architecture
Routing Strategies
Evaluating Routing Protocols
โข BGP operates between ASs, yet there may be a number of routers (termed border
routers) that connect to external networks. As such, there needs to be a mechanism
for border routers from the same AS to communicate path information, so that it
can be passed to multiple ASs (see Figure 6.25).
โข Therefore, there are two types of BGP:
๏ external BGP and internal BGP. External BGP (eBGP) is the โnormalโ operational mode
of BGP: passing path information between ASs.
๏ Internal BGP (iBGP) is used to form tunnels between border routers within an AS, in order
to pass path information across that AS.
35. Addressing and Routing Architecture
Routing Strategies
Choosing and Applying Routing Protocols
Some recommendations for choosing and applying routing protocols for your
network.
1. Minimize the number of routing protocols used in the network. Two should be the
maximum number of protocols allowed, with only one IGP.
2. Start with the simplest routing strategy and routing mechanism/protocol.
3. As the complexity in routing and choices of routing protocols increase, reevaluate the
previous decisions.
36. Addressing and Routing Architecture
Routing Strategies
Choosing and Applying Routing Protocols
โข Starting with the simplest routing mechanism (static routes) and working our
way up to more complex mechanisms, we usually start with the outer edges
of the network, where hierarchy and diversity are lowest, and work our way
toward the center, or backbone, of the network, where hierarchy and
diversity are highest (Figure 6.26).
37. Addressing and Routing Architecture
Routing Strategies
Choosing and Applying Routing Protocols
38. Addressing and Routing Architecture
Routing Strategies
Choosing and Applying Routing Protocols
โข In applying routing protocols we start by evaluating the degrees of hierarchy and
diversity of each functional area and considering any other factors for that
functional area or features of the routing protocols that may apply.
โข When a change is made in the choice of routing protocol, such as from static routes
to RIP/RIPv2, from RIP/RIPv2 to OSPF, or from RIP/RIPv2/OSPF to BGP,
โข We need to reevaluate functional areas where routing protocols or static routes have
already been chosen.
โข In general, RIP/RIPv2 supersedes static routes, and OSPF supersedes RIP/RIPv2.
But remember that you can also consider combining the protocols within the
network. Figure 6.27 illustrates the process of applying routing protocols.
39. Addressing and Routing Architecture
Routing Strategies
Choosing and Applying Routing Protocols
41. Addressing and Routing Architecture
Architectural Considerations
Internal Relationships
โข Depending on the type of network being developed, the set of candidate
addressing and forwarding mechanisms for a component architecture can be
quite different.
โข Two types of interactions are predominant within this component
architecture:
๏ Trade-offs between addressing and forwarding mechanisms
๏ Trade-offs within addressing or within forwarding.
43. Addressing and Routing Architecture
Architectural Considerations
External Relationships
โข External relationships are trade-offs, dependencies, and constraints between
the addressing/routing architecture and each of the other component
architectures (network management, performance, security, and any other
component architectures you may develop).
โข There are common external relationships between addressing/ routing and
each of the other component architectures
44. Addressing and Routing Architecture
Architectural Considerations
External Relationships
Some of common external relationships between addressing/ routing and each
of the other component architectures
๏ Interactions between addressing/routing and network management.
๏ Interactions between addressing/routing and performance.
๏ Interactions between addressing/routing and security.