But I'm confused by your statement that you want the license not to mention patents because you want to leave patent issues to the lawyers. The license isn't software code, it's legal code--it's what the lawyers are arguing about!
If the license doesn't mention patents (and doesn't imply a particular grant of patent rights, which like I said is an open issue), then you haven't chosen "nothing." You've chosen the default: the patent holder retains all rights.
It seems that any variation either hurts my defense or comes off as aggressive (which is what happened to facebook).
In a hypothetical situation where the patent language matters, it's total war. Multiple concurrent lawsuits in opposite directions, ITC injunction requests, etc. Maximum pain to make the opponent capitulate. None of these patents are really valid anyway, it's either math or implementation detail. There's no reason or logic here.
Better to make no statement, leave the default unsaid, and stick your head in the sand, it may keep you under the radar of involvement.
As an illustrative example of what can happen when some third-party profiteers file for patents on your software while re-selling it themselves, read up on the JMRI project's legal troubles:
http://jmri.sourceforge.net/k/summary.shtml http://lwn.net/Articles/181261/ http://lwn.net/Articles/294066/
That's why my preference is for licenses that explicitly deal with patents: ALv2, MPLv2, (L)GPLv3.
Let the lawyers argue about the patents; I don't want to accidentally hobble the ones on my side or arm the ones on the other side, I don't want to accidentally harm other open-source contributors, I'd rather not be involved at all.
(In the BSD vs GPL debate I'm pro-GPL, but not GPLv3, because it involves the patents...)