Debian Codegraph @

rfc1399.html

raw
1 <pre>Network Working Group J. Elliott
2 Request for Comments: 1399 ISI
3 Category: Informational January 1997
4
5
6 <span class="h1">Request for Comments Summary</span>
7
8 RFC Numbers 1300-1399
9
10 Status of This Memo
11
12 This RFC is a slightly annotated list of the 100 RFCs from <a href="./rfc1300">RFC 1300</a>
13 through RFCs 1399. This is a status report on these RFCs. This memo
14 provides information for the Internet community. It does not specify
15 an Internet standard of any kind. Distribution of this memo is
16 unlimited.
17
18 Note
19
20 Many RFCs, but not all, are Proposed Standards, Draft Standards, or
21 Standards. Since the status of these RFCs may change during the
22 standards processing, we note here only that they are on the
23 standards track. Please see the latest edition of "Internet Official
24 Protocol Standards" for the current state and status of these RFCs.
25 In the following, RFCs on the standards track are marked [STANDARDS-
26 TRACK].
27
28 RFC Author Date Title
29 --- ------ ---- -----
30
31 <span class="h2"><a class="selflink" id="section-1399" href="#section-1399">1399</a> Elliott </span> Jan 97 Requests For Comments Summary
32
33 This memo.
34
35
36 <span class="h2"><a class="selflink" id="section-1398" href="#section-1398">1398</a> Kastenholz </span> Jan 93 Definitions of Managed Objects for the
37 Ethernet-like Interface Types
38
39 This memo defines a portion of the Management Information Base (MIB) for
40 use with network management protocols in TCP/IP-based internets. In
41 particular, it defines objects for managing ehternet-like objects.
42 [STANDARDS-TRACK]
43
44
45
46
47
48
49
50
51
52 <span class="grey">Elliott Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
55
56
57 <span class="h2"><a class="selflink" id="section-1397" href="#section-1397">1397</a> Haskin </span> Jan 93 Default Route Advertisement In BGP2 and
58 BGP3 Versions of the Border Gateway
59 Protocol
60
61 This document speficies the recommendation of the BGP Working Group on
62 default route advertisement support in BGP2 [1] and BGP3 [2] versions of
63 the Border Gateway Protocol. [STANDARDS-TRACK]
64
65
66 <span class="h2"><a class="selflink" id="section-1396" href="#section-1396">1396</a> Crocker </span> Jan 93 The Process for Organization of Internet
67 Standards
68
69 This report provides a summary of the POISED Working Group (WG),
70 starting from the events leading to the formation of the WG to the end
71 of 1992. This memo provides information for the Internet community. It
72 does not specify an Internet standard.
73
74
75 <span class="h2"><a class="selflink" id="section-1395" href="#section-1395">1395</a> Reynolds </span> Jan 93 BOOTP Vendor Information Extensions
76
77 This RFC is a slight revision and extension of <a href="./rfc1048">RFC-1048</a> by Philip
78 Prindeville, who should be credited with the original work in this memo.
79 This memo will be updated as additional tags are defined. This edition
80 introduces Tag 14 for Merit Dump File, Tag 15 for Domain Name, Tag 16
81 for Swap Server and Tag 17 for Root Path. This memo is a status report
82 on the vendor information extensions used int the Bootstrap Protocol
83 (BOOTP).
84
85
86 <span class="h2"><a class="selflink" id="section-1394" href="#section-1394">1394</a> Robinson </span> Jan 93 Relationship of Telex Answerback Codes
87 to Internet Domains
88
89 This RFC gives the list, as best known, of all common Internet domains
90 and the conversion between specific country telex answerback codes and
91 Internet country domain identifiers. It also lists the telex code and
92 international dialing code, wherever it is available. It will also list
93 major Internet "Public" E-Mail addresses. This memo provides
94 information for the Internet community. It does not specify an Internet
95 standard.
96
97
98 <span class="h2"><a class="selflink" id="section-1393" href="#section-1393">1393</a> Malkin </span> Jan 93 Traceroute Using an IP Option
99
100 This document specifies a new IP option and ICMP message type which
101 duplicates the functionality of the existing traceroute method while
102 generating fewer packets and completing in a shorter time. This memo
103 defines an Experimental Protocol for the Internet community.
104
105
106
107
108 <span class="grey">Elliott Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1392" href="#section-1392">1392</a> Malkin </span> Jan 93 Internet Users' Glossary
114
115 There are many networking glossaries in existence. This glossary
116 concentrates on terms which are specific to the Internet. This memo
117 provides information for the Internet community. It does not specify an
118 Internet standard.
119
120
121 <span class="h2"><a class="selflink" id="section-1391" href="#section-1391">1391</a> Malkin </span> Jan 93 The Tao of IETF
122 A Guide for New Attendees of the
123 Internet Engineering Task Force
124
125 The purpose of this For Your Information (FYI) RFC is to explain to the
126 newcomers how the IETF works. This will give them a warm, fuzzy feeling
127 and enable them to make the meeting more productive for everyone. This
128 memo provides information for the Internet community. It does not
129 specify an Internet standard.
130
131
132 <span class="h2"><a class="selflink" id="section-1390" href="#section-1390">1390</a> Katz </span> Jan 93 Transmission of IP and ARP over FDDI
133 Networks
134
135 This memo defines a method of encapsulating the Internet Protocol (IP)
136 datagrams and Address Resolution Protocol (ARP) requests and replies on
137 Fiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK]
138
139
140 <span class="h2"><a class="selflink" id="section-1389" href="#section-1389">1389</a> Malkin </span> Jan 93 RIP Version 2 MIB Extension
141
142 This memo defines a portion of the Management Information Base (MIB) for
143 use with network management protocols in TCP/IP-based internets.
144 [STANDARDS-TRACK]
145
146
147 <span class="h2"><a class="selflink" id="section-1388" href="#section-1388">1388</a> Malkin </span> Jan 93 RIP Version 2
148 Carrying Additional Information
149
150 This document specifies an extension of the Routing Information Protocol
151 (RIP), as defined in [1], to expand the amount of useful information
152 carried in RIP packets and to add a measure of security. [STANDARDS-
153 TRACK]
154
155
156
157
158
159
160
161
162
163
164 <span class="grey">Elliott Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
167
168
169 <span class="h2"><a class="selflink" id="section-1387" href="#section-1387">1387</a> Malkin </span> Jan 93 RIP Version 2 Protocol Analysis
170
171 As required by Routing Protocol Criteria (<a href="./rfc1264">RFC 1264</a>), this report
172 documents the key features of the RIP-2 protocol and the current
173 implementation experience. This memo provides information for the
174 Internet community. It does not specify an Internet standard.
175
176
177 <span class="h2"><a class="selflink" id="section-1386" href="#section-1386">1386</a> Cooper </span> Dec 92 The US Domain
178
179 This is a description of the US Top Level Domains on the Internet. This
180 memo provides information for the Internet community. It does not
181 specify an Internet standard.
182
183
184 <span class="h2"><a class="selflink" id="section-1385" href="#section-1385">1385</a> Wang </span> Nov 92 EIP: The Extended Internet Protocol
185 A Framework for Maintaining Backward
186 Compatibility
187
188 EIP can substantially reduce the amount of modifications needed to the
189 current Internet systems and greatly ease the difficulties of
190 transition. This is an "idea" paper and discussion is strongly
191 encouraged on [email protected]. This memo provides
192 information for the Internet community. It does not specify an Internet
193 standard.
194
195
196 <span class="h2"><a class="selflink" id="section-1384" href="#section-1384">1384</a> Barker </span> Jan 93 Naming Guidelines for Directory Pilots
197
198 This document defines a number of naming guidelines. Alignment to these
199 guidelines is recommended for directory pilots. This memo provides
200 information for the Internet community. It does not specify an Internet
201 standard.
202
203
204 <span class="h2"><a class="selflink" id="section-1383" href="#section-1383">1383</a> Huitema </span> Dec 92 An Experiment in DNS Based IP Routing
205
206 Potential solutions to the routing explosion. This memo defines an
207 Experimental Protocol for the Internet community.
208
209
210 <span class="h2"><a class="selflink" id="section-1382" href="#section-1382">1382</a> Throop </span> Nov 92 SNMP MIB Extension for the X.25 Packet
211 Layer
212
213 This memo defines a portion of the Management Information Base (MIB) for
214 use with network management protocols in TCP/IP-based internets.
215 [STANDARDS-TRACK]
216
217
218
219
220 <span class="grey">Elliott Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
223
224
225 <span class="h2"><a class="selflink" id="section-1381" href="#section-1381">1381</a> Throop </span> Nov 92 SNMP MIB Extension for X.25 LAPB
226
227 This memo defines a portion of the Management Information Base (MIB) for
228 use with network management protocols in TCP/IP-based internets. In
229 particular, it defines objects for managing the Link Layer of X.25,
230 LAPB. [STANDARDS-TRACK]
231
232
233 <span class="h2"><a class="selflink" id="section-1380" href="#section-1380">1380</a> Gross </span> Nov 92 IESG Deliberations on Routing and
234 Addressing
235
236 This memo summarizes issues surrounding the routing and addressing
237 scaling problems in the IP architecture, and it provides a brief
238 background of the ROAD group and related activities in the Internet
239 Engineering Task Force (IETF). This memo provides information for the
240 Internet community. It does not specify an Internet standard.
241
242
243 <span class="h2"><a class="selflink" id="section-1379" href="#section-1379">1379</a> Braden </span> Nov 92 Extending TCP for Transactions --
244 Concepts
245
246 This memo discusses extension of TCP to provide transaction-oriented
247 service, without altering its virtual-circuit operation. This memo
248 provides information for the Internet community. It does not specify an
249 Internet standard.
250
251
252 <span class="h2"><a class="selflink" id="section-1378" href="#section-1378">1378</a> Parker </span> Nov 92 The PPP AppleTalk Control Protocol
253 (ATCP)
254
255 This document defines the NCP for establishing and configuring the
256 AppleTalk Protocol [3] over PPP. [STANDARDS-TRACK]
257
258
259 <span class="h2"><a class="selflink" id="section-1377" href="#section-1377">1377</a> Katz </span> Nov 92 The PPP OSI Network Layer Control
260 Protocol (OSINLCP)
261
262 This document defines the NCP for establishing and configuring OSI
263 Network Layer Protocols. [STANDARDS-TRACK]
264
265
266
267
268
269
270
271
272
273
274
275
276 <span class="grey">Elliott Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
279
280
281 <span class="h2"><a class="selflink" id="section-1376" href="#section-1376">1376</a> Senum </span> Nov 92 The PPP DECnet Phase IV Control
282 Protocol (DNCP)
283
284 This document defines the NCP for establishing and configuring Digital's
285 DNA Phase IV Routing protocol (DECnet Phase IV) over PPP. This document
286 applies only to DNA Phase IV Routing messages (both data and control),
287 and not to other DNA Phase IV protocols (MOP, LAT, etc.). [STANDARDS-
288 TRACK]
289
290
291 <span class="h2"><a class="selflink" id="section-1375" href="#section-1375">1375</a> Robinson </span> Oct 92 Suggestion for New Classes of IP
292 Addresses
293
294 This RFC suggests a change in the method of specifying the IP address to
295 add new classes of networks to be called F, G, H, and K, to reduce the
296 amount of wasted address space, and to increase the available IP address
297 number space, especially for smaller organizations or classes of
298 connectors that do not need or do not want a full Class C IP address.
299 This memo provides information for the Internet community. It does not
300 specify an Internet standard.
301
302
303 <span class="h2"><a class="selflink" id="section-1374" href="#section-1374">1374</a> Renwick </span> Oct 92 IP and ARP on HIPPI
304
305 The ANSI X3T9.3 committee has drafted a proposal for the encapsulation
306 of IEEE 802.2 LLC PDUs and, by implication, IP on HIPPI. Another X3T9.3
307 draft describes the operation of HIPPI physical switches. X3T9.3 chose
308 to leave HIPPI networking issues largely outside the scope of their
309 standards; this document discusses methods of using of ANSI standard
310 HIPPI hardware and protocols in the context of the Internet, including
311 the use of HIPPI switches as LANs and interoperation with other
312 networks. This memo is intended to become an Internet Standard.
313 [STANDARDS-TRACK]
314
315
316 <span class="h2"><a class="selflink" id="section-1373" href="#section-1373">1373</a> Tignor </span> Oct 92 PORTABLE DUAs
317
318 This document comes in two parts. The first part is for regular people
319 who wish to set up their own DUAs (Directory User Interfaces) to access
320 the Directory. The second part is for ISODE-maintainers wishing to
321 provide portable DUAs to users. This part gives instructions in a
322 similar but longer, step-by-step format. This memo provides information
323 for the Internet community. It does not specify an Internet standard.
324
325
326
327
328
329
330
331
332 <span class="grey">Elliott Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
335
336
337 <span class="h2"><a class="selflink" id="section-1372" href="#section-1372">1372</a> Hedrick </span> Oct 92 Telnet Remote Flow Control Option
338
339 This document specifies an extended version of the Telnet Remote Flow
340 Control Option, <a href="./rfc1080">RFC 1080</a>, with the addition of the RESTART-ANY and
341 RESTART-XON suboptions. [STANDARDS-TRACK]
342
343
344 <span class="h2"><a class="selflink" id="section-1371" href="#section-1371">1371</a> Gross </span> Oct 92 Choosing a "Common IGP" for the IP
345 Internet
346 (The IESG's Recommendation to the IAB)
347
348 This memo presents motivation, rationale and other surrounding
349 background information leading to the IESG's recommendation to the IAB
350 for a single "common IGP" for the IP portions of the Internet. This
351 memo provides information for the Internet community. It does not
352 specify an Internet standard.
353
354
355 <span class="h2"><a class="selflink" id="section-1370" href="#section-1370">1370</a> I.A.B. </span> Oct 92 Applicability Statement for OSPF
356
357 This Applicability Statement places a requirement on vendors claiming
358 conformance to this standard, in order to assure that users will have
359 the option of deploying OSPF when they need a multivendor, interoperable
360 IGP in their environment. [STANDARDS-TRACK]
361
362
363 <span class="h2"><a class="selflink" id="section-1369" href="#section-1369">1369</a> Kastenholz </span> Oct 92 Implementation Notes and Experience for
364 The Internet Ethernet MIB
365
366 This document reflects the currently known status of 11 different
367 implementations of the MIB by 7 different vendors on 7 different
368 Ethernet interface chips. This memo provides information for the
369 Internet community. It does not specify an Internet standard.
370
371
372 <span class="h2"><a class="selflink" id="section-1368" href="#section-1368">1368</a> McMaster </span> Oct 92 Definitions of Managed Objects for IEEE
373 802.3 Repeater Devices
374
375 This memo defines a portion of the Management Information Base (MIB) for
376 use with network management protocols in TCP/IP-based internets. In
377 particular, it defines objects for managing IEEE 802.3 10 Mb/second
378 baseband repeaters, sometimes referred to as "hubs". [STANDARDS-TRACK]
379
380
381
382
383
384
385
386
387
388 <span class="grey">Elliott Informational [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
391
392
393 <span class="h2"><a class="selflink" id="section-1367" href="#section-1367">1367</a> Topolcic </span> Oct 92 Schedule for IP Address Space
394 Management Guidelines
395
396 This memo suggests a schedule for the implementation of the IP network
397 number allocation plan described in <a href="./rfc1366">RFC 1366</a>. This memo provides
398 information for the Internet community. It does not specify an Internet
399 standard.
400
401
402 <span class="h2"><a class="selflink" id="section-1366" href="#section-1366">1366</a> Gerich </span> Oct 92 Guidelines for Management of IP Address
403 Space
404
405 This document has been reviewed by the Federal Engineering Task Force
406 (FEPG) on behalf of the Federal Networking Council (FNC), the co-chairs
407 of the International Engineering Planning Group (IEPG), and the Reseaux
408 IP Europeens (RIPE). There was general consensus by those groups to
409 support the recommendations proposed in this document for management of
410 the IP address space. This memo provides information for the Internet
411 community. It does not specify an Internet standard.
412
413
414 <span class="h2"><a class="selflink" id="section-1365" href="#section-1365">1365</a> Siyan </span> Spt 92 An IP Address Extension Proposal
415
416 This RFC suggests an extension to the IP protocol to solve the shortage
417 of IP address problem, and requests discussion and suggestions for
418 improvements. This memo provides information for the Internet
419 community. It does not specify an Internet standard.
420
421
422 <span class="h2"><a class="selflink" id="section-1364" href="#section-1364">1364</a> Varadhan </span> Spt 92 BGP OSPF Interaction
423
424 This memo defines the various criteria to be used when designing
425 Autonomous System Border Routers (ASBR) that will run BGP with other
426 ASBRs external to the AS and OSPF as its IGP. [STANDARDS-TRACK]
427
428
429 <span class="h2"><a class="selflink" id="section-1363" href="#section-1363">1363</a> Partridge </span> Spt 92 A Proposed Flow Specification
430
431 The flow specification defined in this memo is intended for information
432 and possible experimentation (i.e., experimental use by consenting
433 routers and applications only). This RFC is a product of the Internet
434 Research Task Force (IRTF). This memo provides information for the
435 Internet community. It does not specify an Internet standard.
436
437
438
439
440
441
442
443
444 <span class="grey">Elliott Informational [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
447
448
449 <span class="h2"><a class="selflink" id="section-1362" href="#section-1362">1362</a> Allen </span> Spt 92 Novell IPX Over Various WAN Media
450 (IPXWAN)
451
452 This document describes how Novell IPX operates over various WAN media.
453 Specifically, it describes the common "IPX WAN" protocol Novell uses to
454 exchange necessary router to router information prior to exchanging
455 standard IPX routing information and traffic over WAN datalinks. This
456 memo provides information for the Internet community. It does not
457 specify an Internet standard.
458
459
460 <span class="h2"><a class="selflink" id="section-1361" href="#section-1361">1361</a> Mills </span> Aug 92 Simple Network Time Protocol (SNTP)
461
462 This memorandum describes the Simple Network Time Protocol (SNTP), which
463 is an adaptation of the Network Time Protocol (NTP) used to synchronize
464 computer clocks in the Internet. This memorandum does not obsolete or
465 update any RFC. This memo provides information for the Internet
466 community. It does not specify an Internet standard.
467
468
469 <span class="h2"><a class="selflink" id="section-1360" href="#section-1360">1360</a> I.A.B. </span> Spt 92 IAB OFFICIAL PROTOCOL STANDARDS
470
471 Discussion of the standardization process and the RFC document series is
472 presented first, followed by an explanation of the terms. Sections <a href="#section-6.2">6.2</a>
473 - <a href="#section-6.9">6.9</a> contain the lists of protocols in each stage of standardization.
474 Finally come pointers to references and contacts for further
475 information. [STANDARDS-TRACK]
476
477
478 <span class="h2"><a class="selflink" id="section-1359" href="#section-1359">1359</a> ACM SIGUCCS </span> Aug 92 Connecting to the Internet
479 What Connecting Institutions Should
480 Anticipate
481
482 This FYI RFC outlines the major issues an institution should consider in
483 the decision and implementation of a campus connection to the Internet.
484 This memo provides information for the Internet community. It does not
485 specify an Internet standard.
486
487
488 <span class="h2"><a class="selflink" id="section-1358" href="#section-1358">1358</a> Chapin </span> Aug 92 Charter of the Internet Architecture
489 Board (IAB)
490
491 The Internet Architecture Board (IAB) shall be constituted and shall
492 operate as a technical advisory group of the Internet Society. This
493 memo provides information for the Internet community. It does not
494 specify an Internet standard.
495
496
497
498
499
500 <span class="grey">Elliott Informational [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
503
504
505 <span class="h2"><a class="selflink" id="section-1357" href="#section-1357">1357</a> Cohen </span> Jul 92 A Format for E-mailing Bibliographic
506 Records
507
508 This memo defines a format for E-mailing bibliographic records of
509 technical reports. It is intended to accelerate the dissemination of
510 information about new Computer Science Technical Reports (CS-TR). This
511 memo provides information for the Internet community. It does not
512 specify an Internet standard.
513
514
515 <span class="h2"><a class="selflink" id="section-1356" href="#section-1356">1356</a> Malis </span> Aug 92 Multiprotocol Interconnect
516 on X.25 and ISDN in the Packet Mode
517
518 This document specifies the encapsulation of IP and other network layer
519 protocols over X.25 networks, in accordance and alignment with ISO/IEC
520 and CCITT standards. It is a replacement for <a href="./rfc877">RFC 877</a>, "A Standard for
521 the Transmission of IP Datagrams Over Public Data Networks" [1].
522 [STANDARDS-TRACK]
523
524
525 <span class="h2"><a class="selflink" id="section-1355" href="#section-1355">1355</a> Curran </span> Aug 92 Privacy and Accuracy Issues in Network
526 Information Center Databases
527
528 This document provides a set of guidelines for the administration and
529 operation of public Network Information Center (NIC) databases. This
530 memo provides information for the Internet community. It does not
531 specify an Internet standard.
532
533
534 <span class="h2"><a class="selflink" id="section-1354" href="#section-1354">1354</a> Baker </span> Jul 92 IP Forwarding Table MIB
535
536 This memo defines a portion of the Management Information Base (MIB) for
537 use with network management protocols in TCP/IP-based internets. In
538 particular, it defines objects for managing routes in the IP Internet.
539 [STANDARDS-TRACK]
540
541
542 <span class="h2"><a class="selflink" id="section-1353" href="#section-1353">1353</a> McCloghrie </span> Jul 92 Definitions of Managed Objects
543 for Administration of SNMP Parties
544
545 This memo defines a portion of the Management Information Base (MIB) for
546 use with network management protocols in TCP/IP-based internets. In
547 particular, it describes a representation of the SNMP parties defined in
548 [8] as objects defined according to the Internet Standard SMI [1].
549 [STANDARDS-TRACK]
550
551
552
553
554
555
556 <span class="grey">Elliott Informational [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
559
560
561 <span class="h2"><a class="selflink" id="section-1352" href="#section-1352">1352</a> Galvin </span> Jul 92 SNMP Security Protocols
562
563 The Simple Network Management Protocol (SNMP) specification [1] allows
564 for the protection of network management operations by a variety of
565 security protocols. The SNMP administrative model described in [2]
566 provides a framework for securing SNMP network management. In the
567 context of that framework, this memo defines protocols to support the
568 following three security services: data integrity, data origin
569 authentication and data confidentiality. [STANDARDS-TRACK]
570
571
572 <span class="h2"><a class="selflink" id="section-1351" href="#section-1351">1351</a> Davin </span> Jul 92 SNMP Administrative Model
573
574 This memo presents an elaboration of the SNMP administrative model set
575 forth in [1]. This model provides a unified conceptual basis for
576 administering SNMP protocol entities to support: authenticaiton and
577 integrity, privacy, access control, and cooperation of protocol
578 entities. [STANDARDS-TRACK]
579
580
581 <span class="h2"><a class="selflink" id="section-1350" href="#section-1350">1350</a> Sollins </span> Jul 92 THE TFTP PROTOCOL (REVISION 2)
582
583 TFTP is a very simple protocol used to transfer files. It is from this
584 that its name comes, Trivial File Transfer Protocol or TFTP. Each
585 nonterminal packet is acknowledged separately. This document describes
586 the protocol and its types of packets. The document also explains the
587 reasons behind some of the design decisions. [STANDARDS-TRACK]
588
589
590 <span class="h2"><a class="selflink" id="section-1349" href="#section-1349">1349</a> Almquist </span> Jul 92 Type of Service in the Internet
591 Protocol Suite
592
593 This memo changes and clarifies some aspects of the semantics of the
594 Type of Service octet in the Internet Protocol (IP) header.
595 [STANDARDS-TRACK]
596
597
598 <span class="h2"><a class="selflink" id="section-1348" href="#section-1348">1348</a> Manning </span> Jul 92 DNS NSAP RRs
599
600 This RFC defines the format of two new Resource Records (RRs) for the
601 Domain Name System (DNS), and reserves corresponding DNS type mnemonic
602 and numerical codes. This memo defines an Experimental Protocol for the
603 Internet community.
604
605
606
607
608
609
610
611
612 <span class="grey">Elliott Informational [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
615
616
617 <span class="h2"><a class="selflink" id="section-1347" href="#section-1347">1347</a> Callon </span> Jun 92 TCP and UDP with bigger Addresses
618 (TUBA), A Simple Proposal for Internet
619 Addressing and Routing
620
621 This paper describes a simple proposal which provides a long-term
622 solution to Internet addressing, routing, and scaling. This memo
623 provides information for the Internet community. It does not specify an
624 Internet standard.
625
626
627 <span class="h2"><a class="selflink" id="section-1346" href="#section-1346">1346</a> Jones </span> Jun 92 Resource Allocation, Control, and
628 Accounting for the Use of Network
629 Resources
630
631 The purpose of this RFC is to focus discussion on particular challenges
632 in large service networks in general, and the International IP Internet
633 in particular. No solution discussed in this document is intended as a
634 standard. Rather, it is hoped that a general consensus will emerge as
635 to the appropriate solutions, leading eventually to the adoption of
636 standards. This memo provides information for the Internet community.
637 It does not specify an Internet standard.
638
639
640 <span class="h2"><a class="selflink" id="section-1345" href="#section-1345">1345</a> Simonsen </span> Jun 92 Character Mnemonics &amp; Character Sets
641
642 This memo lists a selection of characters and their presence in some
643 coded character sets. This memo provides information for the Internet
644 community. It does not specify an Internet standard.
645
646
647 <span class="h2"><a class="selflink" id="section-1344" href="#section-1344">1344</a> Borenstein </span> Jun 92 Implicaitons of MIME for Internet Mail
648 Gateways
649
650 While MIME was carefully designed so that it does not require any
651 changes to Internet electronic message transport facilities, there are
652 several ways in which message transport systems may want to take
653 advantage of MIME. These opportunities are the subject of this memo.
654 This memo provides information for the Internet community. It does not
655 specify an Internet standard.
656
657
658 <span class="h2"><a class="selflink" id="section-1343" href="#section-1343">1343</a> Borenstein </span> Jun 92 A User Agent Configuration Mechanism
659 For Multimedia Mial Format Information
660
661 This memo suggests a file format to be used to inform multiple mail
662 reading user agent programs about the locally-installed facilities for
663 handling mail in various formats. This memo provides information for
664 the Internet community. It does not specify an Internet standard.
665
666
667
668 <span class="grey">Elliott Informational [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
671
672
673 <span class="h2"><a class="selflink" id="section-1342" href="#section-1342">1342</a> Moore </span> Jun 92 Representation of Non-ASCII Text in
674 Internet Message Headers
675
676 This memo describes an extension to the message format defined in [1]
677 (known to the IETF Mail Extensions Working Group as "<a href="./rfc1341">RFC 1341</a>"), to
678 allow the representation of character sets other than ASCII in <a href="./rfc822">RFC 822</a>
679 message headers. [STANDARDS-TRACK]
680
681
682 <span class="h2"><a class="selflink" id="section-1341" href="#section-1341">1341</a> Borenstein </span> Jun 92 MIME: Mechanisms for Specifying and
683 Describing the Format of Internet
684 Message Bodies
685
686 This document redefines the format of message bodies to allow multi-part
687 textual and non-textual message bodies to be represented and exchanged
688 without loss of information. [STANDARDS-TRACK]
689
690
691 <span class="h2"><a class="selflink" id="section-1340" href="#section-1340">1340</a> Reynolds </span> Jul 92 ASSIGNED NUMBERS
692
693 This Network Working Group Request for Comments documents the currently
694 assigned values from several series of numbers used in network protocol
695 implementations. This memo is a status report on the parameters (i.e.,
696 numbers and keywords) used in protocols in the Internet community.
697
698
699 <span class="h2"><a class="selflink" id="section-1339" href="#section-1339">1339</a> Dorner </span> Jun 92 Remote Mail Checking Protocol
700
701 This RFC defines a protocol to provide a mail checking service to be
702 used between a client and server pair. Typically, a small program on a
703 client workstation would use the protocol to query a server in order to
704 find out whether new mail has arrived for a specified user. This memo
705 defines an Experimental Protocol for the Internet community.
706
707
708 <span class="h2"><a class="selflink" id="section-1338" href="#section-1338">1338</a> Fuller </span> Jun 92 Supernetting: an Address Assignment
709 and Aggregation Strategy
710
711 This memo discusses strategies for address assignment of the existing IP
712 address space with a view to conserve the address space and stem the
713 explosive growth of routing tables in default-route-free routers run by
714 transit routing domain providers. This memo provides information for
715 the Internet community. It does not specify an Internet standard.
716
717
718
719
720
721
722
723
724 <span class="grey">Elliott Informational [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
727
728
729 <span class="h2"><a class="selflink" id="section-1337" href="#section-1337">1337</a> Braden </span> May 92 TIME-WAIT Assassination Hazards in TCP
730
731 This note describes some theoretically-possible failure modes for TCP
732 connections and discusses possible remedies. In particular, one very
733 simple fix is identified. This memo provides information for the
734 Internet community. It does not specify an Internet standard.
735
736
737 <span class="h2"><a class="selflink" id="section-1336" href="#section-1336">1336</a> Malkin </span> May 92 Who's Who in the Internet
738 Biographies of IAB, IESG and
739 IRSG Members
740
741 This FYI RFC contains biographical information about members of the
742 Internet Activities Board (IAB), the Internet Engineering Steering Group
743 (IESG) of the Internet Engineering Task Force (IETF), and the the
744 Internet Research Steering Group (IRSG) of the Internet Research Task
745 Force (IRTF). This memo provides information for the Internet
746 community. It does not specify any standard.
747
748
749 <span class="h2"><a class="selflink" id="section-1335" href="#section-1335">1335</a> Wang </span> May 92 A Two-Tier Address Structure for the
750 Internet: A Solution to the Problem
751 of Address Space Exhaustion
752
753 This RFC presents a solution to problem of address space exhaustion in
754 the Internet. It proposes a two-tier address structure for the
755 Internet. This is an "idea" paper and discussion is strongly
756 encouraged. This memo provides information for the Internet community.
757 It does not specify an Internet standard.
758
759
760 <span class="h2"><a class="selflink" id="section-1334" href="#section-1334">1334</a> Lloyd </span> Oct 92 PPP Authentication Protocols
761
762 This document defines two protocols for Authentication: the Password
763 Authentication Protocol and the Challenge-Handshake Authentication
764 Protocol. [STANDARDS-TRACK]
765
766
767 <span class="h2"><a class="selflink" id="section-1333" href="#section-1333">1333</a> Simpson </span> May 92 PPP Link Quality Monitoring
768
769 The Point-to-Point Protocol (PPP) [1] provides a standard method of
770 encapsulating Network Layer protocol information over point-to-point
771 links. PPP also defines an extensible Link Control Protocol, which
772 allows negotiation of a Quality Protocol for continuous monitoring of
773 the viability of the link. [STANDARDS-TRACK]
774
775
776
777
778
779
780 <span class="grey">Elliott Informational [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
783
784
785 <span class="h2"><a class="selflink" id="section-1332" href="#section-1332">1332</a> McGregor </span> May 92 The PPP Internet Protocol Control
786 Protocol (IPCP)
787
788 The Point-to-Point Protocol (PPP) [1] provides a standard method of
789 encapsulating Network Layer protocol information over point-to-point
790 links. PPP also defines an extensible Link Control Protocol, and
791 proposes a family of Network Control Protocols (NCPs) for establishing
792 and configuring different network-layer protocols. [STANDARDS-TRACK]
793
794
795 <span class="h2"><a class="selflink" id="section-1331" href="#section-1331">1331</a> Simpson </span> May 92 The Point-to-Point Protocol (PPP&gt;
796 for the Transmission of Multi-protocol
797 Datagrams over Point-to-Point Links
798
799 This document defines the PPP encapsulation scheme, together with the
800 PPP Link Control Protocol (LCP), an extensible option negotiation
801 protocol which is able to negotiate a rich assortment of configuration
802 parameters and provides additional management functions. [STANDARDS-
803 TRACK]
804
805
806 <span class="h2"><a class="selflink" id="section-1330" href="#section-1330">1330</a> E.S.C.C. </span> May 92 Recommendations for the Phase I
807 Deployment of OSI Directory Services
808 (X.500) and OSI Message Handling
809 Services &lt;X.400) within the ESnet
810 Community
811
812 This RFC is a near verbatim copy of the whitepaper produced by the ESnet
813 Site Coordinating Committee's X.500/X.400 Task Force. This memo
814 provides information for the Internet community. It does not specify an
815 Internet standard.
816
817
818 <span class="h2"><a class="selflink" id="section-1329" href="#section-1329">1329</a> Kuehn </span> May 92 Thoughts on Address Resolution for
819 Dual MAC FDDI Networks
820
821 In this document an idea is submitted how IP and ARP can be used on
822 inhomogeneous FDDI networks (FDDI networks with single MAC and dual MAC
823 stations) by introducing a new protocol layer in the protocol suite of
824 the dual MAC stations. This memo provides information for the Internet
825 community. It does not specify an Internet standard.
826
827
828
829
830
831
832
833
834
835
836 <span class="grey">Elliott Informational [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
839
840
841 <span class="h2"><a class="selflink" id="section-1328" href="#section-1328">1328</a> Kille </span> May 92 X.400 1988 to 1984 downgrading
842
843 This document considers issues of downgrading from X.400(1988) to
844 X.400(1984) [MHS88a, MHS84]. Annexe B of X.419 specifies some
845 downgrading rules [MHS88b], but these are not sufficient for provision
846 of service in an environment containing both 1984 and 1988 components.
847 This document defines a number of extensions to this annexe.
848 [STANDARDS-TRACK]
849
850
851 <span class="h2"><a class="selflink" id="section-1327" href="#section-1327">1327</a> Kille </span> May 92 Mapping between X.400(1988) / ISO
852 10021 and <a href="./rfc822">RFC 822</a>
853
854 This document specifies a mapping between two protocols. This
855 specification should be used when this mapping is performed on the DARPA
856 Internet or in the UK Academic Community. This specification may be
857 modified in the light of implementation experience, but no substantial
858 changes are expected. [STANDARDS-TRACK]
859
860
861 <span class="h2"><a class="selflink" id="section-1326" href="#section-1326">1326</a> Tsuchiya </span> May 92 Mutual Encapsulation Considered
862 Dangerous
863
864 This memo describes a packet explosion problem that can occur with
865 mutual encapsulation of protocols (A encapsulates B and B encapsulates
866 A). This memo provides information for the Internet community. It does
867 not specify an Internet standard.
868
869
870 <span class="h2"><a class="selflink" id="section-1325" href="#section-1325">1325</a> Malkin </span> May 92 FYI on Questions and Answers
871 Answers to Commonly asked "New
872 Internet User" Questions
873
874 This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A),
875 produced by the User Services Working Group of the Internet Engineering
876 Task Force (IETF). The goal is to document the most commonly asked
877 questions and answers in the Internet. This memo provides information
878 for the Internet community. It does not specify an Internet standard.
879
880
881
882
883
884
885
886
887
888
889
890
891
892 <span class="grey">Elliott Informational [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
895
896
897 <span class="h2"><a class="selflink" id="section-1324" href="#section-1324">1324</a> Reed </span> May 92 A Discussion on Computer Network
898 Conferencing
899
900 This memo is intended to make more people aware of the present
901 developments in the Computer Conferencing field as well as put forward
902 ideas on what should be done to formalize this work so that there is a
903 common standard for programmers and others who are involved in this
904 field to work with. This memo provides information for the Internet
905 community. It does not specify an Internet standard.
906
907
908 <span class="h2"><a class="selflink" id="section-1323" href="#section-1323">1323</a> Jacobson </span> May 92 TCP Extensions for High Performance
909
910 This memo presents a set of TCP extensions to improve performance over
911 large bandwidth*delay product paths and to provide reliable operation
912 over very high-speed paths. It defines new TCP options for scaled
913 windows and timestamps, which are designed to provide compatible
914 interworking with TCP's that do not implement the extensions.
915 [STANDARDS-TRACK]
916
917
918 <span class="h2"><a class="selflink" id="section-1322" href="#section-1322">1322</a> Estrin </span> May 92 A Unified Approach to Inter-Domain
919 Routing
920
921 This memo is an informational RFC which outlines one potential approach
922 for inter-domain routing in future global internets. This memo provides
923 information for the Internet community. It does not specify an Internet
924 standard.
925
926
927 <span class="h2"><a class="selflink" id="section-1321" href="#section-1321">1321</a> Rivest </span> Apr 92 The MD5 Message-Digest Algorithm
928
929 This document describes the MD5 message-digest algorithm. The algorithm
930 takes as input a message of arbitrary length and produces as output a
931 128-bit "fingerprint" or "message digest" of the input. This memo
932 provides information for the Internet community. It does not specify an
933 Internet standard.
934
935
936 <span class="h2"><a class="selflink" id="section-1320" href="#section-1320">1320</a> Rivest </span> Apr 92 The MD4 Message-Digest Algorithm
937
938 This document describes the MD4 message-digest algorithm [1]. The
939 algorithm takes as input a message of arbitrary length and produces as
940 output a 128-bit "fingerprint" or "message digest" of the input. This
941 memo provides information for the Internet community. It does not
942 specify an Internet standard.
943
944
945
946
947
948 <span class="grey">Elliott Informational [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
951
952
953 <span class="h2"><a class="selflink" id="section-1319" href="#section-1319">1319</a> Kaliski </span> Apr 92 The MD2 Message-Digest Algorithm
954
955 This document describes the MD2 message-digest algorithm. The algorithm
956 takes as input a message of arbitrary length and produces as output a
957 128-bit "fingerprint" or "message digest" of the input. This memo
958 provides information for the Internet community. It does not specify an
959 Internet standard.
960
961
962 <span class="h2"><a class="selflink" id="section-1318" href="#section-1318">1318</a> Stewart </span> Apr 92 Definitions of Managed Objects
963 for Parallel-printer-like Hardware
964 Devices
965
966 This memo defines a portion of the Management Information Base (MIB) for
967 use with network management protocols in TCP/IP based internets. In
968 particular, it defines objects for the management of parallel-printer-
969 like devices. [STANDARDS-TRACK]
970
971
972 <span class="h2"><a class="selflink" id="section-1317" href="#section-1317">1317</a> Stewart </span> Apr 92 Definitions of Managed Objects for
973 RS-232-like Hardware Devices
974
975 This memo defines a portion of the Management Information Base (MIB) for
976 use with network management protocols in TCP/IP based internets. In
977 particular, it defines objects for the management of RS-232-like
978 devices. [STANDARDS-TRACK]
979
980
981 <span class="h2"><a class="selflink" id="section-1316" href="#section-1316">1316</a> Stewart </span> Apr 92 Definitions of Managed Objects
982 for Character Stream Devices
983
984 This memo defines a portion of the Management Information Base (MIB) for
985 use with network management protocols in TCP/IP based internets. In
986 particular it defines objects for the management of character stream
987 devices. [STANDARDS-TRACK]
988
989
990 <span class="h2"><a class="selflink" id="section-1315" href="#section-1315">1315</a> Brown </span> Apr 92 Management Information Base for Frame
991 Relay DTEs
992
993 This memo defines a portion of the Management Information Base (MIB) for
994 use with network management protocols in TCP/IP-based internets. In
995 particular, it defines objects for managing Frame Relay. [STANDARDS-
996 TRACK]
997
998
999
1000
1001
1002
1003
1004 <span class="grey">Elliott Informational [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
1007
1008
1009 <span class="h2"><a class="selflink" id="section-1314" href="#section-1314">1314</a> Katz </span> Apr 92 A File Format for the Exchange of
1010 Images in the Internet
1011
1012 This document defines a standard file format for the exchange of fax-
1013 like black and white images within the Internet. [STANDARDS-TRACK]
1014
1015
1016 <span class="h2"><a class="selflink" id="section-1313" href="#section-1313">1313</a> Partridge </span> Apr 92 Today's Programming for KRFC AM 1313
1017 Internet Talk Radio
1018
1019 Hi and welcome to KRFC Internet Talk Radio, your place on the AM dial
1020 for lively talk and just-breaking news on internetworking. This memo
1021 provides information for the Internet community. It does not specify an
1022 Internet standard.
1023
1024
1025 <span class="h2"><a class="selflink" id="section-1312" href="#section-1312">1312</a> Nelson </span> Apr 92 Message Send Protocol 2
1026
1027 The Message Send Protocol is used to send a short message to a given
1028 user on a given terminal on a given host. This memo defines an
1029 Experimental Protocol for the Internet community.
1030
1031
1032 <span class="h2"><a class="selflink" id="section-1311" href="#section-1311">1311</a> Postel </span> Mar 92 Introduction to the STD Notes
1033
1034 The STDs are a subseries of notes within the RFC series that are the
1035 Internet standards. The intent is to identify clearly for the Internet
1036 community those RFCs which document Internet standards. [STANDARDS-
1037 TRACK]
1038
1039
1040 <span class="h2"><a class="selflink" id="section-1310" href="#section-1310">1310</a> I.A.B. </span> Mar 92 The Internet Standards Process
1041
1042 This memo documents the process currently used for the standardization
1043 of Internet protocols and procedures. [STANDARDS-TRACK]
1044
1045
1046 <span class="h2"><a class="selflink" id="section-1309" href="#section-1309">1309</a> Weider </span> Mar 92 Technical Overview of Directory
1047 Services Using the X.500 Protocol
1048
1049 This document is an overview of the X.500 standard for people not
1050 familiar with the technology. It compares and contrasts Directory
1051 Services based on X.500 with several of the other Directory services
1052 currently in use in the Internet. This paper also describes the status
1053 of the standard and provides references for further information on X.500
1054 implementations and technical information. This memo provides
1055 information for the Internet community. It does not specify an Internet
1056 standard.
1057
1058
1059
1060 <span class="grey">Elliott Informational [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
1063
1064
1065 <span class="h2"><a class="selflink" id="section-1308" href="#section-1308">1308</a> Weider </span> Mar 92 Executive Introduction to Directory
1066 Services Using the X.500 Protocol
1067
1068 This document is an Executive Introduction to Directory Services using
1069 the X.500 protocol. It briefly discusses the deficiencies in currently
1070 deployed Internet Directory Services, and then illustrates the solutions
1071 provided by X.500. This memo provides information for the Internet
1072 community. It does not specify an Internet standard.
1073
1074
1075 <span class="h2"><a class="selflink" id="section-1307" href="#section-1307">1307</a> Young </span> Mar 92 Dynamically Switched Link Control
1076 Protocol
1077
1078 This memo describes an experimental protocol developed by a project team
1079 at Cray Research, Inc., in implementing support for circuit-switched T3
1080 services. The protocol is used for the control of network connections
1081 external to a host, but known to the host. This memo defines an
1082 Experimental Protocol for the Internet community.
1083
1084
1085 <span class="h2"><a class="selflink" id="section-1306" href="#section-1306">1306</a> Nicholson </span> Mar 92 Experiences Supporting By-Request
1086 Circuit-Switched T3 Networks
1087
1088 This memo describes the experiences of a project team at Cray Research,
1089 Inc., in implementing support for circuit-switched T3 services. While
1090 the issues discussed may not be directly relevant to the research
1091 problems of the Internet, they may be interesting to a number of
1092 researchers and implementers. This RFC provides information for the
1093 Internet community. It does not specify an Internet standard.
1094
1095
1096 <span class="h2"><a class="selflink" id="section-1305" href="#section-1305">1305</a> Mills </span> Mar 92 Network Time Protocol (Version 3):
1097 Specification, Implementation and
1098 Analysis
1099
1100 This document describes the Network Time Protocol (NTP), specifies its
1101 formal structure and summarizes information useful for its
1102 implementation. [STANDARDS-TRACK]
1103
1104
1105 <span class="h2"><a class="selflink" id="section-1304" href="#section-1304">1304</a> Cox </span> Feb 92 Definitions of Managed Objects for the
1106 SIP Interface Type
1107
1108 This memo defines a portion of the Management Information Base (MIB) for
1109 use with network management protocols in TCP/IP-based internets. In
1110 particular, it defines objects for managing SIP (SMDS Interface
1111 Protocol) objects. [STANDARDS-TRACK]
1112
1113
1114
1115
1116 <span class="grey">Elliott Informational [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
1119
1120
1121 <span class="h2"><a class="selflink" id="section-1303" href="#section-1303">1303</a> McCloghrie </span> Feb 92 A Convention for Describing SNMP-based
1122 Agents
1123
1124 This memo suggests a straight-forward approach towards describing SNMP-
1125 based agents. This memo provides information for the Internet
1126 community. It does not specify an Internet standard.
1127
1128
1129 <span class="h2"><a class="selflink" id="section-1302" href="#section-1302">1302</a> Sitzler </span> Feb 92 Building a Network Information
1130 Services Infrastructure
1131
1132 This FYI RFC document is intended for existing Internet Network
1133 Information Center (NIC) personnel, people interested in establishing a
1134 new NIC, Internet Network Operations Centers (NOCs), and funding
1135 agencies interested in contributing to user support facilities. This
1136 memo provides information for the Internet community. It does not
1137 specify an Internet standard.
1138
1139
1140 <span class="h2"><a class="selflink" id="section-1301" href="#section-1301">1301</a> Armstrong </span> Feb 92 Multicast Transport Protocol
1141
1142 This memo describes a protocol for reliable transport that utilizes the
1143 multicast capability of applicable lower layer networking architectures.
1144 The transport definition permits an arbitrary number of transport
1145 providers to perform realtime collaborations without requiring
1146 networking clients (aka, applications) to possess detailed knowledge of
1147 the population or geographical dispersion of the participating members.
1148 It is not network architectural specific, but does implicitly require
1149 some form of multicasting (or broadcasting) at the data link level, as
1150 well as some means of communicating that capability up through the
1151 layers to the transport. This memo provides information for the
1152 Internet community. It does not specify an Internet standard.
1153
1154
1155 <span class="h2"><a class="selflink" id="section-1300" href="#section-1300">1300</a> Greenfield </span> Feb 92 Remembrances of Things Past
1156
1157 Poem. This memo provides information for the Internet community. It
1158 does not specify an Internet standard.
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172 <span class="grey">Elliott Informational [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc1399">RFC 1399</a> Summary of 1300-1399 January 1997</span>
1175
1176
1177 Security Considerations
1178
1179 Security issues are not discussed in this memo.
1180
1181 Author's Address
1182
1183 Josh Elliott
1184 University of Southern California
1185 Information Sciences Institute
1186 4676 Admiralty Way
1187 Marina del Rey, CA 90292
1188
1189 Phone: (310) 822-1511
1190
1191 EMail: [email protected]
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228 Elliott Informational [Page 22]
1229 </pre>