BGP Route Leak Protection Community
draft-heitz-idr-route-leak-community-00

Document Type Active Internet-Draft (individual)
Last updated 2017-10-01
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
IDR                                                             J. Heitz
Internet-Draft                                                     Cisco
Intended status: Standards Track                             J. Snijders
Expires: April 4, 2018                                               NTT
                                                         October 1, 2017

                  BGP Route Leak Protection Community
                draft-heitz-idr-route-leak-community-00

Abstract

   In general, BGP autonomous system (AS) relationships are either
   customer-transit or peer-peer.  If an AS sends a route received from
   a transit or a peer to another transit or to another peer, it is
   considered a route leak.  AS relationships are sometimes different
   for different routes or in different regions.  A method of detecting
   route leaks is proposed that does not require participation by the
   leaking AS or by IXPs.  Only the ASes that perform leak detection
   need to adopt the proposal.  ASes that request leak protection need
   to send a community to make the request.  The proposal works even if
   the leaking AS or other ASes modify or discard path attributes in the
   route or create more specific routes.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

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 April 4, 2018.

Heitz & Snijders          Expires April 4, 2018                 [Page 1]
Internet-Draft             BGP Leak Protection              October 2017

Copyright Notice

   Copyright (c) 2017 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
   (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.  Concept . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  More Specific Routes  . . . . . . . . . . . . . . . . . . . .   4
   4.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Encoding  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Limited Alternative using Regular Communities . . . . . .   6
   6.  Procedures  . . . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Deployment Considerations . . . . . . . . . . . . . . . . . .   8
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   11. Discussion Topics . . . . . . . . . . . . . . . . . . . . . .   9
     11.1.  Use of the Regular Community . . . . . . . . . . . . . .   9
     11.2.  Limited Reach  . . . . . . . . . . . . . . . . . . . . .   9
     11.3.  Well Known Large Communities . . . . . . . . . . . . . .  10
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     12.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   In general, BGP autonomous system (AS) relationships are either
   customer-transit or peer-peer.  A route received from a transit or a
   peer can only be sent to a customer.  If an AS sends such a route to
   a transit or to a peer, then it is considered a route leak.  An AS
Show full document text