RFC 4486: Subcodes for BGP Cease Notification Message
In plain English — editorial summary, not part of the RFC
This document defines several subcodes for the BGP Cease NOTIFICATION message that would provide more information to aid network operators in correlating network events and diagnosing BGP peering issues. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4486
- Published
- April 2006
- Authors
- E. Chen; V. Gillet
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 6
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4659BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPNCurrent
September 2006
- RFC 4277Experience with the BGP-4 ProtocolCurrent
January 2006
- RFC 4276BGP-4 Implementation ReportCurrent
January 2006
- RFC 4275BGP-4 MIB Implementation SurveyCurrent
January 2006
- RFC 4274BGP-4 Protocol AnalysisCurrent
January 2006
- RFC 4273Definitions of Managed Objects for BGP-4Current
January 2006
- RFC 4272BGP Security Vulnerabilities AnalysisCurrent
January 2006
- RFC 4724Graceful Restart Mechanism for BGPUpdated
January 2007
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?