Trivial File Transfer Protocol
Encyclopedia : T : TR : TRI : Trivial File Transfer Protocol
| Layer | Protocols |
|---|---|
| Application | DNS, TLS/SSL, TFTP, FTP, HTTP, IMAP, IRC, NNTP, POP3, SIP, SMTP, SNMP, SSH, TELNET, BitTorrent, RTP, rlogin, … |
| Transport | TCP, UDP, DCCP, SCTP, IL, RUDP, |
| Network | IP (IPv4, IPv6), ICMP, IGMP, ARP, RARP, … |
| Link | Ethernet, Wi-Fi, Token ring, Point-to-Point Protocol>PPP, SLIP, FDDI, ATM, DTM, Frame Relay, SMDS, … |
Trivial File Transfer Protocol (TFTP) is a very simple file transfer protocol, with the functionality of a very basic form of FTP; it was first defined in 1980.
Since it is so simple, it is easy to implement in a very small amount of memory, an important consideration at that time. TFTP was therefore useful for booting computers such as routers which did not have any mass storage devices. It is still used to transfer small files between hosts on a network, such as when a remote X Window System terminal or any other thin client boots from a network host or server.
TFTP is based in part on the earlier protocol EFTP, which was part of the PUP protocol suite. In the early days of work on the TCP/IP protocol suite, TFTP was often the first protocol implemented on a new host type, because it was so simple.
The original versions of TFTP, prior to RFC 1350, displayed a particularly bad protocol flaw, which was named Sorcerer's Apprentice Syndrome (after the Sorcerer's Apprentice segment of Fantasia) when it was discovered.
Technical information
Some details of TFTP:
- It uses UDP (port 69) as its transport protocol (unlike FTP which uses TCP port 21).
- It cannot list directory contents.
- It has no authentication or encryption mechanisms.
- It is used to read files from, or write files to, a remote server.
- It supports three different transfer modes, "netascii", "octet" and "mail", with the first two corresponding to the "ASCII" and "image" (binary) modes of the FTP protocol; the third is now obsolete and is hardly ever used.
- The original protocol has a file size limit of 32 MB, although this was extended when RFC 2347 introduced block-size negotiation in 1998 (allowing a maximum of 4 GB and potentially higher throughput).
- Since TFTP utilizes UDP, it has to supply its own transport and session support. Each file transferred via TFTP constitutes an independent exchange. That transfer is performed in lock-step, with only one packet (either a block of data, or an 'acknowledgement') ever in flight on the network at any time. Due to this lack of windowing, TFTP provides low throughput over high latency links.
- Due to the lack of security, it is dangerous over the open Internet. Thus, TFTP is generally only used on private, local networks.
Details of a TFTP session
- The initiating host A sends an RRQ (read request) or WRQ (write request) packet to host B, containing the filename and transfer mode.
- B replies with an ACK (acknowledgement) packet to WRQ and directly with a DATA packet to RRQ, which also serves to inform A of which port on host B the remaining packets should be sent to.
- The source host sends numbered DATA packets to the destination host, all but the last containing a full-sized block of data. The destination host replies with numbered ACK packets for all DATA packets.
- The final DATA packet must contain less than a full-sized block of data to signal that it is the last. If the size of the transferred file is an exact multiple of the block-size, the source sends a final DATA packet containing 0 bytes of data.
See also
Example command in tftp in Windows Transfers files to and from a remote computer running the TFTP service.TFTP [-i] host [GET | PUT] source [destination]
-i Specifies binary image transfer mode (also called octet). In binary image mode the file is moved literally, byte by byte. Use this mode when transferring binary files. host Specifies the local or remote host. GET Transfers the file destination on the remote host to the file source on the local host. PUT Transfers the file source on the local host to the file destination on the remote host. source Specifies the file to transfer. destination Specifies where to transfer the file.
References
- Karen R. Sollins, [The TFTP Protocol] (IEN 133, January, 1980)
- Karen R. Sollins, TFTP Protocol (revision 2) (RFC 783, June, 1981)
- Karen R. Sollins, TFTP Protocol (revision 2) (RFC 1350, July, 1992)
- R. Finlayson, Bootstrap loading using TFTP (RFC 906, June, 1984)
- Gary Malkin, A. Harkin, TFTP Option Negotiation Analysis (RFC 1785, March 1995)
- Gary Malkin, A. Harkin, TFTP Option Extension (RFC 2347, May 1998)
- Gary Malkin, A. Harkin, TFTP Blocksize Option (RFC 2348, May 1998)
- Gary Malkin, A. Harkin, TFTP Timeout Interval and Transfer Size Options (RFC 2349, May 1998)
External links
- [Tftpd32] TFTP Server and Client for Windows
- [WinAgents TFTP Server] TFTP Server for Windows
- [Tftp Manual on Unix]
- [Weird Solutions] Free TFTP servers and clients for Unix and Windows
- [Whitehorn TFTP Server] free multithreaded TFTP server
- [TFTP Server by Solarwinds]
- [Advanced TFTP server and client]
- [TFTP server by NetMechanica]
From Wikipedia, the Free Encyclopedia. Original article here. Support Wikipedia by contributing or donating.
All text is available under the terms of the GNU Free Documentation License See Wikipedia Copyrights for details.