Workshop on multi-site executive programs
Announcement of a workshop on unified command interfaces for ARPANET resources
Thomas, R., "Workshop on multi-site executive programs", RFC 471, DOI 10.17487/RFC0471, March 1973, <https://www.rfc-editor.org/info/rfc471>.
@misc{rfc471,
series = {Request for Comments},
number = 471,
howpublished = {RFC 471},
publisher = {RFC Editor},
doi = {10.17487/RFC0471},
url = {https://www.rfc-editor.org/info/rfc471},
author = {R. Thomas},
title = {{Workshop on multi-site executive programs}},
pagetotal = 2,
year = 1973,
month = mar,
} RFC text
Network Working Group Bob Thomas
Request for Comments: #471 BBN-TENEX
NIC #14800 March 13, 1973
Announcement Of A (Tentative) Workshop
On Multi Site Executive Programs
An executive program is one which accepts and interprets commands from a
user, calling upon other programs to provide the resources required to
satisfy each command. There is currently interest in making resources on
the ARPANET available to the user via a standard, conversational
facility which one might call an ARPANET Executive. With such a facility
a user at a Host site or a TIP could conveniently access a wide range of
resources at other sites without mastering the idiosyncrasies of each
Host operating system which is contributing resources.
For example, the ARPANET executive could make it possible to locate (by
name) a user logged in anywhere on the network and to establish a
teletype link to that user in order to engage in an on-line dialogue. It
could also provide status information on the subnet and on all Hosts,
on-line ARPANET news service, on-line collections of trouble reports,
etc. The range of possible services is practically unlimited once a
basic structure is devised for calling upon these services.
Major areas of interest here are:
1. How can the interfaces to resources of interest be standardized so
as to be accessible by "server" processes;
2. How can communications with such server processes be standardized?
(an ARPANET Executive protocol?)
3. To what extent can the conversational user interface be standardized
in the user processes? (an ARPANET Executive language?)
4. How can access authentication and accounting procedures be modified
to permit a user to "login" only once, yet use resources at many
Host sites?
If you are interested in discussing these and related issues forward
your name to Bob Thomas (BTHOMAS @BBN-TENEX), Bolt Beranek and Newman,
Inc., 50 Moulton Street, Cambridge, Massachusetts 02139, (617) 491-1850,
extension 483. If there is sufficient response, a Workshop (tentatively
planned for April) will be hosted by the BBN TENEX and BBN TIP groups.
The Workshop will permit participants to present relevant work and to
discuss the issues raised above.
In the meantime, an example of an executive program which interprets a
limited set of commands in a multi-site context is available for
experimental use by TIP and TENEX users. The "N" command of the TIP and
the RSEXEC (Resource Sharing Executive) subsystem on TENEX, provide
command interpretation in the context of TENEX and ITS sites. Users
whose access to the network is neither via a TIP or a TENEX may use the
RSEXEC by directing their user TELNET to ICP to socket 367 (Octal) at
BBN-TENEX.
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by Alex McKenzie with ]
[ support from GTE, formerly BBN Corp. 9/99 ]
AI ELI5
On this page
§1The Need for a Common Interface
Bob Thomas of BBN-TENEX announced a tentative workshop on multi-site executive programs. An executive program is one that accepts and interprets commands from a user and calls on other programs to provide needed resources. Thomas observed that the ARPANET community wanted to make diverse resources available to users through a standard, conversational facility called an ARPANET Executive. With such a facility, a user at any host or a TIP could conveniently access resources at other sites without needing to master each different host's operating system and command syntax.
Every computer on the network had its own weird way of doing things. The idea was to build a translator that everyone could use.
§2Capabilities and Applications
The ARPANET Executive could enable many services: locating a user by name anywhere on the network and establishing a teletype link for dialogue; providing status information on the subnet and all hosts; running an on-line ARPANET news service; maintaining on-line collections of trouble reports; and supporting practically unlimited additional services through a flexible framework. This vision anticipated many functions that would later be provided by email systems, web search, and messaging platforms.
With one control panel, you could find someone, send messages, check if computers were working, and read the news.
§3Key Design Questions
Thomas identified four major areas to address at the workshop. First, how could interfaces to diverse network resources be standardized so server processes could access them uniformly? Second, how could communication with such server processes be standardized, possibly through an ARPANET Executive protocol? Third, to what extent could the user-facing conversational interface be standardized, possibly through an ARPANET Executive language? Fourth, how could authentication and accounting be unified so a user could log in once and access resources at multiple sites?
The workshop would tackle four hard problems: making all computers understand the same commands, making a common language for them, protecting who can use what, and logging in just once.