Arguments for Separating Edges from Transit Core by Dan Jen, - - PowerPoint PPT Presentation

▶
arguments for separating edges from transit core
SMART_READER_LITE
LIVE PREVIEW

Arguments for Separating Edges from Transit Core by Dan Jen, - - PowerPoint PPT Presentation

Mar 06, 2024 507 likes •863 views

Arguments for Separating Edges from Transit Core by Dan Jen, Michael Meisel, He Yan, Dan Massey, Lan Wang, Beichuan Zhang, Lixia Zhang presented by Dan Jen University of California, Los Angeles 1 Routing Scalability is a Hot Topic 2

slide-1
SLIDE 1

1

Arguments for Separating Edges from Transit Core

by

Dan Jen, Michael Meisel, He Yan, Dan Massey, Lan Wang, Beichuan Zhang, Lixia Zhang

presented by

Dan Jen

University of California, Los Angeles

slide-2
SLIDE 2

2

Routing Scalability is a Hot Topic

slide-3
SLIDE 3

3

Will Routers Be Able to Keep Up?

  • No consensus

– Yes! – No!

  • Correct Answer:

– Maybe... but what if they can't?

slide-4
SLIDE 4

4

  • BSTS. IRTF RRG.
  • Routing Research Group

– “One of the key topics facing the Internet today is the issue

  • f Interdomain routing scalability - the need for a new routing
  • architecture. Currently, a sub-group of the IRTF RRG has

been created to define and investigate what the possible requirements for such an architecture might be and to also explore possible methods.”

  • Basically, come up with a proposal that helps

scale the Internet for the foreseeable future.

slide-5
SLIDE 5

5

Many Scalability Proposals, No Verdict yet

LISP APT Shim6 Multipath Transport Six/One Router ILNP TRRP

slide-6
SLIDE 6

6

Many Scalability Proposals, No Verdict yet

Can We Help with the Debate? LISP APT Shim6 Multipath Transport Six/One Router ILNP TRRP

slide-7
SLIDE 7

7

Our Contributions

APT LISP TRRP

Six/One Router

Shim6

Multipath Transport ILNP

Separation Elimination

slide-8
SLIDE 8

8

Our Contributions

APT LISP TRRP

Six/One Router

Shim6

Multipath Transport ILNP

Separation Elimination

slide-9
SLIDE 9

9

Our Contributions

APT LISP TRRP

Six/One Router

Shim6

Multipath Transport ILNP

Separation > Elimination

slide-10
SLIDE 10

10

Observation: Two Camps

  • All proposals use aggregation as the

mechanism for routing scalability.

  • Ability to aggregate(and thus scale) comes in
  • ne of two ways:

– Separate non-aggregatable prefixes from global

routing scope.

– Eliminate the use of non-aggregatable addresses

altogether.

slide-11
SLIDE 11

11

Separation

  • Edge networks moved outside the scope of

global routing. Only transit network prefixes are globally routable.

  • Edge networks are mapped to routable,

aggregatable provider addresses.

– Each Separation proposal has a mapping system

Example: Map & Encap

slide-12
SLIDE 12

12

Transit Core Transit Core

P1 P2

ISP1 ISP1 ISP2 ISP2 Site2 Site2 Edge Space Edge Space Site1 Site1

Src Dst

ISP3 ISP3

slide-13
SLIDE 13

13

Site2 Site2 Site1 Site1

Src Dst

Dst Transit Core Transit Core Edge Space Edge Space

P1 P2

ISP1 ISP1 ISP2 ISP2 ISP3 ISP3

slide-14
SLIDE 14

14

Site2 Site2

Src Dst

Site1 Site1 Transit Core Transit Core Edge Space Edge Space

P1 P2

ISP1 ISP1 ISP2 ISP2 ISP3 ISP3 Dst

slide-15
SLIDE 15

15

Site2 Site2

Src Dst

Site1 Site1 Transit Core Transit Core Edge Space Edge Space

P1 P2

ISP1 ISP1 ISP2 ISP2 ISP3 ISP3 Dst

slide-16
SLIDE 16

16

Site2 Site2

Src Dst

Site1 Site1 Transit Core Transit Core Edge Space Edge Space

P1 P2

ISP1 ISP1 ISP2 ISP2 ISP3 ISP3 Dst

P2

slide-17
SLIDE 17

17

Site2 Site2

Src Dst

Site1 Site1 Transit Core Transit Core Edge Space Edge Space

P1 P2

ISP1 ISP1 ISP2 ISP2 ISP3 ISP3 Dst

P2

slide-18
SLIDE 18

18

Site2 Site2

Src Dst

Site1 Site1 Transit Core Transit Core Edge Space Edge Space

P1 P2

ISP1 ISP1 ISP2 ISP2 ISP3 ISP3 Dst

P2

slide-19
SLIDE 19

19

Site2 Site2

Src Dst

Site1 Site1 Transit Core Transit Core Edge Space Edge Space

P1 P2

ISP1 ISP1 ISP2 ISP2 ISP3 ISP3 Dst

slide-20
SLIDE 20

20

Site2 Site2

Src Dst

Site1 Site1 Transit Core Transit Core Edge Space Edge Space

P1 P2

ISP1 ISP1 ISP2 ISP2 ISP3 ISP3 Dst

slide-21
SLIDE 21

21

Site2 Site2

Src Dst

Site1 Site1 Transit Core Transit Core Edge Space Edge Space

P1 P2

ISP1 ISP1 ISP2 ISP2 ISP3 ISP3 Dst

slide-22
SLIDE 22

22

Elimination

  • Keeps all players in routable scope, but

eliminates the use of unaggregatable prefixes

  • Hosts are upgraded with the ability to utilize

multiple IP addresses. Example: Multipath Transport

slide-23
SLIDE 23

23

3.4/16

ISP2 ISP2

host1

Multihomed Multihomed Edge Site1 Edge Site1

1.2.1.1 3.4.1.1

1.2/16

ISP1 ISP1

host2

Multihomed Multihomed Edge Site2 Edge Site2

1.2.2.1 3.4.2.1

1.2.1/24 3.4.1/24 1.2.2/24 3.4.2/24

slide-24
SLIDE 24

24

3.4/16

ISP2 ISP2

host1

Multihomed Multihomed Edge Site1 Edge Site1

1.2.1.1 3.4.1.1

1.2/16

ISP1 ISP1

host2

Multihomed Multihomed Edge Site2 Edge Site2

1.2.2.1 3.4.2.1

1.2.1/24 3.4.1/24 1.2.2/24 3.4.2/24

slide-25
SLIDE 25

25

3.4/16

ISP2 ISP2

host1

Multihomed Multihomed Edge Site1 Edge Site1

1.2.1.1 3.4.1.1

1.2/16

ISP1 ISP1

host2

Multihomed Multihomed Edge Site2 Edge Site2

1.2.2.1 3.4.2.1

1.2.1/24 3.4.1/24 1.2.2/24 3.4.2/24

slide-26
SLIDE 26

26

Our Claim: Separation is Better

  • Who deploys scalability solution?

– Separation solutions deployed by networks – Elimination solutions deployed by hosts

  • Who benefits from scalability?

– Networks only

slide-27
SLIDE 27

27

Elimination: Misalignment of Cost and Benefit

  • Must Fight Inertia

– Hosts don't directly benefit from routing scalability – Other incentives unrelated to scalability offered by

elimination proposals to convince hosts to upgrade.

– Deployment speed depends upon this incentive's

desirability.

  • No guarantee that enough hosts will upgrade

before it's too late.

slide-28
SLIDE 28

28

Separation Ties Demand with Deployment

  • Under separation, affected parties are the ones

with the power to fix their problems.

  • Networks that need scalability can deploy the

new solution and benefit immediately

– APT, basically an interdomain Viaggre (and more!) – What's Viaggre? See next presentation.

slide-29
SLIDE 29

29

Other Reasons for Choosing Separation

  • Easier Rollout of New Protocols

– Edge Networks and Transit Networks can deploy new

protocols independently of one another.

  • DDoS Mitigation

– Mapping System is a natural mounting point for DDoS

defense

  • Explicit Ingress Traffic Engineering

– Can be placed in mapping entries. – No more need for prefix splitting and BGP trickery

* Details Are In The Paper *

slide-30
SLIDE 30

30

(Separation > Elimination) != (Elimination Schemes are Useless)

  • Use separation for scalability
  • But retain non-scalability benefits offered by

elimination schemes.

– Example: Multipath transport

  • Often, these benefits can be added to

separation schemes

  • Again, details are in paper.
slide-31
SLIDE 31

31

3.4/16

ISP2 ISP2

host1

Multihomed Multihomed Edge Site Edge Site

1.2.1.1 3.4.1.1

1.2/16

ISP1 ISP1

host2

Multihomed Multihomed Edge Site Edge Site

1.2.2.1 3.4.2.1

1.2.1/24 3.4.1/24 1.2.2/24 3.4.2/24

slide-32
SLIDE 32

32

In Conclusion...

slide-33
SLIDE 33

33

Before our work, the Routing Research Group argued endlessly about all of the scalability solutions

  • n the table.
slide-34
SLIDE 34

34

Now, we hope the Routing Research Group can stop arguing about Elimination solutions to scalability, and argue endlessly about other things.

slide-35
SLIDE 35

35

Questions? Comments?

jenster@cs.ucla.edu