RFC 1783:TFTP Blocksize Option
RFC-Ref

RFC - 1783

TFTP Blocksize Option

Original: ftp://ftp.isi.edu/in-notes/rfc1783.txt
Authors: G. Malkin [Xylogics, Inc.], A. Harkin [Hewlett Packard Co.]
Date: March 1995
Category: Informational
 
This specification has been !!! obsoleted !!!



Obsoleted by:
RFC-2348draft TFTP Blocksize Option

Updates:
RFC-1350std33
[STD 33]
The TFTP Protocol (Revision 2) (Updated by RFC-1783, RFC-1784, RFC-1785, RFC-1782, RFC-2347draft, RFC-2349draft, RFC-2348draft)

Referred by: 14 RFC
Refers to: 2 RFC

Status

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.

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. One of its primary uses is the booting of diskless nodes on a Local Area Network. TFTP is used because it is very simple to implement in a small node's limited ROM space. However, the choice of a 512-byte blocksize is not the most efficient for use on a LAN whose MTU may 1500 bytes or greater.

This document describes a TFTP option which allows the client and server to negotiate a blocksize more applicable to the network medium. The TFTP Option Extension mechanism is described in [2].


About Resource

Google
Web
RFC-Ref