On Wed, Sep 20, 2023 at 9:55 AM Jason Gunthorpe <jgg@xxxxxxxxxx> wrote: > And what happens if one of your non-standard nodes points its IWCM at > an IP that is actually running iWarp? IWCM takes an IP and a port, creates a socket and listens or connects to that endpoint. It's not like we are hijacking, say, a dedicated RoCE UDP/4791 port and using it for something else. While the user may try to connect his app to an arbitrary iWarp listener, it would fail to negotiate. But that could happen even without us. Similarly our protocol would fail a negotiation if something else tries to connect to our listening endpoint. I think the name causes all this confusion. Thanks.
