Some tests were done on Comcast networks on cable plant. Slide deck below explains it: https://datatracker.ietf.org/meeting/118/materials/slides-11... Not sure where this leads but I guess ISPs will start charging toll for express lanes
L4S is not really an express lane. It is a way for applications to know when their traffic is congested, enabling them to scale DOWN their traffic to alleviate the congestion. Less congestion means less latency.
Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: RFC 9330
21–30 of 91 posts
Re: Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: RFC 9330
#22Earlier quoted context omitted.
I would assume the downvotes are because the comment is GPT-generated. People come here for the community's comments and insights, not for GPT's summarisations, even if you yourself find them useful. I personally agree with the downvotes - I don't want to see every HN post littered with "this is what GPT-4 has to say about this".
I think an AI summary, clearly marked as such, can be just as useful as the obligatory Archive link. I understand the aversion against „AI spam“, but I find it weird that a supposed tech community rejects AI tech wholesale.
Clearly labelled as LLM generated and used to summarise a long RFC (where I personally didn’t find the abstract as clear as GPTs summary).
But everyone will have their own views on this. There is definitely a lot of anti-AI or anti-LLM scepticism or denial on HN.
Re: Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: RFC 9330
#23Earlier quoted context omitted.
L4S is not really an express lane. It is a way for applications to know when their traffic is congested, enabling them to scale DOWN their traffic to alleviate the congestion. Less congestion means less latency.
How is that different to TCP congestion control?
Re: Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: RFC 9330
#24Re: Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: RFC 9330
#25How can you differentiate between L4S and non-L4S traffic at the network level, especially in mixed traffic environments?
Re: Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: RFC 9330
#26Re: Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: RFC 9330
#27Earlier quoted context omitted.
L4S is not really an express lane. It is a way for applications to know when their traffic is congested, enabling them to scale DOWN their traffic to alleviate the congestion. Less congestion means less latency.
How is that different to TCP congestion control?
Also, when the congestion signal disappears you can try to push the transfer speed up immediately, rather than slowly ramping back up like with TCP.
Re: Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: RFC 9330
#28> Center TCP (DCTCP) [RFC8257] and a Dual-Queue Coupled AQM [RFC9332]
this only exists to ask that cable modems (and maybe mobile phones?) use that too
Re: Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: RFC 9330
#29Earlier quoted context omitted.
I found this useful and don’t understand the downvotes.
There's literally an abstract at the top of this document which provides a summary. If you want more, you can feed it into chatgpt (or many other services) yourself, same as everyone here. There's no reason to post a summary as an unsolicited comment.
But sure, they could have just posted that instead of going through GPT. Doesn't really matter much imo.
Re: Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: RFC 9330
#30This thing is cool. I saw a live demo at IETF 118 in Prague last month. It totally eliminates buffer bloat, which makes it awesome for video chat. I saw the demo and was like "woah... I didn't think this would ever be possible." It requires an additional bit to be inserted into IP packets, to carry information about when buffers are full (I think?), but it actually works. It feels like living in the future!