Doug:
Thanks for the clarification why SyncReply belongs in 'Core Functionality'
rather than in 'Additional Features'.
I have two related questions:
1. Is syncReply assumed one of those parameters that are perMessage? I don't
think that the CPP/A team is aware of such an assumption.
2. If not, is the element mandatory when it is already specified in the CPA?
When no intermediaries are involved, I would have expected that a syncReply
specification in the CPA would imply that sync reply is to be used
regardless of the presence or absence of a SyncReply element in the message
header. What triggers the sender to include a SyncReply element in the first
place?
Thanks,
-Arvola