Communication - Princeton University

Download Report

Transcript Communication - Princeton University

Future Internet Architectures:
Toward an Architecture-Agnostic Architecture
Jennifer Rexford
Princeton University
http://www.cs.princeton.edu/~jrex
1
Deciding Not to Decide
• Flexibility has been key to the Internet’s success
– Many different applications and services
– Beyond anything the initial designers ever envisioned
• Today this flexibility is limited to the end systems
– Not surprisingly, this is where we have seen innovation
• And, the “inside” is quite difficult to change
– Witness the fate of IPv6, QoS, multicast, secure routing
• Even if we could start over…
– Maybe the design problem is over-constrained
– Too many goals, some of them conflicting
2
It’s Hard to be a Routing Protocol These Days
• Many, many design goals
–Global reachability
–Fast convergence
–Efficient use of resources
–Low protocol overhead
–Secure control plane
–Flexible routing policies
–<your wish list here>
• Perhaps we cannot satisfy all of these goals
–Perhaps we should not even try
3
Example: Security vs. Reachability
Online Banking
Web Surfing
Properties
Security, even at the
Reachability more
expense of reachability important than security
Routing
Secure control plane
Insecure control plane
for participating parties for all parties
Addressing Self-certifying address Ephemeral address
associated with person related to the topology
4
Example: Convergence vs. Scalability
Voice over IP
Gateway
Properties
Fast convergence
for a few prefixes
Remaining Traffic
Scalability to 200K
prefixes
Dissemination Flooding
Hierarchical
Routing
Protocol
Internal BGP with
route reflectors
OSPF or IS-IS
5
Concurrent Architectures are Better than One
• Virtualization
– Multiple logical routers on a single platform
– Resource isolation in CPU, FIBs, and bandwidth
• Programmability
– General-purpose CPUs for control and manipulation
– Network processors and FPGAs for fast forwarding
– Third-party providers for routing and forwarding solutions
• Economic refactoring
– Infrastructure provider: manage routers and links
– Service provider: offer end-to-end services
http://www.cs.princeton.edu/~jrex/papers/cabo.pdf
6