Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!killer!ames!ncar!gatech!dcatla!dnwcv From: dnwcv@dcatla.UUCP (William C. VerSteeg) Newsgroups: comp.protocols.tcp-ip Subject: TFTP mode strings Summary: What values are used for TFTP file types ? Message-ID: <6549@dcatla.UUCP> Date: 11 Jul 88 14:57:04 GMT References: <8807082155.AA03962@uc.msc.umn.edu> <438@helios.ee.lbl.gov> Reply-To: dnwcv@sune.UUCP (William C. VerSteeg) Organization: DCA Inc., Alpharetta, GA Lines: 21 I am writing a TFTP file transfer program for a proprietary communications server. There appears to be some discrepancy between the TFTP document (IEN 133) and the packages that I have seen in use. Basically, the IEN calls for three type of files- netascii, binary, and mail. In addition to these types, I have seen "image", "octet", and "test" in the MIT package for the PC. I am not sure, but I think that I have seen other modes in other packages. My intent is to support netascii and binary file transfers. Mail mode is not well defined for my communications server (we have no embedded mail facility). The test mode also doesn't apply for this application. This leads me to my question. What other text strings should I expect to see in the mode field of a TFTP file access request? Is IEN 133 (dated Jan. 29 1980) the correct document to be referencing ? If it is, why are there conflicting text strings for binary mode ? Thanks Bill VerSteeg