RE: Useful real-time text reference

Interestingly, the current U.S. telecommunications regulations refer to IETF RFC 4103 for their real-time text requirement:
https://www.ecfr.gov/cgi-bin/text-idx?SID=ada7cebd65433a9e05c35426a2bc76b8&mc=true&node=pt47.3.67&rgn=div5
while also allowing for transcoding from other communications networks that use different protocols.

It would be interesting to know what standards are being used in Europe and elsewhere.

-----Original Message-----
From: Joshue O Connor <joconnor@w3.org>
Sent: Thursday, June 6, 2019 5:58 AM
To: White, Jason J <jjwhite@ets.org>; RQTF <public-rqtf@w3.org>
Subject: Re: Useful real-time text reference

On 05/06/2019 21:23, White, Jason J wrote:

> While searching for further references, I found the following - also from the IETF, and older than RFC 5194:
>
> "RFC 3351 - User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired Individuals"
> https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc3351&amp;data=02%7C01%7Cjjwhite%40ets.org%7Cf25d44e179a04f4bbb3e08d6ea657427%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636954118810489132&amp;sdata=Idd2uVGDXfr6aJmiGklwCN%2F6rC%2FaNPd26btauaTSxcE%3D&amp;reserved=0

That's useful Jason, thanks.

Josh

> I also found a general list of standards and documents related to real-time text and accessible telecommunications. The copyright date of the page is 2014, thus it isn't clear how up to date the references now are.
>
> https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.realtimetext.org%2Frtt_in_detail%2Fstandards&amp;data=02%7C01%7Cjjwhite%40ets.org%7Cf25d44e179a04f4bbb3e08d6ea657427%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636954118810499128&amp;sdata=KT0lH0g89%2FM8IWlu05gVbbnSnr%2Fo6RQKRA4VoXx5nAk%3D&amp;reserved=0
>
> From: White, Jason J
> Sent: Wednesday, May 22, 2019 3:48 PM
> To: RQTF <public-rqtf@w3.org>
> Subject: Useful real-time text reference
>
> This is probably the reference that Josh cited at the meeting:
> https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc5194&amp;data=02%7C01%7Cjjwhite%40ets.org%7Cf25d44e179a04f4bbb3e08d6ea657427%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636954118810499128&amp;sdata=mYtorrrX8BRl4LZxTlJxf7hSlxXfHwdVR7JnTKa7hHM%3D&amp;reserved=0
>
>
> ________________________________
>
> This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.
>
>
> Thank you for your compliance.
>
> ________________________________
>
--
Emerging Web Technology Specialist/A11y (WAI/W3C)


________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________

Received on Thursday, 6 June 2019 14:11:00 UTC