Balance fewer waits against path limits
05Bigger blocks can reduce packet overhead and stop-and-wait exchanges, but a negotiated value is not proof that the path can carry the packet without fragmentation.
A 4096-data-octet packet plus those32 header octets is 4128, over the example MTU 1500. Agreement alone does not prevent fragmentation or authenticate the peer.
Source for this drawing: RFC 2348 · Read RFC source: Proof of Concept / Security · p.4 ↗
New to this? Start hereA quick picture + helpful background
A message needs an address.
Think of a packet as a small addressed envelope. Devices pass it onward; transport protocols decide what delivery promises an application gets.
Helpful first, if these ideas are unfamiliar
These pictures are analogies to help you learn. The linked RFC explains the actual rules.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
In a 4096-octet example, 512-byte blocks need eight full DATA packets plus the empty final DATA: nine DATA/ACK exchanges. At 1024, four full DATA plus one empty final DATA need five exchanges. These exact counts include the end marker, not a claim of exactly half as many in every file.
- In a 4096-octet example, 512-byte blocks need eight full DATA packets plus the empty final DATA: nine DATA/ACK exchanges. At 1024, four full DATA plus one empty final DATA need five exchanges. These exact counts include the end marker, not a claim of exactly half as many in every file.
- A chosen IPv4 example with no IP options uses20 IP +8 UDP +4 TFTP header octets. A 1468-octet DATA payload then fits an IP MTU 1500. Different headers, paths and encapsulations change that budget.
- The published foobar request uses 1428; it is a valid example, not a universal 1500-minus-minimum-headers formula. Blocks above path MTU can cause IP fragmentation/reassembly and extra overhead. Negotiation itself performs no path-MTU discovery.
- The proof-of-concept timings describe a particular historical test setup, not guaranteed performance today. TFTP and this option add no authentication or encryption; use an appropriate protected environment or another protocol when those protections are needed.
A selected octet-mode example, not a complete TFTP implementation. One octet is an eight-bit byte. Follow the actual RFC source and its companion option-negotiation rules.
Read the RFC section ↗