📄 rfc1921.txt
字号:
This message is used to purge the current screen copy request message. When the "TNVIP server" or the "TNVIP client" receives this message, if it has not already acknowledged the request message, it returns a screen copy purge acknowledgement message. If it has already replied, it ignores and deletes the message. The following command value is defined as: <CDE> = PURGE indication = 40 (0x28).There is no parameter field.9. The TM attention The TM attention is the signal used to activate the local dialog of the DSA Terminal Manager. The Telnet Abort Output (AO) command [1] is the mechanism used to implement the TM attention key support in TNVIP. IAC AO (0xFF 0xF5) In order to implement the TM attention key support, "TNVIP clients" should provide a key (or combination of keys) that is identified as mapping to the TM attention key. When the user presses this key(s),Dujonc Informational [Page 23]RFC 1921 TNVIP Protocol March 1996 the "TNVIP client" should transmit a Telnet AO command to the "TNVIP server". Upon receipt of the AO command, a "TNVIP server" that implements the DSA Terminal Manager should enter in what will be loosely termed "TM Local Dialog", suspending the eventual DSA host connection, else it should simply ignore it.10. The Break Key Generally, there is no break key on the real VIP terminal. The break signal is transmitted to the host application through a TM local dialog command ($*$BRK for example) On "TNVIP client" emulating VIP terminal, it is often possible to map the break signal on a special key combination or by other way (using mouse ...). The Telnet Break (BRK) command [1] is used to map the Break signal of the TNVIP. IAC BRK (0xFF 0xF3)11. The Logout Key The Telnet Interrupt Process (IP) command [1] can be used to map the logout command of the TM Local Dialog ($*$LO for example) if it is implemented on the "TNVIP server". IAC IP (0xFF 0xF4)12. TNVIP messages list All the TNVIP commands are summarized here after (and the values are given in hexadecimal).12.1 Screen Flow Data request (allowed in the two ways) SCREEN DATA-REQ <FC1> <FC2> STX [<screen-data>] IAC EOR 60 01 <FC1> <FC2> 02 [<screen-data>] FF EF - Allowed responses to the screen Data request. SCREEN ACK IAC EOR 60 0A FF EFDujonc Informational [Page 24]RFC 1921 TNVIP Protocol March 1996 SCREEN ERROR IAC EOR 60 0E FF EF SCREEN BUSY IAC EOR 60 12 FF EF SCREEN ABORTED IAC EOR 60 16 FF EF SCREEN PURGED IAC EOR 60 1A FF EF Password request (only from the "TNVIP server" to the "TNVIP client") SCREEN PASSW-REQ <FC1> <FC2> STX [<screen-data>] IAC EOR 60 05 <FC1> <FC2> 02 [<screen-data>] FF EF - Allowed responses to the password request. SCREEN ACK IAC EOR 60 0A FF EF SCREEN ERROR IAC EOR 60 0E FF EF SCREEN BUSY IAC EOR 60 12 FF EF SCREEN ABORTED IAC EOR 60 16 FF EF SCREEN PURGED IAC EOR 60 1A FF EF Local state request (only from the "TNVIP client" to the "TNVIP server"). SCREEN LOCAL-ST IAC EOR 60 2D FF EF - Allowed responses to the Local state request. SCREEN ACK IAC EOR 60 0A FF EF SCREEN PURGED IAC EOR 60 1A FF EFDujonc Informational [Page 25]RFC 1921 TNVIP Protocol March 1996 Responses to request violating the TNVIP protocol (allowed in the two ways) SCREEN NOT-AVAIL IAC EOR 60 0E FF EF SCREEN PROT-VIOL IAC EOR 60 22 FF EF SCREEN UNKN-CDE IAC EOR 60 26 FF EF Indications (allowed in the two ways) SCREEN DATA-IND <FC1> <FC2> STX [<screen-data>] IAC EOR 60 00 <FC1> <FC2> 02 [<screen-data>] FF EF SCREEN PURGE IAC EOR 60 28 FF EF Password indication (only from the "TNVIP server" to the "TNVIP client"). SCREEN PASSW-IND <FC1> <FC2> STX [<screen-data>] IAC EOR 60 04 <FC1> <FC2> 02 [<screen-data>] FF EF On line state indication (only from the "TNVIP client" to the "TNVIP server"). SCREEN ONLINE-ST IAC EOR 60 30 FF EF12.2 Printer flow Data request (only from the "TNVIP server" to the "TNVIP client") PRINTER DATA-REQ <FC1> <FC2> STX [<printer-data>] IAC EOR 68 01 <FC1> <FC2> 02 [<printer-data>] FF EF - Allowed responses to the printer data request. PRINTER ACK [<status>] IAC EOR 68 0A [<status>] FF EF PRINTER ERROR [<status>] IAC EOR 68 0E [<status>] FF EFDujonc Informational [Page 26]RFC 1921 TNVIP Protocol March 1996 PRINTER BUSY [<status>] IAC EOR 68 12 [<status>] FF EF PRINTER ABORTED [<status>] IAC EOR 68 16 [<status>] FF EF PRINTER PURGED [<status>] IAC EOR 68 1A [<status>] FF EF PRINTER NOT-AVAIL [<status>] IAC EOR 68 1E [<status>] FF EF State request (only from the "TNVIP server" to the "TNVIP client") PRINTER STATE-REQ IAC EOR 68 35 FF EF - Allowed responses to the state request. PRINTER READY IAC EOR 68 3A FF EF PRINTER STANDBY IAC EOR 68 3E FF EF PRINTER PURGED IAC EOR 68 1A FF EF PRINTER NOT-AVAIL IAC EOR 68 1E FF EF Responses to request violating the TNVIP protocol (allowed in the two ways) PRINTER PROT-VIOL IAC EOR 68 22 FF EF PRINTER UNKN-CDE IAC EOR 68 26 FF EF Indication (only from the "TNVIP server" to the "TNVIP client") PRINTER PURGE IAC EOR 68 28 FF EFDujonc Informational [Page 27]RFC 1921 TNVIP Protocol March 199612.3 Screen Copy Printing messages flow Copy request (only from the "TNVIP client" to the "TNVIP server") SCPM COPY-REQ IAC EOR 69 41 FF EF - Allowed responses to the copy request (from the "TNVIP server" to the "TNVIP client") SCPM ERROR <reason> IAC EOR 69 0E <reason> FF EF SCPM PURGED IAC EOR 69 1A FF EF SCPM NOT-AVAIL IAC EOR 69 1E FF EF SCPM LOCAL-COPY-RQ IAC EOR 69 47 FF EF Local copy request (only from the "TNVIP server" to the "TNVIP client" ) SCPM LOCAL-COPY-RQ IAC EOR 69 47 FF EF - Allowed responses to the local copy request (from the "TNVIP client" to the "TNVIP server"). SCPM ACK IAC EOR 69 0A FF EF SCPM ERROR IAC EOR 69 0E FF EF SCPM BUSY IAC EOR 69 12 FF EF SCPM ABORTED IAC EOR 69 16 FF EF SCPM PURGED IAC EOR 69 1A FF EF SCPM NOT-AVAIL IAC EOR 69 1E FF EFDujonc Informational [Page 28]RFC 1921 TNVIP Protocol March 1996 Data request. (only from the "TNVIP client" to the "TNVIP server") SCPM DATA-REQ <FC1> <FC2> STX [<screen-data>] IAC EOR 69 01 <FC1> <FC2> 02 [<screen-data>] FF EF - Allowed responses to the data request SCPM ACK IAC EOR 69 0A FF EF SCPM PURGED IAC EOR 69 1A FF EF SCPM NOT-AVAIL IAC EOR 69 1E FF EF Responses to request violating the TNVIP protocol (allowed in the two ways) SCPM PROT-VIOL IAC EOR 69 22 FF EF SCPM UNKN-CDE IAC EOR 69 26 FF EF Indications (allowed in the two ways) SCPM DATA-IND <FC1> <FC2> STX [<screen-data>] IAC EOR 69 00 <FC1> <FC2> 02 [<screen-data>] FF EF SCPM PURGE IAC EOR 69 28 FF EF13. Security Considerations Security issues are not addressed in this document. It is anticipated that once authentication mechanisms have become well established, use of them can be made by TNVIP. One of the important uses of authentication would be to answer the question of whether or not a given user should be allowed to "use" a specific terminal.Dujonc Informational [Page 29]RFC 1921 TNVIP Protocol March 199614. References [1] Postel, J., and J. Reynolds, "Telnet Protocol Specification", STD 8, RFC 854, USC/Information Sciences Institute, May 1983. [2] "Communications. MainWay. Terminal Management. DNS-E", Ref : 39A213EB Rev00, BULL S.A. [3] VanBokkelen, J., "Telnet Terminal-Type Option", RFC 1091, FTP Software, Inc., February 1989. [4] Postel, J., "Telnet End of Record Option", RFC 885, USC/Information Sciences Institute, December 1983. [5] Postel, J., and J. Reynolds, "Telnet Binary Transmission", STD 27, RFC 856, USC/Information Sciences Institute, May 1983. [6] Postel, J., and J. Reynolds, "Telnet Suppress Go Ahead Option", STD 29, RFC 858, USC/Information Sciences Institute, May 1983. [7] "Affinity V2. DKU7107 Reference Manual" Ref : 40 A2 23 WA, BULL S.A. [8] "Affinity V2. VIP7800 Reference Manual" Ref : 40 A2 24 WA, BULL S.A. [9] "Bull Questar 200. TCS 7424 et TCS 7434. Transmission de donnees. Manuel de reference" Ref : 80 F2 41DC Rev0, BULL S.A.15. Author's Address Jean-Yves Dujonc BULL S.A. rue Jean Jaures 78340 Les Clayes-sous-Bois France Phone: 1 30 80 62 95 Fax: 1 30 80 65 40 EMail: J.Y.Dujonc@frcl.bull.frDujonc Informational [Page 30]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -