From: rjmcmahon <rjmcmahon@rjmcmahon.com>
To: "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] Flash priority
Date: Sat, 09 Mar 2024 10:43:04 -0800 [thread overview]
Message-ID: <917dd3641c98e29c1d259aa32f1c2414@rjmcmahon.com> (raw)
In-Reply-To: <b07dfdecd67b71c02f632e1d4aecfac6@rjmcmahon.com>
I should note that I haven't evaluated ECN marks, just that 45 gets
passed to/fro
Bob
>> [JL] Quite true: each network tends to use DSCP marks on a
>> private/internal basis and so will bleach the DSCP marks on ingress
>> from peers. This will, however, change with the upcoming IETF RFC on
>> Non-Queue-Building (NQB) Per Hop Behavior -
>> https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-nqb. And I can
>> report that we at Comcast now permit DSCP-45 inbound for NQB packets,
>> in case developers would like to experiment with this (we just
>> finished updating router configs last week for residential users on
>> DOCSIS; FTTP and commercial are still in process).
>
> iperf 2 now supports a --dscp option as a convenience (vs setting the
> --tos byte.) I can confirm --dscp 45 is being passed over my xfinity
> hop to my linodes (now Akamai) servers in both directions at multiple
> colo locations.
>
> The --dscp is in the master branch.
> https://sourceforge.net/p/iperf2/code/ci/master/tree/ Older versions
> require --tos and setting the byte, e.g. 180
>
> Bob
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
next prev parent reply other threads:[~2024-03-09 18:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2416.1709929573.1074.nnagain@lists.bufferbloat.net>
2024-03-09 2:31 ` 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 ` [NNagain] [EXTERNAL] " Livingood, Jason
2024-03-09 18:38 ` [NNagain] " rjmcmahon
2024-03-09 18:43 ` rjmcmahon [this message]
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
[not found] <mailman.5.1710003601.27690.nnagain@lists.bufferbloat.net>
2024-03-09 17:56 ` [NNagain] Flash Priority Douglas Goncz A.A.S. M.E.T. 1990
2024-03-09 18:08 ` Dave Cohen
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=917dd3641c98e29c1d259aa32f1c2414@rjmcmahon.com \
--to=rjmcmahon@rjmcmahon.com \
--cc=DGoncz@replikon.net \
--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