Re: [Idr] BGP autoconfiguration - draft-minto-idr-bgp-autodiscovery

Robert Raszuk <robert@raszuk.net> Sun, 20 March 2022 23:20 UTC

Return-Path: <robert@raszuk.net>
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 686853A1582 for <idr@ietfa.amsl.com>; Sun, 20 Mar 2022 16:20:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 zjoKbmGnRXf9 for <idr@ietfa.amsl.com>; Sun, 20 Mar 2022 16:20:01 -0700 (PDT)
Received: from mail-vs1-xe36.google.com (mail-vs1-xe36.google.com [IPv6:2607:f8b0:4864:20::e36]) (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 4D1C03A1581 for <idr@ietf.org>; Sun, 20 Mar 2022 16:20:01 -0700 (PDT)
Received: by mail-vs1-xe36.google.com with SMTP id i186so9619520vsc.9 for <idr@ietf.org>; Sun, 20 Mar 2022 16:20:01 -0700 (PDT)
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 :cc; bh=kH0WFlN8hPjPbdO8NXbwdzR0iTdBe8bDTX0/Vhq2Kw4=; b=QlVs86sWHyytPvhJB5ttvbFvPPFJovbRDUhM8nc6bYbWTZkxvCJ38HtSbfgP97q1la uGWGAhzcndJ84mPq0/nzgTstIISAP09dslAL1+BrxilJkk4PG/TWeZ1aduNvv7IjaHA8 IyQDz/U2bIVCvU0607ESaEReB2A7wFPRAdUY20Cva8n8iC92fc+JX6meQi2fc0uqPIiD yc/U2eEZGWnLxSHO7WiO0PP5yOhNWVBaFJtx5AJ2Ul1ngSOCMavBFEqOk+cMxK1iuMlz tNP1lgvj99S1J1KwgDWbGhmwafUituwJg+Y+kNk1ebzIuV+nsdPy3ZAV8nYHFc2BD4AY L6EA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kH0WFlN8hPjPbdO8NXbwdzR0iTdBe8bDTX0/Vhq2Kw4=; b=kJ7H1hZsbi/JOgfugF2iNDh/t6awOs1CH3BnS+GGYUOktjVvckzGSaQo0v5jkoKdzs JynhKjpuNMnP7VH073LB1sTMcfcoSeFBxzj9ACtUP1YdJDPpSgaySpEmoUfkOBlFJX6y sJfPnQImBRc3xJ6jLBnjMvnnmvbi5RWrVt1divgL9dvHp6eHtGXLCdbWz/qDEmcR0dRN iFByZXQrfnpp/Zicqtca4ug17yGvOvHr+LDxWNcDsvrY/eRO2C00n15UKY9lCQpBDKGh StEn+YB9DAL6d7ogz2DaM7W/SqyD5W3ykxZuAtljsp49MNqbPEHbNvJPHlv3wkNK+AdT BiGw==
X-Gm-Message-State: AOAM531443NOuf9CbGWXq0qtIJUOfvBkZOesiMNyyAcl0+SjvSdip90j bOdvnoFd6/Wn31aORjj0cIVyMLpnPZ+qmvh1/1G6u2g7DNI=
X-Google-Smtp-Source: ABdhPJysv6Vu7OpPzGObyzwMbx07DlJQDYNmNQPMo6NMfAulxYJyz7i81C3jyWhQdVpzcE/TVlRsbaimOWzIhu5Zg5Y=
X-Received: by 2002:a05:6102:b01:b0:324:f5d8:a7d8 with SMTP id b1-20020a0561020b0100b00324f5d8a7d8mr2004301vst.27.1647818399913; Sun, 20 Mar 2022 16:19:59 -0700 (PDT)
MIME-Version: 1.0
References: <20220308062429.GF17510@pfrc.org> <BYAPR05MB4359013ABE17D0296F6CEB86A5139@BYAPR05MB4359.namprd05.prod.outlook.com> <00b501d83b8b$cd5ff320$681fd960$@ndzh.com> <20220319192926.GC4905@pfrc.org> <018201d83c55$80173180$80459480$@ndzh.com> <20220320173421.GP4905@pfrc.org> <002f01d83c89$106cc6e0$314654a0$@ndzh.com> <20220320183916.GQ4905@pfrc.org> <002201d83cae$74bbcb30$5e336190$@ndzh.com>
In-Reply-To: <002201d83cae$74bbcb30$5e336190$@ndzh.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 21 Mar 2022 00:20:38 +0100
Message-ID: <CAOj+MMEbfzChAqfK4Kc7WoFzM7sQ_zPmhyn-gurGiAwzH6ab-w@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Cc: Jeffrey Haas <jhaas@pfrc.org>, "idr@ietf. org" <idr@ietf.org>, draft-minto-idr-bgp-autodiscovery@ietf.org, Minto Jeyananth <minto=40juniper.net@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="00000000000061abfb05daae9e0d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/3sV6ctxvL6NOr-Zo-nc1DV8fNjc>
Subject: Re: [Idr] BGP autoconfiguration - draft-minto-idr-bgp-autodiscovery
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: Sun, 20 Mar 2022 23:20:07 -0000

Sue,

What encapsulation happens to be used by BGP or for that matter any other
protocol is (and should be) protocol agnostic.

I hope we are not trying here to bind a TCP session to encapsulation X or Y
irrespective of what routing (and given encap orchestration - LDP FEC
binding or SR policy or something else) tells you to do. That would quickly
get very very inconsistent and prone to many failures.

Btw there is no such a thing as "MPLS interface". All MPLS interfaces I
have seen do support IP routing/switching too. And honestly it may be much
better if BGP keeps its transport limited to IPv4 and IPv6 native.

Thx,
Robert





On Mon, Mar 21, 2022 at 12:02 AM Susan Hares <shares@ndzh.com> wrote:

> Jeff:
>
> I'm really trying to answer your question - so if I do not understand your
> question.  I'll try again.
>
> The BGP transport sessions can have policy that requires the BGP hello to
> be
> exchanged across a L3 connection running on a particular MPLS interface.
> This policy ties down the TCP to a specific L3 connection on a specific
> L2.5
> connection.   This example, show the benefit for some overlay/underlay
> deployments.
>
> How does it impact the BGP FSM?   You will not get an TCP connection up due
> to machine policy (it is reject except for the l3 connection attached to
> specific MPLS interface).
>
> I really hope I've understood your question.
>
> Sue
>
>
> -----Original Message-----
> From: Jeffrey Haas [mailto:jhaas@pfrc.org]
> Sent: Sunday, March 20, 2022 2:39 PM
> To: Susan Hares
> Cc: 'Minto Jeyananth'; idr@ietf.org;
> draft-minto-idr-bgp-autodiscovery@ietf.org
> Subject: Re: [Idr] BGP autoconfiguration -
> draft-minto-idr-bgp-autodiscovery
>
> Sue,
>
> I'm asking a very specific question.  Let me repeat:
>
> On Sun, Mar 20, 2022 at 02:33:56PM -0400, Susan Hares wrote:
> > You asked  L3DN is useful where besides the DC.
>
> No, I asked:
> > > It is still unclear what the "encapsulation" fields are used for with
> > > respect to BGP discovery.
>
> > I am looking for the same level of answer from the draft-minto-*.   Are
> they
> > planning to use this for WAN BGP auto-configuration.
>
> I'm not speaking for them.  Minto or Shiva can commment on their draft.
>
> > On the encapsulation,  as Randy has said AFI/SAFI.  Consider a data
> center
> > with multiple overlays (L2, mpls, L3) and AFI/SAFIs.  Suppose, you want
> to
> > use an MPLS interface for an L3 connections.  You might want to select a
> > specific set of labels for the underlay for L3DN.
>
> That's still not clear.
>
> How is this used to setup BGP's transport session during discovery?
> I.e. how does this impact BGP's TCP SYN and the rest of the session?
>
> -- Jeff
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>