A GeneralizedLabel-Forwarding Architecture   for the Future Internet              2nd GI/ITG KuVS Workshop              Fu...
Todays Internet model – in theory    APPLICATION                                                       APPLICATION    TRAN...
Todays Internet model – in reality    APPLICATION                                                       APPLICATION     TR...
Todays Internet model – in reality    APPLICATION                                                       APPLICATION     TR...
Lessons learned so far (1)…•   End-to-End semantics are good for overall    robustness but bad for privacy•   Minimize the...
Lessons learned so far (2)…•   Security is needed everywhere but has to    be easily deployable (IPSec vs. TLS)•   Some of...
Basic Idea•   Label-switched network design between    applications using „extended labels“•   Extended labels include a p...
Proposed Architecture: ELSSA protocol   Extended Label Stream Switching Architecture
Properties and Comparisons•   Separation of forwarding and routing,    location and addressing•   Built-in security and pr...
Future Project Development
- Questions?- Feedback?
Upcoming SlideShare
Loading in …5
×

A Generalized Label-Forwarding Architecture for the Future Internet

608 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
608
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

A Generalized Label-Forwarding Architecture for the Future Internet

  1. 1. A GeneralizedLabel-Forwarding Architecture for the Future Internet 2nd GI/ITG KuVS Workshop Future Internet Karlsruhe 11/2008 Achim Friedland SONES GmbH / TU Ilmenau achim.friedland@sones.de
  2. 2. Todays Internet model – in theory APPLICATION APPLICATION TRANSPORT S/MIME DNSSec APPLICATION TRANSPORT NETWORK SOCKS, SSH TLS, DTLS TRANSPORT IP Se c NETWORK IP-in-IP, GRE (G)MPLS MACSec, 802.11i LINK Q-in-Q, MAC-in-MAC
  3. 3. Todays Internet model – in reality APPLICATION APPLICATION TRANSPORT S/MIME DNSSec APPLICATION TRANSPORT NETWORK SOCKS, SSH TLS, DTLS TRANSPORT IP Se c NETWORK IP-in-IP, GRE (G)MPLS MACSec, 802.11i LINK Q-in-Q, MAC-in-MAC
  4. 4. Todays Internet model – in reality APPLICATION APPLICATION TRANSPORT S/MIME DNSSec APPLICATION TRANSPORT NETWORK SOCKS, SSH TLS, DTLS TRANSPORT IP Se c NETWORK IP-in-IP, GRE (G)MPLS MACSec, 802.11i LINK Q-in-Q, MAC-in-MAC The Software Engineers‘ way: 1. Refactoring 2. Enhancement
  5. 5. Lessons learned so far (1)…• End-to-End semantics are good for overall robustness but bad for privacy• Minimize the state within the network but allow 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
  6. 6. Lessons learned so far (2)…• Security is needed everywhere but has to be easily deployable (IPSec vs. TLS)• Some of todays (Cross-Layer)-Designs can be seen as „lawfull“ layer violations (e.g. TCP, IPSec)• Stackable Flow-Labels for traffic differen- tiation, aggregation and advanced traffic engineering (e.g. MPLS)
  7. 7. Basic Idea• Label-switched network design between applications 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 implement security, privacy, mobility and QoS
  8. 8. Proposed Architecture: ELSSA protocol Extended Label Stream Switching Architecture
  9. 9. 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
  10. 10. Future Project Development
  11. 11. - Questions?- Feedback?

×