RFC 217 UNKNOWN HOST SERVICES · REVISIONS

Specifications changes for OLS, RJE/RJOR, and SMFS

A 1971 UCSB note that retires one network service and adjusts two others to match protocol changes.

On rfc-editor.org ↗
PUBLISHED
September 1971
AUTHORS
J.E. White
STREAM
Legacy
BUILDS ON
RFC 74 — Specifications for Network Use of the UCSB On-Line System, RFC 105 — UCSB RJE, RFC 122 — UCSB SMFS
RJE SOCKET
x'201' (was x'200')
RJOR SOCKET
x'301' (was x'300')
REQUIRED BYTE SIZE
8, to the user's receive socket
DOI
10.17487/RFC0217

RFC text

Original text · RFC Editor View on rfc-editor.org ↗
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

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   ]

AI ELI5

On this page
PROBLEMThree UCSB network specifications (RFC 74, RFC 105 and RFC 122) no longer matched reality after changes to the Host-Host protocol and a lack of users.
MECHANISMThis note lists four revisions: RFC 74 is declared obsolete, the message type is dropped from RJE and RJOR, their listening sockets change, and byte sizes are fixed for the user connection.
WHAT CHANGEDIt updates RFC 105 and RFC 122 and marks RFC 74 as obsolete. The RFC itself is a short change notice, not a full protocol.

§1Three Documents Being Revised

RFC 217, written by James E. White at the University of California, Santa Barbara (UCSB), revises three earlier UCSB documents. They cover the On-Line System (OLS) in RFC 74, Remote Job Entry (RJE) and Remote Job Output Retrieval (RJOR) in RFC 105, and the Simple-Minded File System (SMFS) in RFC 122.

The note is dated 8 September 1971 and lists four numbered revisions.

It is a short note saying which of three old instruction sheets are out of date and what to change in them.

§2The Four Revisions

First, no network site is known to have written code for the OLS software documented in RFC 74. UCSB therefore stopped supporting it, and RFC 74 is declared obsolete.

Second, following Host-Host protocol changes, the notion of message type is dropped from RJE and RJOR. They no longer send, or expect to receive, 8 bits of zeros as the first byte on a connection.

Third, RJE and RJOR now use a standard ICP (initial connection protocol) to create a full duplex connection to the user. They listen on sockets x'201' and x'301' instead of x'200' and x'300'. RJOR still calls the user back over a simplex connection to the user's receive socket when requested output is ready.

One service is closed because nobody used it. The job services get new mailbox numbers and stop sending a pointless first byte.

§3Byte Sizes

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 of the other simplex connection. UCSB accepts any valid byte size there.

On the connection that carries data to you, the pieces must be eight bits wide. On the other one you can pick the size you like.

§4References