netinet/ip.h and DSCP

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux