a generalized label-forwarding architecture for the future internet

11
A Generalized Label-Forwarding Architecture for the Future Internet 2nd GI/ITG KuVS Workshop Future Internet Achim Friedland SONES GmbH / TU Ilmenau [email protected] Karlsruhe 11/2008

Upload: achim-friedland

Post on 19-Jan-2015

394 views

Category:

Technology


2 download

DESCRIPTION

 

TRANSCRIPT

A GeneralizedLabel-Forwarding Architecture

for the Future Internet

2nd GI/ITG KuVS WorkshopFuture Internet

Achim FriedlandSONES GmbH / TU [email protected]

Karlsruhe 11/2008

Todays Internet model – in theory

IPSec

MACSec, 802.11i

IP-in-IP, GRE

Q-in-Q, MAC-in-MAC

(G)MPLS

DNSSec

SOCKS, SSH

APPLICATION

TRANSPORT

TLS, DTLS

S/MIME

APPLICATION

TRANSPORT

NETWORK APPLICATION

TRANSPORT

NETWORK

LINK

Todays Internet model – in reality

APPLICATION

TRANSPORT

NETWORK

LINK

IPSec

TLS, DTLS

Q-in-Q, MAC-in-MACMACSec, 802.11i

(G)MPLS

DNSSec

IP-in-IP, GRE

S/MIME

APPLICATION

TRANSPORT

NETWORKSOCKS, SSH

APPLICATION

TRANSPORT

Todays Internet model – in reality

The Software Engineers‘ way:1. Refactoring2. Enhancement

APPLICATION

TRANSPORT

NETWORK

LINK

IPSec

TLS, DTLS

Q-in-Q, MAC-in-MACMACSec, 802.11i

(G)MPLS

DNSSec

IP-in-IP, GRE

S/MIME

APPLICATION

TRANSPORT

NETWORKSOCKS, SSH

APPLICATION

TRANSPORT

Lessons learned so far (1)…

• End-to-End semantics are good for overallrobustness but bad for privacy

• Minimize the state within the network butallow some state at the (domain) edges(Firewalls, NAT, VPN, Proxies, MobileIP, QoS Classification)

• Protocol layering minimizes complexity and boosts abstraction but everyone tries to bypass the layer model using tunnels

Lessons learned so far (2)…

• Security is needed everywhere but has to be easily deployable (IPSec vs. TLS)

• Some of todays (Cross-Layer)-Designs canbe seen as „lawfull“ layer violations(e.g. TCP, IPSec)

• Stackable Flow-Labels for traffic differen-tiation, aggregation and advanced trafficengineering (e.g. MPLS)

Basic Idea

• Label-switched network design betweenapplications using „extended labels“

• Extended labels include a packet counter to support e.g. security, loss detection, …

• Label may be „globally unique“ for suppor-ting e.g. IP Addresses, DIFF-Serv tags

• Network state is used to implementsecurity, privacy, mobility and QoS

Proposed Architecture: ELSSA protocol

Extended Label Stream Switching Architecture

Properties and Comparisons

• Separation of forwarding and routing, location and addressing

• Built-in security and privacy

• Built-in (micro-)mobilty and QoS

• Support of heterogeneous subnetworks, modularity and soft migration

Future Project Development

- Questions?- Feedback?