Professional Documents
Culture Documents
L22 Rout Nup
L22 Rout Nup
L22 Rout Nup
time into the future. standard” (NZ e-Government Interoperability Framework e-GIF,
2002).
! Dual-stack operation: ! IPv4 exhaustion:
! Some nodes and routers will have both IPv4 and IPv6 ! IANA and ARIN registration exhaustion: 2011 / 2012
! ISP level: 2015
protocol stacks.
! The version field will be used to direct a packet to the correct ! NAT
stack. ! Too many changes:
! Apps and API’s have to change
! Tunneling IPv6 through IPv4. ! Domain Name System (DNS) changes
! Border Gateway Protocol (BGP) changes
! Each IPv6 packet is encapsulated into an IPv4 packet whose
! Routing protocol changes
address is the address of the other end of the tunnel. ! IPv4 over xxx now needs IPv6 over xxx
Where to Route? Routing Flows in the Design Environment Functional Areas
! Without a map many a road cannot be found. ! Need to Understand How Flows will likely be Routed ! Earlier focused on regions of the logical design
termed areas based on geography, user
! Routing protocols are about dissemination of routing through our Design Environment concentrations or information flow hierarchies
data among the routers of the routing network ! These areas are candidates as functional areas for
! Need addressing and routing
! Routing algorithms: find a path with minimum cost ! The Logical Layout of the Network Design
sum for sending a packet to receiving node. ! Functional Areas involves combining work groups
! An Understanding of the Potential Information Flows
(logical groups of users that have common
Within the Network
locations, applications, and requirements, or
! Numbers, Locations, and Purposes of Routers in the Network belong to same organization) usually centered in a
(e.g., are they general IP packet forwarding engines, or a physical area but possibly not when focus is on
filtering and aggregation point?) applications or sets of requirements.
! Determine Functional Areas/Boundaries/Flows
Lecture 23: Routing Strategy TELE 302 Lecture 23: Routing Strategy TELE 302 Lecture 23: Routing Strategy TELE 302
Lecture 23: Routing Strategy TELE 302 Lecture 23: Routing Strategy TELE 302 Lecture 23: Routing Strategy TELE 302
Lecture 23: Routing Strategy TELE 302 ! Distance Vector & Link State Lecture 23: Routing Strategy TELE 302 Lecture 23: Routing Strategy TELE 302
Link State Routing Hierarchical Routing Developing a Routing Strategy
! Distance vector no longer used on large WANs ! Hierarchy of routing protocols used at different ! Characteristics of popular routing protocols
levels
! Link State Procedure ! Criteria for making selections among protocols
! Find neighbors ! This is what happens in practice
! Test delay to neighbors-- send echo ! Lowest level, workstations, use default router ! Where to apply and mix protocols
! Broadcast to all routers
! LAN routers use SPF
! Each router computes shortest path to all other routers
(using e.g. Dijkstra) ! First level WANs use private Link State
! Corporate WANs, small ISPs
! Problems ! Core Internet networks use link state
! Distribution of updates ! Exterior protocols (RGP) exchange data with first level
! Network can partition if update breaks WANs.
! Keeps router table size manageable on core Internet and on
first level networks.
Lecture 23: Routing Strategy TELE 302 Lecture 23: Routing Strategy TELE 302 Lecture 23: Routing Strategy TELE 302
Lecture 23: Routing Strategy TELE 302 Lecture 23: Routing Strategy TELE 302 Lecture 23: Routing Strategy TELE 302
! Interoperability is an issue.
Lecture 23: Routing Strategy TELE 302 Lecture 23: Routing Strategy TELE 302 Lecture 23: Routing Strategy TELE 302
Choosing and Applying Routing
BGP-4 Protocols
Keep It Simple
! Border Gateway Protocol version 4 ! A simple strategy:
! Three basic rules of thumb for applying routing
! Use static routing for stub areas
! Path vector-based EGP using route policies and rules to protocols to your design
allow peering between ASs ! For non-stub areas consider RIP/RIPv2
! Minimize the number you use. Two routing protocols should
generally be the maximum number, one IGP is best. ! Where high hierarchy or redundancy is a consideration
! Uses AS numbers, providing an abstraction layer above use OSPF
the network addresses of OSPF and RIP ! Start with the simplest routing strategy/routing protocol.
! Use BGP-4 when an EGP is required
! As complexity in the routing design and choice of routing
! Natural for applying policies to ASs because one can protocol increase, reevaluate earlier decisions.
develop policies for collections of networks
Lecture 23: Routing Strategy TELE 302 Lecture 23: Routing Strategy TELE 302 Lecture 23: Routing Strategy TELE 302