IETF Logo Mail Archive

Re: [Bgp-autoconf] assumptions

Randy Bush <randy@psg.com> Tue, 25 February 2020 21:15 UTC

Return-Path: <randy@psg.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 27FCA3A15F8 for <bgp-autoconf@ietfa.amsl.com>; Tue, 25 Feb 2020 13:15:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 4lMhOaa94AMl for <bgp-autoconf@ietfa.amsl.com>; Tue, 25 Feb 2020 13:15:24 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1FF83A15F6 for <bgp-autoconf@ietf.org>; Tue, 25 Feb 2020 13:15:23 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1j6hY0-0006OO-Eg; Tue, 25 Feb 2020 21:15:20 +0000
Date: Tue, 25 Feb 2020 13:15:19 -0800
Message-ID: <m24kvextaw.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: bgp autoconf <bgp-autoconf@ietf.org>, "Dongjie (Jimmy)" <jie.dong@huawei.com>
In-Reply-To: <F9DF2BA0-3980-488E-B10B-B8E57C804DAB@pfrc.org>
References: <m2v9nvxsc6.wl-randy@psg.com> <3fc500dc7cdd4df2967ad51efdb5cf29@huawei.com> <m2eeuixxaa.wl-randy@psg.com> <F9DF2BA0-3980-488E-B10B-B8E57C804DAB@pfrc.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/megti_mRg4MLWcRiwWckdu42ZOc>
Subject: Re: [Bgp-autoconf] assumptions
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: Tue, 25 Feb 2020 21:15:25 -0000

> I believe that sticking with as close to base BGP as possible is a
> feature: It means that auto-discovery features can be lightly strapped
> on top of boring BGP implementations that have modest support for
> programmatic neighbor setup.

i can support this position

randy

v2.8.7 | Report a Bug | By Email