[iccrg] Re: [tsvwg] [Call for participation] IETF 12 6 Hackathon on Testing Congestion Control and Queue Management Me chanisms

--===============1771587008549328298==
Content-Type: multipart/alternative; boundary="00000000000068d1c60656dc2557"

--00000000000068d1c60656dc2557
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks, Jason.

I have replied inline below:

On Sat, Jul 4, 2026 at 11:01=E2=80=AFPM Livingood, Jason <Jason_Livingood=
=3D
[email protected]> wrote:

> If you are looking for some fun extensions to this - perhaps consider
> testing these AQMs on the APs that the IETF meeting network uses, as I
> would love to see AQM in those APs.
>

Sure, let me talk to the network team.

FQ-PIE is available from OpenWrt 23.04 and above. I will check what we have
with the APs at the IETF.


> Also, perhaps test Meetecho using L4S via libwebrtc in Chromium.
>

This seems possible. We have a mobile phone with L4S for testing.


> The ultimate test for me is how much delay is there when someone plays a
> video in Meetecho in a meeting and it comes through so choppy and delayed=
 -
> seems like a prime candidate for AQM and L4S to improve.
>

Thanks for the suggestions. We will share an update on what we achieve,

Best Regards,
Mohit P. Tahiliani

>

--00000000000068d1c60656dc2557
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Thanks, Jason.=C2=A0<div><br></div><div>I=
 have replied inline below:</div></div><br><div class=3D"gmail_quote gmail_=
quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Jul 4, 2026 =
at 11:01=E2=80=AFPM Livingood, Jason &lt;Jason_Livingood=3D<a href=3D"mailt=
o:[email protected]">[email protected]</a>&gt; wrote:=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">



<div>
<div style=3D"direction:ltr;font-family:Aptos,Arial,Helvetica,sans-serif;fo=
nt-size:14pt;color:rgb(0,0,0)">
If you are looking for some fun extensions to this - perhaps consider testi=
ng these AQMs on the APs that the IETF meeting network uses, as I would lov=
e to see AQM in those APs.</div></div></blockquote><div><br></div><div>Sure=
, let me talk to the network team.</div><div><br></div><div>FQ-PIE is avail=
able from OpenWrt 23.04 and above. I will check what we have with the APs a=
t the IETF.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div><div style=3D"direction:ltr;font-family:Aptos,Arial,Helveti=
ca,sans-serif;font-size:14pt;color:rgb(0,0,0)"><span style=3D"background-co=
lor:transparent;font-size:14pt">Also, perhaps test Meetecho using L4S via l=
ibwebrtc in Chromium.</span></div></div></blockquote><div><br></div><div>Th=
is seems possible. We have a mobile phone with L4S for testing.</div><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div sty=
le=3D"direction:ltr;font-family:Aptos,Arial,Helvetica,sans-serif;font-size:=
14pt;color:rgb(0,0,0)"><span style=3D"background-color:transparent;font-siz=
e:14pt"> The ultimate test for me is how much delay is there when someone p=
lays a video in Meetecho in a meeting and it comes through so choppy and de=
layed - seems like a prime candidate for AQM and L4S
 to improve.</span></div></div></blockquote><div><br></div><div>Thanks for =
the suggestions. We will share an update on what we achieve,</div><div><br>=
</div><div>Best Regards,</div><div>Mohit P. Tahiliani</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex"><div><div id=3D"m_-1405164670837767610mai=
l-editor-reference-message-container">
</div>
</div>

</blockquote></div></div>

--00000000000068d1c60656dc2557--


--===============1771587008549328298==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KaWNjcmcgbWFp
bGluZyBsaXN0IC0tIGljY3JnQGlydGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4gZW1haWwg
dG8gaWNjcmctbGVhdmVAaXJ0Zi5vcmcK

--===============1771587008549328298==--