[Bgp-autoconf] Fwd: BGP Auto Discovery and BGP Auto Session Setup
Robert Raszuk <robert@raszuk.net> Wed, 29 January 2020 19:18 UTC
Return-Path: <robert@raszuk.net>
X-Original-To: bgp-autoconf@ietfa.amsl.com
Delivered-To: bgp-autoconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30E141208CF for <bgp-autoconf@ietfa.amsl.com>; Wed, 29 Jan 2020 11:18:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=raszuk.net
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 Eu-B6GXGhU6K for <bgp-autoconf@ietfa.amsl.com>; Wed, 29 Jan 2020 11:18:26 -0800 (PST)
Received: from mail-oi1-x233.google.com (mail-oi1-x233.google.com [IPv6:2607:f8b0:4864:20::233]) (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 A9A8A120916 for <bgp-autoconf@ietf.org>; Wed, 29 Jan 2020 11:18:23 -0800 (PST)
Received: by mail-oi1-x233.google.com with SMTP id a142so864480oii.7 for <bgp-autoconf@ietf.org>; Wed, 29 Jan 2020 11:18:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=FTcha+Rj3XYWpAMuthLNtKoVFUKbqwIaJnnnDUdwGzM=; b=X4kJCMFu3NSHt0B9uNWOfNLWkCTjwjjuenIwRpesAGuDqzvtViNyymVTzj6ySmV1QD AAr7FWvuhnnbgyIczvaIac/I82yDzs53M39aAa5gacrz7ZlJnnqst948b5KTZEaKu9nQ +Ze2ah+C8F+TsNenVcH/9DZBEQ4Y4t/1ykBMbkBOuc+4EUU4FH8zS47f6uYsuuMchp9w 4bFgl9cRIatXjUnDh8jdCIG2u/mmOYIciQHSNPyis5Ty1MKpcfHS53YmnTVrjuhbUtzt HI9sF8PBYDkGoaNe4+/McgKgBfkiv9RN3I/+NIw3OeRbImEGKmcepvBxEQ8TfKK8EHzG n+ww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=FTcha+Rj3XYWpAMuthLNtKoVFUKbqwIaJnnnDUdwGzM=; b=dUXmVOHve8i/Qi7ohH60Kliu3lvvO0Fz3YU87KAByWTp1H6TZuaKltvQxxebaaEUVE zamB5zkvHm5mgj3UZJa7Xo++0HeiEmKnPgd0or+T2zDJq87bCxQzhgQtzDlP4i2IF0vc dnj7/qPwdNat3l3F9kECAmxUn/pT/yRAnmvWNGymQ3epAtJOJ2YXiS5HBhRuq6bRFk+v m14eF9m5qQHkCPlIBHTNYE+nYIYq2GjvZPqAJypMr5ke9ZdfFiaab04b8dlnSxztvY6X GrWHpmL0X2smTii3Lka/lUpZCUHpebNHMmCa4bu1ULLez/Zu+4Ap36p5f9c4W5ly5s5C PuFQ==
X-Gm-Message-State: APjAAAUdr5f32gC/QPf5ZBpmFIAv64lJzApdbWCuFWKk6gBpbA0qVEVO 5TpHltYNmrceGjp2sgmzMaVy2bXFEYKt9MExb1iCg+09
X-Google-Smtp-Source: APXvYqyodpFU/WRvE2QL8NX81Ynx4ENiBh2dlzJcDUptmZS81n/gXeqmfQ3MOTVj8wWTlGlmLxHCyR1JyLNA+jIAJzc=
X-Received: by 2002:a05:6808:611:: with SMTP id y17mr314709oih.146.1580325502607; Wed, 29 Jan 2020 11:18:22 -0800 (PST)
MIME-Version: 1.0
References: <CAOj+MMEJ8qWUrPacdw10nTqEL4Vo1AjyRGtyENVZS9WVjF+LBw@mail.gmail.com>
In-Reply-To: <CAOj+MMEJ8qWUrPacdw10nTqEL4Vo1AjyRGtyENVZS9WVjF+LBw@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Wed, 29 Jan 2020 20:18:14 +0100
Message-ID: <CAOj+MMFDJEyC=vB57BEsNtgmKcKmJqQ3ue2oJNQPySqbPt3etw@mail.gmail.com>
To: bgp-autoconf@ietf.org
Content-Type: multipart/alternative; boundary="00000000000036791b059d4c3480"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/vaNZAWAWbw5lCICqfLcwNuzuE6A>
Subject: [Bgp-autoconf] Fwd: BGP Auto Discovery and BGP Auto Session Setup
X-BeenThere: bgp-autoconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP autoconfiguration design team discussion list <bgp-autoconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bgp-autoconf>, <mailto:bgp-autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bgp-autoconf/>
List-Post: <mailto:bgp-autoconf@ietf.org>
List-Help: <mailto:bgp-autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bgp-autoconf>, <mailto:bgp-autoconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2020 19:18:29 -0000
Hello, Let me see if the list works :) Resending for the record two proposals in the BGP autodiscovery space. I understand that first we perhaps need to agree on requirements. Some of them are listed in the below documents. Perhaps few of them are missing. IMO we should also agree first on decoupling BGP in WAN and IX automated session setup from Data Centers. While on the surface they may look the same "Oh I just want my BGP to come up" if you look under the hood and say compare iBGP vs eBGP via L2 switch vs eBGP via p2p link they are really different animals in the same garden. Thx, R. ---------- Forwarded message --------- From: Robert Raszuk <robert@raszuk.net> Date: Wed, Dec 11, 2019 at 8:24 PM Subject: BGP Auto Discovery and BGP Auto Session Setup To: idr@ietf. org <idr@ietf.org> Cc: grow@ietf.org grow@ietf.org <grow@ietf.org> Dear WG, We have seen formation of BGP Autodiscovery WG followed by total silence. Well maybe group is live just not everyone got onto its private list :) Regardless of this I refreshed and resubmitted two proposals in this very space. 1. BGP Auto Discovery https://tools.ietf.org/html/draft-raszuk-idr-bgp-auto-discovery-06 and 2. BGP Automated Session Setup https://tools.ietf.org/html/draft-raszuk-idr-bgp-auto-session-setup-01 *Ad 1:* First document is focused on WAN and IX scenario where establishing full mesh of IBGP or selected eBGP peering can automate the operational management tasks or if run in informational mode could validate NMS session setup correctness. Original proposal was presented many years ago in Vienna and at that point suggested extension to IGPs to flood discovery information for IBGP auto mesh. Later based on the input and discussions with Pedro the proposal got simplified to use classic Route Reflector as bootstrap node (info broker). Last input from Jon and Warren added the ability to also automate setup of eBGP sessions in selected scenarios. Since then the document was shelved for some time waiting for IDR WG turn to deal with discovery topic. So here we are. *Ad 2: * The second document first published in July 2018 provides a very trivial to implement mechanism (without even changing BGP state machine) to automatically establish common LAN or p2p interfaces BGP sessions. Typical use case would be Clos DC fabrics, customer PE-CE LANs, TORs to Compute Nodes etc ... Comments, questions, feedback on both proposals all very welcome. Kind regards, Robert.
- [Bgp-autoconf] Fwd: BGP Auto Discovery and BGP Au… Robert Raszuk
- Re: [Bgp-autoconf] Fwd: BGP Auto Discovery and BG… Randy Bush
- Re: [Bgp-autoconf] Fwd: BGP Auto Discovery and BG… Robert Raszuk
- Re: [Bgp-autoconf] Fwd: BGP Auto Discovery and BG… Jeff Tantsura
- Re: [Bgp-autoconf] Fwd: BGP Auto Discovery and BG… Robert Raszuk
- Re: [Bgp-autoconf] Fwd: BGP Auto Discovery and BG… Jeff Tantsura
- Re: [Bgp-autoconf] Fwd: BGP Auto Discovery and BG… Robert Raszuk
- Re: [Bgp-autoconf] Fwd: BGP Auto Discovery and BG… Randy Bush
- Re: [Bgp-autoconf] Fwd: BGP Auto Discovery and BG… Dongjie (Jimmy)
- Re: [Bgp-autoconf] Fwd: BGP Auto Discovery and BG… Dongjie (Jimmy)
- Re: [Bgp-autoconf] Fwd: BGP Auto Discovery and BG… Jeff Tantsura
- Re: [Bgp-autoconf] Fwd: BGP Auto Discovery and BG… Acee Lindem (acee)
- Re: [Bgp-autoconf] Fwd: BGP Auto Discovery and BG… Robert Raszuk
- Re: [Bgp-autoconf] BGP Auto Discovery and BGP Aut… Mankamana Mishra (mankamis)