Re: [tcmtf] Using the concept of "latency budget" for TCM-TF

[Mirko Sužnjević <[e-mail]>]

Hello,
I think this is just the concept about which we talk in the draft. We got some tolerable latency or it can be called latency budget. Portions of that latency are consumed by the sources of latency. When the service has some latency "left" after all sources have taken their share the quality of the experience should not be degraded. We could rewrite it to have the common terms in the next iteration.
Cheers!
Mirko

From: tcmtf [mailto:[e-mail]] On Behalf Of Jose Saldana
Sent: Thursday, February 6, 2014 10:23 AM
To: [e-mail]
Cc: [e-mail]
Subject: [tcmtf] Using the concept of "latency budget" for TCM-TF

Hi all,

The report of the Workshop on Reducing Internet Latency (http://www.internetsociety.org/latency2013) talks about a very interesting concept: "latency budget":

"A latency budget is applicable to the application and is consumed by sources of latency."
"Latency budgets can be hard or soft and may be derived from biological or computational expectations."
"The application operates effectively only when the cost is kept within the budget."

Since TCM-TF savings require the addition of an small latency as a counterpart, perhaps we could say something like "if an amount of latency budget is available, a part of it can be consumed in multiplexing packets, thus providing bandwidth savings".

And some sentences of the draft about delay limits could even be rewritten accordingly: for example, instead of talking about "delay recommendations" in section 6, we could talk about "latency budget" for each application.

What do you think?

Best regards,

Jose