From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 709413CB35 for ; Tue, 12 Nov 2019 07:20:57 -0500 (EST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1573561256; bh=3G/yqSKkkcQoyTTimnq/vdND/Vij2bS7f9tu1LfMYuw=; h=From:To:Subject:In-Reply-To:References:Date:From; b=yrN25mK9vWIRhcnVxoSVhndhCPj4WR+zBZI2FtXqbZhWmzISkoX9fzaxjEs5JwYql jC1BpXmuH0P908SqWXHo796+8Qb3u/UnisV3Y6ndLR7LSmw4QesVl/joisscOuCEAW o0BUpnc6JvlGBoxdOB33Nyei1VBMnW+tumeRz/Vs7pCjERqi3yjsCeZsujXjF1sp+Y IkxatLTbHW+MlVa6nwdbIwYFFTSYPAmbTSC9brrGBHijajbiXpJPRnJ+Hk2HK5ScQ8 tnI4cuCKHyONHniUNbgBQW4vMMD4bJILlKEVRSTGnF+UqD+n2J5IHh/6TvdSCOZ+vb qTOsGoGq34nSw== To: Rich Brown , ecn-sane@lists.bufferbloat.net In-Reply-To: <1CF67BBC-B528-4667-97AE-760DCE027466@gmail.com> References: <1CF67BBC-B528-4667-97AE-760DCE027466@gmail.com> Date: Tue, 12 Nov 2019 13:20:55 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87y2wlp9p4.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Ecn-sane] Meanwhile, over on NANOG... 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: Tue, 12 Nov 2019 12:20:57 -0000 Rich Brown writes: > I saw this message crop up in the NANOG digest today... > https://mailman.nanog.org/pipermail/nanog/2019-November/104045.html Heh. The guy asking is from my ISP; I'm pretty sure I'm that customer... :D Ref: https://lists.bufferbloat.net/pipermail/ecn-sane/2019-September/000514.html I'm not on the nanog list, but feel free to cross-post; would be good to actually get to the bottom of this issue! Marek and I already had an off-list back-and-forth after that original thread, and we couldn't find anything wrong on the Cloudflare side. And the RSTs have a higher TTL than the actual traffic, indicating an in-path problem... -Toke