PR035, PR009, PR020

["Durand, Jacques R." <JDurand@us.fujitsu.com>]

Proposal for these, concerning the wsrm core specification (complementary proposal from Chris is about additions in WS RM Policy)

 

Add a new 2.2 section (moving down former 2.2 -> 2.3, etc)

 

2.2 Delivery Assurances

 

The delivery assurances (DAs) alluded to at the beginning of section 2, and enabled by the reliable messaging protocol are defined below as AtLeastOnceDelivery, AtMostOnceDelivery, ExactlyOnceDelivery and InOrderDelivery. Their enforcement is communicated or advertised between parties in the form of policy assertions that are defined in WS-RM Policy specification. This specification does not require that these DAs be signaled between RM Source and RM Destination over the protocol described here. Users may choose to communicate these DAs via the protocol, e.g. using extensibility points.

AtLeastOnceDelivery: When sending a message under this delivery assurance (DA), one of the two following outcomes shall occur: either (1) the RMD has received the message and successfully delivered it to the AD, or (2) either the AS or the AD is made aware of a delivery failure. Note: it may happen that both (1) and (2) occur for a message. It is also possible that the message is delivered more than once.

AtMostOnceDelivery: When sent under this DA, a message shall not be delivered more than once by the RMD to the AD. Message duplicates are identified based on Sequence ID and Sequence number. Note: a message that is not delivered at all is compliant with this DA.

ExactlyOnceDelivery: This DA is equivalent to the combination of  AtLeastOnceDelivery and AtMostOnceDelivery DAs.

InOrderDelivery:  When sent under this DA, messages from the same sequence shall be delivered by the RMD in the same order they have been sent by the AS, i.e. submitted to the RMS. Note: the protocol provides ways to signal specific delivery behaviors regarding incomplete sequences (see IncompleteSequenceBehavior).

-Jacques