Fri, Jun 30, 2017 at 03:26:08PM +0000, [email protected]: > > From: heasley [mailto:[email protected]] > Sent: Thursday, June 29, 2017 > > 8:28 PM > > > > Tue, Jun 27, 2017 at 01:14:34PM +0000, [email protected]: > > > > > > > > > > From: heasley [mailto:[email protected]] > Sent: Monday, June 26, > 2017 7:07 PM > > > > To: DECRAENE Bruno IMT/OLN > > > > Cc: [email protected] > > > > Subject: Re: [GROW] draft-ietf-grow-bgp-gshut > > > > > > > > Mon, Jun 26, 2017 at 01:57:54PM +0000, [email protected]: > > > > > > Suggestions: > > > > > > > > > > > > OLD Abstract: > > > > > > This draft describes operational procedures aimed at reducing > the > > > > > > amount of traffic lost during planned maintenances of routers > or > > > > > > links, involving the shutdown of BGP peering sessions. > > > > > > NEW Abstract: > > > > > > This draft describes operational procedures aimed at reducing > the > > > > > > amount of traffic lost during planned maintenances of routers > or > > > > > > links, involving the shutdown of BGP peering sessions. > Additionally > > > > > > this document describes the use of a well-known Border Gateway > > > > > > Protocol (BGP) community to signal that a graceful shutdown > has been > > > > > > initiated for the tagged prefix. > > > > > > > > > > [Bruno] OK. Slightly reworded as "It defines a well-known BGP > community, called > > gshut, to > > > > signal the graceful shutdown of paths to other Autonomous Systems." > > > > > > > > s/paths to other Autonomous Systems./a path in the presence of other > paths./ > > > > > > > > ie: it does nothing when there is no other path and it may not move to > > > > anoter AS, just to another path. it is per-session, not per-AS. > > > > > > My sentence was misleading. Changing to: "It defines a well-known BGP > community, > > called g-shut, to signal over the EBGP session to be shutdown, the > graceful shutdown of > > paths." > > > > As Jakob mentioned, its not ebgp-only, as it also addresses shutting an > > ibgp or an entire speaker. > > The procedure is not limited to ebgp. However the BGP community is defined in > order to perform the signaling specifically over EBGP. > Over IBGP, we use LOCAL_PREF to lower the preference of the route. Even if > the community may be kept for information.
you would still want to add the community; if you have no other path, you still want the community to be on routes to remote eBGP peers, if you have any in-bound iBGP policy that might affect the LP, you still want/need to communicate to the ibgp peers. _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
