Extending Networking into the Virtualization Layer

By Ben Pfaff, Justin Pettit, Keith Amidon, Martín Casado, Teemu Koponen, Scott Shenker. ACM Workshop on Hot Topics in Networks, 2009

640 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/c6c3baeb4f4a0895abace790a220d7e337ebbd50

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Citations in the corpus

ONOS: towards an open, distributed SDN OS (2014, methodology): “The switches were Open vSwitches [12] and had an average of 4 active ports.”
Split/Merge: System Support for Elastic Execution in Virtual Middleboxes (2013, unknown): “, switches [20], routers) to enforce routing to various replicas.”
Cloud security issues and challenges: A survey (2017, unknown): “[127] Virtual network security [99] [93] [184] [68]”
Presto: Edge-based Load Balancing for Fast Datacenter Networks (2015, background): “We piggyback on recent trends where several network functions, e.g. , ﬁrewalls and application-level load balancers, are moving into hypervi-sors and software virtual switches on end-hosts [10, 36, 51].”
Network Innovation using OpenFlow: A Survey (2014, methodology): “It is also possible to implement an OpenFlow-compliant softwarebased switch using Open vSwitch [29], [30].”
Survey on Network Virtualization Hypervisors for Software Defined Networking (2015, background): “Hypervisors that execute hypervisor functions on the data plane, i.e., the distributed hypervisors that involve NEs (see Sections V-B–V-D), require special consideration when evaluating control plane isolation.”
Software-defined networking (SDN): a survey (2016, background): “There are also two other cloud-based models: network virtualization model [36,37] and evolutionary model [38].”
A Survey and a Layered Taxonomy of Software-Defined Networking (2014, background): “, Open vSwitch (OVS) [34]–[36]) and OpenFlow-enabled hardware-based implementations (e.”
Inside the Social Network's (Datacenter) Network (2015, methodology): “…arrivals; many concurrent ﬂows (§6) Bimodal ACK/MTU packet size, on/off behavior [12]; <5 concurrent large ﬂows [8] SDN controllers [1, 22, 28, 32, 34]; Circuit/hybrid switching [7, 20, 30, 39] Table 1: Each of our major ﬁndings differs from previously published characterizations of…”
Near optimal placement of virtual network functions (2015, background): “The first is the ongoing transition into all-IP networks (VoIP, LTE, IP DSLAMs); and the second is the introduction of software defined networks (SDN) ([4], [8]) and the separation of the control and data planes.”
Security in Software Defined Networks: A Survey (2015, unknown): “The Open vSwitch platform provides isolation in multi-tenant environments and during mobility across multiple subnets [152].”
Combining OpenFlow and sFlow for an effective and scalable anomaly detection and mitigation mechanism on SDN environments (2014, methodology): “For this purpose, we used Open vSwitch [29], a software switch that can handle the required traffic loads.”
Security issues in cloud environments: a survey (2014, background): “[213] also pointed out the particular issue of securing the dynamic establishment of virtualized communication channels, which is aggravated when”
E2: a framework for NFV applications (2015, background): “…plane is in charge of (i) placement (instan-tiating the pipelets on servers), (ii) interconnection (setting up and conﬁguring the interconnections between NFs), (iii) scaling (dynamically adapting the placement decisions depending on load variations), and (iv) ensuring afﬁnity constraints of NFs.”
Software-Defined Network Function Virtualization: A Survey (2015, background): “Thus, SDN and NFV are applied to the wireless access networks [115]–[117], [120] to sharing their remote basestation infrastructure to achieve better coverage and services with the minimum investment of CAPEX and OPEX.”
One Sketch to Rule Them All: Rethinking Network Flow Monitoring with UnivMon (2016, methodology): “Feasible implementation roadmap: While pure software solutions (e.g., Open vSwitch [42]) may be valuable in many deployments, for broader adoption and performance requirements, the UnivMon primitives used to achieve [R1] and [R2] must have a viable implementation in (emerging) switch hardware…”