RFCs in HTML Format


RFC 1785

                    TFTP Option Negotiation Analysis

Test Results

   A TFTP client, modified to send TFTP options, was tested against five
   unmodified servers:

      DEC   DEC 3000/400 alpha   OSF1 V3.0
      SGI   IP17 mips            IRIX 5.2
      SUN   sun4c sparc          SunOS 5.1
      IBM   RS/6000 Model 320    AIX 3.4
      SUN   sun4m                SunOS 4.1.3

   In each case, the servers ignored the option information in the
   Request packet and the transfer proceeded as though no option
   negotiation had been attempted.  In addition, the standard BSD4.3
   source for TFTPD, the starting point for many implementations, was
   examined.  The code clearly ignores any extraneous information in
   Request packets.

   From these results and examinations, it is clear that the TFTP option



Malkin & Harkin                                                 [Page 1]

RFC 1785 TFTP Option Negotiation Analysis March 1995 negotiation mechanism is fully backward-compatible with unmodified TFTP servers. Security Considerations Security issues are not discussed in this memo. References [1] Malkin, G., and A. Harkin, "TFTP Option Extension", RFC 1782, Xylogics, Inc., Hewlett Packard Co., March 1995. [2] Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, RFC 1350, MIT, July 1992.



Back to RFC index

 

Associates:

 



Sponsered-Sites:

Register domain name and transfer | Cheap webhosting service | Domain name registration

 

 

""