RFC 7908: Problem Definition and Classification of BGP Route Leaks
In plain English — editorial summary, not part of the RFC
A systemic vulnerability of the Border Gateway Protocol routing system, known as "route leaks", has received significant attention in recent years. Frequent incidents that result in significant disruptions to Internet routing are labeled route leaks, but to date a common definition of the term has been lacking. This document provides a working definition of route leaks while keeping in mind the real occurrences that have received significant attention. Further, this document attempts to enumerate (though not exhaustively) different types of route leaks based on observed events on the Internet. The aim is to provide a taxonomy that covers several forms of route leaks that have been observed and are of concern to the Internet user community as well as the network operator community.
Document record
- Document ID
- RFC7908
- Published
- June 2016
- Authors
- K. Sriram; D. Montgomery; D. McPherson; E. Osterweil; B. Dickson
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8205BGPsec Protocol SpecificationUpdated
September 2017
- RFC 9234Route Leak Prevention and Detection Using Roles in UPDATE and OPEN MessagesCurrent
May 2022
- RFC 7854BGP Monitoring Protocol (BMP)Updated
June 2016
- RFC 8195Use of BGP Large CommunitiesCurrent
June 2017
- RFC 8212Default External BGP (EBGP) Route Propagation Behavior without PoliciesCurrent
July 2017
- RFC 8313Use of Multicast across Inter-domain Peering PointsCurrent
January 2018
- RFC 8327Mitigating the Negative Impact of Maintenance through BGP Session CullingCurrent
March 2018
- RFC 8549Export of BGP Community Information in IP Flow Information Export (IPFIX)Current
April 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?