On 2/2/2015 12:48 PM, Michael Welzl wrote:
So, in summary, yes, an API from transport to the service layer should have an indication of latency, but this is a very complex,*bidirectional* interface. So other than saying that this should be addressed in the future, anything said now will be at best woefully incomplete, and at worst, wrong.
>
I’m for keeping this first document correct and complete.
In that case, I suggest that latency issues be listed under "TBD". The only way to deal with them currently is via interfaces that describe HOW an existing mechanism is to be configured, not WHAT the goal of that configuration is.
Joe _______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
