bgp border gateway protocol ee122 section 3. border gateway protocol protocol for inter-domain...

20
BGP Border Gateway Protocol EE122 Section 3

Upload: paulina-brown

Post on 16-Dec-2015

218 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

BGPBorder Gateway Protocol

EE122 Section 3

Page 2: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

Border Gateway Protocol

• Protocol for inter-domain routing• Designed for policy and privacy• Why not distance-vector?– Shortest path may not be policy-compliant– …and policies vary across domains!

• Why not link-state?– Everybody knows everything – privacy goes for a

toss!• Enter path vector!

Page 3: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

BGP: Path Vector

1 2

0

A B

A: 1 B: 2

A: 1 B: 2

Page 4: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

BGP: Path Vector

1 2

0

A B

B: 0 2 A: 0 1

A: 1 B: 2

A: 0 1B: 0 2

Page 5: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

BGP: Path Vector

1 2

0

A B

A: 1B: 1 0 2

A: 2 0 1B: 2

A: 0 1B: 0 2

Page 6: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

BGP: Path Vector

1 2

0

A B

A: 1B: 1 0

A: 2 0 1B: 2

A: 0 1B: 0 2

Withdrawal - B: 0 2Advertise - B: 0

A: 0 1B: 0

Page 7: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

BGP Relationships

• Provider -> Customer:• Peer <-> Peer:

1 2

0

A B C

A: 1B: 1C: 0 1

A: 1 2B: 2C: 0 2

A: 1 0B: 1 0C: 0

Page 8: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

It’s all about the money!

• Customer pays provider• Peers don’t pay each other – Assume equal flow both ways

• Routing policies try to minimize payment

Page 9: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

Typical Export Policy

Destination prefix advertised by… Export route to…

CustomerEveryone

(providers, peers, other customers)

Peer Customers

Provider Customers

We’ll refer to these as the “Gao-Rexford” rules(capture common -- but not required! -- practice!)

Page 10: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

Gao-Rexford

peers

providers

customers

With Gao-Rexford, the AS policy graph is a DAG (directed acyclic graph) and routes are “valley free”

Page 11: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

Packets flow where money flows

• Route Selection– Preference Order: Customer > Peer > Provider

• Route Export Policy– Peers provide transit between their customers– Peers do not provide transit to each other

Page 12: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

Route Selection: Customer > Peer

• Provider -> Customer:• Peer <-> Peer:

1 2

0

A B C

A: 1B: 1C: 0 1

A: 1 2B: 2C: 0 2

A: 1 0B: 1 0C: 0

Page 13: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

Route Selection : Peer > Provider

• Provider -> Customer:• Peer <-> Peer:

1 2

0

A B C

A: 1B: 1C: 0 1

A: 1 2B: 2C: 0 2

A: 1 0B: 1 0C: 0

Page 14: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

Route Selection : Provider (no choice)

• Provider -> Customer:• Peer <-> Peer:

1 2

0

A B C

A: 1B: 1C: 0 1

A: 1 2B: 2C: 0 2

A: 1 0B: 1 0C: 0

Page 15: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

Route Export policy: Advertise customers

• Provider -> Customer:• Peer <-> Peer:

1 2

0

A B C

A: 1B: 1C: 0 1

A: 1 2B: 2C: 0 2

A: 1 0B: 1 0C: 0

Page 16: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

BGP Routing Game!

• No talking! Communicate via pieces of paper• Route selection precedence– Customer > Peer > Provider

• Export policy: Advertise customers• Message format:– Withdrawal - <host network>: <path>– Advertise - <host network>: <path>– Ping - <destination>

• Goal: Reach steady state

Page 17: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

Cogent

Comcast Verizon

Netflix Facebook Google

People on the West

coastAkamai CDN

People in Kansas City

Level3 Google Fiber

People on the East

coast

Time Warner Cable

People in the South

Page 18: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

Comcast Verizon

Netflix Facebook Google

People on the West

coastAkamai CDN

People in Kansas City

Level3 Google Fiber

People on the East

coast

Time Warner Cable

People in the South

South: TWC

West, Akamai:Comcast

West, Akamai:Comcast

Cogent

FB, Google: Level3

FB, Google: Level3

Google, KC: Google Fiber

East, Akamai:Verizon

FB, Google:Level3

Netflix: Cogent

Netflix: Cogent

Page 19: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

Cogent

Comcast Verizon

Netflix Facebook Google

People on the West

coastAkamai CDN

People in Kansas City

Level3 Google Fiber

People on the East

coast

Time Warner Cable

People in the South

West, Akamai:Comcast, Cogent

FB, Google: Level3, Cogent

East, Akamai:Verizon, Level3

East, Akamai:Verizon, Level3

KC: Google Fiber, Level3

Page 20: BGP Border Gateway Protocol EE122 Section 3. Border Gateway Protocol Protocol for inter-domain routing Designed for policy and privacy Why not distance-vector?

Cogent

Comcast Verizon

Netflix Facebook Google

People on the West

coastAkamai CDN

People in Kansas City

Level3 Google Fiber

People on the East

coast

Time Warner Cable

People in the South

East, Akamai:Verizon, Level3,Cogent

West, Akamai:Verizon, Level3,Cogent