Closed job closed 7 years ago
draft-ietf-grow-bgp-gshut was abandoned. if this changes in future, we'll reconsider a patch.
One of the authors stated:
We will revive it, probably removing the non-transitive community part.
https://mailarchive.ietf.org/arch/msg/grow/hqrJ0vpsVVspEWTadpBZw3vin-M
You want to wait 2 weeks? Or until RFC status?
for this, rfc status + demand from ixp operators
people weren't asking for semiconductors either ¯\_(ツ)_/¯
nor rollerblade high heels:
https://qph.ec.quoracdn.net/main-qimg-3b06239fc13829001b5054a8c46d36f2-c
Intro
https://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-06 (
gshut
for short) introduces a well-known BGP community65535:0
to signal to an adjacent network that the path will disappear due to upcoming maintenance, and as such they should hunt for other paths.Implementing the receiving side is straight forward:
And then just add the appropriate
allow_graceful_shutdown();
calls to the filters. I think this can be enabled by default.This way route server participants can use the graceful shutdown mechanism to signal to the route server that soon the path through them will be unavailable and the route server should select another path (if there is any).