[Bgp-autoconf] Minutes and action points of the conference call

"Dongjie (Jimmy)" <jie.dong@huawei.com> Tue, 25 February 2020 15:27 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 266213A0EEF for <bgp-autoconf@ietfa.amsl.com>; Tue, 25 Feb 2020 07:27:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, WEIRD_PORT=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 YHKRJWfF3fEQ for <bgp-autoconf@ietfa.amsl.com>; Tue, 25 Feb 2020 07:27:57 -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 DA0183A0EE2 for <bgp-autoconf@ietf.org>; Tue, 25 Feb 2020 07:27:56 -0800 (PST)
Received: from LHREML713-CAH.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 3087BBC2732C0409A40A for <bgp-autoconf@ietf.org>; Tue, 25 Feb 2020 15:27:55 +0000 (GMT)
Received: from nkgeml703-chm.china.huawei.com (10.98.57.159) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 25 Feb 2020 15:27:54 +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; Tue, 25 Feb 2020 23:27:51 +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; Tue, 25 Feb 2020 23:27:51 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "bgp-autoconf@ietf.org" <bgp-autoconf@ietf.org>
Thread-Topic: Minutes and action points of the conference call
Thread-Index: AdXr7hePhzMOppJARo6tbqvLM4QuyQ==
Date: Tue, 25 Feb 2020 15:27:51 +0000
Message-ID: <37b4733413184637b822528e7939f677@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.190.197]
Content-Type: multipart/alternative; boundary="_000_37b4733413184637b822528e7939f677huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/uX7bE6e2xZXub-r29AG-xxDTdK0>
Subject: [Bgp-autoconf] Minutes and action points of the conference call
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 15:27:59 -0000

Hi all,

First of all, thank you for attending the conference call, we had good discussion on several items, and many thanks to Sue and others who helped with the minutes.

The minutes is on https://etherpad.ietf.org:9009/p/bgp-autoconf-feb-25, please check if you want to make any change to it.

I also summarized our discussion and action points as below:

- We agreed to work on DC first, while keep an eye on what makes the other cases different.

- For DC case, will focus on intra-data center which uses BGP as underlay, either interface addresses or loopbacks can be used for peering. Inter-DC and VPNs are out of scope.

- We had some discussion about whether we should cover the misconnectivity or misconfiguration detection, there is still no clear result.

- The team agrees that discovering the role of a device could be useful, something similar has been used in RIFT.

- We discussed the security requirements, the authentication has two properties, transport or object security, and authenticating the peer.

- In order to reduce the number of parallel peers between two nodes, need to use loopbacks to setup only one session, then need to consider how to automatically generate the configuration of routes to peer's loopback.

- Enablement of BFD based on auto-discovery is considered as one optional function, while the complexity needs to be considered.

- Some considerations on Zero touch provisioning (ZTP). It is assumed some level of provisioning/pre-configuration is still required.

The team agrees to look at the list of solution drafts, summarize the requirements from each draft, and find a minimal common set.

Action points:
1. The author of each draft to summarize the list of requirement from his draft, and share it on design team list. (by end of this Friday)
2. Other people can provide additional comments to the summarized requirements. (in next week)
3. The team to provide a minimal common set.

Best regards,
Jie