Hi, just wondering if you’d noticed Google’s QUIC protocol? It looks ideal between the imp and the imp server for reducing both the number packets and the number of round trips, when micro-joules matter.
It certainly can help in connection setup, but it’s more about performance than power… it’s intended for use when fetching web pages which are large and generally have a lot of connections - hence why it includes HTTP2.
For us, we have a much simpler pipe. There are certainly optimizations we can do even with our current TCP+TLS setup, but the power savings are minimal - the WiFi receiver takes significant power no matter what we’re sending.