scispace - formally typeset
D

David Hay

Researcher at Hebrew University of Jerusalem

Publications -  87
Citations -  2370

David Hay is an academic researcher from Hebrew University of Jerusalem. The author has contributed to research in topics: Network packet & Jitter. The author has an hindex of 22, co-authored 83 publications receiving 2098 citations. Previous affiliations of David Hay include Ben-Gurion University of the Negev & Technion – Israel Institute of Technology.

Papers
More filters
Proceedings ArticleDOI

Palette: Distributing tables in software-defined networks

TL;DR: The Palette distribution framework is presented, which copes with two NP-hard optimization problems: Decomposing a large SDN table into equivalent subtables, and distributing the subtables such that each connection traverses each type of subtable at least once.
Proceedings ArticleDOI

Power Grid Vulnerability to Geographically Correlated Failures - Analysis and Control Implications

TL;DR: In this article, the authors consider line outages in the transmission net of the power grid, and specifically those caused by natural disasters or large-scale physical attacks, and show how to identify the most vulnerable locations in the network.
Proceedings ArticleDOI

OpenBox: A Software-Defined Framework for Developing, Deploying, and Managing Network Functions

TL;DR: OpenBox effectively decouples the control plane of NFs from their data plane, similarly to SDN solutions that only address the network’s forwarding plane.
Journal ArticleDOI

The resilience of WDM networks to probabilistic geographical failures

TL;DR: This work provides a unified framework to model network vulnerability when the event has a probabilistic nature, defined by an arbitrary probability density function and uses computational geometric tools to provide efficient algorithms to identify vulnerable points within the network under various metrics.
Proceedings ArticleDOI

Deep Packet Inspection as a Service

TL;DR: This paper proposes to treat DPI as a service to the middleboxes, implying that traffic should be scanned only once, but against the data of all middleboxes that use the service, having significant advantages in performance, scalability, robustness, and as a catalyst for innovation in the middlebox domain.