Methods for Detection and Mitigation of BGP Route Leaks
draft-ietf-idr-route-leak-detection-mitigation-09

Document Type Active Internet-Draft (idr WG)
Last updated 2018-07-02
Replaces draft-sriram-idr-route-leak-detection-mitigation
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)
IDR and SIDR                                              K. Sriram, Ed.
Internet-Draft                                                  USA NIST
Intended status: Standards Track                          A. Azimov, Ed.
Expires: January 3, 2019                                     Qrator Labs
                                                            July 2, 2018

        Methods for Detection and Mitigation of BGP Route Leaks
           draft-ietf-idr-route-leak-detection-mitigation-09

Abstract

   Problem definition for route leaks and enumeration of types of route
   leaks are provided in RFC 7908.  This document specifies BGP
   enhancements that significantly extend its route-leak detection and
   mitigation capabilities.  The solution involves each participating AS
   setting a route-leak protection (RLP) field in BGP updates.  The RLP
   fields are carried in a new optional transitive attribute, called BGP
   RLP Attribute.  The RLP Attribute helps with detection and mitigation
   of route leaks at ASes downstream from the leaking AS (in the path of
   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 January 3, 2019.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Sriram & Azimov          Expires January 3, 2019                [Page 1]
Internet-Draft     Route Leak Detection and Mitigation         July 2018

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (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.  Route-Leak Types that the Solution Must Address . . . . . . .   3
   3.  Mechanisms for Detection and Mitigation of Route Leaks  . . .   5
     3.1.  Ascertaining Peering Relationship . . . . . . . . . . . .   5
     3.2.  Route-Leak Protection (RLP) Field Encoding by Sending
           Router  . . . . . . . . . . . . . . . . . . . . . . . . .   6
       3.2.1.  BGP RLP Attribute . . . . . . . . . . . . . . . . . .   8
       3.2.2.  Carrying RLP Field Values in the BGPsec Flags . . . .   9
     3.3.  Recommended Actions at a Receiving Router for Detection
           and Mitigation of Route Leaks . . . . . . . . . . . . . .  10
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  12
   Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   RFC 7908 [RFC7908] provides a definition of the route leak problem,
   and enumerates several types of route leaks.  This document first
   examines which of those route-leak types are detected and mitigated
   by the existing Origin Validation (OV) [RFC6811] method.  OV
   [RFC6811] and BGPsec path validation [RFC8205] together offer
   mechanisms to protect against re-originations and hijacks of IP
   prefixes as well as man-in-the-middle (MITM) AS path modifications.
   Route leaks [RFC7908] are another type of vulnerability in the global
   BGP routing system against which OV offers very limited protection.
   BGPsec path validation provides cryptographic protection for some
   aspects of BGP update messages, but in its current form BGPsec does
   not offer any protection against route leaks.
Show full document text