> On Dec 2, 2018, at 8:50 PM, Aseem Choudhary (asechoud) <[email protected]> > wrote: > > [AC] Diffserv behavior is defined in section 4. Based on it, policing is > defined inline or as template. The priority defined for queuing is not > mandatory and hence become priority entry based on whether defined or not. > Similarly for min-rate, max-rate. There is no specific reference to MDRR. The > queuing actions are defined as per classifier entry or as separate queuing > policy.
If there is no reference to MDRR, I find the following confusing:
identity mdrr-queuing-policy {
base compc-qos-policy;
}
...
must "((../sub-type != 'mdrr-queuing-policy') and " +
" (../sub-type != 'pwfq-queuing-policy')) or " +
"(((../sub-type = 'mdrr-queuing-policy') or " +
" (../sub-type = 'pwfq-queueing-policy')) and " +
...
container traffic-queue {
when "(../sub-type = 'mdrr-queuing-policy') or " +
"(../sub-type = 'pwfq-queuing-policy')" {
description
"Queuing policy properties";
}
(Twice)
...
case mdrr-queuing-policy {
when "../../../sub-type = 'mdrr-queuing-policy'" {
description
"MDRR queue handling properties for the traffic " +
"classified into current queue";
}
leaf mdrr-queue-weight {
type uint8 {
range "20..100";
}
units percentage;
}
}
--------------------------------------------------------------------------------
Victorious warriors win first and then go to war,
Defeated warriors go to war first and then seek to win.
Sun Tzu
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
