Sollins, K., "The TFTP Protocol (Revision 2)", RFC 783, NIC, June 1981. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
First 50 documents
FIRE: Flexible Intra-AS Routing Environment - Partridge, Snoeren, Strayer.. (2001) (8 citations) (Correct)
....receipt of the OCM, a node retrieves the listed OCFs from one of the file repositories specified in the OCM. File retrieval is facilitated by a special, simple file transfer protocol called the Large Data Transfer Protocol (LDTP) This protocol is based on the Trivial File Transfer Protocol (TFTP) [33], altered to run over FLINT and enhanced to protect against insertion attacks and reduce its vulnerability to Denial of Service attacks. When an OCF is retrieved from a file repository, the OCF is parsed and any additional support files downloaded. In particular, the OCF contains the a list of ....
K. SOLLINS, "The TFTP protocol (revision 2)," RFC 1350 (Jul 1992).
Meet-Me Service - Mahadevan, Ordille (2001) (Correct)
....the internal network. A communication session is a TCP connection or a series of related UDP messages between the same source and destination ports. A UDP session might be a simple request response pair of messages, an RTP[8] audio stream or other sessions between the same pair of ports as in TFTP [12]. Traditional NATs are often used in conjunction with firewalls, because they protect the enterprise from incoming session initiations. Traditional NATs are of two flavors: basic NATs and Network Address Port Translators (NAPTs) In basic NATs, a block of external IP addresses is available for ....
Sollins, K, "The TFTP Protocol (Revision 2)," RFC 1350, July 1992.
RadioNet Driver Implementation for the Mobile INTernet Router.. - Guerin (1994) (3 citations) (Correct)
.... (5=error) opcode (1=RRQ) 2=WRQ) filename mode error message 0 0 0 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 1byte N bytes N bytes N bytes 0 512 bytes TFTP message IP datagram UDP datagram 1byte 1byte Mobile INTernet Router Radio Device Driver page 23 TFTP [9][11] is a file transfer protocol implemented on top of UDP and is designed to be small and easy to implement, and to fit into ROM. TFTP is used by BOOTP when bootstrapping a diskless system (such as MINT or any X terminal) The only thing it can do is read and write files from to a remote server. ....
K. R. Sollins, "The TFTP Protocol (Revision 2)", RFC-783, June 1981.
Encouraging the Unexpected: Cluster Management for OS and.. - Cunniffe, Coghlan (Correct)
....non standard way. Most PC Ethernet cards have a socket for a bootrom , which can be recognised by the normal boot sequence and invoked before any other bootable device. This bootrom sends a BOOTP [8] request to find the machine s own identity and the name of a file to download, and then uses TFTP [9] to download it. Once downloaded, that file is executed. Obviously, if two different files are downloaded on two successive boots, the compute node will boot differently. This is what MultiOS does, alternating between two executables. The first executable is the management environment; the second ....
Sollins, K., "The TFTP Protocol (Revision 2)", IETF Request For Comments Document no.1350, July 1992.
Mach 3.0 as an Operating System for the MINT - Klemets (Correct)
....instance, if the MINT uses NFS to access its files, it may not work together with a mobile computer that is not an NFS server, such as a Macintosh. Our current solution is a compromise. The MINT does rely on the mobile workstation to download the operating system and its files, but it uses TFTP[17], a standardized and simple to implement file transfer protocol. As opposed to NFS and other filesystems, TFTP does not need to be implemented in the kernel, or require any special kernel support, on the mobile workstation. The reason for this is that TFTP is nothing but a plain file transfer ....
K. R. Sollins, "The TFTP Protocol (Revision 2)", RFC-783, June 1981.
A Novel Approach to Reduce Latency on the Internet.. - Noghani, Kretchmen.. (Correct)
....to ensure a reliable virtual connection. Slowness of TCP has been the motivation for designing faster application protocols. This has been achieved as a trade off loosing the data integrity i.e. no guarantee that the user receives all the packets. For example TFTP (Trivial File Transfer Protocol) [Sol92] uses UDP, as its transport level service, to move files around with no reliability guarantee. Or, ARDP (Asynchronous Reliable Delivery Protocol) ISI] which is a protocol developed by University of Southern California, for reliable transmission of data over UDP. In the next section we introduce ....
K. Sollins, "The TFTP Protocol (Revision 2)", IETF, RFC 1350, MIT, July 1992.
Unknown - (Correct)
No context found.
Sollins, K., "The TFTP Protocol (Revision 2)", RFC 783, NIC, June 1981.
Unknown - (Correct)
No context found.
Sollins, K., "The TFTP Protocol (Revision 2)", RFC 783, NIC, June 1981.
Network Working Group G. Malkin Request for Comments: 1782.. - Status Of This (Correct)
No context found.
Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, RFC 1350, MIT, July 1992.
Network Working Group G. Malkin Request for Comments: 1783.. - Status Of This (Correct)
No context found.
Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, RFC 1350, MIT, July 1992.
Network Working Group A. Emberson Request for Comments: 2090.. - Status Of This (Correct)
No context found.
Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, RFC 1350, MIT, July 1992.
Unknown - Status Of This (Correct)
No context found.
Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, RFC 1350, MIT, July 1992.
Network Working Group G. Scott, Editor Request for.. - Guide For Internet (Correct)
No context found.
Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, RFC 1350, July 1992.
Unknown - (Correct)
No context found.
Sollins, K., "The TFTP Protocol (Revision 2)", RFC 783, MIT, June 1981.
Unknown - (Correct)
No context found.
Sollins, K., "The TFTP Protocol (Revision 2)", RFC 783, MIT/LCS, June 1981.
Unknown - (Correct)
No context found.
Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, RFC 1350, July 1992.
Unknown - (Correct)
No context found.
Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, RFC 1350, July 1992.
Network Working Group J. Postel Request for Comments: 879.. - And Related Topics (Correct)
No context found.
Sollins, K., "The TFTP Protocol (Revision 2)", RFC 783, MIT/LCS, June 1981.
Unknown - (Correct)
No context found.
Sollins, K., "TFTP Protocol (revision 2)", RFC 1350, July 1992.
Network Working Group G. Malkin Request for Commments: 2347.. - Status Of This (Correct)
No context found.
Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, RFC 1350, October 1992.
Network Working Group G. Malkin Request for Commments: 2348.. - Status Of This (Correct)
No context found.
Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, RFC 1350, October 1992.
Unknown - Status Of This (Correct)
No context found.
Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, RFC 1350, October 92.
Network Working Group E. Lear Request for Comments.. - Applicability.. (Correct)
No context found.
Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, RFC 1350, July 1992.
Unknown - (Correct)
No context found.
Sollins, K., "The TFTP Protocol (Revision 2)", RFC 783, NIC, June 1981.
Concurrent Programming in ERLANG - Armstrong, al. (1993) (230 citations) (Correct)
No context found.
Sollins, K. R., "The TFTP Protocol (Revision 2)", Request For Comment 783, June 1981.
First 50 documents
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC