Applying Mesh Protocol 1.1 specification
Hi,
I found that the bluetooth-mesh part has not applied SIG Mesh Protocol 1.1 specification yet. I would like to update various changes to the specification, such as SAR transmitter/receiver state.
For example, in the line corresponding to the link below, I don't understand why it sends a segmented message for a multicast address a fixed number of times, 4 times. This is causing performance issues with my product.
https://github.com/bluez/bluez/blob/master/mesh/net.c#L3335
Most of the mesh/net.c code was last written 4 or 6 years ago and is out of date with Mesh Protocol 1.1. Is there a reason for not applying Mesh Protocol 1.1 or is anyone working on?
Regards,
Junho Lee
Quoted 5 lines · Junho Lee
Hi,
I found that the bluetooth-mesh part has not applied SIG Mesh Protocol 1.1 specification yet. I would like to update various changes to the specification, such as SAR transmitter/receiver state.
Nobody has the job currently of maintaining bluetooth-meshd specifically. I still keep an eye on patch submissions to the mesh daemon and tools, so if you would like to implement the v1.1 changes, I would be happy to be an extra set of eyes.
Quoted 14 lines
For example, in the line corresponding to the link below, I don't understand why it sends a segmented message for a multicast address a fixed number of times, 4 times. This is causing performance issues with my product.
https://github.com/bluez/bluez/blob/master/mesh/net.c#L3335Most of the
mesh/net.ccode was last written 4 or 6 years ago and is out of date with Mesh Protocol 1.1. Is there a reason for not applying Mesh Protocol 1.1 or is anyone working on?Regards,
Junho Lee