Browse Prior Art Database

TFTP Option Extension (RFC2347)

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

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Malkin: AUTHOR [+2]

Abstract

The Trivial File Transfer Protocol [1] is a simple, lock-step, file transfer protocol which allows a client to get or put a file onto a remote host. This document describes a simple extension to TFTP to allow option negotiation prior to the file transfer.

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

Network Working Group G. Malkin

Request for Commments: 2347 Bay Networks

Updates: 1350 A. Harkin

Obsoletes: 1782 Hewlett Packard Co.

Category: Standards Track May 1998

TFTP Option Extension

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1998). All Rights Reserved.

Abstract

The Trivial File Transfer Protocol [1] is a simple, lock-step, file

transfer protocol which allows a client to get or put a file onto a

remote host. This document describes a simple extension to TFTP to

allow option negotiation prior to the file transfer.

Introduction

The option negotiation mechanism proposed in this document is a

backward-compatible extension to the TFTP protocol. It allows file

transfer options to be negotiated prior to the transfer using a

mechanism which is consistent with TFTP's Request Packet format. The

mechanism is kept simple by enforcing a request-respond-acknowledge

sequence, similar to the lock-step approach taken by TFTP itself.

While the option negotiation mechanism is general purpose, in that

many types of options may be negotiated, it was created to support

the Blocksize option defined in [2]. Additional options are defined

in [3].

Packet Formats

TFTP options are appended to the Read Request and Write Request

packets. A new type of TFTP packet, the Option Acknowledgment

(OACK), is used to acknowledge a client's option negotiation request.

A new error code, 8, is hereby defined to indicate that a transfer

should be terminated due to option negotiation.

Options are appended to a TFTP Read Request or Write Request packet

as follows:

+-------+---~~---+---+---~~---+---+---~~---+---+---~~---+---+-->

| opc |filename| 0 | mode | 0 | opt1 | 0 | value1 | 0 | <

+-------+---~~---+---+---~~---+---+---~~---+---+---~~---+---+-->

>-------+---+---~~---+---+

< optN | 0 | valueN | 0 |

>-------+---+---~~---+---+

opc

The opcode field contains either a 1, for Read Requests, or 2,

for Write Requests, as defined in [1].

...