<br><br><div class="gmail_quote">On Jan 5, 2008 11:49 PM, Luke -Jr <<a href="mailto:luke@dashjr.org">luke@dashjr.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">> Any protocol that uses TCP and human-readable text "supports" the *telnet*<br>> * client*. That's the way most of the Internet got designed. When you're<br>> testing a server, you telnet to it and converse via the protocol you're
<br>> trying to implement. Once you get the server running, you can implement a<br>> client that talks to it.<br><br></div></div>Which telnet client? While it may often work in practice, how many non-telnet<br>protocols allow for Telnet features like AYT, or feature negotiation?
<br></blockquote></div><br><br>Pretty much any telnet client. AYT is one of the codes in the range F0-FF, (and is only to be interpreted as such if immediately preceded by FF) which won't be used by 7-bit ASCII. That's what most Internet protocols have traditionally used, and even UTF-8 won't use FF.
<br><br>These protocols were designed by people who wanted to minimize the chance that legitimate data would have to be "escaped", and designed them to not conflict with one another.<br>