Thread (36 messages) flat view 36 messages, 4 authors, 2026-01-21

Re: [PATCH v9 net-next 04/15] tcp: ECT_1_NEGOTIATION and NEEDS_ACCECN identifiers

From: Eric Dumazet <edumazet@google.com>
Date: 2026-01-20 09:54:00
Also in: bpf, linux-doc, linux-kselftest

On Mon, Jan 19, 2026 at 7:59 PM [off-list ref] wrote:
From: Chia-Yu Chang <redacted>

Two CA module flags are added in this patch related to AccECN negotiation.
First, a new CA module flag (TCP_CONG_NEEDS_ACCECN) defines that the CA
expects to negotiate AccECN functionality using the ECE, CWR and AE flags
in the TCP header.

Second, during ECN negotiation, ECT(0) in the IP header is used. This patch
enables CA to control whether ECT(0) or ECT(1) should be used on a per-segment
basis. A new flag (TCP_CONG_ECT_1_NEGOTIATION) defines the expected ECT value
in the IP header by the CA when not-yet initialized for the connection.

The detailed AccECN negotiaotn during the 3WHS can be found in the AccECN spec:
  https://tools.ietf.org/id/draft-ietf-tcpm-accurate-ecn-28.txt
While for some reason linux uses icsk_ca_ops, I think the terminology
is about "CC : Congestion Control"

Not sure what CA means...

Reviewed-by: Eric Dumazet <edumazet@google.com>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help