Re: [rtcweb] DSCP marking for STUN packets

[James Polk <[e-mail]>]

At 12:16 AM 3/10/2014, Justin Uberti wrote:
>I think that the existing guidance should be sufficient in 
>non-multiplexing cases (i.e. BUNDLE). For consent checks, I think 
>the same DSCP markings as any other ICE connectivity checks should 
>be used; for ICE-for-SCTP checks, the same DSCP markings as media 
>packets (i.e. the SCTP traffic) should be used.
>
>If multiplexing is being performed, the connectivity checks probably 
>should use the highest DSCP value being used by the multiplexed media.

why is (seemingly) everyone's default position "use the highest DSCP 
available" for signaling packets?

You just need to make sure the packets aren't starved or dropped 
by/at congestion points.

James



>On Fri, Mar 7, 2014 at 4:35 AM, Muthu Arul Mozhi Perumal (mperumal) 
><<mailto:[e-mail]>[e-mail]> wrote:
>
>ICE says that an endpoint SHOULD apply the same DSCP marking as 
>media packets to connectivity checks. This looks insufficient for 
>RTCWEB, since it doesn't cover (at least) the following:
>
>- connectivity checks performed for a stream using different drop 
>pecedences (draft-dhesikan-tsvwg-rtcweb-qos).
>
>- connectivity checks performed for non-media/data-channel traffic.
>
>- DSCP markings for consent checks.
>
>
>
>Comments on where we need to specify them? The last one can probably 
>go into draft-ietf-rtcweb-stun-consent-freshness?
>
>
>
>Muthu
>
>_______________________________________________
>rtcweb mailing list
><mailto:[e-mail]>[e-mail]
>https://www.ietf.org/mailman/listinfo/rtcweb
>
>
>_______________________________________________
>rtcweb mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/rtcweb