This read-only counter tallies bytes permitted by this interface. Because CAR's rate limit is fundamentally a bits-per-second contract, this byte counter, converted to a rate over time, is what actually needs to be checked against ccarConfigRate to judge conformance, since packet counts alone can be misleading if packet sizes vary significantly. An entry could show ccarStatSwitchedPkts growing at a modest pace while this byte counter grows much faster than expected, if the conforming traffic happens to consist of unusually large packets.