On 1/27/26 9:09 PM, Jakub Kicinski wrote: > On Fri, 23 Jan 2026 11:07:16 +0100 [email protected] > wrote: >> Based on specification: >> https://tools.ietf.org/id/draft-ietf-tcpm-accurate-ecn-28.txt >> >> Based on Section 3.1.5 of AccECN spec (RFC9768), a TCP Server in >> AccECN mode MUST NOT set ECT on any packet for the rest of the connection, >> if it has received or sent at least one valid SYN or Acceptable SYN/ACK >> with (AE,CWR,ECE) = (0,0,0) during the handshake. >> >> In addition, a host in AccECN mode that is feeding back the IP-ECN >> field on a SYN or SYN/ACK MUST feed back the IP-ECN field on the >> latest valid SYN or acceptable SYN/ACK to arrive. > > FWIW this series is marked as Changes Requested in patchwork. > I don't think I did that, IDK why it's in that state :S
I was me. I went over the AI feedback and it looked legit and relevant to me: AFAICS the listener socket status is wrongly updated instead of the request socket and likely corrupted. I was sure I sent the feedback email before updating the series status, but I see it did not land anywhere - PEBKAC here, I'm sorry. /P
