Re: [Dart] RTP and non-RTP traffic on same UDP 5-tuple

[Ben Campbell <[e-mail]>]

On Jun 11, 2014, at 8:39 PM, Brian E Carpenter <[e-mail]> wrote:

>> What do you mean by 'all the packets would be classified the same'?  If you mean all the packets in a 5-tuple would get the same differentiated treatment, that is not desirable, because there are lots of folks wanting to send video i-frames or packets with FEC or other stuff with lower drop precedence than other packets.
> 
> Dan, if a packet crosses a diffserv domain boundary,
> the assumption is that (absent a specific SLA) its
> DSCP *will* be rewritten in whatever way the classifier
> of the receiving domain desires. DSCPs don't have end to
> end semantics, unless there is a string of SLAs along
> the path that all provide the same DSCP semantics.
> 
> Not everybody likes this, but it was what the operators
> in the diffserv WG wanted at the time.
> 
> If all operators agree to implement a common subset of
> the DSCPs suggested in various TSVWG documents, there would
> be a de facto end to end SLA for those DSCPs. But today,
> that's a bit of a dream world. So, for two arbitrary
> RTCweb users, there's certainly no assurance that the
> DSCP set at the source will be preserved until the
> destination. On the contrary, it's quite likely to
> be set to zero (at the boundary of an operator that
> distrusts the DSCP field) or to a value deemed suitable
> by an ingress classifier for whatever 5-tuple it carries.
> It seems unlikely that a classifier will look further
> into the payload than the port numbers.

I think I understand your meaning, but just to be sure:

Even if the packets with the same 5-tuple have different DSCPs, the are likely to get reset to the same DSCP (probably zero)  at a boundary, because the classifier either ignores or distrusts the original markings entirely? (As opposed to remapping any given DSCP to a different DSCP, but maintaining some distinction within the flow.)

Thanks!

Ben.