IETF Logo Mail Archive

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

"Dongjie (Jimmy)" <jie.dong@huawei.com> Fri, 07 February 2020 10:38 UTC

Return-Path: <jie.dong@huawei.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 7A927120838 for <bgp-autoconf@ietfa.amsl.com>; Fri, 7 Feb 2020 02:38:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 dM8rcSCvXOAZ for <bgp-autoconf@ietfa.amsl.com>; Fri, 7 Feb 2020 02:38:07 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 C5296120241 for <bgp-autoconf@ietf.org>; Fri, 7 Feb 2020 02:38:07 -0800 (PST)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 063CB8DB58A27B3A7F12 for <bgp-autoconf@ietf.org>; Fri, 7 Feb 2020 10:38:05 +0000 (GMT)
Received: from nkgeml703-chm.china.huawei.com (10.98.57.159) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 7 Feb 2020 10:38:04 +0000
Received: from nkgeml701-chm.china.huawei.com (10.98.57.156) by nkgeml703-chm.china.huawei.com (10.98.57.159) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Fri, 7 Feb 2020 18:38:02 +0800
Received: from nkgeml701-chm.china.huawei.com ([10.98.57.156]) by nkgeml701-chm.china.huawei.com ([10.98.57.156]) with mapi id 15.01.1713.004; Fri, 7 Feb 2020 18:38:02 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "bgp-autoconf@ietf.org" <bgp-autoconf@ietf.org>
Thread-Topic: Discussion about BGP autoconf requirements in DC
Thread-Index: AdXdoUXCj6AoAVwuSs2cA3dZ7wwGNA==
Date: Fri, 07 Feb 2020 10:38:01 +0000
Message-ID: <89bb996682564b99af57133a76b8dc6b@huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.221.218]
Content-Type: multipart/alternative; boundary="_000_89bb996682564b99af57133a76b8dc6bhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/PRImJWJOravNeBlRQdrnaAXvs4c>
Subject: [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 10:38:09 -0000

Hi all,

It seems we have some consensus to work on the DC case first. Then we can start to identify the set of requirements of BGP auto-conf for using BGP as the underlay protocol in DC.

I try to make an initial list requirement as below. Some of the requirements may be optional, and some may be missing. Any comment

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.

Best regards,
Jie

v2.23.0 | Report a Bug | By Email