RFC 8203: BGP Administrative Shutdown Communication
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9003.
Current version: RFC 9003 — Extended BGP Administrative Shutdown Communication
In plain English — editorial summary, not part of the RFC
This document enhances the BGP Cease NOTIFICATION message "Administrative Shutdown" and "Administrative Reset" subcodes for operators to transmit a short freeform message to describe why a BGP session was shutdown or reset. This document updates RFC 4486.
Document record
- Document ID
- RFC8203
- Published
- July 2017
- Authors
- J. Snijders; J. Heitz; J. Scudder
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 6
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6198Requirements for the Graceful Shutdown of BGP SessionsCurrent
April 2011
- RFC 8205BGPsec Protocol SpecificationUpdated
September 2017
- RFC 8207BGPsec Operational ConsiderationsCurrent
September 2017
- RFC 8092BGP Large Communities AttributeCurrent
February 2017
- RFC 7938Use of BGP for Routing in Large-Scale Data CentersCurrent
August 2016
- RFC 8502L2L3 VPN Multicast MIBCurrent
December 2018
- RFC 7899Multicast VPN State DampingCurrent
June 2016
- RFC 8538Notification Message Support for BGP Graceful RestartCurrent
March 2019
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?