Agreed but I think it’s better to use streams and deliver messages reliably and in order today, despite the extra effort. For instance, TLS is stateful. If you

Agreed but I think it’s better to use streams and deliver messages reliably and in order today, despite the extra effort. For instance, TLS is stateful. If you want to deliver unannounced (stateless) datagrams to a server, you’d technically be able to use the servers pubkey but you’d have to sacrifice forward secrecy. Making business logic with dropped packets and OOO delivery is also very difficult depending on domain. Personally I would like to see faster bootstrap and especially resumes of streams to eliminate handshake cost. For instance: - resume with last shared secret for 0rtt handshake (I believe Quic supports this) - allow the dialer to queue/send data before ack (this is an API-breaking change on sockets, but worthwhile imo - it makes socket FSM on app layer easier to use because it never needs to be nil