RFC 8327: Mitigating the Negative Impact of Maintenance through BGP Session Culling
In plain English — editorial summary, not part of the RFC
This document outlines an approach to mitigate the 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 that will be affected by maintenance are forcefully torn down before the actual maintenance activities commence.
Document record
- Document ID
- RFC8327
- Published
- March 2018
- Authors
- W. Hargrave; M. Griswold; J. Snijders; N. Hilliard
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 10
- Also known as
- BCP214
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8212Default External BGP (EBGP) Route Propagation Behavior without PoliciesCurrent
July 2017
- RFC 8313Use of Multicast across Inter-domain Peering PointsCurrent
January 2018
- RFC 8195Use of BGP Large CommunitiesCurrent
June 2017
- RFC 8549Export of BGP Community Information in IP Flow Information Export (IPFIX)Current
April 2019
- RFC 8704Enhanced Feasible-Path Unicast Reverse Path ForwardingCurrent
February 2020
- RFC 7908Problem Definition and Classification of BGP Route LeaksCurrent
June 2016
- RFC 7854BGP Monitoring Protocol (BMP)Updated
June 2016
- RFC 9069Support for Local RIB in the BGP Monitoring Protocol (BMP)Updated
February 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?