Should we configure PFC for iWARP?

Simple question. Our server guys are experimenting with standing up an S2D Cluster (Hyper-V HCI) and have chosen for the network Chelsio/iWARP.

I did some reading, and found that iWARP uses TCP, and then the network switching environment shouldn't really care about it, since it just uses the native features of TCP to handle congestion and windowing, etc.. (in other words, it should not require special configuration like PFC on our switches for this to work)

However, our server guys have asked us to configure "Data Center Bridging" on our switches, saying it is required for this deployment. I did some reading and THINK they are talking about Priority Flow Control (they don't know specifically what they need, I'm afraid, as they're following a guide they found that mentions vaguely "You'll need data center bridging configured on your network switches" (yes that's really all it says on the matter. And that one vague statement is enough for them to put in a service request for us to "Configure Data Center Bridging")

For me, PFC makes sense for RoCE, but not really for iWarp.

Any thoughts on the matter? I've also never configured PFC before, and it's for Juniper QFX switches. So there'd be a bit of a learning curve. From what I've read, it seems like it may be as easy as one set command to just turn PFC "on" for the interface, but on the other hand, there's a whole book work of nerd knobs and other auxiliary configuration that could be considered too. I'm also not a big fan of blindly turning a feature on that we don't fully understand, that they may not even need.. just because some blogger said to do it.

Yes I'll go ahead and say it for you guys, this is really a "don't know what's going on, need a consultant" situation, unfortunately it's not an option.

Any advice? Thanks!