[GROW] Re: I-D Action: draft-ietf-grow-bmp-adj-ribs-filtered-01.txt

Camilo Cardona <ietf@grogsletters.cc> Fri, 16 October 2026 15:02 UTC

Received: from sender5-op-o12.zoho.com (sender5-op-o12.zoho.com [165.173.182.12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 3EA3E46 for <grow@ietf.org>; Fri, 16 Oct 2026 15:02:39 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=none; arc=pass ("zohomail.com:s=zohoarc:i=1"); spf=pass (mx.ietf.org: domain of ietf@grogsletters.cc designates 165.173.182.12 as permitted sender) smtp.mailfrom=ietf@grogsletters.cc; dmarc=none
ARC-Seal: i=1; a=rsa-sha256; t=1792162950; cv=none; d=zohomail.com; s=zohoarc; b=dXNiwC1oTirezXA5x77V2ccpoa87C1zZncstAbboCqcKq0jHfAsrWVy6ZfecF19U5G7QQsKxYQA4oNA7Rk8FYE3xQ0e9KvW63CqtHTGtqiDjcle7JlJ0hPk10n9JXc6j3GDrWv8pn7+FzcRqMoLCn+ZPUlTLH52V/f2zC4QIrWI=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1792162950; h=Content-Type:Date:Date:From:From:In-Reply-To:MIME-Version:Message-ID:Subject:Subject:To:To:Message-Id:Reply-To:Cc; bh=ING9XJQ+kzbMmQMo0XuJnboAdDNGvDMSUSa3vnw3qBU=; b=bpN3110azxCxaWkGU32JbOvh0y5VGrpiorAxJOwG4s/4TMY0pricDrG+/8xNlKC6KewIWPR6cKeW6Y7U35UaNsZJvJryqnyOMVrW80RSRszGQeIGJvvao43qZOF1K7QEq77ESpK260YxMstd79TM8Sbs7FUP7P5ZXvMFKBU79ug=
ARC-Authentication-Results: i=1; mx.zohomail.com; spf=pass smtp.mailfrom=ietf@grogsletters.cc; dmarc=pass header.from=<ietf@grogsletters.cc>
Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1792162945125349.8921273833387; Fri, 16 Oct 2026 08:02:25 -0700 (PDT)
Date: Fri, 16 Oct 2026 10:02:25 -0500
From: Camilo Cardona <ietf@grogsletters.cc>
To: grow <grow@ietf.org>
Message-Id: <1a1453c5814.673325253480578.7470063191057146907@grogsletters.cc>
In-Reply-To: <179210709917.535502.16211142861117630860@dt-datatracker-66f49ddcbd-klxkm>
References: <179210709917.535502.16211142861117630860@dt-datatracker-66f49ddcbd-klxkm>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_11793314_636068854.1792162945044"
Importance: Medium
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
X-Spamd-Bar: -----------------
Message-ID-Hash: FBSLUIQCPTY2IU7VSB7TSWFO6G3Z5N36
X-Message-ID-Hash: FBSLUIQCPTY2IU7VSB7TSWFO6G3Z5N36
X-MailFrom: ietf@grogsletters.cc
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-grow.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [GROW] Re: I-D Action: draft-ietf-grow-bmp-adj-ribs-filtered-01.txt
List-Id: Grow Working Group Mailing List <grow.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/5ahf5q1OWwR0MaENC15EPiuiQtw>
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>

Hello grow,

We submitted a new version of draft-ietf-grow-bmp-adj-ribs-filtered.

The main change of this version relates to an email Paolo Lucente sent in this group a while ago: there is no coordinated treatment of BMP statistics across the different RIBs and new TLVs. Each one is doing its own thing, and it is hard to steer this without global coordiation that should also include what operators actually use from BMP statistics.

Since this is a document that is, on purpose, simple, we don't want to propose anything different or solve the above problem. We therefore decided to simplify everything related to BMP statistics and make the F flag consistent with the already standardized O flag over the same RIBs. The draft now proposes not modifying any BMP statistics semantics at all: the F flag is unset in Statistics Report messages and should be ignored. More global and coordinated work can modify this in the future, if needed.

Besides that, we clarified some of the text, made explicit that describing the filters is outside the scope of the document (added the BMP YANG draft as an informative reference for this); removed unneeded draft dependencies; and updated the Security Considerations.


Thanks,

Camilo & Paolo & Mukul







De:  <internet-drafts@ietf.org>
Para: <i-d-announce@ietf.org>
CC: <grow@ietf.org>
Fecha: jue, 15 oct 2026 18:31:39 -0500
Asunto: [GROW] I-D Action: draft-ietf-grow-bmp-adj-ribs-filtered-01.txt



Internet-Draft draft-ietf-grow-bmp-adj-ribs-filtered-01.txt is now available. 
It is a work item of the Global Routing Operations (GROW) WG of the IETF. 
 
 Title:   Filtering Adj-Rib-In and Adj-Rib-Out to BMP receivers 
 Authors: Paolo Lucente 
 Camilo Cardona 
 Mukul Srivastava 
 Name:    draft-ietf-grow-bmp-adj-ribs-filtered-01.txt 
 Pages:   5 
 Dates:   2026-10-15 
 
Abstract: 
 
 Filtering RIBs in BMP (BGP Monitoring Protocol) can be desirable for 
 several use-cases like, for example, limiting the amount of data a 
 collector station has to process or allow a sender to export only a 
 certain afi/safi of interest.  This document defines an indicator to 
 inform a collector station that a Adj-Rib-In or Adj-Rib-Out data feed 
 is being filtered at the BMP exporter.  This document updates RFC 
 7854. 
 
The IETF datatracker status page for this Internet-Draft is: 
https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-adj-ribs-filtered/  
 
There is also an HTMLized version available at: 
https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-adj-ribs-filtered-01  
 
A diff from the previous version is available at: 
https://author-tools.ietf.org/iddiff?url2=draft-ietf-grow-bmp-adj-ribs-filtered-01  
 
Internet-Drafts are also available by rsync at: 
rsync.ietf.org::internet-drafts 
 
 
_______________________________________________ 
GROW mailing list -- mailto:grow@ietf.org  
To unsubscribe send an email to mailto:grow-leave@ietf.org