nanog mailing list archives
Re: router startup behavior
From: Yakov Rekhter <yakov () juniper net>
Date: Mon, 14 Jan 2002 13:05:50 -0800
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.that will *greatly* reduce the garbage in the global routing table. to zero, in fact. and, of course, we can not know when a peer has sent all the routes it has to send to you.
draft-ietf-idr-restart-01.txt describes a way to do this (to find out when a peer has sent all the routes it has to send to you). yakov.
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)
- FW: router startup behavior Borchers, Mark (Jan 15)
- Re: FW: router startup behavior Simon Lockhart (Jan 15)
- Re: FW: router startup behavior Jared Mauch (Jan 17)
- Re: FW: router startup behavior Simon Lockhart (Jan 15)