On Mon, 16 Aug 2004, Fred Templin wrote: > In the case of logical (pt-to-pt) interfaces, actual per-source traffic > measurements may be readily available. In such cases, why would > an implementation use an aggregate estimator when it can easily > compute actual per-source values for rate limiting?? > > I vote for the "SHOULD" option for per-interface rate limiting > when per-source traffic measurements are available.
Are there any implementations doing this or interface-specific limiting? None that I know of, but please enlighten us if so. I don't think having such in a draft standard is acceptable. On the other hand, node-based token bucket limiters are commonplace, and work without any perceived problems AFAICS even behind slow/fast interfaces, behind tunnels, etc. -- why do we need to say more than that? -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings -------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
