On Wednesday, May 09, 2012 7:57 AM, Jeffrey Haas <mailto:jh...@pfrc.org> wrote:
> On Tue, May 08, 2012 at 09:08:11PM -0400, Jakob Heitz wrote: >> On Monday, May 07, 2012 10:58 AM, Jeffrey Haas <> wrote: >>> An alternative before you get to such a stage is to perform BGP >>> graceful shutdown procedures on the session's routes. This permits >>> the routes to be routes of last resort until the issue is dealt >>> with. >> >> That raises the possibility that the routes are actually used. >> That may cause loops. > > I'm not talking about the routes we'd be doing "treat as withdraw", > I'm > talking about all of the otherwise "good" routes on the session. > > -- Jeff Sorry, I misunderstood. You mean for the case when a router does "treat as withdraw" for routes in an errored update message, but does not bring down the session, to deprefer the rest of the routes from that peer. Right? -- Jakob Heitz. _______________________________________________ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
