Browse Prior Art Database

TELNET KERMIT OPTION (RFC2840)

IP.com Disclosure Number: IPCOM000003439D
Original Publication Date: 2000-May-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 9 page(s) / 21K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Altman: AUTHOR [+2]

Abstract

This document describes an extension to the Telnet protocol to allow the negotiation, coordination, and use of the Kermit file transfer and management protocol over an existing Telnet protocol connection.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 13% of the total text.

Network Working Group J. Altman

Request for Comments: 2840 F. da Cruz

Category: Informational Columbia University

May 2000

TELNET KERMIT OPTION

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 Internet Society (2000). All Rights Reserved.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",

"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this

document are to be interpreted as described in RFC 2119.

ABSTRACT

This document describes an extension to the Telnet protocol to allow

the negotiation, coordination, and use of the Kermit file transfer

and management protocol over an existing Telnet protocol connection.

CONTENTS

1. MOTIVATION . . . . . . . . . . . . . . . . . . . . . . . . 2

2. DEFINITIONS. . . . . . . . . . . . . . . . . . . . . . . . 2

3. COMMANDS AND CODES . . . . . . . . . . . . . . . . . . . . 3

4. COMMAND MEANINGS . . . . . . . . . . . . . . . . . . . . . 3

5. KERMIT PROTOCOL IMPLICATIONS . . . . . . . . . . . . . . . 5

6. EXAMPLES . . . . . . . . . . . . . . . . . . . . . . . . . 6

6.1. EXAMPLE 1. . . . . . . . . . . . . . . . . . . . . . . . 6

6.2. EXAMPLE 2. . . . . . . . . . . . . . . . . . . . . . . . 7

6.3. EXAMPLE 3. . . . . . . . . . . . . . . . . . . . . . . . 8

6.4. EXAMPLE 4. . . . . . . . . . . . . . . . . . . . . . . . 9

6.5. EXAMPLE 5. . . . . . . . . . . . . . . . . . . . . . . . 10

7. SECURITY CONSIDERATIONS. . . . . . . . . . . . . . . . . . 11

8. REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . 11

9. AUTHORS' ADDRESSES . . . . . . . . . . . . . . . . . . . . 11

10. FULL COPYRIGHT STATEMENT. . . . . . . . . . . . . . . . . 12

1. MOTIVATION

The Kermit protocol [KER] performs error-corrected file transfer and

management over many types of connections, including terminal

connections, among diverse hardware and software platforms. It is

supported by a large number of Telnet clients and is also widely

available on the Internet hosts to which Telnet connections are made.

Traditionally, the Kermit protocol connection is started manually by

a user, or perhaps by an automated script. It is the user's

responsibility to start the Kermit server on one end of the

connection and the Kermit client on the other, or to start a Kermit

...