1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
|
<pre>Network Working Group Bob Thomas
RFC # 504 BBN
NIC # 16155 April 30, 1973
<span class="h1">Workshop Announcement</span>
Title: Automated Resource Sharing on the ARPANET
Date: Monday May 21, 1973
Time: 9:00 AM to 5:00 PM
Place: Bolt Beranek and Newman Inc., Cambridge, Mass.
Hosts: TENEX and TIP Groups at BBN
Theme:
-----
This workshop will focus on various aspects of the question:
What steps can be taken to automate access to the distributed
resources on the ARPANET?
In particular, how can we move from where we are today toward an
environment which facilitates resource sharing by moving the burden of
dealing with the network from the human user to processes which act on
his behalf? Additionally, operating systems themselves perform various
operations not directly initiated by human users which could better be
performed with the availability of resources on other systems (e.g.
file system backup); how can we move toward an environment which
facilitates such system-system cooperation?
Objectives of Workshop:
----------------------
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. To identify and clarify the issues raised by automated resource</span>
<span class="h2"> sharing.</span>
What are the obstacles preventing more widespread resource sharing
on the ARPANET? Are they technical, political, administrative in
nature? Is it that there are few resources worth sharing (we don't
think so)? Is automated sharing a bad idea (We don't think so)?
<span class="grey">Thomas [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc504">RFC 504</a> Workshop Announcement April 1973</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. To identify resources at various network sites appropriate for</span>
<span class="h2"> automated sharing; and to identify the need for resources which</span>
don't but should exist.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. To formulate a series of experiments for the purpose of evaluating</span>
<span class="h2"> relative merits and disadvantages of different approaches to</span>
automating resource sharing.
The intent of such experimentation is to gain experience through
construction and use of prototype systems which support automated
sharing.
Format of Workshop:
------------------
Morning:
In order to get the workshop "up to speed", each participant will be
expected to give a brief presentation of relevant work he (his site) is
currently engaged in, is planning to do, or to identify and discuss
issues he feels are relevant to the subject. Time will be allowed for
brief discussion after each presentation.
Afternoon:
General discussion of the issues raised during the morning session.
Possible subjects for discussion include (but need not be limited to):
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Identification of possible multi-site "services".</span>
<span class="h2"> Intersite mail, terminal linking, status information are some</span>
examples - what are others?
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Identification of resources appropriate for remote utilization.</span>
<span class="h2"> File systems, compilers, on-line query systems, manuscript</span>
preparation systems are some examples - what are others?
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Access to remote resources.</span>
<span class="h2"> Possibility of access paths other than the standard logger port. To</span>
what extent (if at all) can the access paths to a variety of
different resources be standardized? How can resources which may
move from Host to Host or may be available on several Hosts be
dynamically located and selected for use? The need for
(desirability of) a "broadcast ICP".
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Problems of accounting for resource utilization.</span>
<span class="h2"> Some form of network wide accounting would be a great convenience.</span>
For example, it would be nice if a user could use the same account
at many (all?) sites. What are the problems (if any) preventing
this?
<span class="grey">Thomas [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc504">RFC 504</a> Workshop Announcement April 1973</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Problems of security and access control.</span>
<span class="h2"> Authentication of users/processes attempting to use resources. As</span>
with network wide accounts, the ability to use the same name and
password at all sites would be convenient. How can a user's
password and other sensitive data be protected in such an
environment?
The notion of a third party password validation and user
authentication service.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Approaches to automating resource sharing.</span>
<span class="h2"> It is possible without difficulty to identify several which on the</span>
surface appear to be different:
a. Multi-site executive programs which make resources accessible to
the user at the command language level; e.g. the inter-site,
user-user interaction and file maintenance activity supported by
the RSEXEC.
b. A programming language environment designed to facilitate
resource sharing; e.g. LISP is a machine independent language -
one could imagine a multi-computer LISP system which supported
automated resource sharing.
c. The "collect a resource" approach - identify an Editor here,
file storage service there, a compiler somewhere else, etc; and
build a "workshop" environment which provides convenient access
to these resources.
What are the relative merits and disadvantages of these approaches?
What aspects do these approaches have in common? Is it possible to
identify a common base capable of supporting them all?
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Protocols to support automated resource sharing.</span>
<span class="h2"> It would be inappropriate to attempt to generate a detailed protocol</span>
specification at this workshop. However, it is appropriate to
discuss the kinds of activity a protocol should support. Existing
protocols (excepting Host-Host protocol and possibly, the new TELNET
protocol) appear to be oriented toward human users. Automated
resource sharing suggests processes acting on behalf of human users
to interface to remote resources; this in turn suggests that the
protocols should be highly process oriented. For example, because
there should be minimal human intervention in error recovery, the
protocols should be extremely robust; e.g., include well specified
time outs, etc.
<span class="grey">Thomas [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc504">RFC 504</a> Workshop Announcement April 1973</span>
Arrangements:
------------
If you are planning to attend the workshop, please notify Bob Thomas at
BBN (send net mail to BTHOMAS@BBN, telephone (617) 491-1850, x483). If
you would like us to make motel reservations for you (at the homestead
Inn at Fresh Pond) call Mrs Terry Bernier at BBN (x545).
It is possible that a single day will prove to be insufficient for this
workshop. If that is the consensus of the attendees, the workshop will
continue through Tuesday May 22.
Position papers, memos, notes, etc. prepared by participants in advance
of the workshop will help contribute to the success of the workshop and
are requested. All such papers received before May 11 will be
distributed, in advance, to workshop attendees.
The following questions may be helpful in focusing your thinking:
- What resources would your site be willing to make available for use in
automated resource sharing experiments?
- Under what conditions would your site be willing or able to
participate in such experiments?
- What administrative and/or technical considerations would prevent your
site from entering into a network wide resource sharing agreement?
- If you employ accounting Procedures that require cost recovery, how,
if at all, should they be modified to work in a network resource
sharing environment?
Reading List:
------------
We are aware of little that has been written on the subject of automated
resource sharing. However, the following items are relevant (at least
marginally) to the workshop. Please inform us of others of which you
are aware.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. ARPANET NEWS, Issue 2, Report on COMPCON 73 "Birds of a Feather</span>
<span class="h2"> Session" on Resource Sharing Networks, NIC 15337.</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. "A Resource Sharing Executive for the ARPANET", R. Thomas, Preprint</span>
<span class="h2"> of paper for 1973 National Computer Conference, BBN Report 2522, NIC</span>
#14689.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. "Terminal Access to the ARPANET - Experience and Improvements", N.</span>
<span class="h2"> Mimno, B. Cosell, Walden, et. al., COMPCON 73 Proceedings, NIC</span>
14791.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. "A Tentative Proposal for a Modified User Protocol", M. Padlipsky,</span>
<a href="./rfc451">RFC 451</a>, NIC #14135.
<span class="grey">Thomas [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc504">RFC 504</a> Workshop Announcement April 1973</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. "Interentity Communication - An experiment", R. Bressler, R. Thomas,</span>
<a href="./rfc441">RFC 441</a>, NIC 13773.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. "Netbank", J. Postel, <a href="./rfc408">RFC 408</a>, NIC #12390.</span>
[ 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 ]
Thomas [Page 5]
</pre>
|
