RFC 1921 (rfc1921) - Page 2 of 30


TNVIP Protocol



Alternative Format: Original Text Document



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 the
   TNVIP protocol is successfully negotiated.












Dujonc                       Informational