@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 {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 {Tra2015, title = {A New Transport Encapsulation for Middlebox Cooperation}, booktitle = {Proceedings of the 2015 IEEE Conference on Standards for Communications and Networking}, year = {2015}, month = {Oct}, address = {Tokyo, Japan}, author = {Brian Trammell and Mirja Kuehlewind and Elio Gubser and Joe Hildebrand} } @inproceedings {Tra2015a, title = {Observing Internet Path Transparency to Support Protocol Engineering}, booktitle = {Proceedings of the first IRTF/ISOC Workshop on Research and Applications of Internet Measurements (RAIM)}, year = {2015}, month = {Oct}, address = {Yokohama, Japan}, author = {Brian Trammell and Mirja K{\"u}hlewind} } @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 {Tra2014, title = {Inline Data Integrity Signals for Passive Measurement}, booktitle = {Sixth International Workshop on Traffic Monitoring and Analysis (TMA 2014)}, year = {2014}, month = {04/2014}, abstract = {

In passive network measurement, the quality of an observed traffic stream is obviously crucial to the quality of the results. Some sources of error (e.g., packet loss at a capture device) are well understood, others less so. In this work, we describe the inline data integrity measurement provided by the QoF TCP-aware flow meter. By instrumenting the data structures QoF uses for detecting lost and retransmitted TCP segments, we can provide an in-band, per-flow estimate of observation loss: segments which were received by the recipient but not observed by the flow meter. We evaluate this mechanism against controlled, induced error, and apply it to two data sets used in previous work.

}, author = {Brian Trammell and David Gugelmann and Nevil Brownlee} } @article {rfc7119, title = {Operation of the IP Flow Information Export (IPFIX) Protocol on IPFIX Mediators (RFC 7119)}, year = {2014}, month = {02/2014}, abstract = {
This document specifies the operation of the IP Flow Information Export (IPFIX) protocol specific to IPFIX Mediators, including Template and Observation Point management, timing considerations, and other Mediator-specific concerns.
}, url = {http://www.ietf.org/rfc/rfc7119.txt}, author = {B. Claise and A. Kobayashi and B. Trammell} } @article {rfc7125, title = {Revision of the tcpControlBits IP Flow Information Export (IPFIX) Information Element (RFC 7125)}, year = {2014}, month = {02/2014}, abstract = {
This document revises the tcpControlBits IP Flow Information Export (IPFIX) Information Element as originally defined in RFC 5102 to reflect changes to the TCP Flags header field since RFC 793.
}, url = {http://www.ietf.org/rfc/rfc7125.txt}, author = {B. Trammell and P. Aitken} } @inproceedings {Tra2013c, title = {A Measurement-Centered Approach to Latency Reduction}, booktitle = {ISOC Workshop on Reducing Internet Latency}, year = {2013}, month = {09/2013}, type = {Position Paper}, address = {London, England}, url = {http://www.internetsociety.org/latency2013}, author = {Brian Trammell and Alessandro Finamore and Marco Mellia} } @article {Tra2013b, title = {python-ipfix-0.9.1}, year = {2013}, abstract = {

This module provides a Python interface to IPFIX message streams, and provides tools for building IPFIX Exporting and Collecting Processes. It handles message framing and deframing, encoding and decoding IPFIX data records using templates, and a bridge between IPFIX ADTs and appropriate Python data types.\ 

}, url = {http://pypi.python.org/pypi/ipfix}, author = {Brian Trammell} } @article {Mar2013a, title = {Standardizing large-scale measurement platforms}, journal = {SIGCOMM Comput. Commun. Rev.}, volume = {43}, year = {2013}, pages = {58{\textendash}63}, keywords = {design, ietf, measurement platforms, standardization}, issn = {0146-4833}, doi = {10.1145/2479957.2479967}, url = {http://doi.acm.org/10.1145/2479957.2479967}, author = {Bagnulo Marcelo and Eardley Philip and Burbridge Trevor and Brian Trammell and Rolf Winter} } @inproceedings {Kue2013, title = {On the state of ECN and TCP Options on the Internet}, booktitle = {Passive and Active Measurement Conference (PAM)}, year = {2013}, month = {03/2013}, address = {Hong Kong}, abstract = {

Explicit Congestion Notification (ECN) is a TCP/IP extension that can avoid packet loss and thus improve network performance. Though standardized in 2001, it is barely used in today{\textquoteright}s Internet. This study, following on previous active measurement studies over the past decade, shows marked and continued increase in the deployment of ECN-capable servers, and usability of ECN on the majority of paths to such servers. We additionally present new measurements of ECN on IPv6, passive observation of actual ECN usage from flow data, and observations on other congestion-relevant TCP options (SACK, Timestamps and Window Scaling). We further present initial work on burst loss metrics for loss-based congestion control following from our findings.\ 

}, doi = {10.1007/978-3-642-36516-4_14}, author = {Mirja Kuehlewind and Sebastian Neuner and Brian Trammell} } @inproceedings {Tra2012, title = {On Flow Concurrency in the Internet and its Implications for Capacity Sharing}, booktitle = {Proceedings of the Second ACM CoNext Capacity Sharing Workshop (CSWS)}, year = {2012}, month = {12/2012}, address = {Nice, France}, doi = {10.1145/2413219.2413225}, author = {Brian Trammell and Dominik Schatzmann} }