Update and proposal for i021

Update (based on other recent issues resolved) and formal proposal for i021:

Description:

It is not clear whether an RM policy attached to a WSDL only applies to inbound sequences or to outbound sequences as well. Although a policy clearly identifies two roles: RMS and RMD, it does no say in which role it applies to the subject endpoint. Last sentence of Section 2.4 in RM-Policy V0.2 says that an RM policy MUST apply to all messages in a binding (when associated to binding). That means applying equally (same AI, max number) to both in and out messages of an operation of type request-response, and to sequences that contain these messages.

Justification:

Imposing the same RM policy to inbound sequences and outbound sequences is clearly is not desirable (and did not seem to be the original intent): because of possible conflicts with another RM policy on the other side, and because of forcing the same policy in a symmetrical way between two RM nodes is not appropriate. The implicit intent of attaching an RM policy to a WSDL, is to apply the policy to the Web service instance acting in a Destination role, i.e. to inbound messages and sequences, not as a Source role, i.e. not to outbound messages and sequences. That would be controlled by another policy on the receiving side of outbound messages.

Resorting to applying RM policy at message binding level to resolve this, is not a good option: that would create all sorts of complications.

Target: policy

Proposal:

Add after L148: "When attaching an RM policy with endpoint policy subject, the RM policy applies to the endpoint acting in the destination role."

L182: replace: "...specifically indicating that WS-ReliableMessaging must be used over all the messages in

the binding."

with:

"...specifically indicating that WS-ReliableMessaging must be used over all inbound messages in

the binding."

ws-rx message