| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20111130182753.02798425@nehalam.linuxnetplumber.net> Date: Wed, 30 Nov 2011 18:27:53 -0800 From: Stephen Hemminger <shemminger@...tta.com> To: Maciej Żenczykowski <zenczykowski@...il.com> Cc: netdev@...r.kernel.org Subject: Re: [PATCH] netconsole: implement ipv4 tos support On Wed, 30 Nov 2011 18:11:32 -0800 Maciej Żenczykowski <zenczykowski@...il.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 -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists