This method is called by SAF to actually deliver a received sequence
message into the RM reliability queue. Note, SAF *DOES NOT* elliminate
dups on its own, so we could get this call more than once for a given
sequence id / seq num combination. The actual dup detection will be done
by RM's reliability queue so those messages won't actually get processed
more than once. However, we must be careful when trying to map request
seq num to response seq num, and detect/ignore a dup instead of redoing
a mapping we've already done on a prior message.
Historically speaking, receiving-side SAF is really only used by RM, and
the SAF team felt it was better to allow the RM queue (with built-in dup
ellimination) handle dups instead of reimplementing it in SAF.
Check to see if this SAFEndpoint is available
TODO firstname.lastname@example.org -- this there to help AT_MOST_ONCE QOS to be a better
QOS. We can drop messages on the floor, but if we know that the destination
is not available then we should try to deliver the message at all and thus
not drop it on the floor