NEW ISSUE Editorial, Sec 3.5 Request Acknowledgement text assumesSequence is known

["Bob Freund-Hitachi" <bob.freund@hitachisoftware.com>]

In WD 15 Section 3.5 “Request Acknowledgement” starting on line 600 states

 

“An RM Destination that receives a message that contains an AckRequested header block MUST send a

message containing a SequenceAcknowledgement header block to the AcksTo endpoint reference

(see Section 3.1).”

 

If the RM Destination is unaware of the Sequence, such a response is impossible.

 

Proposal:

New Text:

 

“An RM Destination that receives a message that contains an AckRequested header block for a Sequence known to it and not terminated MUST send a

message containing a SequenceAcknowledgement header block to the AcksTo endpoint reference

(see Section 3.1).  If the Sequence identified in the AckRequested header block is unknown or has been terminated, then the RM Destination SHALL send an UnknownSequence fault (see Section 4.3)”

 

Impact to state tables:

I assumed this to be the intended behavior in the submitted version of the state tables sent today.