On Sat, Jun 30, 2012 at 6:03 PM, Gregg Vanderheiden <[email protected]>wrote:
> The problem here is that in emergency situations -- RTT becomes critical - > as in life saving. > Have it turned off all the time is fine. But the client software should > not say that it CAN'T do RTT when it is just that the user wants it to be > turned off. > I can see the situation happening -- my animation at http://www.realjabber.org/real_time_text_demo.html demonstrates a sample emergency call in XEP-0301. The user stops hitting Enter in the middle of the last message, so the whole message is never sent -- but the real-time text made it, so some critical information made it through. Obviously, client capabilities specific to NG911 contexts may be mandated by by the NG911 rules and not the specification itself -- so such clients might be encouraged to ignore the "SHOULD NOT" normative in Section 5, and transmit RTT anyway whenever "Emergency Mode" is turned on. Also, I've now modified Section 5 to leave the door open to alternative sender signalling of a desire to turn on RTT, even when there's no disco response. This will also allow RTT to proceed in extenuating circumstances, regardless of disco. Mark Rejhon
