Re: [Bgp-autoconf] Fwd: BGP Auto Discovery and BGP Auto Session Setup

Jeff Tantsura <jefftant.ietf@gmail.com> Thu, 30 January 2020 11:09 UTC

Return-Path: <jefftant.ietf@gmail.com>
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 74382120125 for <bgp-autoconf@ietfa.amsl.com>; Thu, 30 Jan 2020 03:09:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 67m9pFo3sUmh for <bgp-autoconf@ietfa.amsl.com>; Thu, 30 Jan 2020 03:09:09 -0800 (PST)
Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (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 6101F120104 for <bgp-autoconf@ietf.org>; Thu, 30 Jan 2020 03:09:09 -0800 (PST)
Received: by mail-wm1-x329.google.com with SMTP id c84so3721636wme.4 for <bgp-autoconf@ietf.org>; Thu, 30 Jan 2020 03:09:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=NwFJ6z6bYze/D5LBjfXNxDSZLxxRTA00sjX8imDNq1M=; b=jZ/z3cd14nLjMIr1JKYtffXcBeLVpHac8nci3nLTiMnxYQoa61xAiWlMcrpSbYIPr8 1TceMKWKMoGLnBcEhlUSEn3nJ4DVQT3+8IPCatsh6Oie/Mult07y7ZskWIC22T/CqcTs qh0o2ZYjc+kC+Zih4d/Qfr7/pYHhgKSkURs4itrfpoEQNM33aS+OsTBXTAE39A8fIiix t3PtwpY8oEEPCSaj4YbGqpOC+ictUr7PxWoxWKrPJ7JDMCMQqMgNBvxwEZH5dX/7BwQt Brnp2Ps+ow2sBR7uD2Opj2rA0YlN9F97BbqfUsKBecpl1ddJp/ovab+L44weyo+ZrIGL +d1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=NwFJ6z6bYze/D5LBjfXNxDSZLxxRTA00sjX8imDNq1M=; b=ga2xvC50Ss/uapxntguLoR3wkCdluTVXQhfpWC2/J9EYpGM8MeuAG19rPliJbyuH8q n5lCkXBvoamEtYvvJEMgvLSMSYMNI0IenM1JHlodxjQBBXYl+YoKDwzYaTy6GgULodDu bj+j43zo+oM5iP2Vrw5DtMStPs+BvX8sWzaLhQNytS01UkmK/OOhU/KywqwD40R4gGBf F8B1cjlhBrJnDdEq1/dum/bZMg7DrFBo9QLcTKtdANfjJiE1lm7DJDd4IZPa/0vg6d8s NcR2yXbXAvt0BzQ75t348lphKIxIhrcb8UzFg4ZEnwvmzBlSLf4Ms6jqIKz7oc+majwg qUCw==
X-Gm-Message-State: APjAAAU+0kXcNa24W8A17tiybIUSPv1W95pOE1TShA/uoPuvSNVZ5gSZ 6Tpmam6jvvPV/sI3YpuW0b/8QM1+
X-Google-Smtp-Source: APXvYqyfF2Am6EHKQ2uJcIBoxTYB83FupsmPtSPUxDZjiTezPKDRlQpYlzpwGNrW2k3o3Aht4Be+1w==
X-Received: by 2002:a7b:c389:: with SMTP id s9mr4760779wmj.7.1580382547695; Thu, 30 Jan 2020 03:09:07 -0800 (PST)
Received: from ?IPv6:2a05:f8c0:2:83ff:34cf:a40d:98a9:845c? ([2a05:f8c0:2:83ff:34cf:a40d:98a9:845c]) by smtp.gmail.com with ESMTPSA id t13sm5985894wrw.19.2020.01.30.03.09.06 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 30 Jan 2020 03:09:06 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-82ACB554-417D-4F4E-A9BC-F9A92C93AE1F"
Content-Transfer-Encoding: 7bit
From: Jeff Tantsura <jefftant.ietf@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Thu, 30 Jan 2020 12:09:06 +0100
Message-Id: <2EC7DA29-2FFC-4A9C-AF5A-6EE7F07D21D0@gmail.com>
References: <CAOj+MMFDJEyC=vB57BEsNtgmKcKmJqQ3ue2oJNQPySqbPt3etw@mail.gmail.com>
Cc: bgp-autoconf@ietf.org
In-Reply-To: <CAOj+MMFDJEyC=vB57BEsNtgmKcKmJqQ3ue2oJNQPySqbPt3etw@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
X-Mailer: iPhone Mail (17C54)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/BXsGxp9ooBoHAGOLY5aSEY0ErRQ>
Subject: Re: [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: Thu, 30 Jan 2020 11:09:11 -0000

Hi Robert,

To my feeling we have already agreed to treat them separately?

Regards,
Jeff

> On Jan 29, 2020, at 20:18, Robert Raszuk <robert@raszuk.net> wrote:
> 
> 
> 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 mailing list
> Bgp-autoconf@ietf.org
> https://www.ietf.org/mailman/listinfo/bgp-autoconf