OlivierHecart

1. With the standard DDSI protocol, all Participants in the system need to discover all remote Participants, DataReaders and DataWriters in the system. A reliable "channel" with some state to...

By the way, you may be interested in reading: 1. [This zenoh.io blog post](https://zenoh.io/blog/2021-03-23-discovery/) about discovery overhead with some real figures. 2. [This zenoh.io blog post](https://zenoh.io/blog/2021-06-14-zenoh-reliability/) on zenoh reliability and...

This is probably due to incompatible storages and/or rest plugins. Maybe @JEnoch or @gabrik can provide more infos as the first investigated those problems and the second faced them.

What we are trying to ensure is that the same zenoh resources can be retrieved using the same queries and selectors from our language bindings (rust, c, python, ...) as...

Zenoh clearly targets dynamic networks where nodes are constantly joining, leaving and or moving and where the network topology changes frequently. From our past experience UDP multicast is often poorly...

The [zenoh.io](https://zenoh.io) clearly needs to be improved on a lot of aspects and dynamic networks support is obviously one of them. Note that we tend to publish figures and plots...

@ckaran No, we can't do that in our simplistic simulation environment right now. But this is something we'll have to test and characterize as well.

Merged here: https://github.com/eclipse-zenoh/zenoh/pull/774

> For now, my main blocker is not code (I haven't read much of it yet), but lack of documentation. Most of the answers (if they exist) are there: https://github.com/eclipse-zenoh/roadmap/blob/main/rfcs/ALL/Non%20Blocking%20Fault%20Tolerant%20Reliability.md...

> @Mallets @OlivierHecart @DariusIMP noticed, that there is a problem with this issue. Before the fix the `reply_id` was set to random, which was definitely wrong: https://github.com/eclipse-zenoh/zenoh/pull/1138/files#diff-f0aac9d83f0d53d0be9a6ee02269c26605c3920dbd6782f744e59c21aec235d5L2311 > > But...