Re: [Cake] ieee vs ietf stds for dscp mappings

[Jonathan Morton <chromatix99@gmail.com>]

> On 14 Nov, 2015, at 17:53, Sebastian Moeller <moeller0@gmx.de> wrote:
> 
> Is anybody actually using any of that? The set of differences between the schemes as RFCd for the different technologies makes me believe nobody is ever using more than one of those domains.

That’s part of the problem.  The various recommendations conflict with each other and with actual practice.

Note in particular the different treatments just of CS0 (default, and defined as Best Effort) and CS1 (defined as Background Traffic) - RFC 7561 actually gets them backwards!  The Szigeti-Baker draft is relatively sane and comprehensive, even though it differs from Cake’s schema in detail.

The core of the problem is that Diffserv was originally specified without a complete, working implementation of its PHBs (Per Hop Behaviours).  AFAIK, no such implementation exists to date - certainly no public one.  So there are ad-hoc, locally-defined approximations all over the place, and my chart illustrates some of that.

As well as the PHBs being poorly defined, it has become general practice for *networks* to set the DSCPs on traffic passing through them, rather than applications setting them at the endpoints.  This makes it difficult for applications to express their traffic characteristics and transport needs in general.  However, I think this practice has arisen because applications have not bothered to set their own DSCPs, due to their having no effect in most networks.

Dave noted previously that a lot of traffic gets marked as CS1 in Comcast’s network.  I’ve recently noticed the same about the Elisa/Saunalahti network over here, having got myself a 4G-capable receiver that came with a prepaid 1-month Saunalahti SIM.  DNA, my usual network, does something different - not sure whether it just doesn’t bother changing DSCPs, or does something more complex.

 - Jonathan Morton