home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
drafts
/
draft_n_r
/
draft-rfced-exp-polites-00.txt
< prev
next >
Wrap
Text File
|
1996-08-16
|
3KB
|
68 lines
A new Request for Comments is now available in online RFC libraries.
RFC 1986:
Title: Experiments with a Simple File Transfer Protocol
for Radio Links using Enhanced Trivial File
Transfer Protocol (ETFTP)
Author: W. Polites, W. Wollman, D. Woo & R. Langan
Date: August 1996
Mailbox: wpolites@mitre.org, wwollman@mitre.org,
dwoo@mitre.org, langanr@doim6.monmouth.army.mil
Pages: 21
Characters: 49,772
Updates/Obsoletes: none
URL: ftp://ds.internic.net/rfc/rfc1986.txt
This document is a description of the Enhanced Trivial File Transfer
Protocol (ETFTP). This protocol is an experimental implementation of
the NETwork BLock Transfer Protocol (NETBLT), RFC 998 [1], as a file
transfer application program. It uses the User Datagram Protocol
(UDP), as its transport layer. The two protocols are layered to create
the ETFTP client server application. The ETFTP program is named after
Trivial File Transfer Protocol (TFTP), because the source code from
TFTP is used as the building blocks for the ETFTP program. This
implementation also builds on but differs from the work done by the
National Imagery Transmission Format Standard. This document is
published for discussion and comment on improving the throughput
performance of data transfer utilities over Internet Protocol (IP)
compliant, half duplex, radio networks.
This memo defines an Experimental Protocol for the Internet community.
This memo does not specify an Internet standard of any kind.
Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@ISI.EDU
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU. Please consult RFC 1543, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds
USC/Information Sciences Institute