>>> what would be your suggestion for message broker?
I haven’t thought of any solution but from top of my mind I can think of
following:
1.
Some kind of controlled mechanism to enforce message ordering. For example,
acks from BMP collector for some messages. This has its own challenge, like
this will require two-way messaging in BMP and other considerations.
2.
3.
Adding some implementation considerations in the draft which can guide
implementation:
4.
*
Simplest solution: All BMP messages will go on one topic. This will guarantee
all BMP messages from a router are ordered. Given a production deployment will
have multiple partitions on this topic and feed from different routers will
land on different partitions, there is still some parallelism here. We are
achieving ordering at the cost of true parallelism.
*
*
Identifying control messages in BMP like, init, term, peer up/down and sending
these control messages on same topic, say control-topic. Other BMP messages can
go in different topics but there can still be ordering problem. For example, RM
message can arrive at BMP station after processing term message from the
router. So, BMP station needs to be aware of this situation and handle it by
using some internal state.
Thanks
Mukul
From: [email protected] <[email protected]>
Date: Monday, March 16, 2026 at 10:17 PM
To: Srivastava, Mukul <[email protected]>,
[email protected]
<[email protected]>,
draft-netana-nmop-message-broker-bmp-telemetry-msg.auth...@ietf.org
<draft-netana-nmop-message-broker-bmp-telemetry-msg.auth...@ietf.org>
Cc: [email protected] <[email protected]>, [email protected] <[email protected]>
Subject: RE: draft-netana-nmop-message-broker-bmp-telemetry-msg - BMP message
ordering on Kafka
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.
2. 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
_______________________________________________
GROW mailing list -- [email protected]
To unsubscribe send an email to [email protected]
