Characterization of failures in an IP backbone

479 citations recorded by the source corpus.

How researchers see this paper

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

LIPSIN: line speed publish/subscribe inter-networking (2009, background): “These two types of failures cover around 85% of all unplanned outages [27].”
Debugging the data plane with anteater (2011, methodology): “[34] Ruby-Prolog. https://rubyforge.org/projects/ruby-prolog.”
Characterization of Failures in an Operational IP Backbone Network (2008, background): “…occurrence and impact of failures in these networks have received Manuscript received July 15, 2004; revised October 10, 2005, and September 13, 2006; .rst published February 25, 2008; last published August 15, 2008 (projected); approved by IEEE/ACM TRANSACTIONS ON NETWORKING Editor M. Roughan.”
Combining filtering and statistical methods for anomaly detection (2005, background): “Such drops can either be short-lived or long-lived, and the short-lived outages are not infrequent since failures of one sort or another are fairly commonplace in the Internet today [1].”
Characterization of network-wide anomalies in traffic flows (2004, background): “Researchers have characterized Internet intrusion activity [24], failure events in IP networks [17], and also constructed taxonomies for Internet worms [23], denial of service attacks [9] and defenses [18].”
Achieving sub-second IGP convergence in large IP networks (2005, background): “We begin our simulation study with link failures, the most frequent event that can occur in the topology of a network [15].”