Enable QUIC ECN reporting
Categories
(Core :: Networking, enhancement, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox140 | --- | fixed |
People
(Reporter: mail, Assigned: mail)
References
Details
(Whiteboard: [necko-triaged] )
Attachments
(1 file)
Bug 1918070 introduced the network.http.http3.ecn
pref, enabled on Firefox Nightly. When true
, Firefox would (a) mark and (b) report ECN.
Bug 1948739 enabled the pref on Firefox Beta.
With the pref set to true
, we see around 2% of ECN blackholes, i.e. network paths that drop all ECN marked datagrams. Such a blackhole leads to significant connection establishment delay.
While we are hesitant to enable ECN marking on Firefox Release, we can already ship ECN reporting.
I suggest we split the ECN pref into two, one for marking (prone to ECN blackholes) and one for reporting (no known issues). The former we will keep on Beta only, the latter we can have ride the trains.
Bug 1918070 introduced the network.http.http3.ecn
pref, enabled on
Firefox Nightly. When true
, Firefox would (a) mark and (b) report ECN.
Bug 1948739 enabled the pref on Firefox Beta.
With the pref set to true
, we see around 2% of ECN
blackholes, i.e. network
paths that drop all ECN marked datagrams. Such a blackhole leads to
significant connection establishment
delay.
While we are hesitant to enable ECN marking on Firefox Release, we can
already ship ECN reporting.
This commit splits the ECN pref into two, one for marking (prone to ECN
blackholes) and one for reporting (no known issues). The former we will
keep on Beta only, the latter we can have ride the trains.
Description
•