* Re: [Starlink] The "reasons" that bufferbloat isn't a problem
@ 2024-05-08 9:31 David Fernández
2024-05-08 11:32 ` [Starlink] [Bloat] L4S Rich Brown
0 siblings, 1 reply; 2+ messages in thread
From: David Fernández @ 2024-05-08 9:31 UTC (permalink / raw)
To: starlink
[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]
I see that L4S is not really solving everything (I read about issues with
Wi-Fi), although it seems to be a step in the right direction, to be
improved, let's hope.
At least, Nokia is implementing it in its network gear (for mobile
operators), so the bufferbloat problem is somehow acknowledged by industry,
at least initially or partially.
I have seen two consecutive RFCs to 9330:
https://www.rfc-editor.org/info/rfc9331
https://www.rfc-editor.org/info/rfc9332
I suspect that optimal results require the bufferbloat to be addressed not
only at network layer (IP), but also with some pipelining or cross-layering
at link level (Ethernet, Wi-Fi or any other link technology, such as 5G,
SATCOM, VHF...)
Regards,
David F.
Date: Tue, 7 May 2024 08:46:03 -0400
From: Dave Collier-Brown <dave.collier-Brown@indexexchange.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] The "reasons" that bufferbloat isn't a problem
Message-ID: <3d6bdccf-e3d1-4f62-a029-25bfd1f458f5@indexexchange.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
It has an RFC at https://datatracker.ietf.org/doc/rfc9330/
I read it as a way to rapidly find the available bandwidth without the TCP
"sawtooth". The paper cites fc_codel and research based on it.
I suspect My Smarter Colleagues know more (;-))
--dave
On 2024-05-07 08:13, David Fernández via Starlink wrote:
Is L4S a solution to bufferbloat? I have read that gamers are happy with it.
Sorry, I read it here, in Spanish:
https://www.adslzone.net/noticias/operadores/retardo-videojuegos-nokia-vodafone
Regards,
David F.
[-- Attachment #2: Type: text/html, Size: 2553 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Starlink] [Bloat] L4S
2024-05-08 9:31 [Starlink] The "reasons" that bufferbloat isn't a problem David Fernández
@ 2024-05-08 11:32 ` Rich Brown
0 siblings, 0 replies; 2+ messages in thread
From: Rich Brown @ 2024-05-08 11:32 UTC (permalink / raw)
To: David Fernández; +Cc: starlink, bloat
[-- Attachment #1: Type: text/plain, Size: 2430 bytes --]
Let's split this thread and use this message to continue the discussion of L4S. Thanks
> On May 8, 2024, at 5:31 AM, David Fernández via Starlink <starlink@lists.bufferbloat.net> wrote:
>
> I see that L4S is not really solving everything (I read about issues with Wi-Fi), although it seems to be a step in the right direction, to be improved, let's hope.
>
> At least, Nokia is implementing it in its network gear (for mobile operators), so the bufferbloat problem is somehow acknowledged by industry, at least initially or partially.
>
> I have seen two consecutive RFCs to 9330:
> https://www.rfc-editor.org/info/rfc9331 <https://www.rfc-editor.org/info/rfc9331>
> https://www.rfc-editor.org/info/rfc9332 <https://www.rfc-editor.org/info/rfc9332>
>
> I suspect that optimal results require the bufferbloat to be addressed not only at network layer (IP), but also with some pipelining or cross-layering at link level (Ethernet, Wi-Fi or any other link technology, such as 5G, SATCOM, VHF...)
>
> Regards,
>
> David F.
>
> Date: Tue, 7 May 2024 08:46:03 -0400
> From: Dave Collier-Brown <dave.collier-Brown@indexexchange.com <mailto:dave.collier-Brown@indexexchange.com>>
> To: starlink@lists.bufferbloat.net <mailto:starlink@lists.bufferbloat.net>
> Subject: Re: [Starlink] The "reasons" that bufferbloat isn't a problem
> Message-ID: <3d6bdccf-e3d1-4f62-a029-25bfd1f458f5@indexexchange.com <mailto:3d6bdccf-e3d1-4f62-a029-25bfd1f458f5@indexexchange.com>>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> It has an RFC at https://datatracker.ietf.org/doc/rfc9330/ <https://datatracker.ietf.org/doc/rfc9330/>
>
> I read it as a way to rapidly find the available bandwidth without the TCP "sawtooth". The paper cites fc_codel and research based on it.
>
> I suspect My Smarter Colleagues know more (;-))
>
> --dave
>
>
>
> On 2024-05-07 08:13, David Fernández via Starlink wrote:
> Is L4S a solution to bufferbloat? I have read that gamers are happy with it.
>
> Sorry, I read it here, in Spanish:
> https://www.adslzone.net/noticias/operadores/retardo-videojuegos-nokia-vodafone <https://www.adslzone.net/noticias/operadores/retardo-videojuegos-nokia-vodafone>
>
> Regards,
>
> David F.
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
[-- Attachment #2: Type: text/html, Size: 3894 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2024-05-08 11:32 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-05-08 9:31 [Starlink] The "reasons" that bufferbloat isn't a problem David Fernández
2024-05-08 11:32 ` [Starlink] [Bloat] L4S Rich Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox