NEW ISSUE: CloseSequenceResponse and Acks

[Doug Davis <dug@us.ibm.com>]

Title: CloseSequenceResponse and Acks

Description:
Using the CloseSequence operation a RMS will be able to get the true final
accounting of the ACKs for a sequence - sort of.  There is one case
that could be problematic.  Let's say that the CreateSequence operation
is given a bad AcksTo EPR.  In this case no Acks will ever be received
by the RMS - and this could be the reason for it closing the sequence.
 However, if all ACKs are always sent to the AcksTo EPR then the RMS
will have no choice but to eventually Terminate the sequence (or wait for
it to timeout) without ever getting the true final accounting of Acks.
 This would leave the RMS and RMD with a very different view of the
state of the sequence.

Justification:
See above.

Target: wsrm spec

Type: design

Proposal:
To solve this I'd like to require that the CloseSequenceResponse message
include the "final" Ack.

So, using:
http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/14548/wsrm-1.1-spec-wd-03.pdf

Replace the text on line 608:
  Upon receipt of this message the RM Destination
MUST send a
  SequenceAcknowledgement to the RM Source.
With:
  Upon receipt of this message the RM Destination
MUST send a
  SequenceAcknowledgement to the RM Source in
the 
  CloseSequenceResponse message.

Related issues: i019, i028