Section 3.2.2: Clarify meaning of "low latency"

[aboba]

Partial fix for #103

---

Preview | Diff

[steely-glint]

I welcome the improved clarity here, but I think perhaps <1sec is too high. If you look at auctions and betting I think they need ~500ms - they also require a 'fairness' e.g. no-one is more than 3 frames behind anyone else. Can we include that here ?

[aboba]

@steely-glint You make a good point. Section 3.2.2 is mixing "low latency" use cases (< 1 second) and "ultra-low latency" (e.g. auctions and betting), for which the glass-glass latency requirements will be more stringent. I think we need to describe both of these uses and the differences between them. For example, requirements N13 and N16 may be relevant to "low latency" but not to "ultra low latency" where requirement N39 will come into play.

I have revised the PR to cover both scenarios.

[dontcallmedom-bot]

This issue was discussed in WebRTC July 2023 meeting – (PR #121: Section 3.2.2: Clarify meaning of “low latency” (Bernard))

[aboba]

This use case was originally focused on auctions, which have very stringent latency requirements. I have submitted a new PR #123 to clarify that this use case requires "ultra low latency" (e.g. < 500 ms). These changes distinguish this use case from fanout use cases that have a much higher latency budget.