[ofa-general] [RFP] support for iWARP requirement - active connect side MUST send first FPDU

[Sean Hefty]

> If you think customers are willing to work around this restriction then 
> by all means leave the architecture alone and simply document the rdma 
> API's. I would think that this put's iWARP vendors at a disadvantage.

I think a connection service can hide this restriction, similar to how 
some MPI implementations handle this today.  The solution I mentioned 
was to send a message over the QP from the active side.  This leaves the 
existing architecture unchanged.