<div>This work might interest some of you. Let us know your feedback!</div><div> </div><div><a href="https://tools.ietf.org/html/draft-iops-grow-bgp-session-culling-00" rel="noreferrer" class="gmail_msg" target="_blank">https://tools.ietf.org/html/draft-iops-grow-bgp-session-culling</a> </div><div> </div><div><div class="gmail_quote"><div>---------- Forwarded message --------- From: Job Snijders <<a href="mailto:job@ntt.net">job@ntt.net</a>> Date: Sun, 12 Mar 2017 at 23:16 Subject: draft-iops-grow-bgp-session-culling-00 To: <<a href="mailto:grow@ietf.org">grow@ietf.org</a>>, <<a href="mailto:draft-iops-grow-bgp-session-culling@ietf.org">draft-iops-grow-bgp-session-culling@ietf.org</a>> </div> 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: <a href="https://ripe67.ripe.net/archives/video/116/" rel="noreferrer" class="gmail_msg" target="_blank">https://ripe67.ripe.net/archives/video/116/</a> 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 a 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 <a href="mailto:internet-drafts@ietf.org" class="gmail_msg" target="_blank">internet-drafts@ietf.org</a> ----- Date: Sun, 12 Mar 2017 14:00:18 -0700 From: <a href="mailto:internet-drafts@ietf.org" class="gmail_msg" target="_blank">internet-drafts@ietf.org</a> To: <a href="mailto:i-d-announce@ietf.org" class="gmail_msg" target="_blank">i-d-announce@ietf.org</a> 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: <a href="https://datatracker.ietf.org/doc/draft-iops-grow-bgp-session-culling/" rel="noreferrer" class="gmail_msg" target="_blank">https://datatracker.ietf.org/doc/draft-iops-grow-bgp-session-culling/</a> There's also a htmlized version available at: <a href="https://tools.ietf.org/html/draft-iops-grow-bgp-session-culling-00" rel="noreferrer" class="gmail_msg" target="_blank">https://tools.ietf.org/html/draft-iops-grow-bgp-session-culling-00</a> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at <a href="http://tools.ietf.org" rel="noreferrer" class="gmail_msg" target="_blank">tools.ietf.org</a>. Internet-Drafts are also available by anonymous FTP at: <a href="ftp://ftp.ietf.org/internet-drafts/" rel="noreferrer" class="gmail_msg" target="_blank">ftp://ftp.ietf.org/internet-drafts/</a> _______________________________________________ I-D-Announce mailing list <a href="mailto:I-D-Announce@ietf.org" class="gmail_msg" target="_blank">I-D-Announce@ietf.org</a> <a href="https://www.ietf.org/mailman/listinfo/i-d-announce" rel="noreferrer" class="gmail_msg" target="_blank">https://www.ietf.org/mailman/listinfo/i-d-announce</a> Internet-Draft directories: <a href="http://www.ietf.org/shadow.html" rel="noreferrer" class="gmail_msg" target="_blank">http://www.ietf.org/shadow.html</a> or <a href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt" rel="noreferrer" class="gmail_msg" target="_blank">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a> ----- End forwarded message ----- </div></div>