Rev "d" of Rel52, 57

Rel 57: (revision d) Ordering and Missing Message Behavior
---------------------------------------

Proposal:

[notes from author: 
- We also use GroupMaxIdleTime -if specified- for terminating an out-of-order sequence.
- Discarding out-of-order messages of a group, and more generally terminating a 
group, does not mean yet the removal of the group state, as message IDs may still 
be needed for duplicate checks. See Rel52 for this.
- The term "delivery" below has been precisely defined earlier.]


On the Receiver side, as soon as either:
(1) the earliest ExpiryTime of pending (stored) out-of-order messages has expired, or 
(2) GroupMaxIdleTime has been specified, and has expired,
all the pending and future out-of-order messages MUST NOT be delivered. 
The RMP MUST terminate the out-of-order group as early as convenient after this date, 
and out-of-order messages must be discarded. 

On the Sender side, the RMP MUST terminate an ordered group as early as possible after
one of these events occurs, whichever comes first:
(1) a message for the group has not been acknowledged after all retries have
been exhausted, plus a buffer time (e.g. retryinterval).
(2) a message supposed to be sent or resent, has expired, and therefore will not
be sent. 

NOTE: On the Receiver side, out-of-order messages, although well-received, 
will not be delivered and acknowledged before the sequence is complete, which may 
trigger unncessary resending from the Sender. 
The Sender MAY decide to NOT systematically resend a non-acknowledged message, 
in case a previous message in the group has not yet been acknowledged.