RFC217 Specifications changes for OLS, RJE/RJOR, and SMFS

0217 Specifications changes for OLS, RJE/RJOR, and SMFS. J.E. White. September 1971. (Format: TXT=2956 bytes) (Updates RFC0074, RFC0105, RFC0122) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

RFC 217                                       8 September 71
NIC 7547                                      James E. White
Categories:  G.3                      Computer Research Lab.
Updates:  RFC 105, RFC 122               Univ. of California
Obsoletes: RFC 74                              Santa Barbara


               Specification Changes for
               OLS, RJE/RJOR, and SMFS

     The following documents are hereby revised:

     (1)  'Specifications for Network Use of the UCSB
          On-Line System [16 October 70, RFC 74, NIC 5417],

     (2)  'Network Specifications for Remote Job Entry and
          Remote Job Output Retrieval at UCSB' [22 March 71,
          RFC 105, NIC 5775], and

     (3)  'Network Specifications for UCSB's Simple-
          Minded File System' [26 April 71, RFC 122,
          NIC 5834].

     Revisions are as follows:

     (1)  As far as can be determined, no Network site has
          written code to interface to the UCSB software
          documented in RFC 74 last October.  Accordingly,
          UCSB has terminated support for that software,
          and hence RFC 74 is obsolete.

     (2)  In accordance with subsequent Host-Host protocol
          changes, the notion of 'message type' has been
          dropped from the specifications for RJE and RJOR,
          RFC 105.  RJE/RJOR no longer send, nor expect to
          receive 8 bits of zeros as the first byte trans-
          mitted over a connection.

     (3)  In accordance with Document 2, RJE and RJOR now
          employ a standard ICP to create a full duplex
          connection to the user.  Accordingly, RJE and
          RJOR listen on sockets x'201' and x'301',
          respectively (rather than on x'200' and x'300'
          as before).  As documented in RFC 105, RJE
          required only a simplex connection to the user.
          A full duplex connection is now supported, but
          no data is transmitted to the user over the




                                                                [Page 1]

NIC 7547

          added simplex connection.  RJOR now also supports
          a full duplex connection.  However, if RJOR is
          required to call the user back when a requested
          job's output is ready, it still does so employing
          a simplex connection to the user's receive socket.

     (4)  RJE/RJOR and SMFS specify a byte size of
          eight for their connection to the user's
          receive socket.  The user may choose the
          byte size for the other simplex connection
          to suit himself;  any valid byte size is
          acceptable to UCSB.




       [ 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 2]

一覧

 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 

スポンサーリンク

ChiaのPlot(耕作)中の各フェーズの動作

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

上に戻る