Some Network Information Center policies on handling documents
RFC 115

Document Type RFC - Unknown (April 1971; No errata)
Last updated 2013-03-02
Stream Legacy
Formats plain text pdf html bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 115 (Unknown)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         R. Watson
Request for Comments: 115                                      J. North
NIC 5822                              Stanford Research Institute (ARC)
                                                          16 April 1971

     SOME NETWORK INFORMATION CENTER POLICIES ON HANDLING DOCUMENTS

INTRODUCTION

   The Network Information Center (NIC) seeks to facilitate the flow of
   information between sites on the Network and to and from other
   stations whose work makes them valuable as participants in the
   Network dialog.  The NIC is concerned both with the techniques for
   the flow and with optimizing the content of the information itself.
   Some aspects of the work of the NIC in support of information flow
   are described here, and some suggestions made to Network participants
   of ways they can help this work.

   All information handled by the NIC is available to any Network
   participant.  All information generated by the NIC is unclassified
   and is without distribution limitation except as dictated by staff
   and budget size.  Any information sent by an originating party to the
   NIC for recording or distribution is presumed to be unclassified and
   without distribution limitations as well.  Any statement carried by a
   document thus submitted which seems to imply a limitation on
   distribution, quotation, or citation is presumed not to apply to its
   handling by the Network Information Center.

NIC NUMBER

   One important function of the Network Information Center is to make
   records of the existence of RFC's, formal NIC-related manuals and
   reports, Network memos, other Network informational items, and other
   informational items of interest to Network participants, and to index
   these records so that such items can be recalled when needed.

   To tag the informational items a serial number is assigned by NIC.
   The serial number has no intrinsic meaning, not even necessarily an
   indication of sequence of issue.  It is a unique identifier and can
   be used to refer to the item in further communications, to facilitate
   indexing, and to allow numeric filing of documents.

Watson & North                                                  [Page 1]
RFC 115              Policies on Handling Documents        16 April 1971

   Use of the NIC number has advantages in online dialog which are not
   yet demonstrable around the Network, but the cooperation of Network
   participants in applying one when a document is originated is
   important.

THE NIC CATALOG

   Items of information relevant to the Network appear in many forms,
   including technical reports, RFC's, brief network memos, journal
   articles, and letters.  Reference to these is simplified by
   assignment of a NIC number to each.  To record the item to which the
   NIC number refers, a description of each item, using a set of
   standard data elements, i.e, author, title, etc., is coded and
   entered as an online system (NLS) statement into a machine file.

   An example of a statement with typical coded data elements:

         (A5480) *a1 James E. White #2 org *b2 University of California
         at Santa Barbara #3 Computer Research Laboratory #5 Santa
         Barbara, California *c1 An NCP for the ARPA Network #6 142p.
         *d1 21 December 1970 *f1 r *f2 o *rl UCSB CRL 12 *31 ARPA #6 AF
         19628-70-0-0314 *w2 3-11-71 *y1 Describes program designed and
         implemented at Santa Barbara node of ARPA Network, written in
         assembly language and implemented on 360/75.  Discusses
         interface with hardware, software, and operator. *y3 Host-
         Interface protocol; Host-IMP protocol; User-NCP protocol;
         Host-Host protocol; Host-IMP messages, IMP-Host messages *z1
         all *z2 NIC *z3 new *

   The group of files at ARC containing these statements of data about
   NIC items and other informational items is the Master Catalog.  The
   term NIC Catalog refers to the machine file created by collecting the
   statements coded *z2 NIC in the Master Catalog.

   The data element *z1 indicates which Stations hold a copy of an item;
   not all items related to NIC are sent to Stations, and in the future
   it is expected that Stations will submit many documents to NIC for
   cataloging which are not held by other Stations.

Watson & North                                                  [Page 2]
RFC 115              Policies on Handling Documents        16 April 1971

NIC CATALOG LISTINGS AND INDEXES

   Programs have been written at ARC to collect, sort, analyze and
   format the statements and the data elements in the statements to
   produce catalogs and indexes such as those in the Current Catalog of
   the NIC Collection, NIC (5145,).

   The Current Catalog of the NIC Collection is a functional document,
   as explained in Branch 3 below.  It has as its contents, at any time,
   the current issue of a bibliography of items from the NIC Catalog,
Show full document text