RFC: What's next for esp-openthread? Community Input Needed!

[tom-borcin]

Hello community! 👋

We're reaching out to gather input and ideas for the future development of this repository. Your feedback is crucial in shaping the project and ensuring that it meets the needs of the community.

Where we are?

Code has been validated on ESP32-C6 only, and the testing has focused on fundamental functionality. Currently, there are limited Rust wrappers available. Until all functionalities are wrapped, it's necessary to utilize the raw bindings for more advanced features.

We invite you to...

1. Comment on this issue with your suggestions and ideas.
2. Open Feature Requests: What new features would you like to see in esp-openthread?
3. Report Bugs: Are there any existing bugs or issues that need our attention?
4. Submit Documentation Issues: Any specific areas of the documentation that need improvement or clarification?

Please keep this discussion focused on future for esp-openthread. For any other topics, please open separate issues or pull requests.

[bjoernQ]

Some background: the original motivation to create this is to support rs-matter with Thread support. But rs-matter is currently missing BLE commissioning (which is a prerequisite to support Thread)

[thedevleon]

We have been using openthread with the Nordic nRF chips for some time now, but we would ultimately like to switch to the esp32c6.
As of right now, the following features are missing in our eyes to be feature equivalent to what we have right now (they are all present in the openthread SDK, but not wrapped yet AFAIK):

• Joiner role (https://openthread.io/reference/group/api-joiner) for commissioning into a thread network (with EUI64 support)
• NAT64 and DNS64 support (https://openthread.io/codelabs/openthread-border-router-nat64) -> to be able to talk to IPv4 targets on the internet
• OpenThread TCP support