IETF Logo Mail Archive

Re: [Bgp-autoconf] bgp auto configuration -01 update after interim discussion

Robert Raszuk <robert@raszuk.net> Wed, 23 June 2021 05:47 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 C1EA63A2A9E for <bgp-autoconf@ietfa.amsl.com>; Tue, 22 Jun 2021 22:47:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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 DTuBzJ4-6ePr for <bgp-autoconf@ietfa.amsl.com>; Tue, 22 Jun 2021 22:47:17 -0700 (PDT)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 82AF93A2A9F for <bgp-autoconf@ietf.org>; Tue, 22 Jun 2021 22:47:17 -0700 (PDT)
Received: by mail-lf1-x129.google.com with SMTP id r5so2095239lfr.5 for <bgp-autoconf@ietf.org>; Tue, 22 Jun 2021 22:47:17 -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=kKLLvXupOg7EOusWCJ7luYU9xhrxKLVifvNz6YX8Xk0=; b=HoNqT+MJHDZnm6x3vEzBtruYOCh+X5oMVc2LhGie3llLe600v7hxRZqx6PYit5b9iL nXxZN3qwct6AeVXHXFNxKsUqCvy5qPc6SogEVHq++h9X1rzEhUy/QuGHfI6HEt80lIQO Jawrdn32RGOKBzHEgfCbNPKA7HpC4x5sxG6gU8QsLfdqLETbLp3NNjtERQzEVLaHyQKe Cr3Z8mJK3o2MTgZeR71DdpgTW4xO6QIxXTxjy7E49SsKVjiirZXCRN9LXozsOdA87OYI BmHlnRmqguWjX6o39NhFl87cHCWSAsWZbqv65qSoaF89POCBje4A5dBc9MMruueif0e4 ZMbw==
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:cc; bh=kKLLvXupOg7EOusWCJ7luYU9xhrxKLVifvNz6YX8Xk0=; b=Ygko6/8pqeY45kTdCHuOGjc62FCx8fPK2Je46TDIokYNMelugPaDdRIA1n9bA6TjnI bXf+BwrBaXLbPTp4sxArVcfsjwRWzrInteFGcDljQO0ivPHvLMz8c6QBSiOZqfDweYaD mhRiwYvVX4SlVRanCxRfrKkO4iDaIW7+nasri+tylGrXLAEs9HF0lvr3jM8Nj0NiXNAL butWS9hbCskntEuEwBViGpBB86w4e2TgR/1sN4OLIrIHbm0WObaH+Gz/r7xSQQNeFH0J AaQVEBhCP/k4SIbAZJvrP9WuBlRWqEsG3cxmJsDKcdcw24xmOApDX0RzJvQYzZGJxDTj AYfg==
X-Gm-Message-State: AOAM532EEMlw7oYz3VwiDMJ3Syu6gTonwKTPexrpUCLJgU3eABn9bwXP MxlDMM6KYmNhwFyHlLdEIM7MIymIQcgyAaD3gCXnAw==
X-Google-Smtp-Source: ABdhPJw0UmqxOBmH1rDyNR6i+LY7jK+mGs/EcarfqWAAsKPk2YNGEWANvyLcUtoY+25T63c6w1sIWJXvMuXYcUO6kXU=
X-Received: by 2002:ac2:5feb:: with SMTP id s11mr5688173lfg.591.1624427233647; Tue, 22 Jun 2021 22:47:13 -0700 (PDT)
MIME-Version: 1.0
References: <20210622203227.GA17412@pfrc.org>
In-Reply-To: <20210622203227.GA17412@pfrc.org>
From: Robert Raszuk <robert@raszuk.net>
Date: Wed, 23 Jun 2021 07:47:02 +0200
Message-ID: <CAOj+MMH1qRbHjqTJAdbgV1_OGC5x18VYgzfweN3KwmwOrryDhg@mail.gmail.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: bgp-autoconf@ietf.org, idr-chairs <idr-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000039af2f05c56870c7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/vfPjwkvun0v5b2fhw-ZayrQjyzI>
Subject: Re: [Bgp-autoconf] bgp auto configuration -01 update after interim discussion
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, 23 Jun 2021 05:47:23 -0000

Hi Jeff,

I think one thing from the list below requires a bit of clarification ...
specifically this is about AFI/SAFI list.

   BGP Session Protocol State, discovered at BGP OPEN:

   *  AS Numbers
   *  BGP Identifier
  * *  Supported AFI/SAFIs*


So I have two questions:


Q1 Assume operator needs to enable new AFI/SAFI at some point. How
would it work as far as auto discovery is concerned ?


Q2 Assume we use dynamic capabilities (only for AFI/SAFI update) how
would it work with auto discovery if at all ?


I guess the bigger question here is the scope of auto discovery.


Is auto-discovery simply bootstrap any BGP relation between peers ?


or


Is auto discovery required/to be also used in run time when adding new
AFI/SAFIs for already established session(s) ?


The reason for this is that what we are doing is essentially
duplicating AFI/SAFI from BGP OPEN which I am not sure if this is a
feature or a bug.


Lastly, how about cases where endpoints have configured potential
peering, however it is not activated in cfg. Assuming that we would
still want to signal those in autodiscovery would you send it when
enabled and not activated on a neighbor ?


Thx,
R.










On Tue, Jun 22, 2021 at 10:06 PM Jeffrey Haas <jhaas@pfrc.org> wrote:

> Please find attached proposed updates to the auto-configuration
> Internet-Draft that attempts to address the consensus discussion at this
> week's IDR interim for auto configuration.
>
> I'd like to publish this on Friday.  Your review is greatly appreciated.
>
> -- Jeff
> --
> Bgp-autoconf mailing list
> Bgp-autoconf@ietf.org
> https://www.ietf.org/mailman/listinfo/bgp-autoconf
>

v2.23.0 | Report a Bug | By Email