TNVIP Protocol
RFC 1921
Document | Type |
RFC - Informational
(March 1996; No errata)
Was draft-rfced-info-dujonc (individual)
|
|
---|---|---|---|
Author | Jean-Yves Dujonc | ||
Last updated | 2013-03-02 | ||
Stream | Legacy stream | ||
Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
Stream | Legacy state | (None) | |
Consensus Boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | RFC 1921 (Informational) | |
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
Network Working Group J. Dujonc Request for Comments: 1921 Bull S.A. Category: Informational March 1996 TNVIP Protocol Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Abstract The goal of this document specifies a Telnet profile to support VIP terminal emulation allowing the access to the BULL hosts applications through a TCP/IP network. Table of Contents 1. Motivation . . . . . . . . . . . . . . . . . . . . . . 2 2. Background . . . . . . . . . . . . . . . . . . . . . . 3 3. Telnet Options and Commands Used . . . . . . . . . . . 3 3.1. Terminal type option . . . . . . . . . . . . . . . . 4 3.1.1. Subnegotiation of the Terminal Type . . . . . . . . 4 3.1.2. Terminal-types supported by the TNVIP protocol . . 4 3.1.3. TNVIP terminal models . . . . . . . . . . . . . . . 5 3.1.4. Mailbox name . . . . . . . . . . . . . . . . . . . 5 3.2. End of Record Option . . . . . . . . . . . . . . . . 6 3.3. Binary Transmission option . . . . . . . . . . . . . 6 3.4. Suppress Go Ahead option . . . . . . . . . . . . . . 7 4. TNVIP functions . . . . . . . . . . . . . . . . . . . 8 4.1. TNVIP terminal station . . . . . . . . . . . . . . . 9 4.1.1. Local and online states . . . . . . . . . . . . . . 9 4.1.2. Data receiving . . . . . . . . . . . . . . . . . 10 4.1.3. Data sending . . . . . . . . . . . . . . . . . . 10 4.2. TNVIP Server functions . . . . . . . . . . . . . . 10 4.2.1. VIP Terminal Manager . . . . . . . . . . . . . . 10 5. TNVIP Messages Format . . . . . . . . . . . . . . . 12 5.1. Address Field . . . . . . . . . . . . . . . . . . . 12 5.2. Command field . . . . . . . . . . . . . . . . . . . 13 5.3. Parameter field . . . . . . . . . . . . . . . . . . 14 6. The screen flow . . . . . . . . . . . . . . . . . . 14 6.1. Screen data messages . . . . . . . . . . . . . . . 14 6.2. Local state monitoring messages . . . . . . . . . . 15 6.3. Screen response messages . . . . . . . . . . . . . 16 6.3.1 Page overflow processing . . . . . . . . . . . . . 17 Dujonc Informational [Page 1] RFC 1921 TNVIP Protocol March 1996 6.4. Screen data purge indication message . . . . . . . 17 7. The printer flow . . . . . . . . . . . . . . . . . . 17 7.1. Printer data messages . . . . . . . . . . . . . . . 17 7.2. Printer response messages . . . . . . . . . . . . . 18 7.3. 7800 printer status management . . . . . . . . . . 19 7.4. Printer state request message . . . . . . . . . . 20 7.5. Printer state response messages . . . . . . . . . . 20 7.6. Printer purge indication message . . . . . . . . . 20 8. The Screen Copy Printing flow . . . . . . . . . . . 21 8.1. Screen copy request messages . . . . . . . . . . . 21 8.2. Screen copy data message . . . . . . . . . . . . . 21 8.3. Screen copy response messages . . . . . . . . . . . 22 8.4. Screen copy purge indication message . . . . . . . 23 9. The TM attention . . . . . . . . . . . . . . . . . . 23 10. The Break Key . . . . . . . . . . . . . . . . . . . 24 11. The Logout Key . . . . . . . . . . . . . . . . . . . 24 12. TNVIP messages list . . . . . . . . . . . . . . . . 24 12.1. Screen Flow . . . . . . . . . . . . . . . . . . . . 24 12.2. Printer flow . . . . . . . . . . . . . . . . . . . 26 12.3. Screen Copy Printing messages flow . . . . . . . . 28 13. Security Considerations . . . . . . . . . . . . . . 29 14. References . . . . . . . . . . . . . . . . . . . . . 30 15. Author's Address . . . . . . . . . . . . . . . . . . 30 1. Motivation P200 [7] and 7800 [8] VIP (Visual Information Projection) terminals differ mainly from NVT terminals [1] in that they work in block mode and have the capability to manage an associated printer. Generally in a DSA (Distributed Systems Architecture) network they are managed through the VIP transmission line procedure (character oriented). That is the reason why they are generically referred as VIP terminals. This document specifies the options to be modified successfully, to pass from the NVT terminal emulation supported on a Telnet connection, to a VIP terminal emulation. It defines also the format of the messages exchanged between the server and the client when theShow full document text