Hacker News new | ask | show | jobs
by astro1138 502 days ago
> L4S pulls this off by giving internet packets an indicator that lets them know if they’ve run into congestion or queueing along any of the hops in their trip between a user and whatever they’re connecting to.

Sounds a lot like ECN (RFC 3168) which was specified in 2001.

2 comments

Apparently it relies on ECN, so that makes sense:

> It uses the Explicit Congestion Notification (ECN) protocol... Because ECN support is essential for L4S, senders use the ECN field as the protocol that allows the network to identify which packets are L4S and which are Classic.

https://datatracker.ietf.org/doc/rfc9330/

> The IETF's Transport Area Working Group (TSVWG) has finalized experimental RFCs for Low Latency, Low Loss, Scalable Throughput (L4S) and new Non-Queue-Building (NQB) per hop behavior. These documents describe a new architecture and protocol for deploying low latency networking.

https://datatracker.ietf.org/doc/draft-livingood-low-latency...

Found in their press release:

https://corporate.comcast.com/stories/comcast-kicks-off-indu...