Hello I think I see how container meter-cfg is intended to allow configuration of RFC 2697 and 2698 style meters (by linking two meters in the meter-list via the pointer next-meter-id). But it seems to me that a way to indicate overflow from one bucket to another during token update is needed. In RFC 2697, bucket E is incremented only if bucket C is full, i.e. C overflows into E. In RFC 2698, buckets C and P are updated independently.
The Metro Ethernet Forum's Bandwidth Profile Algorithm explicitly supports configuring this type of coupling, via parameter CF, "coupling flag". It's not clear to me how RFC 2697 can be supported by concatenating the meters in the YANG model, unless there is a way to indicate overflow between them. Ferdi Pienaar Alcatel Shanghai-Bell _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
