Re: [MEDIACTRL] ISSUE 17 - Control Framework - Transaction-Timeout

Works for me.

On Aug 4, 2010, at 9:47 AM, Chris Boulton wrote:

> As part of our IESG review the following has been identified:
> Discuss:
> > Transaction-Timeout: The maximum allowed time between a Control
> > Client or Server issuing a framework message and receiving a
> > corresponding response. The value for 'Transaction-Timeout' is 5
> > seconds.
> 
> ISSUE 17 - DISCUSS: As I understand it, Transaction-Timeout has two meanings. For
> clients, it's the *minimum* amount of time they need to wait for the
> server to respond. For the server, it's the amount of time after which
> they should let the client know that processing will take longer. The
> mechanism as described isn't very robust. First, 5 seconds is not
> sufficiently larger than some Internet RTTs, which may cause spurious
> transaction failures even under normal operating conditions. Second,
> clients and servers use the same value, which means that if there is
> any delay spike or congestion along the path, a spurious transaction
> failures will occur.
> 
> The Transaction-Timeout set to 5 seconds does not seem appropriate for the job.  Firstly we need to take realistic (internet)
> RTT time into consideration.  Proposal is that we assert a RTT time of 10 seconds for the mediactrl framework. Thoughts?
> 
> We also need to construct more robust timeout rules for client and server.  The proposal is that:
> 
> - client sets Transaction-Timeout to be 2*RTT on issuing a request.
> - server sets Transaction-Timeout to be 1*RTT on receiving a request.
> 
> Chris.
> 
> -- 
> Chris Boulton
> CTO & Co-founder
> NS-Technologies
> m: +44.7876.476681
> _______________________________________________
> MEDIACTRL mailing list
> MEDIACTRL@ietf.org
> https://www.ietf.org/mailman/listinfo/mediactrl
> Supplemental Web Site:
> http://www.standardstrack.com/ietf/mediactrl

Re: [MEDIACTRL] ISSUE 17 - Control Framework - Transaction-Timeout

Attachment: smime.p7s