From: Stephen Hemminger <shemminger@vyatta.com>
To: "Maciej Żenczykowski" <zenczykowski@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] netconsole: implement ipv4 tos support
Date: Wed, 30 Nov 2011 18:27:53 -0800 [thread overview]
Message-ID: <20111130182753.02798425@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <CANP3RGfwUr3ho3Tz_cfVz4CBJWMktOb7MDbUYYXz7XfjErw7Zg@mail.gmail.com>
On Wed, 30 Nov 2011 18:11:32 -0800
Maciej Żenczykowski <zenczykowski@gmail.com> wrote:
> > Why make it an option? TOS should always be set to interactive
> > traffic (like telnet and slogin)
>
> Because 'interactive' doesn't mean anything. You don't know what
> value of tos defines 'interactive' traffic on my network.
> I may also consider network console/debug/dump/etc traffic less
> important then say serving web traffic, and thus not even want it to
> be considered 'interactive' in the first place.
>
> TOS values are relevant within a LAN/WAN/Organization/AS, but are not
> relevant internet-wide.
> Almost all AS-boundary gateways/routers will do TOS remarking to their
> own internal specifications.
>
> - Maciej
Giving the user choice in general is good, but network configuration
is already confusing enough.
Although interpretation of TOS is per organization, in practice the
values are standardized in places like RFC4594. For example, routing protocols
all use IPTOS_PREC_INTERNETCONTROL = 0xc0
next prev parent reply other threads:[~2011-12-01 2:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 1:18 [PATCH] netconsole: implement ipv4 tos support Maciej Żenczykowski
2011-12-01 1:34 ` Stephen Hemminger
2011-12-01 2:11 ` Maciej Żenczykowski
2011-12-01 2:27 ` Stephen Hemminger [this message]
2011-12-01 8:59 ` Maciej Żenczykowski
2011-12-01 9:25 ` Maciej Żenczykowski
2011-12-01 3:50 ` Eric Dumazet
2011-12-01 9:07 ` Maciej Żenczykowski
2011-12-01 3:37 ` David Miller
2011-12-01 9:04 ` Maciej Żenczykowski
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=20111130182753.02798425@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=netdev@vger.kernel.org \
--cc=zenczykowski@gmail.com \
/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