Re: T2 Clarify TimeToLive

[Arvola Chan <arvola@tibco.com>]

David:

I agree with you that we need to clarify in the spec how TimeToLive
should be set for a given message. For reliably delivered messages,
I don't think we want to reset the the TimeToLive on every retry. It just
incurs unnecessary signature recomputation overhead. I would suggest setting
TimeToLive to current time (for the initial attempt) + (retry + 1) *
retryInterval. This must also be less than the receiver MSH's persist
duration.

For messages delivered by BestEffort, the TimeToLive can either be
omitted, or perhaps set to the current time plus the
RequestingBusinessActivity's or RespondingBusinessActivity's
timeToReceiveAcknowledgment.

Cheers,
-Arvola

-----Original Message-----
From: David Fischer <david@drummondgroup.com>
To: ebXML Msg <ebxml-msg@lists.oasis-open.org>
Date: Tuesday, September 11, 2001 4:52 PM
Subject: T2 Clarify TimeToLive


I don't know if this is a problem or not.  TimeToLive is a time, not an
interval, and should probably be set to current time plus 1/2 RetryInterval
(half of the round trip from sender to receiver back to sender).  Won't this
have to be recalculated each retry?  Won't this invalidate the signature?

Maybe I'm getting the correct value of TimeToLive wrong?  What in the world
should this be?  Maybe this is more along the lines of "This PO is valid for
30
days" so this value should be set to current time plus 30 days?  In any
case, we
probably need to clarify the spec.

Regards,

David Fischer
Drummond Group.


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>