Debian Codegraph @

rfc1099.html

raw
1 <pre>Network Working Group J. Reynolds
2 Request for Comments: 1099 ISI
3 December 1991
4
5
6 <span class="h1">Request for Comments Summary</span>
7
8 RFC Numbers 1000-1099
9
10 Status of This Memo
11
12 This memo is a slightly annotated list of the 100 RFCs from <a href="./rfc1000">RFC 1000</a>
13 through RFCs 1099. 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. Distribution of this memo is unlimited.
16
17 RFC Author Date Title
18 --- ------ ---- -----
19
20 <span class="h2"><a class="selflink" id="section-1099" href="#section-1099">1099</a> Reynolds </span> Dec 91 Requests For Comments Summary
21
22 This memo.
23
24
25 <span class="h2"><a class="selflink" id="section-1098" href="#section-1098">1098</a> Case </span> Apr 89 A Simple Network Management
26 Protocol (SNMP)
27
28 This RFC is a re-release of <a href="./rfc1067">RFC 1067</a>, with a changed "Status of this
29 Memo" section. This memo defines a simple protocol by which management
30 information for a network element may be inspected or altered by
31 logically remote users. In particular, together with its companion
32 memos which describe the structure of management information along with
33 the initial management information base, these documents provide a
34 simple, workable architecture and system for managing TCP/IP-based
35 internets and in particular the Internet.
36
37
38 <span class="h2"><a class="selflink" id="section-1097" href="#section-1097">1097</a> Miller </span> Apr 89 Telnet Subliminal-Message Option
39
40 This RFC specifies a standard for the Internet community. Hosts on the
41 Internet that display subliminal messages within the Telnet protocol are
42 expected to adopt and implement this standard.
43
44
45 <span class="h2"><a class="selflink" id="section-1096" href="#section-1096">1096</a> Marcy </span> Mar 89 Telnet X Display Location Option
46
47 This RFC specifies a standard for the Internet community. Hosts on the
48 Internet that transmit the X display location within the Telnet protocol
49
50
51
52 <span class="grey">Reynolds [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
55
56
57 are expected to adopt and implement this standard.
58
59
60 <span class="h2"><a class="selflink" id="section-1095" href="#section-1095">1095</a> Warrier </span> Apr 89 The Common Management Information
61 Services and Protocol over TCP/IP
62 (CMOT)
63
64 This memo defines a network management architecture that uses the
65 International Organization for Standardization's (ISO) Common Management
66 Information Services/Common Management Information Protocol (CMIS/CMIP)
67 in a TCP/IP environment. This architecture provides a means by which
68 control and monitoring information can be exchanged between a manager
69 and a remote network element. In particular, this memo defines the
70 means for implementing the Draft International Standard (DIS) version of
71 CMIS/CMIP on top of Internet transport protocols for the purpose of
72 carrying management information defined in the Internet-standard
73 management information base. DIS CMIS/CMIP is suitable for deployment
74 in TCP/IP networks while CMIS/CMIP moves toward becoming an
75 International Standard. Together with the relevant ISO standards and
76 the companion RFCs that describe the initial structure of management
77 information and management information base, these documents provide the
78 basis for a comprehensive architecture and system for managing TCP/IP-
79 based internets, and in particular the Internet.
80
81
82 <span class="h2"><a class="selflink" id="section-1094" href="#section-1094">1094</a> Sun </span> Mar 89 NFS: Network File System
83 Protocol Specification
84
85 This RFC describes a protocol that Sun Microsystems, Inc., and others
86 are using. A new version of the protocol is under development, but
87 others may benefit from the descriptions of the current protocol, and
88 discussion of some of the design issues.
89
90
91 <span class="h2"><a class="selflink" id="section-1093" href="#section-1093">1093</a> Braun </span> Feb 89 The NSFNET Routing Architecture
92
93 This document describes the routing architecture for the NSFNET centered
94 around the new NSFNET Backbone, with specific emphasis on the interface
95 between the backbone and its attached networks.
96
97
98 <span class="h2"><a class="selflink" id="section-1092" href="#section-1092">1092</a> Rekhter </span> Feb 89 EGP and Policy Based Routing
99 in the New NSFNET Backbone
100
101 This memo discusses implementation decisions for routing issues in the
102 NSFNET, especially in the NSFNET Backbone. Of special concern is the
103 restriction of routing information to advertize the best route as
104 established by a policy decision.
105
106
107
108 <span class="grey">Reynolds [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1091" href="#section-1091">1091</a> VanBokkelen </span>Feb 89 Telnet Terminal-Type Option
114
115 This RFC specifies a standard for the Internet community. Hosts on the
116 Internet that exchange terminal type information within the Telnet
117 protocol are expected to adopt and implement this standard.
118
119 This standard supersedes <a href="./rfc930">RFC 930</a>. A change is made to permit cycling
120 through a list of possible terminal types and selecting the most
121 appropriate
122
123
124 <span class="h2"><a class="selflink" id="section-1090" href="#section-1090">1090</a> Ullmann </span> Feb 89 SMTP on X.25
125
126 This memo proposes a standard for SMTP on the virtual circuit facility
127 provided by the X.25 standard of the CCITT.
128
129
130 <span class="h2"><a class="selflink" id="section-1089" href="#section-1089">1089</a> Schoffstall </span>Feb 89 SNMP over Ethernet
131
132 This memo describes an experimental method by which the Simple Network
133 Management Protocol (SNMP) can be used over Ethernet MAC layer framing
134 instead of the Internet UDP/IP protocol stack. This specification is
135 useful for LAN based network elements that support no higher layer
136 protocols beyond the MAC sub-layer.
137
138
139 <span class="h2"><a class="selflink" id="section-1088" href="#section-1088">1088</a> McLaughlin </span> Feb 89 A Standard for the Transmission of IP
140 Datagrams over NetBIOS Networks
141
142 This document specifies a standard method of encapsulating the Internet
143 Protocol (IP) datagrams on NetBIOS networks.
144
145
146 <span class="h2"><a class="selflink" id="section-1087" href="#section-1087">1087</a> IAB </span> Jan 89 Ethics and the Internet
147
148 This memo is a statement of policy by the Internet Activities Board
149 (IAB) concerning the proper use of the resources of the Internet.
150
151
152 <span class="h2"><a class="selflink" id="section-1086" href="#section-1086">1086</a> Onions </span> Dec 88 ISO-TP0 bridge between TCP and X.25
153
154 This memo proposes a standard for the Internet community. Hosts on the
155 Internet that choose to implement ISO TP0 transport connectivity between
156 TCP and X.25 based hosts are expected to experiment with this proposal.
157 TCP port 146 is reserved for this proposal.
158
159
160
161
162
163
164 <span class="grey">Reynolds [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
167
168
169 <span class="h2"><a class="selflink" id="section-1085" href="#section-1085">1085</a> Rose </span> Dec 88 ISO Presentation Services
170 on top of TCP/IP-based internets
171
172 <a href="./rfc1006">RFC 1006</a> describes a mechanism for providing the ISO transport service
173 on top of TCP/IP. Once this method is applied, one may implement "real"
174 ISO applications on top of TCP/IP-based internets, by simply
175 implementing OSI session, presentation, and application services on top
176 of the transport service access point which is provided on top of the
177 TCP. Although straight-forward, there are some environments in which
178 the richness provided by the OSI application layer is desired, but it is
179 nonetheless impractical to implement the underlying OSI infrastructure
180 (i.e., the presentation, session, and transport services on top of the
181 TCP).
182
183 This memo describes an approach for providing "stream-lined" support of
184 OSI application services on top of TCP/IP-based internets for such
185 constrained environments. This memo proposes a standard for the
186 Internet community.
187
188
189 <span class="h2"><a class="selflink" id="section-1084" href="#section-1084">1084</a> Reynolds </span> Dec 88 BOOTP Vendor Information Extensions
190
191 This RFC is a slight revision and extension of <a href="./rfc1048">RFC-1048</a> by Philip
192 Prindeville. This memo will be updated as additional tags are are
193 defined. This edition introduces Tag 13 for Boot File Size. Comments
194 and suggestions for improvements are sought.
195
196
197 <span class="h2"><a class="selflink" id="section-1083" href="#section-1083">1083</a> IAB </span> Dec 88 IAB Official Protocol Standards
198
199 This memo describes the state of standardization of protocols used in
200 the Internet as determined by the Internet Activities Board (IAB). An
201 overview of the standards procedures is presented first, followed by
202 discussions of the standardization process and the RFC document series,
203 then the explanation of the terms is presented, the lists of protocols
204 in each stage of standardization follows, and finally pointers to
205 references and contacts for further information.
206
207 This memo is issued quarterly, please be sure the copy you are reading
208 is dated within the last three months.
209
210
211 <span class="h2"><a class="selflink" id="section-1082" href="#section-1082">1082</a> Rose </span> Nov 88 Post Office Protocol - Version 3
212 Extended Service Offerings
213
214 This memo suggests a simple method for workstations to dynamically
215 access mail from a discussion group server, as an extension to an
216 earlier memo which dealt with dynamically accessing mail from a mailbox
217
218
219
220 <span class="grey">Reynolds [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
223
224
225 server using the Post Office Protocol - Version 3 (POP3). This RFC
226 specifies a proposed protocol for the Internet community, and requests
227 discussion and suggestions for improvements. All of the extensions
228 described in this memo to the POP3 are OPTIONAL.
229
230
231 <span class="h2"><a class="selflink" id="section-1081" href="#section-1081">1081</a> Rose </span> Nov 88 Post Office Protocol - Version 3
232
233 This memo suggests a simple method for workstations to dynamically
234 access mail from a mailbox server. This RFC specifies a proposed
235 protocol for the Internet community, and requests discussion and
236 suggestions for improvements.
237
238
239 <span class="h2"><a class="selflink" id="section-1080" href="#section-1080">1080</a> Hedrick </span> Dec 88 Telnet Remote Flow Control Option
240
241 This RFC specifies a standard for the Internet community. Hosts on the
242 Internet that do remote flow control within the Telnet protocol are
243 expected to adopt and implement this standard.
244
245
246 <span class="h2"><a class="selflink" id="section-1079" href="#section-1079">1079</a> Hedrick </span> Dec 88 Telnet Terminal Speed Option
247
248 This RFC specifies a standard for the Internet community. Hosts on the
249 Internet that exchange terminal speed information within the Telnet
250 protocol are expected to adopt and implement this standard.
251
252
253 <span class="h2"><a class="selflink" id="section-1078" href="#section-1078">1078</a> Lottor </span> Nov 88 TCP Port Service Multiplexer (TCPMUX)
254
255 This RFC proposes an Internet standard which can be used by future TCP
256 services instead of using 'well-known ports'.
257
258
259 <span class="h2"><a class="selflink" id="section-1077" href="#section-1077">1077</a> Leiner </span> Nov 88 Critical Issues in High Bandwidth
260 Networking
261
262 This memo presents the results of a working group on High Bandwidth
263 Networking. This RFC is for your information and you are encouraged to
264 comment on the issues presented.
265
266
267 <span class="h2"><a class="selflink" id="section-1076" href="#section-1076">1076</a> Trewitt </span> Nov 88 HEMS Monitoring and Control Language
268
269 This RFC specifies a query language for monitoring and control of
270 network entities. This RFC supercedes <a href="./rfc1023">RFC 1023</a>, extending the query
271 language and providing more discussion of the underlying issues.
272
273
274
275
276 <span class="grey">Reynolds [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
279
280
281 This language is a component of the High-Level Entity Monitoring System
282 (HEMS) described in <a href="./rfc1021">RFC 1021</a> and <a href="./rfc1022">RFC 1022</a>. Readers may wish to consult
283 these RFCs when reading this memo. <a href="./rfc1024">RFC 1024</a> contains detailed
284 assignments of numbers and structures used in this system. Portions of
285 <a href="./rfc1024">RFC 1024</a> that define query language structures are superceded by
286 definitions in this memo. This memo assumes a knowledge of the ISO data
287 encoding standard, ASN.1.
288
289
290 <span class="h2"><a class="selflink" id="section-1075" href="#section-1075">1075</a> Waitzman </span> Nov 88 Distance Vector Multicast Routing
291 Protocol
292
293 This RFC describes a distance-vector-style routing protocol for routing
294 multicast datagrams through an internet. It is derived from the Routing
295 Information Protocol (RIP), and implements multicasting as described in
296 <a href="./rfc1054">RFC-1054</a>. This is an experimental protocol, and its implementation is
297 not recommended at this time.
298
299
300 <span class="h2"><a class="selflink" id="section-1074" href="#section-1074">1074</a> Rekhter </span> Oct 88 The NSFNET Backbone SPF based Interior
301 Gateway Protocol
302
303 This RFC is an implementation description of the standard ANSI IS-IS and
304 ISO ES-IS routing protocols within the NSFNET backbone network.
305
306
307 <span class="h2"><a class="selflink" id="section-1073" href="#section-1073">1073</a> Waitzman </span> Oct 88 Telnet Window Size Option
308
309 This RFC describes a proposed Telnet option to allow a client to convey
310 window size to a Telnet server.
311
312
313 <span class="h2"><a class="selflink" id="section-1072" href="#section-1072">1072</a> Jacobson </span> Oct 88 TCP Extensions for Long-Delay Paths
314
315 This RFC proposes a set of extensions to the TCP protocol to provide
316 efficient operation over a path with a high bandwidth*delay product.
317 These extensions are not proposed as an Internet standard at this time.
318 Instead, they are intended as a basis for further experimentation and
319 research on transport protocol performance.
320
321
322 <span class="h2"><a class="selflink" id="section-1071" href="#section-1071">1071</a> Braden </span> Aug 88 Computing the Internet Checksum
323
324 This RFC summarizes techniques and algorithms for efficiently computing
325 the Internet checksum. It is not a standard, but a set of useful
326 implementation techniques.
327
328
329
330
331
332 <span class="grey">Reynolds [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
335
336
337 <span class="h2"><a class="selflink" id="section-1070" href="#section-1070">1070</a> Hagens </span> Feb 89 Use of the Internet as a Subnetwork
338 for Experimentation with the OSI
339 Network Layer
340
341 This RFC proposes a scenario for experimentation with the International
342 Organization for Standardization (ISO) Open Systems Interconnection
343 (OSI) network layer protocols over the Internet and requests discussion
344 and suggestions for improvements to this scenario. This RFC also
345 proposes the creation of an experimental OSI internet. To participate
346 in the experimental OSI internet, a system must abide by the agreements
347 set forth in this RFC.
348
349
350 <span class="h2"><a class="selflink" id="section-1069" href="#section-1069">1069</a> Callon </span> Feb 89 Guidelines for the use of Internet-IP
351 addresses in the ISO Connectionless-
352 Mode Network Protocol
353
354 This RFC suggests an addressing scheme for use with the ISO
355 Connectionless Network Protocol (CLNP) in the Internet. This is a
356 solution to one of the problems inherent in the use of "ISO-grams" in
357 the Internet. This memo is a revision of <a href="./rfc986">RFC 986</a>. This RFC suggests a
358 proposed protocol for the Internet community, and requests discussion
359 and suggestions for improvements.
360
361
362 <span class="h2"><a class="selflink" id="section-1068" href="#section-1068">1068</a> DeSchon </span> Aug 88 Background File Transfer Program
363 (BFTP)
364
365 This RFC describes an Internet background file transfer service that is
366 built upon the third-party transfer model of FTP. No new protocols are
367 involved. The purpose of this memo is to stimulate discussions on new
368 Internet service modes.
369
370
371 <span class="h2"><a class="selflink" id="section-1067" href="#section-1067">1067</a> Case </span> Aug 88 A Simple Network Management Protocol
372
373 This RFC defines a simple protocol by which management information for a
374 network element may be inspected or altered by logically remote users.
375 In particular, together with its companion memos which describe the
376 structure of management information along with the initial management
377 information base, these documents provide a simple, workable
378 architecture and system for managing TCP/IP-based internets and in
379 particular, the Internet.
380
381 This memo specifies a draft standard for the Internet community. TCP/IP
382 implementations in the Internet which are network manageable are
383 expected to adopt and implement this specification.
384
385
386
387
388 <span class="grey">Reynolds [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
391
392
393 <span class="h2"><a class="selflink" id="section-1066" href="#section-1066">1066</a> McCloghrie </span> Aug 88 Management Information Base for Network
394 Management of TCP/IP-based internets
395
396 This RFC provides the initial version of the Management Information Base
397 (MIB) for use with network management protocols in TCP/IP-based
398 internets in the short-term. In particular, together with its companion
399 memos which describe the structure of management information along with
400 the initial network management protocol, these documents provide a
401 simple, workable architecture and system for managing TCP/IP-based
402 internets, and in particular, the Internet.
403
404 This memo specifies a draft standard for the Internet community. TCP/IP
405 implementations in the Internet which are network manageable are
406 expected to adopt and implement this specification.
407
408
409 <span class="h2"><a class="selflink" id="section-1065" href="#section-1065">1065</a> Rose </span> Aug 88 Structure and Identification of
410 Management Information for
411 TCP/IP-based internets
412
413 This RFC provides the common definitions for the structure and
414 identification of management information for TCP/IP-based internets. In
415 particular, together with its companion memos, which describe the
416 initial management information base along with the initial network
417 management protocol, these documents provide a simple, working
418 architecture and system for managing TCP/IP-based internets and in
419 particular, the Internet.
420
421 This memo specifies a draft standard for the Internet community. TCP/IP
422 implementation in the Internet which are network manageable are expected
423 to adopt and implement this specification.
424
425
426 <span class="h2"><a class="selflink" id="section-1064" href="#section-1064">1064</a> Crispin </span> Jul 88 Interactive Mail Access Protocol -
427 Version 2
428
429 This memo suggests a method for workstations to dynamically access mail
430 from a mailbox server ("respository"). This RFC specifies a standard
431 for the SUMEX-AIM community and a proposed experimental protocol for the
432 Internet community. Discussion and suggestions for improvement are
433 requested.
434
435
436 <span class="h2"><a class="selflink" id="section-1063" href="#section-1063">1063</a> Mogul </span> Jul 88 IP MTU Discovery Options
437
438 A pair of IP options that can be used to learn the minimum MTU of a path
439 through an internet is described, along with its possible uses. This is
440 a proposal for an Experimental protocol.
441
442
443
444 <span class="grey">Reynolds [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
447
448
449 <span class="h2"><a class="selflink" id="section-1062" href="#section-1062">1062</a> Romano </span> Aug 88 Internet Numbers
450
451 This memo is an official status report on the network numbers and
452 gateway autonomous system numbers used in the Internet community.
453
454
455 <span class="h2"><a class="selflink" id="section-1061" href="#section-1061">1061</a> Never issued.</span>
456
457
458 <span class="h2"><a class="selflink" id="section-1060" href="#section-1060">1060</a> Reynolds </span> Mar 90 Assigned Numbers
459
460 This memo is a status report on the parameters (i.e., numbers and
461 keywords) used in protocols in the Internet community. Distribution of
462 this memo is unlimited.
463
464
465 <span class="h2"><a class="selflink" id="section-1059" href="#section-1059">1059</a> Mills </span> Jul 88 Network Time Protocol (Version 1)
466 Specification and Implementation
467
468 This memo describes the Network Time Protocol (NTP), specifies its
469 formal structure and summarizes information useful for its
470 implementation. NTP provides the mechanisms to synchronize time and
471 coordinate time distribution in a large, diverse internet operating at
472 rates from mundane to lightwave. It uses a returnable-time design in
473 which a distributed subnet of time servers operating in a self-
474 organizing, hierarchical master-slave configuration synchronizes logical
475 clocks within the subnet and to national time standards via wire or
476 radio. The servers can also redistribute reference time via local
477 routing algorithms and time daemons.
478
479 The NTP architectures, algorithms and protocols which have evolved over
480 several years of implementation and refinement are described in this
481 document. The prototype system, which has been in regular operation in
482 the Internet for the last two years, is described in an Appendix along
483 with performance data which shows that timekeeping accuracy throughout
484 most portions of the Internet can be ordinarily maintained to within a
485 few tens of milliseconds, even the cases of failure or disruption of
486 clocks, time servers or nets. This is a Draft Standard for an Elective
487 protocol.
488
489
490 <span class="h2"><a class="selflink" id="section-1058" href="#section-1058">1058</a> Hedrick </span> Jun 88 Routing Information Protocol
491
492 This RFC describes an existing protocol for exchanging routing
493 information among gateways and other hosts. It is intended to be used
494 as a basis for developing gateway software for use in the Internet
495 community.
496
497
498
499
500 <span class="grey">Reynolds [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
503
504
505 <span class="h2"><a class="selflink" id="section-1057" href="#section-1057">1057</a> Sun </span> Jun 88 RPC: Remote Procedure Call Protocol
506 Specification Version 2
507
508 This RFC describes a standard that Sun Microsystems and others are
509 using, and is one we wish to propose for the Internet's consideration.
510 This memo is not an Internet standard at this time.
511
512
513 <span class="h2"><a class="selflink" id="section-1056" href="#section-1056">1056</a> Lambert </span> Jun 88 PCMAIL: A Distributed Mail System
514 for Personal Computers
515
516 This memo is a discussion of the Pcmail workstation based distributed
517 mail system. It is identical to the discussion in <a href="./rfc993">RFC-993</a>, save that a
518 new, much simpler mail transport protocol is described. The new
519 transport protocol is the result of continued research into ease of
520 protocol implementation and use issues.
521
522
523 <span class="h2"><a class="selflink" id="section-1055" href="#section-1055">1055</a> Romkey </span> Jun 88 A Nonstandard for Transmission of
524 IP Datagrams over Serial Lines: SLIP
525
526 The TCP/IP protocol family runs over a variety of network media: IEEE
527 <span class="h3"><a class="selflink" id="section-802.3" href="#section-802.3">802.3</a> (ethernet) and 802.5 (token ring) LAN's, X.25 lines, satellite</span>
528 links, and serial lines. There are standard encapsulations for IP
529 packets defined for many of these networks, but there is no standard for
530 serial lines. SLIP, Serial Line IP, is a currently a de facto standard,
531 commonly used for point-to-point serial connections running TCP/IP. It
532 is not an Internet standard.
533
534
535 <span class="h2"><a class="selflink" id="section-1054" href="#section-1054">1054</a> Deering </span> May 88 Host Extensions for IP Multicasting
536
537 This memo specifies the extensions required of a host implementation of
538 the Internet Protocol (IP) to support multicasting. IP multicasting is
539 the transmission of an IP datagram to a "host group", a set hosts
540 identified by a single IP destination address. A multicast datagram is
541 delivered to all members of its destination host group with the same
542 "best-efforts" reliability as regular unicast IP datagrams. It is
543 proposed as a standard for IP multicasting in the Internet. This
544 specification is a major revision of <a href="./rfc988">RFC-988</a>.
545
546
547 <span class="h2"><a class="selflink" id="section-1053" href="#section-1053">1053</a> Levy </span> Apr 88 Telnet X.3 PAD Option
548
549 This RFC proposes a new option to Telnet for the Internet community, and
550 requests discussion and suggestions for improvements.
551
552
553
554
555
556 <span class="grey">Reynolds [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
559
560
561 <span class="h2"><a class="selflink" id="section-1052" href="#section-1052">1052</a> Cerf </span> Apr 88 IAB Recommendations for the
562 Development of Internet Network
563 Management Standards
564
565 This RFC is intended to convey to the Internet community and other
566 interested parties the recommendations of the Internet Activities Board
567 (IAB) for the development of network management protocols for use in the
568 TCP/IP environment. This memo does NOT, in and of itself, define or
569 propose an Official Internet Protocol. It does reflect, however, the
570 policy of the IAB with respect to further network management development
571 in the short and long term.
572
573
574 <span class="h2"><a class="selflink" id="section-1051" href="#section-1051">1051</a> Prindeville </span> Mar 88 A Standard for the Transmission of IP
575 Datagrams and ARP Packets over ARCNET
576 Networks
577
578 This memo specifies a standard method of encapsulating Internet Protocol
579 (IP) and Address Resolution Protocol (ARP) datagrams on an ARCNET. This
580 RFC is a standard protocol for the Internet community.
581
582
583 <span class="h2"><a class="selflink" id="section-1050" href="#section-1050">1050</a> Sun </span> Apr 88 RPC: Remote Procedure Call
584 Protocol Specification
585
586 This memo specifies a message protocol used in implementing Sun's Remote
587 Procedure Call (RPC) package. This RFC describes a standard that Sun
588 Microsystems and others are using and is one they wish to propose for
589 the Internet's consideration. It is not an Internet standard at this
590 time.
591
592
593 <span class="h2"><a class="selflink" id="section-1049" href="#section-1049">1049</a> Sirbu </span> Mar 88 A Content-Type Header Field for
594 Internet Messages
595
596 This memo suggests proposed additions to the Internet Mail Protocol,
597 <a href="./rfc822">RFC-822</a>, for the Internet community, and requests discussion and
598 suggestions for improvements.
599
600
601 <span class="h2"><a class="selflink" id="section-1048" href="#section-1048">1048</a> Prindeville </span> Feb 88 BOOTP Vendor Information Extensions
602
603 This memo proposes an addition to the Bootstrap Protocol (BOOTP).
604 Comments and suggestions for improvements are sought.
605
606
607
608
609
610
611
612 <span class="grey">Reynolds [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
615
616
617 <span class="h2"><a class="selflink" id="section-1047" href="#section-1047">1047</a> Partridge </span> Feb 88 Duplicate Messages and SMTP
618
619 An examination of a synchronization problem in the Simple Mail Transfer
620 Protocol (SMTP) is presented. This synchronization problem can cause a
621 message to be delivered multiple times. A method for avoiding this
622 problem is suggested. Nodding familiarity with the SMTP specification,
623 <a href="./rfc821">RFC-821</a>, is required.
624
625
626 <span class="h2"><a class="selflink" id="section-1046" href="#section-1046">1046</a> Prue </span> Feb 88 A Queuing Algorithm to Provide
627 Type-of-Service for IP Links
628
629 This memo is intended to explore how Type-of-Service might be
630 implemented in the Internet. The proposal describes a method of queuing
631 which can provide the different classes of service. The technique also
632 prohibits one class of service from consuming excessive resources or
633 excluding other classes of service. This is an "idea paper" and
634 discussion is strongly encouraged.
635
636
637 <span class="h2"><a class="selflink" id="section-1045" href="#section-1045">1045</a> Cheriton </span> Feb 88 VMTP: Versatile Message Transaction
638 Protocol Protocol Specification
639
640 This memo specifies the Versatile Message Transaction Protocol (VMTP)
641 [Version 0.7 of 19-Feb-88], a transport protocol specifically designed
642 to support the transaction model of communication, as exemplified by
643 remote procedure call (RPC). The full function of VMTP, including
644 support for security, real-time, asynchronous message exchanges,
645 streaming, multicast and idempotency, provides a rich selection to the
646 VMTP user level. Subsettability allows the VMTP module for particular
647 clients and servers to be specialized and simplified to the services
648 actually required. Examples of such simple clients and servers include
649 PROM network bootload programs, network boot servers, data sensors and
650 simple controllers, to mention but a few examples. This RFC describes a
651 protocol proposed as a standard for the Internet community.
652
653
654 <span class="h2"><a class="selflink" id="section-1044" href="#section-1044">1044</a> Hardwick </span> Feb 88 Internet Protocol on Network Systems
655 HYPERchannel Protocol Specification
656
657 This memo intends to provide a complete discussion of the protocols and
658 techniques used to embed DoD standard Internet Protocol datagrams (and
659 its associated higher level protocols) on Network Systems Corporation's
660 HYPERchannel equipment. This document is directed toward network
661 planners and implementors who are already familiar with the TCP/IP
662 protocol suite and the techniques used to carry TCP/IP traffic on common
663 networks such as the DDN or the Ethernet. No great familiarity with NSC
664 products is assumed; an appendix is devoted to a review of NSC
665
666
667
668 <span class="grey">Reynolds [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
671
672
673 technologies and protocols.
674
675
676 <span class="h2"><a class="selflink" id="section-1043" href="#section-1043">1043</a> Yasuda </span> Feb 88 TELNET Data Entry Terminal Option
677 DODIIS Implementation
678
679 This RFC suggests a proposed protocol on the TELNET Data Entry Terminal
680 (DET) Option - DODIIS Implementation for the Internet community. It is
681 intended that this specification be capatible with the specification of
682 DET Option in <a href="./rfc732">RFC-732</a>. Discussion and suggests for improvements are
683 encouraged.
684
685
686 <span class="h2"><a class="selflink" id="section-1042" href="#section-1042">1042</a> Postel </span> Feb 88 A Standard for the Transmission of
687 IP Datagrams over IEEE 802 Networks
688
689 This RFC specifies a standard method of encapsulating the Internet
690 Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests
691 and replies on IEEE 802 Networks to allow compatible and interoperable
692 implementations. This RFC specifies a protocol standard for the
693 Internet community.
694
695
696 <span class="h2"><a class="selflink" id="section-1041" href="#section-1041">1041</a> Rekhter </span> Jan 88 Telnet 3270 Regime Option
697
698 This RFC specifies a proposed standard for the Internet community.
699 Hosts on the Internet that want to support 3270 data stream within the
700 Telnet protocol, are expected to adopt and implement this standard.
701
702
703 <span class="h2"><a class="selflink" id="section-1040" href="#section-1040">1040</a> Linn </span> Jan 88 Privacy Enhancement for Internet
704 Electronic Mail: Part I Message
705 Encipherment and Authentication
706 Procedures
707
708 This RFC is the Outgrowth of a series of IAB Privacy Task Force meetings
709 and of internal working papers distributed for those meetings. This
710 memo defines message encipherment and authentication procedures, as the
711 initial phase of an effort to provide privacy enhancement services for
712 electronic mail transfer in the Internet. Detailed key management
713 mechanisms to support these procedures will be defined in a subsequent
714 RFC. As a goal of this initial phase, it is intended that the
715 procedures defined here be compatible with a wide range of key
716 management approaches, including both conventional (symmetric) and
717 public-key (asymmetric) approaches for encryption of data encrypting
718 keys. Use of conventional cryptography for message text encryption
719 and/or integrity check computation is anticipated.
720
721
722
723
724 <span class="grey">Reynolds [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
727
728
729 <span class="h2"><a class="selflink" id="section-1039" href="#section-1039">1039</a> Latham </span> Jan 88 A DoD Statement on Open Systems
730 Interconnection Protocols
731
732 This RFC reproduces a memorandum issued on 2-JUL-87 from the Assistant
733 Secretary of Defense for Command, Control, Communications, and
734 Intelligence (ASDC31) to the Director of the Defense Communications
735 Agency (DCA). This memo is distributed for information only.
736
737
738 <span class="h2"><a class="selflink" id="section-1038" href="#section-1038">1038</a> St. Johns </span> Jan 88 Draft Revised IP Security Option
739
740 This memo is a pre-publication draft of the revised Internet Protocol
741 Security Option. This RFC reflects the version as approved by the
742 Protocol Standards Steering group, and is provided for informational
743 purposes only. The final version of this document will be available
744 from Navy publications and should not differ from this document in any
745 major fashion. This document will be published as a change to the MIL-
746 STD 1777, "Internet Protocol".
747
748
749 <span class="h2"><a class="selflink" id="section-1037" href="#section-1037">1037</a> Greenberg </span> Dec 87 NFILE - A File Access Protocol
750
751 This document includes a specification of the NFILE file access protocol
752 and its underlying levels of protocol, the Token List Transport Layer
753 and Byte Stream with Mark. The goal of this specification is to promote
754 discussion of the ideas described here, and to encourage designers of
755 future file protocols to take advantage of these ideas. A secondary
756 goal is to make the specification available to sites that might benefit
757 from implementing NFILE.
758
759
760 <span class="h2"><a class="selflink" id="section-1036" href="#section-1036">1036</a> Horton </span> Dec 87 Standard for Interchange of
761 USENET Messages
762
763 This RFC defines the standard format for the interchange of network News
764 messages among USENET hosts. It updates and replaces <a href="./rfc850">RFC-850</a>,
765 reflecting version B2.11 of the News program. This memo is distributed
766 as an RFC to make this information easily accessible to the Internet
767 community. It does not specify an Internet standard.
768
769
770 <span class="h2"><a class="selflink" id="section-1035" href="#section-1035">1035</a> Mockapetris </span> Nov 87 Domain Names - Implementation
771 Specification
772
773 This RFC is the revised specification of the protocol and format used in
774 the implementation of the Domain Name System. It obsoletes <a href="./rfc883">RFC-883</a>.
775 This memo documents the details of the domain name client - server
776 communication.
777
778
779
780 <span class="grey">Reynolds [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
783
784
785 <span class="h2"><a class="selflink" id="section-1034" href="#section-1034">1034</a> Mockapetris </span> Nov 87 Domain Names - Concepts and
786 Facilities
787
788 This RFC is the revised basic definition of The Domain Name System. It
789 obsoletes <a href="./rfc882">RFC-882</a>. This memo describes the domain style names and their
790 used for host address look up and electronic mail forwarding. It
791 discusses the clients and servers in the domain name system and the
792 protocol used between them.
793
794
795 <span class="h2"><a class="selflink" id="section-1033" href="#section-1033">1033</a> Lottor </span> Nov 87 Domain Administrators Operations
796 Guide
797
798 This RFC provides guidelines for domain administrators in operating a
799 domain server and maintaining their portion of the hierarchical
800 database. Familiarity with the domain system is assumed (see RFCs 1031,
801 1032, 1034, and 1035).
802
803
804 <span class="h2"><a class="selflink" id="section-1032" href="#section-1032">1032</a> Stahl </span> Nov 87 Domain Administrators Guide
805
806 Domains are administrative entities that provide decentralized
807 management of host naming and addressing. The domain-naming system is
808 distributed and hierarchical.
809
810 This memo describes procedures for registering a domain with the Network
811 Information Center (NIC) of Defense Data Network (DDN), and offers
812 guidelines on the establishment and administration of a domain in
813 accordance with the requirements specified in <a href="./rfc920">RFC-920</a>. It is recommended
814 that the guidelines described in this document be used by domain
815 administrators in the establishment and control of second-level domains.
816 The role of the domain administrator (DA) is that of coordinator,
817 manager, and technician. If his domain is established at the second
818 level or lower in the tree, the domain administrator must register by
819 interacting with the management of the domain directly above this.
820
821
822 <span class="h2"><a class="selflink" id="section-1031" href="#section-1031">1031</a> Lazear </span> Nov 87 Milnet Name Domain Transition
823
824 This RFC consolidates information necessary for the implementation of
825 domain style names throughout the DDN/MILNET Internet community. The
826 introduction of domain style names will impact all hosts in the
827 DDN/MILNET Internet. This RFC is designed as an aid to implementors and
828 administrators by providing: 1) an overview of the transition process
829 from host tables to domains, 2) a timetable for the transition, and 3)
830 references to documentation and software relating to the domain system.
831
832
833
834
835
836 <span class="grey">Reynolds [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
839
840
841 <span class="h2"><a class="selflink" id="section-1030" href="#section-1030">1030</a> Lambert </span> Nov 87 On Testing the NETBLT Protocol over
842 Divers Networks
843
844 This memo describes the results gathered from testing NETBLT over three
845 networks of different bandwidths and round-trip delays. The results are
846 not complete, but the information gathered so far has not been
847 promising. The NETBLT protocol is specified in <a href="./rfc998">RFC-998</a>; this document
848 assumes an understanding of the specification as described in <a href="./rfc998">RFC-998</a>.
849
850
851 <span class="h2"><a class="selflink" id="section-1029" href="#section-1029">1029</a> Parr </span> May 88 A More Tolerant Approach to Address
852 Resolution for Multi-Lan system of
853 Ethernets
854
855 This memo discusses an extension to a Bridge Protocol to detect and
856 disclose changes in heighbouring host address parameters in a Multi-Lan
857 system of Ethernets. The problem is one which is appearing more and
858 more regularly as the interconnected systems grow larger on Campuses and
859 in Commercial Institutions. This RFC suggests a protocol enhancement
860 for the Internet community, and requests discussion and suggestions for
861 improvements.
862
863
864 <span class="h2"><a class="selflink" id="section-1028" href="#section-1028">1028</a> Davin </span> Nov 87 A Simple Gateway Monitoring Protocol
865
866 This memo defines a simple application-layer protocol by which
867 management information for a gateway may be inspected or altered by
868 remote users. This proposal is intended only as an interim response to
869 immediate gateway monitoring needs.
870
871
872 <span class="h2"><a class="selflink" id="section-1027" href="#section-1027">1027</a> Carl-Mitchell </span> Oct 87 Using ARP to Implement Transparent
873 Subnet Gateways
874
875 This RFC describes the use of the Address Resolution Protocol (ARP) by
876 subnet gateways to permit hosts on the connected subnets to communicate
877 without being aware of the existence of subnets, using the technique of
878 "Proxy ARP".
879
880
881 <span class="h2"><a class="selflink" id="section-1026" href="#section-1026">1026</a> Kille </span> Sep 87 Addendum to <a href="./rfc987">RFC-987</a> (Mapping between
882 X.400 and <a href="./rfc882">RFC-882</a>)
883
884 This memo suggest a proposed protocol for the Internet community, and
885 request discussion and suggestions for improvements.
886
887
888
889
890
891
892 <span class="grey">Reynolds [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
895
896
897 <span class="h2"><a class="selflink" id="section-1025" href="#section-1025">1025</a> Postel </span> Sep 87 TCP and IP Bake Off
898
899 This memo describes some of the procedures, scoring and tests used in
900 the TCP and IP bake offs held in the early development of these
901 protocols. These procedures and tests may still be of use in testing
902 newly implemented TCP and IP modules.
903
904
905 <span class="h2"><a class="selflink" id="section-1024" href="#section-1024">1024</a> Partridge </span> Oct 87 HEMS Variable Definitions
906
907 This memo assigns instruction codes, defines object formats and object
908 semantics for use with the High-Level Monitoring and Control Language,
909 defined in <a href="./rfc1023">RFC-1023</a>. A general system has been described in previous
910 memos (<a href="./rfc1021">RFC-1021</a>, <a href="./rfc1022">RFC-1022</a>). This system is called the High-Level Entity
911 Management System (HEMS). This memo is provisional and the definitions
912 are subject to change. Readers should confirm with the authors that
913 they have the most recent version. This RFC assumes a working knowledge
914 of the ISO data encoding standard, ASN.1, and a general understanding of
915 the IP protocol suite.
916
917
918 <span class="h2"><a class="selflink" id="section-1023" href="#section-1023">1023</a> Partridge </span> Oct 87 HEMS Monitoring and Control Language
919
920 This RFC specifies the High-Level Entity Management System (HEMS)
921 Monitoring and Control Language. This language defines the requests and
922 replies used in HEMS. This memo assumes knowledge of the HEMS system
923 described in <a href="./rfc1021">RFC-1021</a>, and of the ISO data encoding standard, ASN.1.
924
925
926 <span class="h2"><a class="selflink" id="section-1022" href="#section-1022">1022</a> Partridge </span> Oct 87 The High-Level Entity Management
927 Protocol (HEMP)
928
929 This memo presents an application protocol for managing network entities
930 such as hosts, gateways, and front end machines. This protocol is a
931 component of the High-level Entity Management System HEMS), described is
932 <a href="./rfc1021">RFC-1021</a>. This memo also assumes a knowledge of the ISO data encoding
933 standard, ASN.1.
934
935
936 <span class="h2"><a class="selflink" id="section-1021" href="#section-1021">1021</a> Partridge </span> Oct 87 The High-Level Entity Management
937 System (HEMS)
938
939 This memo provides a general overview of the High-level Entity
940 management system (HEMS). This system is experimental, and is currently
941 being tested in portions of the Internet.
942
943
944
945
946
947
948 <span class="grey">Reynolds [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
951
952
953 <span class="h2"><a class="selflink" id="section-1020" href="#section-1020">1020</a> Romano </span> Nov 87 Internet Numbers
954
955 This RFC is a list of the Assigned IP Network Numbers and EGP Autonomous
956 System Numbers. This RFC obsoletes <a href="./rfc997">RFC-997</a>.
957
958
959 <span class="h2"><a class="selflink" id="section-1019" href="#section-1019">1019</a> Arnon </span> Sep 87 Report of the Workshop on
960 Environments for Computational
961 Mathematics
962
963 This memo is a report on the discussion of the representation of
964 equations in a workshop at the ACM SIGGRAPH Conference held in Anaheim,
965 California on 30 July 1987.
966
967
968 <span class="h2"><a class="selflink" id="section-1018" href="#section-1018">1018</a> McKenzie </span> Aug 87 Some Comments on SQuID
969
970 This memo is a discussion of some of the ideas expressed in <a href="./rfc1016">RFC-1016</a> on
971 Source Quench. This memo introduces the distinction of the cause of
972 congestion in a gateway between the effects of "Funneling" and
973 Mismatch". It is offered in the same spirit as <a href="./rfc1016">RFC-1016</a>; to stimulate
974 discussion. The opinions offered are personal, not corporate, opinions.
975
976
977 <span class="h2"><a class="selflink" id="section-1017" href="#section-1017">1017</a> Leiner </span> Aug 87 Network Requirements for Scientific
978 Research
979
980 This RFC identifies the requirements on communication networks for
981 supporting scientific research. It proposes some specific areas for
982 near term work, as well as some long term goals. This is an "idea"
983 paper and discussion is strongly encouraged.
984
985
986 <span class="h2"><a class="selflink" id="section-1016" href="#section-1016">1016</a> Prue </span> July 87 Something a Host Could Do with Source
987 Quench: The Source Quench Introduced
988 Delay (SQuID)
989
990 The memo is intended to explore the issue of what a host could do with a
991 source quench. The proposal is for each source host IP module to
992 introduce some delay between datagrams sent to the same destination
993 host. This is a "crazy idea paper" and discussion is essential.
994
995
996 <span class="h2"><a class="selflink" id="section-1015" href="#section-1015">1015</a> Leiner </span> July 87 Implementation Plan for Interagency
997 Research Internet
998
999 This RFC proposes an Interagency Research Internet as the natural
1000 outgrowth of the current Internet. This is an "idea paper" and
1001
1002
1003
1004 <span class="grey">Reynolds [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
1007
1008
1009 discussion is strongly encouraged.
1010
1011
1012 <span class="h2"><a class="selflink" id="section-1014" href="#section-1014">1014</a> Sun </span> Jun 87 XDR: External Data Representation
1013 Standard
1014
1015 XDR is a standard for the description and encoding of data. It is
1016 useful for transferring data between different computer architectures.
1017 XDR fits into ISO presentation layer, and is roughly analogous in
1018 purpose to X.409, ISO Abstract Syntax Notation. The major difference
1019 between these two is that XDR uses implicit typing, while X.409 uses
1020 explicit typing. This RFC is distributed for information only, it does
1021 not establish a Internet standard.
1022
1023
1024 <span class="h2"><a class="selflink" id="section-1013" href="#section-1013">1013</a> Scheifler </span> Jun 87 X Window System Protocol,
1025 Version 11-Beta
1026
1027 This RFC is distributed to the Internet community for information only.
1028 It does not establish an Internet standard. The X window system has
1029 been widely reviewed and tested. The Internet community is encouraged
1030 to experiment with it.
1031
1032
1033 <span class="h2"><a class="selflink" id="section-1012" href="#section-1012">1012</a> Reynolds </span> Jun 87 Bibliography of Requests for
1034 Comments 1-999
1035
1036 This RFC is a reference guide for the Internet community which provides
1037 a bibliographic summary of the Request for Comments numbers 1 through
1038 <span class="h2"><a class="selflink" id="section-999" href="#section-999">999</a> issued between the years 1969-1987.</span>
1039
1040
1041 <span class="h2"><a class="selflink" id="section-1011" href="#section-1011">1011</a> Reynolds </span> May 87 Official Internet Protocols
1042
1043 This memo is an official status report on the protocols used in the
1044 Internet community. It identifies the documents specifying the official
1045 protocols used in the Internet. Comments indicate any revisions or
1046 changes planned.
1047
1048
1049 <span class="h2"><a class="selflink" id="section-1010" href="#section-1010">1010</a> Reynolds </span> May 87 Assigned Numbers
1050
1051 This memo is an official status report on the numbers used in protocols
1052 in the Internet community. It documents the currently assigned values
1053 from several series of numbers including link, socket, port, and
1054 protocol, used in network protocol implementations.
1055
1056
1057
1058
1059
1060 <span class="grey">Reynolds [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
1063
1064
1065 <span class="h2"><a class="selflink" id="section-1009" href="#section-1009">1009</a> Braden </span> Jun 87 Requirements for Internet Gateways
1066
1067 This RFC summarizes the requirements for gateways to be used between
1068 networks supporting the Internet protocols. This document is a formal
1069 statement of the requirements to be met by gateways used in the Internet
1070 system. As such, it is an official specification for the Internet
1071 community.
1072
1073
1074 <span class="h2"><a class="selflink" id="section-1008" href="#section-1008">1008</a> McCoy </span> Jun 87 Implementation Guide for the ISO
1075 Transport Protocol
1076
1077 This RFC is being distributed to members of the Internet community in
1078 order to solicit comments on the Implementors Guide. While this
1079 document may not be directly relevant to the research problems of the
1080 Internet, it may be of some interest to a number of researchers and
1081 implementors.
1082
1083
1084 <span class="h2"><a class="selflink" id="section-1007" href="#section-1007">1007</a> McCoy </span> Jun 87 Military Supplement to the ISO
1085 Transport Protocol
1086
1087 This document supplements the Transport Service and Protocol of the
1088 International Standards Organization (ISO), IS 8072 and IS 8073,
1089 respectively, and their formal descriptions by providing conventions,
1090 option selections and parameter values. This RFC is being distributed
1091 to members of the Internet community in order to solicit comments on the
1092 Draft Military Supplement. While this document may not be directly
1093 relevant to the research problems of the Internet, it may be of some
1094 interest to a number of researchers and implementors.
1095
1096
1097 <span class="h2"><a class="selflink" id="section-1006" href="#section-1006">1006</a> Rose </span> May 87 ISO Transport Services on top of
1098 the TCP Version: 3
1099
1100 This memo specifies a standard for the Internet community. Hosts on the
1101 Internet that choose to implement ISO transport services on top of the
1102 TCP are expected to adopt and implement this standard. TCP port 102 is
1103 reserved for hosts which implement this standard. This memo specifies
1104 version 3 of the protocol and supersedes <a href="./rfc983">RFC-983</a>. Changes between the
1105 protocol is described in <a href="./rfc983">RFC-983</a> and this memo are minor, but
1106 unfortunately incompatible.
1107
1108
1109 <span class="h2"><a class="selflink" id="section-1005" href="#section-1005">1005</a> Khanna </span> May 87 The ARPANET AHIP-E Host Access
1110 Protocol (Enhanced AHIP)
1111
1112 This RFC is a proposed specification for the encoding of Class A IP
1113
1114
1115
1116 <span class="grey">Reynolds [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
1119
1120
1121 addresses for use on ARPANET-style networks such as the Milnet and
1122 Arpanet, and for enhancements to the ARPANET AHIP Host Access Protocol
1123 (AHIP; formerly known as 1822). These enhancements increase the size of
1124 the PSN field, allow ARPANET hosts to use logical names to address each
1125 other, allow for the communication of type-of-service information from
1126 the host to the PSN and enable the PSN to provide congestion feedback to
1127 the host on a connection basis.
1128
1129
1130 <span class="h2"><a class="selflink" id="section-1004" href="#section-1004">1004</a> Mills </span> Apr 87 A Distributed-Protocol
1131 Authentication Scheme
1132
1133 The purpose of this RFC is to focus discussion on authentication
1134 problems in the Internet and possible methods of solution. The proposed
1135 solutions this document are not intended as standards for the Internet
1136 at this time. Rather, it is hoped that a general consensus will emerge
1137 as to the appropriate solution to authentication problems, leading
1138 eventually to the adoption of standards. This document suggests
1139 mediated access-control and authentication procedures suitable for those
1140 cases when an association is to be set up between users belonging to
1141 different trust environments.
1142
1143
1144 <span class="h2"><a class="selflink" id="section-1003" href="#section-1003">1003</a> Katz </span> Mar 87 Issues in Defining an Equations
1145 Representation Standard
1146
1147 This memo is intended to identify and explore issues in defining a
1148 standard for the exchange of mathematical equations. No attempt is made
1149 at a complete definition and more questions are asked than are answered.
1150 Questions about the user interface are only addressed to the extent that
1151 they affect interchange issues.
1152
1153
1154 <span class="h2"><a class="selflink" id="section-1002" href="#section-1002">1002</a> NETBIOS </span> Mar 87 Protocol Standard for A NetBIOS
1155 Service on a TCP/UDP Transport:
1156 Detailed Specifications
1157
1158 This RFC defines a proposed standard protocol to support NetBIOS
1159 services in a TCP/IP environment. Both local network and internet
1160 operation are supported. Various node types are defined to accommodate
1161 local and internet topologies and to allow operation with or without the
1162 use of IP broadcast. This RFC gives the detailed specifications of the
1163 netBIOS-over-TCP packets, protocols, and defined constants and
1164 variables. A more general overview is found in a companion RFC,
1165 "Protocol Standard For NetBIOS Service on TCP/UDP Transport: Concepts
1166 and Methods".
1167
1168
1169
1170
1171
1172 <span class="grey">Reynolds [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc1099">RFC 1099</a> Summary of 1000-1099 December 1991</span>
1175
1176
1177 <span class="h2"><a class="selflink" id="section-1001" href="#section-1001">1001</a> NETBIOS </span> Mar 87 Protocol Standard for A NetBIOS
1178 Service on a TCP/UDP Transport:
1179 Concepts and Methods
1180
1181 This RFC defines a proposed standard protocol to support NetBIOS
1182 services in a TCP/IP environment. Both local network and internet
1183 operation are supported. Various node types are defined to accommodate
1184 local and internet topologies and to allow operation with or without the
1185 use of IP broadcast. This RFC describes the NetBIOS-over-TCP protocols
1186 in a general manner, emphasizing the underlying ideas and techniques.
1187 Detailed specifications are found in a companion RFC, "Protocol Standard
1188 For a NetBIOS Service on a TCP/UDP Transport: Detailed Specifications".
1189
1190
1191 <span class="h2"><a class="selflink" id="section-1000" href="#section-1000">1000</a> Reynolds </span> Aug 87 The Request for Comments Reference
1192 Guide
1193
1194 This RFC Reference Guide is intended to provide a historical account by
1195 categorizing and summarizing of the Request for Comments numbers 1
1196 through 999 issued between the years 1969-1987. These documents have
1197 been crossed referenced to indicate which RFCs are current, obsolete, or
1198 revised.
1199
1200
1201 Security Considerations
1202
1203 Security issues are not discussed in this memo.
1204
1205 Author's Address
1206
1207 Joyce K. Reynolds
1208 University of Southern California
1209 Information Sciences Institute
1210 4676 Admiralty Way
1211 Marina del Rey, CA 90292
1212
1213 Phone: (310) 822-1511
1214
1215 EMail: [email protected]
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228 Reynolds [Page 22]
1229 </pre>