[Idr] Regarding comments on draft-wang-idr-bgp-ifit-capabilities

Lizhenbin <lizhenbin@huawei.com> Wed, 10 March 2021 15:55 UTC

Return-Path: <lizhenbin@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id B7BC73A1229 for <idr@ietfa.amsl.com>; Wed, 10 Mar 2021 07:55:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id t5gFkdQi4w2o for <idr@ietfa.amsl.com>; Wed, 10 Mar 2021 07:55:04 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E0E53A1227 for <idr@ietf.org>; Wed, 10 Mar 2021 07:55:04 -0800 (PST)
Received: from fraeml703-chm.china.huawei.com (unknown []) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Dwbzh4K81z67x3C for <idr@ietf.org>; Wed, 10 Mar 2021 23:46:56 +0800 (CST)
Received: from fraeml703-chm.china.huawei.com ( by fraeml703-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2106.2; Wed, 10 Mar 2021 16:55:00 +0100
Received: from DGGEMM422-HUB.china.huawei.com ( by fraeml703-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.2106.2 via Frontend Transport; Wed, 10 Mar 2021 16:54:59 +0100
Received: from DGGEMM512-MBS.china.huawei.com ([]) by dggemm422-hub.china.huawei.com ([]) with mapi id 14.03.0513.000; Wed, 10 Mar 2021 23:54:55 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: Tony Li <tony.li@tony.li>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: Regarding comments on draft-wang-idr-bgp-ifit-capabilities
Thread-Index: AdcVxLfkS+qkLnhFT6+BcnBJc3WyHA==
Date: Wed, 10 Mar 2021 15:54:55 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D93A2947E@dggemm512-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/4DfPr0ZLwY9R3RLwurjriKK9e1c>
Subject: [Idr] Regarding comments on draft-wang-idr-bgp-ifit-capabilities
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2021 15:55:06 -0000

Hi Tonny,
I am not sure if you do not like BGP to take too much unnecessary work. But the advantage of BGP is apparent:
1. BGP should not be used for management plane: Before BGP-LS, the topology can be collected by SNMP. BGP-LS definitely has much advantages in the performance and interoperability and becomes the de facto standard for SDN controller to collect topology information.
2. BGP should not be used for non-routing work. But BGP can be utilized to negotiate seamless BFD information.

BGP already becomes a god protocol :)

Best Regards,