I-D Action: draft-ietf-idr-bgp-open-policy-24.txt

internet-drafts@ietf.org Fri, 01 April 2022 14:56 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: idr@ietf.org
Subject: I-D Action: draft-ietf-idr-bgp-open-policy-24.txt
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: idr@ietf.org
Message-ID: <164882500537.8391.15552563205182403567@ietfa.amsl.com>
Date: Fri, 01 Apr 2022 07:56:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/F2sNGqTYaI9zWnT-VPJxClhbihU>

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing WG of the IETF.

        Title           : Route Leak Prevention and Detection using Roles in UPDATE and OPEN Messages
        Authors         : Alexander Azimov
                          Eugene Bogomazov
                          Randy Bush
                          Keyur Patel
                          Kotikalapudi Sriram
	Filename        : draft-ietf-idr-bgp-open-policy-24.txt
	Pages           : 15
	Date            : 2022-04-01

Abstract:
   Route leaks are the propagation of BGP prefixes that violate
   assumptions of BGP topology relationships, e.g., announcing a route
   learned from one transit provider to another transit provider or a
   lateral (i.e., non-transit) peer or announcing a route learned from
   one lateral peer to another lateral peer or a transit provider.
   These are usually the result of misconfigured or absent BGP route
   filtering or lack of coordination between autonomous systems (ASes).
   Existing approaches to leak prevention rely on marking routes by
   operator configuration, with no check that the configuration
   corresponds to that of the eBGP neighbor, or enforcement that the two
   eBGP speakers agree on the peering relationship.  This document
   enhances the BGP OPEN message to establish an agreement of the
   peering relationship on each eBGP session between autonomous systems
   in order to enforce appropriate configuration on both sides.
   Propagated routes are then marked according to the agreed
   relationship, allowing both prevention and detection of route leaks.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-open-policy/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-open-policy-24

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-bgp-open-policy-24


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts

I-D Action: draft-ietf-idr-bgp-open-policy-24.txt internet-drafts