Re: can you be constructive? Re: pls read the specs Re: Section 2.4, item (f) of draft-ietf-ipngwg-icmp-v3-04.txt

2004-08-19 Thread Pekka Savola
One set of answers to your earlier message.. This is probably past its usefulness. On Wed, 18 Aug 2004, Alex Conta wrote: 1. IP forwarding and ICMP generation is done in one processor, which also controls all interfaces. A host with multiple NICs can act as such a router. Sure. I say

can you be constructive? Re: pls read the specs Re: Section 2.4, item (f) of draft-ietf-ipngwg-icmp-v3-04.txt

2004-08-18 Thread Alex Conta
Pekka Savola wrote: [...] you seem to have a fundamental misunderstanding of the context of the word send in the rate-limiter specification [...] It is amusing for you to say that. As a co-author of the ICMPv6 RFC 2463, and RFC 1885, work which started in 1994, I have a good insight on the

RE: can you be constructive? Re: pls read the specs Re: Section 2.4, item (f) of draft-ietf-ipngwg-icmp-v3-04.txt

2004-08-18 Thread Mukesh . Gupta
Multiplying the ICMP rate a node originates by the number of interfaces should not make much of a difference operationally, and if a router has many interfaces it also has more paths to spread this traffic over. On the other hand, for a strictly software based router, having to

Re: can you be constructive? Re: pls read the specs Re: Section 2.4, item (f) of draft-ietf-ipngwg-icmp-v3-04.txt

2004-08-18 Thread Fred Templin
Mukesh, [EMAIL PROTECTED] wrote: So are you saying that the ICMPv6 spec is talking about rate limiting the ICMPv6 traffic that is being forwarded by a router ? If that is the case, Pekka is not alone. I also get the perception that it is talking about generating the ICMPv6 messages and NOT

Re: can you be constructive? Re: pls read the specs Re: Section 2.4, item (f) of draft-ietf-ipngwg-icmp-v3-04.txt

2004-08-18 Thread Fred Templin
Pekka Savola wrote: That's definitely out of scope of this *protocol* specification. They're just forwarded IP packets. More often than not, the router doesn't even know it's ICMPv6 (because it just looks at the destination address), and *cannot* even know that (e.g., there are extension headers,

Re: can you be constructive? Re: pls read the specs Re: Section 2.4, item (f) of draft-ietf-ipngwg-icmp-v3-04.txt

2004-08-18 Thread Havard Eidnes
[...], but consider the case that an L2 device on the path between routers A and B starts sending lots of ICMPs along the reverse path back through A. What should A do in that case? Attempt to forward all of the ICMPs, or use rate-limiting? Seen from A's side, doesn't this L2 device

RE: can you be constructive? Re: pls read the specs Re: Section 2.4, item (f) of draft-ietf-ipngwg-icmp-v3-04.txt

2004-08-18 Thread Mukesh . Gupta
Fred, That's definitely out of scope of this *protocol* specification. They're just forwarded IP packets. More often than not, the router doesn't even know it's ICMPv6 (because it just looks at the destination address), and *cannot* even know that (e.g., there are extension headers,

Re: can you be constructive? Re: pls read the specs Re: Section 2.4, item (f) of draft-ietf-ipngwg-icmp-v3-04.txt

2004-08-18 Thread Fred Templin
Hello Mukesh, [EMAIL PROTECTED] wrote: Fred If the router can know that they are error messages and can also know, e.g., that the errors are arriving at a disproportionally high rate with respect to the IPv6 packets that could have possibly generated them, then it should perform rate limiting.

Re: can you be constructive? Re: pls read the specs Re: Section 2.4, item (f) of draft-ietf-ipngwg-icmp-v3-04.txt

2004-08-18 Thread Alex Conta
Mukesh, [EMAIL PROTECTED] wrote: [...]I am rather interested in a quick positive outcome and a win-win situation. So are you saying that the ICMPv6 spec is talking about rate limiting the ICMPv6 traffic that is being forwarded by a router ? From a certain perspective, a router's system

Re: pls read the specs Re: Section 2.4, item (f) of draft-ietf-ipngwg-icmp-v3-04.txt

2004-08-17 Thread Pekka Savola
I will not respond to your other message as you seem to have a fundamental misunderstanding of the context of the word send in the rate-limiter specification, so any discussion about that would be useless. See the clarification below: On Tue, 17 Aug 2004, Alex Conta wrote: Please read the specs