nanog mailing list archives
Re: router startup behavior
From: Valdis.Kletnieks () vt edu
Date: Mon, 14 Jan 2002 15:58:09 -0500
On Mon, 14 Jan 2002 12:40:49 PST, Randy Bush said:
a fix might be to not advertise any routes to a BGP peer until you receive all the routes that peer has to send you.and, of course, we can not know when a peer has sent all the routes it has to send to you.
Well, wait till it sends you the FIRST route, and then wait a fixed amount of time for it to finish babbling. Figuring out how long the OTHER end will wait for you to finish babbling before sending the first route is left as a trivial excersize... ;) -- Valdis Kletnieks Computer Systems Senior Engineer Virginia Tech
Attachment:
_bin
Description:
Current thread:
- router startup behavior Ratul Mahajan (Jan 14)
- Re: router startup behavior Jared Mauch (Jan 14)
- RE: router startup behavior Steve Naslund (Jan 14)
- RE: router startup behavior David Schwartz (Jan 14)
- RE: router startup behavior Randy Bush (Jan 14)
- Re: router startup behavior Valdis . Kletnieks (Jan 14)
- Re: router startup behavior Paul Donner (Jan 14)
- Re: router startup behavior Valdis . Kletnieks (Jan 14)
- RE: router startup behavior David Schwartz (Jan 14)
- Re: router startup behavior Yakov Rekhter (Jan 14)
- RE: router startup behavior Paul Donner (Jan 14)
- Re: router startup behavior Pierfrancesco Caci (Jan 14)
- Re: router startup behavior Lincoln Dale (Jan 15)
- <Possible follow-ups>
- RE: router startup behavior Steve Naslund (Jan 14)
- RE: router startup behavior Borchers, Mark (Jan 15)
- Re: router startup behavior Havard Eidnes (Jan 16)