Skip to main content
To refer to this page use: http://arks.princeton.edu/ark:/88435/pr1ss0c
Full metadata record
DC FieldValueLanguage
dc.contributor.authorZave, Pamela-
dc.contributor.authorFerreira, Ronaldo A-
dc.contributor.authorZou, Xuan K-
dc.contributor.authorMorimoto, Masaharu-
dc.contributor.authorRexford, Jennifer-
dc.date.accessioned2021-10-08T19:49:03Z-
dc.date.available2021-10-08T19:49:03Z-
dc.date.issued2017en_US
dc.identifier.citationZave, Pamela, Ronaldo A. Ferreira, Xuan Kelvin Zou, Masaharu Morimoto, and Jennifer Rexford. "Dynamic Service Chaining with Dysco." In Proceedings of the Conference of the ACM Special Interest Group on Data Communication (2017): pp. 57-70. doi:10.1145/3098822.3098827en_US
dc.identifier.urihttps://www.cs.princeton.edu/courses/archive/spring17/cos598D/DynamicServiceChaining17.pdf-
dc.identifier.urihttp://arks.princeton.edu/ark:/88435/pr1ss0c-
dc.description.abstractMiddleboxes are crucial for improving network security and performance, but only if the right traffic goes through the right middleboxes at the right time. Existing traffic-steering techniques rely on a central controller to install fine-grained forwarding rules in network elements---at the expense of a large number of rules, a central point of failure, challenges in ensuring all packets of a session traverse the same middleboxes, and difficulties with middleboxes that modify the "five tuple." We argue that a session-level protocol is a fundamentally better approach to traffic steering, while naturally supporting host mobility and multihoming in an integrated fashion. In addition, a session-level protocol can enable new capabilities like dynamic service chaining, where the sequence of middleboxes can change during the life of a session, e.g., to remove a load-balancer that is no longer needed, replace a middlebox undergoing maintenance, or add a packet scrubber when traffic looks suspicious. Our Dysco protocol steers the packets of a TCP session through a service chain, and can dynamically reconfigure the chain for an ongoing session. Dysco requires no changes to end-host and middlebox applications, host TCP stacks, or IP routing. Dysco's distributed reconfiguration protocol handles the removal of proxies that terminate TCP connections, middleboxes that change the size of a byte stream, and concurrent requests to reconfigure different parts of a chain. Through formal verification using Spin and experiments with our Linux-based prototype, we show that Dysco is provably correct, highly scalable, and able to reconfigure service chains across a range of middleboxes.en_US
dc.format.extent57 - 70en_US
dc.language.isoen_USen_US
dc.relation.ispartofProceedings of the Conference of the ACM Special Interest Group on Data Communicationen_US
dc.rightsAuthor's manuscripten_US
dc.titleDynamic Service Chaining with Dyscoen_US
dc.typeConference Articleen_US
dc.identifier.doi10.1145/3098822.3098827-
pu.type.symplectichttp://www.symplectic.co.uk/publications/atom-terms/1.0/conference-proceedingen_US

Files in This Item:
File Description SizeFormat 
DynamicServiceChainingDysco.pdf1.6 MBAdobe PDFView/Download


Items in OAR@Princeton are protected by copyright, with all rights reserved, unless otherwise indicated.