A new Request for Comments is now available in online RFC libraries.


        RFC 1783:

        Title:      TFTP Blocksize Option
        Author:     G. Malkin & A. Harkin
        Date:       March 1995
        Mailbox:    gmalkin@xylogics.com, ash@cup.hp.com
        Pages:      5
        Characters: 7,814
        Updates:    1350

        URL:        ftp://ds.internic.net/rfc/rfc1783.txt


The Trivial File Transfer Protocol (STD 33, RFC 1350) 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.  This RFC
is the product of the TFTP Extensions Working Group of the IETF.

This is now a Proposed Standard Protocol.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute