Re: [Idr] I-D Action: draft-ietf-idr-bgp-open-policy-15.txt

Alejandro Acosta <alejandroacostaalamo@gmail.com> Tue, 19 January 2021 15:51 UTC

Return-Path: <alejandroacostaalamo@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0651D3A15D1 for <idr@ietfa.amsl.com>; Tue, 19 Jan 2021 07:51:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.36
X-Spam-Level:
X-Spam-Status: No, score=-2.36 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4eUGszoTTbL4 for <idr@ietfa.amsl.com>; Tue, 19 Jan 2021 07:51:51 -0800 (PST)
Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 650FA3A1338 for <idr@ietf.org>; Tue, 19 Jan 2021 07:51:51 -0800 (PST)
Received: by mail-qk1-x72b.google.com with SMTP id z11so22241505qkj.7 for <idr@ietf.org>; Tue, 19 Jan 2021 07:51:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=Ee9qnNdOJ/hiDL0sJ54Np8UZfGr/eaCaNIPGnHDJG98=; b=j2iuCpwRNqMkFHenawr3U3DqGCOiSPBLxQx7VX1a88iqp3eprhB7+omMPCbZ+gAmbo 4uGr1WfYvRSDtJIt6z1Iz5fpi4tkR6QQcrISXw3fnyiH3t/Tdq4KA8tyQ+YVxljNFtui PvEDIpGNMwHyr3DqS8fA3S04u5IcO8fmU9jzGt+aZsDtK/Ln1AD8i2D7su5Qk2dm/OFi ghodJB3SdhB5JKvge+r+2MGXknbSDV3cI5G3apPtlfqJPih3vfe94dk4tYT0u/XxSI+v GuErNykxJDVM1YpXpFqZoQZYHQYs2MezTQuE5zXki3O5LpoXHtDfjn3GDqNi/y8UdMzM 01zQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=Ee9qnNdOJ/hiDL0sJ54Np8UZfGr/eaCaNIPGnHDJG98=; b=a45pdZoq33ydPK0wVGALuzjKR760RtxE2qErwLKYftYaBooQy+9krkB7sWb3RDQxF4 Bkb7wl2o7fUEv3GOYDBHB1e9qsAMtScdOPUFKfrbJesvdS2WxOSzmEIf4XXAjHGDkC9f Letvpgr5em+W0+vj3CokITgy7I6sXoP8ukzLwDxfZrgzMB1+l5qFBcQki73JXLt76sr6 WNxpb05RAqMU+vWtGx0axgteHa9O+OIebjXhsFQryZg/ZgN7F+hEhkEdLA+WsnnE/tqA kkivGWdjnuJXn6+oRQqQskLUONZ5g1nc8vovITF9A5s9tgju7Dv1YAAWQV3ubnSm+lym 4LZA==
X-Gm-Message-State: AOAM530cHmgiOHnd0UOXdlQTX8X+GUOiEQlqWreHtaMmWXVuw7zZaXCV umXwLmeHIK6XWTQBjUx9s2/6vPot6rwuCrfv
X-Google-Smtp-Source: ABdhPJx9V6VZuxvZmv3b2bwUDwBXctxS3/zKmIEyHTMBcKndLlZlIeVowxhSBGU14Mu/lw5ZRWzXDw==
X-Received: by 2002:a05:620a:6c8:: with SMTP id 8mr4919775qky.176.1611071510120; Tue, 19 Jan 2021 07:51:50 -0800 (PST)
Received: from Windows10AnyBody.local ([2001:470:5:516:cdbc:868e:d056:e643]) by smtp.gmail.com with ESMTPSA id x28sm12255751qtv.8.2021.01.19.07.51.47 for <idr@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 19 Jan 2021 07:51:49 -0800 (PST)
To: idr@ietf.org
References: <161081288638.19019.5456683696650869664@ietfa.amsl.com>
From: Alejandro Acosta <alejandroacostaalamo@gmail.com>
Message-ID: <1fcc652f-bf7c-9389-33d9-ad73b6519827@gmail.com>
Date: Tue, 19 Jan 2021 11:51:42 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <161081288638.19019.5456683696650869664@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/TZcUyPH7U3fQEePO3peeHGydrI4>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-bgp-open-policy-15.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Tue, 19 Jan 2021 15:51:53 -0000

Hello,

   I know it's late and this draft was already asked for publication 
(congratulations). I think this is a terrific job and I can  imagine 
different scenarios.

   I wonder if there is already some working code somewhere?, probably 
some beta code for quagga, frr, etc?.


Thanks,


Alejandro,


On 16/1/21 12:01 PM, internet-drafts@ietf.org wrote:
> 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-15.txt
> 	Pages           : 11
> 	Date            : 2021-01-16
>
> Abstract:
>     Route leaks are the propagation of BGP prefixes which violate
>     assumptions of BGP topology relationships; e.g. passing a route
>     learned from one lateral peer to another lateral peer or a transit
>     provider, passing a route learned from one transit provider to
>     another transit provider or a lateral peer.  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
>     relationship.  This document enhances BGP OPEN to establish agreement
>     of the (peer, customer, provider, Route Server, Route Server client)
>     relationship of two neighboring eBGP speakers to enforce appropriate
>     configuration on both sides.  Propagated routes are then marked with
>     an Only to Customer (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-15
> https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-open-policy-15
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-bgp-open-policy-15
>
>
> 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 mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr