← Prev in month ← Prev in thread
Next in thread → Next in month →

NEW ISSUE: Editorial (maybe) RMS MessageNumberRollover behavior unclear

From
Bob Freund-Hitachi <>
Date
2006-06-26T22:54:14+00:00
ID
Thread
NEW ISSUE: Editorial (maybe) RMS MessageNumberRollover behavior unclear
In the June 26 version of WD 15 in Section 3.4 “Sequences”
starting at line 581 states

 

“If the message
number exceeds the internal limitations of an RM Source or RM Destination or
reaches the

maximum value of
9,223,372,036,854,775,807 the RM Source or Destination MUST generate a

MessageNumberRollover fault. In
this case the RM Destination should continue to accept , and the RM

Source should continue to
retransmit,undelivered messages until the Sequence is closed or terminated.”

 

1) It is unclear under what
circumstances the RM Source generates a MessageNumberRollover fault

 

Should the RM Source generate an
unTransmitted fault if a message is Sent that exceeds the RM Source’s
internal limitation?

Should the RM Source transmit a
fault if a message is Sent that exceeds the RM Source’s internal
limitation?  If so, what should the RM Destination do with it?

Should the RM Source generate a MessageNumberRollover fault at all?

 

2) Assuming that the RM
Destination Transmits a MessageNumberRollover fault upon receipt of a message
with a MessageNumber that exceeds its internal limitations or the big number
cited, whichever happens first, what mechanism is used by the RM Source to
close or terminate the sequence?

 

Proposal:

New Text:

 

“If the message
number exceeds the internal limitations of an RM Destination or reaches the

maximum value of
9,223,372,036,854,775,807 the RM Destination MUST Transmit a

MessageNumberRollover fault. The
RM Destination should continue to accept, and the RM

Source should continue to
retransmit, unacknowledged messages until the Sequence is closed or terminated.

 

“If the message
number exceeds the internal limitations of an RM Source or reaches the

maximum value of
9,223,372,036,854,775,807 the RM Source MUST generate a

MessageNumberRollover fault. The
AS SHOULD Send no further messages.  The RM Source should operate normally
and the state of the Sequence is unchanged.

 

This proposal assumes that some coordination between the AS
and the RM Source will exist that will determine the timing of Sequence closure.
← Prev in month ← Prev in thread
Next in thread → Next in month →