Need to rethink semantics of duplicate elimination behaviour

[Tom Rutt <tom@coastin.com>]

Based on our current thinking, we are not sending an ack until the 
message is actually delivered.

Thus in the ordered delivery held waiting for prior message state, an 
RMP may receive several
retransmits of that held, and thus not acknowledged message.

In such a case, the receiving rmp should respond to sending rmp
regarding its receipt of the duplicate message with an appropirate 
DuplicateMessage fault.


Please correct me if I am wrong, but I think we need to clean up the 
semantics of this from what is in the current draft.

Tom Rutt

-- 
----------------------------------------------------
Tom Rutt		email: tom@coastin.com; trutt@fsw.fujitsu.com
Tel: +1 732 801 5744          Fax: +1 732 774 5133