The RFC Archive
0001+ 0101+ 0201+ 0301+ 0401+ 0501+ 0601+ 0701+ 0801+ 0901+ 1001+ 1101+ 1201+ 1301+ 1401+ 1501+ 1601+ 1701+ 1801+ 1901+ 2001+ 2101+ 2201+ 2301+ 2401+ 2501+ 2601+ 2701+ 2801+ 2901+ 3001+ 3101+ 3201+ 3301+ 3401+ 3501+ 3601+ 3701+ 3801+ 3901+ 4001+ 4101+ 4201+ 4301+ 4401+ 4501+ 4601+ 4701+ 4801+ 4901+ 5001+ 5101+ 5201+ 5301+

File Transfer and Error Recovery






Network Working Group                                      R. L. Sunberg
Request for Comments: 133                             Harvard University
NIC 6710                                                   27 April 1971
[Categories C.4, C.5, C.6, D.4, D.7, D.7]


                    FILE TRANSFER AND ERROR RECOVERY


1   FILE TRANSFER PROTOCOL

1A   Handshaking

   I think that Mr Bhushan(RFC #114, NIC 5823) is not strict enough in
   his concept of a transaction sequence.  Every transaction should
   prompt a response from its recipient (recall Kalin's crates --
   RFC #60, NIC 4762).  Control should pass back and forth until the
   server terminates.  The server _always_ gets the last word (more on
   error recovery later).

   Some sample interchanges are given.

       User                Server       Comments

       <...>       ==>                  Establish a connection
                   <==     <...>
       <...>    ==>                  Identify self
                   <==     <+>          Ok, ready

       <...>    ==>                  Retrieval request
                   <==              I've got your file
               ==>                  Send it
                   <==     <,><...>     Here's the first part
               ==>                  Got it
                   <==     <+>          All done

       <...>    ==>                  Store request
                   <==              Ok, go ahead