<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Brian Trammell</style></author><author><style face="normal" font="default" size="100%">Mirja Kühlewind</style></author><author><style face="normal" font="default" size="100%">Damiano Boppart</style></author><author><style face="normal" font="default" size="100%">Iain Learmonth</style></author><author><style face="normal" font="default" size="100%">Gorry Fairhurst</style></author><author><style face="normal" font="default" size="100%">Richard Scheffenegger</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Enabling Internet-Wide Deployment of Explicit Congestion Notification</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2015 Passive and Active Measurement Conference</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2015</style></year><pub-dates><date><style  face="normal" font="default" size="100%">03/2015</style></date></pub-dates></dates><pub-location><style face="normal" font="default" size="100%">New York</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">&lt;p&gt;\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.&lt;/p&gt;</style></abstract></record></records></xml>