<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Same thing applies for WiFi - oftentimes WiFi with poor signal
levels will cause drops, without congestion. This is something I'm
working to fix from the WiFi / L2 side. What are the solutions in
L3? Some kind of hybrid delay & drop based CC?<br>
<br>
Simon<br>
<br>
<div class="moz-cite-prefix">On 4/23/2015 8:52 AM, Jonathan Morton
wrote:<br>
</div>
<blockquote
cite="mid:CAJq5cE0hP-X5eaEMsOmzkL4a5948-PZ=bbAa-AfVQMNPp8So1w@mail.gmail.com"
type="cite">
<p dir="ltr">> By curiosity, what is now responsible for the
drops if not the congestion?</p>
<p dir="ltr">I think the point was not that observed drops are not
caused by congestion, but that congestion doesn't reliably cause
drops. Correlation is not causation.</p>
<p dir="ltr">There are also cases when drops are in fact caused by
something other than congestion, including faulty ADSL phone
lines. Some local loop providers have been known to explicitly
consider several percent of packet loss due to line conditions
as "not a fault", to the consternation of the actual ISP who was
trying to provide a decent device over it.</p>
<p dir="ltr"> - Jonathan Morton<br>
</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Bloat mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bloat@lists.bufferbloat.net">Bloat@lists.bufferbloat.net</a>
<a class="moz-txt-link-freetext" href="https://lists.bufferbloat.net/listinfo/bloat">https://lists.bufferbloat.net/listinfo/bloat</a>
</pre>
</blockquote>
<br>
</body>
</html>