[Idr] I-D Action: draft-ietf-idr-bgp-open-policy-08.txt
internet-drafts@ietf.org Mon, 09 March 2020 21:39 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7316B3A0828; Mon, 9 Mar 2020 14:39:03 -0700 (PDT)
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
X-Test-IDTracker: no
X-IETF-IDTracker: 6.120.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: idr@ietf.org
Message-ID: <158378994340.5631.608455050681429437@ietfa.amsl.com>
Date: Mon, 09 Mar 2020 14:39:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/L09xdZV4BliLa56R1QCVH_xYL_4>
Subject: [Idr] I-D Action: draft-ietf-idr-bgp-open-policy-08.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2020 21:39:16 -0000
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 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-08.txt Pages : 10 Date : 2020-03-09 Abstract: Route leaks are the propagation of BGP prefixes which violate assumptions of BGP topology relationships; e.g. passing a route learned from one peer to another peer or to a transit provider, passing a route learned from one transit provider to another transit provider or to a peer. Today, approaches to leak prevention rely on marking routes by operator configuration, with no check that the configuration corresponds to that of the BGP neighbor, or enforcement that the two BGP speakers agree on the relationship. This document enhances BGP OPEN to establish agreement of the (peer, customer, provider, Route Server, Route Server client) relationship of two neighboring BGP speakers to enforce appropriate configuration on both sides. Propagated routes are then marked with an OTC attribute 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 are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-idr-bgp-open-policy-08 https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-open-policy-08 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-bgp-open-policy-08 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
- [Idr] I-D Action: draft-ietf-idr-bgp-open-policy-… internet-drafts