- ''EFTP is also the ICAO code for Tampere-Pirkkala airport
As with its descendant, TFTP, it did not use the reliable byte stream protocol of the suite (Byte Stream Protocol in the case of PUP); rather, it ran directly on top of the basic internetwork layer. (An early version of EFTP ran on top of bare Ethernet packets.) Also, like TFTP, it was a simple lock-step protocol; there was only ever one packet outstanding at any time, and every packet received by either party caused one packet to be sent in reply (until the termination of the transfer).
Since it was so simple, it was easy to implement in a very small amount of memory, an important consideration at that time. It was used for booting Xerox Altos over the Ethernet, and also to send files to the print spoolers of laser printers.
Unlike TFTP, however, it made no provisions for sending the file-name as part of transfers, so it could only be used either in places that didn't need a file name (as with spooling), or in conjunction with another protocol that provided the file-name (as in booting).
References
- John Shoch, EFTP: A PUP-based Ether File Transfer Protocol (Xerox PARC, Palo Alto, June 1976)
- Ed Taft, Spruce Protocols (Xerox PARC, Palo Alto, June 1979)
- Ed Taft, David Boggs, Alto Boot Protocol (Xerox PARC, Palo Alto, February 1979)
This article is licensed under the GNU Free Documentation License.
Last updated on Friday July 11, 2008 at 13:19:34 PDT (GMT -0700)
View this article at Wikipedia.org - Edit this article at Wikipedia.org - Donate to the Wikimedia Foundation
Copyright © 2008, Dictionary.com, LLC. All rights reserved.
