presto workshop discussion notes n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
PRESTO workshop discussion notes PowerPoint Presentation
Download Presentation
PRESTO workshop discussion notes

play fullscreen
1 / 8

PRESTO workshop discussion notes

80 Views Download Presentation
Download Presentation

PRESTO workshop discussion notes

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. PRESTO workshop discussion notes Henning Schulzrinne Columbia University PRESTO Workhop (Princeton, NJ)

  2. Goals • Goals • exchange of ideas, plead with vendors • platform (“Linux”) • funding program • Abstract models forwarding/routing • Guaranteeing resources PRESTO Workhop (Princeton, NJ)

  3. Why programmable? • trying new ideas or solve real problems with current networks? • e.g., richer interface for management • research: existing tools are not performant enough • rapid roll-out (verticalization) • several agendas: e.g., some ideas are related to GENI, but similar things useful for service providers • CS-like openness because we cannot predict the future PRESTO Workhop (Princeton, NJ)

  4. Carriers • Do SPs want open routers? • their own services? • customer services? • platform separate from the router? • Carriers maintain traditional CiSw viewpoint • good match for services customers asking for? • Meant for domain experts, but who is that? • server vs. router, flavors of Unix • Policy arbitration • Hardware not designed for virtualization/isolation • security infrastructure • won’t allow external code on today’s routers PRESTO Workhop (Princeton, NJ)

  5. Virtualization, scaling • Virtualization in research space difficult • under-resourced • easier in commercial space • Can’t scale open routing software to reality • not “open” source problem, but software architecture? • can I move it to a real network later? • software forwarding is slow • add netFPGA • What is virtualization? • What is programmability? • routing & forwarding vs. control plane • services on the same platform - close to fabric • convenience PRESTO Workhop (Princeton, NJ)

  6. Interfaces • What kind of interface/programmability? • recompile kernel • kernel module • netfilter, pcap-style, mirror interface • netflow, SNMP, RSVP, ... - external “APIs” • Levels • packet forwarding • network operating system PRESTO Workhop (Princeton, NJ)

  7. Community • Need for community • other researchers working on the same platform • tools, OS, common knowledge • ability to impact operational systems PRESTO Workhop (Princeton, NJ)

  8. Routers • Commercial routers vs. open router components • other than Juniper & Cisco • these vendors need to be open • same question as in 1957 at IBM: “why do you want to write your own programs?” PRESTO Workhop (Princeton, NJ)