<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:14.0pt">Should be for COAM and leased. If you are having issues – you can email me 1:1 at this work address. Please include your modem make/model and account # so I can investigate. :-)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">JL<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Aaron Wood <woody77@gmail.com><br>
<b>Date: </b>Saturday, July 31, 2021 at 15:27<br>
<b>To: </b>Simon Barber <simon@superduper.net><br>
<b>Cc: </b>"Livingood, Jason" <Jason_Livingood@cable.comcast.com>, "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>, bloat <bloat@lists.bufferbloat.net><br>
<b>Subject: </b>[EXTERNAL] Re: [Bloat] Of interest: Comcast AQM Paper<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If we see that AQM appears to be not functioning as expected for upstream connections on DOCSIS3.1, what's the right avenue for getting that resolved? (and does that only apply to the Comcast-owned, vs. customer-owned, modems?)<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Sat, Jul 31, 2021 at 10:50 AM Simon Barber <<a href="mailto:simon@superduper.net">simon@superduper.net</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">Awesome to hear that you are turning this on both upstream and downstream. Do you know if the wifi stacks in your home routers also have AQM?<br>
<br>
Simon<br>
<br>
<br>
> On Jul 30, 2021, at 10:28 PM, Livingood, Jason via Bloat <<a href="mailto:bloat@lists.bufferbloat.net" target="_blank">bloat@lists.bufferbloat.net</a>> wrote:<br>
> <br>
> FYI that I will be presenting a lightning talk at the IRTF MAPRG meeting today at 17:30 ET (<a href="https://urldefense.com/v3/__https:/datatracker.ietf.org/meeting/111/materials/agenda-111-maprg__;!!CQl3mcHX2A!Rz15R4ZotXRWgIwMICwg0hP8rUn_zYmu7Xj_ujBrgBBYt5p7D8wGY4Toi7StQUQRf1LEmw$" target="_blank">https://datatracker.ietf.org/meeting/111/materials/agenda-111-maprg</a>).
The talk links to a just-published paper at <a href="https://urldefense.com/v3/__https:/arxiv.org/abs/2107.13968__;!!CQl3mcHX2A!Rz15R4ZotXRWgIwMICwg0hP8rUn_zYmu7Xj_ujBrgBBYt5p7D8wGY4Toi7StQUSKQx-diA$" target="_blank">
https://arxiv.org/abs/2107.13968</a> (click PDF link in upper right of page) that will likely be of interest to these two lists.<br>
> <br>
> High-level: turning on AQM in the cable modem (upstream queue) took working latency from around 250 ms to between 15-30 ms, which is actually kind of cool. ;-) AQM is turned on in all of our CMTSes (downstream queue) and in DOCSIS 3.1 modems (upstream queue).<br>
> <br>
> Have a nice weekend,<br>
> Jason<br>
> <br>
> _______________________________________________<br>
> Bloat mailing list<br>
> <a href="mailto:Bloat@lists.bufferbloat.net" target="_blank">Bloat@lists.bufferbloat.net</a><br>
> <a href="https://urldefense.com/v3/__https:/lists.bufferbloat.net/listinfo/bloat__;!!CQl3mcHX2A!Rz15R4ZotXRWgIwMICwg0hP8rUn_zYmu7Xj_ujBrgBBYt5p7D8wGY4Toi7StQUQ2nBiSiA$" target="_blank">
https://lists.bufferbloat.net/listinfo/bloat</a><br>
<br>
_______________________________________________<br>
Bloat mailing list<br>
<a href="mailto:Bloat@lists.bufferbloat.net" target="_blank">Bloat@lists.bufferbloat.net</a><br>
<a href="https://urldefense.com/v3/__https:/lists.bufferbloat.net/listinfo/bloat__;!!CQl3mcHX2A!Rz15R4ZotXRWgIwMICwg0hP8rUn_zYmu7Xj_ujBrgBBYt5p7D8wGY4Toi7StQUQ2nBiSiA$" target="_blank">https://lists.bufferbloat.net/listinfo/bloat</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>