RFC: Should intr/soft NFSv4 mounts be disabled?

Hi,

NFSv4 mounts using the "soft" and/or "intr" mount options
have never functioned correctly.  This is noted in the BUGS
section of "man mount_nfs" and commit c0d14b0220ae
added the generation of a warning message when such
a mount is done. The breakage can occur when the server
is slow/overloaded or network partitioned such that the RPC
reply is not received for over 1 second, resulting in the RPC
attempt to fail without the RPC reply being processed.

Breakage of the protocol has become more frequent for
NFSv4.1/4.2 mounts since, when a syscall returns before
the RPC reply is processed, it leaves the session slot for the
RPC non-usable.  When all slots are non-usable, the mount
is hung.

During review of commit c0d14b0220ae, emaste@ asked if
NFSv4 mounts using "soft" and/or "intr" should actually
be disabled, so I am now asking others for their opinion
on this? (Doing so will cause many extant mounts in fstab(5)
to fail.)

Thanks for any comments, rick