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. _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
