From: Stephen Hemminger <stephen@networkplumber.org>
To: Russell Strong <russell@strong.id.au>
Cc: netdev@vger.kernel.org
Subject: Re: IPv4 TOS vs DSCP
Date: Thu, 12 Nov 2020 08:13:06 -0800 [thread overview]
Message-ID: <20201112081306.0496a95b@hermes.local> (raw)
In-Reply-To: <20201112100954.62d696b6@192-168-1-16.tpgi.com.au>
On Thu, 12 Nov 2020 10:09:54 +1000
Russell Strong <russell@strong.id.au> wrote:
> Hello,
>
> After needing to do policy based routing based on DSCP, I discovered
> that IPv4 does not support this. It does support TOS, but this has
> never been upgraded to the new ( now quite old ) DSCP interpretation.
>
> Is there a historical reason why the interpretation has not changed?
>
> I could copy the dscp into a fwmark and then use that, but that seems a
> little unnecessarily complicated. If I were to change this, what would
> be the objections?
>
> Russell
Probably a couple of reasons: no one needed it badly enough to work on it.
And more importantly any change would have to retain the legacy behavior
as the default.
prev parent reply other threads:[~2020-11-12 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 0:09 IPv4 TOS vs DSCP Russell Strong
2020-11-12 16:13 ` Stephen Hemminger [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201112081306.0496a95b@hermes.local \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=russell@strong.id.au \
/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;
as well as URLs for NNTP newsgroup(s).