ebxml-msg — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
RE: FW: T2, Proposed solution for ... Re: SyncReplyandReliableMessagingMethod in QualityOfServiceInfo
Chris, Does this mean communications between two Trading Partners is ALWAYS RM or NEVER RM? We've already decided DeliveryChannel is address specific so there cannot be two DeliveryChannels between one set of addresses. Does this mean the RM settings are fixed and never changing between these two Trading Partners? Doesn't sound very flexible. Some documents will be critical and thus require RM while some do not. How do we accommodate this? Chris wrote:
How does this work if the sending MSH knows nothing of intermediaries?
Are you suggesting that the Via element is now REQUIRED on all messages? In the case of single-hop, no retryCount is necessary. I have to agree though, how does the sender know this is single-hop? Since there is always the potential of transparent IMs, shouldn't we assume that nothing is single-hop and therefore Via is ALWAYS required for RM? On the issue of an MSH knowing it is an IM, this decision has to be made at the MSH layer since security is an MSH layer function (see figure 6-1). If you wait, the MSH will try to validate the signature (or decrypt) and fail thus sending an error message back to the From Party. Again, message packaging and security are in the MSH, not the Application*. The MSH MUST know it is an IM. Packaging and forwarding are MSH functions, not application. *A different set of criteria might apply to an intra-company mailroom situation. Regards, David Fischer Drummond Group.
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]