ebxml-msg — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
RE: Delivery Receipt,NRR and MSG/CPPA/BPSS (mis-)alignment andthelayering mishmash (was jumbledinto: reliable messaging - hop by hop)
Arvola, The main function of RM is to provide a receipt to the sender, either the previous hop or the original sender. If I send using NRR isn't that by definition RM since there is a receipt (end-to-end RM)? I don't understand how we can have NRR and NOT RM? Seems like NRR is automatically RM (yes I know RM can also mean idempotence...). If you mean we can have end-to-end NRR/RM without hop-to-hop RM then I agree with you. It seems to me that basic security requires NRR. If we don't do NRR, how can the sender be assured that the receipt is for the original message? Just having RefToMessageId in the Delivery Receipt message does not assure that the message arrived without change or that the receipt isn't mistakenly for another message but with the wrong RefToMessageId. With NRR there is an absolute tie between the Receipt and the original message and there is assurance of who sent the DR -- you have to have both. What good is a DR without NRR, there would be no legal standing. Even with NRR there can be argument (Dale's wiggle room) but we do the best we can. Regards, David Fischer Drummond Group.
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]