Detailed proposal to resolve Rel 113

[Tom Rutt <tom@coastin.com>]

DIR="LTR">

Detailed proposal to Resolve Issue Rel 113


Lines 526 thru 532 currently state:

“
If the RMP sending a Reliable Message does not receive an Acknowledgment 
for a sent message that has not yet expired, it MUST resend the same 
message with same Message Identifier to the receiver RMP until the 
sender gets an Acknowledgment message from the receiver, or until the 
number of resend attempts specified by the RetryMaxTimes agreement item 
is exhausted, whichever occurs first. The time interval between two 
retries is specified by the RetryTimeInterval agreement item. If the 
sender RMP fails to send the message (i.e., no Acknowledgment is 
received), the sender RMP MUST notify a delivery error.
“

This does not talk about fault conditions.

Proposed Change:

Change “Acknowledgement” to “Acknolwedgement or Fault” in the first 
sentence of the text quoted above.

Add the following paragraphs immediately after the exsting line 532:
"
The sending RMP MUST NOT send retries with a message ID, for which it 
received an rm-response with one of the following fault types:

    *

      an invalid message format fault code (table 18)

    *

      an unsupported feature fault code

    *

      a permanent processing faulure fault code

The RMP MUST NOT return an RM fault for a delivered messageID.

The RMP MUST NOT deliver a message which encounters an RM fault.
“

Add the following paragraph immediately after exsiting line 660:
“
The receiving RMP MUST NOT update its Group Termination Criterea using 
parameter values from a rm-request which encounters an RM fault.
“


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