On 5/31/10 1:30 PM, Ben Gardiner wrote:
On Tue, May 18, 2010 at 8:04 PM, Philip A. Prindeville
<philipp@xxxxxxxxxxxxxxxxxxxxx> wrote:
On 03/11/2010 12:29 PM, Philip A. Prindeville wrote:
On 03/11/2010 12:27 PM, David Miller wrote:
From: "Philip A. Prindeville"<philipp_subx@xxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 11 Mar 2010 12:21:11 -0700
And yes, there will always be misbehaving users. They are a fact of
life. That doesn't mean we should lobotomize the network. We don't
have an authentication mechanism on ICMP Redirects or Source-Quench,
Which is why most networks block those packets from the outside.
Nor is ARP authenticated.
Which is why people control who can plug into their physical
network.
None of the things you are saying support the idea of having
applications decide what the DSCP marking should be.
Does "decide what the DSCP marking should be" include complying to the recommendations of RFC-4594?
If anyone cares, here's an update:
I've submitted patches for QoS configuration for:
APR/Apache (stalled);
Proftpd (committed);
Openssh (pending review);
Firefox/Thunderbird (reviewed and on-track for commit);
Cyrus (committed);
Sendmail (submittted and acknowledged, but not yet reviewed);
Curl (stalled);
All, as per the request of the maintainers, default to either no QoS
markings or previous RFC-791 QoS markings if that's what they already
supported (Proftpd and Openssh).
If anyone can think of anything else that needs to be supported to
impact a significant portion of network (or enterprise intranet)
traffic, please call it out.
wget [1], like curl, is used for downloads of artifacts by some build systems.
[1] http://www.gnu.org/software/wget/
Ok, but I'm not sure that changes anything... what I was asking about
was other services not enumerated: not how the above services are used.
Sorry that wasn't clear.
-Philip
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
