<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Times, sans-serif; ">
<div>More information on the transition from TTY, from the FCC.</div>
<div><br>
</div>
<div>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); ">On April 28, 2016, the FCC adopted a Notice of Proposed Rulemaking (Notice) to seek comment on proposals to replace FCC rules requiring support for TTY technology with rules requiring support for real-time text (RTT)
technology. The Notice is designed to ensure that millions of Americans who are deaf, hard of hearing, speech disabled, and deaf-blind who rely on text-based communications are able to access communication over Internet Protocol (IP) networks and services.
RTT allows individuals with and without disabilities to communicate directly with one another, using text on a voice line without the need to buy a stand-alone device like a TTY. <o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); "> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); ">Some of the issues in the Notice include:<o:p></o:p></span></p>
<ul type="disc" style="margin-bottom: 0in; font-family: Times; font-size: medium; margin-top: 0in; ">
<li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">
Proposed requirements for interoperability (so that any RTT user can connect to any other user, over any covered provider or device used by either party to the call);<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">
A proposed requirement for RTT communications to be backward compatible with TTYs for a period of time, so consumers who still use TTYs can communicate with RTT users;<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">
Whether to require specific features (e.g., conference calling, access to 911, the ability to call and be called using 10 digit numbers) so people with disabilities have accessible and effective text-based communications service, and<o:p></o:p></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">
A proposed deadline of December 31, 2017 for larger wireless service providers (and a request for comment about an appropriate timeline for smaller providers).<o:p></o:p></li></ul>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); "> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); ">We will announce the public comment due dates for the NPRM when these become available. <o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); "> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); ">Links to the Press Release:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); ">Weblink: <a href="https://www.fcc.gov/document/fcc-adopts-real-time-text-proposed-rulemaking" style="color: purple; ">https://www.fcc.gov/document/fcc-adopts-real-time-text-proposed-rulemaking</a><o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); ">Word: <a href="https://apps.fcc.gov/edocs_public/attachmatch/DOC-339100A1.doc" style="color: purple; ">https://apps.fcc.gov/edocs_public/attachmatch/DOC-339100A1.doc</a><o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); ">PDF: <a href="http://transition.fcc.gov/Daily_Releases/Daily_Business/2016/db0428/DOC-339100A1.pdf" style="color: purple; ">http://transition.fcc.gov/Daily_Releases/Daily_Business/2016/db0428/DOC-339100A1.pdf</a><o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); ">Text: <a href="https://apps.fcc.gov/edocs_public/attachmatch/DOC-339100A1.txt" style="color: purple; ">https://apps.fcc.gov/edocs_public/attachmatch/DOC-339100A1.txt</a><o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); "> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); ">Links to the Notice:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); ">Weblink: <a href="https://www.fcc.gov/document/real-time-text-nprm" style="color: purple; ">https://www.fcc.gov/document/real-time-text-nprm</a><o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); ">Word: <a href="https://apps.fcc.gov/edocs_public/attachmatch/FCC-16-53A1.docx" style="color: purple; ">https://apps.fcc.gov/edocs_public/attachmatch/FCC-16-53A1.docx</a><o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); ">PDF: <a href="https://apps.fcc.gov/edocs_public/attachmatch/FCC-16-53A1.pdf" style="color: purple; ">https://apps.fcc.gov/edocs_public/attachmatch/FCC-16-53A1.pdf</a><o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); ">Text: <a href="https://apps.fcc.gov/edocs_public/attachmatch/FCC-16-53A1.txt" style="color: purple; ">https://apps.fcc.gov/edocs_public/attachmatch/FCC-16-53A1.txt</a><o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); "> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); ">For more information about RTT, please contact Suzy Rosen Singleton at <a href="mailto:Suzanne.Singleton@fcc.gov" style="color: purple; ">Suzanne.Singleton@fcc.gov</a>.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style="color: rgb(31, 73, 125); "> </span></p>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Kathy Cahill <<a href="mailto:kcahill@mit.edu">kcahill@mit.edu</a>><br>
<span style="font-weight:bold">Reply-To: </span>Access Technology Higher Education Network <<a href="mailto:athen-list@u.washington.edu">athen-list@u.washington.edu</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, April 28, 2016 10:17 AM<br>
<span style="font-weight:bold">To: </span>Access Network <<a href="mailto:athen-list@u.washington.edu">athen-list@u.washington.edu</a>><br>
<span style="font-weight:bold">Subject: </span>[Athen] TTY numbers -- still a thing?<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>Hi Colleagues,</div>
<div><br>
</div>
<div>We recently had a discussion with our Telecommunications staff who were trying to track down the former sites of all TTY devices that were on campus. A lot of them have been disconnected and or gotten rid of since they are an older technology. However,
I would like to ask how your university is handling this issue. Do you have any TTYs on campus? Are they advertised on the university contact page? I know that Video Relay is much more in use as well as email by deaf/HOH users but I would like to know if
there are any good reasons to retain TTYs, perhaps for consumers who have older technologies they still use for communication.</div>
<div><br>
</div>
<div>Thanks</div>
<div>Kathy</div>
<div><br>
</div>
<div>
<div>Kathleen Cahill</div>
<div>MIT Assistive Technology Information Center (ATIC)</div>
<div>77 Mass. Ave. 7-143</div>
<div>Cambridge MA 02139</div>
<div>(617) 253-5111</div>
<div><a href="mailto:kcahill@mit.edu">kcahill@mit.edu</a></div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>