Debian Codegraph @

rfc1120.html

raw
1 <pre>Network Working Group V. Cerf
2 Request for Comments: 1120 NRI
3 September 1989
4
5
6 <span class="h1">The Internet Activities Board</span>
7
8 Status of this Memo
9
10 This RFC provides a history and description of the Internet
11 Activities Board (IAB) and its subsidiary organizations. This memo
12 is for informational use and does not constitute a standard.
13 Distribution of this memo is unlimited.
14
15 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
16
17 In 1968, the U.S. Defense Advanced Research Projects Agency (DARPA)
18 initiated an effort to develop a technology which is now known as
19 packet switching. This technology had its roots in message switching
20 methods, but was strongly influenced by the development of low-cost
21 minicomputers and digital telecommunications techniques during the
22 mid-1960's [BARAN 64, ROBERTS 70, HEART 70, ROBERTS 78]. A very
23 useful survey of this technology can be found in [IEEE 78].
24
25 During the early 1970's, DARPA initiated a number of programs to
26 explore the use of packet switching methods in alternative media
27 including mobile radio, satellite and cable [IEEE 78, IEEE 87].
28 Concurrently, Xerox Palo Alto Research Center (PARC) began an
29 exploration of packet switching on coaxial cable which ultimately led
30 to the development of Ethernet local area networks [METCALFE 76].
31
32 The successful implementation of packet radio and packet satellite
33 technology raised the question of interconnecting ARPANET with other
34 types of packet nets. A possible solution to this problem was
35 proposed by Cerf and Kahn [CERF 74] in the form of an internetwork
36 protocol and a set of gateways to connect the different networks.
37 This solution was further developed as part of a research program in
38 internetting sponsored by DARPA and resulted in a collection of
39 computer communications protocols based on the original Transmission
40 Control Protocol (TCP) and its lower level counterpart, Internet
41 Protocol (IP). Together, these protocols, along with many others
42 developed during the course of the research, are referred to as the
43 TCP/IP Protocol Suite [LEINER 85, POSTEL 85, CERF 82, CLARK 86, <a href="./rfc1100">RFC</a>
44 <a href="./rfc1100">1100</a>].
45
46 In the early stages of the Internet research program, only a few
47 researchers worked to develop and test versions of the internet
48 protocols. Over time, the size of this activity increased until, in
49
50
51
52 <span class="grey">Cerf [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1120">RFC 1120</a> The IAB September 1989</span>
55
56
57 1979, it was necessary to form an informal committee to guide the
58 technical evolution of the protocol suite. This group was called the
59 Internet Configuration Control Board (ICCB) and was established by
60 Dr. Vinton Cerf who was then the DARPA program manager for the
61 effort. Dr. David C. Clark of the Lab for Computer Science at
62 Massachusetts Institute of Technology was named the chairman of this
63 committee.
64
65 In January, 1983, the Defense Communications Agency, then responsible
66 for the operation of the ARPANET, declared the TCP/IP protocol suite
67 to be standard for the ARPANET and all systems on the network
68 converted from the earlier Network Control Program (NCP) to TCP/IP.
69 Late that year, the ICCB was reorganized by Dr. Barry Leiner, Cerf's
70 successor at DARPA, around a series of task forces considering
71 different technical aspects of internetting. The re-organized group
72 was named the Internet Activities Board.
73
74 As the Internet expanded, it drew support from U.S. Government
75 organizations including DARPA, the National Science Foundation (NSF),
76 the Department of Energy (DOE) and the National Aeronautics and Space
77 Administration (NASA). Key managers in these organizations,
78 responsible for computer networking research and development, formed
79 an informal Federal Research Internet Coordinating Committee (FRICC)
80 to coordinate U.S. Government support for and development and use of
81 the Internet system. The FRICC sponsors most of the U.S. research on
82 internetting, including support for the Internet Activities Board and
83 its subsidiary organizations.
84
85 At the international level, a Coordinating Committee for
86 Intercontinental Research Networks (CCIRN) has been formed which
87 includes the U.S. FRICC and its counterparts in North America and
88 Europe. The CCIRN provides a forum for cooperative planning among
89 the principal North American and European research networking bodies.
90
91 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Internet Activities Board</span>
92
93 The Internet Activities Board (IAB) is the coordinating committee for
94 Internet design, engineering and management. The Internet is a
95 collection of over a thousand packet switched networks located
96 principally in the U.S., but also includes systems in many other
97 parts of the world, all interlinked and operating using the protocols
98 of the TCP/IP protocol suite. The IAB is an independent committee of
99 researchers and professionals with a technical interest in the health
100 and evolution of the Internet system. Membership changes with time
101 to adjust to the current realities of the research interests of the
102 participants, the needs of the Internet system and the concerns of
103 the U.S. Government, university and industrial sponsors of the
104 elements of the Internet.
105
106
107
108 <span class="grey">Cerf [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1120">RFC 1120</a> The IAB September 1989</span>
111
112
113 IAB members are deeply committed to making the Internet function
114 effectively and evolve to meet a large scale, high speed future. All
115 IAB members are required to have at least one other major role in the
116 Internet community in addition to their IAB membership. New members
117 are appointed by the chairman of the IAB, with the advice and consent
118 of the remaining members. The chairman serves a term of two years.
119
120 The IAB focuses on the TCP/IP protocol suite, and extensions to the
121 Internet system to support multiple protocol suites.
122
123 The IAB has two principal subsidiary task forces:
124
125 1) Internet Engineering Task Force (IETF)
126
127 2) Internet Research Task Force (IRTF)
128
129 Each of these Task Forces is led by a chairman and guided by a
130 Steering Group which reports to the IAB through its chairman. Each
131 task force is organized by the chairman, as required, to carry out
132 its charter. For the most part, a collection of Working Groups
133 carries out the work program of each Task Force.
134
135 All decisions of the IAB are made public. The principal vehicle by
136 which IAB decisions are propagated to the parties interested in the
137 Internet and its TCP/IP protocol suite is the Request for Comment
138 (RFC) note series. The archival RFC series was initiated in 1969 by
139 Dr. Stephen D. Crocker as a means of documenting the development of
140 the original ARPANET protocol suite [<a href="./rfc1000">RFC 1000</a>]. The editor-in-chief
141 of this series, Dr. Jonathan B. Postel, has maintained the quality
142 of and managed the archiving of this series since its inception. A
143 small proportion of the RFCs document Internet standards. Most of
144 them are intended to stimulate comment and discussion. The small
145 number which document standards are especially marked in a "status"
146 section to indicate the special status of the document. An RFC
147 summarizing the status of all standard RFCs is published regularly
148 [<a href="./rfc1100">RFC 1100</a>].
149
150 RFCs describing experimental protocols, along with other submissions
151 whose intent is merely to inform, are typically submitted directly to
152 the RFC Editor. A Standard RFC starts out as a Proposed Standard and
153 may be promoted to Draft Standard and finally Standard after suitable
154 review, comment, implementation, and testing.
155
156 Prior to publication of a Proposed Standard, Draft Standard or
157 Standard RFC, it is made available for comment through an on-line
158 Internet-Draft directory. Typically, these Internet-Drafts are
159 working documents of the IAB or of the working groups of the Internet
160 Engineering and Research Task Forces. Internet Drafts are either
161
162
163
164 <span class="grey">Cerf [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1120">RFC 1120</a> The IAB September 1989</span>
167
168
169 submitted to the RFC Editor for publication or discarded within three
170 months.
171
172 The IAB performs the following functions:
173
174 1) Sets Internet Standards,
175
176 2) Manages the RFC publication process,
177
178 3) Reviews the operation of the IETF and IRTF,
179
180 4) Performs strategic planning for the Internet, identifying
181 long-range problems and opportunities,
182
183 5) Acts as a technical policy liaison and representative for the
184 Internet community, and
185
186 6) Resolves technical issues which cannot be treated within the
187 IETF or IRTF frameworks.
188
189 To supplement its work via electronic mail, the IAB meets quarterly
190 to review the condition of the Internet, to review and approve
191 proposed changes or additions to the TCP/IP suite of protocols, to
192 set technical development priorities, to discuss policy matters which
193 may need the attention of the Internet sponsors, and to agree on the
194 addition or retirement of IAB members and on the addition or
195 retirement of task forces reporting to the IAB. Typically, two of
196 the quarterly meetings are by means of video teleconferencing
197 (provided, when possible, through the experimental Internet packet
198 video-conferencing system).
199
200 The IAB membership is currently as follows:
201
202 Vinton Cerf - Chairman
203 David Clark - IRTF Chairman
204 Phillip Gross - IETF Chairman
205 Jonathan Postel - RFC Editor
206 Robert Braden - Executive Director
207 Hans-Werner Braun - Member
208 Barry Leiner - Member
209 Daniel Lynch - Member
210 Stephen Kent - Member
211
212 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The Internet Engineering Task Force</span>
213
214 The Internet has grown to encompass a large number of widely geo-
215 graphically dispersed networks in academic and research communities.
216 It now provides an infrastructure for a broad community with various
217
218
219
220 <span class="grey">Cerf [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1120">RFC 1120</a> The IAB September 1989</span>
223
224
225 interests. Moreover, the family of Internet protocols and system
226 components has moved from experimental to commercial development. To
227 help coordinate the operation, management and evolution of the
228 Internet, the IAB established the Internet Engineering Task Force
229 (IETF).
230
231 The IETF is chaired by Mr. Phillip Gross and managed by its Internet
232 Engineering Steering Group (IESG). The IAB has delegated to the IESG
233 the general responsibility for making the Internet work and for the
234 resolution of all short- and mid-range protocol and architectural
235 issues required to make the Internet function effectively.
236
237 The charter of the IETF includes:
238
239 1) Responsibility for specifying the short and mid-term
240 Internet protocols and architecture and recommending
241 standards for IAB approval.
242
243 2) Provision of a forum for the exchange of information within the
244 Internet community.
245
246 3) Identification of pressing and relevant short- to mid-range
247 operational and technical problem areas and convening of
248 Working Groups to explore solutions.
249
250 The Internet Engineering Task Force is a large open community of
251 network designers, operators, vendors, and researchers concerned with
252 the Internet and the Internet protocol suite. It is organized around
253 a set of eight technical areas, each managed by a technical area
254 director. In addition to the IETF Chairman, the area directors make
255 up the IESG membership. Each area director has primary
256 responsibility for one area of Internet engineering activity, and
257 hence for a subset of the IETF Working Groups. The area directors
258 have jobs of critical importance and difficulty and are selected not
259 only for their technical expertise but also for their managerial
260 skills and judgment. At present, the eight technical areas and
261 chairs are:
262
263 1) Applications - TBD
264 2) Host Services - Craig Partridge
265 3) Internet Services - Noel Chiappa
266 4) Routing - Robert Hinden
267 5) Network Management - David Crocker
268 6) OSI Coexistence - Ross Callon and Robert Hagens
269 7) Operations - TBD
270 8) Security - TBD
271
272 The work of the IETF is performed by subcommittees known as Working
273
274
275
276 <span class="grey">Cerf [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1120">RFC 1120</a> The IAB September 1989</span>
279
280
281 Groups. There are currently more than 20 of these. Working Groups
282 tend to have a narrow focus and a lifetime bounded by completion of a
283 specific task, although there are exceptions. The IETF is a major
284 source of proposed protocol standards, for final approval by the IAB.
285
286 The IETF meets quarterly and extensive minutes of the plenary
287 proceedings as well as reports from each of the working groups are
288 issued by the IAB Secretariat, at the Corporation for National
289 Research Initiatives.
290
291 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. The Internet Research Task Force</span>
292
293 To promote research in networking and the development of new
294 technology, the IAB established the Internet Research Task Force
295 (IRTF).
296
297 In the area of network protocols, the distinction between research
298 and engineering is not always clear, so there will sometimes be
299 overlap between activities of the IETF and the IRTF. There is, in
300 fact, considerable overlap in membership between the two groups. This
301 overlap is regarded as vital for cross-fertilization and technology
302 transfer. In general, the distinction between research and
303 engineering is one of viewpoint and sometimes (but not always) time-
304 frame. The IRTF is generally more concerned with understanding than
305 with products or standard protocols, although specific experimental
306 protocols may have to be developed, implemented and tested in order
307 to gain understanding.
308
309 The IRTF is a community of network researchers, generally with an
310 Internet focus. The work of the IRTF is governed by its Internet
311 Research Steering Group (IRSG). The chairman of the IRTF and IRSG is
312 David Clark. The IRTF is organized into a number of Research Groups
313 (RGs) whose chairs are appointed by the chairman of the IRSG. The RG
314 chairs and others selected by the IRSG chairman serve on the IRSG.
315
316 These groups typically have 10 to 20 members, and each covers a broad
317 area of research, pursuing specific topics, determined at least in
318 part by the interests of the members and by recommendations of the
319 IAB.
320
321 The current members of the IRSG are as follows:
322
323 David Clark - Chairman
324 Robert Braden - End-to-End Services
325 Douglas Comer - Member at Large
326 Deborah Estrin - Autonomous Networks
327
328
329
330
331
332 <span class="grey">Cerf [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1120">RFC 1120</a> The IAB September 1989</span>
335
336
337 Stephen Kent - Privacy and Security
338 Keith Lantz - User Interfaces
339 David Mills - Member at Large
340
341 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. The Near-term Agenda of the IAB</span>
342
343 There are seven principal foci of IAB attention for the period 1989 -
344 1990:
345
346 1) Operational Stability
347 2) User Services
348 3) OSI Coexistence
349 4) Testbed Facilities
350 5) Security
351 6) Getting Big
352 7) Getting Fast
353
354 Operational stability of the Internet is a critical concern for all
355 of its users. Better tools are needed for gathering operational
356 data, to assist in fault isolation at all levels and to analyze the
357 performance of the system. Opportunities abound for increased
358 cooperation among the operators of the various Internet components
359 [<a href="./rfc1109">RFC 1109</a>]. Specific, known problems should be dealt with, such as
360 implementation deficiencies in some version of the BIND domain name
361 service resolver software. To the extent that the existing Exterior
362 Gateway Protocol (EGP) is only able to support limited topologies,
363 constraints on topological linkages and allowed transit paths should
364 be enforced until a more general Inter-Autonomous System routing
365 protocol can be specified. Flexibility for Internet implementation
366 would be enhanced by the adoption of a common internal gateway
367 routing protocol by all vendors of internet routers. A major effort
368 is recommended to achieve conformance to the Host Requirements RFCs
369 which are to be published early in the fourth quarter of calendar
370 1989.
371
372 Among the most needed user services, the White Pages (an electronic
373 mailbox directory service) seems the most pressing. Efforts should
374 be focused on widespread deployment of these capabilities in the
375 Internet by mid-1990. The IAB recommends that existing white pages
376 facilities and newer ones, such as X.500, be populated with up-to-
377 date user information and made accessible to Internet users and users
378 of other systems (e.g., commercial email carriers) linked to the
379 Internet. Connectivity with commercial electronic mail carriers
380 should be vigorously pursued, as well as links to other network
381 research communities in Europe and the rest of the world.
382
383 Development and deployment of privacy-enhanced electronic mail
384 software should be accelerated in 1990 after release of public domain
385
386
387
388 <span class="grey">Cerf [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc1120">RFC 1120</a> The IAB September 1989</span>
391
392
393 software implementing the private electronic mail standards [RFC
394 1113, <a href="./rfc1114">RFC 1114</a>, and <a href="./rfc1115">RFC 1115</a>]. Finally, support for new or enhanced
395 applications such as computer-based conferencing, multi-media
396 messaging and collaboration support systems should be developed.
397
398 The National Network Testbed (NNT) resources planned by the FRICC
399 should be applied to support conferencing and collaboration protocol
400 development and application experiments and to support multi-vendor
401 router interoperability testing (e.g., interior and exterior routing,
402 network management, multi-protocol routing and forwarding).
403
404 With respect to growth in the Internet, architectural attention
405 should be focused on scaling the system to hundreds of millions of
406 users and hundreds of thousands of networks. The naming, addressing,
407 routing and navigation problems occasioned by such growth should be
408 analyzed. Similarly, research should be carried out on analyzing the
409 limits to the existing Internet architecture, including the ability
410 of the present protocol suite to cope with speeds in the gigabit
411 range and latencies varying from microseconds to seconds in duration.
412
413 The Internet should be positioned to support the use of OSI protocols
414 by the end of 1990 or sooner, if possible. Provision for multi-
415 protocol routing and forwarding among diverse vendor routes is one
416 important goal. Introduction of X.400 electronic mail services and
417 interoperation with <a href="./rfc822">RFC 822</a>/SMTP [RFC 822, <a href="./rfc821">RFC 821</a>, <a href="./rfc987">RFC 987</a>, <a href="./rfc1026">RFC</a>
418 <a href="./rfc1026">1026</a>] should be targeted for 1990 as well. These efforts will need
419 to work in conjunction with the White Pages services mentioned above.
420 The IETF, in particular, should establish liaison with various OSI
421 working groups (e.g., at NIST, RARE, Network Management Forum) to
422 coordinate planning for OSI introduction into the Internet and to
423 facilitate registration of information pertinent to the Internet with
424 the various authorities responsible for OSI standards in the United
425 States.
426
427 Security Considerations
428
429 Finally, with respect to security, a concerted effort should be made
430 to develop guidance and documentation for Internet host managers
431 concerning configuration management, known security problems (and
432 their solutions) and software and technologies available to provide
433 enhanced security and privacy to the users of the Internet.
434
435 REFERENCES
436
437 [BARAN 64] Baran, P., et al, "On Distributed Communications",
438 Volumes I-XI, RAND Corporation Research Documents, August 1964.
439
440 [CERF 74] Cerf V., and R. Kahn, "A Protocol for Packet Network
441
442
443
444 <span class="grey">Cerf [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc1120">RFC 1120</a> The IAB September 1989</span>
447
448
449 Interconnection", IEEE Trans. on Communications, Vol. COM-22,
450 No. 5, pp. 637-648, May 1974.
451
452 [CERF 82] Cerf V., and E. Cain, "The DoD Internet Protocol
453 Architecture", Proceedings of the SHAPE Technology Center
454 Symposium on Interoperability of Automated Data Systems,
455 November 1982. Also in Computer Networks and ISDN,
456 Vol. 17, No. 5, October 1983.
457
458 [CLARK 86] Clark, D., "The Design Philosophy of the DARPA
459 Internet protocols", Proceedings of the SIGCOMM '88 Symposium,
460 Computer Communications Review, Vol. 18, No. 4, pp. 106-114,
461 August 1988.
462
463 [HEART 70] Heart, F., R. Kahn, S. Ornstein, W. Crowther, and D.
464 Walden, "The Interface Message Processor for the ARPA Computer
465 Network", AFIPS Conf. Proc. 36, pp. 551-567, June 1970.
466
467 [IEEE 78] Kahn, R. (Guest Editor), K. Uncapher, and
468 H. Van Trees (Associate Guest Editors), Proceedings of the
469 IEEE, Special Issue on Packet Communication Networks,
470 Volume 66, No. 11, pp. 1303-1576, November 1978.
471
472 [IEEE 87] Leiner, B. (Guest Editor), D. Nielson, and
473 F. Tobagi (Associate Guest Editors), Proceedings of the
474 IEEE, Special Issue on Packet Radio Networks, Volume 75,
475 No. 1, pp. 1-272, January 1987.
476
477 [LEINER 85] Leiner, B., R. Cole, J. Postel, and D. Mills,
478 "The DARPA Protocol Suite", IEEE INFOCOM 85, Washington, D.C.,
479 March 1985. Also in IEEE Communications Magazine, March 1985.
480
481 [METCALFE 76] Metcalfe, R., and D. Boggs, "Ethernet:
482 Distributed Packet for Local Computer Networks", Communications
483 of the ACM, Vol. 19, No. 7, pp. 395-404, July 1976.
484
485 [POSTEL 85] Postel, J., "Internetwork Applications Using the
486 DARPA Protocol Suite", IEEE INFOCOM 85, Washington, D.C.,
487 March 1985.
488
489 [<a id="ref-RFC 821">RFC 821</a>] Postel, J., "Simple Mail Transfer Protocol", <a href="./rfc821">RFC 821</a>,
490 USC/Information Sciences Institute, August 1982.
491
492 [<a id="ref-RFC 822">RFC 822</a>] Crocker, D., "Standard for the Format of ARPA Internet
493 Text Messages", <a href="./rfc822">RFC 822</a>, University of Delaware, August 1982.
494
495 [<a id="ref-RFC 987">RFC 987</a>] Kille, S., "Mapping between X.400 and <a href="./rfc822">RFC 822</a>",
496 University College London, June 1986.
497
498
499
500 <span class="grey">Cerf [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc1120">RFC 1120</a> The IAB September 1989</span>
503
504
505
506 [<a id="ref-RFC 1000">RFC 1000</a>] Reynolds, J., and J. Postel, "The Request for
507 Comments References Guide", USC/Information Sciences Institute,
508 <a href="./rfc1000">RFC 1000</a>, August 1987.
509
510 [<a id="ref-RFC 1026">RFC 1026</a>] Kille, S., "Addendum to <a href="./rfc987">RFC 987</a>: (Mapping between
511 X.400 and <a href="./rfc822">RFC 822</a>)", <a href="./rfc1026">RFC 1026</a>, University College London,
512 September 1987.
513
514 [<a id="ref-RFC 1100">RFC 1100</a>] Postel, J. (Editor), "IAB Official Protocol
515 Standards", <a href="./rfc1100">RFC 1100</a>, April 1989.
516
517 [<a id="ref-RFC 1109">RFC 1109</a>] Cerf, V., "Report of the Second Ad Hoc Network
518 Management Review Group", <a href="./rfc1109">RFC 1109</a>, NRI, August 1989.
519
520 [<a id="ref-RFC 1113">RFC 1113</a>] Linn, J., "Privacy Enhancement for Internet
521 Electronic Mail: Part I -- Message Encipherment and
522 Authentication Procedures", <a href="./rfc1113">RFC 1113</a>, IAB Privacy Task
523 Force, August 1989.
524
525 [<a id="ref-RFC 1114">RFC 1114</a>] Kent, S., and J. Linn, "Privacy Enhancement for
526 Internet Electronic Mail: Part II -- Certificate-based Key
527 Management", <a href="./rfc1114">RFC 1114</a>, IAB Privacy Task Force, August 1989.
528
529 [<a id="ref-RFC 1115">RFC 1115</a>] Linn, J., "Privacy Enhancement for Internet
530 Electronic Mail: Part III -- Algorithms, Modes and Identifiers",
531 <a href="./rfc1115">RFC 1115</a>, IAB Privacy Task Force, August 1989.
532
533 [ROBERTS 70] Roberts, L., and B. Wessler, "Computer Network
534 Development to Achieve Resource Sharing", pp. 543-549,
535 Proc. SJCC 1970.
536
537 [ROBERTS 78] Roberts, L., "Evolution of Packet Switching",
538 Proc. IEEE, Vol. 66, No. 11, pp. 1307-1313, November 1978.
539
540 Note: RFCs are available from the Network Information Center at
541 SRI International, 333 Ravenswood Ave., Menlo Park, CA 94025,
542 (1-800-235-3155), or on-line via anonymous file transfer from
543 NIC.DDN.MIL.
544
545
546
547
548
549
550
551
552
553
554
555
556 <span class="grey">Cerf [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc1120">RFC 1120</a> The IAB September 1989</span>
559
560
561 Author's Address
562
563 Vinton G. Cerf
564 Corporation for National Research Initiatives
565 1895 Preston White Drive, Suite 100
566 Reston, VA 22091
567
568 Phone: (703) 620-8990
569
570 EMail: [email protected]
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612 Cerf [Page 11]
613 </pre>