IETF Logo Mail Archive

Re: [GROW] [Idr] RFC7854: EoR

Zhuangshunwan <zhuangshunwan@huawei.com> Wed, 21 September 2022 11:56 UTC

Return-Path: <zhuangshunwan@huawei.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D4D8C1522B3 for <grow@ietfa.amsl.com>; Wed, 21 Sep 2022 04:56:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kK4BdKpWv2cV for <grow@ietfa.amsl.com>; Wed, 21 Sep 2022 04:56:04 -0700 (PDT)
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 E7807C14CE41 for <grow@ietf.org>; Wed, 21 Sep 2022 04:56:03 -0700 (PDT)
Received: from fraeml701-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4MXcKY06zkz688nT for <grow@ietf.org>; Wed, 21 Sep 2022 19:54:57 +0800 (CST)
Received: from kwepemi500004.china.huawei.com (7.221.188.17) by fraeml701-chm.china.huawei.com (10.206.15.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.31; Wed, 21 Sep 2022 13:56:00 +0200
Received: from kwepemi500002.china.huawei.com (7.221.188.171) by kwepemi500004.china.huawei.com (7.221.188.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Wed, 21 Sep 2022 19:55:58 +0800
Received: from kwepemi500002.china.huawei.com ([7.221.188.171]) by kwepemi500002.china.huawei.com ([7.221.188.171]) with mapi id 15.01.2375.031; Wed, 21 Sep 2022 19:55:58 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.com>
To: Robert Raszuk <robert@raszuk.net>, Paolo Lucente <paolo@ntt.net>
CC: "grow@ietf.org" <grow@ietf.org>, Maximilian Wilhelm <max@rfc2324.org>
Thread-Topic: [GROW] [Idr] RFC7854: EoR
Thread-Index: AQHYyGkCB1AhD9+82kaEpyfqqrSmha3e4Z0AgAAlNoCAAkylAIAFZf2AgACfEKX//5nwAIAA8lVlgACtjwCAAFNXgIAA6kaw
Date: Wed, 21 Sep 2022 11:55:58 +0000
Message-ID: <fe74bf2a426541c2a72bb31e1a1b8dc7@huawei.com>
References: <bd7c5fb4-b398-c979-6f6b-0de82fd2ee12@bernat.ch> <dba40193-138e-5981-a4c2-6fc44fadde51@bernat.ch> <20220912203612.GA18968@pfrc.org> <6CB8C0EB-DC6E-48A8-993A-C98DEBD0D04A@juniper.net> <463DBA4E-3136-4A0F-A298-D081FEB123EB@pfrc.org> <20220914230819.GD27304@principal.rfc2324.org> <20220916101510.GA1365691@corley.shackle.nl> <MW3PR11MB4651FA81C4FC0E6C0F488DB4B64D9@MW3PR11MB4651.namprd11.prod.outlook.com> <CAOj+MMFtgEDOpXLREEsv8ovpeFXzQOtGv9EO88y5cB2eTo+UdA@mail.gmail.com> <MW3PR11MB46513C54B1D47195ECCBDBF2B64D9@MW3PR11MB4651.namprd11.prod.outlook.com> <CAOj+MME6W8RriOD6o_Cxktx1QnhFVx1ckSgm3VnFhV15FvNPrw@mail.gmail.com> <bea671a4-fc4b-f213-82c0-1ed160be2798@ntt.net> <CAOj+MMG8+4v6NbW+iEvL9Xit+_bDi4PHzWf_S70aXCvj_8wSMw@mail.gmail.com>
In-Reply-To: <CAOj+MMG8+4v6NbW+iEvL9Xit+_bDi4PHzWf_S70aXCvj_8wSMw@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.202.95]
Content-Type: multipart/alternative; boundary="_000_fe74bf2a426541c2a72bb31e1a1b8dc7huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/s_eZM5G8iuTCFMP44l4a74C_vtc>
Subject: Re: [GROW] [Idr] RFC7854: EoR
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Sep 2022 11:56:10 -0000

Hi Robert,

Which use cases require such accurate BGP churn information?

Thanks,
Shunwan

From: GROW [mailto:grow-bounces@ietf.org] On Behalf Of Robert Raszuk
Sent: Wednesday, September 21, 2022 1:52 PM
To: Paolo Lucente <paolo@ntt.net>
Cc: grow@ietf.org; Maximilian Wilhelm <max@rfc2324.org>
Subject: Re: [GROW] [Idr] RFC7854: EoR

Hi Paolo,

A-la: there is multiple updates related to a certain NLRI by when a BMP
message is to be sent out, let's state-compress (ie. not send out) those
that were already obsoleted by a subsequent update.

But this will hide BGP churn for a given NET to be detectable by BMP receiver. Is this a good thing ? I am not sure. It is a loss of information to me.

Thx,
R.

v2.46.0 | Report a Bug | By Email | System Status