I can attest to the technical validity of the solution proposed because this is exactly what we do at the Manitoba Internet Exchange when we do IXP maintenance. We shutdown the route server sessions for everyone and usually notice many participants sessions are still up. Then we apply v4 and v6 ACLs to cull BGP sessions between IX participants. About 15 minutes later there is no traffic flowing across the peering fabric and we are able to do whatever maintenance is required without causing next-hops to be unavailable and traffic to not flow. We have used this at least three times in my memory, and it has worked exactly as described/intended.
Thank you to the authors for writing this BCP Internet-Draft. As an operator of a relatively young IXP, it is very valuable to have these documents and best practices out there. We really appreciate them. Theodore Baschak - AS395089 - Hextet Systems https://bgp.guru/ - https://hextet.net/ http://mbix.ca/ - http://mbnog.ca/ On Sun, Mar 12, 2017 at 5:16 PM, Job Snijders <j...@ntt.net> wrote: > Dear GROW, > > With this BCP Internet-Draft we hope to draw some attention to good > practises which can be applied by IP networks or IXPs to mitigate > negative impact caused by maintenance operations on lower layer > networks. The idea is to promote the concept of breaking the > control-plane in a controlled fashion, before actually breaking the > data-plane. > > Regarding the "Voluntary BGP Session Teardown Recommendations" - we all > too often see operators do the equivalent of 'yanking the cable out of > its socket' while not allowing any time for reconvergence. As far as I > am aware, there is no documentation which recommends to shutdown BGP > sessions and allow for some time for the traffic to subside due to > rerouting, and then commence with the maintenance. > > Some background on the "Involuntary BGP Session Teardown > Recommendations": a number of years ago an (at the time novel) approach > was presented on how to reduce the negative impact of IXP maintenance. > Since then the idea gained popularity and is applied at more and more > IXPs. The video + pdf are available here: > https://ripe67.ripe.net/archives/video/116/ > > The approaches outlined in this document may not be required in every > network topology, for instance some IXPs have fantastic 'make before > break' methodologies accomplished through a layer of photonic switches. > > I'd like to ask the chairs for a 10 minute slot in GROW's session at > IETF 98 to present on this draft. > > Kind regards, > > Job > > ps. Some may point out that this is a rampant layering violation, to which > I > will say: "yes". ;-) > > ----- Forwarded message from internet-dra...@ietf.org ----- > > Date: Sun, 12 Mar 2017 14:00:18 -0700 > From: internet-dra...@ietf.org > To: i-d-annou...@ietf.org > Subject: I-D Action: draft-iops-grow-bgp-session-culling-00.txt > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : Mitigating Negative Impact of Maintenance > through BGP Session Culling > Authors : Will Hargrave > Matt Griswold > Job Snijders > Nick Hilliard > Filename : draft-iops-grow-bgp-session-culling-00.txt > Pages : 9 > Date : 2017-03-12 > > Abstract: > This document outlines an approach to mitigate negative impact on > networks resulting from maintenance activities. It includes guidance > for both IP networks and Internet Exchange Points (IXPs). The > approach is to ensure BGP-4 sessions affected by the maintenance are > forcefully torn down before the actual maintenance activities > commence. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-iops-grow-bgp-session-culling/ > > There's also a htmlized version available at: > https://tools.ietf.org/html/draft-iops-grow-bgp-session-culling-00 > > > Please note that it may take a couple of minutes from the time of > submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > I-D-Announce mailing list > i-d-annou...@ietf.org > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > ----- End forwarded message ----- > > _______________________________________________ > GROW mailing list > GROW@ietf.org > https://www.ietf.org/mailman/listinfo/grow >
_______________________________________________ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
