On Tue, 17 Aug 2004, Alex Conta wrote:I pointed you to the LINUX and CISCO examples.[...] No-one is doing rate-limiting of ICMP generation like that (because those would have to be configured by the users, and those will not just restrict ICMP generation, but ICMP forwarding etc as well). [...]
I think you're confused about what kind of rate-limiting is being specified in the ICMP spec.
Please read the specs before making these statements.
The text is clear in the ICMP specs: "...limit bandwidth and forwarding costs..."
Please read paragraph (f) page 7 of the ICMP specs, which says:
(f) Finally, in order to limit the bandwidth and forwarding costs
incurred by sending ICMPv6 error messages, an IPv6 node MUST
limit the rate of ICMPv6 error messages it sends.This points me to say that you must be confused, misinformed, or grossly misinterpreting.
[...]
We're not discussing rate-limiting of ICMP in general, just discussing the number of ICMP messages the node is allowed to generate on its own. (The point above!)
NO. This may be in your imagination.
We're discussing what is in the IPv6 ICMP specification.
A single limiter certainly wouldn't be sufficient if you wanted to limit e.g., the ICMP traffic the node is forwarding, but that's definitely out of scope of this specification!
You really need to read carefully the specification:
Text in paragraph (f) page 8 says clearly:
A recommended method for implementing the rate-limiting function
is a token bucket, limiting the average rate of transmission to
N, where N can either be packets/second or a fraction of the
attached link's bandwidth, but allowing up to B error messages
to be transmitted in a burst....note "transmission", "attached link bandwidth", "transmitted"?
NOTE: this very wording "attached link's bandwidth" suggest the connection between rate-control and interface.
alex
[...]
smime.p7s
Description: S/MIME Cryptographic Signature-------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
