A client supporting voice and RTT must hand RTT input to its network within 500 ms of the smallest reliably composed unit of entry (a character, a predicted word or a recognised phrase) becoming available, network delay excluded. Under 1 second from key press to display at the other client is deemed to meet it; 300 ms or less feels smoother.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.