Consider renaming T99 to Tmax?

[pac-work]

In "Timing Model Terms and Definitions" of the draft you define T99 to mean the 99.9 percentile. That is very confusing when the rest of the industry would think that T99 meant the 99 percentile, not 99.9. Also using the 99.9 percentile seems quite a low bar, you could be late with over 200 frames pr hour and still be within spec (assuming 60fps).

[jmailhot]

we chose T99 to indicate that it was statistically possible (and indeed likely over the course of a very long session) for a frame to be later - and by implication that codebases ought to deal with that in a non-disastrous manner. calling it Tmax tends to send the other implication, that if the frame is late, then the code is allowed to fail (GIGO philosophy).

[pac-work]

Thank you for clarification, we see that the name like Tmax could be misleading from a different angle than T99 and we understand your view on this. The meaning of the value is well defined in the document, so from the point of view of trying to create an compliant implementation, all is OK.