<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"
xmlns:ns1="http://schemas.microsoft.com/office/2004/12/omml">
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="country-region"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--a:link
{mso-style-priority: 99
;}
span.MSOHYPERLINK
{mso-style-priority: 99
;}
a:visited
{mso-style-priority: 99
;}
span.MSOHYPERLINKFOLLOWED
{mso-style-priority: 99
;}
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Calibri;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:Calibri;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:Arial;
color:navy;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:666831443;
mso-list-type:hybrid;
mso-list-template-ids:610859444 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:1348946439;
mso-list-template-ids:1287317352;}
@list l1:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Arnoud,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I feel compelled to reply to just one
point:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>“If Paul wants audio/t140c so much…”<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Personally, I do not care whether
audio/t140c or text/t140 is adopted as the industry standard. It makes
absolutely no difference to me, as I view both as a viable means of delivering
real-time text in a way that we can use it.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>What has mattered to me is delivering
real-time text capability at all, which was incredibly hard in the face of
constant customer requests for instant messaging. I’ve given both
technical and business reasons why text/t140 <i><span style='font-style:italic'>cannot</span></i>
be universally deployed today and the near future. I’ve given other business
reasons why text/t140 is not favored presently (cost factors).<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Working within those constraints, I wrote
the audio/t140c document. I might be blamed for creating something evil (and I
have been accused of trying to “screw over deaf people”), but the
truth is that I tried to create something that is a stepping stone that will
allow us to deploy RTT universally and will not exclude legacy TTY devices: the
roadmap that I have proposed is easier (and therefore more likely to succeed) than
taking the bigger leap to text/t140, in my opinion. (Note: text/t140 is now 6
years old, so I do not think my assessment is wrong.)<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I’ve said before that I think
text/t140 is where we want to be. How do you suggest we get there?<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>1) We can simply demanding text/t140
support on platforms. Some platforms <i><span style='font-style:italic'>cannot</span></i>
support it. Some platforms could support it, but would require coordination
with other products that also need to implement it (e.g., softswitches,
firewalls, NAT devices, and policy enforcement devices). You end up having an
end-to-end tug of war between product teams who wait for the others to take the
first step. Worse, you isolate anybody using a technology that simply cannot
do it. (How long until the last MGCP or NCS gateway is decommissioned?)<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>2) Shall we demand that service providers
deploy special text gateway devices and just use V.152 to those gateways?
(That pushes all of the cost and burden onto the service provider, rather than
GW vendors. However, it also presents special dialing requirements or line
provisioning requirements. For reasons that would require another full page of
text, I will say this will not work unless we remove the requirement that users
be able to go anywhere with their TTY devices.)<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>3) Shall we just forget about TTY devices
and move everybody to IP, letting those with TTY devices just limp along until
such time as they’re tired of being isolated or things not working part
of the time?<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Other ideas?<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Paul<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt;font-family:"Times New Roman"'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Arnoud van Wijk
[mailto:arnoud@annies.nl] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Friday, August 18, 2006 6:02
AM<br>
<b><span style='font-weight:bold'>To:</span></b> Rac@lists.wisc.edu<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [rac] Audio T.140
evaluation?</span></font><font size=3 face="Times New Roman"><span
style='font-size:12.0pt;font-family:"Times New Roman"'><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>And that is so absolutely true.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Audio/t140c is a very dangerous genie that
is almost out of the bottle now.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>And once deployed outside its limited
purpose, we will get a big mess with fragmentation dangers.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>You only have to look at what has happened
to the different text telephone protocols, or the different IM protocols. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>If it is up to me, I want audio/t140c
erased from existence. It will be hard enough to get text/t140 deployed.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Now as I always say, audio/t140c is ok in
gateway-gateway connections. IP terminals must never be mandated to support
audio/t140c.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Audio/y140c could be added as a special
PSTN functionality. But such IP terminal MUST have text/t140.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>What about gateways? They must support
text/t140 and if they want…audio/t140c.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>You will get a number of scenarios all
from IP side starting: (gateway supports both text/t140 and audio/t140c)<o:p></o:p></span></font></p>
<ol style='margin-top:0in' start=1 type=1>
<li class=MsoNormal style='color:navy;mso-list:l0 level1 lfo3'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial'>call
has audio/t140c and text/t140 in the SDP, nice for the gateway, it selects
audio/t140c. No issue here.<o:p></o:p></span></font></li>
<li class=MsoNormal style='color:navy;mso-list:l0 level1 lfo3'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial'>call
has text/t140 in the SDP plus an indicator that text must be used. No
issues here.<o:p></o:p></span></font></li>
<li class=MsoNormal style='color:navy;mso-list:l0 level1 lfo3'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial'>call
has text/t140 in the SDP, there is no indicator if text must be used.
There are a few possibilities: <br>
a: set up text in a reinvite if a key or text telephony is detected.<br>
b: set up text/t140 port anyway and close this port if no text input is
detected after 60 seconds, it can always then reinvite for text if any
text is detected later.<o:p></o:p></span></font></li>
</ol>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>So, if Paul wants Audio/t140c so much. OK
but only mandate gateways to support both. Text/140 is the universal lina <st1:City
w:st="on"><st1:place w:st="on">franca</st1:place></st1:City> real-time text
protocol and will also be set for interconnectivity between any text to any
text networks.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>With the coming of WiMax, rural areas will
be able to get high speed internet. Sprint is starting to roll out such
network.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>The range is 50 kilometers in rural areas
and 2-3 kilometers in cities.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>So this is quite promising. TTY users
should be one of the first to switch then.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Perhaps that is the best way to
investigate where the move to IP is impossible.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Perhaps we can mandate in the <st1:country-region
w:st="on"><st1:place w:st="on">US</st1:place></st1:country-region> that ToIP
must be able to pass through any operators network, and find a way to ensure we
have ata boxes for TTY connectivity. Such box can support audio/t140c and
text/t140.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Just my 2 cents and a bit.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<p><font size=2 color=black face=Arial><span style='font-size:10.0pt;
font-family:Arial;color:black'>Arnoud A. T. van Wijk</span></font><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:navy'><br>
</span></font><strong><b><font size=2 color=black face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:black'>AnnieS New Technology</span></font></b></strong><font
size=2 color=navy><span style='font-size:10.0pt;color:navy'><br>
<a href="http://www.AnnieS.nl"><font color=black face=Arial><span
style='font-family:Arial;color:black'>www.AnnieS.nl</span></font></a></span></font><font
color=navy><span style='color:navy'><br>
</span></font><font size=2 color=navy face=Arial><span style='font-size:10.0pt;
font-family:Arial;color:navy'>Mobile textphone (SIP): </span></font><font
color=navy><span style='color:navy'><a href="mailto:arnoud@annies.nl"><font
size=2 color=black face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:black'>arnoud@annies.nl</span></font></a></span></font><o:p></o:p></p>
</div>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt;font-family:"Times New Roman"'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Gunnar Hellstrom
[mailto:gunnar.hellstrom@omnitor.se] <br>
<b><span style='font-weight:bold'>Sent:</span></b> donderdag 17 augustus 2006
21:34<br>
<b><span style='font-weight:bold'>To:</span></b> Norman Williams;
Rac@Lists.Wisc.Edu<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [rac] Audio T.140
evaluation?</span></font><font size=3 face="Times New Roman"><span
style='font-size:12.0pt;font-family:"Times New Roman"'><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><st1:City w:st="on"><st1:place w:st="on"><font size=3
color=blue face="Courier New"><span style='font-size:12.0pt;font-family:"Courier New";
color:blue'>Norman</span></font></st1:place></st1:City><font size=3
color=blue face="Courier New"><span style='font-size:12.0pt;font-family:"Courier New";
color:blue'>,</span></font><font size=3 face="Times New Roman"><span
style='font-size:12.0pt;font-family:"Times New Roman"'><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'>I hope you will
get a sample, and a gateway to use it with.</span></font><font size=3
face="Times New Roman"><span style='font-size:12.0pt;font-family:"Times New Roman"'><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt;font-family:"Times New Roman"'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'>audio/t140c
should have very good opportunities to work well, at least for pure text and
for alternating text and voice. And that is as far as it needs to be used with
the applications that are proposed.</span></font><font size=3
face="Times New Roman"><span style='font-size:12.0pt;font-family:"Times New Roman"'><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt;font-family:"Times New Roman"'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'>As usual, there
are many opportunities to do the application integration with different
ambition levels. If you find issues, they may have a source in the surrounding
software or environment but not in the standard itself. </span></font><font
size=3 face="Times New Roman"><span style='font-size:12.0pt;font-family:"Times New Roman"'><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt;font-family:"Times New Roman"'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'>The issues are
more on an IP service architecture plane. You simply should not call other
media "audio" just for sake of convenience even if it seems to work. </span></font><font
size=3 face="Times New Roman"><span style='font-size:12.0pt;font-family:"Times New Roman"'><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt;font-family:"Times New Roman"'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'>We got the RFC
classified "historic", and we had to put in a lot of words about how
the use was restricted to gateway applications.</span></font><font size=3
face="Times New Roman"><span style='font-size:12.0pt;font-family:"Times New Roman"'><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt;font-family:"Times New Roman"'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'>This is a copy of
the words we got from the IETF area director Allison Mankin explaining why it
got deemed "historic" from the beginning:</span></font><font size=3
face="Times New Roman"><span style='font-size:12.0pt;font-family:"Times New Roman"'><o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt;font-family:"Times New Roman"'> <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 color=blue face="Courier New"><span
style='font-size:12.0pt;font-family:"Courier New";color:blue'>---------------------------------------------------------</span></font><font
size=3 face="Times New Roman"><span style='font-size:12.0pt;font-family:"Times New Roman"'><o:p></o:p></span></font></p>
</div>
<div>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>Gunnar, Paul,</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>t140c was approved today, with the IESG
finding it in perfect</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>shape. The only discussion was about the
Historic designation. We</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>discussed the Last Call comments, the
GEN-ART comment, and my rationale</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>(including the announcement text I wrote
in the tracker and my report</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>on the Chairs' views).</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>First, congratulations to you both on the
excellent quality of the</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>document as a document. It made it easy
to work with.</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>The purpose of making it Historic is not
to condemn trunking gateways,</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>it is to avoid setting precedent with a
PS for calling text data an audio</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>type. This document does so due to
implementation pressures of SDP in</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>these gateways. RFC 4103 has the example
(text/t140) we want people</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>to follow.</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>The impact of going to Historic should
not block the goals you and</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>Paul have described: the payload
specification is in an RFC-to-be, the</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>media type being registered with no
blockage from any media experts</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>(which it would have gotten with a different
designation on the</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>document!). There is no internal text
that says the RFC is Historic.</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>So the only meaning of this designation
is for later, when someone</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>pops up with an audio major type with
data that is not audio, the AVT</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>or other working group can press back for
a very tight applicability</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>statement and cite precedent, or if
there's no deployment, ask them to</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>go to a different design.</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>A few more bits inline.</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>I hope this is more understandable now.
Let me underline again</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>the point about the problem of media type
expert review if we</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>had not gone Historic. </span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>With my best regards,</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>Allison</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>---------------------------------------------------------------</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>I find it very hard to go against these words
and strt to use it between terminals. I find it easy and perfectly OK to use it
between gateways. </span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>To use it between gateways and terminals
is a grey area. The words in the RFC does not totally forbid that application,
even if it is clearly stated that the intention is for trunking gateways.
However accepting it between gateways and terminals makes the idea of media
declarations in SIP collapse and the architecture of IP múltimedia to become a
mess. I do not want to contribute to that.</span></font><o:p></o:p></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>These issues will not be visible when you
try it, but certainly something we, as a global advisory group will need to
consider. </span></font><o:p></o:p></p>
<p><font size=3 face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p>
<p><font size=3 color=blue face="Courier New"><span style='font-size:12.0pt;
font-family:"Courier New";color:blue'>Gunnar</span></font><o:p></o:p></p>
</div>
<p><font size=2 face="Times New Roman"><span style='font-size:10.0pt'>-----------------------------------------------------------------------------<br>
Gunnar Hellström, Omnitor<br>
gunnar.hellstrom@omnitor.se<br>
Mob: +46 708 204 288<br>
Phone: +46 8 556 002 03<br>
www.omnitor.se<br>
</span></font> <o:p></o:p></p>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> Norman Williams
[mailto:norman.williams@gallaudet.edu]<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, August 17, 2006
8:19 PM<br>
<b><span style='font-weight:bold'>To:</span></b> Rac@Lists.Wisc.Edu<br>
<b><span style='font-weight:bold'>Subject:</span></b> [rac] Audio T.140
evaluation?</span></font><font size=3 face="Times New Roman"><span
style='font-size:12.0pt;font-family:"Times New Roman"'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'>Hi,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'>I
forgot to bring this topic to the phone conference we had recently.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'>Is
there a way for us to evaluate audio T.140 to see if there are issues? Do we
have a working audio T.140 solution?<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><st1:City w:st="on"><st1:place w:st="on"><font size=2
face=Calibri><span style='font-size:11.0pt'>Norman</span></font></st1:place></st1:City><o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt;font-family:"Times New Roman"'><br>
--- <br>
You are currently subscribed to rac as: gunnar.hellstrom@omnitor.se. <br>
To unsubscribe click here:
https://lists.wisc.edu/u?id)14436N&n=l=c&o455168 <br>
or send a blank email to leave-3455168-2914436N@lists.wisc.edu <o:p></o:p></span></font></p>
</blockquote>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt;font-family:"Times New Roman"'><br>
---<br>
You are currently subscribed to rac as: arnoud@annies.nl.<br>
To unsubscribe click here: https://lists.wisc.edu/u?id)14433R&n=l=c&o456252<br>
or send a blank email to leave-3456252-2914433R@lists.wisc.edu <o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt;font-family:"Times New Roman"'><br>
---<br>
You are currently subscribed to rac as: paulej@packetizer.com.<br>
To unsubscribe click here:
https://lists.wisc.edu/u?id)14439J&n=l=c&o463578<br>
or send a blank email to leave-3463578-2914439J@lists.wisc.edu <o:p></o:p></span></font></p>
</div>
</div>
<BR>
---
<BR>
You are currently subscribed to rac as: paulej@packetizer.com.
<BR>
To unsubscribe click here: https://lists.wisc.edu/u?id)14439J&n=T&l=rac&o474178
<BR>
or send a blank email to leave-3474178-2914439J@lists.wisc.edu
</BODY>
</html>