| 1 |
<pre>Network Working Group Barry M. Leiner |
| 2 |
Request for Comments: 1015 RIACS |
| 3 |
July 1987 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Implementation Plan for Interagency Research Internet</span> |
| 7 |
|
| 8 |
STATUS OF THIS MEMO |
| 9 |
|
| 10 |
The RFC proposes an Interagency Research Internet as the natural |
| 11 |
outgrowth of the current Internet. This is an "idea paper" and |
| 12 |
discussion is strongly encouraged. Distribution of this memo is |
| 13 |
unlimited. |
| 14 |
|
| 15 |
OVERVIEW |
| 16 |
|
| 17 |
Networking has become widespread in the scientific community, and |
| 18 |
even more so in the computer science community. There are networks |
| 19 |
being supported by a number of the Federal agencies interested in |
| 20 |
scientific research, and many scientists throughout the country have |
| 21 |
access to one or more of these networks. Furthermore, there are many |
| 22 |
resources (such as supercomputers) that are accessible via these |
| 23 |
networks. |
| 24 |
|
| 25 |
While many of these networks are interconnected on an informal |
| 26 |
basis, there is currently no consistent mechanism to allow sharing |
| 27 |
of the networking resources. Recognizing this problem, the FCCSET |
| 28 |
Committee on Very High Performance Computing formed a Network |
| 29 |
Working Group. This group has recommended an administrative and |
| 30 |
management structure for interconnecting the current and planned |
| 31 |
agency networks supporting research. The structure is based on the |
| 32 |
concept of a network of networks using standard networking |
| 33 |
protocols. |
| 34 |
|
| 35 |
This report elaborates on the earlier recommendation and provides an |
| 36 |
implementation plan. It addresses three major areas; communications |
| 37 |
infrastructure, user support, and ongoing research. A management and |
| 38 |
administrative structure is recommended for each area, and a |
| 39 |
budgetary estimate provided. A phased approach for implementation |
| 40 |
is suggested that will quickly provide interconnection and lead to |
| 41 |
the full performance and functionality as the required technologies |
| 42 |
are developed and installed. While this report addresses the |
| 43 |
interconnection of agency networks, and cooperation by certain |
| 44 |
federal agencies, some discussion is presented of the possible role |
| 45 |
that industry can play in support and use of such a network. |
| 46 |
|
| 47 |
Work reported herein was supported by Cooperative Agreement NCC 2- |
| 48 |
387 from the National Aeronautics and Space Adminstration (NASA) to |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Leiner [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 55 |
|
| 56 |
|
| 57 |
the Universities Space Research Association (USRA). This report was |
| 58 |
prepared in response to a request from John Cavallini, Chairman of |
| 59 |
the Networking Working Group of the FCCSET Committee on Very High |
| 60 |
Performance Computing. |
| 61 |
|
| 62 |
INTRODUCTION |
| 63 |
|
| 64 |
Computer networks are critical in providing scientists access to |
| 65 |
computing resources (such as supercomputers) and permitting computer |
| 66 |
supported interaction between researchers. Several agencies, |
| 67 |
recognizing this need, have established networks to provide the |
| 68 |
needed communications infrastructure. The need for this |
| 69 |
infrastructure, though, cuts across the various agencies. To that |
| 70 |
end, the FCCSET Committee on Very High Performance Computing Network |
| 71 |
Working Group has recommended the formation of an Interagency |
| 72 |
Research Internet (IRI) [1]. |
| 73 |
|
| 74 |
The purpose of this report is to suggest an implementation plan for |
| 75 |
such an IRI. It addresses three major areas; communications |
| 76 |
infrastructure, user support, and ongoing research. A management and |
| 77 |
administrative structure is recommended for each area, and a |
| 78 |
budgetary estimate provided. A phased approach for implementation is |
| 79 |
suggested that will quickly provide interconnection and lead to the |
| 80 |
full performance and functionality as the required technologies are |
| 81 |
developed and installed. Finally, some discussion is presented on a |
| 82 |
possible role for industry in supporting and using such a network. |
| 83 |
|
| 84 |
Motivation |
| 85 |
|
| 86 |
The prime responsibility for providing the required infrastructure |
| 87 |
for successful research lies with the researcher, his/her |
| 88 |
institution, and the agency supporting that research. Thus, the |
| 89 |
individual agencies have installed and are continuing to enhance |
| 90 |
computer networks to allow their researchers to access advanced |
| 91 |
computing resources such as supercomputers as well as being able to |
| 92 |
communicate with each other via such facilities as electronic mail. |
| 93 |
|
| 94 |
However, there are a number of reasons why it is advantageous to |
| 95 |
interconnect the various agency networks in a coherent manner so as |
| 96 |
to provide a common "virtual" network supporting research. |
| 97 |
|
| 98 |
The need to make effective use of available networks without |
| 99 |
unnecessary duplication. The agencies each support researchers in |
| 100 |
many parts of the country, and have installed equally widespread |
| 101 |
resources. Often, it is more effective for a scientist to be |
| 102 |
provided networking service through a different agency network than |
| 103 |
the one funding his research. For example, suppose several |
| 104 |
scientists at an institution are already being funded by NASA and |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Leiner [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 111 |
|
| 112 |
|
| 113 |
are connected to a NASA supported network. Now a scientist at the |
| 114 |
same institution but supported by NSF needs access to an NSF |
| 115 |
supercomputer. It is much more effective to provide that |
| 116 |
connectivity through an interconnection of NASA and NSF networks |
| 117 |
than to establish another connection (to NSFnet) to the same |
| 118 |
university. |
| 119 |
|
| 120 |
The need to establish communication infrastructure to permit |
| 121 |
scientists to access resources without regard to which network they |
| 122 |
are connected but without violating access controls on either the |
| 123 |
networks or the resources. A scientist may be supported by multiple |
| 124 |
agencies, and therefore have access to resources provided by several |
| 125 |
agencies. It is not cost-effective to have to provide a separate |
| 126 |
network connection to the scientist for each of those agency |
| 127 |
resources. |
| 128 |
|
| 129 |
The need for a communications infrastructure to encourage |
| 130 |
collaborative scientific research. One of the primary functions of a |
| 131 |
computer network supporting science is the encouraging of |
| 132 |
collaboration between researchers. Scientific disciplines typically |
| 133 |
cut across many different agencies. Thus, support of this |
| 134 |
collaboration should be without regard to agency affiliation or |
| 135 |
support of the scientists involved. |
| 136 |
|
| 137 |
The need for a cooperative research and development program to |
| 138 |
evolve and enhance the IRI and its components where appropriate. |
| 139 |
Scientific research is highly demanding of both the computing and |
| 140 |
networking environment. To assure that these needs continue to be |
| 141 |
met, it is necessary to continually advance the state of the art in |
| 142 |
networking, and apply the results to the research networks. No |
| 143 |
individual agency can afford to support the required research |
| 144 |
alone, nor is it desirable to have inordinate duplication of |
| 145 |
research. |
| 146 |
|
| 147 |
Summary of previous report |
| 148 |
|
| 149 |
These reasons led to the formation of the FCCSET Commitee on Very |
| 150 |
High Performance Computing and its Network Working Group. This group |
| 151 |
began in early 1985 to discuss the possibility of interconnecting |
| 152 |
into a common networking facility the various agency networks |
| 153 |
supporting scientific research. These discussions led to the report |
| 154 |
issued earlier this year [1] recommending such an approach. |
| 155 |
|
| 156 |
The report used the "Network of Networks" or Internet model of |
| 157 |
interconnection. Using a standard set of protocols, the various |
| 158 |
networks can be connected to provide a common set of user services |
| 159 |
across heterogenous networks and heterogenous host computers [2, |
| 160 |
3,4]. This approach is discussed further in the Background section |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Leiner [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 167 |
|
| 168 |
|
| 169 |
below. |
| 170 |
|
| 171 |
The report goes on to recommend an administrative and management |
| 172 |
structure that matches the technical approach. Each agency would |
| 173 |
continue to manage and administer its individual networks. An |
| 174 |
interagency body would provide direction to a selected organization |
| 175 |
who would provide the management and operation of the |
| 176 |
interconnections of the networks and the common user services |
| 177 |
provided over the network. This selected organization would also |
| 178 |
provide for coordination of research activities, needed |
| 179 |
developments, and reflecting research community requirements into |
| 180 |
the national and international standards activities. |
| 181 |
|
| 182 |
Overview of Implementation Plan |
| 183 |
|
| 184 |
The general structure of the proposed IRI is analogous to a federal |
| 185 |
approach. Each of the agencies is responsible for operating its own |
| 186 |
networks and satisfying its users' requirements. The IRI provides |
| 187 |
the interconnecting infrastructure to permit the users on one |
| 188 |
network to access resources or users on other networks. The IRI also |
| 189 |
provides a set of standards and services which the individual |
| 190 |
agencies, networks, and user communities can exploit in providing |
| 191 |
capabilities to their individual users. The management structure, |
| 192 |
likewise, provides a mechanism by which the individual agencies can |
| 193 |
cooperate without interfering with the agencies' individual |
| 194 |
authorities or responsibilities. |
| 195 |
|
| 196 |
In this report, an implementation plan for the IRI is proposed. |
| 197 |
First, some background is given of the previous efforts to provide |
| 198 |
networks in support of research, and the genesis of those networks. |
| 199 |
A description of the suggested approach to attaining an IRI is then |
| 200 |
given. This description is divided into two sections; technical and |
| 201 |
management. The technical approach consists of two components. First |
| 202 |
is the provision of an underlying communications infrastructure; |
| 203 |
i.e. a means for providing connectivity between the various |
| 204 |
computers and workstations. Second is provision of the means for |
| 205 |
users to make effective use of that infrastructure in support of |
| 206 |
their research. |
| 207 |
|
| 208 |
The management section elaborates on the suggestions made in the |
| 209 |
FCCSET committee report. A structure is suggested that allows the |
| 210 |
various agencies to cooperate in the operations, maintenance, |
| 211 |
engineering, and research activities required for the IRI. This |
| 212 |
structure also provides the necessary mechanisms for the scientific |
| 213 |
research community to provide input with respect to requirements and |
| 214 |
approaches. |
| 215 |
|
| 216 |
Finally, a phased implementation plan is presented which would allow |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Leiner [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 223 |
|
| 224 |
|
| 225 |
the IRI to be put in place rapidly with modest funding. A budgetary |
| 226 |
estimate is also provided. |
| 227 |
|
| 228 |
BACKGROUND |
| 229 |
|
| 230 |
The combination of packet switched computer networks, |
| 231 |
internetworking to allow heterogeneous computers to communicate over |
| 232 |
heterogeneous networks, the widespread use of local area networks, |
| 233 |
and the availability of workstations and supercomputers has given |
| 234 |
rise to the opportunity to provide greatly improved computing |
| 235 |
capabilities to science and engineering. This is the major |
| 236 |
motivation behind the IRI. |
| 237 |
|
| 238 |
History of Research Network |
| 239 |
|
| 240 |
The Defense Advanced Research Projects Agency (DARPA) developed the |
| 241 |
concept of packet switching beginning in the mid 1960's. Beginning |
| 242 |
with the Arpanet (the world's first packet switched network) [5],a |
| 243 |
number of networks have been developed. These have included packet |
| 244 |
satellite networks [6,7], packet radio networks [8,7], and local |
| 245 |
area networks [9]. |
| 246 |
|
| 247 |
Although the original motivation for the Arpanet development was |
| 248 |
computer resource sharing, it was apparent early on that a major use |
| 249 |
of such networks would be for access to computer resources and |
| 250 |
interaction between users [10]. Following the Arpanet development, |
| 251 |
a number of other networks have been developed and used to provide |
| 252 |
both of these functions [11]. CSNET was initiated to provide |
| 253 |
communications between computer science researchers [12,13]. CSNET |
| 254 |
was initiated by the NSF in cooperation with a number of |
| 255 |
universities, but is now self-sufficient. Its subscribers include |
| 256 |
universities throughout the world as well as industrial members |
| 257 |
interested in interacting with computer scientists. |
| 258 |
|
| 259 |
CSNET makes use of a number of networking technologies including the |
| 260 |
Arpanet, public X.25 networks, and dial-up connections over phone |
| 261 |
lines, to support electronic mail and other networking functions. In |
| 262 |
addition to the basic data transport service, CSNET and Arpanet |
| 263 |
operate network information centers which provide help to users of |
| 264 |
the network as well as a number of services including a listing of |
| 265 |
users with their mail addresses (white pages) and a repository where |
| 266 |
relevant documents are stored and can be retrieved. |
| 267 |
|
| 268 |
With the installation of supercomputers came the desire to provide |
| 269 |
network access for researchers. One of the early networks to |
| 270 |
provide this capability was MFEnet [11]. It was established in the |
| 271 |
early 1970's to provide DOE-supported users access to |
| 272 |
supercomputers, particularly a Cray 1 at Lawrence Livermore National |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Leiner [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 279 |
|
| 280 |
|
| 281 |
Labs. Because MFEnet was established prior to widespread adoption of |
| 282 |
the TCP/IP protocol suite (to be discussed below), the MFEnet uses a |
| 283 |
different set of protocols. However, interfaces have been developed |
| 284 |
between the MFEnet and other networks, and a migration plan is |
| 285 |
currently under development. |
| 286 |
|
| 287 |
NASA Ames Research Center has long been in the forefront of using |
| 288 |
advanced computers to support scientific research. The latest |
| 289 |
computing facility, the Numerical Aerodynamic Simulator, uses a Cray |
| 290 |
2 and other machines along with a number of networking technologies |
| 291 |
to provide support to computational fluid dynamics researchers [14]. |
| 292 |
This system uses the TCP/IP protocol suite both locally and remotely |
| 293 |
and provides easy access through advanced workstations. |
| 294 |
|
| 295 |
Recognizing the importance of advanced computers in carrying out |
| 296 |
scientific research, NSF in 1984 embarked on an ambitious program to |
| 297 |
provide supercomputer access to researchers. This program involved |
| 298 |
both the provision of supercomputers themselves (through purchase of |
| 299 |
computer time initially, and establishment of supercomputer centers) |
| 300 |
and provision of access to those supercomputers through an extensive |
| 301 |
networking program, NSFnet [15]. The NSFnet uses a number of |
| 302 |
existing networks (e.g. Arpanet, BITNET, MFEnet) and exploratory |
| 303 |
networks interconnected using the TCP/IP protocol suite (discussed |
| 304 |
below) to permit scientists widespread access to the supercomputer |
| 305 |
centers and each other. The NSFnet is also taking advantage of the |
| 306 |
widespread installation of campus and regional networks to achieve |
| 307 |
this connectivity in a cost effective manner. |
| 308 |
|
| 309 |
The above are only a small number of the current and existing |
| 310 |
networks being used to support research. Quarterman [11] provides a |
| 311 |
good synopsis of the networks currently in operation. It is obvious |
| 312 |
from this that effective interconnection of the networks can provide |
| 313 |
cost-efficient and reliable services. |
| 314 |
|
| 315 |
Starting in the early 1970's, recognizing that the military had a |
| 316 |
need to interconnect various networks (such as packet radio for |
| 317 |
mobile operation with long-line networks like the Arpanet), DARPA |
| 318 |
initiated the development of the internet technologies [16]. |
| 319 |
Beginning with the development of the protocols for interconnection |
| 320 |
and reliable transport (TCP/IP), the program has developed methods |
| 321 |
for providing electronic mail, remote login, file transfer and |
| 322 |
similar functions between differing computers over dissimilar |
| 323 |
networks [4,3]. Today, using that technology, thousands of |
| 324 |
computers are able to communicate with each other over a "virtual |
| 325 |
network" of approximately 200 networks using a common set of |
| 326 |
protocols. The concepts developed are being used in the reference |
| 327 |
model and protocols of the Open Systems Interconnection model being |
| 328 |
developed by the International Standards Organization (ISO) [17]. |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Leiner [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 335 |
|
| 336 |
|
| 337 |
This is becoming even more important with the widespread use of |
| 338 |
local area networks. As institutions install their own networks, |
| 339 |
and need to establish communications with computers at other sites, |
| 340 |
it is important to have a common set of protocols and a means for |
| 341 |
interconnecting the local networks to wide area networks. |
| 342 |
|
| 343 |
Internet Model |
| 344 |
|
| 345 |
The DARPA Internet system uses a naming and addressing protocol, |
| 346 |
called the Internet Protocol (IP), to interconnect networks into a |
| 347 |
single virtual network. Figure 1 shows the interconnection of a |
| 348 |
variety of networks into the Internet system. The naming and |
| 349 |
addressing structure allows any computer on any network to address |
| 350 |
in a uniform manner any computer on any other network. Special |
| 351 |
processors, called Gateways, are installed at the interfaces between |
| 352 |
two or more networks and provide both routing amongst the various |
| 353 |
networks as well as the appropriate translation from internet |
| 354 |
addresses to the address required for the attached networks. Thus, |
| 355 |
packets of data can flow between computers on the internet. |
| 356 |
|
| 357 |
Because of the possiblity of packet loss or errors, the Transmission |
| 358 |
Control Protocol (TCP) is used above the IP to provide for |
| 359 |
reliability and sequencing. TCP together with IP and the various |
| 360 |
networks and gateways then provides for reliable and ordered |
| 361 |
delivery of data between computers. A variety of functions can use |
| 362 |
this connection to provide service to the users. A summary of the |
| 363 |
functions provided by the current internet system is given in [4]. |
| 364 |
|
| 365 |
To assure interoperability between military users of the system, the |
| 366 |
Office of the Secretary of Defense mandated the use of the TCP/IP |
| 367 |
protocol suite wherever there is a need for interoperable packet |
| 368 |
switched communications. This led to the standardization of the |
| 369 |
protocols [18, 19, 20, 21, 22]. |
| 370 |
|
| 371 |
|
| 372 |
|
| 373 |
|
| 374 |
|
| 375 |
|
| 376 |
|
| 377 |
|
| 378 |
|
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Leiner [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 391 |
|
| 392 |
|
| 393 |
+---+ +---+ +---+ +---+ +---+ +---+ |
| 394 |
| FS| | SC| | SC| | SC| | SC| | SC| |
| 395 |
+-+-+ +-+-+ +-+-+ +-+-+ +-+-+ +-+-+ |
| 396 |
| | | | | | |
| 397 |
--+-------+-----+-----+-------+--LAN-- --+------+-+---+----LAN-- |
| 398 |
| | | | | | |
| 399 |
+-+--+ +-+--+ +-+--+ +-+--+ | | |
| 400 |
| WS | | WS | | WS | | WS | | | |
| 401 |
+-+--+ +-+--+ +-+--+ +-+--+ | | |
| 402 |
+-+-+ +-+-+ |
| 403 |
| G | | G | |
| 404 |
+-+-+ +-+-+ |
| 405 |
| | |
| 406 |
+--------------+ +--------------+ |
| 407 |
| Agency | +-+-+ | Agency | |
| 408 |
| Network |--| G |--| Network | |
| 409 |
+------+-------+ +---+ +------+-----+-+ |
| 410 |
| | | |
| 411 |
+-+-+ +-+-+ | |
| 412 |
| G | | G | | |
| 413 |
+-+-+ +-+-+ | |
| 414 |
/ / +-------+ |
| 415 |
/ / | TS | |
| 416 |
/ / +-+-----+ |
| 417 |
+--------------+ +--------------+ | |...| |
| 418 |
| Regional | | Commercial | T T T |
| 419 |
| Network | | Network | |
| 420 |
+-----+--------+ +------+-------+ |
| 421 |
| | |
| 422 |
+-+-+ | |
| 423 |
| G | | |
| 424 |
+-+-+ | |
| 425 |
| +-+-+ |
| 426 |
| | H | |
| 427 |
| +---+ |
| 428 |
----+------+-----+-----+------LAN---- |
| 429 |
| | | | |
| 430 |
+-+--+ +-+--+ +-+--+ +-+--+ +-------------------------+ |
| 431 |
| WS | | WS | | WS | | WS | | H - Host | |
| 432 |
+-+--+ +-+--+ +-+--+ +-+--+ | WS - Workstation | |
| 433 |
| SC - Supercomputer | |
| 434 |
| TS - Terminal Server | |
| 435 |
| FS - File Server | |
| 436 |
| G - Gateway | |
| 437 |
+-------------------------+ |
| 438 |
|
| 439 |
Figure 1: Internet System |
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Leiner [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 447 |
|
| 448 |
|
| 449 |
Thus, the TCP/IP protocol suite and associated mechanisms (e.g. |
| 450 |
gateways) provides a way to interconnect heterogeneous computers on |
| 451 |
heterogenous networks. Routing and addressing functions are taken |
| 452 |
care of automatically and transparently to the users.The ISO is |
| 453 |
currently developing a set of standards for interconnection which |
| 454 |
are very similar in function to the DARPA developed technologies. |
| 455 |
Although ISO is making great strides, and the National Bureau of |
| 456 |
Standards is working with a set of manufacturers to develop and |
| 457 |
demonstrate these standards, the TCP/IP protocol suite still |
| 458 |
represents the most available and tested technology for |
| 459 |
interconnection of computers and networks. It is for that reason |
| 460 |
that several agencies/programs, including the Department of Defense, |
| 461 |
NSF and NASA/NAS, have all adopted the TCP/IP suite as the most |
| 462 |
viable set of standards currently. As the international standards |
| 463 |
mature, and products supporting them appear, it can be expected that |
| 464 |
the various networks will switch to using those standards. |
| 465 |
|
| 466 |
TECHNICAL APPROACH |
| 467 |
|
| 468 |
The Internet technology described above provides the basis for |
| 469 |
interconnection of the various agency networks. The means to |
| 470 |
interconnect must satisfy a number of constraints if it is to be |
| 471 |
viable in a multi-agency environment. |
| 472 |
|
| 473 |
Each agency must retain control of its own networks. Networks have |
| 474 |
been established to support agency-specific missions as well as |
| 475 |
general computer communications within the agency and its |
| 476 |
contractors. To assure that these missions continue to be supported |
| 477 |
appropriately, as well as assure appropriate accountability for the |
| 478 |
network operation, the mechanism for interconnection must not |
| 479 |
prevent the agencies from retaining control over their individual |
| 480 |
networks. |
| 481 |
|
| 482 |
This is not to say that agencies may not choose to have their |
| 483 |
individual networks operated by the IRI, or even turned over to the |
| 484 |
IRI if they determine that to be appropriate. |
| 485 |
|
| 486 |
Appropriate access control, privacy, and accounting mechanisms must |
| 487 |
be incorporated. This includes access control to data, resources, |
| 488 |
and the networks themselves, privacy of user data, and accounting |
| 489 |
mechanisms to support both cost allocation and cost auditing [23]. |
| 490 |
|
| 491 |
The technical and adminstrative approach must allow (indeed |
| 492 |
encourage) the incorporation of evolving technologies. In |
| 493 |
particular, the network must evolve towards provision of high |
| 494 |
bandwidth, type of service routing, and other advanced techniques to |
| 495 |
allow effective use of new computing technology in a distributed |
| 496 |
research environment. |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Leiner [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 503 |
|
| 504 |
|
| 505 |
Communications Infrastructure |
| 506 |
|
| 507 |
The communications infrastructure provides connectivity between user |
| 508 |
machines, workstations, and centralized resources such as |
| 509 |
supercomputers and database machines. This roughly corresponds to |
| 510 |
communications services at and below the transport layer in the ISO |
| 511 |
OSI reference model. There are two different types of networks. The |
| 512 |
first are local networks, meaning those which are internal to a |
| 513 |
facility, campus, etc. The second are networks which provide transit |
| 514 |
service between facilities. These transit networks can connect |
| 515 |
directly to computers, but are evolving in a direction of connecting |
| 516 |
local networks. The networks supported by the individual agencies |
| 517 |
directly are mainly in the category of transit (or long-haul) |
| 518 |
networks, as they typically provide nationwide connectivity, and |
| 519 |
usually leave communications within a facility to be dealt with by |
| 520 |
the facility itself. The IRI communications infrastructure thus |
| 521 |
deals mainly with the interconnection of transit networks. |
| 522 |
|
| 523 |
The internet model described above provides a simple method for |
| 524 |
interconnecting transit networks (as well as local networks.) By |
| 525 |
using IP gateways between the agency networks, packet transport |
| 526 |
service can be provided between computers on any of the various |
| 527 |
networks. The placement of the gateways and their capacity will have |
| 528 |
to be determined by an initial engineering study. In addition, as |
| 529 |
the IRI evolves, it may be cost-effective to install one or more |
| 530 |
wide area networks (or designate certain existing ones) to be IRI |
| 531 |
transit networks, to be used by all agencies on a cost sharing |
| 532 |
basis. Thus, the IRI communications infrastructure would consist of |
| 533 |
the interconnecting gateways plus any networks used specifically as |
| 534 |
transit networks. Using IP as the standard for interconnection of |
| 535 |
networks and global addressing provides a common virtual network |
| 536 |
packet transport service, upon which can be built various other |
| 537 |
network services such as file transfer and electronic mail. This |
| 538 |
will allow sharing of the communication facilities (channels, |
| 539 |
satellites, etc.) between the various user/agency communities in a |
| 540 |
cost effective manner. |
| 541 |
|
| 542 |
To assure widespread interconnectivity, it is important that |
| 543 |
standards be adopted for use in the IRI and the various computers |
| 544 |
connected to it. These standards need to cover not only the packet |
| 545 |
transport capability but must address all the services required for |
| 546 |
networking in a scientific domain, including but not limited to file |
| 547 |
transfer, remote login, and electronic mail. Ultimately it is |
| 548 |
desirable to move towards a single set of standards for the various |
| 549 |
common services, and the logical choice for those standards are |
| 550 |
those being developed in the international commercial community |
| 551 |
(i.e. the ISO standards). However, many of the scientific networks |
| 552 |
today use one or more of a small number of different standards; in |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Leiner [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 559 |
|
| 560 |
|
| 561 |
particular the TCP/IP protocol suite mentioned above, the MFEnet |
| 562 |
protocols, and DECNET. As the international standards mature, it is |
| 563 |
expected that the number of communities using the same protocol |
| 564 |
suite will grow [5] [6]. Even today, several of the |
| 565 |
agencies/communities are using a common protocol suite, namely the |
| 566 |
TCP/IP suite. All the users connected to those computers and |
| 567 |
networks are able to have the full functions of an interoperable |
| 568 |
networking capability. And therefore the ability of the users to |
| 569 |
share resources and results will increase. |
| 570 |
|
| 571 |
User Services |
| 572 |
|
| 573 |
In order that scientists can effectively use the network, there |
| 574 |
needs to be a user support organization. To maximize the cost |
| 575 |
effectiveness of the overall IRI, the local user support personnel |
| 576 |
must be used effectively. In particular, it is anticipated that |
| 577 |
direct support of users/researchers would be provided by local |
| 578 |
support personnel. The IRI user support organization would provide |
| 579 |
support to those local support personnel in areas where nationwide |
| 580 |
common service is cost effective. |
| 581 |
|
| 582 |
In particular, the this organization has several functions: assist |
| 583 |
the local support personnel in the installation of facilities |
| 584 |
compatible with the IRI, provide references to standard facilities |
| 585 |
(e.g. networking interfaces, mail software) to the local support |
| 586 |
personnel, answer questions that local personnel are not able to |
| 587 |
answer, aid in the provision of specific user community services, |
| 588 |
e.g. database of relevance to specific scientific domain. |
| 589 |
|
| 590 |
Internet Research Coordination |
| 591 |
|
| 592 |
To evolve internet to satisfy new scientific requirements and make |
| 593 |
use of new technology, research is required in several areas. These |
| 594 |
include high speed networking, type of service routing, new end to |
| 595 |
end protocols, and congestion control. The IRI organizational |
| 596 |
structure can assist in identifying areas of research where the |
| 597 |
various agencies have a common interest in supporting in order to |
| 598 |
evolve the network, and then assist in the coordination of that |
| 599 |
research. |
| 600 |
|
| 601 |
MANAGEMENT APPROACH |
| 602 |
|
| 603 |
A management approach is required that will allow each agency to |
| 604 |
retain control of its own networking assets while sharing certain |
| 605 |
resources with users sponsored by other agencies. To accomplish |
| 606 |
this, the following principles and constraints need to be followed. |
| 607 |
|
| 608 |
IRI consists of the infrastructure to connect agency networks and |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Leiner [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 615 |
|
| 616 |
|
| 617 |
the user services required for effective use of the combined |
| 618 |
networks and resources. |
| 619 |
|
| 620 |
An organization must be identified to be responsible for the |
| 621 |
engineering, operation, and maintenance of both the interconnecting |
| 622 |
infrastructure and the user services support. |
| 623 |
|
| 624 |
While some agencies may choose to make use of IRI facilities and |
| 625 |
contractors to manage their individual agency networks, this would |
| 626 |
not be required and is not anticipated to be the normal situation. |
| 627 |
Any such arrangement would have to be negotiated individually and |
| 628 |
directly between the agency and the IRI operations organization. |
| 629 |
Normally, the IRI organization would neither manage the individual |
| 630 |
agency networks nor have any jurisdiction within such networks. |
| 631 |
|
| 632 |
Gateways that interconnect the agency networks as well as any long- |
| 633 |
haul networks put in place specifically as jointly supported transit |
| 634 |
networks (if any such networks are required) will be managed and |
| 635 |
operated under the IRI organization. |
| 636 |
|
| 637 |
A support organization for common IRI services is required. The |
| 638 |
principal clients for these services would be the local support |
| 639 |
personnel. |
| 640 |
|
| 641 |
The IRI structure should support the coordination of the individual |
| 642 |
research activities required for evolution and enhancement of the |
| 643 |
IRI. |
| 644 |
|
| 645 |
General Management Structure |
| 646 |
|
| 647 |
Figure 2 shows the basic management structure for the IRI. It is |
| 648 |
based on the use of a non-profit organization (call it the |
| 649 |
Interagency Research Internet Organization, IRIO) to manage both the |
| 650 |
communications infrastructure and user support. The IRIO contracts |
| 651 |
for the engineering, development, operations, and maintenance of |
| 652 |
those services with various commercial and other organizations. It |
| 653 |
would be responsible for providing technical and administrative |
| 654 |
management of the contractors providing these functions. Having the |
| 655 |
IRI operational management provided by an independent non-profit |
| 656 |
organization skilled in the area of computer networking will permit |
| 657 |
the flexibility required to deal with the evolving and changing |
| 658 |
demands of scientific networking in a cost-effective manner. |
| 659 |
|
| 660 |
Direction and guidance for the IRIO will be provided by a Policy |
| 661 |
Board consisting of representatives from the Government agencies who |
| 662 |
are funding the IRI. The Chairman of the Board will be selected from |
| 663 |
the agency representatives on a rotating basis. The Board will also |
| 664 |
have an Executive Director to provide administrative and other |
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Leiner [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 671 |
|
| 672 |
|
| 673 |
support. To provide effective support for the IRI Policy Board as |
| 674 |
well as assure appropriate coordination with the IRIO, the Executive |
| 675 |
Director shall be the Director of the IRIO. |
| 676 |
|
| 677 |
To assure that the IRI provides the best support possible to the |
| 678 |
scientific research community, the Policy Board will be advised by a |
| 679 |
Technical Advisory Board (TAB) consisting of representatives from |
| 680 |
the network research and engineering community, the various networks |
| 681 |
being interconnected with the IRI, and the scientific user |
| 682 |
community. Members of the TAB will be selected by the Policy Board. |
| 683 |
The TAB will review the operational support of science being |
| 684 |
provided by the IRI and suggest directions for improvement. The TAB |
| 685 |
will interface directly with the IRIO to review the operational |
| 686 |
status and plans for the future, and recommend to the Policy Board |
| 687 |
any changes in priorities or directions. |
| 688 |
|
| 689 |
Research activities related to the use and evolution of the internet |
| 690 |
system will be coordinated by the Internet Research Activities Board |
| 691 |
(IRAB). The IRAB consists of the chairmen of the research task |
| 692 |
forces (see below) and has as ex-officio members technical r |
| 693 |
representatives from the funding agencies and the IRIO. The |
| 694 |
charter of the IRAB is to identify required directions for research |
| 695 |
to improve the IRI, and recommend such directions to the funding |
| 696 |
agencies. In addition, the IRAB will continually review ongoing |
| 697 |
research activities and identify how they can be exploited to |
| 698 |
improve the IRI. |
| 699 |
|
| 700 |
The Research Task Forces will each be concerned with a particular |
| 701 |
area/emphasis of research (e.g. end-to-end protocols, gateway |
| 702 |
architectures, etc.). Members will be active researchers in the |
| 703 |
field and the chairman an expert in the area with a broad |
| 704 |
understanding of research both in that area and the general internet |
| 705 |
(and its use for scientific research). The chairmen of the task |
| 706 |
forces will be selected by IRAB, and thus the IRAB will be a self- |
| 707 |
elected and governing organization representing the networking |
| 708 |
research community. The chairmen will solicit the members of the |
| 709 |
task force as volunteers. |
| 710 |
|
| 711 |
|
| 712 |
|
| 713 |
|
| 714 |
|
| 715 |
|
| 716 |
|
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Leiner [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 727 |
|
| 728 |
|
| 729 |
+------+ +------+ +------+ +------+ .... +------+ |
| 730 |
|DARPA | | NSF | | DOE | | NASA | |Others| |
| 731 |
+--+---+ +--+---+ +--+---+ +--+---+ +--+---+ |
| 732 |
| | | | | |
| 733 |
+--+--------+-----------+----+------+-------------------+ |
| 734 |
| | +------------+ |
| 735 |
| Funding | Representatives | Scientific| |
| 736 |
| | | Research | |
| 737 |
V V | Community | |
| 738 |
+-------------+ +-------------+ +----------+-+ |
| 739 |
| Selecting | Policy | Policy | | |
| 740 |
| Contracting|<-------------+ Board | Advice | |
| 741 |
| Agency | +->| |<------------+ | |
| 742 |
+-----+-------+ | +------+------+ | | |
| 743 |
|Funding | |Management +------+<--+ |
| 744 |
| Advice and Plans| | | TAB |<-------+ |
| 745 |
| +---------------+ V +------+<---- + | |
| 746 |
| | +------------+ ^ ^ | | |
| 747 |
+---|------------------>| | Interaction| | | | |
| 748 |
| | IRIO |<-----------+ | | | |
| 749 |
| +------------->| |<-----------+ | | | |
| 750 |
| | Interaction +-----+------+ Interaction| | | | |
| 751 |
| | | V | | | |
| 752 |
| | +-----------+----------+ +------------+ | | |
| 753 |
| | |Management | Funding | | Constituent| | | |
| 754 |
| | | | | | Networks | | | |
| 755 |
V V V V V +------------+ | | |
| 756 |
+-------+ +--------+ +--------+ +-----------+ | | |
| 757 |
| IRAB | |Network | | User | | Other | | | |
| 758 |
+-------+ | O&M | |Services| |Contractors| | | |
| 759 |
| +----+---+ +---+----+ +-----+-----+ | | |
| 760 |
| | | | | | |
| 761 |
| +---------+-------------+----------------+ | |
| 762 |
| | |
| 763 |
+-----------------+--------------------+ | |
| 764 |
|Chair |Chair |Chair | |
| 765 |
V V V | |
| 766 |
+----------+ +----------+ +----------+ | |
| 767 |
|TASK FORCE| |TASK FORCE| .... |TASK FORCE| | |
| 768 |
+----------+ +----------+ +----------+ | |
| 769 |
^ ^ ^ | |
| 770 |
| | | | |
| 771 |
V V V | |
| 772 |
+--------------------------------------+ | |
| 773 |
| Network Research Community |------------------+ |
| 774 |
+--------------------------------------+ |
| 775 |
|
| 776 |
Figure 2: IRI Management Structure |
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Leiner [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 783 |
|
| 784 |
|
| 785 |
Funding |
| 786 |
|
| 787 |
In this section, the funding of the IRI is described. Recall that |
| 788 |
the IRI consists of the infrastructure to connect the agency |
| 789 |
networks and the services required for users to make effective use |
| 790 |
of such an infrastructure. These costs are divided into two |
| 791 |
categories; operations costs and research costs. The operations |
| 792 |
costs are those to operate and maintain both the communications |
| 793 |
infrastructure and the user services. These costs must be shared |
| 794 |
between the various agencies and channeled to the IRIO to operate |
| 795 |
the IRI. The research costs are those used to carry out the needed |
| 796 |
research to evolve the IRI. These costs are handled within the |
| 797 |
various agency budgets and used to support research in each agency |
| 798 |
with coordination between the agencies. |
| 799 |
|
| 800 |
Operations Cost |
| 801 |
|
| 802 |
Each participating agency will contribute a share of operations cost |
| 803 |
of IRI. Initially, each agency will contribute an equal share. |
| 804 |
Later, perhaps, the agency contributions will be adjusted according |
| 805 |
to a number of factors such as number of users, amount of traffic, |
| 806 |
type of support required (high bandwidth real time versus low |
| 807 |
bandwidth mail for example). |
| 808 |
|
| 809 |
To facilitate the funding and administration of the IRI, one agency |
| 810 |
will be selected to manage the contract with IRIO. All funds will |
| 811 |
flow through that agency to the IRIO via interagency transfer. The |
| 812 |
role of the selected agency would be to provide the needed |
| 813 |
contractual activities and adminstrative management. Technical |
| 814 |
guidance and monitoring of IRIO activities would be provided by the |
| 815 |
IRI Policy Board. |
| 816 |
|
| 817 |
It is not yet clear which Federal agency is best for this role. The |
| 818 |
requirements for such an agency include the ability to deal flexibly |
| 819 |
with the evolving requirements of the IRI, to deal with funding |
| 820 |
flowing from the various agencies, and to deal flexibly with the |
| 821 |
various agency technical representatives and incorporate their |
| 822 |
recommendations into the contract as required. One of the first |
| 823 |
activities required for the Policy Board would be to select an |
| 824 |
appropriate funding agency. |
| 825 |
|
| 826 |
All operations and maintenance funding for the IRI will flow through |
| 827 |
the IRIO to selected contractors. This allows centralized management |
| 828 |
of the operation of the IRI. |
| 829 |
|
| 830 |
There are two major assumptions underlying the budgetary estimates |
| 831 |
to follow. First of all, the IRIO should maintain a fairly low |
| 832 |
profile with respect to the end users (i.e. the scientists and |
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Leiner [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 839 |
|
| 840 |
|
| 841 |
researchers). That is, the users will interact directly with their |
| 842 |
local support personnel. The IRIO will act as facilitator and |
| 843 |
coordinator, and provide facilities, information and help services |
| 844 |
to the local sites. This will allow the IRIO to remain relatively |
| 845 |
small, as it will not need to deal directly with the thousands of |
| 846 |
scientists/users. |
| 847 |
|
| 848 |
Second, it is assumed that the operations budget supports the |
| 849 |
interconnection of agency networks as well as transit networking |
| 850 |
where required, but does not include costs of the individual agency |
| 851 |
networks. |
| 852 |
|
| 853 |
<a href="#appendix-A">Appendix A</a> provides details of the budgetary estimate. Table 1 gives |
| 854 |
a summary. Note that the initial year has a higher expenditure of |
| 855 |
capital equipment, reflecting the need to purchase both the gateways |
| 856 |
needed for initial interconnection and the needed facilities to |
| 857 |
provide the operation of the gateways and the user services. |
| 858 |
Operations costs are expected to grow by inflation while the capital |
| 859 |
costs should remain constant (decrease when inflation is considered) |
| 860 |
as the IRI is stabilized. |
| 861 |
|
| 862 |
Research Costs |
| 863 |
|
| 864 |
In addition to the costs of operating and maintaining the |
| 865 |
communications infrastructure and user services, funding must be |
| 866 |
allocated to support an ongoing program of research to improve and |
| 867 |
evolve the IRI. |
| 868 |
|
| 869 |
While each agency funds its own research program, the intent is that |
| 870 |
the various programs are coordinated through the IRI Policy Board. |
| 871 |
Likewise, while it is not intended that funds shall be combined or |
| 872 |
joint funding of projects is required, such joint activity can be |
| 873 |
done on an individual arrangement basis. |
| 874 |
|
| 875 |
Each agency agrees, as part of the joint IRI activity, to fund an |
| 876 |
appropriate level of networking research in areas applicable to IRI |
| 877 |
evolution. The total funding required is currently estimated to be |
| 878 |
four million dollars in FY87, growing by inflation in the outyears. |
| 879 |
Details of this budgetary estimate are provided in <a href="#appendix-A">Appendix A</a>. |
| 880 |
|
| 881 |
|
| 882 |
|
| 883 |
|
| 884 |
|
| 885 |
|
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Leiner [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 895 |
|
| 896 |
|
| 897 |
+--------------------------------------------------+ |
| 898 |
| Table 1 | |
| 899 |
| | |
| 900 |
| Annual IRI Operations Budget | |
| 901 |
+----------+-------------+------------+------------+ |
| 902 |
| Fiscal | Capital | O & M | Total | |
| 903 |
| Year | Cost | Cost | | |
| 904 |
| | | | | |
| 905 |
| | ($M) | ($M) | ($M) | |
| 906 |
+----------+-------------+------------+------------+ |
| 907 |
| 1987 | 2 | 8 | 10 | |
| 908 |
+----------+-------------+------------+------------+ |
| 909 |
| 1988 | 1 | 9 | 10 | |
| 910 |
+----------+-------------+------------+------------+ |
| 911 |
| 1989 | 1 | 10 | 11 | |
| 912 |
+--------------------------------------------------+ |
| 913 |
| 1990 | 1 | 11 | 12 | |
| 914 |
+--------------------------------------------------+ |
| 915 |
| 1991 | 1 | 12 | 13 | |
| 916 |
+--------------------------------------------------+ |
| 917 |
|
| 918 |
PHASED IMPLEMENTATION PLAN |
| 919 |
|
| 920 |
The long-term goal of the IRI activity is to put in place a |
| 921 |
functional high-performance network available to scientists across |
| 922 |
the nation. To accomplish this goal, a steady evolution of |
| 923 |
capability is envisioned. This phased approach involves both |
| 924 |
technical and administrative aspects. |
| 925 |
|
| 926 |
Technical Phasing |
| 927 |
|
| 928 |
Currently, networks are being supported by a number of agencies as |
| 929 |
discussed in <a href="#section-2">Section 2</a>. Many are using the DoD protocol suite |
| 930 |
(TCP/IP, etc.) and others have incorporated or are incorporating |
| 931 |
mechanisms for interoperability with networks using the DoD protocol |
| 932 |
suite (e.g. MFEnet). Most have discussed eventual evolution to ISO |
| 933 |
protocols and beyond. By and large, most of these networks are |
| 934 |
hooked together in some mainly ad hoc manner already, some by |
| 935 |
pairwise arrangement and some through third party connections (e.g. |
| 936 |
a university network connected to two agency networks). |
| 937 |
|
| 938 |
There are two major shortcomings to this ad hoc connection, though. |
| 939 |
Performance is not adequate for advanced scientific environments, |
| 940 |
such as supercomputer usage, and community wide user support is not |
| 941 |
generally available. The phased apprach described below will allow |
| 942 |
these deficiencies to be overcome through coordinated action on the |
| 943 |
part of the various funding agencies. |
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Leiner [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 951 |
|
| 952 |
|
| 953 |
Phase I - Functional Interoperability |
| 954 |
|
| 955 |
The initial stage of the IRI would provide for sharing of the |
| 956 |
communications facilities (e.g. channels, satellites, etc.) by |
| 957 |
interconnecting the networks using the Internet Protocol and IP |
| 958 |
gateways. In addition, mechanisms will be installed (where required) |
| 959 |
and maintained to allow interconnection of the common user services, |
| 960 |
such as electronic mail. This will allow sharing of resources |
| 961 |
attached to the network, such as supercomputers. [7] [8] Note: |
| 962 |
actual use of facilities other than mail would require arrangements |
| 963 |
with the various responsible parties for each host. For example, to |
| 964 |
login to a host not only requires network access; it also requires a |
| 965 |
login account on that host. |
| 966 |
|
| 967 |
Specific steps to be undertaken in Phase I are the following: |
| 968 |
|
| 969 |
Gateways will be purchased and installed where needed to |
| 970 |
interconnect the agency networks. The location and performance of |
| 971 |
these gateways will be specified by the IRIO and approved by the |
| 972 |
Policy Board. This engineering will take into account an estimate of |
| 973 |
current and future traffic requirements as well as existing |
| 974 |
interconnecting gateways. It may also result in a recommendation |
| 975 |
that some or all existing gateways between agency networks be |
| 976 |
replaced with common hardware so that adequate management of the |
| 977 |
interconnection can be achieved. |
| 978 |
|
| 979 |
An IRI operations and management center will be established for the |
| 980 |
interconnecting gateways. [9] [10] This perhaps could be done in |
| 981 |
conjunction with a network management center for another set of |
| 982 |
gateways, e.g. those supported by DARPA or NSF. |
| 983 |
|
| 984 |
The requirement for application gateways or other techniques to |
| 985 |
interconnect communities using different protocols will be |
| 986 |
investigated and a recommendation made by the IRIO in conjuction |
| 987 |
with the IRAB. The appropriate mechanisms will be installed by the |
| 988 |
IRIO at the direction of the Policy Board. |
| 989 |
|
| 990 |
An initial user services facility will be established. This facility |
| 991 |
will provide at a minimum such services as a white pages of users |
| 992 |
(similar to the current Internet "whois" service) and a means for |
| 993 |
making accessible standard networking software. |
| 994 |
|
| 995 |
The IRAB, in coordination with the Policy Board, will draft a |
| 996 |
coordinated research plan for the development of the new |
| 997 |
technologies required for evolution of the IRI. |
| 998 |
|
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Leiner [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
Phase II - Full IRI Capability |
| 1010 |
|
| 1011 |
Phase II will make the IRI fully functional with enhanced |
| 1012 |
capabilities and performance. |
| 1013 |
|
| 1014 |
High performance gateways with appropriate new capabilities and |
| 1015 |
functions will be installed, replacing and/or augmenting the |
| 1016 |
gateways in place from Phase I. The functionality and performance |
| 1017 |
of these gateways will be specified based on the experience from |
| 1018 |
Phase I use, the anticipated new uses of the network, and the state |
| 1019 |
of the art technologies available as a result of the ongoing |
| 1020 |
research. |
| 1021 |
|
| 1022 |
The basic user services facility will be mature and support network |
| 1023 |
operation. New capabilities will be developed to support specific |
| 1024 |
scientific communities (such as a data base of software used by a |
| 1025 |
specific community and its availability over the network.) |
| 1026 |
|
| 1027 |
A high performance backbone network wil be installed if needed to |
| 1028 |
connect high performance agency networks. [11] [12] This is |
| 1029 |
anticipated because of the move in several agencies to provide high |
| 1030 |
bandwidth networks in support of such activities as supercomputer |
| 1031 |
access. |
| 1032 |
|
| 1033 |
The introduction and use of international standards will be |
| 1034 |
investigated and a plan developed for providing more services to the |
| 1035 |
broad scientific community through use of these standards. |
| 1036 |
|
| 1037 |
Administrative Phasing |
| 1038 |
|
| 1039 |
The goal of the IRI is to get to a fully cooperating and managed |
| 1040 |
interagency research internet involving most if not all of the |
| 1041 |
agencies supporting scientific research. Recognizing that currently, |
| 1042 |
the major research networking players (both networking for research |
| 1043 |
and research in networking) are DOE, NASA, DARPA, and NSF, the |
| 1044 |
following steps are recommended: |
| 1045 |
|
| 1046 |
The first and critical step is to establish a four agency Memorandum |
| 1047 |
of Agreement (MOA) to interconnect the agency networks and to share |
| 1048 |
the costs of interconnection, transit networks, and an operations |
| 1049 |
center. A management structure should be agreed upon as outlined |
| 1050 |
above. Agreement must also be reached on the need to fund an |
| 1051 |
ongoing research and engineering activity to evolve the internet. |
| 1052 |
|
| 1053 |
A Policy Board and Technical Advisory Board should be established as |
| 1054 |
quickly as possible to assure appropriate guidance and direction. |
| 1055 |
|
| 1056 |
The Policy Board shall then select an agency to handle the |
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Leiner [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
administrative and contractual actions with the IRIO. |
| 1066 |
|
| 1067 |
A non-profit organization shall then be selected by that agency |
| 1068 |
through an appropriate procurement mechanism to be the IRIO. The |
| 1069 |
Policy Board of the IRI shall be the selection panel. |
| 1070 |
|
| 1071 |
The initial four agencies shall transfer the agreed upon funds to |
| 1072 |
the selected contracting agency on equal basis to start. |
| 1073 |
|
| 1074 |
These funds will then allow the contracting agency to establish a |
| 1075 |
contract for the IRIO with the selected non-profit organization. |
| 1076 |
|
| 1077 |
The IRIO can then establish sub-contracts for engineering, |
| 1078 |
procurement, installation, and management of gateways and operation |
| 1079 |
of the user services center. |
| 1080 |
|
| 1081 |
To initiate the research coordination, the following steps will be |
| 1082 |
accomplished. |
| 1083 |
|
| 1084 |
The Internet Activities Board will evolve into the Internet Research |
| 1085 |
Activities Board, through added membership and charter revision. |
| 1086 |
|
| 1087 |
Additional task forces will be formed as needed to reflect the |
| 1088 |
expanded areas of research interest. |
| 1089 |
|
| 1090 |
Once the IRI is established and operating, the funding and use of |
| 1091 |
the IRI will be reviewed to determine if equal funding is equitable. |
| 1092 |
If not, the IRIO should be tasked to develop a recommendation for a |
| 1093 |
practical cost allocation scheme. In addition, once the IRI has |
| 1094 |
proved itself to be successful, other agencies will join the IRI |
| 1095 |
and provide additional funding. |
| 1096 |
|
| 1097 |
INDUSTRY ROLE |
| 1098 |
|
| 1099 |
This report has thus far addressed the interconnection of agency |
| 1100 |
supported networks and the use of such an internet by agency |
| 1101 |
supported researchers. However, industry also has a need for a |
| 1102 |
similar infrastructure to support its research activities. [13] |
| 1103 |
[14]. Note that this refers only to industrial research activities. |
| 1104 |
It is not envisioned, nor would it be appropriate, for the IRI to |
| 1105 |
provide a communications system for normal industrial activities. |
| 1106 |
Regulatory concerns make it difficult for industry to connect to a |
| 1107 |
network that is supported by a federal agency in pursuit of the |
| 1108 |
agency mission. |
| 1109 |
|
| 1110 |
The IRI structure above, though, may permit the connection of |
| 1111 |
industrial research organizations. Since the IRIO is a non-profit |
| 1112 |
non-government organization, it would be able to accept funds from |
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Leiner [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
industry as a fair share of the costs of using the IRI. These funds |
| 1122 |
in turn can be used to expand the networking resources so that no |
| 1123 |
degradation of service is felt by the users suppported by the |
| 1124 |
federal agencies. This topic would need to be discussed further by |
| 1125 |
the Policy Board and the organization selected as the IRIO. |
| 1126 |
|
| 1127 |
SUMMARY AND CONCLUSIONS |
| 1128 |
|
| 1129 |
The interconnection of the various agency networks supporting |
| 1130 |
scientific research into an overall infrastructure in support of |
| 1131 |
such research represents an exciting opportunity. This report |
| 1132 |
recommends an approach and a specific set of actions that can |
| 1133 |
achieve that goal. It is hoped that, regardless of the mechanism |
| 1134 |
used, that the Federal agencies involved recognize the importance of |
| 1135 |
providing an appropriate national infrastructure in support of |
| 1136 |
scientific research and take action to make such an infrastructure a |
| 1137 |
reality. |
| 1138 |
|
| 1139 |
ACKNOWLEDGEMENT |
| 1140 |
|
| 1141 |
This report was prepared with advice and comments from a large |
| 1142 |
number of people, including the members of the FCCSET Committee |
| 1143 |
Network Working Group and the Internet Activities Board. Their |
| 1144 |
input is greatly appreciated, and I hope that this report represents |
| 1145 |
a consensus on both the need for the IRI and the proposed approach. |
| 1146 |
|
| 1147 |
|
| 1148 |
|
| 1149 |
|
| 1150 |
|
| 1151 |
|
| 1152 |
|
| 1153 |
|
| 1154 |
|
| 1155 |
|
| 1156 |
|
| 1157 |
|
| 1158 |
|
| 1159 |
|
| 1160 |
|
| 1161 |
|
| 1162 |
|
| 1163 |
|
| 1164 |
|
| 1165 |
|
| 1166 |
|
| 1167 |
|
| 1168 |
|
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Leiner [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
APPENDIX A - FUNDING BREAKDOWN |
| 1178 |
|
| 1179 |
This appendix provides the details for the budgetary estimates of |
| 1180 |
Table 1. |
| 1181 |
|
| 1182 |
Gateways |
| 1183 |
|
| 1184 |
Gateways will be required between the various agency (and perhaps |
| 1185 |
regional) networks. As an upper bound, assume one IRI gateway per |
| 1186 |
state times $40K per gateway, spread out over two years, for a |
| 1187 |
capital cost of $1M per year for first two years. |
| 1188 |
|
| 1189 |
Operation Center |
| 1190 |
|
| 1191 |
The IRI operations center will have to engineer the location and |
| 1192 |
capacity of the gateways, as well as install, operate and maintain |
| 1193 |
them. It also will need to coordinate support and maintenance of |
| 1194 |
end-to-end service, helping to identify and correct problems in the |
| 1195 |
interconnections. Costs are estimated as two people round the clock |
| 1196 |
to man the operations center and three full time people to |
| 1197 |
coordinate, operate, and engineer the IRI. Using an estimate of |
| 1198 |
$120K (including other direct costs (ODC)) per year for an operator |
| 1199 |
and $200K per year for other activities, and translating 2 people |
| 1200 |
round the clock into 9 people results in a total annual cost of |
| 1201 |
$1.7M. In addition, equipment costs of roughly $500K per year can be |
| 1202 |
expected. |
| 1203 |
|
| 1204 |
Transit Networks |
| 1205 |
|
| 1206 |
It is expected that support of at least one transit network will be |
| 1207 |
necessary. This may involve reimbursement to one of the agencies for |
| 1208 |
use of their network, or may involve operations and maintenance of |
| 1209 |
an IRI dedicated network. An estimate for these costs, based on |
| 1210 |
historical data for operating the Arpanet, is $4M per year. |
| 1211 |
|
| 1212 |
User Support Organization |
| 1213 |
|
| 1214 |
To provide effective support as discussed above will require a staff |
| 1215 |
available during working hours. A reasonable estimate for the costs |
| 1216 |
of such an organization is 5 people times $200K per year, or $1M per |
| 1217 |
year (including ODC). In addition, there will be capital equipment |
| 1218 |
costs in the first two years totalling roughly $2M. |
| 1219 |
|
| 1220 |
|
| 1221 |
|
| 1222 |
|
| 1223 |
|
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Leiner [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
REFERENCES |
| 1234 |
|
| 1235 |
1. FCCSET Committee on Very High Performance Computing Network |
| 1236 |
Working Group, Report on Interagency Networking for Research |
| 1237 |
Programs, February 1986. |
| 1238 |
|
| 1239 |
2. Cerf, V.G. and P. Kirstein, "Issues in packet-network |
| 1240 |
interconnection," Proceedings of the IEEE, pp. 1386-1408, |
| 1241 |
November 1978 |
| 1242 |
|
| 1243 |
3. Cerf, V.G. and E. Cain, "The Dod intenet architecture model, |
| 1244 |
"Computer Networks, pp. 307-318, July 1983. |
| 1245 |
|
| 1246 |
4. Leiner, B.M., J. Postel, R. Cole, and D. Mills, "The DARPA |
| 1247 |
internet protocol suite," IEEE communications Magazine |
| 1248 |
March 1985. |
| 1249 |
|
| 1250 |
5. Defense Advanced Research Projects Agency, A History of the |
| 1251 |
Arpanet: The First Decade, Defense Advanced Research Projects |
| 1252 |
Agency, April 1981. (Defense Tech. Info. Center AD A1 15440) |
| 1253 |
|
| 1254 |
6. Jacobs, I.M. et. al., "General purpose satellite networks," |
| 1255 |
Proceedings of the IEEE pp. 1448-1467, November 1978 |
| 1256 |
|
| 1257 |
7. Tobagi, F., R. Binder, and B.M. Leiner, "Packet radio and |
| 1258 |
satellite networks," IEEE Communications Magazine, November |
| 1259 |
1984. |
| 1260 |
|
| 1261 |
8. Kahn, R.E. et. al., "Advances in packet radio technology," |
| 1262 |
Proceedings of the IEEE pp. 1468-1496, November |
| 1263 |
|
| 1264 |
9. Clark, D. et. al., "An introduction to local area |
| 1265 |
networks,", Proceedings of the IEEE, November 1978 |
| 1266 |
|
| 1267 |
10. Lederberg, J., "Digital communications and the conduct |
| 1268 |
of science: the new literacy," vol. 66, pp. 1314-1319, |
| 1269 |
November 1978. |
| 1270 |
|
| 1271 |
11. Hoskins, J.C. and J.S. Quaterman, "Notable Computer |
| 1272 |
Networks,", pp. 932-971, October 1986. |
| 1273 |
|
| 1274 |
12. Dennings, P.J., A.C. Hearn, and C.W. Kern, "History and |
| 1275 |
overview of CSNET," pp. 138-145, March 1983. |
| 1276 |
|
| 1277 |
13. Comer, D., "The computer science research network |
| 1278 |
CSNET: A history and status report", vol. 26, pp. 747-753, |
| 1279 |
October 1983. |
| 1280 |
|
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Leiner [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc1015">RFC 1015</a> IRI Plan July 1987</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
14. Bailey, R.R. NAS: supercomputing master tool for |
| 1290 |
aeronautics Aerospace America, pp. 118-121, January 1985 |
| 1291 |
|
| 1292 |
15. Jennings, D.M., L.H. Landweber, I.H. Fuchs, W.R. Adrion |
| 1293 |
"Computer Networking for Scientist Science" vol. 231 |
| 1294 |
pp. 943-950, February 1986 |
| 1295 |
|
| 1296 |
16. Cerf, V.G. R.E. Kahn, "A protocol for packet network |
| 1297 |
intercommunication, IEEE Transactions on Communications |
| 1298 |
vol. COM-22, May 1974 |
| 1299 |
|
| 1300 |
17. Zimmerman, H. "OSI reference model - the ISO model of |
| 1301 |
architecture for open systems intercommunications, IEEE |
| 1302 |
Transactions on Communications vol. COM-28 pp. 425-432 |
| 1303 |
April 1980 |
| 1304 |
|
| 1305 |
18. Defense Communications Agency, MIL STD 1777: Internet |
| 1306 |
Protocol, 1983 |
| 1307 |
|
| 1308 |
19. Defense Communications Agency, MIL STD 1778: Transmission |
| 1309 |
Control Protocol Defense Communications Agency, 1983 |
| 1310 |
|
| 1311 |
20. Defense Communications Agency, MIL STD 1780: File Transfer |
| 1312 |
Protocol Defense Communications Agency, 1985 |
| 1313 |
|
| 1314 |
21. Defense Communications Agency, MIL STD 1781: Simple Mail |
| 1315 |
Transfer Protocol Defense Communications Agency, 1985 |
| 1316 |
|
| 1317 |
22. Defense Communications Agency, MIL STD 1782: Telnet |
| 1318 |
Protocol Defense Communications Agency, 1985 |
| 1319 |
|
| 1320 |
23. Leiner, B.M. and M. Bishop, Research Institute for Advanced |
| 1321 |
Computer Science Access Control and Privacy in Large |
| 1322 |
Distribution Systems, RIACS TR 86.6, March 1986 |
| 1323 |
|
| 1324 |
|
| 1325 |
|
| 1326 |
|
| 1327 |
|
| 1328 |
|
| 1329 |
|
| 1330 |
|
| 1331 |
|
| 1332 |
|
| 1333 |
|
| 1334 |
|
| 1335 |
|
| 1336 |
|
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
Leiner [Page 24] |
| 1341 |
</pre> |