Networking Network layer Three concepts Naming A way to identify - - PowerPoint PPT Presentation

networking network layer
SMART_READER_LITE
LIVE PREVIEW

Networking Network layer Three concepts Naming A way to identify - - PowerPoint PPT Presentation

Networking Network layer Three concepts Naming A way to identify the source/destination E.g., house address Routing Finding how to move towards the destination E.g., which airplane should the stuff go on


slide-1
SLIDE 1

Networking — Network layer

Three concepts

  • Naming
  • A way to identify the source/destination
  • E.g., house address
  • Routing
  • Finding “how to” move towards the destination
  • E.g., which airplane should the stuff go on
  • Forwarding
  • Actually “moving” towards the destination
  • E.g., Using airplane/truck/rail
slide-2
SLIDE 2

Network layer — Forwarding

slide-3
SLIDE 3

Network layer — Forwarding

Lets come up with an approach? Generalize Ethernet ideas?

slide-4
SLIDE 4

Network layer — Forwarding

slide-5
SLIDE 5

Attempt 1: Broadcast

Network layer — Forwarding

slide-6
SLIDE 6

Attempt 1: Broadcast

  • Send to everybody

Network layer — Forwarding

slide-7
SLIDE 7

Attempt 1: Broadcast

  • Send to everybody
  • Goods

Network layer — Forwarding

slide-8
SLIDE 8

Attempt 1: Broadcast

  • Send to everybody
  • Goods
  • Oh, well, simplicity

Network layer — Forwarding

slide-9
SLIDE 9

Attempt 1: Broadcast

  • Send to everybody
  • Goods
  • Oh, well, simplicity
  • Not-so-goods

Network layer — Forwarding

slide-10
SLIDE 10

Attempt 1: Broadcast

  • Send to everybody
  • Goods
  • Oh, well, simplicity
  • Not-so-goods
  • Oh, well, everything else

Network layer — Forwarding

slide-11
SLIDE 11

Attempt 1: Broadcast

  • Send to everybody
  • Goods
  • Oh, well, simplicity
  • Not-so-goods
  • Oh, well, everything else
  • Bandwidth overheads

Network layer — Forwarding

slide-12
SLIDE 12

Network layer — Forwarding

slide-13
SLIDE 13

Attempt 2: Time division Multiplexing

Network layer — Forwarding

slide-14
SLIDE 14

Attempt 2: Time division Multiplexing

  • Each source-destination pair assigned a time slot

Network layer — Forwarding

slide-15
SLIDE 15

Attempt 2: Time division Multiplexing

  • Each source-destination pair assigned a time slot
  • Can send data only during that slot

Network layer — Forwarding

slide-16
SLIDE 16

Attempt 2: Time division Multiplexing

  • Each source-destination pair assigned a time slot
  • Can send data only during that slot
  • Goods

Network layer — Forwarding

slide-17
SLIDE 17

Attempt 2: Time division Multiplexing

  • Each source-destination pair assigned a time slot
  • Can send data only during that slot
  • Goods
  • No collisions

Network layer — Forwarding

slide-18
SLIDE 18

Attempt 2: Time division Multiplexing

  • Each source-destination pair assigned a time slot
  • Can send data only during that slot
  • Goods
  • No collisions
  • Not-so-goods

Network layer — Forwarding

slide-19
SLIDE 19

Attempt 2: Time division Multiplexing

  • Each source-destination pair assigned a time slot
  • Can send data only during that slot
  • Goods
  • No collisions
  • Not-so-goods
  • Underutilization of resources

Network layer — Forwarding

slide-20
SLIDE 20

Network layer — Forwarding

slide-21
SLIDE 21

Attempt 3: Frequency division Multiplexing

Network layer — Forwarding

slide-22
SLIDE 22

Attempt 3: Frequency division Multiplexing

  • Each source-destination pair assigned a subset of resources

Network layer — Forwarding

slide-23
SLIDE 23

Attempt 3: Frequency division Multiplexing

  • Each source-destination pair assigned a subset of resources
  • Can use only “assigned” resources (e.g., bandwidth)

Network layer — Forwarding

slide-24
SLIDE 24

Attempt 3: Frequency division Multiplexing

  • Each source-destination pair assigned a subset of resources
  • Can use only “assigned” resources (e.g., bandwidth)
  • Goods

Network layer — Forwarding

slide-25
SLIDE 25

Attempt 3: Frequency division Multiplexing

  • Each source-destination pair assigned a subset of resources
  • Can use only “assigned” resources (e.g., bandwidth)
  • Goods
  • Predictable performance

Network layer — Forwarding

slide-26
SLIDE 26

Attempt 3: Frequency division Multiplexing

  • Each source-destination pair assigned a subset of resources
  • Can use only “assigned” resources (e.g., bandwidth)
  • Goods
  • Predictable performance
  • Not-so-goods

Network layer — Forwarding

slide-27
SLIDE 27

Attempt 3: Frequency division Multiplexing

  • Each source-destination pair assigned a subset of resources
  • Can use only “assigned” resources (e.g., bandwidth)
  • Goods
  • Predictable performance
  • Not-so-goods
  • Underutilization of resources

Network layer — Forwarding

slide-28
SLIDE 28

Network layer — Forwarding

slide-29
SLIDE 29

Attempt 2 and 3: Circuit Switching

Network layer — Forwarding

slide-30
SLIDE 30

Attempt 2 and 3: Circuit Switching

  • Source establishes connection

Network layer — Forwarding

slide-31
SLIDE 31

Attempt 2 and 3: Circuit Switching

  • Source establishes connection
  • Resources along the path are reserved

Network layer — Forwarding

slide-32
SLIDE 32

Attempt 2 and 3: Circuit Switching

  • Source establishes connection
  • Resources along the path are reserved
  • Source sends data

Network layer — Forwarding

slide-33
SLIDE 33

Attempt 2 and 3: Circuit Switching

  • Source establishes connection
  • Resources along the path are reserved
  • Source sends data
  • Transmit data using the reserved resources

Network layer — Forwarding

slide-34
SLIDE 34

Attempt 2 and 3: Circuit Switching

  • Source establishes connection
  • Resources along the path are reserved
  • Source sends data
  • Transmit data using the reserved resources
  • Source tears down connection

Network layer — Forwarding

slide-35
SLIDE 35

Attempt 2 and 3: Circuit Switching

  • Source establishes connection
  • Resources along the path are reserved
  • Source sends data
  • Transmit data using the reserved resources
  • Source tears down connection
  • Free resources for others to use

Network layer — Forwarding

slide-36
SLIDE 36

Network layer — Forwarding

slide-37
SLIDE 37

Circuit Switching

Network layer — Forwarding

slide-38
SLIDE 38

Circuit Switching

  • Goods:

Network layer — Forwarding

slide-39
SLIDE 39

Circuit Switching

  • Goods:
  • Predictable performance

Network layer — Forwarding

slide-40
SLIDE 40

Circuit Switching

  • Goods:
  • Predictable performance
  • Reliable delivery

Network layer — Forwarding

slide-41
SLIDE 41

Circuit Switching

  • Goods:
  • Predictable performance
  • Reliable delivery
  • Simple forwarding mechanism

Network layer — Forwarding

slide-42
SLIDE 42

Circuit Switching

  • Goods:
  • Predictable performance
  • Reliable delivery
  • Simple forwarding mechanism
  • Not-so-goods

Network layer — Forwarding

slide-43
SLIDE 43

Circuit Switching

  • Goods:
  • Predictable performance
  • Reliable delivery
  • Simple forwarding mechanism
  • Not-so-goods
  • Resource underutilization

Network layer — Forwarding

slide-44
SLIDE 44

Circuit Switching

  • Goods:
  • Predictable performance
  • Reliable delivery
  • Simple forwarding mechanism
  • Not-so-goods
  • Resource underutilization
  • Blocked connections

Network layer — Forwarding

slide-45
SLIDE 45

Circuit Switching

  • Goods:
  • Predictable performance
  • Reliable delivery
  • Simple forwarding mechanism
  • Not-so-goods
  • Resource underutilization
  • Blocked connections
  • Connection set up overheads

Network layer — Forwarding

slide-46
SLIDE 46

Circuit Switching

  • Goods:
  • Predictable performance
  • Reliable delivery
  • Simple forwarding mechanism
  • Not-so-goods
  • Resource underutilization
  • Blocked connections
  • Connection set up overheads
  • Per-connection state in switches (scalability problem)

Network layer — Forwarding

slide-47
SLIDE 47

Network layer — Forwarding

slide-48
SLIDE 48

Attempt 4: Packet Switching

Network layer — Forwarding

slide-49
SLIDE 49

Attempt 4: Packet Switching

  • Divide the message into packets

Network layer — Forwarding

slide-50
SLIDE 50

Attempt 4: Packet Switching

  • Divide the message into packets
  • Put destination address in the header of each packet

Network layer — Forwarding

slide-51
SLIDE 51

Attempt 4: Packet Switching

  • Divide the message into packets
  • Put destination address in the header of each packet
  • Just like shipping stuff

Network layer — Forwarding

slide-52
SLIDE 52

Attempt 4: Packet Switching

  • Divide the message into packets
  • Put destination address in the header of each packet
  • Just like shipping stuff
  • Each device stores a “look-up table”

Network layer — Forwarding

slide-53
SLIDE 53

Attempt 4: Packet Switching

  • Divide the message into packets
  • Put destination address in the header of each packet
  • Just like shipping stuff
  • Each device stores a “look-up table”
  • Whats the next hop towards the destination?

Network layer — Forwarding

slide-54
SLIDE 54

Attempt 4: Packet Switching

  • Divide the message into packets
  • Put destination address in the header of each packet
  • Just like shipping stuff
  • Each device stores a “look-up table”
  • Whats the next hop towards the destination?
  • Destination receives the packet(s)

Network layer — Forwarding

slide-55
SLIDE 55

Attempt 4: Packet Switching

  • Divide the message into packets
  • Put destination address in the header of each packet
  • Just like shipping stuff
  • Each device stores a “look-up table”
  • Whats the next hop towards the destination?
  • Destination receives the packet(s)
  • And reconstructs the message

Network layer — Forwarding

slide-56
SLIDE 56

Network layer — Forwarding

slide-57
SLIDE 57

Packet Switched forwarding

Network layer — Forwarding

slide-58
SLIDE 58

Packet Switched forwarding

  • Hop-by-hop forwarding

Network layer — Forwarding

slide-59
SLIDE 59

Packet Switched forwarding

  • Hop-by-hop forwarding
  • Each router has a “look-up table” (forwarding information base)

Network layer — Forwarding

slide-60
SLIDE 60

Packet Switched forwarding

  • Hop-by-hop forwarding
  • Each router has a “look-up table” (forwarding information base)
  • What should be stored in this table?

Network layer — Forwarding

slide-61
SLIDE 61

Packet Switched forwarding

  • Hop-by-hop forwarding
  • Each router has a “look-up table” (forwarding information base)
  • What should be stored in this table?

Network layer — Forwarding

slide-62
SLIDE 62

Packet Switched forwarding

  • Hop-by-hop forwarding
  • Each router has a “look-up table” (forwarding information base)
  • What should be stored in this table?
  • Prefix-based forwarding (longest-prefix matching)

Network layer — Forwarding

slide-63
SLIDE 63

Packet Switched forwarding

  • Hop-by-hop forwarding
  • Each router has a “look-up table” (forwarding information base)
  • What should be stored in this table?
  • Prefix-based forwarding (longest-prefix matching)
  • Maps prefixes to the next-hop

Network layer — Forwarding

slide-64
SLIDE 64

Network layer — Forwarding

slide-65
SLIDE 65

Packet Switching

Network layer — Forwarding

slide-66
SLIDE 66

Packet Switching

  • Goods:

Network layer — Forwarding

slide-67
SLIDE 67

Packet Switching

  • Goods:
  • No resource underutilization

Network layer — Forwarding

slide-68
SLIDE 68

Packet Switching

  • Goods:
  • No resource underutilization
  • A source can send more if others don’t use resources

Network layer — Forwarding

slide-69
SLIDE 69

Packet Switching

  • Goods:
  • No resource underutilization
  • A source can send more if others don’t use resources
  • No blocked connection problem

Network layer — Forwarding

slide-70
SLIDE 70

Packet Switching

  • Goods:
  • No resource underutilization
  • A source can send more if others don’t use resources
  • No blocked connection problem
  • No per-connection state

Network layer — Forwarding

slide-71
SLIDE 71

Packet Switching

  • Goods:
  • No resource underutilization
  • A source can send more if others don’t use resources
  • No blocked connection problem
  • No per-connection state
  • No set-up cost

Network layer — Forwarding

slide-72
SLIDE 72

Packet Switching

  • Goods:
  • No resource underutilization
  • A source can send more if others don’t use resources
  • No blocked connection problem
  • No per-connection state
  • No set-up cost
  • Not-so-goods:

Network layer — Forwarding

slide-73
SLIDE 73

Packet Switching

  • Goods:
  • No resource underutilization
  • A source can send more if others don’t use resources
  • No blocked connection problem
  • No per-connection state
  • No set-up cost
  • Not-so-goods:
  • Packet header overhead

Network layer — Forwarding

slide-74
SLIDE 74

Packet Switching

  • Goods:
  • No resource underutilization
  • A source can send more if others don’t use resources
  • No blocked connection problem
  • No per-connection state
  • No set-up cost
  • Not-so-goods:
  • Packet header overhead
  • Network failures become a problem

Network layer — Forwarding

slide-75
SLIDE 75

Networking — Network layer

Three concepts

  • Naming
  • A way to identify the source/destination
  • E.g., house address
  • Routing
  • Finding “how to” move towards the destination
  • E.g., which airplane should the stuff go on
  • Forwarding
  • Actually “moving” towards the destination
  • E.g., Using airplane/truck/rail
slide-76
SLIDE 76

Network layer — Example

C

1 2 3 1 7

B A Dest.

slide-77
SLIDE 77

Network layer — Routing

slide-78
SLIDE 78

Lets come up with a routing scheme

Network layer — Routing

slide-79
SLIDE 79

Network layer — Routing

C

1 2 3 1 7

B A Dest.

slide-80
SLIDE 80

Network layer — Routing

C

1 2 3 1 7

B A Dest.

A wants to find a path to Dest. {(A, 0)}

slide-81
SLIDE 81

Network layer — Routing

C

1 2 3 1 7

B A Dest.

A wants to find a path to Dest. {(A, 0)} A wants to find a path to Dest. {(A, 0), (B, 2)}

slide-82
SLIDE 82

Network layer — Routing

C

1 2 3 1 7

B A Dest.

A wants to find a path to Dest. {(A, 0)} A wants to find a path to Dest. {(A, 0), (B, 2)} A wants to find a path to Dest. {(A, 0), (C, 7)}

slide-83
SLIDE 83

Network layer — Routing

C

1 2 3 1 7

B A Dest.

A wants to find a path to Dest. {(A, 0)} A wants to find a path to Dest. {(A, 0), (B, 2)} A wants to find a path to Dest. {(A, 0), (C, 7)} Path to Dest. {(A, 0), (B, 2), (D, 3)}

slide-84
SLIDE 84

Network layer — Routing

C

1 2 3 1 7

B A Dest.

A wants to find a path to Dest. {(A, 0)} A wants to find a path to Dest. {(A, 0), (B, 2)} A wants to find a path to Dest. {(A, 0), (C, 7)} Path to Dest. {(A, 0), (B, 2), (D, 3)} Path to Dest. {(A, 0), (C, 7), (D, 1)}

slide-85
SLIDE 85

Network layer — Routing

C

1 2 3 1 7

B A Dest.

A wants to find a path to Dest. {(A, 0)} A wants to find a path to Dest. {(A, 0), (B, 2)} A wants to find a path to Dest. {(A, 0), (C, 7)} Path to Dest. {(A, 0), (B, 2), (D, 3)} A wants to find a path to Dest. {(A, 0), (B, 2), (C, 1)} Path to Dest. {(A, 0), (C, 7), (D, 1)}

slide-86
SLIDE 86

Network layer — Routing

C

1 2 3 1 7

B A Dest.

A wants to find a path to Dest. {(A, 0)} A wants to find a path to Dest. {(A, 0), (B, 2)} A wants to find a path to Dest. {(A, 0), (C, 7)} Path to Dest. {(A, 0), (B, 2), (D, 3)} A wants to find a path to Dest. {(A, 0), (B, 2), (C, 1)} Path to Dest. {(A, 0), (C, 7), (D, 1)} Path to Dest. {(A, 0), (B, 2), (C, 1), (D, 1)}

slide-87
SLIDE 87

Network layer — Routing

slide-88
SLIDE 88

Attempt 1: Dynamic Source Routing

Network layer — Routing

slide-89
SLIDE 89

Attempt 1: Dynamic Source Routing

  • Broadcast a Route Request Packet for destination d

Network layer — Routing

slide-90
SLIDE 90

Attempt 1: Dynamic Source Routing

  • Broadcast a Route Request Packet for destination d
  • Put source ID in the packet header

Network layer — Routing

slide-91
SLIDE 91

Attempt 1: Dynamic Source Routing

  • Broadcast a Route Request Packet for destination d
  • Put source ID in the packet header
  • At each router

Network layer — Routing

slide-92
SLIDE 92

Attempt 1: Dynamic Source Routing

  • Broadcast a Route Request Packet for destination d
  • Put source ID in the packet header
  • At each router
  • If a path not known to the destination

Network layer — Routing

slide-93
SLIDE 93

Attempt 1: Dynamic Source Routing

  • Broadcast a Route Request Packet for destination d
  • Put source ID in the packet header
  • At each router
  • If a path not known to the destination
  • Put its {ID, cost} in the packet header

Network layer — Routing

slide-94
SLIDE 94

Attempt 1: Dynamic Source Routing

  • Broadcast a Route Request Packet for destination d
  • Put source ID in the packet header
  • At each router
  • If a path not known to the destination
  • Put its {ID, cost} in the packet header
  • Broadcast the Route Request Packet

Network layer — Routing

slide-95
SLIDE 95

Attempt 1: Dynamic Source Routing

  • Broadcast a Route Request Packet for destination d
  • Put source ID in the packet header
  • At each router
  • If a path not known to the destination
  • Put its {ID, cost} in the packet header
  • Broadcast the Route Request Packet
  • Else

Network layer — Routing

slide-96
SLIDE 96

Attempt 1: Dynamic Source Routing

  • Broadcast a Route Request Packet for destination d
  • Put source ID in the packet header
  • At each router
  • If a path not known to the destination
  • Put its {ID, cost} in the packet header
  • Broadcast the Route Request Packet
  • Else
  • Respond with a Route Reply packet

Network layer — Routing

slide-97
SLIDE 97

Attempt 1: Dynamic Source Routing

  • Broadcast a Route Request Packet for destination d
  • Put source ID in the packet header
  • At each router
  • If a path not known to the destination
  • Put its {ID, cost} in the packet header
  • Broadcast the Route Request Packet
  • Else
  • Respond with a Route Reply packet
  • Put known path in the packet header

Network layer — Routing

slide-98
SLIDE 98

Attempt 1: Dynamic Source Routing

  • Broadcast a Route Request Packet for destination d
  • Put source ID in the packet header
  • At each router
  • If a path not known to the destination
  • Put its {ID, cost} in the packet header
  • Broadcast the Route Request Packet
  • Else
  • Respond with a Route Reply packet
  • Put known path in the packet header
  • Challenge?

Network layer — Routing

slide-99
SLIDE 99

Network layer — Routing

C

1 2 3 1 7

B A Dest.

slide-100
SLIDE 100

Network layer — Routing

C

1 2 3 1 7

B A Dest.

{(A-B, 0), (A-C, 7)}

slide-101
SLIDE 101

Network layer — Routing

C

1 2 3 1 7

B A Dest.

{(A-B, 0), (A-C, 7)} {(A-B, 2), (B-C, 1), (B-D, 3)}

slide-102
SLIDE 102

Network layer — Routing

C

1 2 3 1 7

B A Dest.

{(A-B, 0), (A-C, 7)} {(A-B, 2), (B-C, 1), (B-D, 3)} {(A-C, 7), (B-C, 1)}

slide-103
SLIDE 103

Network layer — Routing

C

1 2 3 1 7

B A Dest.

{(A-B, 0), (A-C, 7)} {(A-B, 2), (B-C, 1), (B-D, 3)} {(A-C, 7), (B-C, 1)} {(B-D, 3), (C-D, 1)}

slide-104
SLIDE 104

Network layer — Routing

C

1 2 3 1 7

B A Dest.

{(A-B, 0), (A-C, 7)} {(A-B, 2), (B-C, 1), (B-D, 3)} {(A-C, 7), (B-C, 1)} {(B-D, 3), (C-D, 1)} {(A-B, 0), (A-C, 7)}

slide-105
SLIDE 105

Network layer — Routing

C

1 2 3 1 7

B A Dest.

{(A-B, 0), (A-C, 7)} {(A-B, 2), (B-C, 1), (B-D, 3)} {(A-C, 7), (B-C, 1)} {(B-D, 3), (C-D, 1)} {(A-B, 0), (A-C, 7)} {(B-D, 3), (C-D, 1)}

slide-106
SLIDE 106

Network layer — Routing

C

1 2 3 1 7

B A Dest.

{(A-B, 0), (A-C, 7)} {(A-B, 2), (B-C, 1), (B-D, 3)} {(A-C, 7), (B-C, 1)} {(B-D, 3), (C-D, 1)} {(A-B, 0), (A-C, 7)} {(B-D, 3), (C-D, 1)} {(A-C, 7), (B-C, 1)}

slide-107
SLIDE 107

Network layer — Routing

slide-108
SLIDE 108

Attempt 2: Link State Routing

Network layer — Routing

slide-109
SLIDE 109

Attempt 2: Link State Routing

  • Each router maintains its local “link state” (LS)

Network layer — Routing

slide-110
SLIDE 110

Attempt 2: Link State Routing

  • Each router maintains its local “link state” (LS)
  • Each router periodically “floods” its LS

Network layer — Routing

slide-111
SLIDE 111

Attempt 2: Link State Routing

  • Each router maintains its local “link state” (LS)
  • Each router periodically “floods” its LS
  • And forwards all the LS received from other routers

Network layer — Routing

slide-112
SLIDE 112

Attempt 2: Link State Routing

  • Each router maintains its local “link state” (LS)
  • Each router periodically “floods” its LS
  • And forwards all the LS received from other routers
  • At one point

Network layer — Routing

slide-113
SLIDE 113

Attempt 2: Link State Routing

  • Each router maintains its local “link state” (LS)
  • Each router periodically “floods” its LS
  • And forwards all the LS received from other routers
  • At one point
  • Every router knows the entire topology

Network layer — Routing

slide-114
SLIDE 114

Attempt 2: Link State Routing

  • Each router maintains its local “link state” (LS)
  • Each router periodically “floods” its LS
  • And forwards all the LS received from other routers
  • At one point
  • Every router knows the entire topology
  • Run a shortest path algorithm (e.g., Dijkstra) locally

Network layer — Routing

slide-115
SLIDE 115

Attempt 2: Link State Routing

  • Each router maintains its local “link state” (LS)
  • Each router periodically “floods” its LS
  • And forwards all the LS received from other routers
  • At one point
  • Every router knows the entire topology
  • Run a shortest path algorithm (e.g., Dijkstra) locally
  • Find path to the destination

Network layer — Routing

slide-116
SLIDE 116

Attempt 2: Link State Routing

  • Each router maintains its local “link state” (LS)
  • Each router periodically “floods” its LS
  • And forwards all the LS received from other routers
  • At one point
  • Every router knows the entire topology
  • Run a shortest path algorithm (e.g., Dijkstra) locally
  • Find path to the destination
  • More importantly, find next-hop to the destination

Network layer — Routing

slide-117
SLIDE 117

Attempt 2: Link State Routing

  • Each router maintains its local “link state” (LS)
  • Each router periodically “floods” its LS
  • And forwards all the LS received from other routers
  • At one point
  • Every router knows the entire topology
  • Run a shortest path algorithm (e.g., Dijkstra) locally
  • Find path to the destination
  • More importantly, find next-hop to the destination
  • Challenge?

Network layer — Routing

slide-118
SLIDE 118

Network layer — Routing

slide-119
SLIDE 119

Attempt 3: Distance Vector Routing

Network layer — Routing

slide-120
SLIDE 120

Attempt 3: Distance Vector Routing

  • Each router

Network layer — Routing

slide-121
SLIDE 121

Attempt 3: Distance Vector Routing

  • Each router
  • maintains its “current distance to destination”

Network layer — Routing

slide-122
SLIDE 122

Attempt 3: Distance Vector Routing

  • Each router
  • maintains its “current distance to destination”
  • Periodically announces it to all its neighbors

Network layer — Routing

slide-123
SLIDE 123

Attempt 3: Distance Vector Routing

  • Each router
  • maintains its “current distance to destination”
  • Periodically announces it to all its neighbors
  • Update its local table

Network layer — Routing

slide-124
SLIDE 124

Attempt 3: Distance Vector Routing

  • Each router
  • maintains its “current distance to destination”
  • Periodically announces it to all its neighbors
  • Update its local table
  • d(A, dest) = min{d(A, neighbor) + d(neighbor, dest)}

Network layer — Routing

slide-125
SLIDE 125

Attempt 3: Distance Vector Routing

  • Each router
  • maintains its “current distance to destination”
  • Periodically announces it to all its neighbors
  • Update its local table
  • d(A, dest) = min{d(A, neighbor) + d(neighbor, dest)}
  • {dest — distance, neighbor-that-minimizes-distance}

Network layer — Routing

slide-126
SLIDE 126

Attempt 3: Distance Vector Routing

  • Each router
  • maintains its “current distance to destination”
  • Periodically announces it to all its neighbors
  • Update its local table
  • d(A, dest) = min{d(A, neighbor) + d(neighbor, dest)}
  • {dest — distance, neighbor-that-minimizes-distance}
  • Broadcast to all its neighbors

Network layer — Routing

slide-127
SLIDE 127