IETF Logo Mail Archive

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

Robert Raszuk <robert@raszuk.net> Wed, 23 June 2021 14:07 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 1E8473A3922 for <bgp-autoconf@ietfa.amsl.com>; Wed, 23 Jun 2021 07:07:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 Z6UUYnK7-lCX for <bgp-autoconf@ietfa.amsl.com>; Wed, 23 Jun 2021 07:07:35 -0700 (PDT)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (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 7A7563A3923 for <bgp-autoconf@ietf.org>; Wed, 23 Jun 2021 07:07:35 -0700 (PDT)
Received: by mail-lf1-x130.google.com with SMTP id k10so4238337lfv.13 for <bgp-autoconf@ietf.org>; Wed, 23 Jun 2021 07:07:35 -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=883r3GGSh065cqAALI3SWxLr5RAB6fBBtOHnz9h5tmE=; b=IkSF3Jp0WjYwbH/wSzrj63ymBt1QBQXfLhsanzUPBTHJa/Ya/6fQ0l75z4kQG4qhz4 ts2mLX5h87ZVS3+/MSeTtatJrwkTUxp8rPUmLysb5vCkncCMtzeIhpzkT7AJDH91jQRk pnvzyfqqiO1X8UlwTEqCRy2T9kpNZzLhoYuKpM8RvfiYQ5VFH8hEWJ6L+6CYpgFSzB72 0DA051NwxARx2hqZYkdXRT46hhL22L1HvZjXCVuNjH0FiB9puaTb4ynQIpId+G6yD5Nd hjjZot0180Q61L2TfrqRHQPTX+NvUl9YXLU+zySrRUAgP80muLTGM7pBVKlacOgnWhmX JVfg==
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=883r3GGSh065cqAALI3SWxLr5RAB6fBBtOHnz9h5tmE=; b=DmK49SmjDn59837TyBQ8/6quzK+OEpf0A2u8aACmqQIwp7/Ry0jWX4Dd0ahBqV6VAB rz/ndLkvW86HK+S5kLl3ky6+IzEUguSV/UJUtIXnimS4FPsAW6qsvR7F0rsClNe6gZPc AHPHIVinSJUM1tUjZsBF20ZU7wsT9R6ttTfk/mjR4PN2+pBR36kwZBhUHtb2EQeNk1nV 9TnHTPx+WTe/evPJRJ4D5is5amSubvY56sPqZ6b8girJtsA2xgUjv9K5HYqbfDhO1CQW wW4lI04N7l3W39d29pbCVR4AIdfRdPH3C/g2RxNt6B2gh45KwcAWHUkeCPHokrFkQNa4 OmSg==
X-Gm-Message-State: AOAM533aGHSBIM4QlwZ8z3LzcZXX6Unytycj7l/JW5eBYlsSZ7vaFmB+ cIM6v00Ewlg6HyAkr3WJgGOqGhAIRZyGjMuLb3I3tA==
X-Google-Smtp-Source: ABdhPJzY+KIJk79h7xlyyBDsxzLXC2e9kboJfyE7LfxCJ95holliWosX+sAvs/i4ngMBKeD3ekTtWYgvlEJThflgGec=
X-Received: by 2002:ac2:5feb:: with SMTP id s11mr7214277lfg.591.1624457252022; Wed, 23 Jun 2021 07:07:32 -0700 (PDT)
MIME-Version: 1.0
References: <20210622203227.GA17412@pfrc.org> <CAOj+MMH1qRbHjqTJAdbgV1_OGC5x18VYgzfweN3KwmwOrryDhg@mail.gmail.com> <20210623130335.GA14665@pfrc.org> <CAOj+MMEE4BZeOw0LNfHSoquocTTw_PK0KnS8YBUoefsdHhPYpg@mail.gmail.com> <20210623140436.GA18680@pfrc.org> <CAOj+MMGe7y04nWMqm9grK70y00LbQ+FfAv+bmJDjd7On_OofgQ@mail.gmail.com> <20210623142555.GB14665@pfrc.org>
In-Reply-To: <20210623142555.GB14665@pfrc.org>
From: Robert Raszuk <robert@raszuk.net>
Date: Wed, 23 Jun 2021 16:07:21 +0200
Message-ID: <CAOj+MMHYQWCk4w6Dz+b=A5TxV-_jMLf7OpaTakc-cyKa0fqVCQ@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="00000000000075b94c05c56f6d1c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/gGw_9YT3GbFNkTMWwR5HddbPaeQ>
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 14:07:41 -0000

>
> Time 2: The discovery message indicates the version number has changed.
>
> Time 3: The client opens a session again.  This time, it notices that the
> required VPNv4 Unicast is present and considers the session acceptable.
> The
> session is permitted to move to Established.
>

I meant one peer adds new SAFI in the cfg and BGP OPEN starts without any
discovery.


That's certainly permissible in the mechanism described.  Auto-discovery
> doesn't remove the need for all configuration.
>
> If both sides select passive mode, nothing will come up.


Sorry I meant to also extend the concept of BGP passive to the
AutoDiscovery passive side. Of course each sitting on the opposite sides.

Thx,
Robert.

v2.23.0 | Report a Bug | By Email