[rtcweb] WG last call comments on use-case and requirement document, “Real-time text”

[Stefan Håkansson LK <[e-mail]>]

This relates to the comments to the WG last call of the use-cases and 
requirements document [1].

The topic in this mail is Real-time text. This was discussed in [2] - 
[8] (i hope I found all the relevant mails, please correct me if I 
missed any).

My reading of the discussion is that although there was some interest in 
the use-case it was shown that it can be implemented on top of the 
existing WebRTC environment and thus does not necessary drive any new 
requirements. The counter argument was the need for common
interoperability for real-time text rather than silos, especially in the 
context of emergency services. However as there no consensus on any 
special requirements regarding emergency services it doesn't appear that 
real-time text support requires that either.

This can be summarized to that there was no consensus for additional 
requirements and the basic functionality can clearly be implemented 
using JS and suitable data transport,, and there is no need to add a 
specific use-case for real-time text.

Another way to view this is that the real-time text use-case is a 
"telephony terminal" use-case with the codec being something like T.140, 
which would narrow the discussion to a codec discussion.

Anyway, with the current input I don’t think there is support to add a 
new use-case on “Real-time text”.

Stefan


[1] http://www.ietf.org/mail-archive/web/rtcweb/current/msg06136.html

[2] http://www.ietf.org/mail-archive/web/rtcweb/current/msg06160.html
[3] http://www.ietf.org/mail-archive/web/rtcweb/current/msg06161.html
[4] http://www.ietf.org/mail-archive/web/rtcweb/current/msg06202.html
[5] http://www.ietf.org/mail-archive/web/rtcweb/current/msg06212.html
[6] http://www.ietf.org/mail-archive/web/rtcweb/current/msg06213.html
[7] http://www.ietf.org/mail-archive/web/rtcweb/current/msg06224.html
[8] http://www.ietf.org/mail-archive/web/rtcweb/current/msg06228.html