Hi All,
As I sensed after all the discussion we had, the WG will prefer
to expand the text to prefer token-bucket method and describe
the limitations of the other two. If my conclusion is wrong,
feel free to scream :) Otherwise, here is the revised text.
Please review the text and let me know if we need to
add/modify/correct anything. If you want something to be
changed, please send me the new proposed text.
I couldn't decide what the correct default values of the
parameters should be. So I haven't mentioned anything. If
anyone wants to add, please send me the values.
=======================================================
(f) Finally, in order to limit the bandwidth and forwarding costs
incurred sending ICMPv6 error messages, an IPv6 node MUST limit
the rate of ICMPv6 error messages it sends. This situation may
occur when a source sending a stream of erroneous packets fails
to heed the resulting ICMPv6 error messages. There are a variety
of ways of implementing the rate-limiting function, for example:
(f.1) Timer-based - for example, limiting the rate of
transmission of error messages to at most once every T
milliseconds.
(f.2) Bandwidth-based - for example, limiting the rate at which
error messages are sent from a particular interface to
some fraction F of the attached link's bandwidth.
(f.3) Token-bucket based - for example, allowing up to B back-
to-back error messages to be transmitted in a burst, but
limiting the average rate of transmission to N where N
can either be packets/seconds or a fraction of the
attached link's bandwidth.
The limit parameters (e.g., T, F, B and N in the above examples)
MUST be configurable for the node.
Token-bucket based function should be preferrable over the other
two.
If Timer-based or Bandwidth-based function is chosen because of
the simplicity of implementation, proper care must be taken in
choosing the value of T or F. Values of T that are higher than
20-30 might break traceroute. A global value of F per node might
not be appropriate for all the links attached to the node.
=======================================================
Regards
Mukesh
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
