Future transports
Daniel Stenberg
●
Free Software
●
Network hacker, code and IETF
●
Embedded developer
●
Consultant
Email: daniel@haxx.se
Tw...
Agenda
●
What transport
●
Direction
●
Problems today
●
Deployment fail
●
New stuff
(in just 30 mins so let's go!)
Transport layer
Contents
Application
Transport
Internet
Link
Current state
●
Roundtrips to several seconds!
●
DNS
●
Single route, multiple interfaces
●
Deploy failures for new
●
Slow ...
Bandwidth growth
RTT limitations
Graph by Mike Belshe
Worse RTT is just downhill
Graph by Mike Belshe
Mobile has not helped
TCP design
●
3­way handshake
●
Slow start
●
Nagle algorithm
●
Delayed ACK
HTTP problems
●
Chatty and sizable
●
Not to mention cookies
●
Pipelining is flawed
●
No header compression
HTTP Workarounds
●
Many connections
●
Pre­lookup host names
●
longpolling / AJAX
●
pipelining attempts
●
Compression
Future
●
4 technologies being developed
●
Attempts
●
Will they actually happen?
SCTP
●
IETF, RFC4960 from 2007
●
Replaces TCP
●
Messages, not a stream
●
Multi­path
●
Multi­streaming
SCTP fail
●
Intermediaries need upgrade
●
HTTP over SCTP
●
SCTP over UDP?
●
Will it rise?
SPDY
●
Google
●
HTTP replacement
●
Multiplexed streams, prioritized and even server 
initialized
●
Always TLS
●
Compressed...
SPDY?
●
Simply too early
●
Only experiments
●
Google tech
MPTCP
●
Multi­path TCP
●
IETF
●
Compatible socket API
●
“kind to the network”
●
Made for multi interface hosts
Multi­path explained
One connection
Multi­path!
WebSockets 1
●
HTML5 – WHATWG
●
IETF – Hybi
●
Javascript­focused
●
Browser to Server
●
Solve the longpolling problem
WebSockets 2
●
TCP replacement(!)
●
HTTP Upgrade, CONNECT or separate
●
“­76/­00” in Chrome, Firefox, Opera
●
Already inco...
WebSockets success?
●
I say likely
●
Join IETF and help out!
Summary
●
Problems with RTT and protocols
●
Ways to work around them
●
Some might end up used
That's it!
Questions or thoughts?
Upcoming SlideShare
Loading in …5
×

Fscons future transports

3,458 views

Published on

Talk by Daniel Stenberg at FSCONS 2010 in english about a few different new coming "future transport" technologies in computer networks.

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
3,458
On SlideShare
0
From Embeds
0
Number of Embeds
1,815
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Fscons future transports

  1. 1. Future transports
  2. 2. Daniel Stenberg ● Free Software ● Network hacker, code and IETF ● Embedded developer ● Consultant Email: daniel@haxx.se Twitter: @bagder Web: daniel.haxx.se Blog: daniel.haxx.se/blog
  3. 3. Agenda ● What transport ● Direction ● Problems today ● Deployment fail ● New stuff (in just 30 mins so let's go!)
  4. 4. Transport layer Contents Application Transport Internet Link
  5. 5. Current state ● Roundtrips to several seconds! ● DNS ● Single route, multiple interfaces ● Deploy failures for new ● Slow start ● Browsers want long connections ● HTTP is “chatty”
  6. 6. Bandwidth growth
  7. 7. RTT limitations Graph by Mike Belshe
  8. 8. Worse RTT is just downhill Graph by Mike Belshe
  9. 9. Mobile has not helped
  10. 10. TCP design ● 3­way handshake ● Slow start ● Nagle algorithm ● Delayed ACK
  11. 11. HTTP problems ● Chatty and sizable ● Not to mention cookies ● Pipelining is flawed ● No header compression
  12. 12. HTTP Workarounds ● Many connections ● Pre­lookup host names ● longpolling / AJAX ● pipelining attempts ● Compression
  13. 13. Future ● 4 technologies being developed ● Attempts ● Will they actually happen?
  14. 14. SCTP ● IETF, RFC4960 from 2007 ● Replaces TCP ● Messages, not a stream ● Multi­path ● Multi­streaming
  15. 15. SCTP fail ● Intermediaries need upgrade ● HTTP over SCTP ● SCTP over UDP? ● Will it rise?
  16. 16. SPDY ● Google ● HTTP replacement ● Multiplexed streams, prioritized and even server  initialized ● Always TLS ● Compressed headers ● Chrome ● Experimental
  17. 17. SPDY? ● Simply too early ● Only experiments ● Google tech
  18. 18. MPTCP ● Multi­path TCP ● IETF ● Compatible socket API ● “kind to the network” ● Made for multi interface hosts
  19. 19. Multi­path explained
  20. 20. One connection
  21. 21. Multi­path!
  22. 22. WebSockets 1 ● HTML5 – WHATWG ● IETF – Hybi ● Javascript­focused ● Browser to Server ● Solve the longpolling problem
  23. 23. WebSockets 2 ● TCP replacement(!) ● HTTP Upgrade, CONNECT or separate ● “­76/­00” in Chrome, Firefox, Opera ● Already incompatible with latest (­03) ● Lively debated and worked on
  24. 24. WebSockets success? ● I say likely ● Join IETF and help out!
  25. 25. Summary ● Problems with RTT and protocols ● Ways to work around them ● Some might end up used
  26. 26. That's it! Questions or thoughts?

×