A DoS-limiting network architecture
By Xiaowei Yang, David Wetherall, T. Anderson. Conference on Applications, Technologies, Architectures, and Protocols for Computer Communication, 2005
446 citations recorded by the source corpus.
Subfields: Artificial Intelligence, Computer Networks and Communications
View Paper: https://www.semanticscholar.org/paper/af4b6f271b485047a51203d8892708bfca87fafc
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Artificial Intelligence
- Arjun Guha
- Dan Boneh
- Michael J. Freedman
- Scott Shenker
- David Warren Tipper
- Michael Bailey
- Vyas Sekar
- James B. D. Joshi
In Computer Networks and Communications
- Ion Stoica
- Scott Shenker
- Dan Boneh
- Matthew C. Caesar
- Nick McKeown
- Michael J. Freedman
- Rodrigo Fonseca
- Karthik Lakshminarayanan
Citations in the corpus
- Bohatei: Flexible and Elastic DDoS Defense (2015, background): “DDoS-resilient Internet architectures: These include the use of capabilities [58], better inter-domain routing (e.”
- SANE: A Protection Architecture for Enterprise Networks (2006, background): “Much recent work has focused on DoS remediation through network enforced capabilities [8, 31, 32] on the WAN.”
- MIRO: multi-path interdomain routing (2006, unknown): “Advanced packet filters or network ca pabilities [19] could be used to prevent this problem.”
- Not-a-Bot: Improving Service Availability in the Face of Botnet Attacks (2009, unknown): “These proposals include using bandwidth-aspayment [31], path validation [ 35 ], and computational proofs of work [20] for DDoS; and using syndicators, premium clicks, and clickable CAPTCHAs for clickfraud [26].”
- A Survey of Defense Mechanisms Against Distributed Denial of Service (DDoS) Flooding Attacks (2013, methodology): “In [102], [105], TVA as a capability-based mechanism is compared to StopIt as a filter-based mechanism under similar assumptions and practical constraints.”
- A data-oriented (and beyond) network architecture (2007, methodology): “We won’t delve into the details here, but mechanisms similar to SIFF [41] and TVA [43] could be used (but on a per-domain basis, not per-router basis), with the capabilities inserted in the FIND as it traversed domains.”
- ROFL: routing on flat labels (2006, background): “Capabilities: The use of flat identifiers allows more fine-grained access control through the use of capabilities (similar to TVA [42]).”
- Participatory networking: an API for application control of SDNs (2013, background): “TVA is a network architecture in which end-hosts authorize the receipt of packet flows via capabilities in order to prevent DoS-attacks [50].”
- Named Data Networking (NDN) Project (2010, unknown): “Capability [84]).”