Measuring Multipath Routing in the Internet

Augustin, Brice; Friedman, Timur; Teixeira, Renata

doi:10.1109/tnet.2010.2096232

Cited by 67 publications

(57 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The analysis in [PARIS2] shows that a significant majority of the flows on the Internet traverse per-destination or per-flow load balancing. It presents statistics that 72% of the flows traverse per-destination load balancing and 39% of the flows traverse per-flow load balancing, while only a negligible part of the flows traverse per-packet load balancing.…”

Section: Using Multiple Paths Concurrentlymentioning

confidence: 99%

Multipath Time Synchronization

Tse¹,

Shpiner²,

Schelp³

et al. 2016

View full text Add to dashboard Cite

Clock synchronization protocols are very widely used in IP-based networks. The Network Time Protocol (NTP) has been commonly deployed for many years, and the last few years have seen an increasingly rapid deployment of the Precision Time Protocol (PTP). As timesensitive applications evolve, clock accuracy requirements are becoming increasingly stringent, requiring the time synchronization protocols to provide high accuracy. This memo describes a multipath approach to PTP and NTP over IP networks, allowing the protocols to run concurrently over multiple communication paths between the master and slave clocks, without modifying these protocols. The multipath approach can significantly contribute to clock accuracy, security, and fault tolerance. The multipath approach that is presented in this document enables backward compatibility with nodes that do not support the multipath functionality.

show abstract

Section: Using Multiple Paths Concurrentlymentioning

confidence: 99%

Multipath Time Synchronization

Tse¹,

Shpiner²,

Schelp³

et al. 2016

View full text Add to dashboard Cite

show abstract

“…Based on Paris traceroute, an algorithm, Multipath Detection Algorithm (MDA), for detecting and listing all routes induced by a load balancer has been proposed [62][63][64]. The deployment of this algorithm shows that 39% of the sourcedestination pairs traverse a per flow load balancer and 70% a per destination load balancer.…”

Section: Load Balancingmentioning

confidence: 99%

Internet Topology Discovery

Donnet

2013

Data Traffic Monitoring and Analysis

View full text Add to dashboard Cite

Abstract. Since the nineties, the Internet has seen an impressive growth, in terms of users, intermediate systems (such as routers), autonomous systems, or applications. In parallel to this growth, the research community has been looking for obtaining and modeling the Internet topology, i.e., how the various elements of the network interconnect between themselves. An impressive amount of work has been done regarding how to collect data and how to analyse and model it. This chapter reviews main approaches for gathering Internet topology data. We first focus on hop limited probing, i.e., traceroute-like probing. We review large-scale tracerouting projects and discuss traceroute limitations and how they are mitigated by new techniques or extensions. Hop limited probing can reveal an IP interface vision of the Internet. We next focus on techniques for aggregating several IP interfaces of a given router into a single identifier. This leads to a router level vision of the topology. The aggregation can be done through a process called alias resolution. We also review a technique based on IGMP probing that silently collect all multicast interfaces of a router into a single probe. We next refine the router level topology by adding subnet information. We finish this chapter by discussing the AS level topology, in particular the relationships between ASes and the induced hierarchy.

show abstract

“…An individual probing round taking on the order of days for Ark [7], DIMES [8] and one day for iPlane [9]. Second, we were concerned that traces that did not employ Paris Traceroute [13] would introduce false dynamics due to the interaction between per-flow load-balancing routers and the way in which classic Traceroute modifies the flow identifier for each probe packet that it sends. Not all distributed network probing systems have switched over to Paris Traceroute (Only Ark has deployed Paris Traceroute).…”

Section: Performance Evaluationmentioning

confidence: 99%

Efficient IP-Level Network Topology Capture

Bourgeau¹,

Friedman²

2013

Passive and Active Measurement

Self Cite

View full text Add to dashboard Cite

Abstract. Large-scale distributed traceroute-based measurement systems are used to obtain the topology of the internet at the IP-level and can be used to monitor and understand the behavior of the network. However, existing approaches to measuring the public IPv4 network space often require several days to obtain a full graph, which is too slow to capture much of the network's dynamics. This paper presents a new network topology capture algorithm, NTC, which aims to better capture network dynamics through accelerated probing, reducing the probing load while maintaining good coverage. There are two novel aspects to our approach: it focuses on obtaining the network graph rather than a full set of individual traces, and it uses past probing results in a new, adaptive, way to guide future probing. We study the performance of our algorithm on real traces and demonstrate outstanding improved performance compared to existing work.

show abstract

Measuring Multipath Routing in the Internet

Cited by 67 publications

References 24 publications

Multipath Time Synchronization

Multipath Time Synchronization

Internet Topology Discovery

Efficient IP-Level Network Topology Capture

Contact Info

Product

Resources

About