OTS11 — Policy split (OTSPolicy & InvocationPolicy)

Ram, Tom, all,

My main concern regarding the introduction of these two policies
is interoperability and source-code portability between
"OTS 1.1 + messaging updates" and the new OTS 1.2 revision we're
working on.

"OTS 1.1 + messaging updates" is a real adopted spec, not a working
draft. The (adopted) messaging spec refers to it. And I know at least
one shipping implementation of this OTS revision.

So far each new OTS revision (including "OTS 1.1 + messaging updates")
has addressed interoperability with earlier revisions; I think
that it would not be wise to adopt a proposal that does not address
this concern.

Also, the question asked by issue #3425 is "what shall I do when on
the client-side I get an IOR with no transaction policy component?".
Does the introduction of these new policies really help answering
this question? Maybe treating this as a separate issue would help
solve issue #3425.