If we decide to keep the Timer-based method, another problem
is to decide the value of T (not more than one icmp to a given
source every T milliseconds). 1 ms might be overwhelming for
a 64 kpbs link and 100 ms will be over-restricting for 10 
gbps link.

What about we keep the Timer-based method, discuss the 
advantages and disadvantages and suggest keeping the value
of T configurable per link so that the administrator can
decide the correct value of T based on the bandwidth of the
link.

Do we all agree to remove the Bandwidth-based method ??

Regards
Mukesh

> -----Original Message-----
> From: ext Pekka Savola [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 06, 2004 9:44 AM
> To: Fred Templin
> Cc: Francis Dupont; Gupta Mukesh (Nokia-NET/MtView); [EMAIL PROTECTED]
> Subject: Re: draft-ietf-ipngwg-icmp-v3-02.txt: Rate Limiting Methods 
> 
> 
> On Tue, 6 Jan 2004, Fred Templin wrote:
> > Asterisks already appear all the time using 'traceroute'. 
> That is why
> > three responses are solicited from each hop and the process proceeds
> > to the next hop even if only one response is received. 
> (Indeed, many of
> > the traceroutes I have seen will "knock three times" 
> repeatedly when a
> > non-responsive hop is encountered.)
> 
> Right.  But in my opinion, we want to optimize for the case that we 
> don't have to fall back to the timeouts unnecessarily.  Multiple 
> seconds' delay at each misbehaving hop is inappropriate.
>   
> > I agree that the traceroute example is a weak one, and not 
> sufficient
> > reason to exclude valid implementation alternatives.
> 
> We'll just have to disagree on this.  Internet traffic is
> characteristically rather bursty.  The rate-limitng functions have to
> be able to deal with 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
--------------------------------------------------------------------

Reply via email to