An Radical but Incrementally Deployable Vision for Future Internet - - PowerPoint PPT Presentation

▶
an radical but incrementally deployable vision for future
SMART_READER_LITE
LIVE PREVIEW

An Radical but Incrementally Deployable Vision for Future Internet - - PowerPoint PPT Presentation

Nov 17, 2022 37 likes •479 views

An Radical but Incrementally Deployable Vision for Future Internet Architecture James McCauley, Yotam Harchol, Aurojit Panda, Barath Raghavan, Scott Shenker (UC Berkeley, NYU, USC, ICSI) The Internet architecture of today Based on IP

slide-1
SLIDE 1

An Radical but Incrementally Deployable Vision for Future Internet Architecture

James McCauley, Yotam Harchol, Aurojit Panda, Barath Raghavan, Scott Shenker

(UC Berkeley, NYU, USC, ICSI)

slide-2
SLIDE 2

The Internet architecture of today

  • Based on IP
  • Spectacularly successful architecture!

History of handling…

– Incredible growth – New use cases

  • But the eternal question…

Is the current architecture good enough?

slide-3
SLIDE 3

Is the current architecture good enough?

  • ~20 years ago

– Not good enough! We need IPv6.

  • Since then, proposals driven by...

– Content (NDN, Netinf), Mobility (MobilityFirst), Cloud

(NEBULA), Economics (ChoiceNet), Flexibility (XIA), Security (SCION), …

– And more! – NSF: “it is no longer clear that emerging and future needs ...

can be met by ... incremental changes to the current Internet”

slide-4
SLIDE 4

Problem statement

  • Can we make the Internet fundamentally more

extensible?

– i.e., actually get good architectural ideas deployed!

  • We think so.
slide-5
SLIDE 5

What is an Internet architecture?

  • It’s a design in which…

data from some endpoint travels through some intermediate nodes which process the data according to architecture’s data plane until terminating at one or more endpoints elsewhere

  • It must be intended to do this globally
  • It is a composition of domains (“ASes” today)
slide-6
SLIDE 6

Digging into the data plane

  • Collection of layered protocols
  • Internet architecture centers on this one

(the lowest global one)

– Always IP on today’s Internet – It’s a “universal narrow waist”

L7 - Application L4 - Transport L3 - Internet L2 - Link L1 - Physical

slide-7
SLIDE 7

The universal narrow waist

  • Often (rightly!) credited for Internet’s success
  • Single global protocol is easiest way to achieve

goal of connecting the world!

  • But as we look beyond basic connectivity…

universal narrow waist is the single biggest impediment to architectural change

slide-8
SLIDE 8

The universal narrow waist

  • Universal narrow waist has good cohesion

– .. a narrow set of related responsibilities

  • And has good (loose) coupling with other layers

– .. can run atop many different protocols at layer below – .. and many different protocols can run above it

  • This is great !

... but ...

slide-9
SLIDE 9

The universal narrow waist

  • On a different axis, IP is terribly coupled

– Enormous number of routers must simultaneously agree

  • n single protocol

(or one of two if you count IPv4 and IPv6 separately)

  • Like any tightly coupled system, it’s tough to change

– Local changes have nonlocal effects or dependencies

  • Coupling crosses every set of stakeholders

– Makes difficult to align changes with all priorities

slide-10
SLIDE 10

Return to the problem statement

  • Can we make the Internet fundamentally more

extensible?

slide-11
SLIDE 11

Return to the problem statement

  • Can we make the Internet fundamentally more

extensible?

  • Yes. By removing the universal narrow waist.
slide-12
SLIDE 12

Removing the universal narrow waist

How?

Two steps.

slide-13
SLIDE 13

Step 1: Fix layering

L7 - Application L4 - Transport L3 - Internet L2 - Link L1 - Physical

slide-14
SLIDE 14

Step 1: Fix layering

  • We’re missing a layer!
  • Internet isn’t composition of L2 networks…

it’s a composition of domains

  • Already encoded in control plane!

L7 - Application L4 - Transport L3 - Internet L2 - Link L1 - Physical

slide-15
SLIDE 15

Step 1: Fix layering

  • We’re missing a layer!
  • Internet isn’t composition of L2 networks…

it’s a composition of domains

  • Already encoded in control plane!

L7 - Application L4 - Transport L3 - Internet L2 - Link L1 - Physical L7 - Application L4 - Transport L3 - Pipe L2 - Link L1 - Physical L3.5 - Global

slide-16
SLIDE 16

Step 1: Fix layering

  • We’re missing a layer!
  • Internet isn’t composition of L2 networks…

it’s a composition of domains

  • Already encoded in control plane!
  • Decouples how data is delivered

within/across domain from global protocol

  • .. and how one domain delivers internally

from how another delivers internally

L7 - Application L4 - Transport L3 - Internet L2 - Link L1 - Physical L7 - Application L4 - Transport L3 - Pipe L2 - Link L1 - Physical L3.5 - Global

slide-17
SLIDE 17

Removing the universal narrow waist

1.Decouple interdomain and intradomain data planes (separate global and pipe layers)

slide-18
SLIDE 18

Step 2: Rethink how to add features

  • Traditionally via upgrade model

– Define new version of IP with new features – Replace the old version (or try, anyway...)

  • Even if you don’t care about new features…

you care that what you’re using is being obsoleted!

slide-19
SLIDE 19

Step 2: Rethink how to add features

  • We advocate a coexistence model

– Embrace multiple coexisting architectures

  • Additive:

– If new features don’t benefit you, ignore it – Domains are footing the bill: ability to ignore architectures

they don’t care about is natural

  • Only feasible because we separated internal and

external data planes

slide-20
SLIDE 20

Removing the universal narrow waist

1.Decouple interdomain and intradomain data planes (separate global and pipe layers) 2.Embrace multiple coexisting global layer protocols instead of upgrading a single one

slide-21
SLIDE 21

Removing the universal narrow waist

1.Decouple interdomain and intradomain data planes (separate global and pipe layers) 2.Embrace multiple coexisting global layer protocols instead of upgrading a single one

No more universal narrow waist!

 Global protocols are no longer universal

(Not on every router or even every domain)

 It’s not narrow

(Coexisting protocols)

slide-22
SLIDE 22

Inside a domain

Domain A

IP+NDN

slide-23
SLIDE 23

Domain A Domain C Domain B

IP+NDN Legacy IP-Only IP+NDN

Inside a domain

slide-24
SLIDE 24

Domain A Domain C Domain B

IP+NDN Legacy IP-Only IP+NDN

$ $

Inside a domain

slide-25
SLIDE 25

Domain A Domain C Domain B

IP+NDN Legacy IP-Only IP+NDN

Both NDN and IP packets

Inside a domain

slide-26
SLIDE 26

Domain A Domain C Domain B

IP+NDN Legacy IP-Only IP+NDN

Global layer router which implements IP and NDN

Inside a domain

slide-27
SLIDE 27

Domain A Domain C Domain B

IP+NDN Legacy IP-Only IP+NDN

Global layer router which implements IP and NDN Pipe layer router implements … ?

Inside a domain

slide-28
SLIDE 28

Domain A Domain C Domain B

IP+NDN Legacy IP-Only IP+NDN

Global layer router which implements IP and NDN Pipe layer router implements another IP at the pipe layer

Inside a domain

slide-29
SLIDE 29

Host initialization

To Neighboring Domain

slide-30
SLIDE 30

Host initialization

To Neighboring Domain

1.Host arrives

slide-31
SLIDE 31

Host initialization

To Neighboring Domain

1.Host arrives

What protocols does this domain speak?!

slide-32
SLIDE 32

Host initialization

Bootstrap To Neighboring Domain

1.Host arrives 2.Bootstrap to learn which pipe and global protocols supported

slide-33
SLIDE 33

Host initialization

DHCP (Pipe) To Neighboring Domain

1.Host arrives 2.Bootstrap to learn which pipe and global protocols supported 3.Configure pipe layer (e.g. DHCP for pipe layer IP address)

slide-34
SLIDE 34

Host initialization

1.Host arrives 2.Bootstrap to learn which pipe and global protocols supported 3.Configure pipe layer (e.g. DHCP for pipe layer IP address) 4.Configure global layer (e.g., DHCP for global layer IP address)

To Neighboring Domain DHCP (Global)

slide-35
SLIDE 35

Host initialization

1.Host arrives 2.Bootstrap to learn which pipe and global protocols supported 3.Configure pipe layer (e.g. DHCP for pipe layer IP address) 4.Configure global layer (e.g., DHCP for global layer IP address) 5.Initialization complete

To Neighboring Domain

slide-36
SLIDE 36

Multiprotocol web

To Neighboring Domain Link (Eth) Pipe (IP) Global (IP) Transport (TCP) App (HTTP)

Downloading web page with http: URL

slide-37
SLIDE 37

Multiprotocol web

Link (Eth) To Neighboring Domain Pipe (IP) Global (NDN) Transport (NDN chunks)

Downloading resources with ndnchunks: URL

slide-38
SLIDE 38

A bit more concretely...

  • Devil is always in the details, but…
  • Only two major mechanistic components

– Pipes to carry global protocols – Bootstrap protocol so hosts understand the domain

they’re attached to

  • Together, these form a framework for architectural

coexistence

slide-39
SLIDE 39

Our contribution

  • A framework that allows incremental, side-by-side

deployment of new architectures

  • And is itself incrementally deployable
slide-40
SLIDE 40

A little context

  • Approaches to handle heterogeneity (Clark):

– Conversion

  • Maps between different technologies

– Overlays (Spanning)

  • Can mean fairly different things

– Underlays

  • MPLS
slide-41
SLIDE 41

A quick reflection

  • Goal: enable extensibility in Internet architecture
  • Problem: the universal narrow waist ( ️

️ ❗️ ❗️ )

  • Solution: remove it!

– Decouple intradomain and interdomain data planes – Embrace coexistence of interdomain protocols

  • Result:

– An incrementally deployable design – .. which can incrementally deploy new architectures

slide-42
SLIDE 42

A quick tangent

  • Internet today relies on specialized data plane HW

– It’s more cost effective – Replacing every router with SW on general-purpose HW

is out of the question…

– .. but replacing only global layer routers seems feasible – Huge reduction of risk & investment for experimentation

slide-43
SLIDE 43

Conclusion

  • On one hand, this work is dull
  • On the other, we think it’s incredibly exciting

– An Internet beyond just connectivity – A dynamic architectural ecosystem

  • An invitation to architects or would-be architects:

– Let’s work together to make this happen

slide-44
SLIDE 44

Thank You