<html xmlns:v="urn:schemas-microsoft-com:vml" 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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.ik-banner
{mso-style-name:ik-banner;
background:#E2E3E5;}
span.ik-footer
{mso-style-name:ik-footer;
background:#E2E3E5;}
span.EmailStyle22
{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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-IE" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">In terms of the standard itself the DOCSIS MULPI spec mandates that AQM must always be enabled on each Best Effort US service flow configured on the CM, along with a default target latency
of 10ms.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">AQM can be explicitly disabled, using the DISABLE AQM TLV configured on each US service flow configured in the CM Configuration file supplied during registration of the CM to the CMTS.
Similarly, explicit configuration using the TARGET LATENCY TLV is required to modify the default 10ms.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">It is entirely possible through the mechanics of DOCSIS provisioning that AQM could be enabled or disabled on different CMs or groups of CMs. Doing so would be rather petty and may add
additional unnecessary complexity to the provisioning system. Users that own their CMs are still paying for the internet access with the specific ISP, so would likely expect equivalent performance.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">User owned CMs connecting to ISPs are generally approved/accepted by that ISP, and a minimum expectation is that they are DOCSIS 3.1 certified (meaning 100% support for US AQM). US AQM
processing itself is purely confined within the CM itself and how it deals with each US service flow – it has not material impact on the CMTS, so a view that a non-ISP supplied CM running AQM might somehow negatively impact the CMTS would be without any foundation.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US">- Ian<o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="text-autospace:none"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Dave Taht <dave.taht@gmail.com><br>
<b>Date: </b>Wednesday 7 July 2021 at 03:11<br>
<b>To: </b>"Wheelock, Ian" <ian.wheelock@commscope.com><br>
<b>Cc: </b>"Livingood, Jason" <Jason_Livingood@comcast.com>, Aaron Wood <woody77@gmail.com>, "bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net><br>
<b>Subject: </b>Re: [Bloat] Really getting 1G out of ISP?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-line-height-alt:.75pt;background:white"></p></div><!--removed inky banner--><p class="MsoNormal"><o:p> </o:p></p>
</div>
<p style="margin:0cm">On Tue, Jul 6, 2021 at 3:28 PM Wheelock, Ian <ian.wheelock@commscope.com> wrote:<o:p></o:p></p>
<p style="margin:0cm">><o:p> </o:p></p>
<p style="margin:0cm">> The support for AQM (PIE) is mandatory in D3.1 modems regardless of the US mode in use (ie sc-qam (3.0) or ofdma (3.1) upstream), so it should be enabled.<o:p></o:p></p>
<p style="margin:0cm"> <o:p></o:p></p>
<p style="margin:0cm">I am under the distinct impression it is only on for ISP provided<o:p></o:p></p>
<p style="margin:0cm">modems for at least one ISP.<o:p></o:p></p>
<p style="margin:0cm"> <o:p></o:p></p>
<p style="margin:0cm">> Get Outlook for Android<o:p></o:p></p>
<p style="margin:0cm">><o:p> </o:p></p>
<p style="margin:0cm">> ________________________________<o:p></o:p></p>
<p style="margin:0cm">> From: Bloat <bloat-bounces@lists.bufferbloat.net> on behalf of Aaron Wood <woody77@gmail.com><o:p></o:p></p>
<p style="margin:0cm">> Sent: Tuesday, July 6, 2021 11:13:59 PM<o:p></o:p></p>
<p style="margin:0cm">> To: Livingood, Jason <Jason_Livingood@comcast.com><o:p></o:p></p>
<p style="margin:0cm">> Cc: bloat@lists.bufferbloat.net <bloat@lists.bufferbloat.net><o:p></o:p></p>
<p style="margin:0cm">> Subject: Re: [Bloat] Really getting 1G out of ISP?<o:p></o:p></p>
<p style="margin:0cm">><o:p> </o:p></p>
<p style="margin:0cm">> Are these in-flux changes to where the upstream split is why some modems report DOCSIS 3.1 downstream, but only 3.0 upstream? (and therefore aren't enabling AQM on the upstream?)<o:p></o:p></p>
<p style="margin:0cm">><o:p> </o:p></p>
<p style="margin:0cm">> -Aaron<o:p></o:p></p>
<p style="margin:0cm">><o:p> </o:p></p>
<p style="margin:0cm">> On Tue, Jun 22, 2021 at 4:04 PM Livingood, Jason via Bloat <bloat@lists.bufferbloat.net> wrote:<o:p></o:p></p>
<p style="margin:0cm">><o:p> </o:p></p>
<p style="margin:0cm">> > For DOCSIS the issue seems to be an unfortunate frequency split between up and downstream and use of lower efficiency coding schemes.<o:p></o:p></p>
<p style="margin:0cm">><o:p> </o:p></p>
<p style="margin:0cm">> Performance really takes a big step forward once a person has a D3.1 modem in their home, bringing OFDM and OFDMA as key advancements. Also in flux at the moment is where the upstream split is in cable networks, which are moving to mid-split
or high-split designs that bring more upstream bandwidth. As well, over the past 18+ months, most cable networks have added substantially more upstream channels as well as performed quite a number of fiber node splits. And that is just below the physical layer
stuff - there's also a lot of work at the software layer for modems and CMTSes that is quite interesting.<o:p></o:p></p>
<p style="margin:0cm">><o:p> </o:p></p>
<p style="margin:0cm">> JL<o:p></o:p></p>
<p style="margin:0cm">><o:p> </o:p></p>
<p style="margin:0cm">> _______________________________________________<o:p></o:p></p>
<p style="margin:0cm">> Bloat mailing list<o:p></o:p></p>
<p style="margin:0cm">> Bloat@lists.bufferbloat.net<o:p></o:p></p>
<p style="margin:0cm">> <a href="https://secure-web.cisco.com/1ONp6C2XmyCfN3ti15R4dj_0N3utHIeQ_etf8rF_YuPX9PY8HyOvcU-M-mKgEiJgb1K_B2h3x6WPCTUCVOrrS4YgUhza41owjh6HB8vTcAKMqNbcVtT6ym7vfN6GtSDKzHepnxefd8HEx0WXLTyAEVveRpFgQDNcL_rSZe1oTsqz3IH8X7dVj53lHVh3osO09T7ot_gEkGzPg-OVa28-RbNJxu-prknTw5jkzcU2Gg2c5Fr3-2v_wATMol4pgnePUhTHAcba998rdwi6xj2Nf1Nn0bkMqja4F58Q30KhsDfhjapErVB7gMbj8ekpAxhy0/https%3A%2F%2Flists.bufferbloat.net%2Flistinfo%2Fbloat">
https://secure-web.cisco.com/1ONp6C2XmyCfN3ti15R4dj_0N3utHIeQ_etf8rF_YuPX9PY8HyOvcU-M-mKgEiJgb1K_B2h3x6WPCTUCVOrrS4YgUhza41owjh6HB8vTcAKMqNbcVtT6ym7vfN6GtSDKzHepnxefd8HEx0WXLTyAEVveRpFgQDNcL_rSZe1oTsqz3IH8X7dVj53lHVh3osO09T7ot_gEkGzPg-OVa28-RbNJxu-prknTw5jkzcU2Gg2c5Fr3-2v_wATMol4pgnePUhTHAcba998rdwi6xj2Nf1Nn0bkMqja4F58Q30KhsDfhjapErVB7gMbj8ekpAxhy0/https%3A%2F%2Flists.bufferbloat.net%2Flistinfo%2Fbloat</a><o:p></o:p></p>
<p style="margin:0cm">><o:p> </o:p></p>
<p style="margin:0cm">> _______________________________________________<o:p></o:p></p>
<p style="margin:0cm">> Bloat mailing list<o:p></o:p></p>
<p style="margin:0cm">> Bloat@lists.bufferbloat.net<o:p></o:p></p>
<p style="margin:0cm">> <a href="https://secure-web.cisco.com/1ONp6C2XmyCfN3ti15R4dj_0N3utHIeQ_etf8rF_YuPX9PY8HyOvcU-M-mKgEiJgb1K_B2h3x6WPCTUCVOrrS4YgUhza41owjh6HB8vTcAKMqNbcVtT6ym7vfN6GtSDKzHepnxefd8HEx0WXLTyAEVveRpFgQDNcL_rSZe1oTsqz3IH8X7dVj53lHVh3osO09T7ot_gEkGzPg-OVa28-RbNJxu-prknTw5jkzcU2Gg2c5Fr3-2v_wATMol4pgnePUhTHAcba998rdwi6xj2Nf1Nn0bkMqja4F58Q30KhsDfhjapErVB7gMbj8ekpAxhy0/https%3A%2F%2Flists.bufferbloat.net%2Flistinfo%2Fbloat">
https://secure-web.cisco.com/1ONp6C2XmyCfN3ti15R4dj_0N3utHIeQ_etf8rF_YuPX9PY8HyOvcU-M-mKgEiJgb1K_B2h3x6WPCTUCVOrrS4YgUhza41owjh6HB8vTcAKMqNbcVtT6ym7vfN6GtSDKzHepnxefd8HEx0WXLTyAEVveRpFgQDNcL_rSZe1oTsqz3IH8X7dVj53lHVh3osO09T7ot_gEkGzPg-OVa28-RbNJxu-prknTw5jkzcU2Gg2c5Fr3-2v_wATMol4pgnePUhTHAcba998rdwi6xj2Nf1Nn0bkMqja4F58Q30KhsDfhjapErVB7gMbj8ekpAxhy0/https%3A%2F%2Flists.bufferbloat.net%2Flistinfo%2Fbloat</a><o:p></o:p></p>
<p style="margin:0cm"> <o:p></o:p></p>
<p style="margin:0cm"> <o:p></o:p></p>
<p style="margin:0cm"> <o:p></o:p></p>
<p style="margin:0cm">-- <o:p></o:p></p>
<p style="margin:0cm">Latest Podcast:<o:p></o:p></p>
<p style="margin:0cm"><a href="https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/">https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/</a><o:p></o:p></p>
<p style="margin:0cm"> <o:p></o:p></p>
<p style="margin:0cm">Dave Täht CTO, TekLibre, LLC<o:p></o:p></p>
<p style="margin:0cm"> <o:p></o:p></p>
</div>
</body>
</html>