TRANS13 — separate client-side behavior issue

I can offer to write up a votable resolution proposal concerning the
client-side behavior issue (soley). The proposal would assume nothing about the
resolution of the absence-of-transaction-policy issue, and offer two variants
to choose from:

the caller can have a transaction when calling the non-transactional
object; no need to suspend/resume
around this call

(ii) force the programmer to call suspend/resume if he has a current
transaction when calling a non-transactional object

(iii) two possible client-side behaviors (enforce or do not enforce
suspend/resume when the caller has a transaction), selected through a
client-side policy)

This issue was addressed in the proposal for issue 3425