2013
DOI: 10.1007/978-3-642-36516-4_14
|View full text |Cite
|
Sign up to set email alerts
|

On the State of ECN and TCP Options on the Internet

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

3
29
0

Year Published

2015
2015
2020
2020

Publication Types

Select...
4
3
1

Relationship

1
7

Authors

Journals

citations
Cited by 39 publications
(32 citation statements)
references
References 11 publications
3
29
0
Order By: Relevance
“…[14] conducted active probes of the Alexa Top million web servers list in 2014 and found 56.17% negotiated ECN when requested. Similar studies by Kühlewind et al [6] found 29.48% would negotiate ECN in 2012, while [1] found 17.2% would negotiate ECN. Langley [7] and Medina et al [9] present earlier data, showing negligible deployment.…”
Section: Reachability Using Ecn With Tcpsupporting
confidence: 63%
See 1 more Smart Citation
“…[14] conducted active probes of the Alexa Top million web servers list in 2014 and found 56.17% negotiated ECN when requested. Similar studies by Kühlewind et al [6] found 29.48% would negotiate ECN in 2012, while [1] found 17.2% would negotiate ECN. Langley [7] and Medina et al [9] present earlier data, showing negligible deployment.…”
Section: Reachability Using Ecn With Tcpsupporting
confidence: 63%
“…Kühlewind et al [6] also studied the Alexa top web servers, finding ECN support in 25.16% of servers tested in April 2012, rising to 29.48% in August 2012. Tests conducted against IPv6 hosts show 48.56% successfully negotiating ECN.…”
Section: Related Workmentioning
confidence: 99%
“…Current inferencebased passive measurement approaches [21], [22] generally use the TCP Timestamp Option [23], when available [13], [24]. In contrast, loss measurement requires inference about the loss detection and retransmission algorithms in use by the sender [25].…”
Section: Network Performance Measurementmentioning
confidence: 99%
“…As shown in Table 2, we find that 5.1% of IPv4 and 11.2% IPv6 paths systematically cleared the ECN Congestion Experienced (CE) bit of the IP layer. A previous study by Kühlewind et al found, with a completely different methodology, that 8.2% of the tested paths clear the CE bit as well [8]. This behavior makes it impossible for the client to report to the server that its incoming traffic experienced congestion, making ECN unusable.…”
Section: A Intended Functions/purposesmentioning
confidence: 99%
“…Following packets are marked as ECN-Capable Transport (ECT) by both ends but the middlebox is systematically clearing both the ECT and CE (Congestion Experienced) bits in the IP header. If an intermediate router sets the CE bit (Congestion Encountered) of a packet, it will be cleared by the middlebox afterward [8].…”
Section: A Explicit Congestion Notificationmentioning
confidence: 99%