Early Happy Eyeballs v3 implementation landed in #firefox Nightly, for now off by default. My #ietf 125 presentation:
| GitHub | https://github.com/mxinden/ |
| Homepage | https://max-inden.de/ |
Max Inden
@mxinden
- 134 Followers
- 141 Following
- 108 Posts
Network engineer working on #Firefox, focusing on HTTP/3 and #QUIC
Written summary is here:
https://mailarchive.ietf.org/arch/msg/happy/cIWasSSJw-zQEPhd4BzamKriOUc/
Rust library is here:
https://github.com/mozilla/happy-eyeballs/
Is this helpful?
YouTube
RFC EditorRFC 9849: TLS Encrypted Client Hello, E. Rescorla, et al., https://www.rfc-editor.org/info/rfc9849 #RFC This document describes a mechanism in Transport Layer Security (TLS) for encrypting a message under a server public key. This document is a product of the Transport Layer Security Working Group of the IETF.
Frederik Braun �The #Mozilla meetup is coming back to our lovely Berlin office! Haven't been yet? Come join us THIS THURSDAY with cool tech talks on browser privacy and offline LLMs on the web using WASM https://www.meetup.com/berlin-mozilla-meetup/events/312699118/
@djc not that I am aware of. The only requirement on quinn-udp is the ability to set and read ECN bits. (For others, which quinn-udp supports today.)
Based on this data, adoption of classic ECN (ECT0) is low. That said, I am excited for #L4S (ECT1) adoption in the future. #firefox 's #quic stack reflects all of the ECN marks, including ECT1. Thus Firefox is ready for L4S on the receive path already today.
RFC 9330: Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture
This document describes the L4S architecture, which enables Internet applications to achieve low queuing latency, low congestion loss, and scalable throughput control. L4S is based on the insight that the root cause of queuing delay is in the capacity-seeking congestion controllers of senders, not in the queue itself. With the L4S architecture, all Internet applications could (but do not have to) transition away from congestion control algorithms that cause substantial queuing delay and instead adopt a new class of congestion controls that can seek capacity with very little queuing. These are aided by a modified form of Explicit Congestion Notification (ECN) from the network. With this new architecture, applications can have both low latency and high throughput. The architecture primarily concerns incremental deployment. It defines mechanisms that allow the new class of L4S congestion controls to coexist with 'Classic' congestion controls in a shared network. The aim is for L4S latency and throughput to be usually much better (and rarely worse) while typically not impacting Classic performance.
Most connections never see an ECN Congestion Experienced (CE) mark. More specifically, for upload traffic, 99% of connections never receive a CE mark, for download traffic 75% of connections never receive a CE mark.
Upload:
Download:
