RFC250 Some thoughts on file transfer

0250 Some thoughts on file transfer. H. Brodie. October 1971. (Format: TXT=2446 bytes) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

Network Working Group                             H. Brodie
Request for Comments #250                         UCLA-NMC
NIC #7691                                         Computer Science
Categories:  D5, D7                               7 October 71
Updates:  None
Obsoletes:  None

                     Some Thoughts on File Transfer

   There are several aspects of the proposed Data Transfer Protocol (RFC
   #171) and File Transfer Protocol (RFC #172) which we believe could
   use further clarification and perhaps revision.  Interest in
   transferring larger amounts of data than is typically sent via the
   usual TELNET connection is increasing, and at least at UCLA-NMC
   implementation attempts have pointed out several difficulties with
   the proposed protocols.

   First, and probably most easily decided, is the ambiguity in RFC #171
   with regards to the sequence number field of the descriptor and count
   transaction.  The description provided for the transaction header
   provides for 16 bit sequence number.  However, the sequence number
   field in the error codes transaction only provides for 8 bits.  We
   are of the opinion that 8 bits is sufficient for a sequence number
   field.  If the sequence number is reduced to 8 bits, and the two NUL
   bytes are deleted from the descriptor and count header, then its size
   is reduced to 48 bits, which would seem to be as convenient to handle
   as the proposed 72 bit transaction header.

   Another source of difficulty lies in the implementation of the (the
   SEX time-sharing system) the 'end' of a file (which presumably would
   be the begin point of an Append transaction) is almost com- pletely
   context-defined--i.e., the program reading the file determines when
   it has reached the end of the file.  Therefore, the meaning of
   'Append' is somewhat hazy, and since the proposed Mail Box Protocol
   uses the Append feature, not implementing this command in a File
   Transfer service is costly in terms of lost useability.

   We believe that resolution of these ambiguities will lead to a
   greatly accelerated implementation schedule, at least here at UCLA-
   NMC.

       [ This RFC was put into machine readable form for entry ]
       [ into the online RFC archives by BBN Corp. under the   ]
       [ direction of Alex McKenzie.                   12/96   ]







                                                                [Page 1]

一覧

 RFC 1〜100  RFC 1401〜1500  RFC 2801〜2900  RFC 4201〜4300 
 RFC 101〜200  RFC 1501〜1600  RFC 2901〜3000  RFC 4301〜4400 
 RFC 201〜300  RFC 1601〜1700  RFC 3001〜3100  RFC 4401〜4500 
 RFC 301〜400  RFC 1701〜1800  RFC 3101〜3200  RFC 4501〜4600 
 RFC 401〜500  RFC 1801〜1900  RFC 3201〜3300  RFC 4601〜4700 
 RFC 501〜600  RFC 1901〜2000  RFC 3301〜3400  RFC 4701〜4800 
 RFC 601〜700  RFC 2001〜2100  RFC 3401〜3500  RFC 4801〜4900 
 RFC 701〜800  RFC 2101〜2200  RFC 3501〜3600  RFC 4901〜5000 
 RFC 801〜900  RFC 2201〜2300  RFC 3601〜3700  RFC 5001〜5100 
 RFC 901〜1000  RFC 2301〜2400  RFC 3701〜3800  RFC 5101〜5200 
 RFC 1001〜1100  RFC 2401〜2500  RFC 3801〜3900  RFC 5201〜5300 
 RFC 1101〜1200  RFC 2501〜2600  RFC 3901〜4000  RFC 5301〜5400 
 RFC 1201〜1300  RFC 2601〜2700  RFC 4001〜4100  RFC 5401〜5500 
 RFC 1301〜1400  RFC 2701〜2800  RFC 4101〜4200 

スポンサーリンク

HAVING句 集計関数の結果を条件とした絞込み

ホームページ製作・web系アプリ系の製作案件募集中です。

上に戻る