[30676] in North American Network Operators' Group
Re: Community NO-EXPORT
daemon@ATHENA.MIT.EDU (Bradley Dunn)
Wed Aug 23 12:57:44 2000
Date: Wed, 23 Aug 2000 09:55:59 -0700
From: Bradley Dunn <bradley@dunn.org>
To: Kai Schlichting <kai@pac-rim.net>
Cc: nanog@merit.edu
Message-ID: <20000823095559.A21106@kookreport.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4.3.2.7.2.20000823100042.032977c0@mail.conti.nu>; from kai@pac-rim.net on Wed, Aug 23, 2000 at 10:03:21AM -0400
Errors-To: owner-nanog-outgoing@merit.edu
On Wed, Aug 23, 2000 at 10:03:21AM -0400, Kai Schlichting wrote:
> Correct me if I'm wrong, but isn't there a synchronization issue here
> as well? E.g.: AS2 is transit provider, probably has bgp synchronization
> on (default), and will only propagate routes to other AS's that have
> made it into their IGP. The question then is: have all 3 routes made
> it into AS2's IGP successfully? Only if the answer is yes, will it
> actually propagate that /16.
Synchronization is almost universally disabled in the real world.
None of the IGPs in use today would cope well with a full BGP
table redistributed into them. Redistribution of BGP->IGP is
rarely needed or advisable.
