Talk:Type of service

TOS Flow Logic
The TOS Aflow logic in the section 'Type of Service' is severely flawed and was obviously written by a rank amateur. It has three places where 'drops the packet' mentioned.

Needs more explanation on what it's useful for. For example, when downloading big files, throughput is important, so it would be useful to choose a satellite connection. In contrast, when sending commands interactively to a remote machine on the other side of the world, a satellite would have too much latency; it's better to use a direct fiber-optic link (better latency). 201.212.126.164 19:54, 30 September 2007 (UTC)
 * Disagree. If you don't know what it's good for then you shouldn't be reading it. Period.

The diffserv code point seems wrong, that would be the reversed order for the bits. —Preceding unsigned comment added by Sylware (talk • contribs) 16:54, 20 February 2009 (UTC)

Cleanup
So I cleaned a bunch of stuff out of the article. TOS is is deprecated so I don't see the point in getting too specific about it, though more links and references is always good. 3M3RY (talk) 08:48, 22 December 2011 (UTC)

Which fields were actually used?
It sounds like the article contradicts itself regarding the original (pre-DSCP) Precedence and ToS fields: first it says "In practice, only the IP Precedence part of the field was ever used outside US DoD", but later "Although precedence field was part of IP version 4, it was never used", the exact opposite. --—grawity 15:17, 5 November 2021 (UTC)