From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 494903B2A4 for ; Fri, 19 Mar 2021 05:18:49 -0400 (EDT) Received: by mail-wr1-x42b.google.com with SMTP id k8so8344808wrc.3 for ; Fri, 19 Mar 2021 02:18:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heistp.net; s=google; h=message-id:subject:from:to:cc:date:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=D3HDkhvKy1JF1XPP/8trpvVlYtiv0J4xV0yjrIKQekc=; b=ZmGfM42SYAt9I/6/0AeDKGy6MDzz5ohVxEOx+sF74cRFpCu1Bz+eW3EwYgs6K+ZoQi 8Z3ZHcZt1CbOk147uetqTpbr2LULN/tW+giiC6Nd2n6X6EHfyRXkcw4cxLeqgUvoJ2c1 34sZULX6RcYvBGel9LuftJSgthU1K3H6lmmtMiiE8+982tEKGBnfyLGCE8+mYOFe4+ui Xx5Zl0sKFVZdM7uekWOwsTP1m7P6JUFei9xzAK9S/kPGNstO6U826yAKg+X6oI8MSNZ1 fMnoleqFIPmiVM+KTHKYBzI2+4BRI/r1SQ4vgdGHjLyBhLAYp+/b4mQTAxUCWTxnT2Cw cwRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=D3HDkhvKy1JF1XPP/8trpvVlYtiv0J4xV0yjrIKQekc=; b=SZfUgtcK4JrKVOB76igdEUlWQ5F3njXkSldq+Bun5TNyjMJvKzx6jVEMlvs1Ybb0vD dvetJQ3qSWeCg8JjMkhwam7qsk1cVVtaJzvZCJJXGjebmlz5dquA0RA2WoNzVYMW6RTP SL1uX7mUdIPZq2RtRNwn44mCiZaaBV7YP3kUWMxeKOuq8RCRaiJDb9KFlHGabq1eeWbs MenyXrWXVSPdSh9r99mm4pahohBBrNyptz1CGOf05CsM3r/8EFu/Nx731hzITQMBa/Fc ybvdcc96b6E3g2PULXq+YCYGYbCQZuXh1PQSy0R4oGjk2AU+kZ+VOnJMCchI/haVfbac K/og== X-Gm-Message-State: AOAM532h4qBqPvPR+lLym8ks0Byp7fGWrn1VyMaCNy7ZjTt8dydL1xXA BETPgpZ5Wrn7kLL44l0ycaQr6w== X-Google-Smtp-Source: ABdhPJxJjp0K4pvznD8yDvFicmVSccySGSO9C8ePJZ9OvOPYsGLM9vovENlHBLGAihmy9Syp8Nlf3w== X-Received: by 2002:a5d:5906:: with SMTP id v6mr3490734wrd.137.1616145527591; Fri, 19 Mar 2021 02:18:47 -0700 (PDT) Received: from [10.72.0.88] (h-1169.lbcfree.net. [185.193.85.130]) by smtp.gmail.com with ESMTPSA id l9sm4976112wmq.2.2021.03.19.02.18.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 19 Mar 2021 02:18:47 -0700 (PDT) Message-ID: <73737060a1d857675ad5f44a17ddb30b342da5ba.camel@heistp.net> From: Pete Heist To: Sebastian Moeller Cc: ECN-Sane Date: Fri, 19 Mar 2021 10:18:44 +0100 In-Reply-To: <42F85394-FF4B-48BF-89B1-082D97CFA76C@gmx.de> References: <42F85394-FF4B-48BF-89B1-082D97CFA76C@gmx.de> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.4 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [Ecn-sane] re-marking ECT(1) to ECT(0) (was: mosh ecn bits washed out) X-BeenThere: ecn-sane@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of explicit congestion notification's impact on the Internet List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Mar 2021 09:18:49 -0000 ... On Fri, 2021-03-19 at 09:56 +0100, Sebastian Moeller wrote: > Hi Pete, > > > On Mar 19, 2021, at 09:25, Pete Heist wrote: > > > > Meaning, the negotiation succeeds and ECT(0) is set going up, but > > zeroed on packets by the time they come down? > > > > The negotiation can also be blocked with iptables --ecn-tcp-remove, > > which just zeroes out ECE and CWR, preventing negotiation > > (https://git.netfilter.org/iptables/tree/extensions/libipt_ECN.c), > > but > > I doubt that's very commonly done. > >         Oh, that looks interesting, probably not too hard to extend > this to also allow to selectively only re-map ECT(1) and or ECT(0). I > wonder what TCP Prague would do if its ECT(1) flows are switched to > ECT(0) in transit? I suspect it would then dominate all traffic in the C queue, or any other RFC3168 signalling queue (https://github.com/heistp/l4s-tests/#unsafety-in-shared-rfc3168-queues ). That might be an easy way to game the dual queue for higher throughput. Pete > Best Regards >         Sebastian > > > > > On Thu, 2021-03-18 at 13:00 -0700, Dave Taht wrote: > > > mosh, which has long had excellent support for ecn, appears to be > > > getting the > > > ecn bit washed out along my path from california to england. > > > > > > ecn survives up that way, but not down. > > > > > > Just a single data point thus far. > > > > > > > > > _______________________________________________ > > Ecn-sane mailing list > > Ecn-sane@lists.bufferbloat.net > > https://lists.bufferbloat.net/listinfo/ecn-sane >