1 / 13

Networking as an Enabler of New Services

Networking as an Enabler of New Services. Mark Gardner. Office of IT Virginia Tech 2010-10-19. Outline. Motivation Programmability Naming and Isolation Summary. TCP. Life was simple then…. One Machine : One Address. How many interfaces now?. How many?. 0-1 (so far). Two+.

tyrone-clayton
Download Presentation

Networking as an Enabler of New Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Networking as an Enablerof New Services Mark Gardner Office of IT Virginia Tech 2010-10-19

  2. Outline • Motivation • Programmability • Naming and Isolation • Summary TCP

  3. Life was simple then… One Machine : One Address

  4. How many interfaces now? How many? 0-1 (so far) Two+ What should the name(s) be? One+ Three+

  5. The Many Names of Networking • Network address (IP) • Service (port) • Hostname • Service name www.vt.edu 198.82.183.54 Port 80 http

  6. The Many Names of Networking • NAT/NAPT • Internal • External bigfirewall.vt.edu Port 5984 laptop.int.vt.edu Port 3876

  7. The Many Names of Networking • Person • Conversation What is it Bob? Hey Alice! What we really want: We need higher-level abstractions (another level of indirection)

  8. Isolation Boundary for TCP Additional Services Application Isolation Mechanism TCP IP Link Isolation boundary mechanism allows new services to be created Kalim, Gardner, Brown and Feng, “Enabling Renewed Innovation in TCP by Establishing an Isolation Boundary, submitted to PFLDnet 2010.

  9. Connect Sequence Diagram Host A Host B Choose TIFID-A TISeq-A S,TIFID-A,TISeq-A Record TIFID-A, TISeq-A Choose TIFID-B, TISeq-B S,A,TIAck-A, TIFID-B,TISeq-B Record TIFID-B, TISeq-B A,TIAck-B TIAck are zero when not in use. Lack of option in reply causes fallback to legacy mode

  10. Potential New Services Resume from disconnection • Resume from disconnection • Better support for suspend • Migration • Delay tolerant networking • Parallel connections • Support for a session layer • Hybrid packet/circuit networks • Better support for application networking • Campus multi-homing (provider addressing)

  11. Resume Sequence Diagram Host A Host B Use old TIFID-A TISeq-A, TIAck-B S,TIFID-A,TISeq-A, TIAck-B Lookup TIFID-A, Record TISeq-A Use old TIFID-B, TISeq-B, TIAck-B S,A,TIAck-A, TIFID-B,TISeq-B Lookup TIFID-B, Record TISeq-B A,TIAck-B TIAck not zero indicates resume Legacy TCP doesn’t support resumption

  12. Challenges to adoption • TCP mostly good enough • Except when its not • Don’t know what they are missing • Weight of legacy • Billions of installed units • Backwards compatibility is desirable (but not always possible) • Wholesale change is expensive • Change increases risk • Simultaneous adoption is impractical (no “flag day”) • Increasingly complex system • Interactions? • Unintended consequences?

  13. Isolation Boundary Evaluation • Pro • (Mostly) backward compatible w/o performance penalty • Fallback to legacy behavior • No flag day required • Extremely simple mechanism (yet enables complex new behaviors) • Con • Use up remaining option space (on 3-way handshake only) • No room for some lesser used options during handshake • Still relatively new idea Currently being implemented and tested

More Related