Re: Proposed XMPP Extension: Jingle Synchronized Real-Time Text

--===============5653795375439533717==
Content-Type: multipart/alternative; boundary="000000000000aafdeb065344bb0c"

--000000000000aafdeb065344bb0c
Content-Type: text/plain; charset="UTF-8"

On Tue, 2 Jun 2026 at 10:57, Daniel Gultsch <[email protected]> wrote:

> Title: Jingle Synchronized Real-Time Text
> Abstract:
> This specification defines a Jingle application extension for
> negotiating real-time text as part of the same conversational session
> as audio and video.
>
> URL: https://xmpp.org/extensions/inbox/jingle-rtt-sync.html


This generally looks reasonable, and I support publication, but I'm
struggling to find the missing references.

T.140 over datachannel appears to be RFC 8865.

You'll also want XEP-0343 for WebRTC datachannel support in Jingle.

Finally, RFC 4103 updated by RFC 9071 does T.140 over RTP.

(In my view) these don't need to be in place prior to publication but I
thought they'd help others review.

--000000000000aafdeb065344bb0c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, 2 Jun 2=
026 at 10:57, Daniel Gultsch &lt;<a href=3D"mailto:[email protected]">danie=
[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex">Title: Jingle Synchronized Real-Time Text<br>
Abstract:<br>
This specification defines a Jingle application extension for<br>
negotiating real-time text as part of the same conversational session<br>
as audio and video.<br>
<br>
URL: <a href=3D"https://xmpp.org/extensions/inbox/jingle-rtt-sync.html" rel=
=3D"noreferrer" target=3D"_blank">https://xmpp.org/extensions/inbox/jingle-=
rtt-sync.html</a></blockquote><div><br></div><div>This generally looks reas=
onable, and I support publication, but I&#39;m struggling to find the missi=
ng references.</div><div><br></div><div>T.140 over datachannel appears to b=
e RFC 8865.</div><div><br></div><div>You&#39;ll also want XEP-0343 for WebR=
TC datachannel support in Jingle.</div><div><br></div><div>Finally, RFC 410=
3 updated by RFC 9071 does T.140 over RTP.</div><div><br></div><div>(In my =
view) these don&#39;t need to be in place prior to publication but I though=
t they&#39;d help others review.</div></div></div>

--000000000000aafdeb065344bb0c--

--===============5653795375439533717==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Standards mailing list -- [email protected]
To unsubscribe send an email to [email protected]

--===============5653795375439533717==--