IETF Logo Mail Archive

Re: [Bgp-autoconf] Discussion about BGP autoconf requirements in DC

Randy Bush <randy@psg.com> Fri, 07 February 2020 22:50 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 CDACF1200FA for <bgp-autoconf@ietfa.amsl.com>; Fri, 7 Feb 2020 14:50:11 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 IS5MybXARhEn for <bgp-autoconf@ietfa.amsl.com>; Fri, 7 Feb 2020 14:50:10 -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 66B43120103 for <bgp-autoconf@ietf.org>; Fri, 7 Feb 2020 14:50:10 -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 1j0CRr-0006Gj-Di; Fri, 07 Feb 2020 22:50:07 +0000
Date: Fri, 07 Feb 2020 14:50:06 -0800
Message-ID: <m2a75u3tcx.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>
Cc: "bgp-autoconf@ietf.org" <bgp-autoconf@ietf.org>
In-Reply-To: <89bb996682564b99af57133a76b8dc6b@huawei.com>
References: <89bb996682564b99af57133a76b8dc6b@huawei.com>
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/MDg-48DVX7jycjuIHGSXy80LBdY>
Subject: Re: [Bgp-autoconf] Discussion about BGP autoconf requirements in DC
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: Fri, 07 Feb 2020 22:50:12 -0000

> EBGP using connected-interface address
> EBGP using loopback address
> ECMP
> Validation of allowed peers
> Liveness detection
> Supported address family for session setup: IPv4, IPv6
> Authentication
> ....
> 
> Please share your opinions about this list.

- signal your ip address (which will tell me v4 or v6) and, as
  it is the 21st century, assump MPBGP
- signal your asn.  if it is the same as mine, it's iBGP so
  no need to think about multi-hop etc
- signal how many hops i need to get to your listener
- signal the authentication

isn't the rest either discoverd/agreed in the OPEN or automagic?

randy

v2.23.0 | Report a Bug | By Email