From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) (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 74ED13B2A4 for ; Fri, 19 Mar 2021 04:25:19 -0400 (EDT) Received: by mail-wm1-x333.google.com with SMTP id n11-20020a05600c4f8bb029010e5cf86347so7977355wmq.1 for ; Fri, 19 Mar 2021 01:25:19 -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=YdVOS2oYJJV2M4VY+akdGEZYlXnSKUrZ2/G7i0My4Qo=; b=NPf0X5PqCy+julJJIUilRSQyrLSyakkAB+H8FsWd8oVS6/z11BXMow0r1B9epdI+pi H0Rz4F6P2g/zB4Js8b2lkiLdajmqW2DCBn1RvqEA95GTNWi/+lpwn8soJ3tdmyDhbaSb /yERk2ywQqGyEzDxmtLDLMYcrR/Ov5zWC7OG8HXOPjH7dP1v56UfLP90gV0Ae67Y5G7D 6mm+ZHFZOFvUezbzOJeXKGqklWfQt8atvjopYVOKbsCDnKHZayR46BaFHjdTqYTFyBC+ lZ8BTsEkJEsrY4rVe/qS0do7B31TUSgVpiuQHcJQb5lCmZD9hHPTDduZZqghhgjFa6RY 61ng== 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=YdVOS2oYJJV2M4VY+akdGEZYlXnSKUrZ2/G7i0My4Qo=; b=eX2enAR4Clg+eZ4QJ8zZHwtRsYD1kvtcP2OZSgmM+QKn3AvBZGPlPQbJFw0pKC2ow6 KBbk3230PH+OZfKCukSV09iNUsnVohJmPGUWywyUAtW1dZF3qPZJ3+8XnfDoMt26Ajy4 iYhOLjLBhdGCCR/iAJa5Dvhb/R8sYGM2iGDi91CAG9DWUJFg8Kyqw1F6uldRr41OOtVJ /G3fjCCTj/aoMNf21UyZjiKhHuCILNDk7JtoPPmNwVVCeBtQ7mFI5+OTWB/TMUctQYnw yAQaSkfrIRait55Q5/9nJ2CockL3M1/umFYxqjcnWZYFGMFDJj2+THyTN6qSTTtNIU+Y 8FzA== X-Gm-Message-State: AOAM531gjjCBmj4r4NNDxvK7O/N7cPZZ2RdmD1VLTwojUEh/Jjd4geCK 7lKVNVMmxOa5ZO7WUr9XA21m4Q== X-Google-Smtp-Source: ABdhPJzPj3CJYibvczJovwF/pMRpqDT0i/mRCXHJEHnetjxHjnEc2S7Ytwutl/Z7tY+KaAEp6HSckQ== X-Received: by 2002:a1c:6543:: with SMTP id z64mr2617178wmb.50.1616142318470; Fri, 19 Mar 2021 01:25:18 -0700 (PDT) Received: from [10.72.0.88] (h-1169.lbcfree.net. [185.193.85.130]) by smtp.gmail.com with ESMTPSA id p18sm8138280wro.18.2021.03.19.01.25.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 19 Mar 2021 01:25:18 -0700 (PDT) Message-ID: From: Pete Heist To: Dave Taht Cc: ECN-Sane Date: Fri, 19 Mar 2021 09:25:17 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.4 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Ecn-sane] 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 08:25:19 -0000 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. 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. >