@article {Teg2016, title = {Experimental investigation on TCP throughput behavior in Optical Fiber Access Networks}, journal = {Fiber and Integrated Optics}, year = {2016}, type = {Journal article.}, author = {Edion Tego and Francesco Matera and Donato Del Buono} } @inproceedings {TrKu15, title = {Enabling Internet-Wide Deployment of Explicit Congestion Notification}, booktitle = {Proceedings of the 2015 Passive and Active Measurement Conference}, year = {2015}, month = {03/2015}, address = {New York}, abstract = {

\ac{ECN} is an TCP/IP extension to signal network congestion without packet loss, which has barely seen deployment though it was standardized and implemented more than a decade ago. On-going activities in research and standardization aim to make the usage of \ac{ECN} more beneficial. This measurement study provides an update on deployment status and newly assesses the marginal risk of enabling \ac{ECN} negotiation by default on client end-systems. Additionally, we dig deeper into causes of connectivity and negotiation issues linked to \ac{ECN}. We find that about five websites per thousand suffer additional connection setup latency when fallback per RFC 3168 is correctly implemented; we provide a patch for Linux to properly perform this fallback. Moreover, we detect and explore a number of cases in which \ac{ECN} brokenness is clearly path-dependent, i.e. on middleboxes beyond the access or content provider network. Further analysis of these cases can guide their elimination, further reducing the risk of enabling \ac{ECN} by default.

}, author = {Brian Trammell and Mirja K{\"u}hlewind and Damiano Boppart and Iain Learmonth and Gorry Fairhurst and Richard Scheffenegger} } @inproceedings {TrKuPAM15, title = {Enabling Internet-Wide Deployment of Explicit Congestion Notification}, booktitle = {Proceedings of the 2015 Passive and Active Measurement Conference}, year = {2015}, month = {Mar}, address = {New York}, url = {http://ecn.ethz.ch/ecn-pam15.pdf}, author = {Brian Trammell and Mirja K{\"u}hlewind and Damiano Boppart and Iain Learmonth and Gorry Fairhurst and Richard Scheffenegger} } @inproceedings {Cas2015b, title = {Exploring QoE in Cellular Networks: How Much Bandwidth do you Need for Popular Smartphone Apps?}, booktitle = {5th ACM SIGCOMM Workshop on All Things Cellular: Operations, Applications and Challenges}, year = {2015}, author = {Pedro Casas and Raimund Schatz and Florian Wamser and Michael Seufert and Ralf Irmer} } @article {Tra2014a, title = {Evolving Transport in the Internet}, journal = {IEEE Internet Computing}, year = {2014}, month = {09/2014}, abstract = {

The Internet{\textquoteright}s transport layer has seen little evolution over the past three decades, despite wildly changing requirements. Commonly-deployed transport protocols lack diversity, reducing our ability to evolve them to meet these new application requirements. In this work, the authors describe aspects of this problem and propose a solution space and agenda for improving the situation.

}, author = {Brian Trammell}, editor = {Joe Hildebrand} } @inproceedings {Tra2014b, title = {Exploiting Hybrid Measurements for Network Troubleshooting}, booktitle = {IEEE Networks}, year = {2014}, month = {09/2014}, publisher = {IEEE}, organization = {IEEE}, address = {Funchal, PT}, abstract = {Network measurements are a fundamental pillar to understand network performance and perform root cause analysis in case of problems. Traditionally, either active or passive measurements are considered. While active measurements allow to know exactly the workload injected by the application into the network, the passive measurements can offer a more detailed view of transport and network layer impacts. In this paper, we present a hybrid approach in which active throughput measurements are regularly run while a passive measurement tool monitors the generated packets. This allows us to correlate the application layer measurements obtained by the active tool with the more detailed view offered by the passive monitor. The proposed methodology has been implemented following the mPlane reference architecture, tools have been installed in the Fastweb network, and we collect measurements for more than three months. We report then a subset of results that show the benefits obtained when correlating active and passive measurements. Among results, we pinpoint cases of congestion, of ADSL misconfiguration, and of modem issues that impair throughput obtained by the users.}, keywords = {Hybrid measurements, measurement analysis, WP2}, author = {Stefano Traverso and Edion Tego and Eike Kowallik and Stefano Raffaglio and Andrea Fregosi and Marco Mellia and Francesco Matera} } @inproceedings {Ber2013, title = {Exploring the Cloud from Passive Measurements: the Amazon AWS case}, booktitle = {The 32nd Annual IEEE International Conference on Computer Communications (INFOCOM{\textquoteright}2013)}, year = {2013}, address = {Turin, Italy}, abstract = {

Cloud Providers are nowadays the most popular way to quickly deploy new services on the Internet. Understanding mechanisms currently adopted in cloud design is fundamental to identify possible bottlenecks, to optimize performance, and to design more efficient platforms. This paper presents a characterization of Amazon{\textquoteright}s Web Services (AWS), the most prominent cloud provider that offers computing, storage, and content delivery platforms. Leveraging passive measurements collected from several vantage points in Italy for several months, we explore the EC2, S3 and CloudFront AWS services to unveil their infrastructure, the pervasiveness of content they host, and their traffic allocation policies. Measurements reveal that most of the content residing on EC2 and S3 is served by one single Amazon datacenter located in Virginia despite it appears to be the worst performing one for Italian users. This causes traffic to take long and expensive paths in the network. Since no automatic migration and load-balancing policies are offered by AWS among different locations, content is exposed to outages, as we were able to observe in our data. The CloudFront CDN, on the contrary, shows much better performance thanks to the effective cache selection policy that serves 98\% of the traffic from the nearest available cache. CloudFront exhibits also dynamic load-balancing policies, in contrast to the static allocation of instances on EC2 and S3. Information presented in this paper will be useful for developers aiming at entrusting AWS to deploy their contents, and for researchers willing to improve cloud design.

}, doi = {10.1109/INFCOM.2013.6566769}, author = {Ignacio Nicolas Bermudez and Stefano Traverso and Marco Mellia and Maurizio M Munafo{\textquoteright}} }