IBM's iSeries Telnet Enhancements
RFC 4777

 
Document Type RFC - Informational (November 2006; No errata)
Obsoletes RFC 2877
Last updated 2013-03-02
Stream ISE
Formats plain text pdf html
Stream ISE state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 4777 (Informational)
Telechat date
Responsible AD Ted Hardie
Send notices to (None)
Network Working Group                                     T. Murphy, Jr.
Request for Comments: 4777                                      P. Rieth
Obsoletes: 2877                                               J. Stevens
Category: Informational                                              IBM
                                                           November 2006

                   IBM's iSeries Telnet Enhancements

Status of This Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The IETF Trust (2006).

IESG Note

   This RFC is not a candidate for any level of Internet Standard.  The
   IETF disclaims any knowledge of the fitness of this RFC for any
   purpose and in particular notes that the decision to publish is not
   based on IETF review for such things as security, congestion control,
   or inappropriate interaction with deployed protocols.  The RFC Editor
   has chosen to publish this document at its discretion.  Readers of
   this document should exercise caution in evaluating its value for
   implementation and deployment.  See RFC 3932 for more information.

Abstract

   This document describes the interface to the Telnet server on IBM's
   iSeries line of midrange business computers.  This interface allows
   Telnet clients to request a Telnet terminal or printer session using
   specific session attributes related to device names, encryption,
   language support, auto-sign-on, response codes, session association,
   etc.

   These support functions are implemented primarily using the Telnet
   Environment option negotiation RFC 1572 to define new USERVAR
   variables that will be recognized by iSeries Telnet server.

Murphy, et al.               Informational                      [Page 1]
RFC 4777           IBM's iSeries Telnet Enhancements       November 2006

Table of Contents

   1. Introduction ....................................................2
   2. Standard Telnet Option Negotiation ..............................3
   3. Enhanced Telnet Option Negotiation ..............................4
   4. Enhanced Display Emulation Support ..............................7
   5. Enhanced Display Auto-Sign-On and Password Encryption ...........9
      5.1. Data Encryption Standard (DES) Password Substitutes .......13
      5.2. Secure Hash Algorithm (SHA) Password Substitutes ..........16
   6. Kerberos Services Ticket Automatic Sign-On Support .............18
   7. Device Name Collision Processing ...............................21
   8. Enhanced Printer Emulation Support .............................22
   9. Telnet Printer Terminal Types ..................................23
   10. Startup Response Record for Printer and Display Devices .......25
      10.1. Example of a Success Response Record .....................26
      10.2. Example of an Error Response Record ......................27
      10.3. Example of a Response Record with Device Name Retry ......28
      10.4. Response Codes ...........................................31
   11. Printer Steady-State Pass-Through Interface ...................33
      11.1. Example of a Print Record ................................35
      11.2. Example of a Print Complete Record .......................37
      11.3. Example of a Null Print Record ...........................37
   12. End-to-End Print Example ......................................39
   13. Security Considerations .......................................44
   14. IANA Considerations ...........................................44
   15. Normative References ..........................................44
   16. Informative References ........................................44
   17. Relation to Other RFCs ........................................45

1.  Introduction

   The iSeries Telnet server enables clients to negotiate both terminal
   and printer device names through Telnet Environment Options
   Negotiations [RFC1572].

   This allows Telnet servers and clients to exchange environment
   information using a set of standard or custom variables.  By using a
   combination of both standard VARs and custom USERVARs, the iSeries
   Telnet server allows client Telnet to request a pre-defined specific
   device by name.

   If no pre-defined device exists, then the device will be created,
   with client Telnet having the option to negotiate device attributes,
   such as the code page, character set, keyboard type, etc.

   Since printers can now be negotiated as a device name, new terminal
   types have been defined to request printers.  For example, you can

Murphy, et al.               Informational                      [Page 2]
RFC 4777           IBM's iSeries Telnet Enhancements       November 2006
Show full document text