RFC 854:TELNET PROTOCOL SPECIFICATION
RFC-Ref

host


Click on the red underlined text to get to the source

... canonical terminal. This eliminates the need for "server" and "user" hosts to keep information about the characteristics of each other's terminals and ...
... terminals and terminal handling conventions. All hosts, both user and server, map their local device characteristics and conventions so as to appear to be dealing with an NVT ...
... similar mapping by the other party. The NVT is intended to strike a balance between being overly restricted (not providing hosts a rich enough vocabulary for mapping into their local character sets), and ...
... NOTE: The "user" host is the host to which the physical terminal ...
... NOTE: The "user" host is the host to which the physical terminal ...
... physical terminal is normally attached, and the "server" host is the host which is normally providing some service ...
... terminal is normally attached, and the "server" host is the host which is normally providing some service. As an alternate point of view, ...
... terminal-to-terminal or process-to-process communications, the "user" host is the host which initiated the communication. ...
... terminal or process-to-process communications, the "user" host is the host which initiated the communication. ...
... 2. The principle of negotiated options takes cognizance of the fact that many hosts will wish to provide additional services over and above those available within an NVT ...
... effect. (It should be noted that some time will elapse between the transmission of a request and the receipt of an acknowledgment, which may be negative. Thus, a host may wish to buffer data, after requesting an option, until it learns whether ...
... connection in a state which both ends can handle. Thus, all hosts may implement their TELNET processes to be totally unaware of options that are not ...


... network (although options exist to enable a "remote" echoing mode of operation, no host is required to implement this option). The code set is seven-bit USASCII in an eight-bit ...


... 1) Insofar as the availability of local buffer space permits, data should be accumulated in the host where it is generated until a complete line of data is ready for transmission, or until some locally-defined explicit signal to transmit occurs. ...
... The motivation for this rule is the high cost, to some hosts, of processing network input interrupts, coupled with the ...
... be sent from a terminal at the end of each line, since server hosts do not normally require a special signal (in addition to end-of-line or other locally-defined characters) in order to commence processing. Rather, the TELNET ...
... commence processing. Rather, the TELNET GA is designed to help a user's local host operate a physically half duplex terminal which has a "lockable" keyboard such as the IBM 2741. A ...
... terminal-to-terminal communication, GAs may be required in neither, one, or both directions. If a host plans to support terminal-to-terminal ...
... terminal-to-terminal communication it is suggested that the host provide the user with a means of manually signaling that it is ...


... buffers external to the system (in the network and the user's local host) which should be cleared; the appropriate way to do this is to transmit the "Synch" signal (described below) to the user system. ...


... flow control mechanisms may cause such a signal to be buffered elsewhere, for example in the user's host. ...


... When used for remote user access to service hosts (i.e., remote terminal access) this protocol is assigned server port ...



Google
Web
RFC-Ref