Re: WMM classification guideline for applications?

[Johannes Berg <johannes@xxxxxxxxxxxxxxxx>]

On Fri, 2009-12-04 at 16:02 +0200, Kalle Valo wrote:

> Method 3 (IPv4 DSCP field) feels most portable to us, at least most,
> if not all, wifi drivers should use it. And, in theory, the receiver
> should also benefit from the classification, unless ISPs modify it of
> course. But the standardisation for IPv4 QoS bits is a mess and I
> don't really understand where the use of DSCP bits (as used in WMM
> implementations) is specified. 

http://tools.ietf.org/rfc/rfc2474.txt ?

> Also I was told that root privileges
> are needed to set this and that's somewhat cumbersome from application
> developer's point of view.

I don't see that IP_TOS, which will end up setting IP TOS/DSCP, requires
any elevated privileges:

        case IP_TOS:    /* This sets both TOS and Precedence */
                if (sk->sk_type == SOCK_STREAM) {
                        val &= ~3;
                        val |= inet->tos & 3; 
                }
                if (inet->tos != val) {
                        inet->tos = val;
                        sk->sk_priority = rt_tos2priority(val);
                        sk_dst_reset(sk);
                }
                break;

whereas, for instance:

        case IP_IPSEC_POLICY:
        case IP_XFRM_POLICY:
                err = -EPERM;
                if (!capable(CAP_NET_ADMIN))
                        break;

In any case, I think this topic would benefit of cross-posting to
netdev :)

johannes

Attachment: signature.asc
Description: This is a digitally signed message part