[Lsvr] Mail regarding draft-ietf-lsvr-bgp-spf
"Wanghaibo (Rainsword)" <rainsword.wang@huawei.com> Fri, 26 February 2021 07:52 UTC
Return-Path: <rainsword.wang@huawei.com>
X-Original-To: lsvr@ietfa.amsl.com
Delivered-To: lsvr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 736F23A09A8; Thu, 25 Feb 2021 23:52:00 -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, HTML_MESSAGE=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Rgv-Mo78f1c; Thu, 25 Feb 2021 23:51:57 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F2933A099F; Thu, 25 Feb 2021 23:51:57 -0800 (PST)
Received: from fraeml702-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Dn1wP4s3hz67nkl; Fri, 26 Feb 2021 15:47:49 +0800 (CST)
Received: from nkgeml707-chm.china.huawei.com (10.98.57.157) by fraeml702-chm.china.huawei.com (10.206.15.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2106.2; Fri, 26 Feb 2021 08:51:54 +0100
Received: from nkgeml705-chm.china.huawei.com (10.98.57.154) by nkgeml707-chm.china.huawei.com (10.98.57.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Fri, 26 Feb 2021 15:51:52 +0800
Received: from nkgeml705-chm.china.huawei.com ([10.98.57.154]) by nkgeml705-chm.china.huawei.com ([10.98.57.154]) with mapi id 15.01.2106.006; Fri, 26 Feb 2021 15:51:52 +0800
From: "Wanghaibo (Rainsword)" <rainsword.wang@huawei.com>
To: "draft-ietf-lsvr-bgp-spf@ietf.org" <draft-ietf-lsvr-bgp-spf@ietf.org>
CC: "lsvr@ietf.org" <lsvr@ietf.org>
Thread-Topic: Mail regarding draft-ietf-lsvr-bgp-spf
Thread-Index: AdcMEV6wVUgT/mecQUWDtas8BsLytA==
Date: Fri, 26 Feb 2021 07:51:52 +0000
Message-ID: <9a6112022a184b6eb54bdc4176627fbd@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.153.118]
Content-Type: multipart/alternative; boundary="_000_9a6112022a184b6eb54bdc4176627fbdhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/5W2PNy5I0nTcMLgjO3msXzpgZUo>
X-Mailman-Approved-At: Thu, 25 Feb 2021 23:54:16 -0800
Subject: [Lsvr] Mail regarding draft-ietf-lsvr-bgp-spf
X-BeenThere: lsvr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Vector Routing <lsvr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsvr>, <mailto:lsvr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsvr/>
List-Post: <mailto:lsvr@ietf.org>
List-Help: <mailto:lsvr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsvr>, <mailto:lsvr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Feb 2021 07:52:01 -0000
Hi authors, I have found that from the draft-ietf-lsvr-bgp-spf-12 version, a chapter 6.1.1. BGP Self-Originated NLRI is added, whici is similar to IGP. BGP-SPF's NLRI advertisement is based on BGP, should we need to do this? With BGP machanism, one device advertise its own NLRI will not receive it again, because of loop detection(AS loop or originator-id loop) If we allow that loop, it means that we may change the BGP basic mechanics and how to avoid message loop? Regards, Haibo
- [Lsvr] Mail regarding draft-ietf-lsvr-bgp-spf Wanghaibo (Rainsword)