| 1 |
<pre>Network Working Group G. Malkin |
| 2 |
Request for Comments: 1785 Xylogics, Inc. |
| 3 |
Updates: <a href="./rfc1350">1350</a> A. Harkin |
| 4 |
Category: Informational Hewlett Packard Co. |
| 5 |
March 1995 |
| 6 |
|
| 7 |
|
| 8 |
<span class="h1">TFTP Option Negotiation Analysis</span> |
| 9 |
|
| 10 |
Status of this Memo |
| 11 |
|
| 12 |
This memo provides information for the Internet community. This memo |
| 13 |
does not specify an Internet standard of any kind. Distribution of |
| 14 |
this memo is unlimited. |
| 15 |
|
| 16 |
Abstract |
| 17 |
|
| 18 |
The TFTP option negotiation mechanism, proposed in [<a href="#ref-1" title=""TFTP Option Extension"">1</a>], is a |
| 19 |
backward-compatible extension to the TFTP protocol, defined in [<a href="#ref-2" title=""The TFTP Protocol (Revision 2)"">2</a>]. |
| 20 |
It allows file transfer options to be negotiated prior to the |
| 21 |
transfer using a mechanism which is consistent with TFTP's Request |
| 22 |
Packet format. The mechanism is kept simple by enforcing a request- |
| 23 |
respond-acknowledge sequence, similar to the lock-step approach taken |
| 24 |
by TFTP itself. |
| 25 |
|
| 26 |
This document was written to allay concerns that the presence of |
| 27 |
options in a TFTP Request packet might cause pathological behavior on |
| 28 |
servers which do not support TFTP option negotiation. |
| 29 |
|
| 30 |
Test Results |
| 31 |
|
| 32 |
A TFTP client, modified to send TFTP options, was tested against five |
| 33 |
unmodified servers: |
| 34 |
|
| 35 |
DEC DEC 3000/400 alpha OSF1 V3.0 |
| 36 |
SGI IP17 mips IRIX 5.2 |
| 37 |
SUN sun4c sparc SunOS 5.1 |
| 38 |
IBM RS/6000 Model 320 AIX 3.4 |
| 39 |
SUN sun4m SunOS 4.1.3 |
| 40 |
|
| 41 |
In each case, the servers ignored the option information in the |
| 42 |
Request packet and the transfer proceeded as though no option |
| 43 |
negotiation had been attempted. In addition, the standard BSD4.3 |
| 44 |
source for TFTPD, the starting point for many implementations, was |
| 45 |
examined. The code clearly ignores any extraneous information in |
| 46 |
Request packets. |
| 47 |
|
| 48 |
From these results and examinations, it is clear that the TFTP option |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Malkin & Harkin [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1785">RFC 1785</a> TFTP Option Negotiation Analysis March 1995</span> |
| 55 |
|
| 56 |
|
| 57 |
negotiation mechanism is fully backward-compatible with unmodified |
| 58 |
TFTP servers. |
| 59 |
|
| 60 |
Security Considerations |
| 61 |
|
| 62 |
Security issues are not discussed in this memo. |
| 63 |
|
| 64 |
References |
| 65 |
|
| 66 |
[<a id="ref-1">1</a>] Malkin, G., and A. Harkin, "TFTP Option Extension", <a href="./rfc1782">RFC 1782</a>, |
| 67 |
Xylogics, Inc., Hewlett Packard Co., March 1995. |
| 68 |
|
| 69 |
[<a id="ref-2">2</a>] Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, <a href="./rfc1350">RFC 1350</a>, |
| 70 |
MIT, July 1992. |
| 71 |
|
| 72 |
Related Documents |
| 73 |
|
| 74 |
Malkin, G., and A. Harkin, "TFTP Blocksize Option", <a href="./rfc1783">RFC 1783</a>, |
| 75 |
Xylogics, Inc., Hewlett Packard Co., March 1995. |
| 76 |
|
| 77 |
Malkin, G., and A. Harkin, "TFTP Timeout Interval and Transfer Size |
| 78 |
Options", <a href="./rfc1784">RFC 1784</a>, Xylogics, Inc., Hewlett Packard Co., March |
| 79 |
1995. |
| 80 |
|
| 81 |
Authors' Addresses |
| 82 |
|
| 83 |
Gary Scott Malkin |
| 84 |
Xylogics, Inc. |
| 85 |
53 Third Avenue |
| 86 |
Burlington, MA 01803 |
| 87 |
|
| 88 |
Phone: (617) 272-8140 |
| 89 |
EMail: [email protected] |
| 90 |
|
| 91 |
|
| 92 |
Art Harkin |
| 93 |
Internet Services Project |
| 94 |
Information Networks Division |
| 95 |
19420 Homestead Road MS 43LN |
| 96 |
Cupertino, CA 95014 |
| 97 |
|
| 98 |
Phone: (408) 447-3755 |
| 99 |
EMail: [email protected] |
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
Malkin & Harkin [Page 2] |
| 109 |
</pre> |