Re: [rtcweb] Some language on "prioritization"

[Harald Alvestrand <[e-mail]>]

I assume this is the scheduler envisioned in -ndata:


      SCTP_SS_PRIORITY:  Scheduling with different priorities is used.
         Streams having a higher priority will be scheduled first and
         when multiple streams have the same priority, the default
         scheduling should be used for them.  The priority can be
         assigned with the sctp_stream_value struct.  The higher the
         assigned value, the lower the priority, that is the default
         value 0 is the highest priority and therefore the default
         scheduling will be used if no priorities have been assigned.


This sounds like a "strict" scheduler, in that higher priority queues
will starve out lower priority ones completely. I remember having the
discussion at an IETF meeting about whether we wanted a "strict"
scheduler or a "weighted round robin" scheduler for this, but I wouldn't
trust my memory with what the conclusion was.

Was the conclusion that we should do "strict" scheduling? If so, it may
be best to make that consistent across the board - I had written in a
"weighted" scheduler for media into the prioritization text that I
started this thread with, but I think there's value to consistency.

(Note: -ndata has SS_PRIORITY in one place and SS_PRIO / SS_PRIO_INTER
in another place. Is there a subtlety here I'm not seeing?)