📄 rfc101.txt
字号:
protocol and within several weeks a longer term protocol.
Thursday afternoon, February 18
Thursday afternoon was open to a presentation by the University of
Illinois on the ILLIAC IV and a demonstration of the Plato project.
The initial test in November of the transmission lines to the ILLIAC
IV processors indicated no timing problems. The ILLIAC IV hardware
is to be up the fall as is the software. The system will be located
in California at NASA Ames Research Center. The connection to the
network from the University of Illinois will be a PDP-11 with storage
CRTs, 2400 baud character CRTs, typewriters attached. It will have a
Gould Clevite printer, DECtapes and small disc. The B6500 at the
University will also be connected to the Network.
Thursday evening, February 18
The initial topic was a discussion of status and plans for the
Network Information Center. Dick Watson of SRI reviewed the present
off-line system consisting of a Station Agent and Network Liaison
person. The function of the Station Agent is to aid in the use of
the NIC services. The function of the Network Liaison person is to
be a point of contact for technical questions about his site which
may be asked by people at other sites, and to see that the
appropriate people see relevant documents and information received by
the site. If the network is really going to develop the feeling of a
community, people need to be aware of what people are doing and
thinking at the various sites. Therefore, people were encouraged to
send reports, memos, notes, records of conversations of general
interest through the NIC. Any kind of information can be sent
through the NIC from formal reports to informal handwritten notes.
In order to encourage people to send out initial thoughts and ideas
Watson [Page 10]
RFC 101 NOTES ON THE NETWORK WORKING GROUP MEETING February 1971
as well as those having had much thought, the question was raised as
to whether of not there should be titles for different classes of
documents which would help to make clear the level of informality or
formality of the communication.
There did not seem to be a need for such an arrangement. The
question of privacy and security was then raised. There was some
feeling among a few people that if letters or records of
conversations were entered in the NIC collection that there might
be compromise of some privacy. The NIC was asked if it would
check all parties involved in such a communication before entering
it in the collection. Dick felt that given NIC's resources, it
would be better if the parties involved gave their approval before
giving the letter or other communication to the NIC.
The initial online services to be provided by the NIC are access
to a typewriter version of the SRI-ARC On-Line system (NLS),
provision of a message service, access to the NIC catalog and
probably files of site status, network personnel, etc. Services
will be provided later to aid station agents in communities at
their sites. At the principal investigators meeting there seemed
to be considerable interest in having NIC obtain a collection of
ARPA project reports and working papers. To handle storage from
such an expanded collection, user of microfilm seemed important.
There are number of problems with use of microfilm, such as a
single or limited number of readers and need for hardcopy
facilities. The NIC will be looking into these problems and begin
experimenting with use of microfilm material.
The NIC is experimenting with remote access to NLS using an IMLAC
terminal. Considerable interest in graphic access to NIC was
indicated. The NIC feels graphic access is not an immediate high
priority requirement, but will as soon as possible provide
specifications to those sites with programming resources waiting
to experiment with graphic access.
Steve Crocker brought up the problem of how people are to gain
access and learn to use service facilities at various sites. The
question of what additional information needed to be included with
or appended to user documentation to use service facilities over
the network was discussed. The question of what material should
be in hardcopy, and what online was raised. The NIC will study
these problems and produce a set of recommended procedures for
handling user manuals, and a list of information needed to enable
network access.
Watson [Page 11]
RFC 101 NOTES ON THE NETWORK WORKING GROUP MEETING February 1971
Dick Watson indicated that users of the NIC would feel most
comfortable using typewriter terminals running at 30 char/sec and
having upper and lower case graphics, although service would be
available for slower terminals and terminals with single-case
graphics. RFC #97, NIC (5740), described an initial protocol for
connection to the NIC. As a result of the formation of a
committee to produce a standard typewriter connection protocol,
the protocol of RFC #97 will be modified to conform to an interim
protocol suggested by that committee. A new RFC will be issued
shortly with the interim protocol. Since the meeting the
typewriter connection protocol committee has decided not to issue
an interim protocol.
The discussion turned to file transfer between sites by name and
without users being required to log into each site involved in the
transfer. Gary Grossman of the University of Illinois will produce
an initial RFC on this subject.
Friday morning, February 19
There are several aspects of Data Management associated with the
network. The following aspects and the people responsible for them
were indicated:
Data Machine 10^12 bit store
Data Management Language
The Form Machine
ILLIAC IV Information Management System
Interim File System
File Transfer Protocol
The Data Machine is Computer Corporation of America's responsibility,
but close coordination with the ILLIAC IV Information Management
System and network efforts toward a Data Management Language is
required.
The work on a Data Management Language is to be coordinated by J.
Madden of University of Illinois, Bob Metcalfe of Harvard, J. Heafner
of RAND, Jim White of UCSB, and Doug McKay of IBM.
John Heafner indicated that he plans to implement his plans for the
Form Machine, RFC #83, NIC (5609) UCSB, Multics, and Lincoln Lab also
indicated that they are interested in getting a version running.
Watson [Page 12]
RFC 101 NOTES ON THE NETWORK WORKING GROUP MEETING February 1971
A number of sites, UCLA, SRI, RAND, University of Illinois, Raytheon,
MITRE, indicated interest in the range 1-3 months in storing files on
UCSB 360/75 disc packs. Jim White said he would produce a system
within the next 4-6 weeks to allow network users to store files at
UCSB.
The problems of file transfer by name between host systems was again
raised and G. Grossman of University of Illinois indicated he would
start a dialog on the subject by producing an RFC.
The question of user names and the meaning of user IDs in socket
numbers was raised. At present socket numbers have no structure, but
several people felt that for accounting, file transfer, and
interprocess communication some structure was probably valuable. A
committee consisting of:
J. Heafner, RAND (chairman)
E. Meyer, MIT-Multics
G. Grossman, University of Illinois
will produce an RFC stating the issues behind alternate proposals for
socket number structures.
UCLA indicated it wanted a link number in the experimental range of
link numbers for use in measurements experiments with the network.
Link number 223 was assigned to this function. (Link 223 was later
discovered to be assigned. Link 191 was chosen instead. See RFC
#104, NIC (5768,).
The problem of accounting was raised as a number of machine or
systems on the network will provide service functions. The present
service facilities being the 360/91 at UCLA, the 360/75 at UCSB, the
NIC at SRI, Multics at MIT, the ILLIAC IV, the 360/67 at Lincoln Lab,
and the Data Machine. The advanced Host-Host protocol study
committee is looking at the accounting problem. There was brief
mention made of a network banking system. Bob Kahn of BBN indicated
that he would start a dialog on the subject of accounting by
producing a paper putting down the issues as he sees them.
The question was then raised about handling of administrative
procedures such as obtaining accounting numbers on foreign systems.
Dick Watson said he would look into this problem and see how the NIC
can help in its solution.
Watson [Page 13]
RFC 101 NOTES ON THE NETWORK WORKING GROUP MEETING February 1971
The final question to be considered was the frequency and utility of
these NWG meetings. The general consensus was that this had been a
useful meeting, but that more preparation on specific topics to be
discussed at the meeting should be done ahead of time. People who
want to bring up topics at the meeting were asked to distribute
position or introductory papers about a month ahead of the next
meeting, if possible. Peggy Karp will handle trying to obtain a
block of rooms for the NWG during the Spring Joint. She will send
out a request for reservations to the sites soon.
[This RFC was put into machine readable form for entry]
[into the online RFC archives by Kelly Tardif, Viag閚ie 10/99]
Watson [Page 14]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -