[Standards] Call for Experience: Advancement of XEP-0301 (In-Band Real Time Text) to Final

Mark Rejhon mark at realjabber.org
Fri Oct 23 03:33:36 UTC 2015


On Thu, Oct 22, 2015 at 4:03 PM, Peter Saint-Andre - &yet <peter at andyet.net>
wrote:

> [sending on behalf of the XSF's Editor Team]
>
> At its meeting on October 21, 2015, the XMPP Council agreed to issue a
> "Call for Experience" regarding XEP-0301 (In-Band Real Time Text), in
> preparation for perhaps advancing this specification from Draft to Final in
> the XSF's standards process. To help the Council decide whether this XEP is
> ready to advance to a status of Final, the Council would like to gather the
> following information:
>

Fellow members here will observe this is fairly quick for a CfE. Some
background info:

We decided to request CfE rather early, to get comments necessary to
improve the standard as much as possible (if any changes needed).  No
protocol change is anticipated; just simple errata, editorial and
implementation detail clarifications.

1 -- developer experience indicates XEP-0301 is well-engineered (despite
over-engineering);
2 -- our annual review of standard repeatedly show virtually no need for
changes;
3 -- there is a regulatory incentive
4 -- this october 2015, there is a sudden increase in RTT interest

Access-Board.gov
http://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/proposed-rule/v-major-issues
"Yet despite its potential benefits, the Board cannot incorporate XEP-0301
until it becomes a final standard. However, should the XEP-0301 standard be
finalized before publication of the final rule, the Board plans to
incorporate it by reference as an alternative technology to support
transmission of RTT when interoperating with VoIP products or systems using
XMPP. RFC 4103 would, in any event, be retained for ICT interoperating with
VoIP products or systems using SIP technology."

FCC Grants AT&T waiver to introduce real-time text to replace TTY:
http://www.commlawmonitor.com/2015/10/articles/disabilities-access/fcc-grants-att-waiver-request-to-use-real-time-text-for-hearing-impaired-communications/
This will be RFC4103, but will need to interop with XEP-0301.

AT&T plan is for 2017:
https://www.fcc.gov/document/tty-rtt-transition-waiver-att

AT&T mentions XEP-0301 in their RTT presentation:
http://g3ict.org/design/js/tinymce/filemanager/userfiles/File/2015%20Summit/Aaron%20Bangor_Standards.pdf

I should note I am not employed by AT&T and have no financial benefit from
this.However, I want to be sure that XEP-0301 is absolutely as mature as
possible in these short timescales we're asking, preferably far before
2017, given implementation timescales and the sudden increase in RTT
interest in the telecom world.

Also, proprietary implementations of XEP-0301-like real-time text already
exist. http://www.beammessenger.com/ as an example. Having a clear standard
that is promoted to FINAL sooner than one may expect is normal for certain
XSF standard, would encourage more implementers to choose XMPP for
messaging and, consequently, XEP-0301.

Fortunately, developer experience on 0301 has been overall generally
more-positive-than-expected (considering size of standard); and we look
forward to hearing more CfE feeback.

Thanks,
Mark Rejhon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20151022/23a3b584/attachment-0001.html>


More information about the Standards mailing list