Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!rutgers!deimos!uxc!uxc.cso.uiuc.edu!uxg.cso.uiuc.edu!phil
From: phil@uxg.cso.uiuc.edu
Newsgroups: comp.protocols.tcp-ip
Subject: TELNET incompatibility questions
Message-ID: <8800001@uxg.cso.uiuc.edu>
Date: 15 Feb 89 21:44:00 GMT
Lines: 25
Nf-ID: #N:uxg.cso.uiuc.edu:8800001:000:1069
Nf-From: uxg.cso.uiuc.edu!phil    Feb 15 15:44:00 1989


I have the following situation:

-   A host that REQUIRES use of the TELNET IP (Interrupt Process) and
    TELNET AO (Abort Output) commands (prefixed by IAC) in order to
    properly conduct a terminal session.  Without the ability to send
    these commands to that host's TELNET server, it is impossible to
    escape for runaway execution or runaway output.

-   A terminal server that provides no configurable way to transmit
    either the TELNET IP or TELNET AO commands.

Clearly, these two are not going to work well together.  Conceivably,
a modification to either of these could correct the problem.

Are the TELNET IP and AO commands a requirement?  Is it valid TELNET to
require use of them?  Which of the above two would it be more appropriate
to make modifications to?

A change to the host increases the level of compatibility and workability
whereas a change to the terminal server increases the flexibility and
functionality.  I am asking the above questions to get a better insight
on what the TELNET protocol expects of its implementations.

--phil