RFC 2840 (rfc2840) - Page 3 of 12

TELNET KERMIT OPTION

RFC 2840                  TELNET KERMIT OPTION                  May 2000


   Availability of Kermit server
      For the purposes of this document, a Kermit server is said to be
      available if, through the negotiations described herein, its
      Telnet partner knows that it is a Kermit server.

3. COMMANDS AND CODES

   Support for a Kermit server is negotiated separately in each
   direction, allowing Kermit service to be embedded in the Telnet
   client, the Telnet server, or in both.  The proposed Telnet
   extensions are, therefore, symmetrical.

   When the connection is first opened, Kermit service is unavailable in
   both directions.

   The availability of Kermit service is negotiated using the following
   Telnet option:

     KERMIT           47 (assigned by IANA)

   The state of the connection is controlled by the following Telnet
   subnegotiation function codes:

     START-SERVER      0
     STOP-SERVER       1
     REQ-START-SERVER  2
     REQ-STOP-SERVER   3
     SOP               4
     RESP-START-SERVER 8
     RESP-STOP-SERVER  9

4. COMMAND MEANINGS

   The KERMIT OPTION is negotiated using the standard Telnet mechanisms:

   IAC WILL KERMIT
      The sender of this command incorporates a Kermit server and is
      willing to negotiate its use.

   IAC WONT KERMIT
      The sender of this command does not incorporate a Kermit server or
      refuses to negotiate its use.

   IAC DO KERMIT
      The sender of this command requests that the receiver negotiate
      use of a Kermit server.





Altman & da Cruz             Informational