nanog mailing list archives
Re: Multi-homed clients and BGP timers
From: Florian Weimer <fw () deneb enyo de>
Date: Mon, 25 May 2009 22:09:40 +0200
* Danny McPherson:
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.
See the subject of this thread. 8-) I don't think we're talking about full tables here, so you actually have to rely on keepalives (plus TCP retransmits).
Current thread:
- RE: Multi-homed clients and BGP timers, (continued)
- RE: Multi-homed clients and BGP timers Deepak Jain (May 22)
- Re: Multi-homed clients and BGP timers Steve Bertrand (May 22)
- Re: Multi-homed clients and BGP timers Jack Bates (May 22)
- Re: Multi-homed clients and BGP timers Steve Bertrand (May 22)
- RE: Multi-homed clients and BGP timers Ivan Pepelnjak (May 23)
- RE: Multi-homed clients and BGP timers Frank Bulk (May 24)
- RE: Multi-homed clients and BGP timers Ivan Pepelnjak (May 23)
- Re: Multi-homed clients and BGP timers Florian Weimer (May 25)
- Re: Multi-homed clients and BGP timers Danny McPherson (May 25)
- Re: Multi-homed clients and BGP timers Florian Weimer (May 25)
- IXP BGP timers (was: Multi-homed clients and BGP timers) Chris Caputo (May 25)
- Re: IXP BGP timers (was: Multi-homed clients and BGP timers) Andree Toonk (May 25)
- RE: IXP BGP timers (was: Multi-homed clients and BGP timers) John.Herbert (May 25)