[adamch]

This is interesting. But how would you use it? You'd need to open up a new type of socket (neither TCP nor UDP but nyxpsi) and everything along your network route would need to support it. So it wouldn't be useful with existing mobile networks (middle boxes won't speak the protocol) nor within the data center (because it's used for high packet loss situations). So what's the use case? Custom wireless networks with embedded devices?

[wmf]

It's using UDP.

[fragmede]

> middle boxes won't speak the protocol

Middle boxes only need to speak IP, which they do already, and not block nyxpsi packets (which they probably do).

[zamadatix]

You'll still run into trouble with anything wanting to allow everything but trying to do NAT. I'd hazard to guess this actually still uses UDP under the covers for that reason (but haven't bothered to verify). QUIC and HTTP/3 went that route for the same reason.

Edit: It does.

[wyager]

There's not really a sufficiently compelling reason to use anything except UDP for future protocols aiming to replace TCP