NOTE 1 of definition of real time text does not match the 6.2.4 requirement
NOTE 1 of the definition of real time text in version 3.2.1 and in current draft 2024-01-23 is not correct. With the current wording it seems that the time 500 ms in the NOTE should be changed to 1 second. However, other solutions may be searched to explain better what RTT is. The current wording is: "NOTE 1: Users will perceive communication as continuous if the delay between text being created by the sender and received by the recipient is less than 500 ms. However, the actual delay will be dependent on the communication network."
If I understand right that "text being created" means text being provided for sending, and from that moment the current wording of 6.2.4 allows the real transmission from the RTT capable equipment where the text is created to be allowed to occur 500 ms later. That leaves 0 ms for network transmission, which is not logical.
The real user requirement documented in ITU-T F.700 for good RTT, is 1 second from creation to presentation. A simple change would be to align NOTE 1 with that requirement and change 500 ms to 1 s.
But experience tells that readers misread the definition anyway and do not understand that text shall be sent while it is created. I have not understood how the word "continuous" helps the definition, but since NOTE1 is intended to explain that, we should try to make the real time nature of RTT clear from the wording of NOTE 1.
A change should be done in alignment with possible changes in 6.2.4 for easier testing.