[86471] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: BGP terminology question

daemon@ATHENA.MIT.EDU (Howard C. Berkowitz)
Mon Nov 7 08:33:16 2005

In-Reply-To: <17262.23844.626115.614224@roam.psg.com>
Date: Mon, 7 Nov 2005 08:32:38 -0500
To: nanog@merit.edu
From: "Howard C. Berkowitz" <hcb@gettcomm.com>
Errors-To: owner-nanog@merit.edu


At 9:44 AM -1000 11/6/05, Randy Bush wrote:
>  > A peer should never announce a route it has already announced unless 
>>  that route is withdrawn.
>
>one of many counterexamples: change in igp will cause change in
>med.  any attribute changes, and announcement is required.
>
>e.g., an internal igp oscillation could cause what the op
>describes.

For the OP, http://www.ietf.org/rfc/rfc3345.txt

home help back first fref pref prev next nref lref last post