<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
> Where did you find this ? Is this in some FBB notes somewhere
?<br>
<br>
No FBB notes about this what I could discover but it is in the RFC's
of the IETF<br>
at tools.ietf.org<br>
<br>
<br>
<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/rfc1123">https://tools.ietf.org/html/rfc1123</a><br>
<br>
RFC-1123 <br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<pre style="font-size: 13.3333px; margin-top: 0px; margin-bottom: 0px; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span class="h1" style="line-height: 0pt; display: inline; white-space: pre; font-family: monospace; font-size: 1em; font-weight: bold;"><h1 style="line-height: 0pt; display: inline; white-space: pre; font-family: monospace; font-size: 1em; font-weight: bold;">Requirements for Internet Hosts -- Application and Support</h1></span></pre>
<br>
Section <br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<pre class="newpage" style="font-size: 13.3333px; margin-top: 0px; margin-bottom: 0px; break-before: page; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><a href="https://tools.ietf.org/html/rfc1123#section-3.2.7">3.2.7</a> Telnet Binary Option .............................. <a href="https://tools.ietf.org/html/rfc1123#page-20">20</a></pre>
<br>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<pre class="newpage" style="font-size: 13.3333px; margin-top: 0px; margin-bottom: 0px; break-before: page; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;"> 3.2.7 Telnet Binary Option: <a href="https://tools.ietf.org/html/rfc856">RFC-856</a>
When the Binary option has been successfully negotiated,
arbitrary 8-bit characters are allowed. However, the data
stream MUST still be scanned for IAC characters, any embedded
Telnet commands MUST be obeyed, and data bytes equal to IAC
MUST be doubled. Other character processing (e.g., replacing
CR by CR NUL or by CR LF) MUST NOT be done. In particular,
there is no end-of-line convention (see <a href="https://tools.ietf.org/html/rfc1123#section-3.3.1">Section 3.3.1</a>) in
binary mode.</pre>
<br>
etc.<br>
<br>
Read also RFC-856<br>
<br>
<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/rfc856">https://tools.ietf.org/html/rfc856</a><br>
<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<pre class="newpage" style="font-size: 13.3333px; margin-top: 0px; margin-bottom: 0px; page-break-before: always; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span class="h2" style="line-height: 0pt; display: inline; white-space: pre; font-family: monospace; font-size: 1em; font-weight: bold;"><h2 style="line-height: 0pt; display: inline; white-space: pre; font-family: monospace; font-size: 1em; font-weight: bold;"><a class="selflink" name="section-5" href="https://tools.ietf.org/html/rfc856#section-5" style="color: black; text-decoration: none;">
5</a>. Description of the Option</h2></span>
With the binary transmission option in effect, the receiver should
interpret characters received from the transmitter which are not
preceded with IAC as 8 bit binary data, with the exception of IAC
followed by IAC which stands for the 8 bit binary data with the
decimal value 255. IAC followed by an effective TELNET command (plus
any additional characters required to complete the command) is still
the command even with the binary transmission option in effect. IAC
followed by a character which is not a defined TELNET command has the
same meaning as IAC followed by NOP, although an IAC followed by an
undefined command should not normally be sent in this mode.
</pre>
<br>
etc.<br class="Apple-interchange-newline">
----------<br>
<div class="moz-cite-prefix"><br>
73,<br>
<br>
Bob VE3TOK<br>
<br>
<br>
<br>
On 16-04-10 08:38 AM, Maiko Langelaar wrote:<br>
</div>
<blockquote
cite="mid:alpine.LRH.2.20.1604100732580.12213@node162.1.168.192.in-addr.arpa"
type="cite"> <br>
<blockquote type="cite">the data stream MUST still be scanned for
IAC characters ... <br>
</blockquote>
<br>
Where did you find this ? Is this in some FBB notes somewhere ? <br>
<br>
This is the first useful piece of information I have seen for <br>
a long time (I mean I have seen it before), but that particular <br>
statement in context with the binary payload makes it stand out <br>
all of a sudden. <br>
<br>
I always thought I had to avoid the parsing of IAC, not still <br>
have to manage it in the YAPP receive or send functions. I'll <br>
get to work on that then and see if that helps. <br>
<br>
No more test data please, information overload :) <br>
<br>
Maiko <br>
<br>
<br>
</blockquote>
<br>
</body>
</html>