From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (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 388E93B29D for ; Tue, 12 Nov 2019 07:07:47 -0500 (EST) Received: by mail-qt1-x82d.google.com with SMTP id y10so19465198qto.3 for ; Tue, 12 Nov 2019 04:07:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=pppoZ2Atu8RqXorWshgcM+1xAT9Qs+HE1wOT449+bOo=; b=Sgrtkc3XtJNLMnj55b/uZHv9WCQXf2PBJZ6NxdbCO2vHOg663pUiqXi/1uxH4h4or1 v77oX9W8ogiYuQCKeLSpuOnqcjS0l44Z4FyxNLxEKgKzjH01+rcgmw4P/KN1bk4d7ANq MFTgB+cwDXgsFICQiJNZD2j0Hw+g/ToxFtCko4+LTd1DmM47red0IbbHaeEyg4bOvF8Y 3NoynfNM6jBpmEZiSAcEkRzIEmQs7VKLU3ngcIRGsMez9Fykbk6jjDG/Hle5HnIGM35l sSOBYpgAzdXMnBPNxN1tVEixXtrb12NhCpoQAs+N4uqq4rCyLEOaR5jxFfINaSAY3tq0 dylw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=pppoZ2Atu8RqXorWshgcM+1xAT9Qs+HE1wOT449+bOo=; b=W0XpCOjfTNh+37mAEEIbsM/rcUGalU5jDaOe6f9ymkWtTDvtaBtVq7K/jQAxDLvSPk paUmSInkXiksWJgYhwm1Q8wdazROZpU7J1bL8rbA1USfO2RGFby/fk2B6Br9HHkvfVc0 XQpsfwsjXlOyMLOmBECnEAV1407IizJHGqhYrNkYaM6AHuPBhNLHh/dKvOb2J3w7agwy toTJL+/FTbzc43/5dZxA+P88mhYM3kYwoB+9Pf/KaQQpgwL7YOJybOgfyBE2PZpwlg+x A187jiPc0c2mr9EYi9Gy/HMYYoXHDoRGat0Z/PbKrTwF2UFYTVRiAc/25vqgpwJ6yRWI zr/A== X-Gm-Message-State: APjAAAX9CgWD8KxS9/bcWlzT/LJrq+MEGq2sT0NsmaDp83xuFeu1wObS b26Jda8f5fh5quQ3Yz5KlwJ3mIRT X-Google-Smtp-Source: APXvYqzqVW4Gy68QHKL17adSyG3iw/QUakgm15VUrGK2JFzyEsvNToSLQdVNgf50+x5fHAp81L1gDA== X-Received: by 2002:ac8:7085:: with SMTP id y5mr30523650qto.76.1573560466334; Tue, 12 Nov 2019 04:07:46 -0800 (PST) Received: from richs-mbp-10337.lan (pool-70-16-106-117.port.east.myfairpoint.net. [70.16.106.117]) by smtp.gmail.com with ESMTPSA id f21sm7549616qkl.34.2019.11.12.04.07.45 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Nov 2019 04:07:45 -0800 (PST) From: Rich Brown Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Message-Id: <1CF67BBC-B528-4667-97AE-760DCE027466@gmail.com> Date: Tue, 12 Nov 2019 07:07:45 -0500 To: ecn-sane@lists.bufferbloat.net X-Mailer: Apple Mail (2.3273) Subject: [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:07:47 -0000 I saw this message crop up in the NANOG digest today... = https://mailman.nanog.org/pipermail/nanog/2019-November/104045.html Rich > Message: 9 > Date: Mon, 11 Nov 2019 16:55:14 -0800 > From: Owen DeLong > To: Baldur Norddahl > Cc: nanog@nanog.org > Subject: Re: ECN > Message-ID: <59956815-A2BB-4DA3-AD57-C746C49FD617@delong.com> > Content-Type: text/plain; charset=3Dutf-8 >=20 >=20 >=20 >> On Nov 11, 2019, at 05:01 , Baldur Norddahl = wrote: >>=20 >> Hello >>=20 >> I have a customer that believes my network has a ECN problem. We do = not, we just move packets. But how do I prove it? >=20 > Are you saying that none of your routers support ECN or that you think = ECN only applies to endpoints? >=20 >> Is there a tool that checks for ECN trouble? Ideally something I = could run on the NLNOG Ring network. >>=20 >> I believe it likely that it is the destination that has the problem. >=20 > I=E2=80=99d say start with asking the reporter to provide a PCAP of = the problem and review the packet trace to provide clues of tap points > in your network to investigate where ECN is (or should be) occurring = and the opposite is occurring. >=20 > Owen >=20