*Contact emails:* martind...@google.com *Specification* RFC 9000, Section 13.4.1 <https://www.rfc-editor.org/rfc/rfc9000.html#name-reporting-ecn-counts>
*Chrome Status Entry* https://chromestatus.com/feature/5205722919600128 *Summary* A QUIC server might mark Explicit Congestion Notification (ECN) codepoints in IP headers (see RFC 3168 <https://www.rfc-editor.org/rfc/rfc3168.html> and RFC 9331 <https://datatracker.ietf.org/doc/rfc9331/> for why it might do this). When it does, Chrome will report the marking in QUIC ACK frames. This enables advanced congestion controls at those servers, which should improve latency and/or throughput when the server marks packets and bottleneck routers process those marks. There is no behavior change in Chrome other than slightly larger ACK frames, though it can trigger somewhat different behavior at servers and routers. There are no API changes and nothing client applications need to do, though server operators may want to investigate implementing RFC 3168 or RFC 9331 on their QUIC servers to leverage this capability. *Blink Components* Internals>Network>QUIC <https://issues.chromium.org/issues?q=customfield1222907:%22Internals%3ENetwork%3EQUIC%22> *Tracking Bug* crbug.com/40285166 *Estimated Milestone* M134 -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOLk%2BVMNW60MU_tENcorGUtuNkTXGy7Hr28AxLPZA%2B8CREnf5A%40mail.gmail.com.
