RFC 8326: Graceful BGP Session Shutdown
In plain English — editorial summary, not part of the RFC
This document standardizes a new well-known BGP community, GRACEFUL_SHUTDOWN, to signal the graceful shutdown of paths. This document also describes operational procedures that use this well-known community to reduce the amount of traffic lost when BGP peering sessions are about to be shut down deliberately, e.g., for planned maintenance.
Document record
- Document ID
- RFC8326
- Published
- March 2018
- Authors
- P. Francois; B. Decraene; C. Pelsser; K. Patel; C. Filsfils
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 12
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8327Mitigating the Negative Impact of Maintenance through BGP Session CullingCurrent
March 2018
- RFC 8321Alternate-Marking Method for Passive and Hybrid Performance MonitoringObsoleted
January 2018
- RFC 8334Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)Current
March 2018
- RFC 8337Model-Based Metrics for Bulk Transport CapacityCurrent
March 2018
- RFC 8313Use of Multicast across Inter-domain Peering PointsCurrent
January 2018
- RFC 8340YANG Tree DiagramsUpdated
March 2018
- RFC 8341Network Configuration Access Control ModelCurrent
March 2018
- RFC 8342Network Management Datastore Architecture (NMDA)Updated
March 2018
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?