On Tue, Jun 26, 2012 at 11:19 PM, Peter Saint-Andre <[email protected]>wrote:
> On 6/26/12 6:08 PM, Mark Rejhon wrote: > > On 2012-06-26 7:38 PM, "Kurt Zeilenga" <[email protected]> wrote: > >> On Jun 26, 2012, at 4:30 PM, Kurt Zeilenga wrote: > >> Regarding stanza level encryption, if any encryption is used for any > >> message stanza to a particular (full) jid, it should be used for all. > >> and as this likely is "too expensive" in a number of ways, likely > >> better to disable RTT when stanza level encryption is enabled. > >> > > > > Understandable concern, but XEP-0301 is also an accessibility concern. > > Deaf people like me, who cannot use the telephone -- should be able to > > have every opportunity to initiate XEP-0301 if the software supports it. > > > > Forcing XEP-0301 supported software to turn off RTT by a spec > > requirement rather than user preference, is tantamount to putting a > > call-block on all incoming calls from deaf.... > > > > That would be a very discriminatory practice, would you think! > > > > Computers, networks, encryption is gradually becoming faster, and even > > stanza-level encryption for RTT is still is less 'expensive' than a > > video call, or an in-band file transfer. > > I don't think Kurt was suggesting that the spec mandate turning off RTT > if encryption is supported, but that it might be a wise thing for > implementations to do in multi-resource scenarios. > Just FYI, Total Conversation used by Reach-112 ( http://www.reach112.eu/view/en/project/tc.html) uses audio, video and real-time text simultaneously. It is also described in ITU-T Rec. F.703 "Multimedia Conversational Services". XEP-0301 is not required to be used with audio or video, but it certainly can be. Thus, I don't recommend disabling RTT when audio and video resources are used. Mark Rejhon
