Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: "Livingood, Jason" <jason_livingood@comcast.com>
To: "Sebastian Moeller" <moeller0@gmx.de>,
	"Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Cc: "Douglas Goncz A.A.S. M.E.T. 1990" <DGoncz@replikon.net>
Subject: Re: [NNagain] [EXTERNAL] Re:  Flash priority
Date: Sat, 9 Mar 2024 21:11:21 +0000	[thread overview]
Message-ID: <4CC2E1BD-2D21-4566-959F-690F10254B0A@comcast.com> (raw)
In-Reply-To: <CA5A737D-0B01-46A3-AE6C-BA138FB2EF80@gmx.de>

On 3/9/24, 10:04, "Sebastian Moeller" <moeller0@gmx.de <mailto:moeller0@gmx.de>> wrote:
> [SM] ...a big (probably the biggest) DOCSIS ISP in the USA had been remarking a noticeable fraction of packets to CS1 for years (which at a time was defined to mean background or lower priority and is treated as such by default WiFi APs) causing issues at end users' home networks. (Said ISP, to its credit, did fix the issue recently, but it tool a few years...).

[JL] Once the issue was escalated to me (thank you), it was fixed very quickly. ;-) 

> [SM] Since I have your attention, if I try comcast's bespoke networkQuality server (from your L4S tests)...I saw ECT(1) marking on my egressing packets, but none on the ingressing packets... that does not seem to be in line with the L4S RFCs (giving another example why RFC text alone is not sufficient for much). 

[JL] That is far from a production server and we've been making config changes to that box all last week as we prepare for more testing - I would not trust any recent results. But in any case, if you are not seeing ECN marks on packets coming back to you, and you are off-net, then something on the path back to you is bleaching. Feel free to send me a traceroute privately and we can continue to discuss it. 

Jason



  reply	other threads:[~2024-03-09 21:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2416.1709929573.1074.nnagain@lists.bufferbloat.net>
2024-03-09  2:31 ` [NNagain] " Douglas Goncz  A.A.S. M.E.T. 1990
2024-03-09  3:01   ` David Lang
2024-03-09 14:38     ` Livingood, Jason
2024-03-09 15:04       ` Sebastian Moeller
2024-03-09 21:11         ` Livingood, Jason [this message]
2024-03-09 18:38       ` rjmcmahon
2024-03-09 18:43         ` rjmcmahon
2024-03-09 21:01           ` Sebastian Moeller
2024-03-09 22:36             ` rjmcmahon
2024-03-10  2:52         ` Lee
2024-03-10  3:49           ` rjmcmahon
2024-03-09  3:22   ` Dick Roy
2024-03-09  9:41   ` Vint Cerf
2024-03-10 15:39     ` Joe Hamelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/nnagain.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CC2E1BD-2D21-4566-959F-690F10254B0A@comcast.com \
    --to=jason_livingood@comcast.com \
    --cc=DGoncz@replikon.net \
    --cc=moeller0@gmx.de \
    --cc=nnagain@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox