Skip to main content

Methods for Detection and Mitigation of BGP Route Leaks

Document Type Replaced Internet-Draft (idr WG)
Expired & archived
Authors Kotikalapudi Sriram , Alexander Azimov
Last updated 2019-04-18
Replaces draft-sriram-idr-route-leak-detection-mitigation
Replaced by draft-ietf-grow-route-leak-detection-mitigation
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-grow-route-leak-detection-mitigation
Consensus boilerplate Yes
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Problem definition for route leaks and enumeration of types of route leaks are provided in RFC 7908. This document describes a solution for detection and mitigation route leaks which is based on conveying route-leak protection (RLP) information in a Border Gateway Protocol (BGP) community. The RLP information is carried in a new well-known transitive BGP community, called the RLP community. The RLP community helps with detection and mitigation of route leaks at ASes downstream from the leaking AS (in the path of the BGP update). This is an inter-AS (multi-hop) solution mechanism. This solution complements the intra-AS (local AS) route-leak avoidance solution that is described in ietf-idr-bgp-open-policy draft.


Kotikalapudi Sriram
Alexander Azimov

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)