From: Jim Nguyen (nhatquang@thiennam.org)
Date: Tue Apr 12 2005 - 01:55:43 GMT-3
from CCO
Extended Burst Value
Extended burst is configured by setting the extended burst value greater than
the normal burst value. Setting the extended burst value equal to the normal
burst value excludes the extended burst capability. If extended burst is not
configured, given the example scenario, the exceed action of CAR takes effect
because a sufficient number of tokens are not available.
from DQOS
With Bc and Be configured, CAR uses dual token buckets, and the CAR algorithm
gets more complicated. The algorithm is easy and familiar:
1 If the number of bytes in the packet is less than or equal to (<=) the
number of tokens in Bucket1, the packet conforms. CAR also removes tokens from
Bucket1 equal to the number of bytes in the packet and performs the action for
packets that conform to the contract.
2 If the number of bytes in the packet is greater than (>) the number of
tokens in Bucket1, CAR uses the debt calculations to determine whether the
packet conforms or exceeds. CAR removes tokens from Bucket2 equal to the
number of bytes in the packet if the packet conforms based on this rule.
it seems that from CCO, CAR uses 1 token bucket so it says "Setting the
extended burst value equal to the normal burst value excludes the extended
burst capability", but from DQOS, it uses 2 token buckets one for Bc and
another for Be same as police. Any ideal? Anyone can shed the light on this?
This archive was generated by hypermail 2.1.4 : Tue May 03 2005 - 07:54:56 GMT-3