[GROW] Re: review request: BMP statistics scoping and interoperability

Paolo Lucente <paolo@ntt.net> Tue, 01 September 2026 23:44 UTC

Return-Path: <paolo@ntt.net>
X-Original-To: grow@mail2.ietf.org
Delivered-To: grow@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id C3DAB13370F68 for <grow@mail2.ietf.org>; Tue, 1 Sep 2026 16:44:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1788306245; bh=ONK4/uyXVxu1UQE2KKPyDhDlij2g1ScBaPwvK0ARocE=; h=Date:From:Subject:To:Cc:References:In-Reply-To; b=STQuw6Kg0oCG8cmbKWnVRmO1mNaNhA/u8cA6BPq0DZoLV0eHbEbdokrSI34g7/Jds AF+rGBg8tpDQWJ3dwAxK8sG1MrOLguOC2WPemy8F/hjG7OPr0vr+VJjBTokcEKVzro ojZtHhg8UsGBccYk4LMADiMRQ6WwSJSCxKHKIMZU=
X-Virus-Scanned: amavisd-new at ietf.org
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AUSb4pn0NAjz for <grow@mail2.ietf.org>; Tue, 1 Sep 2026 16:44:05 -0700 (PDT)
Received: from mx1.vm.gin.ntt.net (mail.gin.ntt.net [IPv6:2001:418:3ff:5::192:26]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 2162913370F4B for <grow@ietf.org>; Tue, 1 Sep 2026 16:44:05 -0700 (PDT)
Received: from [10.125.141.157] (unknown [201.90.183.106]) by mx1.vm.gin.ntt.net (Postfix) with ESMTPSA id 8E39B40408; Tue, 1 Sep 2026 23:44:03 +0000 (UTC)
Message-ID: <aa647d6c-358e-4ee8-93ed-d17a432bc32f@ntt.net>
Date: Tue, 01 Sep 2026 20:44:01 -0300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
From: Paolo Lucente <paolo@ntt.net>
To: "Dikshit, Saumya" <saumya.dikshit@hpe.com>, "grow@ietf.org" <grow@ietf.org>
References: <SJ0PR84MB2110D90967AB3231DD1F345B94A72@SJ0PR84MB2110.NAMPRD84.PROD.OUTLOOK.COM>
Content-Language: en-US
In-Reply-To: <SJ0PR84MB2110D90967AB3231DD1F345B94A72@SJ0PR84MB2110.NAMPRD84.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: MZUHV6DTICYXFP5PKYU2MYMJKC7BZT6I
X-Message-ID-Hash: MZUHV6DTICYXFP5PKYU2MYMJKC7BZT6I
X-MailFrom: paolo@ntt.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-grow.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "camilo@ntt.net" <camilo@ntt.net>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [GROW] Re: review request: BMP statistics scoping and interoperability
List-Id: Grow Working Group Mailing List <grow.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/gT_ylqGEnWlq_7WV8jQOOlPjA6c>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Owner: <mailto:grow-owner@ietf.org>
List-Post: <mailto:grow@ietf.org>
List-Subscribe: <mailto:grow-join@ietf.org>
List-Unsubscribe: <mailto:grow-leave@ietf.org>

Hi Saumya, All,

I think your proposal to make a "super draft" around statistics instead 
of doing sparse efforts here and there - which for once they are sparse 
but they are also difficult to track and put together in one framework - 
has definitely some merit. The details can be worked out along the way.

I wanted to take this opportunity for a side consideration, this did 
emerge actually from a recent conversation Camilo and myself had around 
the F flag draft: we are collectively putting lots of effort and 
attention to statistics in BMP but how important and, even more 
importantly, how used are they? So, especially among operators / BMP 
users reading, could we do something as basic as a show of hands (of 
course the more elaboration the better) in this sense? Are you using 
statistics? Yes/no? If into elaborating more: for what use-case(s), ie. 
just storing them for analysis, some sort of validation, else?

Paolo


On 17/8/26 15:08, Dikshit, Saumya wrote:
> 
> Hello All ,
> 
> I would like feedback on a BMP statistics issue that appears to be 
> missing from the current discussion.
> 
> There are several ways to represent the same class of object in BMP 
> today: per-instance gauge values scoped by AFI/SAFI, RD, EVPN instance, 
> or route-change policy.
> A collector that wants to support all of these may end up needing 
> multiple incompatible parsers for essentially the same operational concept.
> This is already being discussed in parallel emails chains and this the 
> gap I am trying to address with the following drafts:
> 
>   *
>     https://datatracker.ietf.org/doc/draft-saumthimma-evpn-ip-binding-
>     sync/ <https://datatracker.ietf.org/doc/draft-saumthimma-evpn-ip-
>     binding-sync/>
>   *
>     https://datatracker.ietf.org/doc/draft-dikshit-grow-bmp-rd-scoped-
>     rib-stats/ <https://datatracker.ietf.org/doc/draft-dikshit-grow-bmp-
>     rd-scoped-rib-stats/>
>   *
>     https://datatracker.ietf.org/doc/draft-smc-grow-bmp-route-change-
>     stats/ <https://datatracker.ietf.org/doc/draft-smc-grow-bmp-route-
>     change-stats/>
> 
> 
> This is an ask for review comments on the direction:
> 
>   *
>     whether a common instance-scoped / RD-scoped BMP statistics
>     structure is the right approach, and whether the statistics
>     ecosystem needs a shared pattern before these extensions proliferate.
> 
> 
> I would especially value feedback from people working on:
> 
> - BMP statistics
> - BMP data models
> - EVPN and VPN RIB reporting
> - route-change and policy-driven telemetry
> 
> If the WG thinks a common pattern is useful, I would be happy to align 
> the drafts around that structure.
> If not, It would be great to know about it now, than discovering it  later.
> 
> Thanks.
> Saumya Dikshit