Does the Differentiated Services Field have any effect in the real world

Question

We deliver realtime data to a large number of cellphone users worldwide, and toying with the idea of marking the data using the Differentiated Services Field in the packets to ensure the data gets there in a timely manner. Our data seems perfect for it, but we don't want to make congestion problems worse (or worse yet discover unknown router bugs/issues from a seldom used feature), so we were wondering if anyone had experience of this field being used in the wild. Do the packets turn up more often and in a more timely manner? Or do "Bad Things" happen if used on the big wide web.

As an aside we cracked open an incoming Skype call packet with Wireshark and noticed they set no priority bits, but perhaps this is because they are worried about being singled out?

Any experiences greatly appreciated.

Answer 1

If the packets stay within your own network then you can apply and control QoS polices using these DiffServ markings - effectively giving some traffic higher priority than others, with sensible limits and safeguards.

Once you go into someone else's network or onto the internet, most networks will reset or remove any Diffserver marking at the ingress point to the network.

This is because the network provider itself typically wants to decide which traffic, if any, to prioritise and will not be happy to leave it to clients of the network (unless you have an SLA or other agreement with the network provider to support some QoS scheme - some providers will support services which offer higher service then the typical best effort level, for example BT in the UK offer a priority broadband service, although I am not sure how much take up there is on these types of services).

Note that the service providers will often have QoS set up right to a customers home or premises to provide services like VoIP, IPTV etc - these require better than best effort generally.