[45054] in North American Network Operators' Group
Re: router startup behavior
daemon@ATHENA.MIT.EDU (Valdis.Kletnieks@vt.edu)
Mon Jan 14 16:17:21 2002
Message-Id: <200201142058.g0EKw9St004266@foo-bar-baz.cc.vt.edu>
To: Randy Bush <randy@psg.com>
Cc: David Schwartz <davids@webmaster.com>, nanog@merit.edu
In-Reply-To: Your message of "Mon, 14 Jan 2002 12:40:49 PST."
<E16QDuT-0002rF-00@rip.psg.com>
From: Valdis.Kletnieks@vt.edu
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1935011345P";
micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 14 Jan 2002 15:58:09 -0500
Errors-To: owner-nanog-outgoing@merit.edu
--==_Exmh_-1935011345P
Content-Type: text/plain; charset=us-ascii
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
--==_Exmh_-1935011345P
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001
iD8DBQE8Q0ZhcC3lWbTT17ARAqNNAKC8/aOpqZMfVsGbbv2OBpnF6SyI5QCcCQ5z
UbXipvKSrlqf/a7mpTIUweg=
=Y/0/
-----END PGP SIGNATURE-----
--==_Exmh_-1935011345P--
