Dynamic Routing. The Protocols

Dynamic Routing The Protocols

Desirable Characteristics of Dynamic Routing Automatically detect and adapt to topology changes Provide optimal routing Scalability Robustness Simplicity Rapid convergence Some control of routing choices E.g. which links we prefer to use

Interplay between routing & forwarding routing algorithm local forwarding table header value output link 0100 0101 0111 1001 3 2 2 1 value in arriving packet s header 0111 1 3 2

IP Routing finding the path Path is derived from information received from the routing protocol Several alternative paths may exist best next hop stored in forwarding table Decisions are updated periodically or as topology changes (event driven) Decisions are based on: topology, policies and metrics (hop count, filtering, delay, bandwidth, etc.)

Convergence why do I care? Convergence is when all the routers have a stable view of the network When a network is not converged there is network downtime Packets don t get to where they are supposed to go Black holes (packets disappear ) Routing Loops (packets go back and fore between the same devices) Occurs when there is a change in status of router or the links

Internet Routing Hierarchy The Internet is composed of Autonomous Systems Each Autonomous System is an administrative entity that Uses Interior Gateway Protocols (IGPs) to determine routing within the Autonomous System Uses Exterior Gateway Protocols (EGPs) to interact with other Autonomous Systems

Internet Routing Architecture Autonomous System (AS) Autonomous System (AS) Autonomous System (AS) Autonomous System (AS) Autonomous System (AS) Autonomous System: A collection of IP subnets and routers under the same administrative authority. Interior Routing Protocol Exterior Routing Protocol

Interior Gateway Protocols Four well known IGPs today RIP EIGRP OSPF ISIS

Exterior Gateway Protocols One single de-facto standard: BGP

Routing versus Forwarding Routing = building maps and giving directions Forwarding = moving packets between interfaces according to the directions

IP Forwarding Source S IP Subnet IP Subnet IP Subnet Destination IP Subnet D Forwarding decisions: Destination address class of service (fair queuing, precedence, others) local requirements (packet filtering)

Routing Tables Feed the Forwarding Table Forwarding Information Base (FIB) Routing Information Base (RIB) BGP 4 Routing Table ISIS Link State Database Static Routes

RIB Construction Each routing protocol builds its own Routing Information Base (RIB) Each protocol has its own view of costs e.g., ISIS is administrative weights e.g., BGP4 is Autonomous System path length

FIB Construction There is only ONE forwarding table! An algorithm is used to choose one next-hop toward each IP destination known by any routing protocol the set of IP destinations present in any RIB are collected if a particular IP destination is present in only one RIB, that RIB determines the next hop forwarding path for that destination

FIB Construction Choosing FIB entries, cont.. if a particular IP destination is present in multiple RIBs, then a precedence is defined to select which RIB entry determines the next hop forwarding path for that destination This process normally chooses exactly one next-hop toward a given destination There are no standards for this; it is an implementation (vendor) decision

FIB Contents IP subnet and mask (or length) of destinations can be the default IP subnet IP address of the next hop toward that IP subnet Interface id of the subnet associated with the next hop Optional: cost metric associated with this entry in the forwarding table

IP routing Default route where to send packets if there is no entry for the destination in the routing table most machines have a single default route often referred to as a default gateway 0.0.0.0/0 matches all possible destinations, but is usually not the longest match

IP route lookup: Longest match routing Packet: Destination IP address: 10.1.1.1 R3 Most of 10.0.0.0/8 except for 10.1.0.0/16 R1 Based on destination IP address R2 R2 s IP forwarding table 10.0.0.0/8 R3 10.1.0.0/16 R4 20.0.0.0/8 R5 0.0.0.0/0 R1 R4 10.1.0.0/16

IP route lookup: Longest match routing Most specific/longest match always wins!! Many people forget this, even experienced ISP engineers Default route is 0.0.0.0/0 Can handle it using the normal longest match algorithm Matches everything. Always the shortest match.

Graph abstraction 5 Graph: G = (N,E) N = set of routers = { u, v, w, x, y, z } E = set of links ={ (u,v), (u,x), (v,x), (v,w), (x,w), (x,y), (w,y), (w,z), (y,z) } u 1 2 v x 2 3 1 3 w y 1 5 2 z Path: Sequence of edges (routers) Remark: Graph abstr. is useful in other network contexts Example: P2P, where N is set of peers and E is set of TCP connections

Graph abstraction: costs u 1 2 5 v x 2 3 1 3 w y 1 5 2 z c(x,x ) = cost of link (x,x ) e.g., c(w,z) = 5 cost can be always 1, or inversely related to bandwidth, inversely related to congestion Cost of path (x 1,x 2,x 3,,x p ) = c(x 1,x 2 )+c(x 2,x 3 )+ +c(x p-1,x p ) Question: What s the least-cost path between u and z? Routing algorithm: alg. that finds good path (typically: least cost path)

Distance Vector and Link State Distance Vector Accumulates a metric hop-by-hop as the protocol messages traverse the subnets Link State Builds a network topology database Computes best path routes from current node to all destinations based on the topology

Distance Vector Protocols Each router only advertises to its neighbors, its distance to various IP subnets Each router computes its next-hop routing table based on least cost determined from information received from its neighbors and the cost to those neighbors

Distance Vector Algorithm Bellman-Ford Equation Define d x (y) := cost of least-cost path from x to y Then d x (y) = min {c(x,v) + d v (y) } v where min is taken over all neighbors v of x

Bellman-Ford example u 1 2 5 v x 2 3 1 3 w y 1 5 2 z Clearly, d v (z) = 5, d x (z) = 3, d w (z) = 3 Bellman-Ford equation says: d u (z) = min { c(u,v) + d v (z), c(u,x) + d x (z), c(u,w) + d w (z) } = min {2 + 5, 1 + 3, 5 + 3} = 4 Node that yields minimum is next hop in shortest path forwarding table

Distance Vector RIB Parameters Accumulated cost cost is a constant administrative assignment for each subnet assignment is typically 1 for each subnet (equivalent to hop-count) included in routing protocol exchange Time the update was received (for timeout)

Distance Vector RIB Parameters The next-hop the entry was received from sender s id is included in routing protocol exchange Accumulated Hop count and Maximum Hop Count used to detect cycles hop count included in routing protocol exchange

Distance Vector: Additions When a router learns of new reachable subnets at router startup when an interface in enabled or restored to service A routing update is broadcast to all neighbors

Distance Vector: Additions Any router receiving the packet compares the cost it received in the new packet with that in its RIB If the cost is smaller or the subnet is new the new entry is used in the RIB the new entry is broadcast to all its neighbors (except the one from which it was received)

Distance Vector: Removals Each RIB entry is aged a timeout defines when an entry is removed from the RIB Periodically, each router re-advertises all the routes it knows to its neighbors this can be done in many ways: from simple neighbor hellos to enumeration of all routes

Distance Vector: Removals If a neighbor does not respond within a timeout, all routes learned from that neighbor are removed Route removal may be advertised to neighbors

Distance Vector Algorithm (2) D x (y) = estimate of least cost from x to y Distance vector: D x = [D x (y): y є N ] Node x knows cost to each neighbor v: c(x,v) Node x maintains D x = [D x (y): y є N ] Node x also maintains its neighbors distance vectors For each neighbor v, x maintains D v = [D v (y): y є N ]

Distance Vector Algorithm (3) Basic idea: Each node periodically sends its own distance vector estimate to neighbors When a node x receives new DV estimate from neighbor, it updates its own DV using B-F equation: D x (y) min v {c(x,v) + D v (y)} for each node y N r Under natural conditions the estimates of D x (y) converge to the actual least cost d x (y)

Distance Vector Algorithm (4) Iterative, asynchronous: each local iteration caused by: local link cost change DV update message from neighbor Distributed: each node notifies neighbors only when its Distance Vector changes neighbors then notify their neighbors if necessary Each node: wait for (change in local link cost of msg from neighbor) recompute estimates if Distance Vector to any dest has changed, notify neighbors

node x table cost to x y z from x y z node y table from x y z node z table from x y z 0 2 7 cost to x y z 2 0 1 cost to x y z 7 1 0 D x (y) = min{c(x,y) + D y (y), c(x,z) + D z (y)} = min{2+0, 7+1} = 2 from from from x y z x y z x y z cost to x y z 0 2 3 2 0 1 7 1 0 cost to x y z 0 2 7 2 0 1 7 1 0 cost to x y z 0 2 7 2 0 1 3 1 0 from from from x y z x y z x y z cost to x y z 0 2 3 2 0 1 3 1 0 cost to x y z 0 2 3 2 0 1 3 1 0 cost to x y z 0 2 3 2 0 1 3 1 0 time D x (z) = min{c(x,y) + D y (z), c(x,z) + D z (z)} = min{2+1, 7+0} = 3 x 2 y 7 1 z

Distance Vector (DV): link cost changes Link cost changes: node detects local link cost change updates routing info, recalculates distance vector if DV changes, notify neighbors x 1 4 y 50 1 z good news travels fast At time t 0, y detects the link-cost change, updates its DV, and informs its neighbors. At time t 1, z receives the update from y and updates its table. It computes a new least cost to x and sends its neighbors its DV. At time t 2, y receives z s update and updates its distance table. y s least costs do not change and hence y does not send any message to z.

1 x 4 y 50 1 z node y table cost to x y z from x y 4 1 0 1 z 5 1 0 from cost to x y z x y 1 0 1 z 5 1 0 from cost to x y z x y 1 0 1 z 2 1 0 node z table cost to x y z cost to x y z cost to x y z from x y 4 0 1 z 5 1 0 from x y 1 0 1 z 521 0 from x y 1 0 1 z 2 1 0 time

Distance Vector: link cost changes Link cost changes: y good news travels fast 4 1 bad news travels slow x z 60 50

60 x 4 y 50 1 z D y (x) = min{c(y,x) + D x (x), c(y,z) + D z (x)} = min{60 + 0, 1 + 5} = 6 D y (x) = min{c(y,x) + D x (x), c(y,z) + D z (x)} = min{60 + 0, 1 + 7} = 8 node y table cost to x y z from x y 4 6 0 1 z 5 1 0 from cost to x y z x y 6 0 1 z 5 1 0 from cost to x y z x y 68 0 1 z 7 1 0 node z table cost to x y z cost to x y z cost to x y z from x y 4 0 1 z 5 1 0 from x y 6 0 1 z 57 1 0 from x y 6 0 1 z 7 1 0 time

Distance Vector: link cost changes Link cost changes: good news travels fast bad news travels slow count to infinity problem! 60 x 4 y 50 1 z 44 iterations before algorithm stabilizes. Poisoned reverse: If Z routes through Y to get to X : Z tells Y its (Z s) distance to X is infinite (so Y won t route to X via Z) will this completely solve count to infinity problem?

RIP (Routing Information Protocol) Distance vector algorithm Included in BSD-UNIX Distribution in 1982 Distance metric: # of hops (max = 15 hops) z u A C B D v w y x From router A to subsets: destination hops u 1 v 2 w 2 x 3 y 3 z 2

RIP advertisements Distance vectors: exchanged among neighbors every 30 sec via Response Message (also called advertisement) Each advertisement: list of up to 25 destination nets within AS

RIP: link failure and recovery If no advertisement heard after 180 sec, neighbor/link declared dead Routes via the neighbor are invalidated New advertisements sent to neighbors Neighbors in turn send out new advertisements (if their tables changed) Link failure info quickly propagates to entire net Poison reverse used to prevent ping-pong loops (infinite distance = 16 hops)

Why not use RIP? RIP is a Distance Vector Algorithm Listen to neighbouring routes Install all routes in routing table Lowest hop count wins Advertise all routes in table Very simple, very stupid Only metric is hop count Network is max 16 hops (not large enough) Slow convergence (routing loops) Poor robustness

EIGRP Enhanced Interior Gateway Routing Protocol Predecessor was IGRP which was classfull IGRP developed by Cisco in mid 1980s to overcome scalability problems with RIP Cisco proprietary routing protocol Distance Vector Routing Protocol Has very good metric control Still maybe used in some enterprise networks? Multi-protocol (supports more than IP) Exhibits good scalability and rapid convergence Supports unequal cost load balancing

Link State Protocols Dijsktra IS-IS

Link State Protocols Each router broadcasts to all the routers in the network the state of its locally attached links and IP subnets Each router constructs a complete topology view of the entire network based on these link state updates and computes its next-hop routing table based on this topology view

Link State Operation: Removals Removals are announcements with the metric set to infinity Adjacencies must be refreshed neighbors use hello protocol if a router loses a neighbor, then routes via that neighbor are recomputed send announcements with link metric to lost neighbor set to infinity

Link State: Shortest Path Dijkstra s Shortest Path First graph algorithm Use yourself as starting point Search outward on the graph and add router IDs as you expand the front Addresses are associated with routers Hence the SPF algorithm needs to deal only in the number of routers, not the number of routes

Dijsktra s Algorithm 1 Initialization for A: Notation: 2 N = {A} 3 for all nodes v in Graph 4 if v adjacent to A 5 then D(v) = c(a,v) 6 else D(v) = infinity 7 8 Loop 9 find w not in N such that D(w) is a minimum 10 add w to N 11 update D(v) for all v adjacent to w and not in N : 12 D(v) = min( D(v), D(w) + c(w,v) ) 13 /* new cost to v is either old cost to v or known 14 shortest path cost to w plus cost from w to v */ 15 until all nodes in N c(i,j): link cost from node i to j. cost infinite if not direct neighbors D(v): current value of cost of path from source to dest. v N : set of nodes whose least cost path definitively known

Dijkstra s algorithm: example Step 0 1 2 3 4 5 start N A AD ADE ADEB ADEBC ADEBCF D(B),p(B) 2,A 2,A 2,A D(C),p(C) 5,A 4,D 3,E 3,E D(D),p(D) 1,A D(E),p(E) infinity 2,D D(F),p(F) infinity infinity 4,E 4,E 4,E A E D C B F 2 2 1 3 1 1 2 5 3 5

Dijkstra s algorithm: example (2) Resulting shortest-path tree from A: B C A F D E Resulting forwarding table in A: destination B D E C F link (A,B) (A,D) (A,D) (A,D) (A,D)

OSPF Open Shortest Path First Open means it is public domain Uses Shortest Path First algorithm sometimes called the Dijkstra algorithm Current generation interior routing protocol based on link state concepts (RFC 1131, 10/1/89, obsoleted by OSPF v2, RFC 1723, 11/15/94) Supports hierarchies for scalability Fast convergence and loop avoidance OSPFv3 based on OSPFv2 designed to support IPv6

Hierarchical OSPF

Hierarchical OSPF Two-level hierarchy: local area and backbone. Link-state advertisements only in respective areas. Nodes in each area have detailed area topology; only know direction (shortest path) to networks in other areas. Area Border routers summarize distances to networks in the area and advertise them to other Area Border routers. Backbone routers: run an OSPF routing algorithm limited to the backbone. Boundary routers: connect to other ASs.

IS-IS Overview The Intermediate Systems to Intermediate System Routing Protocol (IS-IS) was originally designed to route the ISO Connectionless Network Protocol (CLNP). (ISO10589 or RFC 1142) Adapted for routing IP in addition to CLNP (RFC1195) as Integrated or Dual IS-IS IS-IS is a Link State Protocol similar to the Open Shortest Path First (OSPF). OSPF supports only IP

IS-IS Overview 3 network layer protocols play together to deliver the ISO defined Connectionless Network Service CLNP IS-IS ES-IS End System to Intermediate System All 3 protocols independently go over layer-2

Link State Algorithm Each router contains a database containing a map of the whole topology Links Their state (including cost) All routers have the same information All routers calculate the best path to every destination Any link state changes are flooded across the network Global spread of local knowledge

Border Gateway Protocol Introduction

BGP Protocol Basics Peering A C AS 100 AS 101 Routing Protocol used between ASes If you aren t connected to multiple ASes you don t need BGP Runs over TCP B E AS 102 D

Consider a typical small ISP Local network in one country May have multiple POPs in different cities Line to Internet International line providing transit connectivity Very, very expensive international line Doesn t yet need BGP

Small ISP with one upstream provider BGP to other large ISPs Provider IGP routes inside Static routes or IGP routes to small customers Small ISP Static or IGP routes inside Static default route to provider

What happens with other ISPs in the same region/country Similar setup Traffic between you and them goes over Your expensive line Their expensive line Traffic can be significant Your customers want to talk to their customers Same language/culture Local email, discussion lists, web sites

Keeping Local Traffic Local Upstream ISP Mainland Europe or USA Small ISP Small ISP UK

Consider a larger ISP with multiple upstreams Large ISP multi-homes to two or more upstream providers multiple connections to achieve: redundancy connection diversity increased speeds Use BGP to choose a different upstream for different destination addresses

A Large ISP with more than one upstream provider USA Upstream ISP Upstream ISP Mainland Europe ISP UK

Terminology: Policy Where do you want your traffic to go? It is difficult to get what you want, but you can try Control of how you accept and send routing updates to neighbours Prefer cheaper connections Prefer connections with better latency Load-sharing, etc

Policy (continued) Implementing policy: Accepting routes from some ISPs and not others Sending some routes to some ISPs and not to others Preferring routes from some ISPs over those from other ISPs

Policy Implementation You want to use a local line to talk to the customers of other local ISPs local peering You do not want other local ISPs to use your expensive international lines no free transit! So you need some sort of control over routing policies BGP can do this

Terminology: Peering and Transit Peering: getting connectivity to the network of other ISPs and just that network, no other networks Usually at zero cost (zero-settlement) Transit: getting connectivity though the other ISP to other ISP networks getting connectivity to rest of world (or part thereof) Usually at cost (customer-provider relationship)

Customers and Providers provider provider customer IP traffic customer Customer pays provider for access to the Internet

Big tier-1 providers $$$ $$$ traffic provider customer Large providers can charge twice for traffic $$$

The Peering Relationship $$$ $$$ peer provider traffic peer customer Peerings are mutual agreements. Both partners benefit

The Peering Relationship peer provider peer customer Peers provide transit between their respective customers traffic allowed traffic NOT allowed Peers do not provide transit between peers Peers (often) do not exchange $$$

Economic Relationships can get complex

Peering Wars Peer Reduces upstream transit costs Can increase end-to-end performance May be the only way to connect your customers to some part of the Internet ( Tier 1 ) Don t Peer You would rather have customers Peers are usually your competition Peering relationships may require periodic renegotiation Peering struggles are by far the most contentious issues in the ISP world! Peering agreements are often confidential.

Structure of the Internet Global Internet Core Global Transit / tier-1 Hyper Giants Large Content, Consumer, Hosting CDN IXP IXP IXP Regional Tier 2 Providers ISP 1 ISP 2 Customer IP Networks