OpenFlow
Nick McKeown, Tom Anderson, Hari Balakrishnan, Guru M. Parulkar, Larry Peterson, Jennifer Rexford, Scott J. Shenker, Jonathan Turner
ACM SIGCOMM Computer Communication Review · 2008 · 8,720 citations
No retraction on record in OpenAlex.Check Crossref now
Cite this paper
McKeown, N., Anderson, T., Balakrishnan, H., Parulkar, G. M., Peterson, L., Rexford, J., Shenker, S. J., & Turner, J. (2008). OpenFlow. ACM SIGCOMM Computer Communication Review, 38(2), 69–74. https://doi.org/10.1145/1355734.1355746
In text: (McKeown et al., 2008)
Ask a question about this research
One question, free, no account. Anchorcite finds the papers, checks each against Crossref and links every sentence of the answer to the passage it comes from.
Abstract
This whitepaper proposes OpenFlow: a way for researchers to run experimental protocols in the networks they use every day. OpenFlow is based on an Ethernet switch, with an internal flow-table, and a standardized interface to add and remove flow entries. Our goal is to encourage networking vendors to add OpenFlow to their switch products for deployment in college campus backbones and wiring closets. We believe that OpenFlow is a pragmatic compromise: on one hand, it allows researchers to run experiments on heterogeneous switches in a uniform way at line-rate and with high port-density; while on the other hand, vendors do not need to expose the internal workings of their switches. In addition to allowing researchers to evaluate their ideas in real-world traffic settings, OpenFlow could serve as a useful campus component in proposed large-scale testbeds like GENI. Two buildings at Stanford University will soon run OpenFlow networks, using commercial Ethernet switches and routers. We will work to encourage deployment at other schools; and We encourage you to consider deploying OpenFlow in your university network too
Related papers
Metadata from OpenAlex (CC0). Citations are generated from the published record.