Subject: [NSIS] CLS-QOSM - mapping of unsued mandatory parameters

From: Bernd Schloer <[email-masked]>
Date: Fri, 11 Aug 2006 22:00:47 +0200

Hi,

here's a new idea of what to do with mandatory parameters which are not used by CLS.

The CLS-QOSM has a queueing mechanism with two priority levels: high priority 
for controlled-load(CL) and low priority for best-effort(BE) traffic. The 
queueing discipline used is the Token Bucket Filter (TBF) for CL and pfifo_fast 
for BE. The TBF limits the amount of traffic placed into the high priority queue.

<Excess Treatment>: defines the behaviour of the Traffic Conditioner for 
out-of-profile traffic

    0: drop, some or all packets are discarded
    1: shape, some or all packets are delayed
    2: remark, reclassification to BE
    3: no metering or policing, ...

<Bandwidth>: can be mapped to <TB>

    Bucket Rate = Bandwidth
    Bucket Size = ?
    Peak Rate   = ?
    Min Unit    = ?
    MTU         = ?

The rest of the mandatory parameters contain somehow priority. This priority is 
used to distinguish between BE and CL to choose the correct queueing mechanism.

<PHB Class>        : DSCP = 00000000 = default PHB = BE, other values = CL
<Y.1541 QoS Class> : Class 5 = BE, all others = CL
<DSTE Class Type>  : ?? what do the values 0..7 represent?
<Preemption & Def.>: Is there a range for BE?
<Admission Prio.>  : 0 = BE, 1 & 2 = CL
<RPH Priority>     : dsn.routine, drsn.routine, q735.4, ets.4, wps.4 = BE, other 
= CL

What do you think of it?

Bernd

_______________________________________________
nsis mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/nsis