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

RFC217                                       8 September 71NIC 7547                                      James E. WhiteCategories:  G.3                      Computer Research Lab.Updates:  RFC105, RFC122               Univ. of CaliforniaObsoletes: RFC74                              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, RFC74, NIC 5417],     (2)  'Network Specifications for Remote Job Entry and          Remote Job Output Retrieval at UCSB' [22 March 71,          RFC105, NIC 5775], and     (3)  'Network Specifications for UCSB's Simple-          Minded File System' [26 APRil 71, RFC122,          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 RFC74 last October.  Accordingly,          UCSB has terminated support for that software,          and hence RFC74 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,          RFC105.  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 RFC105, 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          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 RFCwas put into machine readable form for entry ]       [ into the online RFCarchives by BBN Corp. under the   ]       [ direction of Alex McKenzie.                   12/96   ]