Filed this individual Internet-Draft yesterday as a solo submission.
The argument: existing proximity standards — Bluetooth Mesh, Wi-Fi Aware, Thread — each cover one radio, one domain. No open standard spans BLE, WiFi Direct, and LoRa simultaneously with per-device cryptographic identity for general-purpose communication. The gap is not technical. The gap is institutional.
I know Reticulum exists. Cited it in Section 3. I know LNMesh demonstrated Lightning payments over a WiFi/Bluetooth mesh in 2023. Cited that too.
Every element has prior art. What does not exist is the unified open standard with a CC0 commitment and certification pathway.
Looking for a technical co-author who has shipped an IETF protocol before, and an OpenWrt engineer for the reference implementation.
Is the gap accurately characterised — or does existing work already close it?
npukuk•1h ago
The argument: existing proximity standards — Bluetooth Mesh, Wi-Fi Aware, Thread — each cover one radio, one domain. No open standard spans BLE, WiFi Direct, and LoRa simultaneously with per-device cryptographic identity for general-purpose communication. The gap is not technical. The gap is institutional.
I know Reticulum exists. Cited it in Section 3. I know LNMesh demonstrated Lightning payments over a WiFi/Bluetooth mesh in 2023. Cited that too.
Every element has prior art. What does not exist is the unified open standard with a CC0 commitment and certification pathway.
Looking for a technical co-author who has shipped an IETF protocol before, and an OpenWrt engineer for the reference implementation.
Is the gap accurately characterised — or does existing work already close it?