[114737] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Multi-homed clients and BGP timers

daemon@ATHENA.MIT.EDU (Danny McPherson)
Mon May 25 14:18:56 2009

From: Danny McPherson <danny@tcb.net>
To: NANOG list <nanog@nanog.org>
In-Reply-To: <87bpph6qah.fsf@mid.deneb.enyo.de>
Date: Mon, 25 May 2009 12:18:47 -0600
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


On May 25, 2009, at 11:33 AM, Florian Weimer wrote:

> * Iljitsch van Beijnum:
>
>> 30 60 isn't a good choice because that means that after 30.1  
>> seconds a
>> keepalive comes in and then after 60.0 seconds the session will  
>> expire
>> while the second one would be there in 60.1 seconds.
>
> Wouldn't the underlying TCP retry sooner than that?

I suspect that given update messages serve as implicit
keepalives, it's _extremely rare that an actual keepalive
message is needed in global routing environments.

-danny



home help back first fref pref prev next nref lref last post