Dear Mukul, You are raising with BMP message ordering an important. We have actually already discovered that and have been discussing that during the IETF hackathon weekend. I wanted to mention that during my GROW presentation but was constrained by time. Paolo as a co-author has a slot with NMOP where we will mention this.
In a nutshell. Message Brokers guarantee message ordering within one partition of a topic. Similar as with QUIC streams, we should come up with a topic addressing concept which honors that BMP message ordering is preserved where needed resp. separated into different topics where it makes sense most. Taking the work from https://datatracker.ietf.org/doc/html/draft-liu-grow-bmp-over-quic-06#section-4.1, dividing BMP messages into multiple streams, what would be your suggestion for message broker? Best wishes Thomas From: Srivastava, Mukul <[email protected]> Sent: Monday, March 16, 2026 10:13 PM To: Srivastava, Mukul <[email protected]>; draft-netana-nmop-message-broker-bmp-telemetry-msg.auth...@ietf.org Cc: [email protected] Subject: Re: draft-netana-nmop-message-broker-bmp-telemetry-msg - BMP message ordering on Kafka Be aware: This is an external email. Updating subject to include draft name. Thanks Mukul From: Srivastava, Mukul <[email protected]<mailto:[email protected]>> Date: Monday, March 16, 2026 at 10:07 AM To: draft-netana-nmop-message-broker-bmp-telemetry-msg.auth...@ietf.org<mailto:draft-netana-nmop-message-broker-bmp-telemetry-msg.auth...@ietf.org> <draft-netana-nmop-message-broker-bmp-telemetry-msg.auth...@ietf.org<mailto:draft-netana-nmop-message-broker-bmp-telemetry-msg.auth...@ietf.org>> Cc: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Subject: [GROW] BMP message ordering on Kafka Hello Authors I have a question on the data ordering between the producers (BMP speaking router) and consumers ( BMP station) . My high-level understanding on your draft is that a BMP speaker sends BMP feed to a BMP station based on the yang path subscription. The topics and indexes for partition are created in certain way as described in the draft. Pls correct me if my understanding is not correct. In Kafka, data ordering is guaranteed only on a single partition of a single topic. This means data can arrive unordered to the consumer in below cases- 1. Data sent by a producer across different topics. 1. Data sent by a producer, on a topic which has multiple partitions, and the producer is sending data on different partition. In a BMP echo system, data ordering is important. For example. a collector will expect bmp-init message from a router to arrive before bmp-term message. With the proposed key and topic format, I feel we have an out-out-order issue here. Let me know if I am missing something or this has been handled in some way in this draft. Thanks Mukul
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
