As per Relevance of the word solution, we have this rfc below:
Network Working Group John
Request for Comments: 728 Apr 1977
NIC #40036
A Minor Pitfall in the Telnet
Designers of Telnet options should be aware of the following
case in the Telnet protocol which may generate unexpected behavior
either end of the connection. Although at present none of the
options are susceptible to this problem, it could arise in the future
The Telnet sync sequence causes all data to be deleted from the
stream until a data mark is encountered. Telnet control functions
not affected by the sync sequence (see page 9 of the
specification). A Telnet option subnegotiation could be defined
that it had an affect on the data following it in the data stream.
example, a subnegotiation might be used to indicate the terminal was
display the following data in a particular font or should receive
special treatment by the terminal. A Telnet sync sequence sent
such a subnegotiation and its data and before the subnegotiation
been processed could resuit in the subnegotiation having its affect
data other than that intended
Two possible solutions come to mind at once. First, the data to
affected could be included as a parameter of the subnegotiation.
other words, the data is inserted in the data stream before the IAC
that terminates the subnegotiation. The disadvantages of this
are both theoretical and practical. Theoretically, it is improper
not really in the spirit of the Telnet protocol design to send data
subnegotiation parameters. Practically, in a situation where this
would arise it would be equally unexpected behavior (and
confusing if a human was affected) if all data except that affected
the subnegotiation was flushed
The second solution would be for designers of options which have
subnegotiations define a subnegotiation or other mechanism that
follow immediately after the Data Mark and nullify the affects of
offending subnegotiation. The exact semantics of such a
would probably be very specific to the option
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
