Methods for Detection and Mitigation of BGP Route Leaks
draft-ietf-grow-route-leak-detection-mitigation-00
IDR and SIDR K. Sriram, Ed.
Internet-Draft USA NIST
Intended status: Standards Track A. Azimov, Ed.
Expires: October 21, 2019 Yandex
April 19, 2019
Methods for Detection and Mitigation of BGP Route Leaks
draft-ietf-grow-route-leak-detection-mitigation-00
Abstract
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.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 21, 2019.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
Sriram & Azimov Expires October 21, 2019 [Page 1]
Internet-Draft Route Leak Detection and Mitigation April 2019
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Mechanisms for Detection and Mitigation of Route Leaks . . . 3
2.1. Ascertaining Peering Relationship . . . . . . . . . . . . 3
2.2. Route-Leak Protection (RLP) Semantics . . . . . . . . . . 4
2.2.1. Format of the RLP Community . . . . . . . . . . . . . 5
2.3. Route Leak Detection Rules and the Ingress Router
(Receiver) Actions . . . . . . . . . . . . . . . . . . . 6
2.4. Route Selection Policy . . . . . . . . . . . . . . . . . 6
2.5. Egress Router (Sender) Actions . . . . . . . . . . . . . 7
3. Pseudo Code . . . . . . . . . . . . . . . . . . . . . . . . . 7
4. Security Considerations . . . . . . . . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.1. Normative References . . . . . . . . . . . . . . . . . . 9
6.2. Informative References . . . . . . . . . . . . . . . . . 9
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 10
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction
RFC 7908 [RFC7908] provides a definition of the route leak problem,
and enumerates several types of route leaks. For this document, the
definition that is applied is that a route leak occurs when a route
received from a transit provider or a lateral peer is forwarded
(against commonly used policy) to another transit provider or a
lateral peer. The commonly used policy is that a route received from
a transit provider or a lateral peer may be forwarded "down only" to
customers.
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
Show full document text