Level III Server Protocol for the Lincoln Laboratory 360/67 Host
RFC 109

Document Type RFC - Unknown (March 1971; No errata)
Last updated 2013-03-02
Stream Legacy
Formats plain text html pdf htmlized bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 109 (Unknown)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          J. Winett
Request for Comments: 109                         MIT Lincoln Laboratory
NIC: 5805                                                  24 March 1971

          Level III Server Protocol for the Lincoln Laboratory
                              360/67 Host


   This material has not been reviewed for public release and is
   intended only for use with the ARPA network.  It should not be quoted
   or cited in any publication not related to the ARPA network.


   The Lincoln Laboratory IBM 360/67 is connected to the ARPA network
   and acts as a serving host providing access to the CP-67 virtual
   machine operating system.  Upon completion of the Login procedure,
   users have control of a 360 virtual machine through a virtual 1052
   online console.  Attached to the virtual machine is a virtual card
   reader, card punch and line printer, and a number of disk storage
   devices.  The 360 virtual machine can be either a virtual 360/67 with
   dynamic address translation hardware or a standard System/360.  Most
   users run a standard 360 with 256K bytes of virtual memory and
   operate the CMS conversational monitor system.  CMS provides
   facilities for file creation, maintenance and manipulation, program
   development, debugging and execution, and a number of other useful
   utility functions.  The section in the Network Notebook on the
   Lincoln Laboratory 360/67 more fully describes the facilities

Network Control Program

   All communication with the 360/67 through the IMP are processed by a
   Network Control Program (NCP).  The NCP operates with the Host-Host
   Protocol described in the Network Working Group Document No. 1 dated
   3 August 1970.

Initial Connection Protocol

   To create a virtual machine from the network, a pair of connections
   must be made with the LOGGER.  The sockets to be used are assigned
   following the Initial Connection Protocol (ICP).  The LOGGER is
   enabled and waiting for an RTS control command for socket X'0A 0000
   01'.  This ICP socket corresponds to home X'0A', user X'0000', and
   tag X'01' (send gender).  Requests for connection on the ICP socket
   are stacked until it becomes free.  If the LOGGER is willing to

Winett                                                          [Page 1]
RFC 109                 Level II Server Protocol           24 March 1971

   service another network user, a 32 bit socket ID of a receive socket
   will be sent over this initial connection and the ICP socket will
   then be closed.  If the LOGGER is not willing to service another
   network user, it will not complete the initial connection for the ICP
   socket and will refuse the request by closing the connection without
   completing it.

LOGGER Protocol

   Once a pair of user sockets have been assigned, the connection
   protocol should be completed on these sockets.  The LOGGER then
   expects to receive (on the receive socket) one 8-bit byte indicating
   the data type which characterizes the transmission code used to
   communicate with the network user over this pair of sockets.  A code
   of X'01' implies 7 bit ASCII code in 8-bit bytes with the leading bit
   zero.  A code of X'02' implies 8-bit EBCDIC code.  When the data type
   code is received, the LOGGER will echo back the data type code over
   the send socket followed by the message:


   in the appropriate code.  (In ASCII, NL is transmitted as CR LF).

   The procedure continues according to the normal CP-67 login protocol
   with the LOGGER performing an additional function of mapping network
   userids and passwords into valid CP-67 userids and passwords.  This
   mapping is specified by entries in a file (the LOGGER FILE) which the
   LOGGER accesses.  If a network userid does not match an entry in the
   file or if the password given does not match the corresponding
   network password, the usual CP responses will be sent to the users.
   Thus network access to the Lincoln Laboratory system is restricted to
   those accounts for which an appropriate entry has been made in the

   It should be noted that CP transmits a BYP code (Bypass) to suspend
   the printing of characters keyed while a password is being entered.
   After the password has been entered, CP transmits a RES code
   (Restore) to resume the printing when characters are keyed.  When
   communicating in ASCII, these character codes are converted to X'FF'
   since no corresponding ASCII code is defined.  Refer to the Network
   Resource Notebook for more details on CP-67 and on CMS.

The NET Account

   Lincoln Laboratory is providing one account which can be used by
   network users to familiarize themselves with our time-sharing system.
   The userid of this account is NET and the password is ARPA.  This
   account has 900 records of storage, which can store approximately
Show full document text