From: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
To: netdev@vger.kernel.org
Subject: Re: netinet/ip.h and DSCP
Date: Mon, 12 Oct 2009 11:20:34 -0700 [thread overview]
Message-ID: <4AD37372.8090401@redfish-solutions.com> (raw)
In-Reply-To: <4AC68714.5080909@redfish-solutions.com>
Since linux-net doesn't seem to be the right forum...
On 10/02/2009 04:04 PM, Philip A. Prindeville wrote:
> Is there a reason that /usr/include/netinet/ip.h only contains
> definitions for ToS (precedence-based) markings?
>
> RFCs 2597/2598 have been out a *long* time... why is Linux so far behind
> the learning curve?
>
> We're discussing (at least here in the US) net neutrality... but if
> we're not marking our traffic the way we want it carried *anyway*, don't
> we deserve what we get if the carriers reshape our traffic by their own
> rules?
>
> Should there be definitions in netinet/ip.h like:
>
> #define IPTOS_DSCP_MASK 0xd0
> #define IPTOS_DSCP(x) ((x) & IPTOS_DSCP_MASK)
> #define IPTOS_DSCP_AF11 0x28
> #define IPTOS_DSCP_AF12 0x30
> #define IPTOS_DSCP_AF13 0x38
> #define IPTOS_DSCP_AF21 0x48
> #define IPTOS_DSCP_AF22 0x50
> #define IPTOS_DSCP_AF23 0x58
> #define IPTOS_DSCP_AF31 0x68
> #define IPTOS_DSCP_AF32 0x70
> #define IPTOS_DSCP_AF33 0x78
> #define IPTOS_DSCP_AF41 0x88
> #define IPTOS_DSCP_AF42 0x90
> #define IPTOS_DSCP_AF43 0x98
> #define IPTOS_DSCP_EF 0xb8
>
>
> Should be simple enough, right?
>
> Thanks,
>
> -Philip
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
parent reply other threads:[~2009-10-12 18:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4AC68714.5080909@redfish-solutions.com>]
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=4AD37372.8090401@redfish-solutions.com \
--to=philipp_subx@redfish-solutions.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).