Proposal to consider a network program resource notebook
A proposal for the NIC to collect information about network programs.
Deutsch, L.P., "Proposal to consider a network program resource notebook", RFC 446, DOI 10.17487/RFC0446, January 1973, <https://www.rfc-editor.org/info/rfc446>.
@misc{rfc446,
series = {Request for Comments},
number = 446,
howpublished = {RFC 446},
publisher = {RFC Editor},
doi = {10.17487/RFC0446},
url = {https://www.rfc-editor.org/info/rfc446},
author = {L.P. Deutsch},
title = {{Proposal to consider a network program resource notebook}},
pagetotal = 2,
year = 1973,
month = jan,
} RFC text
Network Working Group L. Peter Deutsch
RFC # 446 SRI
NIC # 14068 January 25, 1973
Proposal to consider a Network Program Resource Notebook
The recent requests by Jean Iseli of MITRE for information about all
resources of type X available on the network (where X=macro processors,
data management systems, and electromagnetic wave analysis programs)
lead me to suggest that the NIC be a repository for the replies.
Since the exchange of knowledge and techniques (not to mention
programs) is a central motivating factor in the development of the
ARPANET, it seems only reasonable that we begin to systematize the
process now that someone (MITRE and the government agencies on whose
behalf it is acting) feels there is enough information to be worth
collecting.
Obviously, the network community should be in a position to profit
from such compilation at least as much as outside agencies.
The NIC already has catalog and keyword capabilities for the Journal and
a large index of computer-related documents which are not on-line. I
would presume that extending this system to include programs and
documentation would not be a major task and would probably bring
immediate payoffs in terms of increased effectiveness of research sites.
This suggestion does not touch on the important larger issue, namely,
what obligations does the network community have to act as a service and
information resource to the outside world (government agencies in
particular) as opposed to its presumed major function of learning about
how to build and use computer networks and its actual major function of
research in many areas of computing which have nothing to do with
networks at all.
I feel that the confusion between the ARPANET as a service network
and the ARPANET as an experiment in the line of network research,
and the frustrations and communication failures resulting from
superimposing network responsibilities on top of existing research
projects, have not received adequate contemplation by the network
community.
I also feel that the ambiguous status of the network has lead to a
sharp division between research/maintenance sites and government
agency user sites, a situation which only can exacerbate my own
feeling that to some extent the former are being exploited for non-
research purposes in a manner that has been fairly rare in the
history or ARPA/IPT.
[ 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 ]
ISO Plain Language
On this page
§1A Place to Find Network Programs
Requests for information about network resources, including macro processors, data management systems, and electromagnetic wave analysis programs, prompted this proposal. L. Peter Deutsch suggests that the Network Information Center (NIC) collect the replies.
The document proposes organizing knowledge and techniques, as well as programs, so that the network community can find them.
Researchers were asking which programs were available on the network. The proposal asks the NIC to collect and organize the answers.
§2Extending the NIC's Catalog
The NIC already had catalog and keyword facilities for the Journal and an index of computer-related documents that were not online. Deutsch argues that the system could be extended to cover programs and documentation.
He expects such an extension would not require major effort and could help research sites find resources, but frames this as a proposal.
The NIC already cataloged documents. Deutsch suggests adding information about programs and their documentation.
§3Research Network or Information Service
The RFC raises a wider question about the network community's obligations to outside users, including government agencies. It contrasts that role with the ARPANET's stated function as a network research experiment and with research in computing more broadly.
Deutsch says the network's status as both a service network and a research effort creates confusion and frustration. The note invites consideration of that tension.
The author asks whether the ARPANET should mainly support research or also provide information services to outside organizations. He says the community has not adequately considered this tension.