RFC 1783: TFTP Blocksize Option
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2348.
Current version: RFC 2348 — TFTP Blocksize Option
In plain English — editorial summary, not part of the RFC
This document describes a TFTP option which allows the client and server to negotiate a blocksize more applicable to the network medium. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1783
- Published
- March 1995
- Authors
- G. Malkin; A. Harkin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 5
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1784TFTP Timeout Interval and Transfer Size OptionsObsoleted
March 1995
- RFC 1782TFTP Option ExtensionObsoleted
March 1995
- RFC 1785TFTP Option Negotiation AnalysisCurrent
March 1995
- RFC 2090TFTP Multicast OptionCurrent
February 1997
- RFC 2577FTP Security ConsiderationsCurrent
May 1999
- RFC 1635How to Use Anonymous FTPCurrent
May 1994
- RFC 2415Simulation Studies of Increased Initial TCP Window SizeCurrent
September 1998
- RFC 1830SMTP Service Extensions for Transmission of Large and Binary MIME MessagesObsoleted
August 1995
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?