You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Zenoh team. Just discovered Zenoh because of a Zephyr-related tweet and I find it very exciting!
I'm most interested to understand in detail how the protocol (especially the lower layer zenoh.net) works, but I didn't find any details regarding packet routing, frame formats, headers etc. on zenoh.io. Is there some other place where this is documented? Is there something like an RFC for the protocol?
BTW: We are also working on a low-overhead protocol called ThingSet to seamlessly interact with resource-constrained devices over different lower layers including CAN, serial, LoRaWAN etc.. I'd be very interested to see how both approaches could work together.
The text was updated successfully, but these errors were encountered:
We used to have a protocol specification for zenoh, but as the protocol has evolved quite rapidly, we retired the spec from our website as it had become obsolete. That said, we plan to update it, since as you may imagine we get often this request -- thus stay tuned!
Concerning your initiative on ThingSet, I'll take a look as I'd like to learn more about it and will get back to you.
Hi Zenoh team. Just discovered Zenoh because of a Zephyr-related tweet and I find it very exciting!
I'm most interested to understand in detail how the protocol (especially the lower layer zenoh.net) works, but I didn't find any details regarding packet routing, frame formats, headers etc. on zenoh.io. Is there some other place where this is documented? Is there something like an RFC for the protocol?
BTW: We are also working on a low-overhead protocol called ThingSet to seamlessly interact with resource-constrained devices over different lower layers including CAN, serial, LoRaWAN etc.. I'd be very interested to see how both approaches could work together.
The text was updated successfully, but these errors were encountered: