| 1 |
<pre>Network Working Group J. Reynolds |
| 2 |
Request for Comments: 1000 J. Postel |
| 3 |
ISI |
| 4 |
August 1987 |
| 5 |
|
| 6 |
Obsoletes: RFCs <a href="./rfc084">084</a>, <a href="./rfc100">100</a>, <a href="./rfc160">160</a>, <a href="./rfc170">170</a>, <a href="./rfc200">200</a>, <a href="./rfc598">598</a>, <a href="./rfc699">699</a>, <a href="./rfc800">800</a>, <a href="./rfc899">899</a>, <a href="./rfc999">999</a> |
| 7 |
|
| 8 |
|
| 9 |
<span class="h1">THE REQUEST FOR COMMENTS REFERENCE GUIDE</span> |
| 10 |
|
| 11 |
|
| 12 |
STATUS OF THIS MEMO |
| 13 |
|
| 14 |
This RFC is a reference guide for the Internet community which |
| 15 |
summarizes of all the Request for Comments issued between April 1969 |
| 16 |
and March 1987. This guide also categorizes the RFCs by topic. |
| 17 |
|
| 18 |
INTRODUCTION |
| 19 |
|
| 20 |
This RFC Reference Guide is intended to provide a historical account |
| 21 |
by categorizing and summarizing of the Request for Comments numbers 1 |
| 22 |
through 999 issued between the years 1969-1987. These documents have |
| 23 |
been crossed referenced to indicate which RFCs are current, obsolete, |
| 24 |
or revised. Distribution of this memo is unlimited. |
| 25 |
|
| 26 |
THE ORIGINS OF RFCS - by Stephen D. Crocker |
| 27 |
|
| 28 |
The DDN community now includes hundreds of nodes and thousands of |
| 29 |
users, but once it was all a gleam in Larry Roberts' eye. While much |
| 30 |
of the development proceeded according to a grand plan, the design of |
| 31 |
the protocols and the creation of the RFCs was largely accidental. |
| 32 |
|
| 33 |
The procurement of the ARPANET was initiated in the summer of 1968 -- |
| 34 |
Remember Vietnam, flower children, etc? There had been prior |
| 35 |
experiments at various ARPA sites to link together computer systems, |
| 36 |
but this was the first version to explore packet-switching on a grand |
| 37 |
scale. ("ARPA" didn't become "DARPA" until 1972.) Unlike most of |
| 38 |
the ARPA/IPTO procurements of the day, this was a competitive |
| 39 |
procurement. The contract called for four IMPs to be delivered to |
| 40 |
UCLA, SRI, UCSB and The University of Utah. These sites were running |
| 41 |
a Sigma 7 with the SEX operating system, an SDS 940 with the Genie |
| 42 |
operating system, an IBM 360/75 with OS/MVT (or perhaps OS/MFT), and |
| 43 |
a DEC PDP-10 with the Tenex operating system. Options existed for |
| 44 |
additional nodes if the first experiments were successful. BBN won |
| 45 |
the procurement in December 1968, but that gets ahead of this story. |
| 46 |
|
| 47 |
Part of the reason for selecting these four sites was these were |
| 48 |
existing ARPA computer science research contractors. The precise |
| 49 |
usage of the ARPANET was not spelled out in advance, and the research |
| 50 |
community could be counted on to take some initiative. To stimulate |
| 51 |
this process, a meeting was called during the summer with |
| 52 |
representatives from the selected sites, chaired by Elmer Shapiro |
| 53 |
|
| 54 |
|
| 55 |
<span class="grey">Reynolds & Postel [Page 1]</span></pre> |
| 56 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 57 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 58 |
|
| 59 |
|
| 60 |
from SRI. If memory serves me correctly, Jeff Rulifson came from |
| 61 |
SRI, Ron Stoughton from UCSB, Steve Carr from Utah and I came from |
| 62 |
UCLA. (Apologies to anyone I've left out; records are inaccessible or |
| 63 |
lost at this point.) At this point we knew only that the network was |
| 64 |
coming, but the precise details weren't known. |
| 65 |
|
| 66 |
That first meeting was seminal. We had lots of questions -- how IMPs |
| 67 |
and hosts would be connected, what hosts would say to each other, and |
| 68 |
what applications would be supported. No one had any answers, but |
| 69 |
the prospects seemed exciting. We found ourselves imagining all |
| 70 |
kinds of possibilities -- interactive graphics, cooperating |
| 71 |
processes, automatic data base query, electronic mail -- but no one |
| 72 |
knew where to begin. We weren't sure whether there was really room |
| 73 |
to think hard about these problems; surely someone from the east |
| 74 |
would be along by and by to bring the word. But we did come to one |
| 75 |
conclusion: We ought to meet again. Over the next several months, we |
| 76 |
managed to parlay that idea into a series of exchange meetings at |
| 77 |
each of our sites, thereby setting the most important precedent in |
| 78 |
protocol design. |
| 79 |
|
| 80 |
The first few meetings were quite tenuous. We had no official |
| 81 |
charter. Most of us were graduate students and we expected that a |
| 82 |
professional crew would show up eventually to take over the problems |
| 83 |
we were dealing with. Without clear definition of what the host-IMP |
| 84 |
interface would look like, or even what functions the IMP would |
| 85 |
provide, we focused on exotic ideas. We envisioned the possibility |
| 86 |
of application specific protocols, with code downloaded to user |
| 87 |
sites, and we took a crack at designing a language to support this. |
| 88 |
The first version was known as DEL, for "Decode-Encode Language" and |
| 89 |
a later version was called NIL, for "Network Interchange Language." |
| 90 |
When the IMP contract was finally let and BBN provided some definite |
| 91 |
information on the host-IMP interface, all attention shifted to |
| 92 |
low-level matters and the ambitious ideas for automatic downloading |
| 93 |
of code evaporated. It was several years before ideas like remote |
| 94 |
procedure calls and typed objects reappeared. |
| 95 |
|
| 96 |
In February of 1969 we met for the first time with BBN. I don't |
| 97 |
think any of us were prepared for that meeting. The BBN folks, led |
| 98 |
by Frank Heart, Bob Kahn, Severo Ornstein and Will Crowther, found |
| 99 |
themselves talking to a crew of graduate students they hadn't |
| 100 |
anticipated. And we found ourselves talking to people whose first |
| 101 |
concern was how to get bits to flow quickly and reliably but hadn't |
| 102 |
-- of course -- spent any time considering the thirty or forty layers |
| 103 |
of protocol above the link level. And while BBN didn't take over the |
| 104 |
protocol design process, we kept expecting that an official protocol |
| 105 |
design team would announce itself. |
| 106 |
|
| 107 |
A month later, after a particularly delightful meeting in Utah, it |
| 108 |
became clear to us that we had better start writing down our |
| 109 |
|
| 110 |
|
| 111 |
<span class="grey">Reynolds & Postel [Page 2]</span></pre> |
| 112 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 113 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 114 |
|
| 115 |
|
| 116 |
discussions. We had accumulated a few notes on the design of DEL and |
| 117 |
other matters, and we decided to put them together in a set of notes. |
| 118 |
I remember having great fear that we would offend whomever the |
| 119 |
official protocol designers were, and I spent a sleepless night |
| 120 |
composing humble words for our notes. The basic ground rules were |
| 121 |
that anyone could say anything and that nothing was official. And to |
| 122 |
emphasize the point, I labeled the notes "Request for Comments." I |
| 123 |
never dreamed these notes would distributed through the very medium |
| 124 |
we were discussing in these notes. Talk about Sorcerer's Apprentice! |
| 125 |
|
| 126 |
Over the spring and summer of 1969 we grappled with the detailed |
| 127 |
problems of protocol design. Although we had a vision of the vast |
| 128 |
potential for intercomputer communication, designing usable protocols |
| 129 |
was another matter. A custom hardware interface and custom intrusion |
| 130 |
into the operating system was going to be required for anything we |
| 131 |
designed, and we anticipated serious difficulty at each of the sites. |
| 132 |
We looked for existing abstractions to use. It would have been |
| 133 |
convenient if we could have made the network simply look like a tape |
| 134 |
drive to each host, but we knew that wouldn't do. |
| 135 |
|
| 136 |
It was clear we needed to support remote login for interactive use -- |
| 137 |
later known as Telnet -- and we needed to move files from machine to |
| 138 |
machine. We also knew that we needed a more fundamental point of |
| 139 |
view for building a larger array of protocols. Unfortunately, |
| 140 |
operating systems of that era tended to view themselves as the center |
| 141 |
of the universe; symmetric cooperation did not fit into the concepts |
| 142 |
currently available within these operating systems. And time was |
| 143 |
pressing: The first IMP was due to be delivered to UCLA September 1, |
| 144 |
1969, and the rest were scheduled at monthly intervals. |
| 145 |
|
| 146 |
At UCLA we scrambled to build a host-IMP interface. SDS, the builder |
| 147 |
of the Sigma 7, wanted many months and many dollars to do the job. |
| 148 |
Mike Wingfield, another grad student at UCLA, stepped in and offered |
| 149 |
to get interface built in six weeks for a few thousand dollars. He |
| 150 |
had a gorgeous, fully instrumented interface working in five and one |
| 151 |
half weeks. I was in charge of the software, and we were naturally |
| 152 |
running a bit late. September 1 was Labor Day, so I knew I had a |
| 153 |
couple of extra days to debug the software. Moreover, I had heard |
| 154 |
BBN was having some timing troubles with the software, so I had some |
| 155 |
hope they'd miss the ship date. And I figured that first some |
| 156 |
Honeywell people would install the hardware -- IMPs were built out of |
| 157 |
Honeywell 516s in those days -- and then BBN people would come in a |
| 158 |
few days later to shake down the software. An easy couple of weeks |
| 159 |
of grace. |
| 160 |
|
| 161 |
BBN fixed their timing trouble, air shipped the IMP, and it arrived |
| 162 |
on our loading dock on Saturday, August 30. They arrived with the |
| 163 |
IMP, wheeled it into our computer room, plugged it in and the |
| 164 |
|
| 165 |
|
| 166 |
|
| 167 |
<span class="grey">Reynolds & Postel [Page 3]</span></pre> |
| 168 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 169 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 170 |
|
| 171 |
|
| 172 |
software restarted from where it had been when the plug was pulled in |
| 173 |
Cambridge. Still Saturday, August 30. Panic time at UCLA. |
| 174 |
|
| 175 |
The second IMP was delivered to SRI at the beginning of October, and |
| 176 |
ARPA's interest was intense. Larry Roberts and Barry Wessler came by |
| 177 |
for a visit on November 21, and we actually managed to demonstrate a |
| 178 |
Telnet-like connection to SRI. |
| 179 |
|
| 180 |
With the pressure to get something working and the general confusion |
| 181 |
as to how to achieve the high generality we all aspired to, we punted |
| 182 |
and defined the first set of protocols to include only Telnet and FTP |
| 183 |
functions. In particular, only asymmetric, user-server relationships |
| 184 |
were supported. In December 1969, we met with Larry Roberts in Utah, |
| 185 |
and suffered our first direct experience with "redirection". Larry |
| 186 |
made it abundantly clear that our first step was not big enough, and |
| 187 |
we went back to the drawing board. Over the next few months we |
| 188 |
designed a symmetric host-host protocol, and we defined an abstract |
| 189 |
implementation of the protocol known as the Network Control Program. |
| 190 |
("NCP" later came to be used as the name for the protocol, but it |
| 191 |
originally meant the program within the operating system that managed |
| 192 |
connections. The protocol itself was known blandly only as the |
| 193 |
host-host protocol.) Along with the basic host-host protocol, we |
| 194 |
also envisioned a hierarchy of protocols, with Telnet, FTP and some |
| 195 |
splinter protocols as the first examples. If we had only consulted |
| 196 |
the ancient mystics, we would have seen immediately that seven layers |
| 197 |
were required. |
| 198 |
|
| 199 |
The initial experiment had been declared an immediate success and the |
| 200 |
network continued to grow. More and more people started coming to |
| 201 |
meetings, and the Network Working Group began to take shape. Working |
| 202 |
Group meetings started to have 50 and 100 people in attendance |
| 203 |
instead of the half dozen we had had in 1968 and early 1969. We held |
| 204 |
one meeting in conjunction with the Spring Joint Computer Conference |
| 205 |
in Atlantic City in 1971. In October 1971 we all convened at MIT for |
| 206 |
a major protocol "fly-off". Representatives from each site were on |
| 207 |
hand, and everyone tried to log in to everyone else's site. With the |
| 208 |
exception of one site that was completely down, the matrix was almost |
| 209 |
completely filled in, and we had reached a major milestone in |
| 210 |
connectivity. |
| 211 |
|
| 212 |
The rapid growth of the network and the working group also led to a |
| 213 |
large pile of RFCs. When the 100th RFC was in sight, Peggy Karp took |
| 214 |
on the task of indexing them. That seemed like a large task then, |
| 215 |
and we could have hardly anticipated seeing more than a 1000 RFCs |
| 216 |
several years later. |
| 217 |
|
| 218 |
Where will it end? The network has the exceeded all estimates of its |
| 219 |
growth. It has been transformed, extended, cloned, renamed and |
| 220 |
reimplemented. I doubt if there is a single computer still on the |
| 221 |
|
| 222 |
|
| 223 |
<span class="grey">Reynolds & Postel [Page 4]</span></pre> |
| 224 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 225 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 226 |
|
| 227 |
|
| 228 |
network that was on it in 1971. But the RFCs march on. Maybe I'll |
| 229 |
write a few words for <a href="./rfc10">RFC 10</a>,000. |
| 230 |
|
| 231 |
REQUEST FOR COMMENTS BY CATEGORIES |
| 232 |
|
| 233 |
The RFCs are categorized into several broad groups and within these |
| 234 |
groups are subdivided by topic. For example, the RFCs relating to |
| 235 |
file transfer are in 5 (Applications) c (File Transfer). |
| 236 |
|
| 237 |
1. Administrative |
| 238 |
|
| 239 |
1a. Assigned Numbers RFCs |
| 240 |
|
| 241 |
997, 990, 960, 943, 923, 900, 870, 820, 790, 776, 770, 762, |
| 242 |
758, 755, 750, 739, 717, 604, 503, 433, 349, 322, 317, 204, |
| 243 |
179, 175, 167. |
| 244 |
|
| 245 |
1b. Official Protocols RFCs |
| 246 |
|
| 247 |
991, 961, 944, 924, 901, 880, 840, 694, 661, 617, 582, 580, |
| 248 |
552. |
| 249 |
774 - Internet Protocol Handbook Table of Contents |
| 250 |
|
| 251 |
1c. Meeting Notes and Minutes |
| 252 |
|
| 253 |
898 - Gateway Special Interest Group Meeting Notes |
| 254 |
808, 805, 469 - Computer Mail Meeting Notes |
| 255 |
910, 807 - Multimedia Mail Meeting Notes |
| 256 |
585 - ARPANET Users Interest Working Group Meeting |
| 257 |
549, 396, 282, 253 - Graphics Meeting Notes |
| 258 |
371 - International Computer Communications Conference |
| 259 |
327 - Data and File Transfer Workshop Notes |
| 260 |
316 - Data Management Working Group Meeting Report |
| 261 |
164, 131, 116, 108, 101, 082, 077, 066, 063, 037, 021 - Network |
| 262 |
Working Group Meeting |
| 263 |
|
| 264 |
1d. Meeting Announcements and Group Overviews |
| 265 |
|
| 266 |
828 - Data Communications: IFIP's International "Network" of |
| 267 |
Experts |
| 268 |
631 - Call for Papers: International Meeting on Minicomputers |
| 269 |
and Data Communication |
| 270 |
584 - Charter for ARPANET Users Interest Working Group |
| 271 |
537 - Announcement of NGG Meeting |
| 272 |
526 - Technical Meeting - Digital Image Processing Software |
| 273 |
Systems |
| 274 |
504 - Workshop Announcement |
| 275 |
483 - Cancellation of the Resource Notebook Framework Meeting |
| 276 |
474, 314, 246, 232, 134 - Network Graphics Working Group |
| 277 |
|
| 278 |
|
| 279 |
<span class="grey">Reynolds & Postel [Page 5]</span></pre> |
| 280 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 281 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 282 |
|
| 283 |
|
| 284 |
471 - Announcement of a (Tentative) Workshop on Multi-Site |
| 285 |
Executive Programs |
| 286 |
461 - Telnet Meeting Announcement |
| 287 |
457 - TIPUG |
| 288 |
456 - Memorandum |
| 289 |
454 - File Transfer Protocol Meeting Announcement |
| 290 |
453 - Meeting Announcement to Discuss a Network Mail System |
| 291 |
374 - IMP System Announcement |
| 292 |
359 - The Status of the Release of the New IMP System (2600) |
| 293 |
343, 331 - IMP System Change Notification |
| 294 |
324 - RJE Protocol Meeting |
| 295 |
323 - Formation of Network Measurement Group (NMG) |
| 296 |
320 - Workshop on Hard Copy Line Graphics |
| 297 |
309 - Data and File Transfer Workshop Announcement |
| 298 |
299 - Information Management System |
| 299 |
295 - Report of the Protocol Workshop |
| 300 |
291, 188, 173 - Data Management Meetings |
| 301 |
245, 234, 207, 188, 173, 140, 116, 099, 087, 085, 075, 043, 035 |
| 302 |
- Network Working Group Meetings |
| 303 |
222 - System Programmer's Workshop |
| 304 |
212 - NWG Meeting on Network Usage |
| 305 |
157 - Invitation to the Second Symposium on Problems in the |
| 306 |
Optimization of Data Communication Systems |
| 307 |
149 - The Best Laid Plans... |
| 308 |
147 - The Definition of a Socket |
| 309 |
111 - Pressure from the Chairman |
| 310 |
048 - A Possible Protocol Plateau |
| 311 |
046 - ARPA Network Protocol Notes |
| 312 |
|
| 313 |
1e. Distribution List |
| 314 |
|
| 315 |
402, 363, 329, 303, 300, 211, 168, 155 - ARPA Network Mailing |
| 316 |
Lists |
| 317 |
069 - Distribution List Change for MIT |
| 318 |
052 - Updated Distribution List |
| 319 |
|
| 320 |
1f. Policies |
| 321 |
|
| 322 |
980 - Protocol Document Order Form |
| 323 |
952, 810, 608 - Host Table Specification |
| 324 |
945 - A DoD Statement on the NRC Report |
| 325 |
902 - ARPA-Internet Protocol Policy |
| 326 |
849 - Suggestions for Improved Host Table Distribution |
| 327 |
678 - Document Formats |
| 328 |
602 - The Stockings Were Hung by the Chimney With Care |
| 329 |
115 - Some Network Information Center Policies on Handling |
| 330 |
Documents |
| 331 |
053 - An Official Protocol Mechanism |
| 332 |
|
| 333 |
|
| 334 |
|
| 335 |
<span class="grey">Reynolds & Postel [Page 6]</span></pre> |
| 336 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 337 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 338 |
|
| 339 |
|
| 340 |
1g. Request for Comments Administrative |
| 341 |
|
| 342 |
999, 899, 800, 699 - Requests for Comments Summary |
| 343 |
825 - Request for Comments on Requests for Comments |
| 344 |
629 - Scenario for Using the Network Journal |
| 345 |
628 - Status of RFC Numbers and a Note on Pre-assigned Journal |
| 346 |
Numbers |
| 347 |
598, 200, 170, 160, 100, 084 - RFC Index |
| 348 |
|
| 349 |
1h. Bibliographies |
| 350 |
|
| 351 |
829 - Packet Satellite Technology Reference Sources |
| 352 |
290 - Computer Network and Data Sharing: A Bibliography |
| 353 |
243 - Network and Data Sharing Bibliography |
| 354 |
|
| 355 |
1i. Other |
| 356 |
|
| 357 |
637 - Change of Network Address for SU-DSL |
| 358 |
634 - Change in Network Address for Haskins Lab |
| 359 |
616 - Latest Network Maps |
| 360 |
609 - Statement of Upcoming Move of NIC/NLS Service |
| 361 |
590 - MULTICS Address Change |
| 362 |
588 - London Node is Now Up |
| 363 |
551 - NYU, ANL, and LBL Joining the Net |
| 364 |
544 - Locating On-Line Documentation at SRI-ARC |
| 365 |
543 - Network Journal Submission and Delivery |
| 366 |
518 - ARPANET Accounts |
| 367 |
511 - Enterprise Phone Service to NIC From ARPANET Sites |
| 368 |
510 - Request for Network Mailbox Addresses |
| 369 |
432 - Network Logical Map |
| 370 |
423, 389 - UCLA Campus Computing Network Liaison Staff for APRA |
| 371 |
Network |
| 372 |
421 - A Software Consulting Service for Network Users |
| 373 |
419 - MIT-DMS on Vacation |
| 374 |
416 - The ARC System will be Unavailable for Use During |
| 375 |
Thanksgiving Week |
| 376 |
405 - Correction to <a href="./rfc404">RFC 404</a> |
| 377 |
404 - Host Address Changes Involving Rand and ISI |
| 378 |
403 - Desirability of a Network 1108 Service |
| 379 |
386 - Letter to TIP Users - 2 |
| 380 |
384 - Official Site IDENTS for Organizations in the ARPA |
| 381 |
Networks |
| 382 |
381 - Three Aids to Improved Network Operation |
| 383 |
356 - ARPA Network Control Center |
| 384 |
334 - Network Use on May 8 |
| 385 |
305 - Unknown Host Numbers |
| 386 |
301 - BBN IMP No. 5 and NCC Schedule for March 4, 1972 |
| 387 |
276 - NIC Course |
| 388 |
249 - Coordination of Equipment and Supplies Purchase |
| 389 |
|
| 390 |
|
| 391 |
<span class="grey">Reynolds & Postel [Page 7]</span></pre> |
| 392 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 393 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 394 |
|
| 395 |
|
| 396 |
223 - Network Information Center Schedule for Network Users |
| 397 |
185 - NIC Distribution of Manuals and Handbooks |
| 398 |
154 - Exposition Style |
| 399 |
136 - Host Accounting and Administrative Procedures |
| 400 |
118 - Information Required for Each Service Available to the |
| 401 |
Network |
| 402 |
095 - Distribution of NWG/RFC's Through the NIC |
| 403 |
016 - MIT |
| 404 |
|
| 405 |
2. ARPANET Host to Host Protocol |
| 406 |
|
| 407 |
2a. Network Control Protocol |
| 408 |
|
| 409 |
801 - NCP/TCP Transition Plan |
| 410 |
773 - Comments on NCP/TCP Mail Service Transition Strategy |
| 411 |
714 - A Host/Host Protocol for an ARPANET-type Network |
| 412 |
689 - Tenex NCP Finite State Machine for Connections |
| 413 |
663 - A Lost Message Detection and Recovery Protocol |
| 414 |
636 - TIP/TENEX Reliability Improvements |
| 415 |
635 - An Assessment of ARPANET Protocols |
| 416 |
534, 516, 512 - Lost Message Detection |
| 417 |
492, 467 - Proposed Change to Host-Host Protocol |
| 418 |
Resynchronization of Connection Status |
| 419 |
489 - Comment on Resynchronization of Connection Status |
| 420 |
Proposal |
| 421 |
425 - "But my NCP Costs $500 a day..." |
| 422 |
210 - Improvement of Flow Control |
| 423 |
197 - Initial Connection Protocol - Revised |
| 424 |
176 - Comments on Byte Size for Connections |
| 425 |
165 - A Proferred Official Initial Connection Protocol |
| 426 |
147 - The Definition of a Socket |
| 427 |
142 - Time-out Mechanism in the Host-Host Protocol |
| 428 |
132, 124, 107, 102 - Output of the Host-Host Protocol Glitch |
| 429 |
Cleaning Committee |
| 430 |
129 - A Request for Comments on Socket Name Structure |
| 431 |
128 - Bytes |
| 432 |
117 - Some Comments on the Official Protocol |
| 433 |
072 - Proposed Moratorium on Changes to Network Protocol |
| 434 |
068 - Comments on Memory Allocation Control Commands (CEASE, |
| 435 |
ALL, GVB, RET) and RFNM |
| 436 |
065 - Comments on Host-Host Protocol Document Number 1 |
| 437 |
060 - A Simplified NCP Protocol |
| 438 |
059 - Flow Control-Fixed Versus Demand Allocation |
| 439 |
058 - Logical Message Synchronization |
| 440 |
057, 054 - An Official Protocol Proffering |
| 441 |
056 - Third Level Protocol |
| 442 |
055 - A Prototypical Implementation of the NCP |
| 443 |
050, 049, 048, 047, 046, 045, 044, 040, 039, 038, 036, 033 - |
| 444 |
New Host-Host Protocol |
| 445 |
|
| 446 |
|
| 447 |
<span class="grey">Reynolds & Postel [Page 8]</span></pre> |
| 448 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 449 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 450 |
|
| 451 |
|
| 452 |
042 - Message Data Types |
| 453 |
023 - Transmission of Multiple Control Messages |
| 454 |
022 - Host-Host Control Message Formats |
| 455 |
018 - Comments Re: Host-Host control link |
| 456 |
015 - Network Subsystem for Time Sharing Hosts |
| 457 |
011 - Implementation of the Host-Host Software Procedures in |
| 458 |
GORDO |
| 459 |
009, 001 - Host Software |
| 460 |
008 - ARPA Network Functional Specifications |
| 461 |
005 - DEL |
| 462 |
002 - Links |
| 463 |
|
| 464 |
2b. Initial Connection Protocol |
| 465 |
|
| 466 |
202 - Possible Deadlock in ICP |
| 467 |
197 - Initial Connection Protocol - Revised |
| 468 |
161 - A Solution to the Race Condition in the ICP |
| 469 |
151, 148, 143, 127, 123 - A Proferred Official ICP |
| 470 |
150 - The Use of IPC Facilities |
| 471 |
145 - Initial Connection Protocol Control Commands |
| 472 |
093 - Initial Connection Protocol |
| 473 |
080 - Protocol and Data Formats |
| 474 |
066 - 3rd Level Ideas and Other Noise |
| 475 |
|
| 476 |
3. Internet Level |
| 477 |
|
| 478 |
3a. Internet Protocol |
| 479 |
|
| 480 |
815 - IP Datagram Reassembly Algorithms |
| 481 |
791, 760 - Internet Protocol (IP) |
| 482 |
781 - A Specification of the Internet Protocol IP Timestamp |
| 483 |
Option |
| 484 |
|
| 485 |
3b. Internet Control Message Protocol |
| 486 |
|
| 487 |
792, 777 - Internet Control Message Protocol (ICMP) |
| 488 |
|
| 489 |
3c. Gateway Protocols |
| 490 |
|
| 491 |
985 - Requirements for Internet Gateways |
| 492 |
975 - Autonomous Confederations |
| 493 |
970 - On Packet Switches With Infinite Storage |
| 494 |
911 - EGP Gateway under Berkeley Unix |
| 495 |
904, 890, 888, 827 - Exterior Gateway Protocol |
| 496 |
875 - Gateways, Architectures, and Heffalumps |
| 497 |
823 - Gateway Gateway Protocol |
| 498 |
|
| 499 |
|
| 500 |
|
| 501 |
|
| 502 |
|
| 503 |
<span class="grey">Reynolds & Postel [Page 9]</span></pre> |
| 504 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 505 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 506 |
|
| 507 |
|
| 508 |
3d. Other |
| 509 |
|
| 510 |
986 - Working Draft - Guidelines for the Use of Internet-IP |
| 511 |
Addressing in the ISO Connectionless-Mode Network |
| 512 |
981 - An Experimental Multiple-Path Routing Algorithm |
| 513 |
963 - Some Problems with the Specification of the Military |
| 514 |
Standard Internet Protocol |
| 515 |
950 - Internet Standard Subnetting Procedure |
| 516 |
947 - Multi-Network Broadcasting Within the Internet |
| 517 |
940, 917, 925, 932, 936, 922 - Internet Subnets Protocol |
| 518 |
925, 917, 826 - Multi-LAN Address Resolution Protocol |
| 519 |
919, 922 - Broadcasting Internet Datagrams |
| 520 |
891 - DCN Local-Network Protocols |
| 521 |
871 - A Perspective on the ARPANET Reference Model |
| 522 |
831 - Backup Access to the European Side of SATNET |
| 523 |
817 - Modularity and Efficiency in Protocol Implementation |
| 524 |
816 - Fault Isolation and Recovery |
| 525 |
814 - Name, Addresses, Ports, and Routes |
| 526 |
796 - Address Mapping |
| 527 |
795 - Service Mappings |
| 528 |
730 - Extensible Field Addressing |
| 529 |
|
| 530 |
4. Host Level |
| 531 |
|
| 532 |
4a. User Datagram Protocol |
| 533 |
|
| 534 |
768 - User Datagram Protocol |
| 535 |
|
| 536 |
4b. Transmission Control Protocol |
| 537 |
|
| 538 |
983 - ISO Transport Services on Top of the TCP |
| 539 |
964 - Some Problems with the Specification of the Military |
| 540 |
Standard Transmission Control Protocol |
| 541 |
896 - Congestion Control in IP/TCP Internetworks |
| 542 |
889 - Internet Delay Experiments |
| 543 |
879 - The TCP Maximum Segment Size and Related Topics |
| 544 |
872 - TCP-ON-A-LAN |
| 545 |
817 - Modularity and Efficiency in Protocol Implementation |
| 546 |
816 - Fault Isolation and Recovery |
| 547 |
814 - Name, Addresses, Ports, and Routes |
| 548 |
794 - Pre-Emption |
| 549 |
793, 761, 675 - Transmission Control Protocol |
| 550 |
721 - Out of Band Control Signals in a Host to Host Protocol |
| 551 |
700 - A Protocol Experiment |
| 552 |
|
| 553 |
4c. Transaction Protocols and Distributed Operating Systems |
| 554 |
|
| 555 |
955 - Towards a Transport Service for Transaction Processing |
| 556 |
Applications |
| 557 |
|
| 558 |
|
| 559 |
<span class="grey">Reynolds & Postel [Page 10]</span></pre> |
| 560 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 561 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 562 |
|
| 563 |
|
| 564 |
938 - Internet Reliable Transaction Protocol Functional and |
| 565 |
Interface Specification |
| 566 |
908 - Reliable Data Protocol |
| 567 |
722 - Thoughts on Interactions in Distributed Services |
| 568 |
713 - MSDTP -- Message Services Data Transmission Protocol |
| 569 |
712 - A Distributed Capability Computing System DCCS |
| 570 |
708 - Elements of a Distributed Programming System |
| 571 |
707 - A High-Level Framework for Network-Based Resource Sharing |
| 572 |
684 - A Commentary on Procedure Calling as A Network Protocol |
| 573 |
677 - The Maintenance of Duplicate Databases |
| 574 |
674 - Procedure Call Documents--Version 2 |
| 575 |
672 - A Multi-Site Data Collection Facility |
| 576 |
671 - A Note on Reconnection Protocol |
| 577 |
645 - Network Standard Data Specification Syntax |
| 578 |
615 - Proposed Network Standard Data Pathname Syntax |
| 579 |
610 - Further Datalanguage Design Concepts |
| 580 |
592 - Some Thoughts on System Design to Facilitate Resource |
| 581 |
Sharing |
| 582 |
578 - Using MIT-MATHLAB MACSYMA From MIT-DMS Muddle - An |
| 583 |
Experiment in Automated Resource Sharing |
| 584 |
515 - Specifications for Datalanguage, Version 0/9 |
| 585 |
500 - The Integration of Data Management Systems on a Computer |
| 586 |
Network |
| 587 |
441 - Inter-Entity Communication - An Experiment |
| 588 |
437 - Data Reconfiguration Service at UCSB |
| 589 |
203 - Achieving Reliable Communication |
| 590 |
076 - Connection-by-Name: User-Oriented Protocol |
| 591 |
062 - A System for Interprocess Communication in a Resource |
| 592 |
Sharing Computer Network |
| 593 |
061 - A Note on Interprocess Communication in a Resource |
| 594 |
Sharing Computer Network |
| 595 |
051 - Proposal for a Network Interchange Language |
| 596 |
031 - Binary Message Forms in Computer Networks |
| 597 |
005 - DEL |
| 598 |
001 - Host Software |
| 599 |
|
| 600 |
4d. Other |
| 601 |
|
| 602 |
998, 969 - NETBLT: A Bulk Data Transfer Protocol |
| 603 |
988 - Host Extensions for IP Multicasting |
| 604 |
979 - PSN End-to-End Functional Specification |
| 605 |
966 - A Multicast Extension to the Internet Protocol |
| 606 |
869 - Host Monitoring Protocol |
| 607 |
741 - Specifications for the Network Voice Protocol NVP |
| 608 |
643 - Cross Net Debugger |
| 609 |
162 - NETBUGGER3 |
| 610 |
|
| 611 |
|
| 612 |
|
| 613 |
|
| 614 |
|
| 615 |
<span class="grey">Reynolds & Postel [Page 11]</span></pre> |
| 616 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 617 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 618 |
|
| 619 |
|
| 620 |
5. Application Level |
| 621 |
|
| 622 |
5a. Telnet Protocol |
| 623 |
|
| 624 |
854, 764 - Telnet Protocol Specification |
| 625 |
818 - The Remote User Telnet Service |
| 626 |
801 - NCP/TCP Transition Plan |
| 627 |
782 - A Virtual Terminal Management Model |
| 628 |
764 - Telnet Protocol Specification |
| 629 |
728 - A Minor Pitfall in the Telnet Protocol |
| 630 |
688 - Tentative Schedule for the New Telnet Implementation for |
| 631 |
the TIP |
| 632 |
681 - Network Unix |
| 633 |
600 - Interfacing an Illinois Plasma Terminal to the ARPANET |
| 634 |
596 - Second Thoughts on Telnet Go-Ahead |
| 635 |
595 - Some Thoughts in Defense of the Telnet Go-Ahead |
| 636 |
593 - Telnet and FTP Implementation Schedule Change |
| 637 |
576 - Proposal for Modifying Linking |
| 638 |
570 - Experimental Input Mapping Between NVT ASCII and UCSB |
| 639 |
Online System |
| 640 |
562 - Modifications to the Telnet Specification |
| 641 |
559 - Comments on the New Telnet Protocol and Its |
| 642 |
Implementation |
| 643 |
529 - A Note on Protocol Synch Sequences |
| 644 |
513 - Comments on the New Telnet Specifications |
| 645 |
495 - Telnet Protocol Specification |
| 646 |
466 - Telnet Logger/Server for Host LL-67 |
| 647 |
461 - Telnet Meeting Announcement |
| 648 |
452 - Telnet Command at Host LL |
| 649 |
435 - Telnet Issues |
| 650 |
426 - Reconnection Protocol |
| 651 |
393 - Comments on Telnet Protocol Changes |
| 652 |
377 - Using TSO Via ARPA Network Virtual Terminal |
| 653 |
357 - An Echoing Strategy for Satellite Links |
| 654 |
355, 346 - Satellite Considerations |
| 655 |
340 - Proposed Telnet Changes |
| 656 |
339 - MLTNET - A "Multi-Telnet" Subsystem for TENEX |
| 657 |
328 - Suggested Telnet Protocol Changes |
| 658 |
318 - Ad Hoc Telnet Protocol |
| 659 |
216 - Telnet Access to UCSB's On-Line System |
| 660 |
215 - NCP, ICP, and Telnet: The Terminal IMP Implementation |
| 661 |
206 - A User Telnet Description of an Initial Implementation |
| 662 |
205 - NETCRT - A Character Display Protocol |
| 663 |
190 - DEC PDP-10 - IMLAC Communication System |
| 664 |
158 - Proposed Telnet Protocol |
| 665 |
139 - Discussion of Telnet Protocol |
| 666 |
137 - Telnet Protocol - A Proposed Document |
| 667 |
135, 110 - Conventions for Using an IBM 2741 Terminal as a User |
| 668 |
Console for Access to Network Server Hosts |
| 669 |
|
| 670 |
|
| 671 |
<span class="grey">Reynolds & Postel [Page 12]</span></pre> |
| 672 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 673 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 674 |
|
| 675 |
|
| 676 |
103 - Implementation of Interrupt Keys |
| 677 |
097 - A First Cut at a Proposed Telnet Protocol |
| 678 |
091 - A Proposed User-User Protocol |
| 679 |
015 - Network Subsystem for Time Sharing Hosts |
| 680 |
|
| 681 |
5b. Telnet Options |
| 682 |
|
| 683 |
946 - Telnet Terminal Location Number Option |
| 684 |
933 - Output Marking Telnet Option |
| 685 |
930 - Telnet Terminal Type Option |
| 686 |
927 - TACACS User Identification Telnet Option |
| 687 |
885 - Telnet End of Record Option |
| 688 |
884 - Telnet Terminal Type Option |
| 689 |
861 - Telnet Extended Options - List Option |
| 690 |
860 - Telnet Timing Mark Option |
| 691 |
859 - Telnet Status Option |
| 692 |
858 - Telnet Suppress Go Ahead Option |
| 693 |
857 - Telnet Echo Option |
| 694 |
856 - Telnet Binary Transmission |
| 695 |
855 - Telnet Option Specifications |
| 696 |
854 - Telnet Protocol Specifications |
| 697 |
779 - Telnet Send-Location Option |
| 698 |
749 - Telnet SUPDUP-OUTPUT Option |
| 699 |
748 - Telnet Randomly-Lose Option |
| 700 |
736 - Telnet SUPDUP Option |
| 701 |
735 - Revised Telnet Byte Macro Option |
| 702 |
734 - SUPDUP Protocol |
| 703 |
747 - Recent Extensions to the SUPDUP Protocol |
| 704 |
746 - The SUPDUP Graphics Extension |
| 705 |
732 - Telnet Data Entry Terminal Option |
| 706 |
731 - Telnet Data Entry Terminal Option |
| 707 |
729 - Telnet Byte Macro Option |
| 708 |
727 - Telnet Logout Option |
| 709 |
726 - Remote Controlled Transmission and Echoing Telnet Option |
| 710 |
719 - Discussion on RCTE |
| 711 |
718 - Comments on RCTE from the Tenex Implementation Experience |
| 712 |
703, 702, 701 - Survey of New-Protocol Telnet Servers |
| 713 |
698 - Telnet Extended ASCII Option |
| 714 |
679 - February, 1975, Survey of New-Protocol Telnet Servers |
| 715 |
669 - November 1974, Survey of New-Protocol Telnet Servers |
| 716 |
659 - Announcing Additional Telnet Options |
| 717 |
658 - Telnet Output Line Feed Disposition |
| 718 |
657 - Telnet Output Vertical Tab Disposition Option |
| 719 |
656 - Telnet Output Vertical Tab Stops Option |
| 720 |
655 - Telnet Output Form Feed Disposition Option |
| 721 |
654 - Telnet Output Horizontal Tab Disposition Option |
| 722 |
653 - Telnet Output Horizontal Tab Stops Option |
| 723 |
652 - Telnet Output Carriage Return Disposition Option |
| 724 |
651 - Revised Telnet Status Option |
| 725 |
|
| 726 |
|
| 727 |
<span class="grey">Reynolds & Postel [Page 13]</span></pre> |
| 728 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 729 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 730 |
|
| 731 |
|
| 732 |
587 - Announcing New Telnet Options |
| 733 |
581 - Corrections to <a href="./rfc560">RFC 560</a> - Remote Controlled Transmission |
| 734 |
and Echoing Telnet Option |
| 735 |
563 - Comments on the RCTE Telnet Option |
| 736 |
560 - Remote Controlled Transmission and Echoing Telnet Option |
| 737 |
|
| 738 |
5c. File Transfer Protocol |
| 739 |
|
| 740 |
987 - Mapping Between X.400 and <a href="./rfc822">RFC 822</a> |
| 741 |
959, 542, 354, 265, 172, 114 - The File Transfer Protocol |
| 742 |
949 - FTP Unique-Named Store Command |
| 743 |
913 - Simple File Transfer Protocol |
| 744 |
906 - Bootstrap Loading Using TFTP |
| 745 |
822 - Standard for the Format of ARPA Internet Text Messages |
| 746 |
821, 788 - Simple Mail Transfer Protocol |
| 747 |
783, 768, 764 - The TFTP Protocol Revision 2 |
| 748 |
775 - Directory Oriented FTP Commands |
| 749 |
743 - FTP Extension: XRSQ/XRCP |
| 750 |
737 - FTP Extension: XSEN |
| 751 |
697 - CWD Command of FTP |
| 752 |
691 - One More Try on the FTP |
| 753 |
686 - Leaving Well Enough Alone |
| 754 |
683 - FTPSRV -- Tenex Extension for Paged Files |
| 755 |
678 - Document File Format Standards |
| 756 |
662 - Performance Improvement in ARPANET File Transfers from |
| 757 |
Multics |
| 758 |
640 - Revised FTP Reply Codes |
| 759 |
630 - FTP Error Code Usage for More Reliable Mail Service |
| 760 |
624 - Comments on the File Transfer Protocol |
| 761 |
614 - Response to <a href="./rfc607">RFC 607</a> - Comments on the FTP |
| 762 |
607 - NIC-21255 Comments on the File Transfer Protocol |
| 763 |
573 - Data and File Transfer - Some Measurement Results |
| 764 |
571 - Tenex FTP Problem |
| 765 |
535 - Comments on File Access Protocol |
| 766 |
532 - The UCSD-CC Server-FTP Facility |
| 767 |
520 - Memo to FTP Group (Proposal for File Access Protocol) |
| 768 |
506 - An FTP Command Naming Problem |
| 769 |
505 - Two Solutions to a File Transfer Access Problem |
| 770 |
501 - Un-Muddling "Free File Transfer" |
| 771 |
487 - Host-Dependent FTP Parameters |
| 772 |
486 - Data Transfer Revisited |
| 773 |
480 - Host-Dependent FTP Parameters |
| 774 |
479 - Use of FTP by the NIC Journal |
| 775 |
478 - FTP Server-Server Interaction - II |
| 776 |
475 - FTP and the Network Mail System |
| 777 |
468 - FTP Data Compression |
| 778 |
463 - FTP Comments and Response to <a href="./rfc430">RFC 430</a> |
| 779 |
458 - Mail Retrieval via FTP |
| 780 |
|
| 781 |
|
| 782 |
|
| 783 |
<span class="grey">Reynolds & Postel [Page 14]</span></pre> |
| 784 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 785 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 786 |
|
| 787 |
|
| 788 |
454 - File Transfer Protocol - Meeting Announcement and a New |
| 789 |
Proposed Document |
| 790 |
448 - Print Files in FTP |
| 791 |
438 - FTP Server-Server Interaction |
| 792 |
430 - Comments on File Transfer Protocol |
| 793 |
418 - Server File Transfer Under TSS/360 at NASA/Ames Research |
| 794 |
Center |
| 795 |
414 - File Transfer Protocols (FTP): Status and Further |
| 796 |
Comments |
| 797 |
412 - User FTP Documentation |
| 798 |
385 - Comments on the File Transfer Protocol (<a href="./rfc354">RFC 354</a>) |
| 799 |
310 - Another Look at Data and File Transfer Protocols |
| 800 |
294 - The Use of "Set Data Type" Transaction in the File |
| 801 |
Transfer Protocol |
| 802 |
281 - A Suggested Addition to File Transfer Protocol |
| 803 |
269 - Some Experience with File Transfer |
| 804 |
264, 171 - The Data Transfer Protocol |
| 805 |
250 - Some Thoughts on File Transfer |
| 806 |
242 - Data Descriptive Language for Shared Data |
| 807 |
238 - Comments on DTP and FTP Protocols |
| 808 |
163 - Data Transfer Protocols |
| 809 |
141 - Comments on <a href="./rfc114">RFC 114</a> (A File Transfer Protocol) |
| 810 |
133 - File Transfer and Error Recovery |
| 811 |
|
| 812 |
5d. Domain Name System |
| 813 |
|
| 814 |
974 - Mail Routing and the Domain System |
| 815 |
973 - Domain System Changes and Observations |
| 816 |
953, 811, 810 - HOSTNAME Protocol |
| 817 |
921, 897 - Domain Name System Implementation Schedule |
| 818 |
920 - Domain Requirements |
| 819 |
883 - Domain Names - Implementation and Specification |
| 820 |
882 - Domain Names - Concepts and Facilities |
| 821 |
881 - The Domain Names Plan and Schedule |
| 822 |
830 - A Distributed System for Internet Name Service |
| 823 |
819 - The Domain Naming Convention for Internet User |
| 824 |
Applications |
| 825 |
799 - Internet Name Domains |
| 826 |
756 - The NIC Name Server -- A Datagram-Based Information |
| 827 |
Utility |
| 828 |
752 - A Universal Host Table |
| 829 |
|
| 830 |
5e. Mail and Message Systems |
| 831 |
|
| 832 |
994, 983 - PCMAIL: A Distributed Mail System |
| 833 |
977 - Network News Transfer Protocol |
| 834 |
976 - UUCP Mail Interchange Format Standard |
| 835 |
974 - Mail Routing and the Domain System |
| 836 |
934 - Proposed Standard for Message Encapsulation |
| 837 |
|
| 838 |
|
| 839 |
<span class="grey">Reynolds & Postel [Page 15]</span></pre> |
| 840 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 841 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 842 |
|
| 843 |
|
| 844 |
915 - Network Mail Path Service |
| 845 |
886 - Proposed Standard for Message Header Munging |
| 846 |
850 - Standard for Interchange of USENET Messages |
| 847 |
841 - Specification for Message Format for Computer Based |
| 848 |
Message Systems |
| 849 |
822 - Standard for the Format of ARPA Internet Text Messages |
| 850 |
821 - Simple Mail Transfer Protocol |
| 851 |
806 - Specification for Message Format for Computer Based |
| 852 |
Message Systems |
| 853 |
780, 772 - Mail Transfer Protocol |
| 854 |
786 - Mail Transfer Protocol - ISI TOPS-20 MTP-NIMAIL Interface |
| 855 |
785 - Mail Transfer Protocol - ISI TOPS-20 File Definitions |
| 856 |
784 - Mail Transfer Protocol - ISI TOPS-20 Implementation |
| 857 |
771 - Mail Transition Plan |
| 858 |
763 - Role Mailboxes |
| 859 |
757 - A Suggested Solution to the Naming, Addressing, and |
| 860 |
Delivery Problem for ARPANET Message Systems |
| 861 |
754 - Out-of-Net Host Addresses for Mail |
| 862 |
753 - Internet Message Protocol |
| 863 |
751 - Survey of FTP Mail and MLFL |
| 864 |
733 - Standard for the Format of ARPA Network Text Messages |
| 865 |
724 - Proposed Official Standard for the Format of ARPA Network |
| 866 |
Messages |
| 867 |
720 - Address Specification Syntax for Network Mail |
| 868 |
706 - On the Junk Mail Problem |
| 869 |
680 - Message Transmission Protocol |
| 870 |
644 - On the Problem of Signature Authentication for Network |
| 871 |
Mail |
| 872 |
577 - Mail Priority |
| 873 |
574 - Announcement of a Mail Facility at UCSB |
| 874 |
561 - Standardizing Network Mail Headers |
| 875 |
555 - Responses to Critiques of the Proposed Mail Protocol |
| 876 |
539, 524 - A Proposed Mail Protocol |
| 877 |
498 - On Mail Service to CCN |
| 878 |
491 - What is "Free"? |
| 879 |
475 - On FTP and the Network Mail System |
| 880 |
458 - Mail Retrieval via FTP |
| 881 |
333 - A Proposed Experiment with a Message Switching Protocol |
| 882 |
278, 224, 221, 196 - A Mail Box Protocol |
| 883 |
|
| 884 |
5f. Facsimile and Bitmaps |
| 885 |
|
| 886 |
809 - UCL Facsimile System |
| 887 |
804 - Facsimile Formats |
| 888 |
803 - Dacom 450/500 Facsimile Date Transcoding |
| 889 |
798 - Decoding Facsimile Data From the Rapicom 450 |
| 890 |
797 - Bitmap Formats |
| 891 |
769 - Rapicom 450 Facimile File Format |
| 892 |
|
| 893 |
|
| 894 |
|
| 895 |
<span class="grey">Reynolds & Postel [Page 16]</span></pre> |
| 896 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 897 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 898 |
|
| 899 |
|
| 900 |
5g. Graphics |
| 901 |
|
| 902 |
965 - A Format for a Graphical Communication Protocol |
| 903 |
553 - Draft Design for a Text/Graphics Protocol |
| 904 |
493 - Graphics Protocol |
| 905 |
401 - Conversion of NGP-0 Coordinates to Device Specific |
| 906 |
Coordinates |
| 907 |
398 - UCSB Online Graphics |
| 908 |
387 - Some Experiences in Implementing Network Graphics |
| 909 |
Protocol Level 0 |
| 910 |
351 - Information Form for the ARPANET Graphics Resources |
| 911 |
Notebook |
| 912 |
336 - Level 0 Graphics Input Protocol |
| 913 |
296 - DS-1 Display System |
| 914 |
292 - Graphics Protocol - Level 0 only |
| 915 |
285 - Network Graphics |
| 916 |
268 - Graphics Facilities Information |
| 917 |
199 - Suggestions for a Network Data-Telnet Graphics Protocol |
| 918 |
192 - Some Factors Which a Network Graphics Protocol Must |
| 919 |
Consider |
| 920 |
191 - Graphics Implementation and Conceptualization at ARC |
| 921 |
186 - A Network Graphics Loader |
| 922 |
184 - Proposed Graphic Display Modes |
| 923 |
181, 177 - A Device Independent Graphical Display Description |
| 924 |
178 - Network Graphics Attention Handling |
| 925 |
125, 086 - Proposal for a Network Standard Format for a Data |
| 926 |
Stream to Control Graphics Display |
| 927 |
094 - Some Thoughts on Network Graphics |
| 928 |
|
| 929 |
5h. Data Management |
| 930 |
|
| 931 |
304 - A Data Management System Proposal for the ARPA Network |
| 932 |
195 - Data Computers - Data Descriptions and Access Language |
| 933 |
194 - The Data Reconfiguration Service - Compiler/Interpreter |
| 934 |
Implementation Notes |
| 935 |
166 - Data Reconfiguration Service - An Implementation |
| 936 |
Specification |
| 937 |
144 - Data Sharing on Computer Networks |
| 938 |
138 - Status Report on Proposed Data Reconfiguration Service |
| 939 |
083 - Language-Machine for Data Reconfiguration |
| 940 |
|
| 941 |
5i. Remote Job Entry |
| 942 |
|
| 943 |
740, 599, 589, 325, 189, 088 - CCN Network Remote Job Entry |
| 944 |
Program - NETRJS |
| 945 |
725 - An RJE Protocol for a Resource Sharing Network |
| 946 |
499 - Harvard's Network RJE |
| 947 |
490 - Surrogate RJS for UCLA-CCN |
| 948 |
477, 436 - Remote Job Service at UCSB |
| 949 |
|
| 950 |
|
| 951 |
<span class="grey">Reynolds & Postel [Page 17]</span></pre> |
| 952 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 953 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 954 |
|
| 955 |
|
| 956 |
407 - Remote Job Entry |
| 957 |
368 - Comments on "Proposed Remote Job Entry Protocol" |
| 958 |
360 - Proposed Remote Job Entry Protocol |
| 959 |
338 - EBCDIC/ASCII Mapping for Network RJE |
| 960 |
307 - Using Network Remote Job Entry |
| 961 |
283 - NETRJT - Remote Job Service Protocol for TIPS |
| 962 |
105 - Network Specification for Remote Job Entry and Remote Job |
| 963 |
Output Retrieval at UCSB |
| 964 |
|
| 965 |
5j. Time |
| 966 |
|
| 967 |
958, 957, 956 - Network Time Protocol |
| 968 |
868 - Time Server Protocol |
| 969 |
867 - Daytime Protocol |
| 970 |
778 - DCNET Time Server Protocol |
| 971 |
738 - Time Server |
| 972 |
685 - Response Time in Cross-network Debugging |
| 973 |
034 - Some Brief Preliminary Notes on the ARC Clock |
| 974 |
032 - Some Thoughts on SRI's Proposed Real Time Clock |
| 975 |
028 - Time Standards |
| 976 |
|
| 977 |
5k. Other |
| 978 |
|
| 979 |
978 - Voice File Interchange Protocol (VFIP) |
| 980 |
972 - Password Generator Protocol |
| 981 |
954, 812 - Whois Protocol |
| 982 |
951 - Bootstrap Protocol |
| 983 |
937, 918 - Post Office Protocol |
| 984 |
931, 912 - Authentication Service |
| 985 |
913 - Simple File Transfer Protocol |
| 986 |
909 - Loader Debugger Protocol |
| 987 |
891 - DCN Local Net Protocol |
| 988 |
887 - Resource Location Protocol |
| 989 |
866 - Active Users Protocol |
| 990 |
865 - Quote of the Day Protocol |
| 991 |
864 - Character Generator Protocol |
| 992 |
863, 361, 348 - Discard Protocol |
| 993 |
862, 361, 347 - Echo Protocol |
| 994 |
821, 822 - Simple Mail Transfer Protocol |
| 995 |
783 - Trivial File Transfer Protocol |
| 996 |
767 - Document Formats |
| 997 |
759 - Internet Message Protocol |
| 998 |
742 - Finger Protocol |
| 999 |
734 - SUPDUP Protocol |
| 1000 |
726 - Remote Controlled Transmission and Echoing Telnet Option |
| 1001 |
666 - Specification of the Unified User-Level Protocol |
| 1002 |
621 - NIC User Directories at SRI-ARC |
| 1003 |
569 - Network Standard Text Editor |
| 1004 |
470 - Change in Socket for TIP News Facility |
| 1005 |
|
| 1006 |
|
| 1007 |
<span class="grey">Reynolds & Postel [Page 18]</span></pre> |
| 1008 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1009 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 1010 |
|
| 1011 |
|
| 1012 |
451 - Tentative Proposal for a Unified User Level Protocol |
| 1013 |
098, 079 - Logger Protocol |
| 1014 |
029 - Note in Response to Bill English's Request for Comments |
| 1015 |
|
| 1016 |
6. Program Documentation |
| 1017 |
|
| 1018 |
6a. General |
| 1019 |
|
| 1020 |
496 - A TNLS Quick Reference Card is Available |
| 1021 |
494 - Availability of MIX and MIXAL in the Network |
| 1022 |
488 - NLS Classes at Network Sites |
| 1023 |
485 - MIS and MIXAL at UCSB |
| 1024 |
431 - Update on SMFS Login and Logout |
| 1025 |
411 - New Multics Network Software Features |
| 1026 |
409 - TENEX Interface to UCSB's Simple-Minded File System |
| 1027 |
399 - SMFS Login and Logout |
| 1028 |
390 - TSO Scenario Batch Compilation and Foreground Execution |
| 1029 |
382 - Mathematical Software on the ARPA Network |
| 1030 |
379 - Using TSO at CCN |
| 1031 |
373 - Arbitrary Character Sets |
| 1032 |
350 - User Accounts for UCSB On-Line System |
| 1033 |
345 - Interest Mixed Integer Programming (MPSX on 360/91 at |
| 1034 |
CCN) |
| 1035 |
321 - CBI Networking Activity at MITRE |
| 1036 |
317 - Official Host-Host Protocol Modification: Assigned Link |
| 1037 |
Numbers |
| 1038 |
311 - New Console Attachments to the UCSB Host |
| 1039 |
251 - Weather Data |
| 1040 |
223 - Network Information Center Schedule for Network Users |
| 1041 |
217 - Specification Changes for OLS, RJE/RJOR, and SMFS |
| 1042 |
174 - UCLA-Computer Science Graphics Overview |
| 1043 |
122 - Network Specifications for UCSB's Simple-Minded File |
| 1044 |
System |
| 1045 |
121 - Network On-Line Operators |
| 1046 |
120 - Network PL1 Subprograms |
| 1047 |
119 - Network FORTRAN Subprograms |
| 1048 |
074 - Specifications for Network Use of the UCSB On-Line System |
| 1049 |
|
| 1050 |
7. Network Specific |
| 1051 |
|
| 1052 |
7a. ARPANET |
| 1053 |
|
| 1054 |
878, 851, 802 - The ARPANET 1822L Host Access Protocol |
| 1055 |
852 - The ARPANET Short Blocking Feature |
| 1056 |
789 - Vulnerabilities of Network Control Protocols: An Example |
| 1057 |
716 - Interim Revision to <a href="#appendix-F">Appendix F</a> of BBN 1822 |
| 1058 |
704 - IMP/Host and Host/IMP Protocol Change |
| 1059 |
696 - Comments on the IMP/HOST and HOST/IMP Protocol Changes |
| 1060 |
695 - Official Change in Host-Host Protocol |
| 1061 |
|
| 1062 |
|
| 1063 |
<span class="grey">Reynolds & Postel [Page 19]</span></pre> |
| 1064 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1065 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 1066 |
|
| 1067 |
|
| 1068 |
692 - Comments on IMP/Host Protocol Changes |
| 1069 |
690 - Comments on the Proposed Host/IMP Protocol Changes |
| 1070 |
687 - IMP/Host and Host/IMP Protocol |
| 1071 |
667 - BBN Host Ports |
| 1072 |
660 - Some Changes to the IMP and the IMP/Host Interface |
| 1073 |
642 - Ready Line Philosophy and Implementation |
| 1074 |
638, 633 - IMP/TIP Preventive Maintenance Schedule |
| 1075 |
632 - Throughput Degradation for Single Packet Message |
| 1076 |
627 - ASCII Text File of Hostnames |
| 1077 |
626 - On a possible Lockup Condition in IMP Subnet due to |
| 1078 |
Message Sequencing |
| 1079 |
625 - On Line Hostnames Service |
| 1080 |
623 - Comments on On-line Host Name Service |
| 1081 |
622 - Scheduling IMP/TIP Down Time |
| 1082 |
620 - Request for Monitor Host Table Updates |
| 1083 |
619 - Mean Round-Trip Times in the ARPANET |
| 1084 |
613 - Network Connectivity: A Response to <a href="./rfc603">RFC 603</a> |
| 1085 |
611 - Two Changes to the IMP/Host Protocol |
| 1086 |
606 - Host Names On-Line |
| 1087 |
594 - Speedup of Host-IMP Interface |
| 1088 |
591 - Addition to the Very Distant Host Specification |
| 1089 |
568, 567 - Cross-Country Network Bandwidth |
| 1090 |
548 - Hosts Using the IMP Going Down Message Specification |
| 1091 |
547 - Change to the Very Distant Host Specification |
| 1092 |
533 - Message-ID Numbers |
| 1093 |
534 - Lost Message Detection |
| 1094 |
528 - Software Checksumming in the IMP and Network Reliability |
| 1095 |
521 - Restricted Use of IMP DDT |
| 1096 |
508 - Real-Time Data Transmission on the ARPANET |
| 1097 |
476, 434 - IMP/TIP Memory Retrofit Schedules |
| 1098 |
449, 442 - The Current Flow-Control Scheme for IMPSYS |
| 1099 |
447, 445 - IMP/TIP Preventive Maintenance Schedule |
| 1100 |
417 - LINK Usage Violation |
| 1101 |
410 - Removal of the 30-second Delay When Hosts Come Up |
| 1102 |
406 - Scheduled IMP Software Releases |
| 1103 |
395 - Switch Settings on IMPs and TIPs |
| 1104 |
394 - Two Proposed Changes to the IMP-HOST Protocol |
| 1105 |
369 - Evaluation of ARPANET Services (January through March, |
| 1106 |
1972) |
| 1107 |
335 - New Interface-IMP/360 |
| 1108 |
312 - Proposed Change in IMP-to-Host Protocol |
| 1109 |
297 - TIP Message Buffers |
| 1110 |
280 - A Draft Set of Host Names |
| 1111 |
274 - Establishing a Local Guide for Network Usage |
| 1112 |
271 - IMP System Change Notification |
| 1113 |
270 - Correction to the BBN Report No. 1822 |
| 1114 |
263 - "Very Distant" Host Interface |
| 1115 |
254 - Scenarios for Using ARPANET Computers |
| 1116 |
247 - Proffered Set of Standard Host Names |
| 1117 |
|
| 1118 |
|
| 1119 |
<span class="grey">Reynolds & Postel [Page 20]</span></pre> |
| 1120 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1121 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 1122 |
|
| 1123 |
|
| 1124 |
241 - Connecting Computers to NLC Ports |
| 1125 |
239 - Host Mnemonics Proposed in <a href="./rfc226">RFC 226</a> |
| 1126 |
237 - The NIC's View of Standard Host Names |
| 1127 |
236 - Standard Host Names |
| 1128 |
233 - Standardization of Host Call Letters |
| 1129 |
230 - Toward Reliable Operation of Minicomputer-based Terminals |
| 1130 |
on a TIP |
| 1131 |
229 - Standard Host Names |
| 1132 |
228 - Clarification |
| 1133 |
226 - Standardization of Host Mnemonics |
| 1134 |
218 - Changing the IMP Status Reporting |
| 1135 |
213 - IMP System Change Notification |
| 1136 |
209 - Host/IMP Interface Documentation |
| 1137 |
208 - Address Tables |
| 1138 |
073, 067 - Proposed Change to Host/IMP Spec to Eliminate |
| 1139 |
Marking |
| 1140 |
071 - Reallocation in Case of Input Error |
| 1141 |
070 - A Note On Padding |
| 1142 |
064 - Getting Rid of Marking |
| 1143 |
041 - IMP/IMP Teletype Communication |
| 1144 |
025 - No High Link Numbers |
| 1145 |
019 - Two Protocol Suggestions to Reduce Congestion at |
| 1146 |
Swap-Bound Nodes |
| 1147 |
017a, 017 - Some Questions Re: HOST-IMP Protocol |
| 1148 |
012 - IMP-HOST Interface Flow Diagrams |
| 1149 |
007 - HOST-IMP Interface |
| 1150 |
006 - Conversation with Bob Kahn |
| 1151 |
|
| 1152 |
7b. Internet Protocol On Networks |
| 1153 |
|
| 1154 |
948 - Two Methods for the Transmission of IP Datagrams Over |
| 1155 |
IEEE 802.3 Networks |
| 1156 |
907 - Host Access Protocol |
| 1157 |
903 - A Reverse Address Resolution Protocol |
| 1158 |
895 - A Standard for the Transmission of IP Datagrams over |
| 1159 |
Experimental Ethernet Networks |
| 1160 |
894 - A Standard for the Transmission of IP Datagrams over |
| 1161 |
Ethernet Networks |
| 1162 |
893 - Trailer Encapsulations |
| 1163 |
891 - Internet Protocol on DC Networks |
| 1164 |
877 - A Standard for the Transmission of IP Datagrams Over |
| 1165 |
Public Data Networks |
| 1166 |
826 - Address Resolution Protocol |
| 1167 |
796 - Address Mappings |
| 1168 |
795 - Service Mappings |
| 1169 |
|
| 1170 |
7c. Host Front End Protocols |
| 1171 |
|
| 1172 |
929, 928, 705, 647 - Host-Front End Protocol |
| 1173 |
|
| 1174 |
|
| 1175 |
<span class="grey">Reynolds & Postel [Page 21]</span></pre> |
| 1176 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1177 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 1178 |
|
| 1179 |
|
| 1180 |
7d. Other |
| 1181 |
|
| 1182 |
935 - Reliable Link Layer Protocols |
| 1183 |
916 - Reliable Asynchronous Transfer Protocol |
| 1184 |
914 - Thinwire Protocol |
| 1185 |
824 - The Cronus Virtual Local Network |
| 1186 |
|
| 1187 |
8. Measurement |
| 1188 |
|
| 1189 |
8a. General |
| 1190 |
|
| 1191 |
573 - Data and File Transfer - Some Measurement Results |
| 1192 |
557 - Revelations in Network Host Measurements |
| 1193 |
546 - Tenex Load Averages for July 1973 |
| 1194 |
462 - Responding to User Needs |
| 1195 |
415 - TENEX Bandwidth |
| 1196 |
392 - Measurement of Host Costs for Transmitting Network Data |
| 1197 |
352 - TIP Site Information Form |
| 1198 |
308 - ARPANET Host Availability Data |
| 1199 |
286 - Network Library Information System |
| 1200 |
274 - Establishing a Local Guide for Network Usage |
| 1201 |
214, 193 - Network Checkout |
| 1202 |
198 - Site Certification - Lincoln Labs |
| 1203 |
182 - Compilation of List of Revelant Site Reports |
| 1204 |
180 - File System Questionnaire |
| 1205 |
156 - Status of the Illinois Site (Response to <a href="./rfc116">RFC 116</a>) |
| 1206 |
153 - SRI ARC-NIC Status |
| 1207 |
152 - SRI Artificial Intelligence Status Report |
| 1208 |
126 - Ames Graphics Facilities at Ames Research Center |
| 1209 |
112 - User/Server Site Protocol Network HOST Questionnaire |
| 1210 |
104 - Link 191 |
| 1211 |
106 - USER/SERVER Site Protocol Network Host Questionnaire |
| 1212 |
|
| 1213 |
8b. Surveys |
| 1214 |
|
| 1215 |
971 - A Survey of Data Representation Standards |
| 1216 |
876 - Survey of SMTP Implementations |
| 1217 |
848 - Who Provides the "Little" TCP Services? |
| 1218 |
847 - Summary of Smallberg Surveys |
| 1219 |
844 - Who Talks ICMP, too? Survey of 18 February 1983 |
| 1220 |
846, 845, 843, 842, 839, 838, 837, 836, 835, 834, 833, 832 - |
| 1221 |
Who Talks TCP? |
| 1222 |
787 - Connectionless Data Transmission Survey/Tutorial |
| 1223 |
703, 702, 701, 679, 669 - Survey of New-Protocol Telnet Servers |
| 1224 |
565 - Storing Network Survey Data at the Datacomputer |
| 1225 |
545 - Of What Quality be the UCSB Resource Evaluators? |
| 1226 |
530 - A Report on the SURVEY Project |
| 1227 |
523 - SURVEY is in Operation Again |
| 1228 |
519 - Resource Evaluation |
| 1229 |
|
| 1230 |
|
| 1231 |
<span class="grey">Reynolds & Postel [Page 22]</span></pre> |
| 1232 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1233 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 1234 |
|
| 1235 |
|
| 1236 |
514 - Network Make-Work |
| 1237 |
464 - Resource Notebook Framework |
| 1238 |
460 - NCP Survey |
| 1239 |
459 - Network Questionnaire |
| 1240 |
450 - Multics Sampling Timeout Change |
| 1241 |
446 - Proposal to Consider a Network Program Resource Notebook |
| 1242 |
096 - An Interactive Network Experiment to Study Modes of |
| 1243 |
Access to the Network Information Center |
| 1244 |
090 - CCN as a Network Service Center |
| 1245 |
081 - Request for Reference Information |
| 1246 |
078 - NCP Status Report: UCSB/Rand |
| 1247 |
|
| 1248 |
8c. Statistics |
| 1249 |
|
| 1250 |
996 - Statistics Server |
| 1251 |
618 - A Few Observations on NCP Statistics |
| 1252 |
612, 601, 586, 579, 566, 556, 538, 522, 509, 497, 482, 455, |
| 1253 |
443, 422, 413, 400, 391, 378 - Traffic Statistics |
| 1254 |
603, 597, 376, 370, 367, 366, 362, 352, 344, 342, 332, 330, |
| 1255 |
326, 319, 315, 306, 298, 293, 288, 287, 267, 266 - |
| 1256 |
Network Host Status |
| 1257 |
550 - NIC NCP Experiment |
| 1258 |
388 - NCP Statistics |
| 1259 |
255, 252, 240, 235 - Site Status |
| 1260 |
|
| 1261 |
9. Network Experience and Demonstrations |
| 1262 |
|
| 1263 |
9a. General |
| 1264 |
|
| 1265 |
968 - 'Twas the Night Before Start-up |
| 1266 |
967 - All Victims Together |
| 1267 |
573 - Data and File Transfer - Some Measurement Results |
| 1268 |
527 - ARPAWOCKY |
| 1269 |
525 - MIT-Mathlab Meets UCSB-OLS |
| 1270 |
439 - PARRY Encounters the Doctor |
| 1271 |
420 - CCA ICC Weather Demo |
| 1272 |
372 - Notes on a Conversation with Bob Kahn on the ICCC |
| 1273 |
364 - Serving Remote Users on the ARPANET |
| 1274 |
302 - Excercising the ARPANET |
| 1275 |
231 - Service Center Standards for Remote Usage - A User's View |
| 1276 |
227 - Data Transfer Rates (RAND/UCLA) |
| 1277 |
113 - Network Activity Report: UCSB and Rand |
| 1278 |
089 - Some Historic Moments in Networking |
| 1279 |
004 - Network Timetable |
| 1280 |
|
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
|
| 1285 |
|
| 1286 |
|
| 1287 |
<span class="grey">Reynolds & Postel [Page 23]</span></pre> |
| 1288 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1289 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 1290 |
|
| 1291 |
|
| 1292 |
10. Site Documentation |
| 1293 |
|
| 1294 |
10a. General |
| 1295 |
|
| 1296 |
30, 27, 24, 16, 10, 3 - Documentation Conventions |
| 1297 |
|
| 1298 |
11. Other Standards |
| 1299 |
|
| 1300 |
11a. ANSI |
| 1301 |
|
| 1302 |
570 - Experimental Input Mapping Between NVT ASCII and UCSB |
| 1303 |
Online System |
| 1304 |
183 - The EBCDIC Codes and Their Mapping to ASCII |
| 1305 |
020 - ASCII Format for Network Interchange |
| 1306 |
|
| 1307 |
11b. CCITT |
| 1308 |
|
| 1309 |
987 - Mapping Between X.400 and <a href="./rfc822">RFC 822</a> |
| 1310 |
874 - A Critique of X.25 |
| 1311 |
|
| 1312 |
11c. NRC |
| 1313 |
|
| 1314 |
942 - Transport Protocols for Department of Defense Data |
| 1315 |
Networks |
| 1316 |
939 - Executive Summary of the NRC Report on Transport |
| 1317 |
Protocols for Department of Defense Data Networks |
| 1318 |
|
| 1319 |
11d. ISO |
| 1320 |
|
| 1321 |
995 - End System to Intermediate System Routing Exchange |
| 1322 |
Protocol for Use in Conjunction with ISO 8473 |
| 1323 |
994 - Final Text of DIS 8473, Protocol for Providing the |
| 1324 |
Connectionless Mode Network Service |
| 1325 |
982 - Guidelines for the Specification of the Structure of the |
| 1326 |
Domain Specific Part (DSP) of the ISO Standard NSAP |
| 1327 |
Address |
| 1328 |
941 - Addendum to the Network Service Definition Covering |
| 1329 |
Network Layer Addressing |
| 1330 |
926 - Protocol for Providing the Connectionless-Mode Network |
| 1331 |
Services |
| 1332 |
905 - ISO Transport Protocol Specification (ISO DP 8073) |
| 1333 |
892 - ISO Transport Protocol |
| 1334 |
873 - The Illusion of Vendor Support |
| 1335 |
|
| 1336 |
|
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
|
| 1341 |
|
| 1342 |
|
| 1343 |
<span class="grey">Reynolds & Postel [Page 24]</span></pre> |
| 1344 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1345 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 1346 |
|
| 1347 |
|
| 1348 |
12. Never Issued |
| 1349 |
|
| 1350 |
12a. Never Issued |
| 1351 |
|
| 1352 |
014, 026, 092, 159, 201, 220, 244, 248, 257, 258, 259, 260, |
| 1353 |
261, 262, 272, 275, 277, 279, 284, 337, 341, 358, 375, 380, |
| 1354 |
383, 397, 424, 427, 428, 444, 465, 481, 484, 502, 507, 517, |
| 1355 |
536, 540, 541, 554, 558, 564, 572, 575, 583, 605, 639, 641, |
| 1356 |
646, 648, 649, 650, 664, 665, 668, 670, 673, 676, 682, 693, |
| 1357 |
709, 710, 711, 715, 723, 853. |
| 1358 |
|
| 1359 |
|
| 1360 |
|
| 1361 |
|
| 1362 |
|
| 1363 |
|
| 1364 |
|
| 1365 |
|
| 1366 |
|
| 1367 |
|
| 1368 |
|
| 1369 |
|
| 1370 |
|
| 1371 |
|
| 1372 |
|
| 1373 |
|
| 1374 |
|
| 1375 |
|
| 1376 |
|
| 1377 |
|
| 1378 |
|
| 1379 |
|
| 1380 |
|
| 1381 |
|
| 1382 |
|
| 1383 |
|
| 1384 |
|
| 1385 |
|
| 1386 |
|
| 1387 |
|
| 1388 |
|
| 1389 |
|
| 1390 |
|
| 1391 |
|
| 1392 |
|
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
|
| 1397 |
|
| 1398 |
|
| 1399 |
<span class="grey">Reynolds & Postel [Page 25]</span></pre> |
| 1400 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1401 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 1402 |
|
| 1403 |
|
| 1404 |
REQUEST FOR COMMENTS LIST WITH ABSTRACTS |
| 1405 |
|
| 1406 |
RFC Author Date Title |
| 1407 |
--- ------ ---- ----- |
| 1408 |
|
| 1409 |
999 Westine Mar 87 Requests For Comments Summary |
| 1410 |
|
| 1411 |
A summary of the Request for Comments Documents from <a href="./rfc900">RFC 900</a>-999. |
| 1412 |
|
| 1413 |
998 Lambert Mar 87 NETBLT: A Bulk Data Transfer |
| 1414 |
Protocol |
| 1415 |
|
| 1416 |
This document is a description of and a specification for the |
| 1417 |
NETBLT protocol. It is a revision of the specification published |
| 1418 |
in <a href="./rfc969">RFC-969</a>. NETBLT (NETwork BLock Transfer) is a transport level |
| 1419 |
protocol intended for the rapid transfer of a large quantity of |
| 1420 |
data between computers. It provides a transfer that is reliable |
| 1421 |
and flow controlled, and is designed to provide maximum throughput |
| 1422 |
over a wide variety of networks. Although NETBLT currently runs |
| 1423 |
on top of the Internet Protocol (IP), it should be able to operate |
| 1424 |
on top of any datagram protocol similar in function to IP. |
| 1425 |
|
| 1426 |
This document is published for discussion and comment, and does |
| 1427 |
not constitute a standard. The proposal may change and certain |
| 1428 |
parts of the protocol have not yet been specified; implementation |
| 1429 |
of this document is therefore not advised. |
| 1430 |
|
| 1431 |
997 Reynolds Mar 87 Internet Numbers |
| 1432 |
|
| 1433 |
This memo is an official status report on the network numbers used |
| 1434 |
in the Internet community. As of 1-Mar-87 the Network Information |
| 1435 |
Center (NIC) at SRI International has assumed responsibility for |
| 1436 |
assignment of Network Numbers and Autonomous System Numbers. This |
| 1437 |
RFC documents the current assignments of these numbers at the time |
| 1438 |
of this transfer of responsibility. |
| 1439 |
|
| 1440 |
996 Mills Feb 87 Statistics Server |
| 1441 |
|
| 1442 |
This RFC specifies a standard for the ARPA Internet community. |
| 1443 |
Hosts and gateways on the DARPA Internet that choose to implement |
| 1444 |
a remote statistics monitoring facility may use this protocol to |
| 1445 |
send statistics data upon request to a monitoring center or |
| 1446 |
debugging host. |
| 1447 |
|
| 1448 |
995 ANSI Apr 86 End System to Intermediate System |
| 1449 |
Routing Exchange Protocol for use in |
| 1450 |
conjunction with ISO 8473. |
| 1451 |
|
| 1452 |
This Protocol is one of a set of International Standards produced |
| 1453 |
|
| 1454 |
|
| 1455 |
<span class="grey">Reynolds & Postel [Page 26]</span></pre> |
| 1456 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1457 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 1458 |
|
| 1459 |
|
| 1460 |
to facilitate the interconnection of open systems. The set of |
| 1461 |
standards covers the services and protocols required to achieve |
| 1462 |
such interconnection. |
| 1463 |
|
| 1464 |
This Protocol is positioned with respect to other related |
| 1465 |
standards by the layers defined in the Reference Model for Open |
| 1466 |
Systems Interconnection (ISO 7498) and by the structure defined in |
| 1467 |
the Internal Organization of the Network Layer (DIS 8648). In |
| 1468 |
particular, it is a protocol of the Network Layer. This Protocol |
| 1469 |
permits End Systems and Intermediate Systems to exchange |
| 1470 |
configuration and routing information to facilitate the operation |
| 1471 |
of the routing and relaying functions of the Network Layer. |
| 1472 |
|
| 1473 |
994 ANSI Mar 86 Final Text of DIS 8473, Protocol for |
| 1474 |
Providing the Connectionless Mode |
| 1475 |
Network Service |
| 1476 |
|
| 1477 |
This Protocol Standard is one of a set of International Standards |
| 1478 |
produced to facilitate the interconnection of open systems. The |
| 1479 |
set of standards covers the services and protocols required to |
| 1480 |
achieve such interconnection. |
| 1481 |
|
| 1482 |
This Protocol Standard is positioned with respect to other related |
| 1483 |
standards by the layers defined in the Reference Model for Open |
| 1484 |
Systems Interconnection (ISO 7498). In particular, it is a |
| 1485 |
protocol of the Network Layer. This Protocol may be used between |
| 1486 |
network-entities in end systems or in Network Layer relay systems |
| 1487 |
(or both). It provides the Connectionless-mode Network Service as |
| 1488 |
defined in Addendum 1 to the Network Service Definition Covering |
| 1489 |
Connectionless-mode Transmission (ISO 8348/AD1). |
| 1490 |
|
| 1491 |
993 Clark Dec 86 PCMAIL: A Distributed Mail System |
| 1492 |
for Personal Computers |
| 1493 |
|
| 1494 |
This document is a discussion of the PCMAIL workstation-based |
| 1495 |
distributed mail system. It is a revision of the design published |
| 1496 |
in NIC <a href="./rfc984">RFC 984</a>. The revision is based on discussion and comments |
| 1497 |
from a variety of sources, as well as further research into the |
| 1498 |
design of interactive PCMAIL clients and the use of client code on |
| 1499 |
machines other than IBM PCs. As this design may change, |
| 1500 |
implementation of this document is not advised. |
| 1501 |
|
| 1502 |
992 Birman Nov 86 On Communication Support for |
| 1503 |
Fault-Tolerant Process Groups |
| 1504 |
|
| 1505 |
This memo describes a collection of multicast communication |
| 1506 |
primitives integrated with a mechanism for handling process |
| 1507 |
failure and recovery. These primitives facilitate the |
| 1508 |
implementation of fault-tolerant process groups, which can be used |
| 1509 |
|
| 1510 |
|
| 1511 |
<span class="grey">Reynolds & Postel [Page 27]</span></pre> |
| 1512 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1513 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 1514 |
|
| 1515 |
|
| 1516 |
to provide distributed services in an environment subject to |
| 1517 |
non-malicious crash failures. |
| 1518 |
|
| 1519 |
Here, we argue that the form of "best effort" reliability provided |
| 1520 |
by host groups may not address the requirements of those |
| 1521 |
researchers who are building fault tolerant software. Our basic |
| 1522 |
premise is that reliable handling of failures, recoveries, and |
| 1523 |
dynamic process migration are important aspects of programming in |
| 1524 |
distributed environments, and that communication support that |
| 1525 |
provides unpredictable behavior in the presence of such events |
| 1526 |
places an unacceptable burden of complexity on higher level |
| 1527 |
application software. This complexity does not arise when using |
| 1528 |
the fault-tolerant process group alternative. |
| 1529 |
|
| 1530 |
991 Reynolds Nov 86 Official ARPA-Internet Protocols |
| 1531 |
|
| 1532 |
This RFC identifies the documents specifying the official |
| 1533 |
protocols used in the Internet. Comments indicate any revisions |
| 1534 |
or changes planned. This memo is an official status report on the |
| 1535 |
numbers used in protocols in the ARPA-Internet community. This |
| 1536 |
memo obsoletes RFCs 961, 944, 924, 901, 880, 840, 694, 661, 617, |
| 1537 |
582, 580, 552. |
| 1538 |
|
| 1539 |
990 Reynolds Nov 86 Assigned Numbers |
| 1540 |
|
| 1541 |
This Network Working Group Request for Comments documents the |
| 1542 |
currently assigned values from several series of numbers used in |
| 1543 |
network protocol implementations. This memo is an official status |
| 1544 |
report on the numbers used in protocols in the ARPA-Internet |
| 1545 |
community. This memo obsoletes RFCs 960, 943, 923, 900, 870, 820, |
| 1546 |
790, 776, 770, 762, 758, 755, 750, 739, 717, 604, 503, 433, 349, |
| 1547 |
322, 317, 204, 179, 175, 167. |
| 1548 |
|
| 1549 |
989 Linn Feb 87 Privacy Enhancement for Internet |
| 1550 |
Electronic Mail: Part I: Message |
| 1551 |
Encipherment and Authentication |
| 1552 |
Procedures |
| 1553 |
|
| 1554 |
This RFC suggests a proposed protocol for the Internet community |
| 1555 |
and requests discussion and suggestions for improvements. This |
| 1556 |
RFC is the outgrowth of a series of IAB Privacy Task Force |
| 1557 |
meetings and of internal working papers distributed for those |
| 1558 |
meetings. This RFC defines message encipherment and |
| 1559 |
authentication procedures, as the initial phase of an effort to |
| 1560 |
provide privacy enhancement services for electronic mail transfer |
| 1561 |
in the Internet. It is intended that the procedures defined here |
| 1562 |
be compatible with a wide range of key management approaches, |
| 1563 |
including both conventional (symmetric) and public-key |
| 1564 |
(asymmetric) approaches for encryption of data encrypting keys. |
| 1565 |
|
| 1566 |
|
| 1567 |
<span class="grey">Reynolds & Postel [Page 28]</span></pre> |
| 1568 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1569 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 1570 |
|
| 1571 |
|
| 1572 |
Use of conventional cryptography for message text encryption |
| 1573 |
and/or authentication is anticipated. |
| 1574 |
|
| 1575 |
Privacy enhancement services (confidentiality, authentication, and |
| 1576 |
message integrity assurance) are offered through the use of |
| 1577 |
end-to- end cryptography between originator and recipient User |
| 1578 |
Agent processes, with no special processing requirements imposed |
| 1579 |
on the Message Transfer System at endpoints or at intermediate |
| 1580 |
relay sites. This approach allows privacy enhancement facilities |
| 1581 |
to be incorporated on a site-by-site or user-by-user basis without |
| 1582 |
impact on other Internet entities. Interoperability among |
| 1583 |
heterogeneous components and mail transport facilities is |
| 1584 |
supported. |
| 1585 |
|
| 1586 |
988 Deering Jul 86 Host Extensions for IP Multicasting |
| 1587 |
|
| 1588 |
This memo specifies the extensions required of a host |
| 1589 |
implementation of the Internet Protocol (IP) to support |
| 1590 |
internetwork multicasting. This specification supersedes that |
| 1591 |
given in <a href="./rfc966">RFC 966</a>, and constitutes a proposed protocol standard for |
| 1592 |
IP multicasting in the ARPA-Internet. The reader is directed to |
| 1593 |
<a href="./rfc966">RFC 966</a> for a discussion of the motivation and rationale behind |
| 1594 |
the multicasting extension specified here. |
| 1595 |
|
| 1596 |
987 Kille Jun 86 Mapping Between X.400 and <a href="./rfc822">RFC 822</a> |
| 1597 |
|
| 1598 |
The X.400 series of protocols have been defined by CCITT to |
| 1599 |
provide an Interpersonal Messaging Service (IPMS), making use of a |
| 1600 |
store and forward Message Transfer Service. It is expected that |
| 1601 |
this standard will be implemented very widely. This document |
| 1602 |
describes a set of mappings which will enable interworking between |
| 1603 |
systems operating the X.400 protocols and systems using <a href="./rfc822">RFC 822</a> |
| 1604 |
mail protocol or protocols derived from <a href="./rfc822">RFC 822</a>. This RFC |
| 1605 |
suggests a proposed protocol for the ARPA-Internet community, and |
| 1606 |
requests discussion and suggestions for improvements. |
| 1607 |
|
| 1608 |
986 Callon Jun 86 Working Draft -- Guidelines for the |
| 1609 |
Use of Internet-IP addressing in the |
| 1610 |
ISO Connectionless-Mode Network |
| 1611 |
Protocol |
| 1612 |
|
| 1613 |
This RFC suggests a method to allow the existing IP addressing, |
| 1614 |
including the IP protocol field, to be used for the ISO |
| 1615 |
Connectionless Network Protocol (CLNP). This is a draft solution |
| 1616 |
to one of the problems inherent in the use of "ISO-grams" in the |
| 1617 |
DoD Internet. Related issues will be discussed in subsequent |
| 1618 |
RFCs. This RFC suggests a proposed protocol for the ARPA-Internet |
| 1619 |
community, and requests discussion and suggestions for |
| 1620 |
improvements. |
| 1621 |
|
| 1622 |
|
| 1623 |
<span class="grey">Reynolds & Postel [Page 29]</span></pre> |
| 1624 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1625 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 1626 |
|
| 1627 |
|
| 1628 |
985 Mills May 86 Requirements for Internet Gateways |
| 1629 |
|
| 1630 |
This RFC summarizes the requirements for gateways to be used on |
| 1631 |
networks supporting the DARPA Internet protocols. While it |
| 1632 |
applies specifically to the National Science Foundation research |
| 1633 |
programs, the requirements are stated in a general context and are |
| 1634 |
believed applicable throughout the Internet community. The |
| 1635 |
purpose of this document is to present guidance for vendors |
| 1636 |
offering products that might be used or adapted for use in an |
| 1637 |
Internet application. It enumerates the protocols required and |
| 1638 |
gives references to RFCs and other documents describing the |
| 1639 |
current specification. Suggestions and comments on this document |
| 1640 |
are welcomed and can be sent to Dave Mills ([email protected]) or |
| 1641 |
Dave Farber ([email protected]). |
| 1642 |
|
| 1643 |
984 Clark May 86 PCMAIL: A Distributed Mail System |
| 1644 |
for Personal Computers |
| 1645 |
|
| 1646 |
This document is a preliminary discussion of the design of a |
| 1647 |
personal-computer-based distributed mail system. Pcmail is a |
| 1648 |
distributed mail system that provides mail service to an arbitrary |
| 1649 |
number of users, each of which owns one or more personal computers |
| 1650 |
(PCs). The system is divided into two halves. The first consists |
| 1651 |
of a single entity called the "repository". The repository is a |
| 1652 |
storage center for incoming mail. Mail for a Pcmail user can |
| 1653 |
arrive externally from the Internet or internally from other |
| 1654 |
repository users. The repository also maintains a stable copy of |
| 1655 |
each user's mail state. The repository is therefore typically a |
| 1656 |
computer with a large amount of disk storage. It is published for |
| 1657 |
discussion and comment, and does not constitute a standard. As |
| 1658 |
the proposal may change, implementation of this document is not |
| 1659 |
advised. |
| 1660 |
|
| 1661 |
983 Cass Apr 86 ISO Transport Services on Top of the |
| 1662 |
TCP |
| 1663 |
|
| 1664 |
This memo describes a proposed protocol standard for the |
| 1665 |
ARPA-Internet community. The CCITT and the ISO have defined |
| 1666 |
various session, presentation, and application recommendations |
| 1667 |
which have been adopted by the international community and |
| 1668 |
numerous vendors. To the largest extent possible, it is desirable |
| 1669 |
to offer these higher level services directly to the |
| 1670 |
ARPA-Internet, without disrupting existing facilities. This |
| 1671 |
permits users to develop expertise with ISO and CCITT applications |
| 1672 |
which previously were not available in the ARPA-Internet. The |
| 1673 |
intention is that hosts within the ARPA-Internet that choose to |
| 1674 |
implement ISO TSAP services on top of the TCP be expected to adopt |
| 1675 |
and implement this standard. Suggestions for improvement are |
| 1676 |
encouraged. |
| 1677 |
|
| 1678 |
|
| 1679 |
<span class="grey">Reynolds & Postel [Page 30]</span></pre> |
| 1680 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1681 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 1682 |
|
| 1683 |
|
| 1684 |
982 ANSI Apr 86 Guidelines for the Specification of |
| 1685 |
the Structure of the Domain Specific |
| 1686 |
Part (DSP) of the ISO Standard NSAP |
| 1687 |
Address |
| 1688 |
|
| 1689 |
This RFC is a draft working document of the ANSI "Guidelines for |
| 1690 |
the Specification of the Structure of the Domain Specific Part |
| 1691 |
(DSP) of the ISO Standard NSAP Address". It provides guidance to |
| 1692 |
private address administration authorities on preferred formats |
| 1693 |
and semantics for the Domain Specific Part (DSP) of an NSAP |
| 1694 |
address. This RFC specifies the way in which the DSP may be |
| 1695 |
constructed so as to facilitate efficient address assignment. |
| 1696 |
This RFC is for informational purposes only and its distribution |
| 1697 |
is unlimited and does not specify a standard of the ARPA-Internet. |
| 1698 |
|
| 1699 |
981 Mills Mar 86 An Experimental Multiple-Path |
| 1700 |
Routing Algorithm |
| 1701 |
|
| 1702 |
This document introduces wiretap algorithms, a class of |
| 1703 |
experimental, multiple routing algorithms that compute |
| 1704 |
quasi-optimum routes for stations sharing a packet-radio broadcast |
| 1705 |
channel. The primary route (a minimum-distance path), and |
| 1706 |
additional paths ordered by distance, which serve as alternate |
| 1707 |
routes should the primary route fail, are computed. This |
| 1708 |
prototype is presented as an example of a class of routing |
| 1709 |
algorithms and data-base management techniques that may find wider |
| 1710 |
application in the Internet community. Discussions and |
| 1711 |
suggestions for improvements are welcomed. |
| 1712 |
|
| 1713 |
980 Jacobsen Mar 86 Protocol Document Order Information |
| 1714 |
|
| 1715 |
This RFC indicates how to obtain various protocol documents used |
| 1716 |
in the DARPA research community. Included is an overview of the |
| 1717 |
new 1985 DDN Protocol Handbook and available sources for obtaining |
| 1718 |
related documents (such as DOD, ISO, and CCITT). |
| 1719 |
|
| 1720 |
979 Malis Mar 86 PSN End-to-End Functional |
| 1721 |
Specification |
| 1722 |
|
| 1723 |
This memo is an updated version of BBN Report 5775, "End-to-End |
| 1724 |
Functional Specification". It describes important changes to the |
| 1725 |
functionality of the interface between a host and the PSN (Packet |
| 1726 |
Switch Node), and should be carefully reviewed by anyone involved |
| 1727 |
in supporting a host on either the ARPANET or MILNET. The new |
| 1728 |
End-to-End Protocol (EE) is being developed in order to correct a |
| 1729 |
number of deficiencies in the old End-to-End Protocol, to improve |
| 1730 |
its performance and overall throughput, and to better equip the |
| 1731 |
Packet Switch Node (also known as the IMP) to support its current |
| 1732 |
and anticipated host population. |
| 1733 |
|
| 1734 |
|
| 1735 |
<span class="grey">Reynolds & Postel [Page 31]</span></pre> |
| 1736 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1737 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 1738 |
|
| 1739 |
|
| 1740 |
978 Reynolds Feb 86 Voice File Interchange Protocol |
| 1741 |
(VFIP) |
| 1742 |
|
| 1743 |
The purpose of the Voice File Interchange Protocol (VFIP) is to |
| 1744 |
permit the interchange of various types of speech files between |
| 1745 |
different systems in the ARPA-Internet community. Suggestions for |
| 1746 |
improvement are encouraged. |
| 1747 |
|
| 1748 |
977 Kantor Feb 86 Network News Transfer Protocol |
| 1749 |
|
| 1750 |
NNTP specifies a protocol for the distribution, inquiry, |
| 1751 |
retrieval, and posting of news articles using a reliable |
| 1752 |
stream-based transmission of news among the ARPA-Internet |
| 1753 |
community. NNTP is designed so that news articles are stored in a |
| 1754 |
central database allowing a subscriber to select only those items |
| 1755 |
he wishes to read. Indexing, cross-referencing, and expiration of |
| 1756 |
aged messages are also provided. This RFC suggests a proposed |
| 1757 |
protocol for the ARPA-Internet community, and requests discussion |
| 1758 |
and suggestions for improvements. |
| 1759 |
|
| 1760 |
976 Horton Feb 86 UUCP Mail Interchange Format |
| 1761 |
Standard |
| 1762 |
|
| 1763 |
This document defines the standard format for the transmission of |
| 1764 |
mail messages between computers in the UUCP Project. It does not |
| 1765 |
however, address the format for storage of messages on one |
| 1766 |
machine, nor the lower level transport mechanisms used to get the |
| 1767 |
date from one machine to the next. It represents a standard for |
| 1768 |
conformance by hosts in the UUCP zone. |
| 1769 |
|
| 1770 |
975 Mills Feb 86 Autonomous Confederations |
| 1771 |
|
| 1772 |
This RFC proposes enhancements to the Exterior Gateway Protocol |
| 1773 |
(EGP) to support a simple, multiple-level routing capability while |
| 1774 |
preserving the robustness features of the current EGP model. The |
| 1775 |
enhancements generalize the concept of core system to include |
| 1776 |
multiple communities of autonomous systems, called autonomous |
| 1777 |
confederations. Discussion and suggestions for improvement are |
| 1778 |
requested. |
| 1779 |
|
| 1780 |
974 Partridge Jan 86 Mail Routing and the Domain System |
| 1781 |
|
| 1782 |
This RFC presents a description of how mail systems on the |
| 1783 |
Internet are expected to route messages based on information from |
| 1784 |
the domain system. This involves a discussion of how mailers |
| 1785 |
interpret MX RRs, which are used for message routing. |
| 1786 |
|
| 1787 |
|
| 1788 |
|
| 1789 |
|
| 1790 |
|
| 1791 |
<span class="grey">Reynolds & Postel [Page 32]</span></pre> |
| 1792 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span> |
| 1793 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 1794 |
|
| 1795 |
|
| 1796 |
973 Mockapetris Jan 86 Domain System Changes and |
| 1797 |
Observations |
| 1798 |
|
| 1799 |
This RFC documents updates to Domain Name System specifications |
| 1800 |
<a href="./rfc882">RFC-882</a> and <a href="./rfc883">RFC-883</a>, suggests some operational guidelines, and |
| 1801 |
discusses some experiences and problem areas in the present |
| 1802 |
system. |
| 1803 |
|
| 1804 |
972 Wancho Jan 86 Password Generator Protocol |
| 1805 |
|
| 1806 |
This RFC specifies a standard for the ARPA-Internet community. |
| 1807 |
The Password Generator Service (PWDGEN) provides a set of six |
| 1808 |
randomly generated eight-character "words" with a reasonable level |
| 1809 |
of pronounceability, using a multi-level algorithm. Hosts on the |
| 1810 |
ARPA-Internet that choose to implement a password generator |
| 1811 |
service are expected to adopt and implement this standard. |
| 1812 |
|
| 1813 |
971 DeSchon Dec 85 A Survey of Data Representation |
| 1814 |
Standards |
| 1815 |
|
| 1816 |
This RFC is a comparison of several data representation standards |
| 1817 |
that are currently in use. The standards discussed are the CCITT |
| 1818 |
X.409 recommendation, the NBS Computer Based Message System (CBMS) |
| 1819 |
standard, DARPA Multimedia Mail system, the Courier remote |
| 1820 |
procedure call protocol, and the SUN Remote Procedure Call |
| 1821 |
package. No proposals in this document are intended as standards |
| 1822 |
for the ARPA-Internet at this time. Rather, it is hoped that a |
| 1823 |
general consensus will emerge as to the appropriate approach to a |
| 1824 |
data representation standard, leading eventually to the adoption |
| 1825 |
of an ARPA-Internet standard. |
| 1826 |
|
| 1827 |
970 Nagle Dec 85 On Packet Switches With Infinite |
| 1828 |
Storage |
| 1829 |
|
| 1830 |
The purpose of this RFC is to focus discussion on a particular |
| 1831 |
problem in the ARPA-Internet and possible methods of solution. |
| 1832 |
Most prior work on congestion in datagram systems focuses on |
| 1833 |
buffer management. In this memo, the case of a packet switch with |
| 1834 |
infinite storage is considered. Such a packet switch can never |
| 1835 |
run out of buffers. It can, however, still become congested. The |
| 1836 |
meaning of congestion in an infinite-storage system is explored. |
| 1837 |
An unexpected result is found that shows a datagram network with |
| 1838 |
infinite storage, first-in-first-out queuing, at least two packet |
| 1839 |
switches, and a finite packet lifetime will, under overload, drop |
| 1840 |
all packets. By attacking the problem of congestion for the |
| 1841 |
infinite-storage case, new solutions applicable to switches with |
| 1842 |
finite storage may be found. No proposed solutions this document |
| 1843 |
are intended as standards for the ARPA-Internet at this time. |
| 1844 |
|
| 1845 |
|
| 1846 |
|
| 1847 |
<span class="grey">Reynolds & Postel [Page 33]</span></pre> |
| 1848 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span> |
| 1849 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 1850 |
|
| 1851 |
|
| 1852 |
969 Clark Dec 85 NETBLT: A Bulk Data Transfer |
| 1853 |
Protocol |
| 1854 |
|
| 1855 |
This RFC has been replaced by <a href="./rfc998">RFC 998</a>. This is a preliminary |
| 1856 |
discussion of the Network Block Transfer (NETBLT) protocol. |
| 1857 |
NETBLT is intended for the rapid transfer of a large quantity of |
| 1858 |
data between computers. It provides a transfer that is reliable |
| 1859 |
and flow controlled, and is structured to provide maximum |
| 1860 |
throughput over a wide variety of networks. This description is |
| 1861 |
published for discussion and comment, and does not constitute a |
| 1862 |
standard. As the proposal may change, implementation of this |
| 1863 |
document is not advised. |
| 1864 |
|
| 1865 |
968 Cerf Dec 85 'Twas the Night Before Start-up' |
| 1866 |
|
| 1867 |
This memo discusses problems that arise and debugging techniques |
| 1868 |
used in bringing a new network into operation. |
| 1869 |
|
| 1870 |
967 Padlipsky Dec 85 All Victims Together |
| 1871 |
|
| 1872 |
This RFC proposes a new set of RFCs on how the networking code is |
| 1873 |
integrated with various operating systems. It appears that this |
| 1874 |
topic has not received enough exposure in the literature. Comments |
| 1875 |
and suggestions are encouraged. |
| 1876 |
|
| 1877 |
966 Deering Dec 85 A Multicast Extension to the |
| 1878 |
Internet Protocol |
| 1879 |
|
| 1880 |
This RFC defines a model of service for Internet multicasting and |
| 1881 |
proposes an extension to the Internet Protocol (IP) to support |
| 1882 |
such a multicast service. Discussion and suggestions for |
| 1883 |
improvements are requested. |
| 1884 |
|
| 1885 |
965 Aguilar Dec 85 A Format for a Graphical |
| 1886 |
Communication Protocol |
| 1887 |
|
| 1888 |
This RFC describes the requirements for a graphical format on |
| 1889 |
which to base a graphical on-line communication protocol, and |
| 1890 |
proposes an Interactive Graphical Communication Format using the |
| 1891 |
GKSM session metafile. We hope this contribution will encourage |
| 1892 |
the discussion of multimedia data exchange and the proposal of |
| 1893 |
solutions. |
| 1894 |
|
| 1895 |
964 Sidhu Nov 85 Some Problems with the Specification |
| 1896 |
of the Military Standard |
| 1897 |
Transmission Control Protocol |
| 1898 |
|
| 1899 |
The purpose of this RFC is to provide helpful information on the |
| 1900 |
Military Standard Transmission Control Protocol (MIL-STD-1778) so |
| 1901 |
|
| 1902 |
|
| 1903 |
<span class="grey">Reynolds & Postel [Page 34]</span></pre> |
| 1904 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span> |
| 1905 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 1906 |
|
| 1907 |
|
| 1908 |
that one can obtain a reliable implementation of this protocol |
| 1909 |
standard. This note points out three errors with this |
| 1910 |
specification. This note also proposes solutions to these |
| 1911 |
problems. |
| 1912 |
|
| 1913 |
963 Sidhu Nov 85 Some Problems with the Specification |
| 1914 |
of the Military Standard Internet |
| 1915 |
Protocol |
| 1916 |
|
| 1917 |
The purpose of this RFC is to provide helpful information on the |
| 1918 |
Military Standard Internet Protocol (MIL-STD-1777) so that one can |
| 1919 |
obtain a reliable implementation of this protocol. This paper |
| 1920 |
points out several problems in this specification. This note also |
| 1921 |
proposes solutions to these problems. |
| 1922 |
|
| 1923 |
962 Padlipsky Nov 85 TCP-4 Prime |
| 1924 |
|
| 1925 |
This memo is in response to Bob Braden's call for a transaction |
| 1926 |
oriented protocol (<a href="./rfc955">RFC-955</a>), and continues the discussion of a |
| 1927 |
possible transaction oriented transport protocol. This memo does |
| 1928 |
not propose a standard. |
| 1929 |
|
| 1930 |
961 Reynolds Dec 85 Official ARPA-Internet Protocols |
| 1931 |
|
| 1932 |
This RFC has been replaced by <a href="./rfc991">RFC 991</a>. |
| 1933 |
|
| 1934 |
960 Reynolds Dec 85 Assigned Numbers |
| 1935 |
|
| 1936 |
This RFC has been replaced by RFCs 997 and 990. |
| 1937 |
|
| 1938 |
959 Postel Oct 85 File Transfer Protocol (FTP) |
| 1939 |
|
| 1940 |
This memo is the official specification of the File Transfer |
| 1941 |
Protocol (FTP) for the DARPA-Internet community. The primary |
| 1942 |
intent is to clarify and correct the documentation of the FTP |
| 1943 |
specification, not to change the protocol. The following new |
| 1944 |
optional commands are included in this edition of the |
| 1945 |
specification: Change to Parent Directory (CDUP), Structure Mount |
| 1946 |
(SMNT), Store Unique (STOU), Remove Directory (RMD), Make |
| 1947 |
Directory (MKD), Print Directory (PWD), and System (SYST). Note |
| 1948 |
that this specification is compatible with the previous edition. |
| 1949 |
|
| 1950 |
958 Mills Sep 85 Network Time Protocol (NTP) |
| 1951 |
|
| 1952 |
This document describes the Network Time Protocol (NTP), a |
| 1953 |
protocol for synchronizing a set of network clocks using a set of |
| 1954 |
distributed clients and servers. NTP is built on the User |
| 1955 |
Datagram Protocol (UDP), which provides a connectionless transport |
| 1956 |
mechanism. It evolved from the Time Protocol and the ICMP |
| 1957 |
|
| 1958 |
|
| 1959 |
<span class="grey">Reynolds & Postel [Page 35]</span></pre> |
| 1960 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span> |
| 1961 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 1962 |
|
| 1963 |
|
| 1964 |
Timestamp message and is a suitable replacement for both. This |
| 1965 |
RFC suggests a proposed protocol for the ARPA-Internet community, |
| 1966 |
and requests discussion and suggestions for improvements. |
| 1967 |
|
| 1968 |
957 Mills Sep 85 Experiments in Network Clock |
| 1969 |
Synchronization |
| 1970 |
|
| 1971 |
This RFC discusses some experiments in clock synchronization in |
| 1972 |
the ARPA-Internet community, and requests discussion and |
| 1973 |
suggestions for improvements. One of the services frequently |
| 1974 |
neglected in computer network design is a high-quality, |
| 1975 |
time-of-day clock capable of generating accurate timestamps with |
| 1976 |
small errors compared to one-way network delays. Such a service |
| 1977 |
would be useful for tracing the progress of complex transactions, |
| 1978 |
synchronizing cached data bases, monitoring network performance |
| 1979 |
and isolating problems. In this memo, one such clock service |
| 1980 |
design will be described and its performance assessed. This |
| 1981 |
design has been incorporated as an integral part of the network |
| 1982 |
routing and control protocols of the Distributed Computer Network |
| 1983 |
(DCnet) architecture. |
| 1984 |
|
| 1985 |
956 Mills Sep 85 Algorithms for Synchronizing Network |
| 1986 |
Clocks |
| 1987 |
|
| 1988 |
This RFC discussed clock synchronization algorithms for the |
| 1989 |
ARPA-Internet community, and requests discussion and suggestions |
| 1990 |
for improvements. The recent interest within the Internet |
| 1991 |
community in determining accurate time from a set of mutually |
| 1992 |
suspicious network clocks has been prompted by several occasions |
| 1993 |
in which errors were found in usually reliable, accurate clock |
| 1994 |
servers after thunderstorms which disrupted their power supply. |
| 1995 |
To these sources of error should be added those due to |
| 1996 |
malfunctioning hardware, defective software and operator mistakes, |
| 1997 |
as well as random errors in the mechanism used to set and |
| 1998 |
synchronize clocks. This report suggests a stochastic model and |
| 1999 |
algorithms for computing a good estimator from time-offset samples |
| 2000 |
measured between clocks connected via network links. Included in |
| 2001 |
this report are descriptions of certain experiments which give an |
| 2002 |
indication of the effectiveness of the algorithms. |
| 2003 |
|
| 2004 |
955 Braden Sep 85 Towards a Transport Service for |
| 2005 |
Transaction Processing Applications |
| 2006 |
|
| 2007 |
The DoD Internet Protocol Suite includes two alternative transport |
| 2008 |
service protocols, TCP and UDP, which provide virtual circuit and |
| 2009 |
datagram service, respectively. These two protocols represent |
| 2010 |
points in the space of possible transport service attributes which |
| 2011 |
are quite "far apart". We want to examine an important class of |
| 2012 |
applications, those which perform what is often called |
| 2013 |
|
| 2014 |
|
| 2015 |
<span class="grey">Reynolds & Postel [Page 36]</span></pre> |
| 2016 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span> |
| 2017 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 2018 |
|
| 2019 |
|
| 2020 |
"transaction processing". We will see that the communication |
| 2021 |
needs for these applications fall into the gap "between" TCP and |
| 2022 |
UDP -- neither protocol is very appropriate. |
| 2023 |
|
| 2024 |
954 Harrenstien Oct 85 NICNAME/WHOIS |
| 2025 |
|
| 2026 |
This RFC is the official specification of the NICNAME/WHOIS |
| 2027 |
protocol. This memo describes the protocol and the service. This |
| 2028 |
is an update of <a href="./rfc812">RFC 812</a>. Obsoletes <a href="./rfc812">RFC 812</a>. |
| 2029 |
|
| 2030 |
953 Harrenstien Oct 85 Hostname Server |
| 2031 |
|
| 2032 |
This RFC is the official specification of the Hostname Server |
| 2033 |
Protocol. This edition of the specification includes minor |
| 2034 |
revisions to <a href="./rfc811">RFC 811</a> which brings it up to date. Obsoletes <a href="./rfc811">RFC</a> |
| 2035 |
<a href="./rfc811">811</a>. |
| 2036 |
|
| 2037 |
952 Harrenstien Oct 85 DoD Internet Host Table |
| 2038 |
Specification |
| 2039 |
|
| 2040 |
This RFC is the official specification of the format of the |
| 2041 |
Internet Host Table. This edition of the specification includes |
| 2042 |
minor revisions to <a href="./rfc810">RFC 810</a> which brings it up to date. Obsoletes |
| 2043 |
RFCs 810, 608. |
| 2044 |
|
| 2045 |
951 Croft Sep 85 Bootstrap Protocol (BOOTP) |
| 2046 |
|
| 2047 |
This RFC describes an IP/UDP bootstrap protocol (BOOTP) which |
| 2048 |
allows a diskless client machine to discover its own IP address, |
| 2049 |
the address of a server host, and the name of a file to be loaded |
| 2050 |
into memory and executed. The bootstrap operation can be thought |
| 2051 |
of as consisting of TWO PHASES. This RFC describes the first |
| 2052 |
phase, which could be labeled `address determination and bootfile |
| 2053 |
selection'. After this address and filename information is |
| 2054 |
obtained, control passes to the second phase of the bootstrap |
| 2055 |
where a file transfer occurs. The file transfer will typically |
| 2056 |
use the TFTP protocol, since it is intended that both phases |
| 2057 |
reside in PROM on the client. However BOOTP could also work with |
| 2058 |
other protocols such as SFTP or FTP. This RFC suggests a proposed |
| 2059 |
protocol for the ARPA-Internet community, and requests discussion |
| 2060 |
and suggestions for improvements. |
| 2061 |
|
| 2062 |
950 Mogul Aug 85 Internet Standard Subnetting |
| 2063 |
Procedure |
| 2064 |
|
| 2065 |
This memo discusses the utility of "subnets" of Internet networks, |
| 2066 |
which are logically visible sub-sections of a single Internet |
| 2067 |
network. For administrative or technical reasons, many |
| 2068 |
organizations have chosen to divide one Internet network into |
| 2069 |
|
| 2070 |
|
| 2071 |
<span class="grey">Reynolds & Postel [Page 37]</span></pre> |
| 2072 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span> |
| 2073 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 2074 |
|
| 2075 |
|
| 2076 |
several subnets, instead of acquiring a set of Internet network |
| 2077 |
numbers. This memo specifies procedures for the use of subnets. |
| 2078 |
These procedures are for hosts (e.g., workstations). The |
| 2079 |
procedures used in and between subnet gateways are not fully |
| 2080 |
described. Important motivation and background information for a |
| 2081 |
subnetting standard is provided in <a href="./rfc940">RFC-940</a>. This RFC specifies a |
| 2082 |
protocol for the ARPA-Internet community. If subnetting is |
| 2083 |
implemented it is strongly recommended that these procedures be |
| 2084 |
followed. |
| 2085 |
|
| 2086 |
949 Padlipsky Jul 85 FTP Unique-Named Store Command |
| 2087 |
|
| 2088 |
There are various contexts in which it would be desirable to have |
| 2089 |
an FTP command that had the effect of the present STOR but rather |
| 2090 |
than requiring the sender to specify a file name istead caused the |
| 2091 |
resultant file to have a unique name relative to the current |
| 2092 |
directory. |
| 2093 |
|
| 2094 |
This RFC proposes an extension to the File Transfer Protocol for |
| 2095 |
the ARPA-Internet community, and requests discussion and |
| 2096 |
suggestions for improvements. |
| 2097 |
|
| 2098 |
948 Winston Jun 85 Two Methods for the Transmission of |
| 2099 |
IP Datagrams Over IEEE 802.3 |
| 2100 |
Networks |
| 2101 |
|
| 2102 |
This memo describes two methods of encapsulating Internet Protocol |
| 2103 |
(IP) datagrams on an IEEE 802.3 network. |
| 2104 |
|
| 2105 |
947 Lebowitz Jun 85 Multi-Network Broadcasting Within |
| 2106 |
the Internet |
| 2107 |
|
| 2108 |
This RFC describes the extension of a network's broadcast domain |
| 2109 |
to include more than one physical network through the use of a |
| 2110 |
broadcast packet repeater. |
| 2111 |
|
| 2112 |
946 Nedved May 85 Telnet Terminal Location Number |
| 2113 |
Option |
| 2114 |
|
| 2115 |
Many systems provide a mechanism for finding out where a user is |
| 2116 |
logged in from usually including information about telephone |
| 2117 |
extension and office occupants names. The information is useful |
| 2118 |
for physically locating people and/or calling them on the phone. |
| 2119 |
In 1982 CMU designed and implemented a terminal location database |
| 2120 |
and modified existing network software to handle a 64-bit number |
| 2121 |
called the Terminal Location Number (or TTYLOC). It now seems |
| 2122 |
appropriate to incorporate this mechanism into the TCP-based |
| 2123 |
network protocol family. The mechanism is not viewed as a |
| 2124 |
replacement for the Terminal Location Telnet Option |
| 2125 |
|
| 2126 |
|
| 2127 |
<span class="grey">Reynolds & Postel [Page 38]</span></pre> |
| 2128 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span> |
| 2129 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 2130 |
|
| 2131 |
|
| 2132 |
(SEND-LOCATION) but as a shorthand mechansim for communicating |
| 2133 |
terminal location information between hosts in a localized |
| 2134 |
community. This RFC proposes a new option for Telnet for the |
| 2135 |
ARPA-Internet community, and requests discussion and suggestions |
| 2136 |
for improvements. |
| 2137 |
|
| 2138 |
945 Postel May 85 A DoD Statement on the NRC Report |
| 2139 |
|
| 2140 |
In May 1983, the National Research Council (NRC) was asked jointly |
| 2141 |
by the DoD and NBS to study the issues and recommend a course of |
| 2142 |
action. The final report of the NRC committee was published in |
| 2143 |
February 1985 (see <a href="./rfc942">RFC-942</a>). The enclosed letter is from Donald C. |
| 2144 |
Latham (ASDC3I) to DCA transmitting the NRC report and requesting |
| 2145 |
specific actions relative to the recommendations of the report. |
| 2146 |
|
| 2147 |
This RFC reproduces a letter from the Assistant Secretary of |
| 2148 |
Defense for Command, Control, Communications, and Intelligence |
| 2149 |
(ASDC3I) to the Director of the Defense Communications Agency |
| 2150 |
(DCA). This letter is distributed for information only. |
| 2151 |
|
| 2152 |
944 Reynolds Apr 85 Official ARPA-Internet Protocols |
| 2153 |
|
| 2154 |
This RFC has been replaced by <a href="./rfc991">RFC 991</a>. |
| 2155 |
|
| 2156 |
943 Reynolds Apr 85 Assigned Numbers |
| 2157 |
|
| 2158 |
This RFC has been replaced by RFCs 997 and 990. |
| 2159 |
|
| 2160 |
942 NRC Feb 85 Transport Protocols for Department |
| 2161 |
of Defense Data Networks |
| 2162 |
|
| 2163 |
This RFC reproduces the National Research Council report resulting |
| 2164 |
from a study of the DoD Internet Protocol (IP) and Transmission |
| 2165 |
Control Protocol (TCP) in comparison with the ISO Internet |
| 2166 |
Protocol (ISO-IP) and Transport Protocol level 4 (TP-4). |
| 2167 |
|
| 2168 |
941 ISO Apr 85 Addendum to the Network Service |
| 2169 |
Definition Covering Network Layer |
| 2170 |
Addressing |
| 2171 |
|
| 2172 |
This Addendum to the Network Service Definition Standard, ISO |
| 2173 |
8348, defines the abstract syntax and semantics of the Network |
| 2174 |
Address (Network Service Access Point Address). The Network |
| 2175 |
Address defined in this Addendum is the address that appears in |
| 2176 |
the primitives of the connection-mode Network Service as the |
| 2177 |
calling address, called address, and responding address |
| 2178 |
parameters, and in the primitives of the connectionless-mode |
| 2179 |
Network Service as the source address and destination address |
| 2180 |
parameters. |
| 2181 |
|
| 2182 |
|
| 2183 |
<span class="grey">Reynolds & Postel [Page 39]</span></pre> |
| 2184 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span> |
| 2185 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 2186 |
|
| 2187 |
|
| 2188 |
This document is distributed as an RFC for information only. It |
| 2189 |
does not specify a standard for the ARPA-Internet. |
| 2190 |
|
| 2191 |
940 GADS Apr 85 Toward an Internet Standard Scheme |
| 2192 |
for Subnetting |
| 2193 |
|
| 2194 |
Several sites now contain a complex of local links connected to |
| 2195 |
the Internet via a gateway. The details of the internal |
| 2196 |
connectivity are of little interest to the rest of the Internet. |
| 2197 |
One way of organizing these local complexes of links is to use the |
| 2198 |
same strategy as the Internet uses to organize networks, that is, |
| 2199 |
to declare each link to be an entity (like a network) and to |
| 2200 |
interconnect the links with devices that perform routing functions |
| 2201 |
(like gateways). This general scheme is called subnetting, the |
| 2202 |
individual links are called subnets, and the connecting devices |
| 2203 |
are called subgateways (or bridges, or gateways). This RFC |
| 2204 |
discusses standardizing the protocol used in subnetted |
| 2205 |
environments in the ARPA-Internet. Distribution of this memo is |
| 2206 |
unlimited. The author of this RFC is the Gateway Algorithms and |
| 2207 |
Data Structures (GADS) Task Force, chaired by David L. Mills. |
| 2208 |
|
| 2209 |
939 NRC Feb 85 Executive Summary of the NRC Report |
| 2210 |
on Transport Protocols for |
| 2211 |
Department of Defense Data Networks |
| 2212 |
|
| 2213 |
This RFC reproduces the material from the "front pages" of the |
| 2214 |
National Research Council report resulting from a study of the DOD |
| 2215 |
Internet Protocol (IP) and Transmission Control Protocol (TCP) in |
| 2216 |
comparison with the ISO Internet Protocol (ISO-IP) and Transport |
| 2217 |
Protocol level 4 (TP-4). The point of this RFC is to make the |
| 2218 |
text of the Executive Summary widely available in a timely way. |
| 2219 |
The order of presentation has been altered, and the pagination |
| 2220 |
changed. |
| 2221 |
|
| 2222 |
938 Miller Feb 85 Internet Reliable Transaction |
| 2223 |
Protocol Functional and Interface |
| 2224 |
Specification |
| 2225 |
|
| 2226 |
This RFC is being distributed to members of the DARPA research |
| 2227 |
community in order to solicit their reactions to the proposals |
| 2228 |
contained in it. While the issues discussed may not be directly |
| 2229 |
relevant to the research problems of the DARPA community, they may |
| 2230 |
be interesting to a number of researchers and implementors. This |
| 2231 |
RFC suggests a proposed protocol for the ARPA-Internet community, |
| 2232 |
and requests discussion and suggestions for improvements. |
| 2233 |
|
| 2234 |
|
| 2235 |
|
| 2236 |
|
| 2237 |
|
| 2238 |
|
| 2239 |
<span class="grey">Reynolds & Postel [Page 40]</span></pre> |
| 2240 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span> |
| 2241 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 2242 |
|
| 2243 |
|
| 2244 |
937 Reynolds Feb 85 Post Office Protocol - Version 2 |
| 2245 |
|
| 2246 |
This RFC suggests a simple method for workstations to dynamically |
| 2247 |
access mail from a mailbox server. This RFC specifies a proposed |
| 2248 |
protocol for the ARPA-Internet community, and requests discussion |
| 2249 |
and suggestions for improvement. This memo is a revision of |
| 2250 |
<a href="./rfc918">RFC 918</a>. |
| 2251 |
|
| 2252 |
936 Karels Feb 85 Another Internet Subnet Addressing |
| 2253 |
Scheme |
| 2254 |
|
| 2255 |
There have been several proposals for schemes to allow the use of |
| 2256 |
a single Internet network number to refer to a collection of |
| 2257 |
physical networks under common administration which are reachable |
| 2258 |
from the rest of the Internet by a common route. Such schemes |
| 2259 |
allow a simplified view of an otherwise complicated topology from |
| 2260 |
hosts and gateways outside of this collection. They allow the |
| 2261 |
complexity of the number and type of these networks, and routing |
| 2262 |
to them, to be localized. Additions and changes in configuration |
| 2263 |
thus cause no detectable change, and no interruption of service, |
| 2264 |
due to slow propagation of routing and other information outside |
| 2265 |
of the local environment. These schemes also simplify the |
| 2266 |
administration of the network, as changes do not require |
| 2267 |
allocation of new network numbers for each new cable installed. |
| 2268 |
This proposal discusses an alternative scheme, one that has been |
| 2269 |
in use at the University of California, Berkeley since April 1984. |
| 2270 |
This RFC suggests a proposed protocol for the ARPA-Internet |
| 2271 |
community, and requests discussion and suggestions for |
| 2272 |
improvements. |
| 2273 |
|
| 2274 |
935 Robinson Jan 85 Reliable Link Layer Protocols |
| 2275 |
|
| 2276 |
This RFC discusses protocols proposed recently in RFCs 914 and |
| 2277 |
916, and suggests a proposed protocol that could meet the same |
| 2278 |
needs addressed in those memos. The stated need is reliable |
| 2279 |
communication between two programs over a full-duplex, |
| 2280 |
point-to-point communication link, and in particular the RFCs |
| 2281 |
address the need for such communication over an asynchronous link |
| 2282 |
at relatively low speeds. The suggested protocol uses the methods |
| 2283 |
of existing national and international data link layer standards. |
| 2284 |
This RFC suggests a proposed protocol for the ARPA-Internet |
| 2285 |
community, and requests discussion and suggestions for |
| 2286 |
improvements. |
| 2287 |
|
| 2288 |
934 Rose Jan 85 Proposed Standard for Message |
| 2289 |
Encapsulation |
| 2290 |
|
| 2291 |
This memo concerns itself with message forwarding. Forwarding can |
| 2292 |
be thought of as encapsulating one or more messages inside |
| 2293 |
|
| 2294 |
|
| 2295 |
<span class="grey">Reynolds & Postel [Page 41]</span></pre> |
| 2296 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span> |
| 2297 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 2298 |
|
| 2299 |
|
| 2300 |
another. Although this is useful for transfer of past |
| 2301 |
correspondence to new recipients, without a decapsulation process |
| 2302 |
(which this memo terms "bursting"), the forwarded messages are of |
| 2303 |
little use to the recipients because they can not be distributed, |
| 2304 |
forwarded, replied-to, or otherwise processed as separate |
| 2305 |
individual messages. In order to burst a message it is necessary |
| 2306 |
to know how the component messages were encapsulated in the draft. |
| 2307 |
At present there is no unambiguous standard for interest group |
| 2308 |
digests. This RFC proposes a proposed protocol for the |
| 2309 |
ARPA-Internet community, and requests discussion and suggestions |
| 2310 |
for improvements. |
| 2311 |
|
| 2312 |
933 Silverman Jan 85 Output Marking Telnet Option |
| 2313 |
|
| 2314 |
This proposed option would allow a Server-Telnet to send a banner |
| 2315 |
to a User-Telnet so that this banner would be displayed on the |
| 2316 |
workstation screen independently of the application software |
| 2317 |
running in the Server-Telnet. |
| 2318 |
|
| 2319 |
932 Clark Jan 85 A Subnetwork Addressing Scheme |
| 2320 |
|
| 2321 |
This RFC proposes an alternative addressing scheme for subnets |
| 2322 |
which, in most cases, requires no modification to host software |
| 2323 |
whatsoever. The drawbacks of this scheme are that the total |
| 2324 |
number of subnets in any one network are limited, and that |
| 2325 |
modification is required to all gateways. |
| 2326 |
|
| 2327 |
931 StJohns Jan 85 Authentication Server |
| 2328 |
|
| 2329 |
This RFC suggests a proposed protocol for the ARPA-Internet |
| 2330 |
community, and requests discussion and suggestions for |
| 2331 |
improvements. This is the second draft of this proposal |
| 2332 |
(superseding <a href="./rfc912">RFC 912</a>) and incorporates a more formal description |
| 2333 |
of the syntax for the request and response dialog, as well as a |
| 2334 |
change to specify the type of user identification returned. |
| 2335 |
|
| 2336 |
930 Solomon Jan 85 Telnet Terminal Type Option |
| 2337 |
|
| 2338 |
This RFC specifies a standard for the ARPA-Internet community. |
| 2339 |
Hosts on the ARPA-Internet that exchange terminal type information |
| 2340 |
within the Telnet protocol are expected to adopt and implement |
| 2341 |
this standard. Distribution of this memo is unlimited. This |
| 2342 |
standard supersedes <a href="./rfc884">RFC 884</a>. The only change is to specify that |
| 2343 |
the TERMINAL-TYPE IS sub-negotiation should be sent only in |
| 2344 |
response to the TERMINAL-TYPE SEND sub-negotiation. |
| 2345 |
|
| 2346 |
|
| 2347 |
|
| 2348 |
|
| 2349 |
|
| 2350 |
|
| 2351 |
<span class="grey">Reynolds & Postel [Page 42]</span></pre> |
| 2352 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span> |
| 2353 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 2354 |
|
| 2355 |
|
| 2356 |
929 Lilienkamp Dec 84 Proposed Host-Front End Protocol |
| 2357 |
|
| 2358 |
The Host-Front End Protocol introduced in <a href="./rfc928">RFC 928</a> is described in |
| 2359 |
detail in this memo. The first order of business is to declare |
| 2360 |
that THIS IS A PROPOSAL, NOT A FINAL STANDARD, and the second |
| 2361 |
order of business is to request that any readers of these |
| 2362 |
documents who are able to do test implementations (a) do so and |
| 2363 |
(b) coordinate their efforts with the author. This RFC suggests a |
| 2364 |
proposed protocol for the ARPA-Internet community, and requests |
| 2365 |
discussion and suggestions for improvements. |
| 2366 |
|
| 2367 |
928 Padlipsky Dec 84 Introduction to Proposed DOD |
| 2368 |
Standard H-FP |
| 2369 |
|
| 2370 |
The broad outline of the Host-Front End Protocol introduced here |
| 2371 |
and described in <a href="./rfc929">RFC 929</a> is the result of the deliberations of a |
| 2372 |
number of experienced H-FP designers, who sat as a committee of |
| 2373 |
the DoD Protocol Standards Technical Panel. It is the intent of |
| 2374 |
the designers that the protocol be subjected to multiple test |
| 2375 |
implementations and probable iteration before being agreed upon as |
| 2376 |
any sort of "standard". Therefore, the first order of business is |
| 2377 |
to declare that THIS IS A PROPOSAL, NOT A FINAL STANDARD, and the |
| 2378 |
second order of business is to request that any readers of these |
| 2379 |
documents who are able to do test implementations (a) do so and |
| 2380 |
(b) coordinate their efforts with the author. This RFC suggests a |
| 2381 |
proposed protocol for the ARPA-Internet community, and requests |
| 2382 |
discussion and suggestions for improvements. |
| 2383 |
|
| 2384 |
927 Anderson Dec 84 TACACS User Identification Telnet |
| 2385 |
Option |
| 2386 |
|
| 2387 |
The following is the description of a Telnet option designed to |
| 2388 |
facilitate double login avoidance. It is intended primarily for |
| 2389 |
TAC connections to target hosts on behalf of TAC users, but it can |
| 2390 |
be used between any two consenting hosts. For example, all hosts |
| 2391 |
at one site (e.g., BBN) can use this option to avoid double login |
| 2392 |
when TELNETing to one another. |
| 2393 |
|
| 2394 |
This RFC suggests a proposed protocol for the ARPA-Internet |
| 2395 |
community, and requests discussion and suggestions for |
| 2396 |
improvements. |
| 2397 |
|
| 2398 |
926 ISO Dec 84 Protocol for Providing the |
| 2399 |
Connectionless-Mode Network Services |
| 2400 |
|
| 2401 |
This note is the draft ISO protocol roughly similar to the DoD |
| 2402 |
Internet Protocol. This document has been prepared by retyping |
| 2403 |
the text of ISO DIS 8473 of May 1984, which is currently |
| 2404 |
undergoing voting within ISO as a Draft International Standard |
| 2405 |
|
| 2406 |
|
| 2407 |
<span class="grey">Reynolds & Postel [Page 43]</span></pre> |
| 2408 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span> |
| 2409 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 2410 |
|
| 2411 |
|
| 2412 |
(DIS). This document is distributed as an RFC for information |
| 2413 |
only. It does not specify a standard for the ARPA-Internet. |
| 2414 |
|
| 2415 |
925 Postel Oct 84 Multi-LAN Address Resolution |
| 2416 |
|
| 2417 |
The problem of treating a set of local area networks (LANs) as one |
| 2418 |
Internet network has generated some interest and concern. It is |
| 2419 |
inappropriate to give each LAN within a site a distinct |
| 2420 |
ARPA-Internet network number. It is desirable to hide the details |
| 2421 |
of the interconnections between the LANs within a site from |
| 2422 |
people, gateways, and hosts outside the site. The question arises |
| 2423 |
on how to best do this, and even how to do it at all. In <a href="./rfc917">RFC 917</a>, |
| 2424 |
Jeffery Mogul makes a case for the use of "explicit subnets" in a |
| 2425 |
multi-LAN environment. The explicit subnet scheme is a call to |
| 2426 |
recursively apply the mechanisms the ARPA-Internet uses to manage |
| 2427 |
networks to the problem of managing LANs within one network. In |
| 2428 |
this note I urge another approach: the use of "transparent |
| 2429 |
subnets" supported by a multi-LAN extension of the Address |
| 2430 |
Resolution Protocol. This RFC suggests a proposed protocol for |
| 2431 |
the ARPA-Internet community, and requests discussion and |
| 2432 |
suggestions for improvements. |
| 2433 |
|
| 2434 |
924 Reynolds Oct 84 Official ARPA-Internet Protocols |
| 2435 |
|
| 2436 |
This RFC has been replaced by <a href="./rfc991">RFC 991</a>. |
| 2437 |
|
| 2438 |
923 Reynolds Oct 84 Assigned Numbers |
| 2439 |
|
| 2440 |
This RFC has been replaced by RFCs 997 and 990. |
| 2441 |
|
| 2442 |
922 Mogul Oct 84 Broadcasting Internet Datagrams in |
| 2443 |
the Presence of Subnets |
| 2444 |
|
| 2445 |
We propose simple rules for broadcasting Internet datagrams on |
| 2446 |
local networks that support broadcast, for addressing broadcasts, |
| 2447 |
and for how gateways should handle them. |
| 2448 |
|
| 2449 |
This RFC suggests a proposed protocol for the ARPA-Internet |
| 2450 |
community, and requests discussion and suggestions for |
| 2451 |
improvements. |
| 2452 |
|
| 2453 |
921 Postel Oct 84 Domain Name System Implementation |
| 2454 |
Schedule - Revised |
| 2455 |
|
| 2456 |
This memo is a policy statement on the implementation of the |
| 2457 |
Domain Style Naming System in the ARPA-Internet. This memo is an |
| 2458 |
update of <a href="./rfc881">RFC 881</a>, and <a href="./rfc897">RFC 897</a>. This is an official policy |
| 2459 |
statement of the IAB and the DARPA. The intent of this memo is to |
| 2460 |
detail the schedule for the implementation for the Domain Style |
| 2461 |
|
| 2462 |
|
| 2463 |
<span class="grey">Reynolds & Postel [Page 44]</span></pre> |
| 2464 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span> |
| 2465 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 2466 |
|
| 2467 |
|
| 2468 |
Naming System. The explanation of how this system works is to be |
| 2469 |
found in the references. |
| 2470 |
|
| 2471 |
920 Postel Oct 84 Domain Requirements |
| 2472 |
|
| 2473 |
This memo states the requirements on establishing a Domain, and |
| 2474 |
introduces the limited set of top level domains. This memo is a |
| 2475 |
policy statement on the requirements of establishing a new domain |
| 2476 |
in the ARPA-Internet and the DARPA research community. This is an |
| 2477 |
official policy statement of the IAB and the DARPA. |
| 2478 |
|
| 2479 |
919 Mogul Oct 84 Broadcasting Internet Datagrams |
| 2480 |
|
| 2481 |
This RFC proposes simple rules for broadcasting Internet datagrams |
| 2482 |
on local networks that support broadcast, for addressing |
| 2483 |
broadcasts, and for how gateways should handle them. This RFC |
| 2484 |
suggests a proposed protocol for the ARPA-Internet community, and |
| 2485 |
requests discussion and suggestions for improvements. |
| 2486 |
|
| 2487 |
918 Reynolds Oct 84 Post Office Protocol (POP) |
| 2488 |
|
| 2489 |
Updated by <a href="./rfc937">RFC 937</a>. |
| 2490 |
|
| 2491 |
917 Mogul Oct 84 Internet Subnets |
| 2492 |
|
| 2493 |
This memo discusses subnets and proposes procedures for the use of |
| 2494 |
subnets, including approaches to solving the problems that arise, |
| 2495 |
particularly that of routing. A subnet of an Internet network is |
| 2496 |
a logically visible sub-section of a single Internet network. For |
| 2497 |
administrative or technical reasons, many organizations have |
| 2498 |
chosen to divide one Internet network into several subnets, |
| 2499 |
instead of acquiring a set of Internet network numbers. This RFC |
| 2500 |
suggests a proposed protocol for the ARPA-Internet community, and |
| 2501 |
requests discussion and suggestions for improvements. |
| 2502 |
|
| 2503 |
916 Finn Oct 84 Reliable Asynchronous Transfer |
| 2504 |
Protocol (RATP) |
| 2505 |
|
| 2506 |
This paper proposes and specifies a protocol which allows two |
| 2507 |
programs to reliably communicate over a communication link. It |
| 2508 |
ensures that the data entering one end of the link if received |
| 2509 |
arrives at the other end intact and unaltered. The protocol, |
| 2510 |
named RATP, is designed to operate over a full duplex |
| 2511 |
point-to-point connection. It contains some features which tailor |
| 2512 |
it to the RS-232 links now in common use. |
| 2513 |
|
| 2514 |
This RFC suggests a proposed protocol for the ARPA-Internet |
| 2515 |
community, and requests discussion and suggestions for |
| 2516 |
improvements. |
| 2517 |
|
| 2518 |
|
| 2519 |
<span class="grey">Reynolds & Postel [Page 45]</span></pre> |
| 2520 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span> |
| 2521 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 2522 |
|
| 2523 |
|
| 2524 |
915 Elvy Dec 84 Network Mail Path Service |
| 2525 |
|
| 2526 |
The network mail path service fills the current need of people to |
| 2527 |
determine mailbox addresses for hosts that are not part of the |
| 2528 |
ARPA-Internet but can be reached by one or more relay hosts that |
| 2529 |
have Unix to Unix Copy (UUCP) mail, CSNET mail, MAILNET mail, |
| 2530 |
BITNET mail, etc. Anyone can use the service if they have |
| 2531 |
TCP/TELENET to one of the hosts with a mail path server. This RFC |
| 2532 |
proposes a new service for the ARPA-Internet community and |
| 2533 |
requests discussion and suggestions for improvements. |
| 2534 |
|
| 2535 |
914 Farber Sep 84 A Thinwire Protocol |
| 2536 |
|
| 2537 |
This document focuses discussion on the particular problems in the |
| 2538 |
ARPA-Internet of low speed network interconnection with personal |
| 2539 |
computers, and possible methods of solution. None of the proposed |
| 2540 |
solutions in this document are intended as standards for the |
| 2541 |
ARPA-Internet. Rather, it is hoped that a general consensus will |
| 2542 |
emerge as to the appropriate solution to the problems, leading |
| 2543 |
eventually to the adoption of standards. |
| 2544 |
|
| 2545 |
913 Lottor Sep 84 Simple File Transfer Protocol |
| 2546 |
|
| 2547 |
This memo describes a proposed Simple File Transfer Protocol |
| 2548 |
(SFTP). It fills the need of people wanting a protocol that is |
| 2549 |
more useful than TFTP but easier to implement (and less powerful) |
| 2550 |
than FTP. SFTP supports user access control, file transfers, |
| 2551 |
directory listing, directory changing, file renaming, and |
| 2552 |
deleting. Discussion of this proposal is encouraged, and |
| 2553 |
suggestions for improvements may be sent to the author. |
| 2554 |
|
| 2555 |
912 StJohns Sep 84 Authentication Service |
| 2556 |
|
| 2557 |
This memo describes a proposed authentication protocol for |
| 2558 |
verifying the identity of a user of a TCP connection. Given a TCP |
| 2559 |
port number pair, it returns a character string which identifies |
| 2560 |
the owner of that connection on the server's system. Suggested |
| 2561 |
uses include automatic identification and verification of a user |
| 2562 |
during an FTP session, additional verification of a TAC dial up |
| 2563 |
user, and access verification for a generalized network file |
| 2564 |
server. |
| 2565 |
|
| 2566 |
911 Kirton Aug 84 EGP Gateway under Berkeley Unix 4.2 |
| 2567 |
|
| 2568 |
This memo describes an implementation of the Exterior Gateway |
| 2569 |
Protocol (EGP) (in that sense it is a status report). The memo |
| 2570 |
also discusses some possible extentions and some design issues (in |
| 2571 |
that sense it is an invitation for further discussion). |
| 2572 |
|
| 2573 |
|
| 2574 |
|
| 2575 |
<span class="grey">Reynolds & Postel [Page 46]</span></pre> |
| 2576 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span> |
| 2577 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 2578 |
|
| 2579 |
|
| 2580 |
910 Forsdick Aug 84 Multimedia Mail Meeting Notes |
| 2581 |
|
| 2582 |
This memo is a report on a meeting about the experimental |
| 2583 |
multimedia mail system (and in a sense a status report on that |
| 2584 |
experiment). The meeting was held at Bolt Beranek and Newman on |
| 2585 |
23-24 July 1984 to discuss recent progress by groups who are |
| 2586 |
building multimedia mail systems and to discuss a variety of |
| 2587 |
issues related to the further development of multimedia systems. |
| 2588 |
Representatives were present from BBN, ISI, SRI and Linkabit. |
| 2589 |
Distribution of this memo is unlimited. |
| 2590 |
|
| 2591 |
909 Welles Jul 84 Loader Debugger Protocol |
| 2592 |
|
| 2593 |
The Loader Debugger Protocol (LDP) is an application layer |
| 2594 |
protocol for loading, dumping, and debugging target machines from |
| 2595 |
hosts in a network environment. This RFC specifies a proposed |
| 2596 |
protocol for the ARPA-Internet and DARPA research community, and |
| 2597 |
requests discussion and suggestions for improvements. |
| 2598 |
|
| 2599 |
908 Velten Jul 84 Reliable Data Protocol |
| 2600 |
|
| 2601 |
The Reliable Data Protocol (RDP) is designed to provide a reliable |
| 2602 |
data transport service for packet-based applications. This RFC |
| 2603 |
specifies a proposed protocol for the ARPA-Internet and DARPA |
| 2604 |
research community, and requests discussion and suggestions for |
| 2605 |
improvemts. |
| 2606 |
|
| 2607 |
907 Storch Jul 84 Host Access Protocol Specification |
| 2608 |
|
| 2609 |
This document specifies the Host Access Protocol (HAP). Although |
| 2610 |
HAP was originally designed as the network-access level protocol |
| 2611 |
for the DARPA/DCA sponsored Wideband Packet Satellite Network, it |
| 2612 |
is intended that it evolve into a standard interface SATNET and |
| 2613 |
TACNET (aka MATNET) as well as the Wideband Network. HAP is an |
| 2614 |
experimental protocol, and will undergo further revision as new |
| 2615 |
capabilities are added and/or different satellite networks are |
| 2616 |
suported. Implementations of HAP should be performed in |
| 2617 |
coordination with satellite network development and operations |
| 2618 |
personnel. |
| 2619 |
|
| 2620 |
906 Finlayson Jun 84 Bootstrap Loading Using TFTP |
| 2621 |
|
| 2622 |
It is often convenient to be able to bootstrap a computer system |
| 2623 |
from a communications network. This RFC proposes the use of the |
| 2624 |
IP/TFTP protocol for bootstrap loading in this case. |
| 2625 |
|
| 2626 |
|
| 2627 |
|
| 2628 |
|
| 2629 |
|
| 2630 |
|
| 2631 |
<span class="grey">Reynolds & Postel [Page 47]</span></pre> |
| 2632 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span> |
| 2633 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 2634 |
|
| 2635 |
|
| 2636 |
905 ISO Apr 84 ISO Transport Protocol Specification |
| 2637 |
(ISO DP 8073) |
| 2638 |
|
| 2639 |
This is the current specification of the ISO Transport Protocol. |
| 2640 |
This document is the text of ISO/TC97/SC16/N1576 as corrected by |
| 2641 |
ISO/TC97/SC16/N1695. This is the specification currently being |
| 2642 |
voted on in ISO as a Draft International Standard (DIS). This |
| 2643 |
document is distributed as an RFC for your information only, it |
| 2644 |
does not specify a standard for the ARPA-Internet or DARPA |
| 2645 |
research community. Our thanks to Alex McKenzie of BBN for making |
| 2646 |
this online version available. Please note the size of this |
| 2647 |
document, the file contains 258,729 characters. |
| 2648 |
|
| 2649 |
904 Mills Apr 84 Exterior Gateway Protocol Formal |
| 2650 |
Specification |
| 2651 |
|
| 2652 |
This is the specification of the Exterior Gateway Protocol (EGP). |
| 2653 |
This memo updates portions of <a href="./rfc888">RFC 888</a> and <a href="./rfc827">RFC 827</a>. This RFC |
| 2654 |
specifies an official protocol of the DARPA community for use |
| 2655 |
between gateways of different autonomous systems in the |
| 2656 |
ARPA-Internet. |
| 2657 |
|
| 2658 |
903 Finlayson Jun 84 A Reverse Address Resolution |
| 2659 |
Protocol |
| 2660 |
|
| 2661 |
This RFC suggests a method for workstations to dynamically find |
| 2662 |
their protocol address (e.g., their Internet Address), when they |
| 2663 |
know only their hardware address (e.g., their attached physical |
| 2664 |
network address). This RFC specifies a proposed protocol for the |
| 2665 |
ARPA-Internet community, and requests discussion and suggestions |
| 2666 |
for improvement. |
| 2667 |
|
| 2668 |
902 Postel Jul 84 ARPA-Internet Protocol Policy |
| 2669 |
|
| 2670 |
The purpose of this memo is to explain how protocol standards are |
| 2671 |
adopted for the ARPA-Internet and the DARPA research community. |
| 2672 |
There are three important aspects to be discussed: the process, |
| 2673 |
the authority, and the complex relationship between the DARPA |
| 2674 |
community and the DDN community. This memo is a policy statement |
| 2675 |
on how protocols become official standards for the ARPA-Internet |
| 2676 |
and the DARPA research community. This is an official policy |
| 2677 |
statement of the ICCB and the DARPA. |
| 2678 |
|
| 2679 |
901 Reynolds Jun 84 Official ARPA-Internet Protocols |
| 2680 |
|
| 2681 |
This RFC has been replaced by <a href="./rfc991">RFC 991</a>. |
| 2682 |
|
| 2683 |
|
| 2684 |
|
| 2685 |
|
| 2686 |
|
| 2687 |
<span class="grey">Reynolds & Postel [Page 48]</span></pre> |
| 2688 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span> |
| 2689 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 2690 |
|
| 2691 |
|
| 2692 |
900 Reynolds Jun 84 Assigned Numbers |
| 2693 |
|
| 2694 |
This RFC has been replaced by RFCs 997 and 990. |
| 2695 |
|
| 2696 |
899 Postel Apr 84 Requests For Comments Summary |
| 2697 |
|
| 2698 |
A summary of the Request for Comments documents from <a href="./rfc800">RFC 800</a>-898. |
| 2699 |
|
| 2700 |
898 Hinden Apr 84 Gateway Special Interest Group |
| 2701 |
Meeting Notes |
| 2702 |
|
| 2703 |
This memo is a report on the Gateway Special Interest Group |
| 2704 |
Meeting that was held at ISI on 28 and 29 February 1984. Robert |
| 2705 |
Hinden of BBNCC chaired, and Jon Postel of ISI hosted the meeting. |
| 2706 |
Approximately 35 gateway designers and implementors attended. |
| 2707 |
These notes are based on the recollections of Jon Postel and Mike |
| 2708 |
Muuss. Under each topic area are Jon Postel's brief notes, and |
| 2709 |
additional details from Mike Muuss. This memo is a report on the |
| 2710 |
meeting. No conclusions, decisions, or policy statements are |
| 2711 |
documented in this note. |
| 2712 |
|
| 2713 |
897 Postel Feb 84 Domain Name System Implementation |
| 2714 |
Schedule |
| 2715 |
|
| 2716 |
This memo is a policy statement on the implementation of the |
| 2717 |
Domain Style Naming System in the ARPA-Internet. This memo is a |
| 2718 |
partial update of <a href="./rfc881">RFC 881</a>. The intent of this memo is to detail |
| 2719 |
the schedule for the implementation of the Domain Style Naming |
| 2720 |
System. The names of hosts will be changed to Domain style names. |
| 2721 |
Hosts will begin to use Domain style names on 14-Mar-84, and the |
| 2722 |
use of old style names will be completely phased out before |
| 2723 |
2-May-84. This applies to both the ARPA research hosts and the |
| 2724 |
DDN operational hosts. This is an official policy statement of |
| 2725 |
the ICCB and the DARPA. |
| 2726 |
|
| 2727 |
896 Nagle Jan 84 Congestion Control in IP/TCP |
| 2728 |
Internetworks |
| 2729 |
|
| 2730 |
This memo discusses some aspects of congestion control in IP/TCP |
| 2731 |
Internetworks. It is intended to stimulate thought and further |
| 2732 |
discussion of this topic. While some specific suggestions are |
| 2733 |
made for improved congestion control implementation, this memo |
| 2734 |
does not specify any standards. |
| 2735 |
|
| 2736 |
895 Postel Apr 84 A Standard for the Transmission of |
| 2737 |
IP Datagrams over Experimental |
| 2738 |
Ethernet Networks |
| 2739 |
|
| 2740 |
This RFC specifies a standard method of encapsulating Internet |
| 2741 |
|
| 2742 |
|
| 2743 |
<span class="grey">Reynolds & Postel [Page 49]</span></pre> |
| 2744 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span> |
| 2745 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 2746 |
|
| 2747 |
|
| 2748 |
Protocol (IP) datagrams on an Experimental Ethernet. This RFC |
| 2749 |
specifies a standard protocol for the ARPA-Internet community. |
| 2750 |
|
| 2751 |
894 Hornig Apr 84 A Standard for the Transmission of |
| 2752 |
IP Datagrams over Ethernet Networks |
| 2753 |
|
| 2754 |
This RFC specifies a standard method of encapsulating Internet |
| 2755 |
Protocol (IP) datagrams on an Ethernet. This RFC specifies a |
| 2756 |
standard protocol for the ARPA-Internet community. |
| 2757 |
|
| 2758 |
893 Leffler Apr 84 Trailer Encapsulations |
| 2759 |
|
| 2760 |
This RFC discusses the motivation for use of "trailer |
| 2761 |
encapsulations" on local-area networks and describes the |
| 2762 |
implementation of such an encapsulation on various media. This |
| 2763 |
document is for information only. This is NOT an official |
| 2764 |
protocol for the ARPA-Internet community. |
| 2765 |
|
| 2766 |
892 ISO Dec 83 ISO Transport Protocol Specification |
| 2767 |
|
| 2768 |
This is a draft version of the transport protocol being |
| 2769 |
standardized by the ISO. This version also appeared in the ACM |
| 2770 |
SIGCOMM Computer Communication Review (V.12, N.3-4) |
| 2771 |
July-October 1982. This version is now out of date. |
| 2772 |
|
| 2773 |
891 Mills Dec 83 DCN Local-Network Protocols |
| 2774 |
|
| 2775 |
This RFC provides a description of the DCN protocols for |
| 2776 |
maintaining connectivity, routing, and clock information in a |
| 2777 |
local network. These procedures may be of interest to the |
| 2778 |
designers and implementers of other local networks. |
| 2779 |
|
| 2780 |
890 Postel Feb 84 Exterior Gateway Protocol |
| 2781 |
Implementation Schedule |
| 2782 |
|
| 2783 |
This memo is a policy statement on the implementation of the |
| 2784 |
Exterior Gateway Protocol (EGP) in the ARPA-Internet. This is an |
| 2785 |
official policy statement of ICCB and DARPA. After 1-Aug-84 there |
| 2786 |
shall be no dumb gateways in the Internet. Every gateway must be |
| 2787 |
a member of some autonomous system. Some gateway of each |
| 2788 |
autonomous system must exchange routing information with some |
| 2789 |
gateway of the core autonomous system using the Exterior Gateway |
| 2790 |
Protocol. |
| 2791 |
|
| 2792 |
889 Mills Dec 83 Internet Delay Experiments |
| 2793 |
|
| 2794 |
This memo reports on some measurements of round-trip times in the |
| 2795 |
Internet and suggests some possible improvements to the TCP |
| 2796 |
|
| 2797 |
|
| 2798 |
|
| 2799 |
<span class="grey">Reynolds & Postel [Page 50]</span></pre> |
| 2800 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span> |
| 2801 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 2802 |
|
| 2803 |
|
| 2804 |
retransmission timeout calculation. This memo is both a status |
| 2805 |
report on the ARPA-Internet and advice to TCP implementers. |
| 2806 |
|
| 2807 |
888 Seamonson Jan 84 "Stub" Exterior Gateway Protocol |
| 2808 |
|
| 2809 |
This RFC describes the Exterior Gateway Protocol (EGP) used to |
| 2810 |
connect Stub Gateways to an Autonomous System of core Gateways. |
| 2811 |
This document specifies the working protocol, and defines an ARPA |
| 2812 |
official protocol. All implementers of Gateways should carefully |
| 2813 |
review this document. |
| 2814 |
|
| 2815 |
887 Accetta Dec 83 Resource Location Protocol |
| 2816 |
|
| 2817 |
This RFC specifies a draft standard for the ARPA-Internet |
| 2818 |
community. It describes a resource location protocol for use in |
| 2819 |
the ARPA-Internet. It is most useful on networks employing |
| 2820 |
technologies which support some method of broadcast addressing, |
| 2821 |
however it may also be used on other types of networks. For |
| 2822 |
maximum benefit, all hosts which provide significant resources or |
| 2823 |
services to other hosts on the ARPA-Internet should implement this |
| 2824 |
protocol. Hosts failing to implement the Resource Location |
| 2825 |
Protocol risk being ignored by other hosts which are attempting to |
| 2826 |
locate resources on the ARPA-Internet. |
| 2827 |
|
| 2828 |
886 Rose Dec 83 Proposed Standard for Message Header |
| 2829 |
Munging |
| 2830 |
|
| 2831 |
This RFC specifies a draft standard for the ARPA-Internet |
| 2832 |
community. It describes the rules to be used when transforming |
| 2833 |
mail from the conventions of one message system to those of |
| 2834 |
another message system. In particular, the treatment of header |
| 2835 |
fields, and recipient addresses is specified. |
| 2836 |
|
| 2837 |
885 Postel Dec 83 Telnet End of Record Option |
| 2838 |
|
| 2839 |
This RFC specifies a standard for the ARPA-Internet community. It |
| 2840 |
specifies a method for marking the end of records in data |
| 2841 |
transmitted on Telnet connections. |
| 2842 |
|
| 2843 |
884 Solomon Dec 83 Telnet Terminal Type Option |
| 2844 |
|
| 2845 |
This RFC specifies a standard for the ARPA-Internet community. It |
| 2846 |
specifies a method for exchanging terminal type information in the |
| 2847 |
Telnet protocol. |
| 2848 |
|
| 2849 |
|
| 2850 |
|
| 2851 |
|
| 2852 |
|
| 2853 |
|
| 2854 |
|
| 2855 |
<span class="grey">Reynolds & Postel [Page 51]</span></pre> |
| 2856 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span> |
| 2857 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 2858 |
|
| 2859 |
|
| 2860 |
883 Mockapetris Nov 83 Domain Names - Implementation and |
| 2861 |
Specification |
| 2862 |
|
| 2863 |
This RFC discusses the implementation of domain name servers and |
| 2864 |
resolvers, specifies the format of transactions, and discusses the |
| 2865 |
use of domain names in the context of existing mail systems and |
| 2866 |
other network software. |
| 2867 |
|
| 2868 |
882 Mockapetris Nov 83 Domain Names - Concepts and |
| 2869 |
Facilities |
| 2870 |
|
| 2871 |
This RFC introduces domain style names, their use for |
| 2872 |
DDN/ARPA-Internet mail and host address support, and the protocol |
| 2873 |
and servers used to implement domain name facilities. |
| 2874 |
|
| 2875 |
881 Postel Nov 83 The Domain Names Plan and Schedule |
| 2876 |
|
| 2877 |
This RFC outlines a plan and schedule for the implementation of |
| 2878 |
domain style names throughout the DDN/ARPA-Internet community. |
| 2879 |
The introduction of domain style names will impact all hosts on |
| 2880 |
the DDN/ARPA-Internet. |
| 2881 |
|
| 2882 |
880 Reynolds Oct 83 Official Protocols |
| 2883 |
|
| 2884 |
This RFC has been replaced by <a href="./rfc991">RFC 991</a>. |
| 2885 |
|
| 2886 |
879 Postel Nov 83 The TCP Maximum Segment Size and |
| 2887 |
Related Topics |
| 2888 |
|
| 2889 |
This RFC discusses the TCP Maximum Segment Size Option and related |
| 2890 |
topics. The purpose is to clarify some aspects of TCP and its |
| 2891 |
interaction with IP. This memo is a clarification to the TCP |
| 2892 |
specification, and contains information that may be considered as |
| 2893 |
"advice to implementers". |
| 2894 |
|
| 2895 |
878 Malis Dec 83 The ARPANET 1822L Host Access |
| 2896 |
Protocol |
| 2897 |
|
| 2898 |
This RFC specifies the ARPANET 1822L Host Access Protocol, which |
| 2899 |
is a successor to the existing 1822 Host Access Protocol. The |
| 2900 |
1822L procedure allows ARPANET hosts to use logical identifiers as |
| 2901 |
well as 1822 physical interface identifiers to address each other. |
| 2902 |
|
| 2903 |
877 Korb Sep 83 A Standard for the Transmission of |
| 2904 |
IP Datagrams Over Public Data |
| 2905 |
Networks |
| 2906 |
|
| 2907 |
This RFC specifies a standard adopted by CSNET, the VAN gateway, |
| 2908 |
|
| 2909 |
|
| 2910 |
|
| 2911 |
<span class="grey">Reynolds & Postel [Page 52]</span></pre> |
| 2912 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span> |
| 2913 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 2914 |
|
| 2915 |
|
| 2916 |
and other organizations for the transmission of IP datagrams over |
| 2917 |
the X.25-based public data networks. |
| 2918 |
|
| 2919 |
876 Smallberg Sep 83 Survey of SMTP Implementations |
| 2920 |
|
| 2921 |
This RFC is a survey of implementation status. It does not |
| 2922 |
specify an official protocol, but rather notes the status of |
| 2923 |
implementation of aspects of a protocol. It is expected that the |
| 2924 |
status of the hosts reported on will change. This information |
| 2925 |
must be treated as a snapshot of the state of these |
| 2926 |
implemetations. |
| 2927 |
|
| 2928 |
875 Padlipsky Sep 82 Gateways, Architectures, and |
| 2929 |
Heffalumps |
| 2930 |
|
| 2931 |
This RFC is a discussion about the role of gateways in an |
| 2932 |
internetwork, especially the problems of translating or mapping |
| 2933 |
protocols between different protocol suites. The discussion notes |
| 2934 |
possible functionality mis-matches, undesirable routing |
| 2935 |
"singularity points", flow control issues, and high cost of |
| 2936 |
translating gateways. Originally published as M82-51 by the MITRE |
| 2937 |
Corporation, Bedford, Massachusetts. |
| 2938 |
|
| 2939 |
874 Padlipsky Sep 82 A Critique of X.25 |
| 2940 |
|
| 2941 |
This RFC is an analysis of X.25 pointing out some problems in the |
| 2942 |
conceptual model, particularly the conflict between the interface |
| 2943 |
aspects and the end-to-end aspects. The memo also touches on |
| 2944 |
security, and implementation issues. Originally published as |
| 2945 |
M82-50 by the MITRE Corporation, Bedford, Massachusetts. |
| 2946 |
|
| 2947 |
873 Padlipsky Sep 82 The Illusion of Vendor Support |
| 2948 |
|
| 2949 |
This memo takes issue with the claim that international standards |
| 2950 |
in computer protocols presently provide a basis for low cost |
| 2951 |
vendor supported protocol implementations. Originally published |
| 2952 |
as M82-49 by the MITRE Corporation, Bedford, Massachusetts. |
| 2953 |
|
| 2954 |
872 Padlipsky Sep 82 TCP-ON-A-LAN |
| 2955 |
|
| 2956 |
This memo attacks the notion that TCP cannot be appropriate for |
| 2957 |
use on a Local Area Network. Originally published as M82-48 by |
| 2958 |
the MITRE Corporation, Bedford Massachusetts. |
| 2959 |
|
| 2960 |
871 Padlipsky Sep 82 A Perspective on the Arpanet |
| 2961 |
Reference Model |
| 2962 |
|
| 2963 |
This RFC is primarily intended as a perspective on the ARM and |
| 2964 |
points out some of the differences between the ARM and the ISORM |
| 2965 |
|
| 2966 |
|
| 2967 |
<span class="grey">Reynolds & Postel [Page 53]</span></pre> |
| 2968 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span> |
| 2969 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 2970 |
|
| 2971 |
|
| 2972 |
which were expressed by members in NWG general meetings, NWG |
| 2973 |
protocol design committee meetings, the ARPA-Internet Working |
| 2974 |
Group, and private conversations over the intervening years. |
| 2975 |
Originally published as M82-47 by the MITRE Corporation, Bedford, |
| 2976 |
Massachusetts. |
| 2977 |
|
| 2978 |
870 Reynolds Oct 83 Assigned Numbers |
| 2979 |
|
| 2980 |
This RFC has been replaced by RFCs 997 and 990. |
| 2981 |
|
| 2982 |
869 Hinden Dec 83 A Host Monitoring Protocol |
| 2983 |
|
| 2984 |
This RFC specifies the Host Monitoring Protocol used to collect |
| 2985 |
information from various types of hosts in the Internet. |
| 2986 |
Designers of Internet communications software are encouraged to |
| 2987 |
consider this protocol as a means of monitoring the behavior of |
| 2988 |
their creations. |
| 2989 |
|
| 2990 |
868 Postel May 83 Time Protocol |
| 2991 |
|
| 2992 |
This RFC specifies a standard for the ARPA-Internet community. |
| 2993 |
Hosts on the ARPA-Internet that choose to implement a Time |
| 2994 |
Protocol are expected to adopt and implement this standard. This |
| 2995 |
protocol provides a site-independent, machine readable date and |
| 2996 |
time. The Time service sends back to the originating source the |
| 2997 |
time in seconds since midnight on January first 1900. |
| 2998 |
|
| 2999 |
867 Postel May 83 Daytime Protocol |
| 3000 |
|
| 3001 |
This RFC specifies a standard for the ARPA-Internet community. |
| 3002 |
Hosts on the ARPA-Internet that choose to implement a Daytime |
| 3003 |
Protocol are expected to adopt and implement this standard. The |
| 3004 |
Daytime service simply sends the current date and time as a |
| 3005 |
character string without regard to the input. |
| 3006 |
|
| 3007 |
866 Postel May 83 Active Users |
| 3008 |
|
| 3009 |
This RFC specifies a standard for the ARPA-Internet community. |
| 3010 |
Hosts on the ARPA-Internet that choose to implement an Active |
| 3011 |
Users Protocol are expected to adopt and implement this standard. |
| 3012 |
The Active Users service simply sends a list of the currently |
| 3013 |
active users on the host without regard to the input. |
| 3014 |
|
| 3015 |
865 Postel May 83 Quote of the Day Protocol |
| 3016 |
|
| 3017 |
This RFC specifies a standard for the ARPA-Internet community. |
| 3018 |
Hosts on the ARPA-Internet that choose to implement a Quote of the |
| 3019 |
Day Protocol are expected to adopt and implement this standard. |
| 3020 |
|
| 3021 |
|
| 3022 |
|
| 3023 |
<span class="grey">Reynolds & Postel [Page 54]</span></pre> |
| 3024 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-55" ></span> |
| 3025 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 3026 |
|
| 3027 |
|
| 3028 |
The Quote of the Day service simply sends a short message without |
| 3029 |
regard to the input. |
| 3030 |
|
| 3031 |
864 Postel May 83 Character Generator Protocol |
| 3032 |
|
| 3033 |
This RFC specifies a standard for the ARPA-Internet community. |
| 3034 |
Hosts on the ARPA-Internet that choose to implement a Character |
| 3035 |
Generator Protocol are expected to adopt and implement this |
| 3036 |
standard. The Character Generator service simply sends data |
| 3037 |
without regard to the input. |
| 3038 |
|
| 3039 |
863 Postel May 83 Discard Protocol |
| 3040 |
|
| 3041 |
This RFC specifies a standard for the ARPA-Internet community. |
| 3042 |
Hosts on the ARPA-Internet that choose to implement a Discard |
| 3043 |
Protocol are expected to adopt and implement this standard. The |
| 3044 |
Discard service simply throws away any data it receives. |
| 3045 |
|
| 3046 |
862 Postel May 83 Echo Protocol |
| 3047 |
|
| 3048 |
This RFC specifies a standard for the ARPA-Internet community. |
| 3049 |
Hosts on the ARPA-Internet that choose to implement a Echo |
| 3050 |
Protocol are expected to adopt and implement this standard. The |
| 3051 |
Echo service simply sends back to the originating source any data |
| 3052 |
it receives. |
| 3053 |
|
| 3054 |
861 Postel May 83 Telnet Extended Options - List |
| 3055 |
Option |
| 3056 |
|
| 3057 |
This Telnet Option provides a mechanism for extending the set of |
| 3058 |
possible options. This RFC specifies a standard for the |
| 3059 |
ARPA-Internet community. Hosts on the ARPA-Internet are expected |
| 3060 |
to adopt and implement this standard. Obsoletes NIC 16239. |
| 3061 |
|
| 3062 |
860 Postel May 83 Telnet Timing Mark Option |
| 3063 |
|
| 3064 |
This Telnet Option provides a way to check the roundtrip path |
| 3065 |
between two Telnet modules. This RFC specifies a standard for the |
| 3066 |
ARPA-Internet community. Hosts on the ARPA-Internet are expected |
| 3067 |
to adopt and implement this standard. Obsoletes NIC 16238. |
| 3068 |
|
| 3069 |
859 Postel May 83 Telnet Status Option |
| 3070 |
|
| 3071 |
This Telnet Option provides a way to determine the other Telnet |
| 3072 |
module's view of the status of options. This RFC specifies a |
| 3073 |
standard for the ARPA-Internet community. Hosts on the |
| 3074 |
ARPA-Internet are expected to adopt and implement this standard. |
| 3075 |
Obsoletes <a href="./rfc651">RFC 651</a> (NIC 31154). |
| 3076 |
|
| 3077 |
|
| 3078 |
|
| 3079 |
<span class="grey">Reynolds & Postel [Page 55]</span></pre> |
| 3080 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-56" ></span> |
| 3081 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 3082 |
|
| 3083 |
|
| 3084 |
858 Postel May 83 Telnet Suppress Go Ahead Option |
| 3085 |
|
| 3086 |
This Telnet Option disables the exchange of go-ahead signals |
| 3087 |
between the Telnet modules. This RFC specifies a standard for the |
| 3088 |
ARPA-Internet community. Hosts on the ARPA-Internet are expected |
| 3089 |
to adopt and implement this standard. Obsoletes NIC 15392. |
| 3090 |
|
| 3091 |
857 Postel May 83 Telnet Echo Option |
| 3092 |
|
| 3093 |
This Telnet Option enables remote echoing by the other Telnet |
| 3094 |
module. This RFC specifies a standard for the ARPA-Internet |
| 3095 |
community. Hosts on the ARPA-Internet are expected to adopt and |
| 3096 |
implement this standard. Obsoletes NIC 15390. |
| 3097 |
|
| 3098 |
856 Postel May 83 Telnet Binary Transmission |
| 3099 |
|
| 3100 |
This Telnet Option enables a binary data mode between the Telnet |
| 3101 |
modules. This RFC specifies a standard for the ARPA-Internet |
| 3102 |
community. Hosts on the ARPA-Internet are expected to adopt and |
| 3103 |
implement this standard. Obsoletes NIC 15389. |
| 3104 |
|
| 3105 |
855 Postel May 83 Telnet Option Specifications |
| 3106 |
|
| 3107 |
This memo specifies the general form for Telnet options and the |
| 3108 |
directions for their specification. This RFC specifies a standard |
| 3109 |
for the ARPA-Internet community. Hosts on the ARPA-Internet are |
| 3110 |
expected to adopt and implement this standard. Obsoletes <a href="./rfc651">RFC 651</a>, |
| 3111 |
NIC 18640. |
| 3112 |
|
| 3113 |
854 Postel May 83 Telnet Protocol Specifications |
| 3114 |
|
| 3115 |
This is the specification of the Telnet protocol used for remote |
| 3116 |
terminal access in the ARPA-Internet. The purpose of the Telnet |
| 3117 |
Protocol is to provide a fairly general, bi-directional, eight-bit |
| 3118 |
byte oriented communications facility. Its primary goal is to |
| 3119 |
allow a standard method of interfacing terminal devices and |
| 3120 |
terminal-oriented processes to each other. It is envisioned that |
| 3121 |
the protocol may also be used for terminal-terminal communication |
| 3122 |
("linking") and process-process communication (distributed |
| 3123 |
computation). This RFC specifies a standard for the |
| 3124 |
ARPA-Internet community. Hosts on the ARPA-Internet are expected |
| 3125 |
to adopt and implement this standard. Obsoletes NIC 18639. |
| 3126 |
|
| 3127 |
853 Never Issued. |
| 3128 |
|
| 3129 |
|
| 3130 |
|
| 3131 |
|
| 3132 |
|
| 3133 |
|
| 3134 |
|
| 3135 |
<span class="grey">Reynolds & Postel [Page 56]</span></pre> |
| 3136 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-57" ></span> |
| 3137 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 3138 |
|
| 3139 |
|
| 3140 |
852 Malis Apr 83 The ARPANET Short Blocking Feature |
| 3141 |
|
| 3142 |
This RFC specifies the ARPANET Short Blocking Feature, which will |
| 3143 |
allow ARPANET hosts to optionally shorten the IMP's host blocking |
| 3144 |
timer. This Feature is a replacement of the ARPANET non-blocking |
| 3145 |
host interface, which was never implemented, and will be available |
| 3146 |
to hosts using either the 1822 or 1822L Host Access Protocol. |
| 3147 |
This RFC is also being presented as a solicitation of comments on |
| 3148 |
the Short Blocking Feature, especially from host network software |
| 3149 |
implementers and maintainers. |
| 3150 |
|
| 3151 |
851 Malis Apr 83 The ARPANET 1822L Host Access |
| 3152 |
Protocol |
| 3153 |
|
| 3154 |
This RFC specifies the ARPANET 1822L Host Access Protocol, which |
| 3155 |
is a successor to the existing 1822 Host Access Protocol. 1822L |
| 3156 |
allows ARPANET hosts to use logical names as well as 1822's |
| 3157 |
physical port locations to address each other. This RFC is also |
| 3158 |
being presented as a solicitation of comments on 1822L, especially |
| 3159 |
from host network software implementers and maintainers. |
| 3160 |
Obsoletes <a href="./rfc802">RFC 802</a>. |
| 3161 |
|
| 3162 |
850 Horton Jun 83 Standard for Interchange of USENET |
| 3163 |
Messages |
| 3164 |
|
| 3165 |
This memo is distributed as an RFC only to make this information |
| 3166 |
easily accessible to researchers in the ARPA-Internet community. |
| 3167 |
It does not specify an Internet standard. This RFC defines the |
| 3168 |
standard format for interchange of Network News articles among |
| 3169 |
USENET sites. It describes the format for articles themselves, |
| 3170 |
and gives partial standards for transmission of news. The news |
| 3171 |
transmission is not entirely standardized in order to give a good |
| 3172 |
deal of flexibility to the individual hosts to choose transmission |
| 3173 |
hardware and software, whether to batch news and so on. |
| 3174 |
|
| 3175 |
849 Crispin May 83 Suggestions for Improved Host Table |
| 3176 |
Distribution |
| 3177 |
|
| 3178 |
This RFC actually is a request for comments. The issue dealt with |
| 3179 |
is that of a naming registry update procedure, both as exists |
| 3180 |
currently and what could exist in the future. None of the |
| 3181 |
proposed solutions are intended as standards at this time; rather |
| 3182 |
it is hoped that a general consensus will emerge as the |
| 3183 |
appropriate solution, leaving eventually to the adoption of |
| 3184 |
standards. |
| 3185 |
|
| 3186 |
|
| 3187 |
|
| 3188 |
|
| 3189 |
|
| 3190 |
|
| 3191 |
<span class="grey">Reynolds & Postel [Page 57]</span></pre> |
| 3192 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-58" ></span> |
| 3193 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 3194 |
|
| 3195 |
|
| 3196 |
848 Smallberg Mar 83 Who provides the "Little" TCP |
| 3197 |
Services? |
| 3198 |
|
| 3199 |
This RFC lists those hosts which provide any of these "little" TCP |
| 3200 |
services: The list of hosts were taken from the NIC hostname |
| 3201 |
table of 24-Feb-83. The tests were run on February 23 and 24, and |
| 3202 |
March 3 and 5 from ISI-VAXA.ARPA. |
| 3203 |
|
| 3204 |
847 Westine Feb 83 Summary of Smallberg Surveys |
| 3205 |
|
| 3206 |
This is a summary of the surveys of Telnet, FTP and Mail (SMTP) |
| 3207 |
servers conducted by David Smallberg in December 1982, January and |
| 3208 |
February 1983 as reported in <a href="./rfc832">RFC 832</a>-843, 845-846. This memo |
| 3209 |
extracts the number of hosts that accepted the connection to their |
| 3210 |
server for each of Telnet, FTP, and SMTP, and compares it to the |
| 3211 |
total host in the ARPA-Internet (not counting TACs or ECHOS). |
| 3212 |
|
| 3213 |
846 Smallberg Feb 83 Who Talks TCP? -- Survey of 22 |
| 3214 |
February 1983 |
| 3215 |
|
| 3216 |
This RFC is a survey of hosts to identify the implementation |
| 3217 |
status of Telnet, FTP, and Mail on TCP. The list of hosts was |
| 3218 |
taken from the NIC hostname table of 18-Feb-83. The tests were |
| 3219 |
run on 22-Feb-83 from ISI-VAXA.ARPA. |
| 3220 |
|
| 3221 |
845 Smallberg Feb 83 Who Talks TCP? -- Survey of 15 |
| 3222 |
February 1983 |
| 3223 |
|
| 3224 |
This RFC is a survey of hosts to identify the implementation |
| 3225 |
status of Telnet, FTP, and Mail on TCP. The list of hosts was |
| 3226 |
taken from the NIC hostname table of 3-Feb-83. The tests were run |
| 3227 |
on 15-Feb-83 from ISI-VAXA.ARPA. |
| 3228 |
|
| 3229 |
844 Clements Feb 83 Who Talks ICMP, too? Survey of 18 |
| 3230 |
February 1983 |
| 3231 |
|
| 3232 |
This survey determines how many hosts are able to respond to |
| 3233 |
Telnet connections from a user at a class C site. This requires, |
| 3234 |
in addition to IP and TCP, participation in gateway routing via |
| 3235 |
ICMP and handling of Class C addresses. The list of hosts was |
| 3236 |
taken from <a href="./rfc843">RFC 843</a>, extracting only those hosts which are listed |
| 3237 |
there as accepting Telnet connection. The tests were run on |
| 3238 |
18-Feb-83. |
| 3239 |
|
| 3240 |
843 Smallberg Feb 83 Who Talks TCP? -- Survey of 8 |
| 3241 |
February 1983 |
| 3242 |
|
| 3243 |
This RFC is a survey of hosts to identify the implementation |
| 3244 |
status of Telnet, FTP, and Mail on TCP. The list of hosts was |
| 3245 |
|
| 3246 |
|
| 3247 |
<span class="grey">Reynolds & Postel [Page 58]</span></pre> |
| 3248 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-59" ></span> |
| 3249 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 3250 |
|
| 3251 |
|
| 3252 |
taken from the NIC hostname table of 3-Feb-83. The tests were run |
| 3253 |
on 8-Feb-83 and on 9-Feb-83 from ISI-VAXA.ARPA. |
| 3254 |
|
| 3255 |
842 Smallberg Feb 83 Who Talks TCP? -- Survey of 1 |
| 3256 |
February 1983 |
| 3257 |
|
| 3258 |
This RFC is a survey of hosts to identify the implementation |
| 3259 |
status of Telnet, FTP, and Mail on TCP. The list of hosts was |
| 3260 |
taken from the NIC hostname table of 28-Jan-83. The tests were |
| 3261 |
run on 1-Feb-83 and on 2-Feb-83 ISI-VAXA.ARPA. |
| 3262 |
|
| 3263 |
841 FIPS PUB 98 Jan 83 Specification for Message Format for |
| 3264 |
Computer Based Message Systems |
| 3265 |
|
| 3266 |
This RFC is FIPS 98. The purpose of distributing this document as |
| 3267 |
an RFC is to make it easily accessible to the ARPA research |
| 3268 |
community. This RFC does not specify a standard for the |
| 3269 |
ARPA-Internet. Obsoletes <a href="./rfc806">RFC 806</a>. |
| 3270 |
|
| 3271 |
840 Postel Apr 83 Official Protocols |
| 3272 |
|
| 3273 |
This RFC has been replaced by <a href="./rfc991">RFC 991</a>. |
| 3274 |
|
| 3275 |
839 Smallberg Jan 83 Who Talks TCP? |
| 3276 |
|
| 3277 |
This RFC is a survey of hosts to identify the implementation |
| 3278 |
status of Telnet, FTP, and Mail on TCP. The list of hosts was |
| 3279 |
taken from the NIC hostname table of 31-Dec-82. The tests were |
| 3280 |
run on 25-Jan-83. |
| 3281 |
|
| 3282 |
838 Smallberg Jan 83 Who Talks TCP? |
| 3283 |
|
| 3284 |
This RFC is a survey of hosts to identify the implementation |
| 3285 |
status of Telnet, FTP, and Mail on TCP. The list of hosts was |
| 3286 |
taken from the NIC hostname table of 31-Dec-82. The tests were |
| 3287 |
run on 18-Jan-83. |
| 3288 |
|
| 3289 |
837 Smallberg Jan 83 Who Talks TCP? |
| 3290 |
|
| 3291 |
This RFC is a survey of hosts to identify the implementation |
| 3292 |
status of Telnet, FTP, and Mail on TCP. The list of hosts was |
| 3293 |
taken from the NIC hostname table of 31-Dec-82. The tests were |
| 3294 |
run on 11-Jan-83. |
| 3295 |
|
| 3296 |
836 Smallberg Jan 83 Who Talks TCP? |
| 3297 |
|
| 3298 |
This RFC is a survey of hosts to identify the implementation |
| 3299 |
status of Telnet, FTP, and Mail on TCP. The list of hosts was |
| 3300 |
|
| 3301 |
|
| 3302 |
|
| 3303 |
<span class="grey">Reynolds & Postel [Page 59]</span></pre> |
| 3304 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-60" ></span> |
| 3305 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 3306 |
|
| 3307 |
|
| 3308 |
taken from the NIC hostname table of 20-Dec-82. The tests were |
| 3309 |
run on 4-Jan-83 through 5-Jan-83. |
| 3310 |
|
| 3311 |
835 Smallberg Dec 82 Who Talks TCP? |
| 3312 |
|
| 3313 |
This RFC is a survey of hosts to identify the implementation |
| 3314 |
status of Telnet, FTP, and Mail on TCP. The list of hosts was |
| 3315 |
taken from the NIC hostname table of 2-Dec-82. The tests were run |
| 3316 |
on 28-Dec-82 through 5-Jan-83. |
| 3317 |
|
| 3318 |
834 Smallberg Dec 82 Who Talks TCP? |
| 3319 |
|
| 3320 |
This RFC is a survey of hosts to identify the implementation |
| 3321 |
status of Telnet, FTP, and Mail on TCP. The list of hosts was |
| 3322 |
taken from the NIC hostname table of 2-Dec-82. The tests were run |
| 3323 |
on 22-Dec-82. |
| 3324 |
|
| 3325 |
833 Smallberg Dec 82 Who Talks TCP? |
| 3326 |
|
| 3327 |
This RFC is a survey of hosts to identify the implementation |
| 3328 |
status of Telnet, FTP, and Mail on TCP. The list of hosts was |
| 3329 |
taken from the NIC hostname table of 2-Dec-82. The tests were run |
| 3330 |
on 14-Dec-82. |
| 3331 |
|
| 3332 |
832 Smallberg Dec 82 Who Talks TCP? |
| 3333 |
|
| 3334 |
This RFC is a survey of hosts to identify the implementation |
| 3335 |
status of Telnet, FTP, and Mail on TCP. The list of hosts was |
| 3336 |
taken from the NIC hostname table of 2-Dec-82. The tests were run |
| 3337 |
on 7-Dec-82. |
| 3338 |
|
| 3339 |
831 Braden Dec 82 Backup Access to the European Side |
| 3340 |
of SATNET |
| 3341 |
|
| 3342 |
The purpose of this RFC is to focus discussion on a particular |
| 3343 |
Internet problem: a backup path for software maintenance of the |
| 3344 |
European sector of the Internet, for use when SATNET is |
| 3345 |
partitioned. We propose a mechanism, based upon the Source |
| 3346 |
Routing option of IP, to reach European Internet sites via the VAN |
| 3347 |
Gateway and UCL. This proposal is not intended as a standard at |
| 3348 |
this time. |
| 3349 |
|
| 3350 |
830 Zaw-Sing Su Oct 82 A Distributed System for Internet |
| 3351 |
Name Service |
| 3352 |
|
| 3353 |
This RFC proposes a distributed name service for ARPA-Internet. |
| 3354 |
Its purpose is to focus discussion on the subject. It is hoped |
| 3355 |
that a general consensus will emerge leading eventually to the |
| 3356 |
adoption of standards. |
| 3357 |
|
| 3358 |
|
| 3359 |
<span class="grey">Reynolds & Postel [Page 60]</span></pre> |
| 3360 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-61" ></span> |
| 3361 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 3362 |
|
| 3363 |
|
| 3364 |
829 Cerf Oct 82 Packet Satellite Technology |
| 3365 |
Reference Sources |
| 3366 |
|
| 3367 |
This RFC describes briefly the packet satellite technology |
| 3368 |
developed by the Defense Advanced Research Projects Agency and |
| 3369 |
several other participating organizations in the U.K. and Norway |
| 3370 |
and provides a bibliography of relevant papers for researchers |
| 3371 |
interested in experimental and operational experience with this |
| 3372 |
dynamic satellite-sharing technique. |
| 3373 |
|
| 3374 |
828 Owen Aug 82 Data Communications: IFIP's |
| 3375 |
International "Network" of Experts |
| 3376 |
|
| 3377 |
This RFC is distributed to inform the ARPA-Internet community of |
| 3378 |
the activities of the IFIP technical committee on Data |
| 3379 |
Communications, and to encourage participation in those |
| 3380 |
activities. |
| 3381 |
|
| 3382 |
827 Rosen Oct 82 Exterior Gateway Protocol (EGP) |
| 3383 |
|
| 3384 |
This RFC is proposed to establish a standard for Gateway to |
| 3385 |
Gateway procedures that allow the Gateways to be mutually |
| 3386 |
suspicious. This document is a DRAFT for that standard. Your |
| 3387 |
comments are strongly encouraged. |
| 3388 |
|
| 3389 |
826 Plummer Nov 82 An Ethernet Address Resolution |
| 3390 |
Protocol |
| 3391 |
|
| 3392 |
The purpose of this RFC is to present a method of Converting |
| 3393 |
Protocol Addresses (e.g., IP addresses) to Local Network Addresses |
| 3394 |
(e.g., Ethernet addresses). This is an issue of general concern |
| 3395 |
in the ARPA-Internet Community at this time. The method proposed |
| 3396 |
here is presented for your consideration and comment. This is not |
| 3397 |
the specification of an ARPA-Internet Standard. |
| 3398 |
|
| 3399 |
825 Postel Nov 82 Request for Comments on Requests for |
| 3400 |
Comments |
| 3401 |
|
| 3402 |
This RFC is intended to clarify the status of RFCs and to provide |
| 3403 |
some guidance for the authors of RFCs in the future. It is in a |
| 3404 |
sense a specification for RFCs. |
| 3405 |
|
| 3406 |
824 MacGregor Aug 82 The Cronus Virtual Local Network |
| 3407 |
|
| 3408 |
The purpose of this note is to describe the CRONUS Virtual Local |
| 3409 |
Network, especially the addressing related features. These |
| 3410 |
features include a method for mapping between Internet Addresses |
| 3411 |
and Local Network addresses. This is a topic of current concern |
| 3412 |
in the ARPA-Internet community. This note is intended to |
| 3413 |
|
| 3414 |
|
| 3415 |
<span class="grey">Reynolds & Postel [Page 61]</span></pre> |
| 3416 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-62" ></span> |
| 3417 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 3418 |
|
| 3419 |
|
| 3420 |
stimulate discussion. This is not a specification of an |
| 3421 |
ARPA-Internet Standard. |
| 3422 |
|
| 3423 |
823 Hinden Sep 82 The DARPA Internet Gateway |
| 3424 |
|
| 3425 |
This RFC is a status report on the Internet Gateway developed by |
| 3426 |
BBN. It describes the Internet Gateway as of September 1982. |
| 3427 |
This memo presents detailed descriptions of message formats and |
| 3428 |
gateway procedures, however, this is not an implementation |
| 3429 |
specification, and such details are subject to change. |
| 3430 |
|
| 3431 |
822 Crocker Aug 82 Standard for the Format of ARPA |
| 3432 |
Internet Text Messages |
| 3433 |
|
| 3434 |
This document revises the specifications in <a href="./rfc733">RFC 733</a>, in order to |
| 3435 |
serve the needs of the larger and more complex ARPA-Internet. |
| 3436 |
Some of <a href="./rfc733">RFC 733</a>'s features failed to gain adequate acceptance. In |
| 3437 |
order to simplify the standard and the software that follows it, |
| 3438 |
these features have been removed. A different addressing scheme |
| 3439 |
is used, to handle the case of internetwork mail; and the concept |
| 3440 |
of re-transmission has been introduced. Obsoletes <a href="./rfc733">RFC 733</a>, |
| 3441 |
NIC 41952. |
| 3442 |
|
| 3443 |
821 Postel Aug 82 Simple Mail Transfer Protocol |
| 3444 |
|
| 3445 |
The objective of Simple Mail Transfer Protocol (SMTP) is to |
| 3446 |
transfer mail reliably and efficiently. SMTP is independent of |
| 3447 |
the particular transmission subsystem and requires only a reliable |
| 3448 |
ordered data stream channel. Obsoletes RFCs 788, 780, 772. |
| 3449 |
|
| 3450 |
820 Postel Jan 82 Assigned Numbers |
| 3451 |
|
| 3452 |
This RFC is is replaced by RFCs 997 and 990. |
| 3453 |
|
| 3454 |
819 Zaw-Sing Su Aug 82 The Domain Naming Convention for |
| 3455 |
Internet User Applications |
| 3456 |
|
| 3457 |
This RFC is an attempt to clarify the generalization of the Domain |
| 3458 |
Naming Convention, the Internet Naming Convention, and to explore |
| 3459 |
the implications of its adoption for ARPA-Internet name service |
| 3460 |
and user applications. |
| 3461 |
|
| 3462 |
818 Postel Nov 82 The Remote User Telnet Service |
| 3463 |
|
| 3464 |
This RFC is the specification of an application protocol. Any |
| 3465 |
host that implements this application level service must follow |
| 3466 |
this protocol. |
| 3467 |
|
| 3468 |
|
| 3469 |
|
| 3470 |
|
| 3471 |
<span class="grey">Reynolds & Postel [Page 62]</span></pre> |
| 3472 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-63" ></span> |
| 3473 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 3474 |
|
| 3475 |
|
| 3476 |
817 Clark Jul 82 Modularity and Efficiency in |
| 3477 |
Protocol Implementation |
| 3478 |
|
| 3479 |
This RFC will discuss some of the commonly encountered reasons why |
| 3480 |
protocol implementations seem to run slowly. |
| 3481 |
|
| 3482 |
816 Clark Jul 82 Fault Isolation and Recovery |
| 3483 |
|
| 3484 |
This RFC describes the portion of fault isolation and recovery |
| 3485 |
which is the responsibility of the host. |
| 3486 |
|
| 3487 |
815 Clark Jul 82 IP Datagram Reassembly Algorithms |
| 3488 |
|
| 3489 |
This RFC describes an alternate approach of dealing with |
| 3490 |
reassembly which reduces the bookkeeping problem to a minimum, and |
| 3491 |
requires only one buffer for storage equal in size to the final |
| 3492 |
datagram being reassembled, which can reassemble a datagram from |
| 3493 |
any number of fragments arriving in any order with any possible |
| 3494 |
pattern of overlap and duplication, and which is appropriate for |
| 3495 |
almost any sort of operating system. |
| 3496 |
|
| 3497 |
814 Clark Jul 82 Name, Addresses, Ports, and Routes |
| 3498 |
|
| 3499 |
This RFC gives suggestions and guidance for the design of the |
| 3500 |
tables and algorithms necessary to keep track of these various |
| 3501 |
sorts of identifiers inside a host implementation of TCP/IP. |
| 3502 |
|
| 3503 |
813 Clark Jul 82 Window and Acknowledgement Strategy |
| 3504 |
in TCP |
| 3505 |
|
| 3506 |
This RFC describes implementation strategies to deal with two |
| 3507 |
mechanisms in TCP, the window and the acknowledgement. It also |
| 3508 |
presents a particular set of algorithms which have received |
| 3509 |
testing in the field, and which appear to work properly with each |
| 3510 |
other. With more experience, these algorithms may become part of |
| 3511 |
the formal specification, until such time their use is |
| 3512 |
recommended. |
| 3513 |
|
| 3514 |
812 Harrenstien Mar 82 NICNAME/WHOIS |
| 3515 |
|
| 3516 |
This RFC gives a description of what the NICNAME/WHOIS Server is |
| 3517 |
and how to access it. This server together with the corresponding |
| 3518 |
Identification Data Base provides online directory look-up |
| 3519 |
equivalent to the ARPANET Directory. |
| 3520 |
|
| 3521 |
|
| 3522 |
|
| 3523 |
|
| 3524 |
|
| 3525 |
|
| 3526 |
|
| 3527 |
<span class="grey">Reynolds & Postel [Page 63]</span></pre> |
| 3528 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-64" ></span> |
| 3529 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 3530 |
|
| 3531 |
|
| 3532 |
811 Harrenstien Mar 82 Hostnames Server |
| 3533 |
|
| 3534 |
This RFC gives a description of what the Hostnames Server is and |
| 3535 |
how to access it. The function of this particular server is to |
| 3536 |
deliver machine-readable name/address information describing |
| 3537 |
networks, gateways, hosts, and eventually domains, within the |
| 3538 |
Internet environment. |
| 3539 |
|
| 3540 |
810 Feinler Mar 82 DoD Internet Host Table |
| 3541 |
Specification |
| 3542 |
|
| 3543 |
This RFC specifies a new host table format applicable to both |
| 3544 |
ARPANET and Internet needs. In addition to host name to host |
| 3545 |
address translation and selected protocol information, we have |
| 3546 |
also included network and gateway name to address correspondence, |
| 3547 |
and host operating system information. This RFC obsoletes the |
| 3548 |
host table described in <a href="./rfc608">RFC 608</a>. |
| 3549 |
|
| 3550 |
809 Chang Feb 82 UCL Facsimile System |
| 3551 |
|
| 3552 |
This RFC describes the features of the computerised facsimile |
| 3553 |
system developed in the Department of Computer Science at UCL. |
| 3554 |
First its functions are considered and the related experimental |
| 3555 |
work are reported. Then the disciplines for system design are |
| 3556 |
discussed. Finally, the implementation of the system are |
| 3557 |
described, while detailed description are given as appendices. |
| 3558 |
|
| 3559 |
808 Postel Mar 82 Summary of Computer Mail Services |
| 3560 |
Meeting Held at BBN on 10 January |
| 3561 |
1979 |
| 3562 |
|
| 3563 |
This RFC is a very belated attempt to document a meeting that was |
| 3564 |
held three years earlier to discuss the state of computer mail in |
| 3565 |
the ARPA community and to reach some conclusions to guide the |
| 3566 |
further development of computer mail systems such that a coherent |
| 3567 |
total mail service would continue to be provided. |
| 3568 |
|
| 3569 |
807 Postel Feb 82 Multimedia Mail Meeting Notes |
| 3570 |
|
| 3571 |
This RFC consists of notes from a meeting held at USC/Information |
| 3572 |
Sciences Institute on the 12th of January to discuss common |
| 3573 |
interests in multimedia computer mail issues and to agree on some |
| 3574 |
specific initial experiments. |
| 3575 |
|
| 3576 |
806 NBS Sep 81 Specification for Message Format for |
| 3577 |
Computer Based Message Systems |
| 3578 |
|
| 3579 |
This RFC deals with Computer Based Message systems which provides |
| 3580 |
a basis for interaction between different CBMS by defining the |
| 3581 |
|
| 3582 |
|
| 3583 |
<span class="grey">Reynolds & Postel [Page 64]</span></pre> |
| 3584 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-65" ></span> |
| 3585 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 3586 |
|
| 3587 |
|
| 3588 |
format of messages passed between them. This RFC is replaced by |
| 3589 |
<a href="./rfc841">RFC 841</a>. |
| 3590 |
|
| 3591 |
805 Postel Feb 82 Computer Mail Meeting Notes |
| 3592 |
|
| 3593 |
This RFC consists of notes from a meeting that was held at |
| 3594 |
USC/Information Sciences Institute on 11 January 1982, to discuss |
| 3595 |
addressing issues in computer mail. The major conclusion reached |
| 3596 |
at the meeting is to extend the "username@hostname" mailbox format |
| 3597 |
to "[email protected]", where the domain itself can be further |
| 3598 |
structured. |
| 3599 |
|
| 3600 |
804 CCITT Jan 82 CCITT Draft Recommendation T.4 |
| 3601 |
|
| 3602 |
This is the CCITT standard for group 3 facsimile encoding. This |
| 3603 |
is useful for data compression of bit map data. |
| 3604 |
|
| 3605 |
803 Agarwal Nov 81 Dacom 450/500 Facsimile Data |
| 3606 |
Transcoding |
| 3607 |
|
| 3608 |
The first part of this RFC describes in detail the Dacom 450 data |
| 3609 |
compression algorithms and is an update and correction to an |
| 3610 |
earlier memorandum. The second part of this RFC describes briefly |
| 3611 |
the Dacom 500 data compression algorithm as used by the INTELPOST |
| 3612 |
electronic-mail network under development by the US Postal Service |
| 3613 |
and several foreign administrators. |
| 3614 |
|
| 3615 |
802 Malis Nov 81 The ARPANET 1822L Host Access |
| 3616 |
Protocol |
| 3617 |
|
| 3618 |
This document proposed two major changes to the current ARPANET |
| 3619 |
host access protocol. The first change will allow hosts to use |
| 3620 |
logical addressing (i.e., host addresses that are independent of |
| 3621 |
their physical location on the ARPANET) to communicate with each |
| 3622 |
other, and the second will allow a host to shorten the amount of |
| 3623 |
time that it may be blocked by its IMP after it presents a message |
| 3624 |
to the network (currently, the IMP can block further input from a |
| 3625 |
host for up to 15 seconds). See RFCs 852 and 851. |
| 3626 |
|
| 3627 |
801 Postel Nov 81 NCP/TCP Transition Plan |
| 3628 |
|
| 3629 |
This RFC discusses the conversion of hosts from NCP to TCP. And |
| 3630 |
making available the principle services: Telnet, File Transfer, |
| 3631 |
and Mail. These protocols allow all hosts in the ARPA community |
| 3632 |
to share a common interprocess communication environment. |
| 3633 |
|
| 3634 |
|
| 3635 |
|
| 3636 |
|
| 3637 |
|
| 3638 |
|
| 3639 |
<span class="grey">Reynolds & Postel [Page 65]</span></pre> |
| 3640 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-66" ></span> |
| 3641 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 3642 |
|
| 3643 |
|
| 3644 |
800 Postel Nov 82 Requests for Comments Summary |
| 3645 |
|
| 3646 |
This RFC is a slightly annotated list of the 100 RFCs from <a href="./rfc700">RFC 700</a> |
| 3647 |
through <a href="./rfc799">RFC 799</a>. This is a status report on these RFCs. |
| 3648 |
|
| 3649 |
799 Mills Sep 81 Internet Name Domains |
| 3650 |
|
| 3651 |
This document suggests that, as the Internet grows, the space of |
| 3652 |
host names cannot remain a flat space of globally unique names, |
| 3653 |
therefore a hierarchy of name domains must be introduced; see also |
| 3654 |
<a href="./rfc822">RFC 822</a>. |
| 3655 |
|
| 3656 |
798 Katz Sep 81 Decoding Facsimile Data From the |
| 3657 |
Rapicom 450 |
| 3658 |
|
| 3659 |
A description of the encoding/decoding procedure for Rapicom 450 |
| 3660 |
facsimile machine. |
| 3661 |
|
| 3662 |
797 Katz Sep 81 Format for Bitmap Files |
| 3663 |
|
| 3664 |
The description of a simple file format for bitmap data. |
| 3665 |
|
| 3666 |
796 Postel Sep 81 Address Mappings |
| 3667 |
|
| 3668 |
A description of the way the addresses of a few actual networks |
| 3669 |
are mapped into internet addresses. |
| 3670 |
|
| 3671 |
795 Postel Sep 81 Service Mappings |
| 3672 |
|
| 3673 |
A description of how the internet type of service is mapped into |
| 3674 |
the actual service parameters of a few particular networks, and |
| 3675 |
vice versa. |
| 3676 |
|
| 3677 |
794 Cerf Sep 81 Pre-Emption |
| 3678 |
|
| 3679 |
Discusses how pre-emption of TCP connection can be implemented. |
| 3680 |
Replaces IEN 125. |
| 3681 |
|
| 3682 |
793 Postel Sep 81 Transmission Control Protocol |
| 3683 |
|
| 3684 |
The specification of TCP. Replaces RFCs 761 and 675. |
| 3685 |
|
| 3686 |
792 Postel Sep 81 Internet Control Message Protocol |
| 3687 |
|
| 3688 |
The specification of ICMP. Replaces RFCs 777 and 760. |
| 3689 |
|
| 3690 |
|
| 3691 |
|
| 3692 |
|
| 3693 |
|
| 3694 |
|
| 3695 |
<span class="grey">Reynolds & Postel [Page 66]</span></pre> |
| 3696 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-67" ></span> |
| 3697 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 3698 |
|
| 3699 |
|
| 3700 |
791 Postel Sep 81 Internet Protocol |
| 3701 |
|
| 3702 |
An updated specification of IP. Replaces <a href="./rfc760">RFC 760</a>. |
| 3703 |
|
| 3704 |
790 Postel Sep 81 Assigned Numbers |
| 3705 |
|
| 3706 |
The RFC is replaced by RFCs 997 and 990. |
| 3707 |
|
| 3708 |
789 Rosen Jul 81 Vulnerabilities of Network Control |
| 3709 |
Protocols: An Example |
| 3710 |
|
| 3711 |
A description of an outage in ARPANET service and the process of |
| 3712 |
determining the cause; also, subtleties of designing network |
| 3713 |
protocols. |
| 3714 |
|
| 3715 |
788 Postel Nov 81 Simple Mail Transfer Protocol |
| 3716 |
|
| 3717 |
An old version; see <a href="./rfc821">RFC 821</a>. |
| 3718 |
|
| 3719 |
787 Chapin Jul 81 Connectionless Data Transmission |
| 3720 |
Survey/Tutorial |
| 3721 |
|
| 3722 |
A discussion of datagram service. Intended for submission to |
| 3723 |
international standards bodies. |
| 3724 |
|
| 3725 |
786 Sluizer Jul 81 Mail Transfer Protocol: ISI TOPS-20 |
| 3726 |
MTP-NIMAIL Interface |
| 3727 |
|
| 3728 |
The description of the way mail is passed between the MTP and the |
| 3729 |
NIMAIL programs in ISI TOPS-20. Outdated. |
| 3730 |
|
| 3731 |
785 Sluizer Jul 81 Mail Transfer Protocol: ISI TOPS-20 |
| 3732 |
File Definitions |
| 3733 |
|
| 3734 |
The description of the file format for passing mail to the MTP |
| 3735 |
program from user mail programs in ISI TOPS-20. Outdated. |
| 3736 |
|
| 3737 |
784 Sluizer Jul 81 Mail Transfer Protocol: ISI TOPS-20 |
| 3738 |
Implementation |
| 3739 |
|
| 3740 |
The description of the program structure for the MTP |
| 3741 |
implementation in the ISI TOPS-20. Outdated. |
| 3742 |
|
| 3743 |
783 Sollins Jun 81 The TFTP Protocol Revision 2 |
| 3744 |
|
| 3745 |
The specification of TFTP. Replaces RFCs 768, 764 and IEN 133. |
| 3746 |
|
| 3747 |
|
| 3748 |
|
| 3749 |
|
| 3750 |
|
| 3751 |
<span class="grey">Reynolds & Postel [Page 67]</span></pre> |
| 3752 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-68" ></span> |
| 3753 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 3754 |
|
| 3755 |
|
| 3756 |
782 Nabielsky undated A Virtual Terminal Management Model |
| 3757 |
|
| 3758 |
A description of the elements of a virtual terminal and the |
| 3759 |
management of communications between them. |
| 3760 |
|
| 3761 |
781 Su May 81 A Specification of the Internet |
| 3762 |
Protocol IP Timestamp Option |
| 3763 |
|
| 3764 |
The description of IP Timestamp option, now included in the IP |
| 3765 |
specification (<a href="./rfc791">RFC 791</a>). |
| 3766 |
|
| 3767 |
780 Sluizer May 81 Mail Transfer Protocol |
| 3768 |
|
| 3769 |
An outdated Mail protocol; see <a href="./rfc821">RFC 821</a>. |
| 3770 |
|
| 3771 |
779 Killian Apr 81 Telnet Send-Location Option |
| 3772 |
|
| 3773 |
Definition of this Telnet option. |
| 3774 |
|
| 3775 |
778 Mills Apr 81 DCNet Internet Clock Service |
| 3776 |
|
| 3777 |
Specifies a format and procedure for the exchange of messages to |
| 3778 |
maintain synchronized clocks. |
| 3779 |
|
| 3780 |
777 Postel Apr 81 Internet Control Message Protocol |
| 3781 |
|
| 3782 |
An old version; see <a href="./rfc792">RFC 792</a>. |
| 3783 |
|
| 3784 |
776 Postel Jan 81 Assigned Numbers |
| 3785 |
|
| 3786 |
This RFC has been replaced by RFCs 997 and 990. |
| 3787 |
|
| 3788 |
775 Mankins Dec 80 Directory Oriented FTP Commands |
| 3789 |
|
| 3790 |
The definition of additional FTP Commands related to directory |
| 3791 |
management. |
| 3792 |
|
| 3793 |
774 Postel Oct 80 Internet Protocol Handbook Table of |
| 3794 |
Contents |
| 3795 |
|
| 3796 |
An out-of-date table of contents for an Internet Protocol |
| 3797 |
Handbook. |
| 3798 |
|
| 3799 |
773 Cerf Oct 80 Comments on NCP/TCP Mail Service |
| 3800 |
Transition Strategy |
| 3801 |
|
| 3802 |
A discussion of issues in the transition from NCP to TCP, |
| 3803 |
particularly as related to MAIL Service. |
| 3804 |
|
| 3805 |
|
| 3806 |
|
| 3807 |
<span class="grey">Reynolds & Postel [Page 68]</span></pre> |
| 3808 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-69" ></span> |
| 3809 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 3810 |
|
| 3811 |
|
| 3812 |
772 Sluizer Sep 80 Mail Transfer Protocol |
| 3813 |
|
| 3814 |
An old version of a Mail Protocol; see <a href="./rfc821">RFC 821</a>. |
| 3815 |
|
| 3816 |
771 Cerf Sep 80 Mail Transition Plan |
| 3817 |
|
| 3818 |
A plan for supporting mail service in the transition from NCP to |
| 3819 |
TCP; see also <a href="./rfc801">RFC 801</a>. |
| 3820 |
|
| 3821 |
770 Postel Sep 80 Assigned Numbers |
| 3822 |
|
| 3823 |
This RFC has been replaced by RFCs 997 and 990. |
| 3824 |
|
| 3825 |
769 Postel Sep 80 Rapicom 450 Facsimile File Format |
| 3826 |
|
| 3827 |
The definition of the exchange format of the encoded facsimile |
| 3828 |
data of the Rapicom 450; see also <a href="./rfc798">RFC 798</a>. |
| 3829 |
|
| 3830 |
768 Postel Aug 80 User Datagram Protocol |
| 3831 |
|
| 3832 |
The specification of the UDP. |
| 3833 |
|
| 3834 |
767 Postel Aug 80 A Structured Format for Transmission |
| 3835 |
of Multi-Media Documents |
| 3836 |
|
| 3837 |
The definition of the format for the document of a multimedia |
| 3838 |
message. |
| 3839 |
|
| 3840 |
766 Postel Jul 80 Internet Protocol Handbook |
| 3841 |
|
| 3842 |
An out-of-date table of contents for the Internet Protocol |
| 3843 |
Handbook. |
| 3844 |
|
| 3845 |
765 Postel Jun 80 File Transfer Protocol Specification |
| 3846 |
|
| 3847 |
The specification of FTP. |
| 3848 |
|
| 3849 |
764 Postel Jun 80 Telnet Protocol Specification |
| 3850 |
|
| 3851 |
The specification of Telnet. |
| 3852 |
|
| 3853 |
763 Abrams May 80 Role Mailboxes |
| 3854 |
|
| 3855 |
A call for mailboxes with role names, such as "Management". |
| 3856 |
|
| 3857 |
|
| 3858 |
|
| 3859 |
|
| 3860 |
|
| 3861 |
|
| 3862 |
|
| 3863 |
<span class="grey">Reynolds & Postel [Page 69]</span></pre> |
| 3864 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-70" ></span> |
| 3865 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 3866 |
|
| 3867 |
|
| 3868 |
762 Postel Jan 80 Assigned Numbers |
| 3869 |
|
| 3870 |
This RFC has been replaced by RFCs 997 and 990. |
| 3871 |
|
| 3872 |
761 Postel Jan 80 DOD Standard Transmission Protocol |
| 3873 |
|
| 3874 |
An old version; see <a href="./rfc793">RFC 793</a>. |
| 3875 |
|
| 3876 |
760 Postel Jan 80 DOD Standard Internet Protocol |
| 3877 |
|
| 3878 |
An old version; see <a href="./rfc791">RFC 791</a>. |
| 3879 |
|
| 3880 |
759 Postel Aug 80 Internet Message Protocol |
| 3881 |
|
| 3882 |
The definition of the protocol and format for the exchange of |
| 3883 |
multimedia mail. Replaces <a href="./rfc753">RFC 753</a>. |
| 3884 |
|
| 3885 |
758 Postel Aug 79 Assigned Numbers |
| 3886 |
|
| 3887 |
This RFC has been replaced by RFCs 997 and 990. |
| 3888 |
|
| 3889 |
757 Deutsch Sep 79 A Suggested Solution to the Naming, |
| 3890 |
Addressing, and Delivery Problem for |
| 3891 |
ARPANET Message Systems |
| 3892 |
|
| 3893 |
Discusses several proposals for handing the name to address to |
| 3894 |
route processing for computer mail. Favors a solution based on |
| 3895 |
unique-ids and a data base, see also RFCs 759, 821 and 822. |
| 3896 |
|
| 3897 |
756 Pickens Jul 79 The NIC Name server--A |
| 3898 |
Datagram-Based Information Utility |
| 3899 |
|
| 3900 |
Describes a Host Name to Address look up service. |
| 3901 |
|
| 3902 |
755 Postel May 79 Assigned Numbers |
| 3903 |
|
| 3904 |
This RFC has been replaced by RFCs 997 and 990. |
| 3905 |
|
| 3906 |
754 Postel Apr 79 Out-of-Net Host Addresses for Mail |
| 3907 |
|
| 3908 |
A discussion of options for addressing computer mail beyond the |
| 3909 |
ARPANET. |
| 3910 |
|
| 3911 |
753 Postel Mar 79 Internet Message Protocol |
| 3912 |
|
| 3913 |
An old version; see <a href="./rfc759">RFC 759</a>. |
| 3914 |
|
| 3915 |
|
| 3916 |
|
| 3917 |
|
| 3918 |
|
| 3919 |
<span class="grey">Reynolds & Postel [Page 70]</span></pre> |
| 3920 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-71" ></span> |
| 3921 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 3922 |
|
| 3923 |
|
| 3924 |
752 Crispin Jan 79 A Universal Host Table |
| 3925 |
|
| 3926 |
Describes the host table used at MIT and Stanford. This has |
| 3927 |
several extensions and generalizations from the NIC standard and |
| 3928 |
the table used by most Tenex and TOPS20 hosts. |
| 3929 |
|
| 3930 |
751 Lebling Dec 78 Survey of FTP Mail and MLFL |
| 3931 |
|
| 3932 |
A survey of hosts' responses to probes of their FTP servers to see |
| 3933 |
if servers (a) accept mail for unknown users and (b) support the |
| 3934 |
MAIL and MLFL commands. |
| 3935 |
|
| 3936 |
750 Postel Sep 78 Assigned Numbers |
| 3937 |
|
| 3938 |
This RFC has been replaced by RFCs 997 and 990. |
| 3939 |
|
| 3940 |
749 Greenberg Sep 78 Telnet SUPDUP-OUTPUT Option |
| 3941 |
|
| 3942 |
Updates <a href="./rfc736">RFC 736</a>; see also RFCs 734, 746, and 747. |
| 3943 |
|
| 3944 |
748 Crispin Apr 78 Telnet Randomly-Lose Option |
| 3945 |
|
| 3946 |
Defines this Telnet option (note the date of this memo). |
| 3947 |
|
| 3948 |
747 Crispin Mar 78 Recent Extensions to the SUPDUP |
| 3949 |
Protocol |
| 3950 |
|
| 3951 |
An update to the SUPDUP protocol (<a href="./rfc734">RFC 734</a>); see also RFCs 749, 746 |
| 3952 |
and 736. |
| 3953 |
|
| 3954 |
746 Stallman Mar 78 The SUPDUP Graphics Extension |
| 3955 |
|
| 3956 |
An extension of SUPDUP for Graphics; see also RFCs 734, 736, 747 |
| 3957 |
and 749. |
| 3958 |
|
| 3959 |
745 Beeler Mar 78 JANUS Interface Specifications |
| 3960 |
|
| 3961 |
The specification of a symmetrical 1822 style interface. |
| 3962 |
|
| 3963 |
744 Sattley Jan 78 MARS - A Message Archiving and |
| 3964 |
Retrieval Service |
| 3965 |
|
| 3966 |
The description of a database service for computer mail messages, |
| 3967 |
which operates via computer mail. |
| 3968 |
|
| 3969 |
|
| 3970 |
|
| 3971 |
|
| 3972 |
|
| 3973 |
|
| 3974 |
|
| 3975 |
<span class="grey">Reynolds & Postel [Page 71]</span></pre> |
| 3976 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-72" ></span> |
| 3977 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 3978 |
|
| 3979 |
|
| 3980 |
543 Harrenstien Dec 77 FTP Extension: XRSQ/XRCP |
| 3981 |
|
| 3982 |
An extension to FTP mail to allow more efficient transmission of |
| 3983 |
computer mail. Now incorporated into SMTP; see <a href="./rfc788">RFC788</a>. |
| 3984 |
|
| 3985 |
742 Harrenstien Dec 77 NAME/FINGER Protocol |
| 3986 |
|
| 3987 |
Defines the Name or Finger Protocol which allows one to get "who |
| 3988 |
is on" or "where is user x" information from another host. |
| 3989 |
|
| 3990 |
741 Cohen Nov 77 Specifications for the Network Voice |
| 3991 |
Protocol NVP |
| 3992 |
|
| 3993 |
Defines the protocol used in the ARPANET packet speech |
| 3994 |
experiments. Replaced by NVP-II and ST for Internet packet speech |
| 3995 |
experiments. ST is documented in ISN 119; NVP-II is documented in |
| 3996 |
an ISI Internal memo. |
| 3997 |
|
| 3998 |
740 Braden Nov 77 NETRJS Protocol |
| 3999 |
|
| 4000 |
Defines the protocol used for Remote Job Entry on the UCLA CCN IBM |
| 4001 |
system; replaces RFCs 599 and 189. |
| 4002 |
|
| 4003 |
739 Postel Nov 77 Assigned Numbers |
| 4004 |
|
| 4005 |
This RFC has been replaced by RFCs 997 and 990. |
| 4006 |
|
| 4007 |
738 Harrenstien Oct 77 Time Server |
| 4008 |
|
| 4009 |
Defines the Time Server Protocol; see IEN 142 for the TCP and VDP |
| 4010 |
versions. |
| 4011 |
|
| 4012 |
737 Harrenstien Oct 77 FTP Extension: XSEN |
| 4013 |
|
| 4014 |
An extension to the Mail procedures. This function is |
| 4015 |
incorporated in the SMTP; see also <a href="./rfc821">RFC 821</a>. |
| 4016 |
|
| 4017 |
736 Crispin Oct 77 Telnet SUPDUP Option |
| 4018 |
|
| 4019 |
Defines the procedure for negotiating to use the SUPDUP, protocol |
| 4020 |
as a Telnet option; see also RFCs 734, 746, 747 and 749. |
| 4021 |
|
| 4022 |
735 Crocker Nov 77 Revised Telnet Byte Macro Option |
| 4023 |
|
| 4024 |
Defines a Telnet option for assigning codes to stand for strings |
| 4025 |
in Telnet connections. Replaces <a href="./rfc729">RFC 729</a>. Obsoletes NIC 40306. |
| 4026 |
|
| 4027 |
|
| 4028 |
|
| 4029 |
|
| 4030 |
|
| 4031 |
<span class="grey">Reynolds & Postel [Page 72]</span></pre> |
| 4032 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-73" ></span> |
| 4033 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 4034 |
|
| 4035 |
|
| 4036 |
734 Crispin Oct 77 SUPDUP Protocol |
| 4037 |
|
| 4038 |
Description of a terminal control protocol used at Stanford and |
| 4039 |
MIT; see also RFCs 736, 746-749. |
| 4040 |
|
| 4041 |
733 Crocker Nov 77 Standard for the Format of ARPA |
| 4042 |
Network Text Messages |
| 4043 |
|
| 4044 |
Specification of the format for the headers of computer mail. An |
| 4045 |
old version; see <a href="./rfc822">RFC 822</a>. |
| 4046 |
|
| 4047 |
732 Day Sep 77 Telnet Data Entry Terminal Option |
| 4048 |
|
| 4049 |
The specification of a Telnet Option for the control of a data |
| 4050 |
entry display terminal. Replaces <a href="./rfc731">RFC 731</a>. |
| 4051 |
|
| 4052 |
731 Day Jun 77 Telnet Data Entry Terminal Option |
| 4053 |
|
| 4054 |
An old version; see <a href="./rfc732">RFC 732</a>. |
| 4055 |
|
| 4056 |
730 Postel May 77 Extensible Field Addressing |
| 4057 |
|
| 4058 |
Discusses some ideas on addressing that come up in the context of |
| 4059 |
changing from 8-bit to 24-bit network addresses. |
| 4060 |
|
| 4061 |
729 Crocker May 77 Telnet Byte Macro Option |
| 4062 |
|
| 4063 |
An old version; see <a href="./rfc735">RFC 735</a>. |
| 4064 |
|
| 4065 |
728 Day Apr 77 A Minor Pitfall in the Telnet |
| 4066 |
Protocol |
| 4067 |
|
| 4068 |
This RFC warns of the possibility of an unexpected occurence in |
| 4069 |
Telnet resulting from the interaction between option |
| 4070 |
subnegotiations and the Telnet SYNCH operation. |
| 4071 |
|
| 4072 |
727 Crispin Apr 77 Telnet Logout Option |
| 4073 |
|
| 4074 |
Defines a Telnet option for causing a logout. |
| 4075 |
|
| 4076 |
726 Postel Mar 77 Remote Controlled Transmission and |
| 4077 |
Echoing Telnet Option |
| 4078 |
|
| 4079 |
Defines a Telnet option for controlling the transmission and |
| 4080 |
echoing of data to smooth the response to use in high transmission |
| 4081 |
delay environments; see also RFCs 719 and 718. |
| 4082 |
|
| 4083 |
|
| 4084 |
|
| 4085 |
|
| 4086 |
|
| 4087 |
<span class="grey">Reynolds & Postel [Page 73]</span></pre> |
| 4088 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-74" ></span> |
| 4089 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 4090 |
|
| 4091 |
|
| 4092 |
725 Day Mar 77 An RJE Protocol for a Resource |
| 4093 |
Sharing Network |
| 4094 |
|
| 4095 |
Describes a possible Remote Job Entry protocol. |
| 4096 |
|
| 4097 |
724 Crocker May 77 Proposed Official Standard for the |
| 4098 |
Format of ARPA Network Messages |
| 4099 |
|
| 4100 |
An old version; see <a href="./rfc822">RFC 822</a>. |
| 4101 |
|
| 4102 |
723 Never Issued. |
| 4103 |
|
| 4104 |
722 Haverty Sep 76 Thoughts on Interactions in |
| 4105 |
Distributed Services |
| 4106 |
|
| 4107 |
A discussion on the design of interactive distributed services and |
| 4108 |
the kinds of primitive operations that are needed. |
| 4109 |
|
| 4110 |
721 Garlick Sep 76 Out of Band Control Signals in a |
| 4111 |
Host to Host Protocol |
| 4112 |
|
| 4113 |
A discussion of the control signals in transport protocols (e.g., |
| 4114 |
NCP's Interrupt or TCP's Urgent). |
| 4115 |
|
| 4116 |
720 Crocker Aug 76 Address Specification Syntax for |
| 4117 |
Network Mail |
| 4118 |
|
| 4119 |
A discussion of computer mail addresses, with comments on real |
| 4120 |
names vs. mailboxes, and mailing lists; see also <a href="./rfc819">RFC 819</a>. |
| 4121 |
|
| 4122 |
719 Postel Jul 76 Discussion on RCTE |
| 4123 |
|
| 4124 |
A short discussion of RCTE implementation issues; see also RFCs |
| 4125 |
726 and 718. |
| 4126 |
|
| 4127 |
718 Postel Jun 76 Comments on RCTE from the Tenex |
| 4128 |
Implementation Experience |
| 4129 |
|
| 4130 |
A short note on the Tenex implementation of RCTE; see also RFCs |
| 4131 |
726 and 719. |
| 4132 |
|
| 4133 |
717 Postel Jul 76 Assigned Network Numbers |
| 4134 |
|
| 4135 |
This RFC has been replaced by <a href="./rfc997">RFC 997</a> and 990. |
| 4136 |
|
| 4137 |
|
| 4138 |
|
| 4139 |
|
| 4140 |
|
| 4141 |
|
| 4142 |
|
| 4143 |
<span class="grey">Reynolds & Postel [Page 74]</span></pre> |
| 4144 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-75" ></span> |
| 4145 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 4146 |
|
| 4147 |
|
| 4148 |
716 Levin May 76 Interim Revision to <a href="#appendix-F">Appendix F</a> of |
| 4149 |
BBN 1822 |
| 4150 |
|
| 4151 |
A short note updating the specification of the Very Distant Host |
| 4152 |
1822 interface. |
| 4153 |
|
| 4154 |
715 Never Issued. |
| 4155 |
|
| 4156 |
714 McKenzie Apr 76 A Host/Host Protocol for an |
| 4157 |
ARPANET-type Network |
| 4158 |
|
| 4159 |
A specification of a NCP-like protocol for an ARPA-like network. |
| 4160 |
Interesting to compare to the NCP specification to see what the |
| 4161 |
author would do differently. |
| 4162 |
|
| 4163 |
713 Haverty Apr 76 MSDTP -- Message Services Data |
| 4164 |
Transmission Protocol |
| 4165 |
|
| 4166 |
The specification of a set of Data Primitives for building |
| 4167 |
interactive services. |
| 4168 |
|
| 4169 |
712 Donnelley Feb 76 A Distributed Capability Computing |
| 4170 |
System DCCS |
| 4171 |
|
| 4172 |
A description of a Distributed Capability based computing system. |
| 4173 |
|
| 4174 |
711 Never Issued. |
| 4175 |
|
| 4176 |
710 Never Issued. |
| 4177 |
|
| 4178 |
709 Never Issued. |
| 4179 |
|
| 4180 |
708 White Jan 76 Elements of a Distributed |
| 4181 |
Programming System |
| 4182 |
|
| 4183 |
A description of a distributed programming system; see also <a href="./rfc707">RFC</a> |
| 4184 |
<a href="./rfc707">707</a>. |
| 4185 |
|
| 4186 |
707 White Dec 75 A High-Level Framework for |
| 4187 |
Network-Based Resource Sharing |
| 4188 |
|
| 4189 |
A description of a programming environment for network-based |
| 4190 |
programs; see also <a href="./rfc708">RFC 708</a>. |
| 4191 |
|
| 4192 |
706 Postel Nov 75 On the Junk Mail Problem |
| 4193 |
|
| 4194 |
A short note pointing out that the ARPANET maybe subject to a |
| 4195 |
"denial of service" attack by a misbehaving host. |
| 4196 |
|
| 4197 |
|
| 4198 |
|
| 4199 |
<span class="grey">Reynolds & Postel [Page 75]</span></pre> |
| 4200 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-76" ></span> |
| 4201 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 4202 |
|
| 4203 |
|
| 4204 |
705 Bryan Nov 75 Front-End Protocol |
| 4205 |
|
| 4206 |
This RFC describes a protocol used between a PDP-11 (the ARPANET |
| 4207 |
front end) and a B6700 to support network communication. |
| 4208 |
|
| 4209 |
704 Santos Sep 75 IMP/Host and Host/IMP Protocol |
| 4210 |
Change |
| 4211 |
|
| 4212 |
Describes the changes to the 1822 interface to eliminate the |
| 4213 |
restriction of 63 IMPs. |
| 4214 |
|
| 4215 |
703 Dodds Jul 75 Survey of New-Protocol Telnet |
| 4216 |
Servers |
| 4217 |
|
| 4218 |
A poll of Telnet servers to check implementation status and Telnet |
| 4219 |
options. Updates RFCs 702, 701, 679 and 669. |
| 4220 |
|
| 4221 |
702 Dodds Sep 74 Survey of New-Protocol Telnet |
| 4222 |
Servers |
| 4223 |
|
| 4224 |
An earlier poll of Telnet server implementation status; see also |
| 4225 |
RFC's703, 701, 679, and 669. |
| 4226 |
|
| 4227 |
701 Dodds Aug 74 Survey of New-Protocol Telnet |
| 4228 |
Servers |
| 4229 |
|
| 4230 |
An earlier poll of Telnet server implementation status; see also |
| 4231 |
RFCs 703, 702, 679 and 669. |
| 4232 |
|
| 4233 |
700 Mader Aug 74 A Protocol Experiment |
| 4234 |
|
| 4235 |
Describes a protocol based loosely on a very early version of TCP, |
| 4236 |
used to send data to a printer server. |
| 4237 |
|
| 4238 |
699 Postel Nov 82 Requests for Comments Summary |
| 4239 |
Notes: 600-699 |
| 4240 |
|
| 4241 |
A summary of the Request for Comments documents from <a href="./rfc600">RFC 600</a>-699. |
| 4242 |
|
| 4243 |
698 Tovar Jul 75 Telnet Extended ASCII Option |
| 4244 |
|
| 4245 |
Describes an option to allow transmission of a special kind of |
| 4246 |
extended ASCII used at the Stanford AI and MIT AI Labs. |
| 4247 |
|
| 4248 |
697 Lieb Jul 75 CWD Command of FTP |
| 4249 |
|
| 4250 |
Discusses FTP login access to "files only" directories. |
| 4251 |
|
| 4252 |
|
| 4253 |
|
| 4254 |
|
| 4255 |
<span class="grey">Reynolds & Postel [Page 76]</span></pre> |
| 4256 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-77" ></span> |
| 4257 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 4258 |
|
| 4259 |
|
| 4260 |
696 Cerf Jul 75 Comments on the IMP/HOST and |
| 4261 |
HOST/IMP Protocol Changes |
| 4262 |
|
| 4263 |
Observations on current international standards recommendations |
| 4264 |
from IFIP working group 6.1; see also RFCs 692, 690 687. |
| 4265 |
|
| 4266 |
695 Krilanovich Jul 75 Official Change in Host-Host |
| 4267 |
Protocol |
| 4268 |
|
| 4269 |
Corrects an ambiguity concerning the ERR command; changes NIC 8246 |
| 4270 |
and NIC 7104. |
| 4271 |
|
| 4272 |
694 Postel Jun 75 Protocol Information |
| 4273 |
|
| 4274 |
This RFC has been replaced by <a href="./rfc991">RFC 991</a>. |
| 4275 |
|
| 4276 |
693 Never Issued. |
| 4277 |
|
| 4278 |
692 Wolfe Jun 75 Comments on IMP/Host Protocol |
| 4279 |
Changes |
| 4280 |
|
| 4281 |
A proposed solution to the problem of combined length of IMP and |
| 4282 |
Host leaders; see also RFCs 696, 690 and 687. |
| 4283 |
|
| 4284 |
691 Harvey May 75 One More Try on the FTP |
| 4285 |
|
| 4286 |
A slight revision of <a href="./rfc686">RFC 686</a>, regarding the subject of print |
| 4287 |
files; see also RFCs 640, 630, 542, 454, 448, 414, 385 and 354. |
| 4288 |
|
| 4289 |
690 Postel Jun 75 Comments on the Proposed Host/IMP |
| 4290 |
Protocol Changes |
| 4291 |
|
| 4292 |
Comments on suggestions in <a href="./rfc687">RFC 687</a>; see also RFCs 692 and 696. |
| 4293 |
|
| 4294 |
689 Clements May 75 Tenex NCP Finite State Machine for |
| 4295 |
Connections |
| 4296 |
|
| 4297 |
Describes the internal states of an NCP connection in the Tenex |
| 4298 |
implementation. |
| 4299 |
|
| 4300 |
688 Walden Jun 75 Tentative Schedule for the New |
| 4301 |
Telnet Implementation for the TIP |
| 4302 |
|
| 4303 |
687 Walden Jun 75 IMP/Host and Host/IMP Protocol |
| 4304 |
Changes |
| 4305 |
|
| 4306 |
This RFC discusses addressing hosts on more than 63 IMPs, and |
| 4307 |
other backwards compatible expansions; see also RFCs 690 and 692. |
| 4308 |
|
| 4309 |
|
| 4310 |
|
| 4311 |
<span class="grey">Reynolds & Postel [Page 77]</span></pre> |
| 4312 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-78" ></span> |
| 4313 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 4314 |
|
| 4315 |
|
| 4316 |
686 Harvey May 75 Leaving Well Enough Alone |
| 4317 |
|
| 4318 |
Discusses the difference between early and later versions of FTP; |
| 4319 |
see also RFCs 691, 640, 630, 542, 454, 448, 414, 385 and 354. |
| 4320 |
|
| 4321 |
685 Beeler Apr 75 Response Time in Cross-network |
| 4322 |
Debugging |
| 4323 |
|
| 4324 |
This memo discusses the contribution of ARPANET communication to |
| 4325 |
response time. |
| 4326 |
|
| 4327 |
684 Schantz Apr 75 A Commentary on Procedure Calling as |
| 4328 |
a Network Protocol |
| 4329 |
|
| 4330 |
Describes issues in designing distributed computing systems. |
| 4331 |
Shortcomings of <a href="./rfc674">RFC 674</a>; see also RFCs 542 and 354. |
| 4332 |
|
| 4333 |
683 Clements Apr 75 FTPSRV -- Tenex Extension for Paged |
| 4334 |
Files |
| 4335 |
|
| 4336 |
Defines an extension to FTP for page-mode transfers between Tenex |
| 4337 |
systems; also discusses file transfer reliability. |
| 4338 |
|
| 4339 |
682 Never Issued. |
| 4340 |
|
| 4341 |
681 Holmgren May 75 Network Unix |
| 4342 |
|
| 4343 |
Capabilities as an ARPANET Mini-Host: standard I/O, Telnet, NCP, |
| 4344 |
Hardware/Software requirements, reliability, availability. |
| 4345 |
|
| 4346 |
680 Myer Apr 75 Message Transmission Protocol |
| 4347 |
|
| 4348 |
Extends message field definition beyond <a href="./rfc561">RFC 561</a> attempts to |
| 4349 |
establish syntactic and semantic standards for ARPANET; see also |
| 4350 |
RFCs 733 and 822. |
| 4351 |
|
| 4352 |
679 Dodds Feb 75 February, 1975, Survey of |
| 4353 |
New-Protocol Telnet Servers |
| 4354 |
|
| 4355 |
An earlier poll of Telnet server implementation status. Updates |
| 4356 |
RFCs 701, 702 and 669; see also <a href="./rfc703">RFC 703</a>. |
| 4357 |
|
| 4358 |
678 Postel Dec 74 Standard File Formats |
| 4359 |
|
| 4360 |
For transmission of documents across different environments. |
| 4361 |
|
| 4362 |
|
| 4363 |
|
| 4364 |
|
| 4365 |
|
| 4366 |
|
| 4367 |
<span class="grey">Reynolds & Postel [Page 78]</span></pre> |
| 4368 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-79" ></span> |
| 4369 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 4370 |
|
| 4371 |
|
| 4372 |
677 Johnson Jan 75 The Maintenance of Duplicate |
| 4373 |
Databases |
| 4374 |
|
| 4375 |
676 Never Issued. |
| 4376 |
|
| 4377 |
675 Cerf Dec 74 Specification of Internet |
| 4378 |
Transmission Control Program (TCP) |
| 4379 |
|
| 4380 |
The first detailed specification of TCP; see <a href="./rfc793">RFC 793</a>. |
| 4381 |
|
| 4382 |
674 Postel Dec 74 Procedure Call Documents--Version 2 |
| 4383 |
|
| 4384 |
A host level protocol used in the NSW--a slightly constrained |
| 4385 |
version of ARPANET Host-to-Host protocol, affecting allocation, |
| 4386 |
RFNM wait, and retransmission; see also <a href="./rfc684">RFC 684</a>. |
| 4387 |
|
| 4388 |
673 Never Issued. |
| 4389 |
|
| 4390 |
672 Schantz Dec 74 A Multi-Site Data Collection |
| 4391 |
Facility |
| 4392 |
|
| 4393 |
Applicability of TIP/Tenex protocols beyond TIP accounting. |
| 4394 |
|
| 4395 |
671 Schantz Dec 74 A Note on Reconnection Protocol |
| 4396 |
|
| 4397 |
Experience with implementation in RSEXEC context. |
| 4398 |
|
| 4399 |
670 Never Issued. |
| 4400 |
|
| 4401 |
669 Dodds Dec 74 November 1974, Survey of |
| 4402 |
New-Protocol Telnet Servers |
| 4403 |
|
| 4404 |
An earlier poll of Telnet server implementation status. Updates |
| 4405 |
<a href="./rfc702">RFC 702</a>; see also RFCs 703 and 679. |
| 4406 |
|
| 4407 |
668 Never Issued. |
| 4408 |
|
| 4409 |
667 Chipman Dec 74 BBN Host Ports |
| 4410 |
|
| 4411 |
Approved scheme to connect host ports to the network. |
| 4412 |
|
| 4413 |
666 Padlipsky Nov 74 Specification of the Unified |
| 4414 |
User-Level Protocol |
| 4415 |
|
| 4416 |
Discusses and proposes a common command language. |
| 4417 |
|
| 4418 |
665 Never Issued. |
| 4419 |
|
| 4420 |
664 Never Issued. |
| 4421 |
|
| 4422 |
|
| 4423 |
<span class="grey">Reynolds & Postel [Page 79]</span></pre> |
| 4424 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-80" ></span> |
| 4425 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 4426 |
|
| 4427 |
|
| 4428 |
663 Kanodia Nov 74 A Lost Message Detection and |
| 4429 |
Recovery Protocol |
| 4430 |
|
| 4431 |
Proposed extension of host-host protocol; see also RFCs 534, 516, |
| 4432 |
512, 492 and 467. |
| 4433 |
|
| 4434 |
662 Kanodia Nov 74 Performance Improvement in ARPANET |
| 4435 |
File Transfers from Multics |
| 4436 |
|
| 4437 |
Experimenting with host output buffers to improve throughput. |
| 4438 |
|
| 4439 |
661 Postel Nov 74 Protocol Information |
| 4440 |
|
| 4441 |
This RFC has been replaced by <a href="./rfc991">RFC 991</a>. |
| 4442 |
|
| 4443 |
660 Walden Oct 74 Some Changes to the IMP and the |
| 4444 |
IMP/Host Interface |
| 4445 |
|
| 4446 |
Decoupling of message number sequences of hosts; host-host access |
| 4447 |
control; message number window; messages outside normal mechanism; |
| 4448 |
see also BBN 1822. |
| 4449 |
|
| 4450 |
659 Postel Oct 74 Announcing Additional Telnet Options |
| 4451 |
|
| 4452 |
Options defined in RFCs 651-658. |
| 4453 |
|
| 4454 |
658 Crocker Oct 74 Telnet Output Line Feed Disposition |
| 4455 |
|
| 4456 |
Defines a Telnet option for specific control of Line Feed. |
| 4457 |
|
| 4458 |
657 Crocker Oct 74 Telnet Output Vertical Tab |
| 4459 |
Disposition Option |
| 4460 |
|
| 4461 |
Defines a Telnet option for specific control of Vertical Tab. |
| 4462 |
|
| 4463 |
656 Crocker Oct 74 Telnet Output Vertical Tab Stops |
| 4464 |
Option |
| 4465 |
|
| 4466 |
Defines a Telnet option for setting the stops for Vertical Tab. |
| 4467 |
|
| 4468 |
655 Crocker Oct 74 Telnet Output Form Feed Disposition |
| 4469 |
Option |
| 4470 |
|
| 4471 |
Defines a Telnet option for specific control of Form Feed. |
| 4472 |
|
| 4473 |
|
| 4474 |
|
| 4475 |
|
| 4476 |
|
| 4477 |
|
| 4478 |
|
| 4479 |
<span class="grey">Reynolds & Postel [Page 80]</span></pre> |
| 4480 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-81" ></span> |
| 4481 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 4482 |
|
| 4483 |
|
| 4484 |
654 Crocker Oct 74 Telnet Output Horizontal Tab |
| 4485 |
Disposition Option |
| 4486 |
|
| 4487 |
Defines a Telnet option for specific control of Horizontal Tab. |
| 4488 |
|
| 4489 |
653 Crocker Oct 74 Telnet Output Horizontal Tab Stops |
| 4490 |
Option |
| 4491 |
|
| 4492 |
Defines a Telnet option for setting the stops for Horizontal Tab. |
| 4493 |
|
| 4494 |
652 Crocker Oct 74 Telnet Output Carriage Return |
| 4495 |
Disposition Option |
| 4496 |
|
| 4497 |
Defines a Telnet option for specific control of Carriage Return. |
| 4498 |
|
| 4499 |
651 Crocker Oct 74 Revised Telnet Status Option |
| 4500 |
|
| 4501 |
Revises the Telnet Option for communicating the status of all |
| 4502 |
Telnet options over the network. |
| 4503 |
|
| 4504 |
650 Never Issued. |
| 4505 |
|
| 4506 |
649 Never Issued. |
| 4507 |
|
| 4508 |
648 Never Issued. |
| 4509 |
|
| 4510 |
647 Padlipsky Nov 74 A Proposed Protocol for Connecting |
| 4511 |
Host Computers to ARPA-Like Networks |
| 4512 |
via Front End Processors |
| 4513 |
|
| 4514 |
Approaches to Front-End protocol processing using available |
| 4515 |
hardware and software. |
| 4516 |
|
| 4517 |
646 Never Issued. |
| 4518 |
|
| 4519 |
645 Crocker Jun 74 Network Standard Data Specification |
| 4520 |
Syntax |
| 4521 |
|
| 4522 |
Providing a mechanism for specifying all attributes of a |
| 4523 |
collection of bits; see also <a href="./rfc615">RFC 615</a>. |
| 4524 |
|
| 4525 |
644 Thomas Jul 74 On The Problem of Signature |
| 4526 |
Authentication for Network Mail |
| 4527 |
|
| 4528 |
Proposes that the mail sender be an authorized system process and |
| 4529 |
that the mail sender and mail receiver processes exchange a |
| 4530 |
password. The sender process takes responsibility for |
| 4531 |
authentication of the signature on the mail. |
| 4532 |
|
| 4533 |
|
| 4534 |
|
| 4535 |
<span class="grey">Reynolds & Postel [Page 81]</span></pre> |
| 4536 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-82" ></span> |
| 4537 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 4538 |
|
| 4539 |
|
| 4540 |
643 Mader Jul 74 Network Debugging Protocol |
| 4541 |
|
| 4542 |
To be used in an implementation of a PDP-11 network bootstrap |
| 4543 |
device and a cross-network debugger. |
| 4544 |
|
| 4545 |
642 Burchfiel Jul 74 Ready Line Philosophy and |
| 4546 |
Implementation |
| 4547 |
|
| 4548 |
641 Never Issued. |
| 4549 |
|
| 4550 |
640 Postel Jun 74 Revised FTP Reply Codes |
| 4551 |
|
| 4552 |
Updates <a href="./rfc542">RFC 542</a>. |
| 4553 |
|
| 4554 |
639 Never Issued. |
| 4555 |
|
| 4556 |
638 McKenzie Apr 74 IMP/TIP Preventive Maintenance |
| 4557 |
Schedule |
| 4558 |
|
| 4559 |
Corrects <a href="./rfc633">RFC 633</a>. |
| 4560 |
|
| 4561 |
637 McKenzie Apr 74 Change of Network Address for SU-DSL |
| 4562 |
|
| 4563 |
A host at Stanford changes its address from 2/2 to 2/3. |
| 4564 |
|
| 4565 |
636 Burchfiel Jun 74 TIP/TENEX Reliability Improvements |
| 4566 |
|
| 4567 |
Obtaining/maintaining connections; recovery from lost connections; |
| 4568 |
connection-state changes. |
| 4569 |
|
| 4570 |
635 Cerf Apr 74 An Assessment of ARPANET Protocols |
| 4571 |
|
| 4572 |
Theoretical and practical motivation for redesign. Multipacket |
| 4573 |
messages; host retransmission; duplicate detection; sequencing; |
| 4574 |
acknowledgement. |
| 4575 |
|
| 4576 |
634 McKenzie Apr 74 Change in Network Address for |
| 4577 |
Haskins Lab. |
| 4578 |
|
| 4579 |
A host a Haskins Lab changes its address from 5/3 to 9/3. |
| 4580 |
|
| 4581 |
633 McKenzie Mar 74 IMP/TIP Preventive Maintenance |
| 4582 |
Schedule |
| 4583 |
|
| 4584 |
An old version; see <a href="./rfc638">RFC 638</a>. |
| 4585 |
|
| 4586 |
|
| 4587 |
|
| 4588 |
|
| 4589 |
|
| 4590 |
|
| 4591 |
<span class="grey">Reynolds & Postel [Page 82]</span></pre> |
| 4592 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-83" ></span> |
| 4593 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 4594 |
|
| 4595 |
|
| 4596 |
632 Opderbeck May 74 Throughput Degradations for Single |
| 4597 |
Packet Messages |
| 4598 |
|
| 4599 |
A study of packet throughput. |
| 4600 |
|
| 4601 |
631 Danthine Apr 74 Call for Papers: International |
| 4602 |
Meeting on Minicomputers and Data |
| 4603 |
Communication |
| 4604 |
|
| 4605 |
A meeting on data communications held January 1975 in Liege, |
| 4606 |
Belgium. |
| 4607 |
|
| 4608 |
630 Sussman Apr 74 FTP Error Code Usage for More |
| 4609 |
Reliable Mail Service |
| 4610 |
|
| 4611 |
Describes FTP reply-code usage in TENEX mail processing. |
| 4612 |
|
| 4613 |
629 North Mar 74 Scenario for Using the Network |
| 4614 |
Journal |
| 4615 |
|
| 4616 |
An example of how to access information in the NIC's Journal |
| 4617 |
database. |
| 4618 |
|
| 4619 |
628 Keeney Mar 74 Status of RFC Numbers and a Note on |
| 4620 |
Pre-assigned Journal Numbers |
| 4621 |
|
| 4622 |
A method for getting the next RFC number to use on a new memo. |
| 4623 |
|
| 4624 |
627 Feinler Mar 74 ASCII Text File of Hostnames |
| 4625 |
|
| 4626 |
See also RFCs 606, 608, 623 and 625. |
| 4627 |
|
| 4628 |
626 Kleinrock Mar 74 On a possible Lockup Condition in |
| 4629 |
IMP Subnet due to Message Sequencing |
| 4630 |
|
| 4631 |
A potential problem in the IMP processing of messages. A detailed |
| 4632 |
description of how this condition can arise. |
| 4633 |
|
| 4634 |
625 Feinler Mar 74 On Line Hostnames Service |
| 4635 |
|
| 4636 |
See also RFCs 606, 608, 623 and 627. |
| 4637 |
|
| 4638 |
624 Krilanovich Feb 74 Comments on the File Transfer |
| 4639 |
Protocol |
| 4640 |
|
| 4641 |
Design changes and slight modifications. Replaces <a href="./rfc607">RFC 607</a>; see |
| 4642 |
also RFCs 614, 542 and 640. |
| 4643 |
|
| 4644 |
|
| 4645 |
|
| 4646 |
|
| 4647 |
<span class="grey">Reynolds & Postel [Page 83]</span></pre> |
| 4648 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-84" ></span> |
| 4649 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 4650 |
|
| 4651 |
|
| 4652 |
623 Krilanovich Feb 74 Comments on On-Line Host Name |
| 4653 |
Service |
| 4654 |
|
| 4655 |
See also RFCs 627, 625, 608 and 606. |
| 4656 |
|
| 4657 |
622 McKenzie Mar 74 Scheduling IMP/TIP Down Time |
| 4658 |
|
| 4659 |
Modification of previous policy. |
| 4660 |
|
| 4661 |
621 Kudlick Mar 74 NIC User Directories at SRI-ARC |
| 4662 |
|
| 4663 |
Changes in user accounts at the NIC. |
| 4664 |
|
| 4665 |
620 Ferguson Mar 74 Request for Monitor Host Table |
| 4666 |
Updates |
| 4667 |
|
| 4668 |
Changes in the hosts Office-1 and SRI-ARC. |
| 4669 |
|
| 4670 |
619 Naylor Mar 74 Mean Round-Trip Times in the ARPANET |
| 4671 |
|
| 4672 |
Actual measurements of round-trip times. |
| 4673 |
|
| 4674 |
618 Taft Feb 74 A Few Observations on NCP Statistics |
| 4675 |
|
| 4676 |
Distribution of NCP and IMP message types by actual measurement. |
| 4677 |
|
| 4678 |
617 Taft Feb 74 A Note on Socket Number Assignment |
| 4679 |
|
| 4680 |
Danger of imposing more fixed socket number requirements; see also |
| 4681 |
RFCs 542, 503 and 451. |
| 4682 |
|
| 4683 |
616 Walden Feb 74 Latest Network Maps |
| 4684 |
|
| 4685 |
Geographic ad Topologic maps of the ARPANET of January 1974. |
| 4686 |
|
| 4687 |
615 Crocker Mar 74 Proposed Network Standard Data |
| 4688 |
Pathname Syntax |
| 4689 |
|
| 4690 |
A suggestion for a network wide standard for naming data (such as |
| 4691 |
files). |
| 4692 |
|
| 4693 |
614 Pogran Jan 74 Response to <a href="./rfc607">RFC 607</a> (NIC-21255), |
| 4694 |
"Comments on the FTP" |
| 4695 |
|
| 4696 |
See also RFCs 624, 542 and 640. |
| 4697 |
|
| 4698 |
|
| 4699 |
|
| 4700 |
|
| 4701 |
|
| 4702 |
|
| 4703 |
<span class="grey">Reynolds & Postel [Page 84]</span></pre> |
| 4704 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-85" ></span> |
| 4705 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 4706 |
|
| 4707 |
|
| 4708 |
613 McKenzie Jan 74 Network Connectivity: A Response to |
| 4709 |
<a href="./rfc603">RFC 603</a> |
| 4710 |
|
| 4711 |
Remarks about connectivity and robustness of networks. |
| 4712 |
|
| 4713 |
612 McKenzie Jan 74 Traffic Statistics |
| 4714 |
|
| 4715 |
A report on Host traffic statistics for the month of December |
| 4716 |
1973. Updates <a href="./rfc601">RFC 601</a>. |
| 4717 |
|
| 4718 |
611 Walden Feb 74 Two Changes to the IMP/Host Protocol |
| 4719 |
|
| 4720 |
Expansion of Host-Going-Down and addition of Dead-Host-Status |
| 4721 |
Message. |
| 4722 |
|
| 4723 |
610 Winter Dec 73 Further Datalanguage Design Concepts |
| 4724 |
|
| 4725 |
Preliminary results of the language design; a model for data |
| 4726 |
languagea semantics; future considerations. |
| 4727 |
|
| 4728 |
609 Ferguson Jan 74 Statement of Upcoming Move of |
| 4729 |
NIC/NLS Service |
| 4730 |
|
| 4731 |
See also RFCs 621 and 620. |
| 4732 |
|
| 4733 |
608 Feinler Jan 73 Host Names On-Line |
| 4734 |
|
| 4735 |
Response to <a href="./rfc606">RFC 606</a>; see also RFCs 627, 625 and 623. |
| 4736 |
|
| 4737 |
607 Krilanovich Jan 73 NIC-21255 Comments on the File |
| 4738 |
Transfer Protocol |
| 4739 |
|
| 4740 |
An old version; see <a href="./rfc624">RFC 624</a>; see also RFCs 614, 542 and 640. |
| 4741 |
|
| 4742 |
606 Deutsch Dec 73 Host Names On-Line |
| 4743 |
|
| 4744 |
Resolving differences in hostname-address mappings; see also RFCs |
| 4745 |
627, 625, 623 and 608. |
| 4746 |
|
| 4747 |
605 Never Issued. |
| 4748 |
|
| 4749 |
604 Postel Dec 73 Assigned Link Numbers |
| 4750 |
|
| 4751 |
Modifies official host-host protocol. Replaced by RFCs 997 and |
| 4752 |
990. |
| 4753 |
|
| 4754 |
|
| 4755 |
|
| 4756 |
|
| 4757 |
|
| 4758 |
|
| 4759 |
<span class="grey">Reynolds & Postel [Page 85]</span></pre> |
| 4760 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-86" ></span> |
| 4761 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 4762 |
|
| 4763 |
|
| 4764 |
603 Burchfiel Dec 73 Response to <a href="./rfc597">RFC 597</a>: Host Status |
| 4765 |
|
| 4766 |
Questions about the ARPANET topology described in <a href="./rfc597">RFC 597</a>. |
| 4767 |
|
| 4768 |
602 Metcalfe Dec 73 "The Stockings Were Hung by the |
| 4769 |
Chimney With Care" |
| 4770 |
|
| 4771 |
Susceptibility of ARPANET to security violations. |
| 4772 |
|
| 4773 |
601 McKenzie Dec 73 Traffic Statistics |
| 4774 |
|
| 4775 |
A report on Host traffic statistics for the month of November |
| 4776 |
1973. Updates <a href="./rfc586">RFC 586</a>. |
| 4777 |
|
| 4778 |
600 Berggreen Nov 73 Interfacing an Illinois Plasma |
| 4779 |
Terminal to the ARPANET |
| 4780 |
|
| 4781 |
Discusses plans to map Plato terminal codes to network ASCII for |
| 4782 |
accessing the Plato system via the network using Telnet. |
| 4783 |
|
| 4784 |
599 Braden Dec 73 Update on NETRJS |
| 4785 |
|
| 4786 |
A status report and update on UCLA-CCN's remote job entry service. |
| 4787 |
|
| 4788 |
598 NICSTA Dec 73 RFC Index - December 5, 1973 |
| 4789 |
|
| 4790 |
Lists RFCs 1-593. |
| 4791 |
|
| 4792 |
597 Neigus Dec 73 Host Status |
| 4793 |
|
| 4794 |
This RFC provides the most current network maps, geographic and |
| 4795 |
logical, plus a list of hosts connected to the ARPANET. |
| 4796 |
|
| 4797 |
596 Taft Dec 73 Second Thoughts on Telnet Go-Ahead |
| 4798 |
|
| 4799 |
Cited objections to the requirement that hosts implement the |
| 4800 |
Telnet Go-Ahead (GA) command, as specified in the Telnet Protocol |
| 4801 |
Specification. |
| 4802 |
|
| 4803 |
595 Hathaway Dec 73 Some Thoughts in Defense of the |
| 4804 |
Telnet Go-Ahead |
| 4805 |
|
| 4806 |
This RFC is in reply to <a href="./rfc596">RFC 596</a>. |
| 4807 |
|
| 4808 |
594 Burchfiel Dec 73 Speedup of Host-IMP Interface |
| 4809 |
|
| 4810 |
A discussion on how to make the full performance capabilities of |
| 4811 |
the subnet available for interprocess communication. |
| 4812 |
|
| 4813 |
|
| 4814 |
|
| 4815 |
<span class="grey">Reynolds & Postel [Page 86]</span></pre> |
| 4816 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-87" ></span> |
| 4817 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 4818 |
|
| 4819 |
|
| 4820 |
593 McKenzie Nov 73 Telnet and FTP Implementation |
| 4821 |
Schedule Change |
| 4822 |
|
| 4823 |
592 Watson Nov 73 Some Thoughts on System Design to |
| 4824 |
Facilitate Resource Sharing |
| 4825 |
|
| 4826 |
Proposes a system interconnection approach which would help in |
| 4827 |
moving toward more resource sharing on the ARPANET. |
| 4828 |
|
| 4829 |
591 Walden Nov 73 Addition to the Very Distant Host |
| 4830 |
Specification |
| 4831 |
|
| 4832 |
A sentence correction notation that should be inserted in <a href="#appendix-F">Appendix</a> |
| 4833 |
<a href="#appendix-F">F</a> of BBN Report 1822. |
| 4834 |
|
| 4835 |
590 Padlipsky Nov 73 MULTICS Address Change |
| 4836 |
|
| 4837 |
Announcement of a plan to change the address of MIT Multics. |
| 4838 |
|
| 4839 |
589 Braden Nov 73 CCN NETRJS Server Messages to Remote |
| 4840 |
User |
| 4841 |
|
| 4842 |
Describes the system to user messages at UCLA-CCN's remote job |
| 4843 |
entry service. |
| 4844 |
|
| 4845 |
588 Stokes Oct 73 London Node is now up |
| 4846 |
|
| 4847 |
Notice that an ARPANET node is operational at University College, |
| 4848 |
London. |
| 4849 |
|
| 4850 |
587 Postel Nov 73 Announcing New Telnet Options |
| 4851 |
|
| 4852 |
Announcement of Negotiate About Output Line Width (NAOL), and |
| 4853 |
Negotiate About Output Page Size (NAOP). |
| 4854 |
|
| 4855 |
586 McKenzie Nov 73 Traffic Statistics |
| 4856 |
|
| 4857 |
A report on the Host traffic statistics for the month of |
| 4858 |
October 1973. Updates <a href="./rfc579">RFC 579</a>. |
| 4859 |
|
| 4860 |
585 Crocker Nov 73 ARPANET Users Interest Working Group |
| 4861 |
Meeting |
| 4862 |
|
| 4863 |
Meeting notes of the first Users Interest Working Group. |
| 4864 |
|
| 4865 |
|
| 4866 |
|
| 4867 |
|
| 4868 |
|
| 4869 |
|
| 4870 |
|
| 4871 |
<span class="grey">Reynolds & Postel [Page 87]</span></pre> |
| 4872 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-88" ></span> |
| 4873 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 4874 |
|
| 4875 |
|
| 4876 |
584 Iseli Nov 73 Charter for ARPANET Users Interest |
| 4877 |
Working Group |
| 4878 |
|
| 4879 |
Describes the background, membership, and scope of the newly |
| 4880 |
formed Users Interest Working Group. |
| 4881 |
|
| 4882 |
583 Never Issued. |
| 4883 |
|
| 4884 |
582 Clements Nov 73 Comments on <a href="./rfc580">RFC 580</a> - Machine |
| 4885 |
Readable Protocols |
| 4886 |
|
| 4887 |
Cites objections to the phrase "preferably NLS files". |
| 4888 |
|
| 4889 |
581 Crocker Nov 73 Corrections to <a href="./rfc560">RFC 560</a> - Remote |
| 4890 |
Controlled Transmission and Echoing |
| 4891 |
Telnet Option |
| 4892 |
|
| 4893 |
This RFC contains corrections to <a href="./rfc560">RFC 560</a>, which described the |
| 4894 |
Remote Controlled Transmission and Echoing Telnet Option. |
| 4895 |
|
| 4896 |
580 Postel Oct 73 Note to Protocol Designers and |
| 4897 |
Implementers |
| 4898 |
|
| 4899 |
An announcement that future proposed protocols shall be submitted |
| 4900 |
in the form of on-line documents, preferably in NLS files, to the |
| 4901 |
Network Information Center. |
| 4902 |
|
| 4903 |
579 McKenzie Oct 73 Traffic Statistics |
| 4904 |
|
| 4905 |
A report on the Host traffic statistics for the month of |
| 4906 |
September 1973. Updates <a href="./rfc566">RFC 566</a>. |
| 4907 |
|
| 4908 |
578 Bhushan Oct 73 Using MIT-MATHLAB MACSYMA From |
| 4909 |
MIT-DMS Muddle - An Experiment in |
| 4910 |
Automated Resource Sharing |
| 4911 |
|
| 4912 |
This paper describes an experiment in non-trivial automated |
| 4913 |
resource sharing between dissimilar systems. The goal of this |
| 4914 |
experiment was to interface the Muddle system at MIT-DMS to the |
| 4915 |
MACSYMA system at MIT-Mathlab. |
| 4916 |
|
| 4917 |
577 Crocker Oct 73 Mail Priority |
| 4918 |
|
| 4919 |
A paper that suggests interpretations for urgency values, based on |
| 4920 |
arguments presented in <a href="./rfc555">RFC 555</a>. References <a href="./rfc539">RFC 539</a>. |
| 4921 |
|
| 4922 |
|
| 4923 |
|
| 4924 |
|
| 4925 |
|
| 4926 |
|
| 4927 |
<span class="grey">Reynolds & Postel [Page 88]</span></pre> |
| 4928 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-89" ></span> |
| 4929 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 4930 |
|
| 4931 |
|
| 4932 |
576 Victor Sep 73 Proposal for Modifying Linking |
| 4933 |
|
| 4934 |
This RFC presents a plan to modify the link jsys in Tenex to work |
| 4935 |
in a better way in terms of the user interface. |
| 4936 |
|
| 4937 |
575 Never Issued. |
| 4938 |
|
| 4939 |
574 Krilanovich Sep 73 Announcement of a Mail Facility at |
| 4940 |
UCSB |
| 4941 |
|
| 4942 |
An announcement of a server program which supports that subset of |
| 4943 |
the File Transfer Protocol necessary for mail delivery. |
| 4944 |
|
| 4945 |
573 Bhushan Sep 73 Data and File Transfer - Some |
| 4946 |
Measurement Results |
| 4947 |
|
| 4948 |
A report on the results of the performance of MIT-DM's FTP-user |
| 4949 |
and FTP-server programs. |
| 4950 |
|
| 4951 |
572 Never Issued. |
| 4952 |
|
| 4953 |
571 Braden Nov 73 Tenex FTP Problem |
| 4954 |
|
| 4955 |
A report on a problem in the current Tenex implementation which is |
| 4956 |
likely to cause incorrect results when transferring files to a |
| 4957 |
non-Tenex site. |
| 4958 |
|
| 4959 |
570 Pickens Oct 73 Experimental Input Mapping Between |
| 4960 |
NVT ASCII and UCSB Online System |
| 4961 |
|
| 4962 |
This RFC updates <a href="./rfc216">RFC 216</a>. This document describes the proposed |
| 4963 |
solutions from the requests to improve the human interface to the |
| 4964 |
UCSB On-Line System. |
| 4965 |
|
| 4966 |
569 Padlipsky Oct 73 NETED: A Common Editor for the ARPA |
| 4967 |
Network |
| 4968 |
|
| 4969 |
Defines a simple line style text editor and suggests that it be |
| 4970 |
made available on every host in the network. |
| 4971 |
|
| 4972 |
568 McQuillan Sep 73 Response to <a href="./rfc567">RFC 567</a> - Cross-Country |
| 4973 |
Network Bandwidth |
| 4974 |
|
| 4975 |
This RFC serves as a brief correction to several fundamental |
| 4976 |
errors in <a href="./rfc567">RFC 567</a>. |
| 4977 |
|
| 4978 |
|
| 4979 |
|
| 4980 |
|
| 4981 |
|
| 4982 |
|
| 4983 |
<span class="grey">Reynolds & Postel [Page 89]</span></pre> |
| 4984 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-90" ></span> |
| 4985 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 4986 |
|
| 4987 |
|
| 4988 |
567 Deutsch Sep 73 Cross-Country Network Bandwidth |
| 4989 |
|
| 4990 |
Computation of cross-country network bandwidth. |
| 4991 |
|
| 4992 |
566 McKenzie Sep 73 Traffic Statistics |
| 4993 |
|
| 4994 |
A report on the Host traffic statistics for the month of |
| 4995 |
August 1973. Updates <a href="./rfc556">RFC 556</a>. |
| 4996 |
|
| 4997 |
565 Cantor Aug 73 Storing Network Survey Data at the |
| 4998 |
Datacomputer |
| 4999 |
|
| 5000 |
A project summary report describing the programs developed and |
| 5001 |
implemented that have been operating successfully with the |
| 5002 |
datacomputer since July 10. |
| 5003 |
|
| 5004 |
564 Never Issued. |
| 5005 |
|
| 5006 |
563 Davidson Aug 73 Comments on the RCTE Telnet Option |
| 5007 |
|
| 5008 |
A critique based on inferences drawn from the sample Tenex |
| 5009 |
interaction in <a href="./rfc560">RFC 560</a>. |
| 5010 |
|
| 5011 |
562 McKenzie Aug 73 Modifications to the Telnet |
| 5012 |
Specification |
| 5013 |
|
| 5014 |
Presenting two documents that update <a href="./rfc495">RFC 495</a>, plus summarizing the |
| 5015 |
changes. |
| 5016 |
|
| 5017 |
561 Bhushan Sep 73 Standardizing Network Mail Headers |
| 5018 |
|
| 5019 |
A proposed document for the explicit specification of such header |
| 5020 |
information as author, title, and date within the current FTP mail |
| 5021 |
protocol. |
| 5022 |
|
| 5023 |
560 Crocker Aug 73 Remote Controlled Transmission and |
| 5024 |
Echoing Telnet Option |
| 5025 |
|
| 5026 |
Defines a Telnet option for detailed control of echoing to promote |
| 5027 |
interactive use on long delay paths. |
| 5028 |
|
| 5029 |
559 Bhushan Aug 73 Comments on the New Telnet Protocol |
| 5030 |
and Its Implementation |
| 5031 |
|
| 5032 |
This RFC describes the experience that MIT-DM had with the |
| 5033 |
implementation of the new Telnet protocol (both server and user). |
| 5034 |
|
| 5035 |
558 Never Issued. |
| 5036 |
|
| 5037 |
|
| 5038 |
|
| 5039 |
<span class="grey">Reynolds & Postel [Page 90]</span></pre> |
| 5040 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-91" ></span> |
| 5041 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 5042 |
|
| 5043 |
|
| 5044 |
557 Wessler Aug 73 Revelations in Network Host |
| 5045 |
Measurements |
| 5046 |
|
| 5047 |
A report to the RFC community on the current network host |
| 5048 |
measurements. |
| 5049 |
|
| 5050 |
556 McKenzie Aug 73 Traffic Statistics |
| 5051 |
|
| 5052 |
A report on the Host traffic statistics for the month of |
| 5053 |
July 1973. Updates <a href="./rfc538">RFC 538</a>. |
| 5054 |
|
| 5055 |
555 White Jul 73 Response to Critiques of the |
| 5056 |
Proposed Mail Protocol |
| 5057 |
|
| 5058 |
Response to the proposal for a Mail Protocol (<a href="./rfc524">RFC 524</a>). |
| 5059 |
|
| 5060 |
554 Never Issued. |
| 5061 |
|
| 5062 |
553 Thomas Jul 73 Draft Design for a Text/Graphics |
| 5063 |
Protocol |
| 5064 |
|
| 5065 |
This document was proposed as a synthesis of existing ideas rather |
| 5066 |
than an attempt to put forth new ones. It draws upon the concerns |
| 5067 |
about the lack of text-handling capabilities of the protoocl |
| 5068 |
suggested in <a href="./rfc493">RFC 493</a>. |
| 5069 |
|
| 5070 |
552 Owen Jul 73 Single Access to Standard Protocols |
| 5071 |
|
| 5072 |
Queries and statements regarding a socket number assignment for a |
| 5073 |
single access protocol before the proposed mail protocol becomes |
| 5074 |
official. |
| 5075 |
|
| 5076 |
551 Feinroth Aug 73 NYU, ANL, and LBL Joining the Net |
| 5077 |
|
| 5078 |
Announcement of the intent of several Atomic Energy Commission |
| 5079 |
installations to enter the network. |
| 5080 |
|
| 5081 |
550 Deutsch Aug 73 NIC NCP Experiment |
| 5082 |
|
| 5083 |
Statistics on total incoming messages, incoming host-host control |
| 5084 |
opcodes, and size of outgoing messages. |
| 5085 |
|
| 5086 |
549 Michener Jul 73 Minutes of Network Graphics Group |
| 5087 |
Meeting |
| 5088 |
|
| 5089 |
Description of a meeting on graphics held in July 1973. |
| 5090 |
|
| 5091 |
|
| 5092 |
|
| 5093 |
|
| 5094 |
|
| 5095 |
<span class="grey">Reynolds & Postel [Page 91]</span></pre> |
| 5096 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-92" ></span> |
| 5097 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 5098 |
|
| 5099 |
|
| 5100 |
548 Walden Aug 73 Hosts Using the IMP Going Down |
| 5101 |
Message |
| 5102 |
|
| 5103 |
Discusses the user and intention of the ARPANET IMP's "going down" |
| 5104 |
message. |
| 5105 |
|
| 5106 |
547 Walden Aug 73 Change to the Very Distant Host |
| 5107 |
Specification |
| 5108 |
|
| 5109 |
A document on a new version of figure F-4 for BBN Report 1822. |
| 5110 |
|
| 5111 |
546 Thomas Aug 73 Tenex Load Averages for July 1973 |
| 5112 |
|
| 5113 |
Report on the load on two of the key service computers on the |
| 5114 |
ARPANET. |
| 5115 |
|
| 5116 |
545 Pickens Jul 73 Of What Quality be the UCSB Resource |
| 5117 |
Evaluators? |
| 5118 |
|
| 5119 |
This memo is in response to <a href="./rfc531">RFC 531</a>. |
| 5120 |
|
| 5121 |
544 Meyer Jul 73 Locating On-Line Documentation at |
| 5122 |
SRI-ARC |
| 5123 |
|
| 5124 |
Updated memo on how to access on-line documentation at the NIC. |
| 5125 |
|
| 5126 |
543 Meyer Jul 73 Network Journal Submission and |
| 5127 |
Delivery |
| 5128 |
|
| 5129 |
Announcement that the first implementation of a Network Journal |
| 5130 |
Submission and Delivery system is now experimentally up. |
| 5131 |
|
| 5132 |
542 Neigus Jul 73 File Transfer Protocol |
| 5133 |
|
| 5134 |
This RFC states that there are considerable changes from the last |
| 5135 |
"official" version of FTP, but the gross structure still remains |
| 5136 |
the same. References RFCs 354, 454, and 495. |
| 5137 |
|
| 5138 |
541 Never Issued. |
| 5139 |
|
| 5140 |
540 Never Issued. |
| 5141 |
|
| 5142 |
539 Crocker Jul 73 Thoughts on the Mail Protocol |
| 5143 |
Proposed in <a href="./rfc524">RFC 524</a> |
| 5144 |
|
| 5145 |
This memo is in response to <a href="./rfc524">RFC 524</a>. In general, the authors of |
| 5146 |
this RFC feel that the protocol is extremely rich. They also feel |
| 5147 |
that there are some minor and some major problems. |
| 5148 |
|
| 5149 |
|
| 5150 |
|
| 5151 |
<span class="grey">Reynolds & Postel [Page 92]</span></pre> |
| 5152 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-93" ></span> |
| 5153 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 5154 |
|
| 5155 |
|
| 5156 |
538 McKenzie Jul 73 Traffic Statistics |
| 5157 |
|
| 5158 |
A report on the Host traffic statistics for the month of June |
| 5159 |
1973. Updates <a href="./rfc522">RFC 522</a>. |
| 5160 |
|
| 5161 |
537 Bunch Jun 73 Announcement of NGG Meeting |
| 5162 |
|
| 5163 |
Arrangement details for a graphics meeting held July 1973. See |
| 5164 |
<a href="./rfc549">RFC 549</a>. |
| 5165 |
|
| 5166 |
536 Never Issued. |
| 5167 |
|
| 5168 |
535 Thomas Jul 73 Comments on File Access Protocol |
| 5169 |
|
| 5170 |
This memo is in response to <a href="./rfc420">RFC 420</a>. |
| 5171 |
|
| 5172 |
534 Walden Jul 73 Lost Message Detection |
| 5173 |
|
| 5174 |
This RFC presents three suggestions for detecting the loss of |
| 5175 |
messages by the communications subsystem. |
| 5176 |
|
| 5177 |
533 Walden Jul 73 Message-ID Numbers |
| 5178 |
|
| 5179 |
Notice that the ARPANET link field of 8-bits has been expanded to |
| 5180 |
12-bits and renamed the message-id field. |
| 5181 |
|
| 5182 |
532 Merryman Jul 73 The UCSD-CC Server-FTP Facility |
| 5183 |
|
| 5184 |
A description of the FTP service at UCSD. |
| 5185 |
|
| 5186 |
531 Padlipsky Jun 73 Feast or Famine? - A Response to Two |
| 5187 |
Recent RFC's About Network |
| 5188 |
Information |
| 5189 |
|
| 5190 |
This memo is in response to RFCs 514 and 519. |
| 5191 |
|
| 5192 |
530 Bhushan Jun 73 A Report on the SURVEY Project |
| 5193 |
|
| 5194 |
The purpose of this paper is 1) to report on the status of the |
| 5195 |
SURVEY project and current data, 2) to inform the ARPANET |
| 5196 |
community of the services offered related to this project, 3) to |
| 5197 |
report on future plans, and 4) to ask for suggestions and |
| 5198 |
improvements. |
| 5199 |
|
| 5200 |
529 McKenzie Jun 73 A Note on Protocol Synch Sequences |
| 5201 |
|
| 5202 |
A response to <a href="./rfc513">RFC 513</a>. |
| 5203 |
|
| 5204 |
|
| 5205 |
|
| 5206 |
|
| 5207 |
<span class="grey">Reynolds & Postel [Page 93]</span></pre> |
| 5208 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-94" ></span> |
| 5209 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 5210 |
|
| 5211 |
|
| 5212 |
528 McQuillan Jun 73 Software Checksumming in the IMP and |
| 5213 |
Network Reliability |
| 5214 |
|
| 5215 |
A description of some of the modifications that have recently |
| 5216 |
been made to the IMP and TIP programs. |
| 5217 |
|
| 5218 |
527 Merryman Jun 73 ARPAWOCKY |
| 5219 |
|
| 5220 |
A parody by D. L. Covill of the ARPANET based on the Jabberwocky |
| 5221 |
of Lewis Carroll |
| 5222 |
|
| 5223 |
526 Pratt Jun 73 Technical Meeting - Digital Image |
| 5224 |
Processing Software Systems |
| 5225 |
|
| 5226 |
Announcement of a technical meeting on digital image processing |
| 5227 |
software systems. |
| 5228 |
|
| 5229 |
525 Parrish Jun 73 MIT-Mathlab Meets UCSB-OLS |
| 5230 |
|
| 5231 |
A description of problem solving using both the MIT-P1ACSYM system |
| 5232 |
and the UCSB-OLS system. |
| 5233 |
|
| 5234 |
524 White Jun 73 A Proposed Mail Protocol |
| 5235 |
|
| 5236 |
A proposed specification for handling mail in the ARPA network. |
| 5237 |
|
| 5238 |
523 Bhushan Jun 73 SURVEY is in Operation Again |
| 5239 |
|
| 5240 |
The purpose of this RFC is to alert the network community that the |
| 5241 |
survey program at MIT-DMCG computer system is in operation. |
| 5242 |
|
| 5243 |
522 McKenzie Jun 73 Traffic Statistics |
| 5244 |
|
| 5245 |
A report on the Host traffic statistics for the month of May 1973. |
| 5246 |
Updates <a href="./rfc509">RFC 509</a>. |
| 5247 |
|
| 5248 |
521 McKenzie May 73 Restricted Use of IMP DDT |
| 5249 |
|
| 5250 |
Proposal of restricted use of IMP DDT due to opinions from |
| 5251 |
representatives of several sites feeling that uncontrolled use of |
| 5252 |
IMP DDT made access control mechanisms too vulnerable to |
| 5253 |
interception or tampering. |
| 5254 |
|
| 5255 |
520 Day Jun 73 Memo to FTP Group (Proposal for File |
| 5256 |
Access Protocol) |
| 5257 |
|
| 5258 |
This document discusses the File Access Protocol as an extension |
| 5259 |
to FTP. |
| 5260 |
|
| 5261 |
|
| 5262 |
|
| 5263 |
<span class="grey">Reynolds & Postel [Page 94]</span></pre> |
| 5264 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-95" ></span> |
| 5265 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 5266 |
|
| 5267 |
|
| 5268 |
519 Pickens Jun 73 Resource Evaluation |
| 5269 |
|
| 5270 |
UCSB announces a new test group based upon <a href="./rfc369">RFC 369</a>, which attempts |
| 5271 |
to take a detailed look at specific network resources and develop |
| 5272 |
initial site dependent and function dependent MINIMAN's. |
| 5273 |
|
| 5274 |
518 Feinler Jun 73 ARPANET Accounts |
| 5275 |
|
| 5276 |
A memo on information regarding opening an account at a given site |
| 5277 |
on the ARPANET. |
| 5278 |
|
| 5279 |
517 Never Issued. |
| 5280 |
|
| 5281 |
516 Postel May 73 Lost Message Detection |
| 5282 |
|
| 5283 |
This RFC is replaced by <a href="./rfc534">RFC 534</a>. |
| 5284 |
|
| 5285 |
515 Winter Jun 73 Specifications for Datalanguage, |
| 5286 |
Version 0/9 |
| 5287 |
|
| 5288 |
This specification for Datalanguage is extremely primitive. |
| 5289 |
Version 0/9 is currently running at CCA and offers an opportunity |
| 5290 |
for experience with the Datacomputer and with fundamental |
| 5291 |
Datalanguage concepts. |
| 5292 |
|
| 5293 |
514 Kantrowitz Jun 73 Network Make-Work |
| 5294 |
|
| 5295 |
Updates <a href="./rfc459">RFC 459</a>. |
| 5296 |
|
| 5297 |
513 Hathaway May 73 Comments on the New Telnet |
| 5298 |
Specifications |
| 5299 |
|
| 5300 |
Discussion of the Telnet Protocol. |
| 5301 |
|
| 5302 |
512 Hathaway May 73 Lost Message Detection |
| 5303 |
|
| 5304 |
This RFC is replaced by <a href="./rfc534">RFC 534</a>. |
| 5305 |
|
| 5306 |
511 North May 73 Enterprise Phone Service to NIC From |
| 5307 |
ARPANET Sites |
| 5308 |
|
| 5309 |
Discussion of cost and alternatives for special telephone numbers |
| 5310 |
for the NIC. |
| 5311 |
|
| 5312 |
510 White May 73 Request for Network Mailbox |
| 5313 |
Addresses |
| 5314 |
|
| 5315 |
Announcement of Network Journal delivery by the NIC and a request |
| 5316 |
for updated/additional network mailbox addresses. |
| 5317 |
|
| 5318 |
|
| 5319 |
<span class="grey">Reynolds & Postel [Page 95]</span></pre> |
| 5320 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-96" ></span> |
| 5321 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 5322 |
|
| 5323 |
|
| 5324 |
509 McKenzie May 73 Traffic Statistics |
| 5325 |
|
| 5326 |
A report on the Host traffic statistics for the month of April |
| 5327 |
1973. Updates <a href="./rfc497">RFC 497</a>. |
| 5328 |
|
| 5329 |
508 Pfeifer May 73 Real-Time Data Transmission on the |
| 5330 |
ARPANET |
| 5331 |
|
| 5332 |
Discussion on the pros and cons of support of real-time processes |
| 5333 |
on the ARPA Network. |
| 5334 |
|
| 5335 |
507 Never Issued. |
| 5336 |
|
| 5337 |
506 Padlipsky Jun 73 An FTP Command Naming Problem |
| 5338 |
|
| 5339 |
This RFC discusses a problem when using the File Transfer |
| 5340 |
Protocol: the choice of names for two crucial commands is faulty. |
| 5341 |
|
| 5342 |
505 Padlipsky Jun 73 Two Solutions to a File Transfer |
| 5343 |
Access Problem |
| 5344 |
|
| 5345 |
This memo is in response to RFCs 487 and 501. |
| 5346 |
|
| 5347 |
504 Thomas May 73 Workshop Announcement |
| 5348 |
|
| 5349 |
Detailed plans for a workshop on Automated Resource Sharing to be |
| 5350 |
held May 1973. |
| 5351 |
|
| 5352 |
503 Neigus Apr 73 Socket Number List |
| 5353 |
|
| 5354 |
This RFC has been replaced by RFCs 997 and 990. |
| 5355 |
|
| 5356 |
502 Never Issued. |
| 5357 |
|
| 5358 |
501 Pogran May 73 Un-Muddling "Free File Transfer" |
| 5359 |
|
| 5360 |
This memo is in response to <a href="./rfc487">RFC 487</a>. |
| 5361 |
|
| 5362 |
500 Shoshani Apr 73 The Integration of Data Management |
| 5363 |
Systems on a Computer Network |
| 5364 |
|
| 5365 |
In this paper, discussion is focused on an approach to integrating |
| 5366 |
data management systems on a computer network for the purpose of |
| 5367 |
data sharing. |
| 5368 |
|
| 5369 |
|
| 5370 |
|
| 5371 |
|
| 5372 |
|
| 5373 |
|
| 5374 |
|
| 5375 |
<span class="grey">Reynolds & Postel [Page 96]</span></pre> |
| 5376 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-97" ></span> |
| 5377 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 5378 |
|
| 5379 |
|
| 5380 |
499 Reussow Apr 73 Harvard's Network RJE |
| 5381 |
|
| 5382 |
A description of the remote job entry service at Harvard. |
| 5383 |
|
| 5384 |
498 Braden Apr 73 On Mail Service to CCN |
| 5385 |
|
| 5386 |
A description of the electronic mail service at UCLA-CCN. |
| 5387 |
|
| 5388 |
497 McKenize Apr 73 Traffic Statistics |
| 5389 |
|
| 5390 |
A report on the Host traffic statistics for the month of March |
| 5391 |
1973. Updates <a href="./rfc482">RFC 482</a>. |
| 5392 |
|
| 5393 |
496 Auerbach Apr 73 A TNLS Quick Reference Card is |
| 5394 |
Available |
| 5395 |
|
| 5396 |
Announcement of a new TNLS Quick Reference Card. |
| 5397 |
|
| 5398 |
495 McKenize May 73 Telnet Protocol Specification |
| 5399 |
|
| 5400 |
Results of an open meeting discussing Telnet, with two attached |
| 5401 |
documents which report the results of that meeting. |
| 5402 |
|
| 5403 |
494 Walden Apr 73 Availability of MIX and MIXAL in the |
| 5404 |
Network |
| 5405 |
|
| 5406 |
A list of hosts that support programming in MIX and MIXAL. |
| 5407 |
|
| 5408 |
993 Michener Apr 73 Graphics Protocol |
| 5409 |
|
| 5410 |
Discuses the opinions and decisions reached at the second meeting |
| 5411 |
of the Network Graphics Group. |
| 5412 |
|
| 5413 |
492 Meyer Apr 73 Response to <a href="./rfc467">RFC 467</a> |
| 5414 |
|
| 5415 |
This document briefly describes the problems and proposed |
| 5416 |
solutions, offers comments and alternative suggestions in response |
| 5417 |
to <a href="./rfc467">RFC 467</a>. |
| 5418 |
|
| 5419 |
491 Padlipsky Apr 73 What is "Free"? |
| 5420 |
|
| 5421 |
This memo discusses the assertion that network mail should be |
| 5422 |
free; i.e., no login or USER command should be required. |
| 5423 |
|
| 5424 |
490 Pickens Mar 73 Surrogate RJS for UCLA-CCN |
| 5425 |
|
| 5426 |
A description of how UCLA's RJS can be accessed from UCSB's |
| 5427 |
standard remote job entry service. |
| 5428 |
|
| 5429 |
|
| 5430 |
|
| 5431 |
<span class="grey">Reynolds & Postel [Page 97]</span></pre> |
| 5432 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-98" ></span> |
| 5433 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 5434 |
|
| 5435 |
|
| 5436 |
489 Postel Mar 73 Comment on Resynchronization of |
| 5437 |
Connection Status Proposal |
| 5438 |
|
| 5439 |
Comments on ideas proposed in <a href="./rfc467">RFC 467</a>. |
| 5440 |
|
| 5441 |
488 Auerbach Mar 73 NLS Classes at Network Sites |
| 5442 |
|
| 5443 |
This RFC solicits comments from the Network community on the |
| 5444 |
desirability of doing on-site classes. |
| 5445 |
|
| 5446 |
487 Bressler Mar 73 Host-Dependent FTP Parameters |
| 5447 |
|
| 5448 |
This memo is in response to <a href="./rfc430">RFC 430</a>. |
| 5449 |
|
| 5450 |
486 Bressler Apr 73 Data Transfer Revisited |
| 5451 |
|
| 5452 |
A proposeal to base RJE and FTP on a common data transfer |
| 5453 |
protocol. |
| 5454 |
|
| 5455 |
485 Pickens Mar 73 MIX and MIXAL at UCSB |
| 5456 |
|
| 5457 |
A response to Walden's MIX query (<a href="./rfc473">RFC 473</a>). |
| 5458 |
|
| 5459 |
484 Never Issued. |
| 5460 |
|
| 5461 |
483 Kudlick Mar 73 Cancellation of the Resource |
| 5462 |
Notebook Famework Meeting |
| 5463 |
|
| 5464 |
482 McKenzie Mar 73 Traffic Statistics |
| 5465 |
|
| 5466 |
A report on the Host traffic statistics for the month of February |
| 5467 |
1973. Updates <a href="./rfc455">RFC 455</a>. |
| 5468 |
|
| 5469 |
481 Never Issued. |
| 5470 |
|
| 5471 |
480 White Mar 73 Host-Dependent FTP Parameters |
| 5472 |
|
| 5473 |
This memo is in response to <a href="./rfc430">RFC 430</a>. |
| 5474 |
|
| 5475 |
479 White Mar 73 Use of FTP by the NIC Journal |
| 5476 |
|
| 5477 |
This RFC states how the NIC outlined its requirements for |
| 5478 |
implementing FTP Journal delivery and submission. |
| 5479 |
|
| 5480 |
478 Bressler Mar 73 FTP Server-Server Interaction - II |
| 5481 |
|
| 5482 |
Discusses server-server interaction where, in a typical situation, |
| 5483 |
a user conversing with two servers is interested in retrieving a |
| 5484 |
file from one site and sending it to another. |
| 5485 |
|
| 5486 |
|
| 5487 |
<span class="grey">Reynolds & Postel [Page 98]</span></pre> |
| 5488 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-99" ></span> |
| 5489 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 5490 |
|
| 5491 |
|
| 5492 |
477 Krilanovich May 73 Remote Job Service at UCSB |
| 5493 |
|
| 5494 |
This RFC is the follow-on document to <a href="./rfc436">RFC 436</a>. This document |
| 5495 |
restates the essence of the official RJE Protocol and documents in |
| 5496 |
detail UCSB's implementation of it. Obsoletes <a href="./rfc436">RFC 436</a>. |
| 5497 |
|
| 5498 |
476 McKenzie Mar 73 IMP/TIP Memory Retrofit Schedules |
| 5499 |
(Revision 2) |
| 5500 |
|
| 5501 |
Describes plans and schedule for upgrading IMPs and TIPs. |
| 5502 |
|
| 5503 |
475 Bhushan Mar 73 FTP and the Network Mail System |
| 5504 |
|
| 5505 |
This paper describes the author's understanding of the results of |
| 5506 |
the Network Mail System meeting and the implications for FTP. |
| 5507 |
|
| 5508 |
474 Bunch Mar 73 Announcement of Forthcoming Meeting |
| 5509 |
of the Network Graphics Working |
| 5510 |
Group and Call for RFC's. |
| 5511 |
|
| 5512 |
Plans for a graphics meeting to be held in May 1973. |
| 5513 |
|
| 5514 |
473 Walden Feb 73 MIX and MIXAL? |
| 5515 |
|
| 5516 |
472 Bunch Mar 73 Illinois' Reply to Maxwell's Request |
| 5517 |
for Graphics Information |
| 5518 |
|
| 5519 |
This RFC represents the author's response to NIC document 14925. |
| 5520 |
|
| 5521 |
471 Thomas Mar 73 Announcement of a (Tenative) |
| 5522 |
Workshop on Multi-Site Executive |
| 5523 |
Programs |
| 5524 |
|
| 5525 |
A suggestion for a workshop and a query for interest. |
| 5526 |
|
| 5527 |
470 Thomas Mar 73 Change in Socket for TIP News |
| 5528 |
Facility |
| 5529 |
|
| 5530 |
469 Kudlick Mar 73 Network Mail Meeting Summary |
| 5531 |
|
| 5532 |
A description of a meeting on mail held February 1973. |
| 5533 |
|
| 5534 |
468 Braden Mar 73 FTP Data Compression |
| 5535 |
|
| 5536 |
This RFC describes the definition of the "HASP" or compressed |
| 5537 |
mode. |
| 5538 |
|
| 5539 |
|
| 5540 |
|
| 5541 |
|
| 5542 |
|
| 5543 |
<span class="grey">Reynolds & Postel [Page 99]</span></pre> |
| 5544 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-100" ></span> |
| 5545 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 5546 |
|
| 5547 |
|
| 5548 |
467 Burchfiel Feb 73 Proposed Change to Host-Host |
| 5549 |
Protocol Resynchronization of |
| 5550 |
Connection Status |
| 5551 |
|
| 5552 |
To achieve resynchronization of allocation, this RFC proposes the |
| 5553 |
addition of two commands to the host-host protocol. |
| 5554 |
|
| 5555 |
466 Winett Feb 73 Telnet Logger/Server for Host LL-67 |
| 5556 |
|
| 5557 |
This RFC contains writeup documents on the Telnet Logger/Server |
| 5558 |
for the CP/CMS system on the Lincoln Laboratory 360/67. |
| 5559 |
|
| 5560 |
465 Never Issued. |
| 5561 |
|
| 5562 |
464 Kudlick Feb 73 Resource Notebook Framework |
| 5563 |
|
| 5564 |
This document presents a framework for coordinating all the |
| 5565 |
surveys and data gathering efforts concerned with "resource |
| 5566 |
notebook" type of information. |
| 5567 |
|
| 5568 |
463 Bhushan Feb 73 FTP Comments and Response to <a href="./rfc430">RFC 430</a> |
| 5569 |
|
| 5570 |
This RFC represents the author's response to <a href="./rfc430">RFC 430</a> and other |
| 5571 |
similar views. |
| 5572 |
|
| 5573 |
462 Iseli Feb 73 Responding to User Needs |
| 5574 |
|
| 5575 |
A proposal to have network documentation maintained at the source, |
| 5576 |
that is, by each site, and available as a distributed database. |
| 5577 |
|
| 5578 |
461 McKenzie Feb 73 Telnet Meeting Announcement |
| 5579 |
|
| 5580 |
Plans for a meeting on Telnet to be held March 1973. |
| 5581 |
|
| 5582 |
460 Kline Feb 73 NCP Survey |
| 5583 |
|
| 5584 |
This RFC is a first in a series which will request information on |
| 5585 |
implmentation of host-to-host protocol. |
| 5586 |
|
| 5587 |
459 Kantrowitz Feb 73 Network Questionnaires |
| 5588 |
|
| 5589 |
Suggests that there is too much or too many different people |
| 5590 |
trying to gather data from all the other sites. |
| 5591 |
|
| 5592 |
458 Bressler Feb 73 Mail Retrieval via FTP |
| 5593 |
|
| 5594 |
Proposal of two new FTP commands called ReaDMailFile and ReaDMail. |
| 5595 |
|
| 5596 |
|
| 5597 |
|
| 5598 |
|
| 5599 |
<span class="grey">Reynolds & Postel [Page 100]</span></pre> |
| 5600 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-101" ></span> |
| 5601 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 5602 |
|
| 5603 |
|
| 5604 |
457 Walden Feb 73 TIPUG |
| 5605 |
|
| 5606 |
How to get updates to the TIP Users Guide. |
| 5607 |
|
| 5608 |
456 NIC Feb 73 Memorandum |
| 5609 |
|
| 5610 |
Change in the meeting time for the Network Mail meeting discussed |
| 5611 |
in <a href="./rfc453">RFC 453</a>. |
| 5612 |
|
| 5613 |
455 McKenzie Feb 73 Traffic Statistics |
| 5614 |
|
| 5615 |
Report on the Host traffic statistics for the month of January |
| 5616 |
1973. Updates <a href="./rfc443">RFC 443</a>. |
| 5617 |
|
| 5618 |
454 McKenzie Feb 73 File Transfer Protocol (Meeting |
| 5619 |
Announcement and a New Proposed |
| 5620 |
Document |
| 5621 |
|
| 5622 |
The specification of the File Transfer Protocol and the |
| 5623 |
announcement of a meeting (March 1973) to discuss it. |
| 5624 |
|
| 5625 |
453 Kudlick Feb 73 Meeting Announcement to Discuss a |
| 5626 |
Network Mail System |
| 5627 |
|
| 5628 |
Plans for a meeting on electronic mail held February 1973. See |
| 5629 |
<a href="./rfc469">RFC 469</a>. |
| 5630 |
|
| 5631 |
452 Winett Feb 73 Telnet Command at Host LL |
| 5632 |
|
| 5633 |
This RFC documents the use of the Telnet command at Host LL for |
| 5634 |
uses under the CP/CMS time-sharing system. |
| 5635 |
|
| 5636 |
451 Padlipsky Feb 73 Tentative Proposal for a Unified |
| 5637 |
User Level Protocol |
| 5638 |
|
| 5639 |
A suggestion for the idea of a network standard command language |
| 5640 |
for interactive systems. |
| 5641 |
|
| 5642 |
450 Padlipsky Feb 73 Multics Sampling Timeout Change |
| 5643 |
|
| 5644 |
Announcement of better service for experimental users of MIT |
| 5645 |
Multics. |
| 5646 |
|
| 5647 |
449 Walden Jan 73 The Current Flow-Control Scheme for |
| 5648 |
IMPSYS |
| 5649 |
|
| 5650 |
Updates <a href="./rfc442">RFC 442</a>. |
| 5651 |
|
| 5652 |
|
| 5653 |
|
| 5654 |
|
| 5655 |
<span class="grey">Reynolds & Postel [Page 101]</span></pre> |
| 5656 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-102" ></span> |
| 5657 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 5658 |
|
| 5659 |
|
| 5660 |
448 Braden Feb 73 Print Files in FTP |
| 5661 |
|
| 5662 |
This document reviews the problem of print files. |
| 5663 |
|
| 5664 |
447 McKenzie Jan 73 IMP/TIP Memory Retrofit Schedule |
| 5665 |
|
| 5666 |
Updates <a href="./rfc434">RFC 434</a>. |
| 5667 |
|
| 5668 |
446 Deutsch Jan 73 Proposal to Consider a Network |
| 5669 |
Program Resource Notebook |
| 5670 |
|
| 5671 |
445 McKenzie Jan 73 IMP/TIP Preventive Maintenance |
| 5672 |
Schedule |
| 5673 |
|
| 5674 |
444 Never Issued. |
| 5675 |
|
| 5676 |
443 McKenzie Jan 73 Traffic Statistics |
| 5677 |
|
| 5678 |
Report on the Host traffic statistics for the month of December |
| 5679 |
1972. Updates <a href="./rfc422">RFC 422</a>. |
| 5680 |
|
| 5681 |
442 Cerf Jan 73 The Current Flow-Control Scheme for |
| 5682 |
IMPSYS |
| 5683 |
|
| 5684 |
This RFC discusses the current flow-control scheme for IMPSYS. |
| 5685 |
|
| 5686 |
441 Bressler Jan 73 Inter-Entity Communication - An |
| 5687 |
Experiment |
| 5688 |
|
| 5689 |
A status report concerning an experiment based on the desire of |
| 5690 |
users, at their consoles, to converse with one another, and to |
| 5691 |
receive some debugging assistance. |
| 5692 |
|
| 5693 |
440 Walden Jan 73 Scheduled Network Software |
| 5694 |
Maintenance |
| 5695 |
|
| 5696 |
Explains plans and schedule for IMP software maintenance, expands |
| 5697 |
the normal time slot. |
| 5698 |
|
| 5699 |
439 Cerf Jan 73 PARRY Encounters the Doctor |
| 5700 |
|
| 5701 |
A lighthearted documentation on a session that actually happened |
| 5702 |
on September 18, 1972. |
| 5703 |
|
| 5704 |
438 Thomas Jan 73 FTP Server-Server Interaction |
| 5705 |
|
| 5706 |
This document suggests a simple extension to FTP which would allow |
| 5707 |
a FTP user process at one site to arrange for FTP server processes |
| 5708 |
at other sites to act cooperatively on its behalf. |
| 5709 |
|
| 5710 |
|
| 5711 |
<span class="grey">Reynolds & Postel [Page 102]</span></pre> |
| 5712 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-103" ></span> |
| 5713 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 5714 |
|
| 5715 |
|
| 5716 |
437 Faeh Jun 73 Data Reconfiguration Service at UCSB |
| 5717 |
|
| 5718 |
Announcement of the availability of the Data Reconfiguration |
| 5719 |
Service (DRS) at UCSB. |
| 5720 |
|
| 5721 |
436 Krilanovich Jan 73 Announcement of RJS at UCSB |
| 5722 |
|
| 5723 |
Announcement of the availability of RJS at UCSB. |
| 5724 |
|
| 5725 |
435 Cosell Jan 73 Telnet Issues |
| 5726 |
|
| 5727 |
This RFC discusses a number of Telnet related issues, with the |
| 5728 |
central issue of discussion being echoing. |
| 5729 |
|
| 5730 |
434 McKenzie Jan 73 IMP/TIP Memory Retrofit Schedule |
| 5731 |
|
| 5732 |
Explains plans and schedule for IMP and TIP upgrades. |
| 5733 |
|
| 5734 |
433 Postel Dec 72 Socket Number List |
| 5735 |
|
| 5736 |
Establishment of assigned socket numbers to be used for public |
| 5737 |
functions. This RFC has been replaced by <a href="./rfc997">RFC 997</a> and 990. |
| 5738 |
|
| 5739 |
432 Neigus Dec 72 Network Logical Map |
| 5740 |
|
| 5741 |
Attachment of the network logical map as of December 30, 1972. |
| 5742 |
|
| 5743 |
431 Krilanovich Dec 72 Update on SMFS Login and Logout |
| 5744 |
|
| 5745 |
This document obsoletes <a href="./rfc399">RFC 399</a>, which introduced the Login and |
| 5746 |
Logout commands for UCSB's SMFS, but was incomplete. <a href="./rfc399">RFC 399</a> is |
| 5747 |
restated more fully in this RFC. |
| 5748 |
|
| 5749 |
430 Braden Feb 73 Comments on File Transfer Protocol |
| 5750 |
|
| 5751 |
Discusses several issues in FTP. |
| 5752 |
|
| 5753 |
429 Postel Dec 72 Character Generator Process |
| 5754 |
|
| 5755 |
A proposal that there be a standard process implemented on |
| 5756 |
whatever hosts desire which generates character data with out any |
| 5757 |
regard to input. |
| 5758 |
|
| 5759 |
428 Never Issued. |
| 5760 |
|
| 5761 |
427 Never Issued. |
| 5762 |
|
| 5763 |
|
| 5764 |
|
| 5765 |
|
| 5766 |
|
| 5767 |
<span class="grey">Reynolds & Postel [Page 103]</span></pre> |
| 5768 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-104" ></span> |
| 5769 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 5770 |
|
| 5771 |
|
| 5772 |
426 Thomas Jan 73 Reconnection Protocol |
| 5773 |
|
| 5774 |
This document describes several situations in which the ability to |
| 5775 |
reconnect is useful, presents a mechanism to achieve |
| 5776 |
reconnections, sketches how the mechanism could be added to |
| 5777 |
Host-Host or Telnet protocol, and recommends a place for the |
| 5778 |
mechanism in the protocol hierarchy. |
| 5779 |
|
| 5780 |
425 Bressler Dec 72 "But my NCP costs $500 a day..." |
| 5781 |
|
| 5782 |
Discussion on the cost of network software and network use. |
| 5783 |
|
| 5784 |
424 Never Issued. |
| 5785 |
|
| 5786 |
423 Noble Dec 72 UCLA Campus Computing Network |
| 5787 |
Liaison Staff for ARPA Network |
| 5788 |
|
| 5789 |
A list of ARPA network contacts at CCN. Updates <a href="./rfc389">RFC 389</a>. |
| 5790 |
|
| 5791 |
422 McKenzie Dec 72 Traffic Statistics |
| 5792 |
|
| 5793 |
Report on the Host traffic statistics for the month of November |
| 5794 |
1972. Updates <a href="./rfc413">RFC 413</a>. |
| 5795 |
|
| 5796 |
421 McKenzie Nov 72 A Software Consulting Service for |
| 5797 |
Network Users |
| 5798 |
|
| 5799 |
An announcement of a BBN software consulting service that has been |
| 5800 |
established for ARPA network users. |
| 5801 |
|
| 5802 |
420 Murray Jan 73 CCA ICCC Weather Demo |
| 5803 |
|
| 5804 |
Announcement that the weather demo for the ICCC show is now |
| 5805 |
generally available. |
| 5806 |
|
| 5807 |
419 Vezza Dec 72 MIT-DMS on Vacation |
| 5808 |
|
| 5809 |
The MIT Dynamic Modeling System will be down for 2-4 weeks. |
| 5810 |
|
| 5811 |
418 Hathaway Nov 72 Server File Transfer Under TSS/360 |
| 5812 |
at NASA/Ames Research Center |
| 5813 |
|
| 5814 |
This RFC is a description of the initial implementation of Server |
| 5815 |
File Transfer at NASA-Ames Research Center. |
| 5816 |
|
| 5817 |
|
| 5818 |
|
| 5819 |
|
| 5820 |
|
| 5821 |
|
| 5822 |
|
| 5823 |
<span class="grey">Reynolds & Postel [Page 104]</span></pre> |
| 5824 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-105" ></span> |
| 5825 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 5826 |
|
| 5827 |
|
| 5828 |
417 Postel Nov 72 LINK Usage Violation |
| 5829 |
|
| 5830 |
The protocol police issue a citation. |
| 5831 |
|
| 5832 |
416 Norton Nov 72 The ARC System will be Unavailable |
| 5833 |
for Use During Thanksgiving Week |
| 5834 |
|
| 5835 |
The SRI-ARC machine will be down for 9-10 days. |
| 5836 |
|
| 5837 |
415 Murray Nov 72 TENEX Bandwidth |
| 5838 |
|
| 5839 |
Considerations of the performances of each host. References |
| 5840 |
<a href="./rfc392">RFC 392</a>. |
| 5841 |
|
| 5842 |
414 Bhushan Nov 72 File Transfer Protocols (FTP) Status |
| 5843 |
and Further Comments |
| 5844 |
|
| 5845 |
A status report on working server and user FTPs. |
| 5846 |
|
| 5847 |
413 McKenzie Nov 72 Traffic Statistics |
| 5848 |
|
| 5849 |
Three sets of network traffic statistic reports. Updates <a href="./rfc400">RFC 400</a>. |
| 5850 |
|
| 5851 |
412 Hicks Nov 72 User FTP Documentation |
| 5852 |
|
| 5853 |
A "help" file for the Utah-10 implementation of the User FTP |
| 5854 |
process. |
| 5855 |
|
| 5856 |
411 Padlipsky Nov 72 New Multics Network Software |
| 5857 |
Features |
| 5858 |
|
| 5859 |
Discussion on two recently-installed features of the Multics |
| 5860 |
Network software. |
| 5861 |
|
| 5862 |
410 McQuillan Nov 72 Removal of the 30-Second Delay When |
| 5863 |
Hosts Come Up |
| 5864 |
|
| 5865 |
A proposal to elminate the 30-second delay altogether. |
| 5866 |
|
| 5867 |
409 White Dec 72 TENEX Interface to UCSB's |
| 5868 |
Simple-Minded File System |
| 5869 |
|
| 5870 |
This document is intended to provide users with the information |
| 5871 |
necessary to use SMFS from a terminal; the reader is assumed |
| 5872 |
familiar with Tenex. |
| 5873 |
|
| 5874 |
|
| 5875 |
|
| 5876 |
|
| 5877 |
|
| 5878 |
|
| 5879 |
<span class="grey">Reynolds & Postel [Page 105]</span></pre> |
| 5880 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-106" ></span> |
| 5881 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 5882 |
|
| 5883 |
|
| 5884 |
408 Owen Oct 72 NETBANK |
| 5885 |
|
| 5886 |
A proposed idea for a protocol (or service) that is offered as an |
| 5887 |
aid to network use for new users. |
| 5888 |
|
| 5889 |
407 Bressler Oct 72 Remote Job Entry Protocol |
| 5890 |
|
| 5891 |
The release of the official Remote Job Entry Protocol, per the |
| 5892 |
ARPA office. |
| 5893 |
|
| 5894 |
406 McQuillan Oct 72 Scheduled IMP Software Releases |
| 5895 |
|
| 5896 |
Explains the plans and schedule for IMP software maintenance. |
| 5897 |
|
| 5898 |
405 McKenzie Oct 72 Correction to <a href="./rfc404">RFC 404</a> |
| 5899 |
|
| 5900 |
Typographical error notation. Obsoletes <a href="./rfc404">RFC 404</a>. |
| 5901 |
|
| 5902 |
404 McKenzie Oct 72 Host Address Changes Involving Rand |
| 5903 |
and ISI |
| 5904 |
|
| 5905 |
The new address of ISI is IMP 22. THe new address of RAND is |
| 5906 |
IMP 7. |
| 5907 |
|
| 5908 |
d |
| 5909 |
|
| 5910 |
403 Hicks Jan 73 Desirability of a Network 1108 |
| 5911 |
Service |
| 5912 |
|
| 5913 |
402 NIC Oct 72 ARPA Network Mailing Lists |
| 5914 |
|
| 5915 |
Obsoletes <a href="./rfc363">RFC 363</a>. |
| 5916 |
|
| 5917 |
401 Hansen Oct 72 Conversion of NGP-0 Coordinates to |
| 5918 |
Device Specific Coordinates |
| 5919 |
|
| 5920 |
A means is described to convert NGP coordinates to interger |
| 5921 |
coordinates in the range zero to M, where M is the maximum address |
| 5922 |
of the device screen on a machine using 2's complement arithmetic. |
| 5923 |
|
| 5924 |
400 McKenzie Oct 72 Traffic Statistics |
| 5925 |
|
| 5926 |
A report on the Host traffic statistics for the month of |
| 5927 |
September 1972. Updates <a href="./rfc391">RFC 391</a>. |
| 5928 |
|
| 5929 |
|
| 5930 |
|
| 5931 |
|
| 5932 |
|
| 5933 |
|
| 5934 |
|
| 5935 |
<span class="grey">Reynolds & Postel [Page 106]</span></pre> |
| 5936 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-107" ></span> |
| 5937 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 5938 |
|
| 5939 |
|
| 5940 |
399 Krilanovich Sep 72 SMFS Login and Logout |
| 5941 |
|
| 5942 |
398 Pickens Sep 72 UCSB Online Graphics |
| 5943 |
|
| 5944 |
Announcement that users with Tektronix or IMLAC terminals, or with |
| 5945 |
systems that support the proposed Level 0 graphics protocol can |
| 5946 |
access UCSB graphics. |
| 5947 |
|
| 5948 |
397 Never Issued. |
| 5949 |
|
| 5950 |
396 Bunch Nov 72 Network Graphics Working Group |
| 5951 |
Meeting - Second Iteration |
| 5952 |
|
| 5953 |
395 McQuillan Oct 72 Switch Settings on IMPs and TIPs |
| 5954 |
|
| 5955 |
Discussion on a description of the switches on the front panel of |
| 5956 |
IMPs and TIPs that are important to the correct operation of the |
| 5957 |
network software. |
| 5958 |
|
| 5959 |
394 McQuillan Sep 72 Two Proposed Changes to the IMP-HOST |
| 5960 |
Protocol |
| 5961 |
|
| 5962 |
Updates <a href="./rfc381">RFC 381</a>. This note describes two changes to the IMP-Host |
| 5963 |
communication protocol described in BBN Report 1822. |
| 5964 |
|
| 5965 |
393 Winett Oct 72 Comments on Telnet Protocol Changes |
| 5966 |
|
| 5967 |
Comments and objections to two of the three recent suggestions for |
| 5968 |
changing the Telnet protocol as described in <a href="./rfc328">RFC 328</a>. |
| 5969 |
|
| 5970 |
392 Hicks Sep 72 Measurement of Host Costs for |
| 5971 |
Transmitting Network Data |
| 5972 |
|
| 5973 |
Discussion of Utah's development of a program to use the Remote |
| 5974 |
Job Service System (RJS) at UCLA-CCN in conjunction with Utah's |
| 5975 |
"batch" users. |
| 5976 |
|
| 5977 |
391 McKenzie Sep 72 Traffic Statistics |
| 5978 |
|
| 5979 |
A report on the Host traffic statistics for the month of |
| 5980 |
August 1972. Updates <a href="./rfc378">RFC 378</a>. |
| 5981 |
|
| 5982 |
390 Braden May 72 TSO Scenario Batch Compilation and |
| 5983 |
Foreground Execution |
| 5984 |
|
| 5985 |
An example session with TSO on UCLA-CCN. |
| 5986 |
|
| 5987 |
|
| 5988 |
|
| 5989 |
|
| 5990 |
|
| 5991 |
<span class="grey">Reynolds & Postel [Page 107]</span></pre> |
| 5992 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-108" ></span> |
| 5993 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 5994 |
|
| 5995 |
|
| 5996 |
389 Noble Aug 72 UCLA Campus Computing Network |
| 5997 |
Liaison Staff for ARPA Network |
| 5998 |
|
| 5999 |
A list for ARPA Network contacts at UCLA/CCN. |
| 6000 |
|
| 6001 |
388 Cerf Aug 72 NCP Statistics |
| 6002 |
|
| 6003 |
Updates <a href="./rfc323">RFC 323</a>. Announcement that UCLA/NMC is prepared to gather |
| 6004 |
NCP statistics on a daily basis. |
| 6005 |
|
| 6006 |
387 Kelley Aug 72 Some Experiences in Implementing |
| 6007 |
Network Graphics Protocol Level 0 |
| 6008 |
|
| 6009 |
386 Cosell Aug 72 Letter to TIP Users - 2 |
| 6010 |
|
| 6011 |
A second point of information letter to TIP users. Updates |
| 6012 |
<a href="./rfc365">RFC 365</a>. |
| 6013 |
|
| 6014 |
385 Bhushan Aug 72 Comments on the File Transfer |
| 6015 |
Protocol (<a href="./rfc354">RFC 354</a>) |
| 6016 |
|
| 6017 |
The comments in this document include errata, further discussion, |
| 6018 |
emphasis points, and additions to the protocol. Updates <a href="./rfc354">RFC 354</a>. |
| 6019 |
|
| 6020 |
384 North Aug 72 Official Site IDENTS for |
| 6021 |
Organizations in the ARPA Network |
| 6022 |
|
| 6023 |
Includes two lists, a list in alpha order and a list by Site |
| 6024 |
address. Obsoletes <a href="./rfc289">RFC 289</a>. |
| 6025 |
|
| 6026 |
383 Never Issued. |
| 6027 |
|
| 6028 |
382 McDaniel Aug 72 Mathematical Software on the ARPA |
| 6029 |
Network |
| 6030 |
|
| 6031 |
Comments on the efforts to develop high quality libraries of |
| 6032 |
mathematical and statistical subroutines. |
| 6033 |
|
| 6034 |
381 McQuillan Jul 72 Three Aids to Improved Network |
| 6035 |
Operation |
| 6036 |
|
| 6037 |
Discusses helpful aids to improved network operation: schedules of |
| 6038 |
software maintenance, IMP-to-Host communication, and network news |
| 6039 |
service. |
| 6040 |
|
| 6041 |
380 Never Issued. |
| 6042 |
|
| 6043 |
|
| 6044 |
|
| 6045 |
|
| 6046 |
|
| 6047 |
<span class="grey">Reynolds & Postel [Page 108]</span></pre> |
| 6048 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-109" ></span> |
| 6049 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 6050 |
|
| 6051 |
|
| 6052 |
379 Braden Aug 72 Using TSO at CCN |
| 6053 |
|
| 6054 |
Announcement that IBM's Time Sharing Option (TSO) is up on a |
| 6055 |
regularly scheduled basis at UCLA/CCN. |
| 6056 |
|
| 6057 |
378 McKenzie Aug 72 Traffic Statistics |
| 6058 |
|
| 6059 |
Traffic statistics for the month of July 1972. |
| 6060 |
|
| 6061 |
377 Braden Aug 72 Using TSO Via ARPA Network Virtual |
| 6062 |
Terminal |
| 6063 |
|
| 6064 |
Announcement of IBM's Time Sharing Option (TSO) availability at |
| 6065 |
UCLA/CCN on Socket 1, using the standard Telnet protocol. |
| 6066 |
|
| 6067 |
376 Westheimer Aug 72 Network Host Status |
| 6068 |
|
| 6069 |
Report on the status of Network Hosts from July 31 to August 4. |
| 6070 |
Updates <a href="./rfc370">RFC 370</a>. |
| 6071 |
|
| 6072 |
375 Never Issued. |
| 6073 |
|
| 6074 |
374 McKenzie Jul 72 IMP System Announcement |
| 6075 |
|
| 6076 |
Updates RFCs 331,343,359. |
| 6077 |
|
| 6078 |
373 McCarthy Jul 72 Arbitrary Character Sets |
| 6079 |
|
| 6080 |
Suggests how to get arbitrary characters sets stored in computers |
| 6081 |
and to be able to display them on any CRT screen, edit them using |
| 6082 |
any keyboard, and print them on any printer. |
| 6083 |
|
| 6084 |
372 Watson Jul 72 Notes on a Conversation with Bob |
| 6085 |
Kahn on the ICCC |
| 6086 |
|
| 6087 |
Discussion on some aspects of the ICCC meeting demonstration. |
| 6088 |
|
| 6089 |
371 Kahn Jul 72 Demonstration at International |
| 6090 |
Computer Communications Conference |
| 6091 |
|
| 6092 |
Observation and notes on the ICCC meeting demonstration. |
| 6093 |
|
| 6094 |
370 Westheimer Jul 72 Network Host Status |
| 6095 |
|
| 6096 |
Report on the status of Network Hosts from July 17 to July 28. |
| 6097 |
Updates <a href="./rfc367">RFC 367</a>. |
| 6098 |
|
| 6099 |
|
| 6100 |
|
| 6101 |
|
| 6102 |
|
| 6103 |
<span class="grey">Reynolds & Postel [Page 109]</span></pre> |
| 6104 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-110" ></span> |
| 6105 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 6106 |
|
| 6107 |
|
| 6108 |
369 Pickens Jul 72 Evaluation of ARPANET Services |
| 6109 |
(January through March, 1972) |
| 6110 |
|
| 6111 |
This paper provides descriptions, surveys, critiques of ARPANET |
| 6112 |
services, and suggestions for improvement. |
| 6113 |
|
| 6114 |
368 Braden Jul 72 Comments on "Proposed Remote Job |
| 6115 |
Entry Protocol" |
| 6116 |
|
| 6117 |
Suggestions on honing the final standard of the RJE protocol |
| 6118 |
(references <a href="./rfc360">RFC 360</a>). |
| 6119 |
|
| 6120 |
367 Westheimer Jul 72 Network Host Status |
| 6121 |
|
| 6122 |
Report on the status of Network Hosts from July 1 to July 16. |
| 6123 |
Updates <a href="./rfc366">RFC 366</a>. |
| 6124 |
|
| 6125 |
366 Westheimer Jul 72 Network Host Status |
| 6126 |
|
| 6127 |
Report on the status of Network Hosts from June 19 to June 30. |
| 6128 |
Updates <a href="./rfc362">RFC 362</a>. |
| 6129 |
|
| 6130 |
365 Walden Jul 72 A Letter to All TIP Users |
| 6131 |
|
| 6132 |
Descriptions of new commands that have recently been added to the |
| 6133 |
"TIP Users Guide". |
| 6134 |
|
| 6135 |
364 Abrams Jul 72 Serving Remote Users on the ARPANET |
| 6136 |
|
| 6137 |
This paper asserts that a problem exists in serving remote users |
| 6138 |
and offers a set of suggestions for its amelioration. |
| 6139 |
|
| 6140 |
363 NIC Aug 72 ARPA Network Mailing Lists |
| 6141 |
|
| 6142 |
Obsoletes <a href="./rfc329">RFC 329</a>. |
| 6143 |
|
| 6144 |
362 Westheimer Jun 72 Network Host Status |
| 6145 |
|
| 6146 |
Report on the status of Network Hosts from June 5 to June 16. |
| 6147 |
Updates <a href="./rfc353">RFC 353</a>. |
| 6148 |
|
| 6149 |
361 Bressler Jul 72 In Response to RFCs 347 and 348 |
| 6150 |
|
| 6151 |
Deamon Processes on Host 106. |
| 6152 |
|
| 6153 |
|
| 6154 |
|
| 6155 |
|
| 6156 |
|
| 6157 |
|
| 6158 |
|
| 6159 |
<span class="grey">Reynolds & Postel [Page 110]</span></pre> |
| 6160 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-111" ></span> |
| 6161 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 6162 |
|
| 6163 |
|
| 6164 |
360 Holland Jun 72 Proposed Remote Job Entry Protocol |
| 6165 |
|
| 6166 |
This protocol specifies the Network standard procedures for remote |
| 6167 |
job entry as a mechanism whereby a user at one location causes a |
| 6168 |
batch-processing job to be run at some other location. |
| 6169 |
|
| 6170 |
359 Walden Jun 72 The Status of the Release of the New |
| 6171 |
IMP System (2600) |
| 6172 |
|
| 6173 |
Obsoletes <a href="./rfc343">RFC 343</a>. |
| 6174 |
|
| 6175 |
358 Never Issued. |
| 6176 |
|
| 6177 |
357 Davidson Jun 72 An Echoing Strategy for Satellite |
| 6178 |
Links |
| 6179 |
|
| 6180 |
This document describes a strategy which will eliminate the delay |
| 6181 |
associated with simple echoing and allow the transmission delay to |
| 6182 |
be hidden in the cost of computation only. This scheme is |
| 6183 |
proposed as an optional addition to existing User Telnets; its use |
| 6184 |
requires the explicit support of a cooperating server process. |
| 6185 |
|
| 6186 |
356 Alter Jun 72 ARPA Network Control Center |
| 6187 |
|
| 6188 |
Announcement of the NCC's new operation schedule. |
| 6189 |
|
| 6190 |
355 Davidson Jun 72 Response to <a href="./rfc346">RFC 346</a> |
| 6191 |
|
| 6192 |
354 Bhushan Jul 72 The File Transfer Protocol |
| 6193 |
|
| 6194 |
This RFC obsoletes RFCs 264,265. The File Transfer Protocol (FTP) |
| 6195 |
is a protocol for file transfer between HOSTs on the ARPANET. The |
| 6196 |
primary function of FTP is to transfer files efficiently and |
| 6197 |
reliably among hosts and to allow the convenient use of remote |
| 6198 |
file storage capabilities. |
| 6199 |
|
| 6200 |
353 Westheimer Jun 72 Network Host Status |
| 6201 |
|
| 6202 |
Status report of most Network Hosts from May 22 to June 2. |
| 6203 |
Updates <a href="./rfc344">RFC 344</a>. |
| 6204 |
|
| 6205 |
352 Crocker Jun 72 TIP Site Information Form (Graphics) |
| 6206 |
|
| 6207 |
An information form to provide additional information for TIP |
| 6208 |
users of the NET. |
| 6209 |
|
| 6210 |
|
| 6211 |
|
| 6212 |
|
| 6213 |
|
| 6214 |
|
| 6215 |
<span class="grey">Reynolds & Postel [Page 111]</span></pre> |
| 6216 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-112" ></span> |
| 6217 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 6218 |
|
| 6219 |
|
| 6220 |
351 Crocker Jun 72 (Graphics) Information Form for the |
| 6221 |
ARPANET Graphics Resources Notebook |
| 6222 |
|
| 6223 |
A questionnaire about the state of graphics resources at various |
| 6224 |
sites. |
| 6225 |
|
| 6226 |
350 Stoughton May 72 User Accounts for UCSB On-Line |
| 6227 |
System |
| 6228 |
|
| 6229 |
Announcement of new login parameters for the UCSB On-Line System. |
| 6230 |
|
| 6231 |
349 Postel May 72 Proposed Standard Socket Numbers |
| 6232 |
|
| 6233 |
A proposal to officially standardize socket number assignments. |
| 6234 |
|
| 6235 |
348 Postel May 72 Discard Process |
| 6236 |
|
| 6237 |
A RFC discussing debugging and measurement puposes for those hosts |
| 6238 |
which are willing to implement a "Discard" process. Old version; |
| 6239 |
see <a href="./rfc863">RFC 863</a>. |
| 6240 |
|
| 6241 |
347 Postel May 72 Echo Process |
| 6242 |
|
| 6243 |
A RFC discussing debugging and measurement puposes for those hosts |
| 6244 |
which are willing to implement an "Echo" process. Old version; |
| 6245 |
see <a href="./rfc862">RFC 862</a>. |
| 6246 |
|
| 6247 |
346 Postel May 72 Satellite Considerations |
| 6248 |
|
| 6249 |
Discussion on using space satellite transmission links in the |
| 6250 |
ARPANET. |
| 6251 |
|
| 6252 |
345 Kelly May 72 Interest in Mixed Integer |
| 6253 |
Programming (MPSX on 360/91 at CCN) |
| 6254 |
|
| 6255 |
Request for interested persons in the MPSX to contact author. |
| 6256 |
|
| 6257 |
344 Westheimer May 72 Network Host Status |
| 6258 |
|
| 6259 |
Updates <a href="./rfc342">RFC 342</a>. |
| 6260 |
|
| 6261 |
343 McKenzie May 72 IMP System Change Notification |
| 6262 |
|
| 6263 |
Obsoletes <a href="./rfc331">RFC 331</a>. Release of IMPSYS 2600 was unsuccessful. |
| 6264 |
|
| 6265 |
|
| 6266 |
|
| 6267 |
|
| 6268 |
|
| 6269 |
|
| 6270 |
|
| 6271 |
<span class="grey">Reynolds & Postel [Page 112]</span></pre> |
| 6272 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-113" ></span> |
| 6273 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 6274 |
|
| 6275 |
|
| 6276 |
342 Westheimer May 72 Network Host Status |
| 6277 |
|
| 6278 |
Updates <a href="./rfc332">RFC 332</a>. |
| 6279 |
|
| 6280 |
341 Never Issued. |
| 6281 |
|
| 6282 |
340 O'Sullivan May 72 Proposed Telnet Changes |
| 6283 |
|
| 6284 |
A proposed change to the Telnet protocol calling for one standard |
| 6285 |
protocol and dropping the idea of minimum implementation. |
| 6286 |
|
| 6287 |
339 Thomas May 72 MLTNET - A "Multi-Telnet" Subsystem |
| 6288 |
for TENEX |
| 6289 |
|
| 6290 |
This RFC describes MLTNET as a Telnet-like facility for Tenex |
| 6291 |
which enables a user to control a number of jobs, running on |
| 6292 |
different ARPANET hosts. MLTNET is currently a subsystem on the |
| 6293 |
BBN-Tenex host. |
| 6294 |
|
| 6295 |
338 Braden May 72 EBCDIC/ASCII Mapping for Network RJE |
| 6296 |
|
| 6297 |
This RFC proposes: to make all users of NETRJS aware of the |
| 6298 |
changed ASCII mapping; to call this problem to the attention of |
| 6299 |
the Network RJE Protocol committee; and to knowledge and support |
| 6300 |
Joel Winett's pioneering work in this area. |
| 6301 |
|
| 6302 |
337 Never Issued. |
| 6303 |
|
| 6304 |
336 Cotton May 72 Level 0 Graphic Input Protocol |
| 6305 |
|
| 6306 |
A description of the graphics input protocol as discussed at a |
| 6307 |
Network Graphics Working Group meeting. |
| 6308 |
|
| 6309 |
335 Bryan May 72 New Interface-IMP/360 |
| 6310 |
|
| 6311 |
Announcement of a new interface and requests to hear of any |
| 6312 |
difficulties network users encounter while operating with UCSB. |
| 6313 |
|
| 6314 |
334 McKenzie May 72 Network Use on May 8 |
| 6315 |
|
| 6316 |
333 Bressler May 72 A Proposed Experiment with a Message |
| 6317 |
Switching Protocol |
| 6318 |
|
| 6319 |
This document attempts to sketch how one would organize the lowest |
| 6320 |
level host-host protocol in the ARPANET around Message Switching |
| 6321 |
Protocols (MSPs) and how this organization would affect the |
| 6322 |
implementation of the host software. |
| 6323 |
|
| 6324 |
|
| 6325 |
|
| 6326 |
|
| 6327 |
<span class="grey">Reynolds & Postel [Page 113]</span></pre> |
| 6328 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-114" ></span> |
| 6329 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 6330 |
|
| 6331 |
|
| 6332 |
332 Westheimer Apr 72 Network Host Status |
| 6333 |
|
| 6334 |
Updates <a href="./rfc330">RFC 330</a>. |
| 6335 |
|
| 6336 |
331 McQuillan Apr 72 IMP System Change Notification |
| 6337 |
|
| 6338 |
Announcement of the release of IMPSYS 2600. |
| 6339 |
|
| 6340 |
330 Westheimer Apr 72 Network Host Status |
| 6341 |
|
| 6342 |
Updates <a href="./rfc326">RFC 326</a>. |
| 6343 |
|
| 6344 |
329 NIC May 72 ARPA Network Mailing Lists |
| 6345 |
|
| 6346 |
328 Postel Apr 72 Suggested Telnet Protocol Changes |
| 6347 |
|
| 6348 |
This RFC proposes changes to the Telnet protocol. |
| 6349 |
|
| 6350 |
327 Bhushan Apr 72 Data and File Transfer Workshop |
| 6351 |
Notes |
| 6352 |
|
| 6353 |
326 Westheimer Apr 72 Network Host Status |
| 6354 |
|
| 6355 |
Updates <a href="./rfc319">RFC 319</a>. |
| 6356 |
|
| 6357 |
325 Hicks Apr 72 Network Remote Job Entry Program - |
| 6358 |
NETRJS |
| 6359 |
|
| 6360 |
Report on the NETRJS running at the University of Utah. |
| 6361 |
|
| 6362 |
324 Postel Apr 72 RJE Protocol Meeting |
| 6363 |
|
| 6364 |
Announcement of a RJE Protocol meeting at UCLA. |
| 6365 |
|
| 6366 |
323 Cerf Mar 72 Formation of Network Measurement |
| 6367 |
Group (NMG) |
| 6368 |
|
| 6369 |
Describes some network measurement results, some plans for further |
| 6370 |
measurement and the formation of an interest group. |
| 6371 |
|
| 6372 |
322 Cerf Mar 72 Well Known Socket Numbers |
| 6373 |
|
| 6374 |
Announcement of intent to catalog all sockets which are supposed |
| 6375 |
to be well-known. |
| 6376 |
|
| 6377 |
|
| 6378 |
|
| 6379 |
|
| 6380 |
|
| 6381 |
|
| 6382 |
|
| 6383 |
<span class="grey">Reynolds & Postel [Page 114]</span></pre> |
| 6384 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-115" ></span> |
| 6385 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 6386 |
|
| 6387 |
|
| 6388 |
321 Karp Mar 72 CBI Networking Activity at MITRE |
| 6389 |
|
| 6390 |
Response to <a href="./rfc313">RFC 313</a> - comments on Computer Based Instruction. |
| 6391 |
|
| 6392 |
320 Reddy Mar 72 Workshop on Hard Copy Line Graphics |
| 6393 |
|
| 6394 |
Announcement of a one day workshop on the XCRIBL system at CMU. |
| 6395 |
|
| 6396 |
319 Westheimer Mar 72 Network Host Status |
| 6397 |
|
| 6398 |
Updates <a href="./rfc315">RFC 315</a>. |
| 6399 |
|
| 6400 |
318 Postel Apr 72 Ad Hoc Telnet Protocol |
| 6401 |
|
| 6402 |
Obsoletes <a href="./rfc158">RFC 158</a>. This Telnet specification was effective for |
| 6403 |
several years. |
| 6404 |
|
| 6405 |
317 Postel Mar 72 Official Host-Host Protocol |
| 6406 |
Modification: Assigned Link Numbers |
| 6407 |
|
| 6408 |
Lists current Link number assignments. This RFC has been replaced |
| 6409 |
by RFCs 997 and 990. |
| 6410 |
|
| 6411 |
316 McKay Feb 72 ARPA Network Data Management Working |
| 6412 |
Group Meeting Report |
| 6413 |
|
| 6414 |
315 Westheimer Mar 72 Network Host Status |
| 6415 |
|
| 6416 |
Updates <a href="./rfc306">RFC 306</a>. |
| 6417 |
|
| 6418 |
314 Cotton Mar 72 Next Network Graphics Working Group |
| 6419 |
Meeting |
| 6420 |
|
| 6421 |
Describes plans for a graphics meeting to be held in April 1972. |
| 6422 |
|
| 6423 |
313 O'Sullivan Mar 72 Computer Based Instruction |
| 6424 |
|
| 6425 |
This paper has two purposes: to solicit comments from the NWG and |
| 6426 |
others on how selected classes of resources of a General Purpose |
| 6427 |
Network might be applied to the field of Computer Based |
| 6428 |
Instructions; and initiate a dialog between interested parties on |
| 6429 |
the problem of Computer Base Instruction. |
| 6430 |
|
| 6431 |
312 McKenzie Mar 72 Proposed Change in IMP-to-Host |
| 6432 |
Protocol |
| 6433 |
|
| 6434 |
This RFC proposes a redefinition of the IMP-to-Host error message |
| 6435 |
types and the creation of additional IMP-to-Host error message |
| 6436 |
types. These changes should assist the Hosts in determining |
| 6437 |
|
| 6438 |
|
| 6439 |
<span class="grey">Reynolds & Postel [Page 115]</span></pre> |
| 6440 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-116" ></span> |
| 6441 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 6442 |
|
| 6443 |
|
| 6444 |
appropriate recovery action without causing any serious |
| 6445 |
reprogramming problems. |
| 6446 |
|
| 6447 |
311 Bryan Feb 72 New Console Attachments to the UCSB |
| 6448 |
Host |
| 6449 |
|
| 6450 |
Describes types of terminals used at UCSB. |
| 6451 |
|
| 6452 |
310 Bhushan Apr 72 Another Look at Data and File |
| 6453 |
Transfer Protocols |
| 6454 |
|
| 6455 |
This paper suggests some specific changes in DTP and FTP that |
| 6456 |
should make them more useful and/or simplify implementation. |
| 6457 |
|
| 6458 |
309 Bhushan Mar 72 Data and File Tranfer Workshop |
| 6459 |
Announcement |
| 6460 |
|
| 6461 |
Describes plans for a meeting on FTP to be held April 1972. |
| 6462 |
|
| 6463 |
308 Seriff Mar 72 ARPANET Host Availability Data |
| 6464 |
|
| 6465 |
A SURVEY program is up and working to aid in gathering information |
| 6466 |
on the availability of various Hosts on the ARPANET. |
| 6467 |
|
| 6468 |
307 Harslem Feb 72 Using Network Remote Job Entry |
| 6469 |
|
| 6470 |
Announcement of a program on a PDP-10 allowing access to the |
| 6471 |
Remote Job Service (RJS) at UCLA. |
| 6472 |
|
| 6473 |
306 Westheimer Feb 72 Network Host Status |
| 6474 |
|
| 6475 |
Updates <a href="./rfc298">RFC 298</a>. |
| 6476 |
|
| 6477 |
305 Alter Jan 72 Unknown Host Numbers |
| 6478 |
|
| 6479 |
Discusses testing of IMPs and notes that this may cause some hosts |
| 6480 |
to receive messages from unregistered addresses. |
| 6481 |
|
| 6482 |
304 McKay Feb 72 A Data Management System Proposal |
| 6483 |
for the ARPA Network |
| 6484 |
|
| 6485 |
A proposal to provide a framework that will allow the ARPA |
| 6486 |
community to recognize and develop the necessary tools in a |
| 6487 |
unified manner enabling the network to manage its resources to the |
| 6488 |
best advantage of the user. |
| 6489 |
|
| 6490 |
|
| 6491 |
|
| 6492 |
|
| 6493 |
|
| 6494 |
|
| 6495 |
<span class="grey">Reynolds & Postel [Page 116]</span></pre> |
| 6496 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-117" ></span> |
| 6497 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 6498 |
|
| 6499 |
|
| 6500 |
303 NIC Feb 72 ARPA Network Mailing List |
| 6501 |
|
| 6502 |
Obsoletes <a href="./rfc300">RFC 300</a>. |
| 6503 |
|
| 6504 |
302 Bryan Feb 72 Excercising the ARPANET |
| 6505 |
|
| 6506 |
Describes a class project to tryout hosts on the ARPANET. |
| 6507 |
|
| 6508 |
301 Alter Feb 72 BBN IMP (No. 5) and NCC Schedule for |
| 6509 |
March 4, 1972 |
| 6510 |
|
| 6511 |
BBN host will be down for a day for moving equipment. |
| 6512 |
|
| 6513 |
300 NIC Jan 72 ARPA Network Mailing Lists |
| 6514 |
|
| 6515 |
Obsoletes <a href="./rfc211">RFC 211</a>. |
| 6516 |
|
| 6517 |
299 Hopkin Feb 72 Information Management System |
| 6518 |
|
| 6519 |
Announcement of intent to build an Information Management and |
| 6520 |
Statistical System for the ILLIAC IV. |
| 6521 |
|
| 6522 |
298 Westheimer Feb 72 Network Host Status |
| 6523 |
|
| 6524 |
Updates <a href="./rfc293">RFC 293</a>. |
| 6525 |
|
| 6526 |
297 Walden Jan 72 TIP Message Buffers |
| 6527 |
|
| 6528 |
Discussion regarding the size of the TIP's message buffers. |
| 6529 |
|
| 6530 |
296 Liddle Jan 72 DS-1 Display System |
| 6531 |
|
| 6532 |
This RFC describes a proposed modular graphic/alphanumeric display |
| 6533 |
system containing a 512 by 512 line, 60 line per inch plasma |
| 6534 |
display/memory panel and a minprocessor. It is intended to |
| 6535 |
combine the advantages of display memory and local processing |
| 6536 |
power in three general modes. |
| 6537 |
|
| 6538 |
295 Postel Oct 71 Report of the Protocol Workshop |
| 6539 |
|
| 6540 |
A report on the decisions reached at the protocol workshop held in |
| 6541 |
conjunction with the NWG meeting of 10 October 1971. |
| 6542 |
|
| 6543 |
294 Bhushan Jan 72 The Use of "Set Data Type" |
| 6544 |
Transaction in File Transfer |
| 6545 |
Protocol |
| 6546 |
|
| 6547 |
Updates <a href="./rfc265">RFC 265</a>. |
| 6548 |
|
| 6549 |
|
| 6550 |
|
| 6551 |
<span class="grey">Reynolds & Postel [Page 117]</span></pre> |
| 6552 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-118" ></span> |
| 6553 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 6554 |
|
| 6555 |
|
| 6556 |
293 Westheimer Jan 72 Network Host Status |
| 6557 |
|
| 6558 |
Updates <a href="./rfc288">RFC 288</a>. |
| 6559 |
|
| 6560 |
292 Michener Jan 72 Graphics Protocol - Level 0 only |
| 6561 |
|
| 6562 |
A description of part of the proposed Network Standard Graphics |
| 6563 |
Protocol for transmitting graphics data within the ARPA network. |
| 6564 |
The particular aspects covered are related to the form and content |
| 6565 |
of graphics information sent from a source of graphical |
| 6566 |
information to a display package for output to a graphics console. |
| 6567 |
|
| 6568 |
291 McKay Jan 72 Data Management Meeting Announcement |
| 6569 |
|
| 6570 |
A meeting about datamanagement will be held February 1972. |
| 6571 |
|
| 6572 |
290 Mullery Jan 72 Computer Network and Data Sharing: A |
| 6573 |
Bibliography |
| 6574 |
|
| 6575 |
Updates <a href="./rfc243">RFC 243</a>. |
| 6576 |
|
| 6577 |
289 Watson Dec 71 What We Hope is an Official List of |
| 6578 |
Host Names |
| 6579 |
|
| 6580 |
An accepted list of official formal host names and nicknames. |
| 6581 |
|
| 6582 |
288 Westheimer Jan 72 Network Host Status |
| 6583 |
|
| 6584 |
Updates <a href="./rfc287">RFC 287</a>. |
| 6585 |
|
| 6586 |
287 Westheimer Dec 71 Network Host Status |
| 6587 |
|
| 6588 |
Reports on tests of host availability for 6 Dec to 18 Dec 1971. |
| 6589 |
|
| 6590 |
286 Forman Dec 71 Network Library Information System |
| 6591 |
|
| 6592 |
This RFC solicites interested parties in the ARPA community to |
| 6593 |
form a working group whose interests include developing a new |
| 6594 |
system that would enable computer query of Library holdings. |
| 6595 |
Georgetown University is currently designing a Learning Resource |
| 6596 |
Center which could be the prototype of the proposed working group. |
| 6597 |
|
| 6598 |
285 Huff Dec 71 Network Graphics |
| 6599 |
|
| 6600 |
This paper is aimed at bringing together the present state of |
| 6601 |
graphics on the NET for the newcomer and attempting to add a |
| 6602 |
little more documentation to the current ground covered in |
| 6603 |
graphics research by ARPA. |
| 6604 |
|
| 6605 |
|
| 6606 |
|
| 6607 |
<span class="grey">Reynolds & Postel [Page 118]</span></pre> |
| 6608 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-119" ></span> |
| 6609 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 6610 |
|
| 6611 |
|
| 6612 |
284 Never Issued. |
| 6613 |
|
| 6614 |
283 Braden Dec 71 NETRJT - Remote Job Service Protocol |
| 6615 |
for TIPS |
| 6616 |
|
| 6617 |
Discusses how it may be feasible in the future to use TIPS for |
| 6618 |
remote job entry in one or more of three ways: attach local card |
| 6619 |
readers, line printer, and card punches directly to TIP ports, |
| 6620 |
connect a remote batch terminal to a full-duplex TIP port via a |
| 6621 |
communication line, and/or use the tape drive, and do card-to-tape |
| 6622 |
and/or tape-to-print on another computer. |
| 6623 |
|
| 6624 |
282 Padlipsky Dec 71 Graphics Meeting Report |
| 6625 |
|
| 6626 |
Describes a graphics meeting held November 1972. |
| 6627 |
|
| 6628 |
281 McKenzie Dec 71 A Suggested Addition to File |
| 6629 |
Transfer Protocol |
| 6630 |
|
| 6631 |
Suggests an improved restart procedure in FTP. |
| 6632 |
|
| 6633 |
280 Watson Nov 71 A Draft Set of Host Names |
| 6634 |
|
| 6635 |
A proposed list of names for hosts. |
| 6636 |
|
| 6637 |
279 Never Issued. |
| 6638 |
|
| 6639 |
278 Bhushan Nov 71 Revision of the Mail Box Protocol |
| 6640 |
|
| 6641 |
This paper obsoletes <a href="./rfc221">RFC 221</a>. The changes to <a href="./rfc221">RFC 221</a> are |
| 6642 |
presented in this document. The protocol is also restated for |
| 6643 |
additional review. |
| 6644 |
|
| 6645 |
277 Never Issued. |
| 6646 |
|
| 6647 |
276 Watson Nov 71 NIC Course |
| 6648 |
|
| 6649 |
A course announcement from the NIC on the use of its Online System |
| 6650 |
(NLS). |
| 6651 |
|
| 6652 |
275 Never Issued. |
| 6653 |
|
| 6654 |
274 Forman Nov 71 Establishing a Local Guide for |
| 6655 |
Network Usage |
| 6656 |
|
| 6657 |
Discussion on the best solutions to the general problem of |
| 6658 |
interfacing Hosts to IMPs. |
| 6659 |
|
| 6660 |
|
| 6661 |
|
| 6662 |
|
| 6663 |
<span class="grey">Reynolds & Postel [Page 119]</span></pre> |
| 6664 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-120" ></span> |
| 6665 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 6666 |
|
| 6667 |
|
| 6668 |
273 Watson Oct 71 More on Standard Host Names |
| 6669 |
|
| 6670 |
Discussion on the best way to set up naming schemes for standard |
| 6671 |
Host names. |
| 6672 |
|
| 6673 |
272 Never Issued. |
| 6674 |
|
| 6675 |
271 Cosell Jan 72 IMP System Change Notification |
| 6676 |
|
| 6677 |
Announcement of a new version of the IMP System, Version 2514. |
| 6678 |
|
| 6679 |
270 McKenzie Jan 72 Correction to BBN Report No. 1822 |
| 6680 |
|
| 6681 |
Updates pages 25 and 26 of BBN report 1822. |
| 6682 |
|
| 6683 |
269 Brodie Dec 71 Some Experience with File Transfer |
| 6684 |
|
| 6685 |
Updates RFCs 122,238,172. |
| 6686 |
|
| 6687 |
268 Postel Nov 71 Graphic Facilities Information |
| 6688 |
|
| 6689 |
Request for graphics information. |
| 6690 |
|
| 6691 |
267 Westheimer Nov 71 Network Host Status |
| 6692 |
|
| 6693 |
Reports on tests of host availability for 8 Nov to 19 Nov 1971. |
| 6694 |
|
| 6695 |
266 Westheimer Nov 71 Network Host Status |
| 6696 |
|
| 6697 |
Reports on tests of host availability for 25 Oct to 5 Nov 1971. |
| 6698 |
|
| 6699 |
265 Bhushan Nov 71 The File Transfer Protocol |
| 6700 |
|
| 6701 |
This paper is a revision of <a href="./rfc172">RFC 172</a>. The changes to <a href="./rfc172">RFC 172</a> are |
| 6702 |
presented in this document. The protocol is also restated for |
| 6703 |
additional review. |
| 6704 |
|
| 6705 |
264 Bhushan Nov 71 The Data Transfer Protocol |
| 6706 |
|
| 6707 |
This paper is a revision of <a href="./rfc171">RFC 171</a>. The changes to <a href="./rfc171">RFC 171</a> are |
| 6708 |
presented in this document. The protocol is also restated for |
| 6709 |
additional review. |
| 6710 |
|
| 6711 |
263 McKenzie Dec 71 "Very Distant" Host Interface |
| 6712 |
|
| 6713 |
Discussion on the best solutions to the general problem of |
| 6714 |
interfacing Hosts to IMPs. |
| 6715 |
|
| 6716 |
262 Never Issued. |
| 6717 |
|
| 6718 |
|
| 6719 |
<span class="grey">Reynolds & Postel [Page 120]</span></pre> |
| 6720 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-121" ></span> |
| 6721 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 6722 |
|
| 6723 |
|
| 6724 |
261 Never Issued. |
| 6725 |
|
| 6726 |
260 Never Issued. |
| 6727 |
|
| 6728 |
259 Never Issued. |
| 6729 |
|
| 6730 |
258 Never Issued. |
| 6731 |
|
| 6732 |
257 Never Issued. |
| 6733 |
|
| 6734 |
256 Cosell Nov 71 IMPSYS Change Notification |
| 6735 |
|
| 6736 |
Announcement of a new version of the IMP system, Version 2513. |
| 6737 |
|
| 6738 |
255 Westheimer Oct 71 Site Status |
| 6739 |
|
| 6740 |
Updates <a href="./rfc252">RFC 252</a>. |
| 6741 |
|
| 6742 |
254 Bhushan Oct 71 Scenarios for Using ARPANET |
| 6743 |
Computers |
| 6744 |
|
| 6745 |
This document is provided to facilitate the use of ARPANET host |
| 6746 |
computer systems via the ARPANET. The objective of these |
| 6747 |
scenarios is to aid a user in sampling host computers on the |
| 6748 |
ARPANET, thereby stimulating his interest in using the ARPANET. |
| 6749 |
|
| 6750 |
253 Moorer Oct 71 Second Network Graphics Meeting |
| 6751 |
Details |
| 6752 |
|
| 6753 |
Plans for a graphics meeting to be held November 1971. See <a href="./rfc282">RFC</a> |
| 6754 |
<a href="./rfc282">282</a>. |
| 6755 |
|
| 6756 |
252 Westheimer Oct 71 Site Status |
| 6757 |
|
| 6758 |
Updates <a href="./rfc240">RFC 240</a>. |
| 6759 |
|
| 6760 |
251 Stern Oct 71 Weather Data |
| 6761 |
|
| 6762 |
Announcement of the USAF Environmental Technical Application |
| 6763 |
Center (ETAC) services in providing weather data for the ARPA |
| 6764 |
Network. |
| 6765 |
|
| 6766 |
250 Brodie Oct 71 Some Thoughts on File Transfer |
| 6767 |
|
| 6768 |
Further clarification and proposed revision on several aspects of |
| 6769 |
the proposed Data Transfer Protocol and the File Transfer |
| 6770 |
Protocol. |
| 6771 |
|
| 6772 |
|
| 6773 |
|
| 6774 |
|
| 6775 |
<span class="grey">Reynolds & Postel [Page 121]</span></pre> |
| 6776 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-122" ></span> |
| 6777 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 6778 |
|
| 6779 |
|
| 6780 |
249 Borelli Oct 71 Coordination of Equipment and |
| 6781 |
Supplies Purchase |
| 6782 |
|
| 6783 |
Announcement of an agreement reached regarding the study of the |
| 6784 |
feasibility of a coordinating point for purchases of equipment and |
| 6785 |
supplies to be used on the network. |
| 6786 |
|
| 6787 |
248 Never Issued. |
| 6788 |
|
| 6789 |
247 Karp Oct 71 Proffered Set of Standard Host Names |
| 6790 |
|
| 6791 |
Proposed general set of rules for forming Host Names. Obsoletes |
| 6792 |
<a href="./rfc226">RFC 226</a>. |
| 6793 |
|
| 6794 |
246 Vezza Oct 71 Networks Graphics Meeting |
| 6795 |
|
| 6796 |
245 Falls Oct 71 Reservations for Network Group |
| 6797 |
Meeting |
| 6798 |
|
| 6799 |
244 Never Issued. |
| 6800 |
|
| 6801 |
243 Mullery Oct 71 Network and Data Sharing |
| 6802 |
Bibliography |
| 6803 |
|
| 6804 |
Updated by <a href="./rfc290">RFC 290</a>. |
| 6805 |
|
| 6806 |
242 Haibt Jul 71 Data Descriptive Language for Shared |
| 6807 |
Data |
| 6808 |
|
| 6809 |
Discussion of representation differences. Three categories are |
| 6810 |
defined: very local representation, representation of collections |
| 6811 |
of data, and other more complex structures that data collections |
| 6812 |
may have. |
| 6813 |
|
| 6814 |
241 McKenzie Sep 71 Connecting Computers to MLC Ports |
| 6815 |
|
| 6816 |
Discussion on the pros and cons of computers being connected |
| 6817 |
through serial communication lines to ports on the Terminal IMP's |
| 6818 |
Multi-Line Controller (MLC). |
| 6819 |
|
| 6820 |
240 McKenzie Sep 71 Site Status |
| 6821 |
|
| 6822 |
A reissue of <a href="./rfc235">RFC 235</a>, without typographical errors. |
| 6823 |
|
| 6824 |
239 Braden Sep 71 Host Mnemonics Proposed in <a href="./rfc226">RFC 226</a> |
| 6825 |
|
| 6826 |
Discussion and comments on <a href="./rfc226">RFC 226</a>. |
| 6827 |
|
| 6828 |
|
| 6829 |
|
| 6830 |
|
| 6831 |
<span class="grey">Reynolds & Postel [Page 122]</span></pre> |
| 6832 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-123" ></span> |
| 6833 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 6834 |
|
| 6835 |
|
| 6836 |
238 Braden Sep 71 Comments on DTP and FTP Protocols |
| 6837 |
|
| 6838 |
This RFC updates RFCs 171,172. |
| 6839 |
|
| 6840 |
237 Watson Sep 71 The NIC's View of Standard Host |
| 6841 |
Names |
| 6842 |
|
| 6843 |
The NIC strongly favors standardization of host names. In this |
| 6844 |
RFC, the NIC proposes that any standard naming scheme should take |
| 6845 |
into account certain considerations. |
| 6846 |
|
| 6847 |
236 Postel Sep 71 Standard Host Names |
| 6848 |
|
| 6849 |
An update of <a href="./rfc229">RFC 229</a>, with some modifications included. |
| 6850 |
|
| 6851 |
235 Westheimer Sep 71 Site Status |
| 6852 |
|
| 6853 |
Starting with this RFC, BBN will report on the status of most |
| 6854 |
Network Hosts. |
| 6855 |
|
| 6856 |
234 Vezza Oct 71 Network Working Group Meeting |
| 6857 |
Schedule |
| 6858 |
|
| 6859 |
Plans for a Network Working Group meeting in October 1971. |
| 6860 |
|
| 6861 |
233 Bhushan Sep 71 Standardization of Host Call Letters |
| 6862 |
|
| 6863 |
A currently recommended list of call letters. |
| 6864 |
|
| 6865 |
232 Vezza Sep 71 Announcement of the next Network |
| 6866 |
Graphics Meeting |
| 6867 |
|
| 6868 |
Schedule conflict and postponement of the graphics meeting. |
| 6869 |
|
| 6870 |
231 Heafner Sep 71 Service Center Standards for Remote |
| 6871 |
Usage - A User's View |
| 6872 |
|
| 6873 |
A statement of views on service center standards. An input to the |
| 6874 |
service center panel discussion of the October Network meeting. |
| 6875 |
|
| 6876 |
230 Pyke Sep 71 Toward Reliable Operation of |
| 6877 |
Minicomputer-based Terminals on a |
| 6878 |
TIP |
| 6879 |
|
| 6880 |
Points out inadequate error detection and initiation of corrective |
| 6881 |
measures in the present protocol for communication between a TIP |
| 6882 |
and attached terminals. References <a href="./rfc203">RFC 203</a>. |
| 6883 |
|
| 6884 |
|
| 6885 |
|
| 6886 |
|
| 6887 |
<span class="grey">Reynolds & Postel [Page 123]</span></pre> |
| 6888 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-124" ></span> |
| 6889 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 6890 |
|
| 6891 |
|
| 6892 |
229 Postel Sep 71 Standard Host Names |
| 6893 |
|
| 6894 |
A suggestion of eight character names and a proposed list of |
| 6895 |
names. |
| 6896 |
|
| 6897 |
228 Walden Sep 71 Clarification |
| 6898 |
|
| 6899 |
A correction to <a href="./rfc70">RFC 70</a>. |
| 6900 |
|
| 6901 |
227 Heafner Sep 71 Data Transfer Rates (RAND/UCLA) |
| 6902 |
|
| 6903 |
A memo on data rates typical of the RJS use at UCLA CCN. |
| 6904 |
|
| 6905 |
226 Karp Sep 71 Standardization of Host Mnemonics |
| 6906 |
|
| 6907 |
A list of Host Mnemonics is provided. |
| 6908 |
|
| 6909 |
225 Harslem Sep 71 RAND/UCSB Network Graphics |
| 6910 |
Experiment |
| 6911 |
|
| 6912 |
Describes use from RAND of the UCSB-OLS system. |
| 6913 |
|
| 6914 |
224 McKenzie Sep 71 Comments on Mailbox Protocol |
| 6915 |
|
| 6916 |
Comments on electronic mail and TIP's. |
| 6917 |
|
| 6918 |
223 Melvin Sep 71 Network Information Center Schedule |
| 6919 |
for Network Users |
| 6920 |
|
| 6921 |
Access schedule for remote users of the NIC. |
| 6922 |
|
| 6923 |
222 Metcalfe Sep 71 System Programmer's Workshop |
| 6924 |
|
| 6925 |
Announcement of the next workshop. |
| 6926 |
|
| 6927 |
221 Watson Aug 71 A Mail Box Protocol, Version-2 |
| 6928 |
|
| 6929 |
Discussion of the initial reaction to <a href="./rfc196">RFC 196</a>. |
| 6930 |
|
| 6931 |
220 Never Issued |
| 6932 |
|
| 6933 |
219 Winter Sep 71 User's View of the Datacomputer |
| 6934 |
|
| 6935 |
A description of the Datacomputer. |
| 6936 |
|
| 6937 |
|
| 6938 |
|
| 6939 |
|
| 6940 |
|
| 6941 |
|
| 6942 |
|
| 6943 |
<span class="grey">Reynolds & Postel [Page 124]</span></pre> |
| 6944 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-125" ></span> |
| 6945 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 6946 |
|
| 6947 |
|
| 6948 |
218 Cosell Sep 71 Changing the IMP Status Reporting |
| 6949 |
|
| 6950 |
A change in internal procedures in the ARPANET status reports from |
| 6951 |
the IMPs to the NIC. |
| 6952 |
|
| 6953 |
217 White Sep 71 Specification Changes for OLS, |
| 6954 |
RJE/RJOR, and SMFS |
| 6955 |
|
| 6956 |
Current listing of documents that have been revised. |
| 6957 |
|
| 6958 |
216 White Sep 71 Telnet Access to UCSB's On-Line |
| 6959 |
System |
| 6960 |
|
| 6961 |
Discussion of the implementation of a teletype-compatible |
| 6962 |
interface to UCSB's On-Line System. |
| 6963 |
|
| 6964 |
215 McKenzie Aug 71 NCP, ICP, and Telnet: The Terminal |
| 6965 |
IMP Implementation |
| 6966 |
|
| 6967 |
Announcement of six Terminal IMPs being incorporated into the |
| 6968 |
Network, with additional Terminal IMPS scheduled for delivery. |
| 6969 |
|
| 6970 |
214 Harslem Aug 71 Network Checkout |
| 6971 |
|
| 6972 |
Notification of the verification of certain sites. |
| 6973 |
|
| 6974 |
213 Cosell Aug 71 IMP System Change Notification |
| 6975 |
|
| 6976 |
Several changes in the IMP internal procedures. |
| 6977 |
|
| 6978 |
212 Vezza Aug 71 NWG Meeting on Network Usage |
| 6979 |
|
| 6980 |
A mailing list for RFC distribution. |
| 6981 |
|
| 6982 |
211 NIC Aug 71 ARPA Network Mailing List |
| 6983 |
|
| 6984 |
210 Conrad Aug 71 Improvement of Flow Control |
| 6985 |
|
| 6986 |
Discussion of the current "give back" - "return" scheme. |
| 6987 |
|
| 6988 |
209 Cosell Aug 71 Host/IMP Interface Documentation |
| 6989 |
|
| 6990 |
Discussion of a change to the IMP and the documentation |
| 6991 |
(BBN report 1822). |
| 6992 |
|
| 6993 |
|
| 6994 |
|
| 6995 |
|
| 6996 |
|
| 6997 |
|
| 6998 |
|
| 6999 |
<span class="grey">Reynolds & Postel [Page 125]</span></pre> |
| 7000 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-126" ></span> |
| 7001 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 7002 |
|
| 7003 |
|
| 7004 |
208 McKenzie Aug 71 Address Tables |
| 7005 |
|
| 7006 |
A table of hosts on or soon to be on the ARPANET. |
| 7007 |
|
| 7008 |
207 Vezza Aug 71 A September Network Working Group |
| 7009 |
Meeting |
| 7010 |
|
| 7011 |
Next meeting announcement. |
| 7012 |
|
| 7013 |
206 White Aug 71 A User Telnet Description of an |
| 7014 |
Initial Implementation |
| 7015 |
|
| 7016 |
This document describes a program whose function is to make an |
| 7017 |
Online System terminal appear to any teletype-compatible, |
| 7018 |
time-sharing system in the Network as if it were directly |
| 7019 |
connected to that system. |
| 7020 |
|
| 7021 |
205 Braden Aug 71 NETCRT - A Character Display |
| 7022 |
Protocol |
| 7023 |
|
| 7024 |
A significant revision of the character-display protocol (NETCRT), |
| 7025 |
based on CCN's proposed NETCRT from the May NWG Meeting. |
| 7026 |
|
| 7027 |
204 Postel Aug 71 Sockets in use |
| 7028 |
|
| 7029 |
Announcement to collect information on the use of socket numbers |
| 7030 |
for standard service programs. |
| 7031 |
|
| 7032 |
203 Kalin Aug 71 Achieving Reliable Communication |
| 7033 |
|
| 7034 |
This is a non-standard protocol, suitable for either second or |
| 7035 |
third level use and is proposed with the intent of providing error |
| 7036 |
resistant and highly reliable communication channels. |
| 7037 |
|
| 7038 |
202 Wolfe Jul 71 Possible Deadlock in ICP |
| 7039 |
|
| 7040 |
A notation of a possible deadlock that will occur if both sides |
| 7041 |
open thier send or both sides open their receive sockets first. |
| 7042 |
|
| 7043 |
201 Never Issued. |
| 7044 |
|
| 7045 |
200 NIC Aug 71 RFC List by Number |
| 7046 |
|
| 7047 |
RFC's 1-200. |
| 7048 |
|
| 7049 |
|
| 7050 |
|
| 7051 |
|
| 7052 |
|
| 7053 |
|
| 7054 |
|
| 7055 |
<span class="grey">Reynolds & Postel [Page 126]</span></pre> |
| 7056 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-127" ></span> |
| 7057 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 7058 |
|
| 7059 |
|
| 7060 |
199 Williams Jul 71 Suggestions for a Network |
| 7061 |
Data-Tablet Graphics Protocol |
| 7062 |
|
| 7063 |
SDC's comments to the discussion of a protocol for network |
| 7064 |
graphics within the ARPA Network community. Concern is focused on |
| 7065 |
the development of the graphics protocol in two areas: |
| 7066 |
non-interactive graphics and data-tablet graphics, as opposed to |
| 7067 |
fully interactive graphics. |
| 7068 |
|
| 7069 |
198 Heafner Jul 71 Site Certification - Lincoln Labs |
| 7070 |
360/67 |
| 7071 |
|
| 7072 |
A report from RAND that Lincoln Labs protocol implementations are |
| 7073 |
correct. |
| 7074 |
|
| 7075 |
197 Shoshani Jul 71 Initial Connection Protocol - |
| 7076 |
Revised |
| 7077 |
|
| 7078 |
An attempt at a simple version of ICP, assuming one may add |
| 7079 |
commands to Host-Host protocol. |
| 7080 |
|
| 7081 |
196 Watson Jul 71 A Mail Box Protocol |
| 7082 |
|
| 7083 |
The purpose of this protocol is to provide at each site a standard |
| 7084 |
mechanism to receive sequential files for immediate or deferred |
| 7085 |
printing or other uses. |
| 7086 |
|
| 7087 |
195 Mealy Jul 71 Data Computers - Data Descriptions |
| 7088 |
and Access Language |
| 7089 |
|
| 7090 |
This document discusses some of the problems involved in the |
| 7091 |
unified approach to Network data management, and to suggest |
| 7092 |
possible avenues of approach toward their resolution. |
| 7093 |
|
| 7094 |
194 Cerf Jul 71 The Data Reconfiguration Service - |
| 7095 |
Compiler/Interpreter Implementation |
| 7096 |
Notes |
| 7097 |
|
| 7098 |
This document describes the new features of the language, the new |
| 7099 |
syntax, the form interpreter, and the instruction set. |
| 7100 |
|
| 7101 |
193 Harslem Jul 71 Network Checkout |
| 7102 |
|
| 7103 |
A report form RAND on testing ten other hosts. |
| 7104 |
|
| 7105 |
|
| 7106 |
|
| 7107 |
|
| 7108 |
|
| 7109 |
|
| 7110 |
|
| 7111 |
<span class="grey">Reynolds & Postel [Page 127]</span></pre> |
| 7112 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-128" ></span> |
| 7113 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 7114 |
|
| 7115 |
|
| 7116 |
192 Watson Jul 71 Some Factors Which a Network |
| 7117 |
Graphics Protocol Must Consider |
| 7118 |
|
| 7119 |
Discussion on what any network graphics protocol should come to |
| 7120 |
grips with. |
| 7121 |
|
| 7122 |
191 Irby Jul 71 Graphics Implementation and |
| 7123 |
Conceptualization at ARC |
| 7124 |
|
| 7125 |
A brief description of the way in which graphics terminals are |
| 7126 |
conceptualized and used at the Augmentation Research Center. |
| 7127 |
|
| 7128 |
190 Deutsch Jul 71 DEC PDP-10 - IMLAC Communication |
| 7129 |
System |
| 7130 |
|
| 7131 |
This document describes an operational system for communicating |
| 7132 |
textual display information between a main-site computer and a |
| 7133 |
remote display processor. |
| 7134 |
|
| 7135 |
189 Braden Jul 71 Interim NETRJS Specifications |
| 7136 |
|
| 7137 |
A description of the operation and protocol of the remote job |
| 7138 |
entry service to CCN's 360 Model 91. This interim protocol will |
| 7139 |
be implemented as a production service before the end of July. |
| 7140 |
|
| 7141 |
188 Karp Jan 71 Data Management Meeting Announcement |
| 7142 |
|
| 7143 |
Plans for a data management meeting to be held Auguest 1971. |
| 7144 |
|
| 7145 |
187 McKay Jul 71 A Network/440 Protocol Concept |
| 7146 |
|
| 7147 |
An information Request for Comments that is intended to convey |
| 7148 |
some of the thinking and philosophy that went into IBM's network |
| 7149 |
protocol and overall network design. |
| 7150 |
|
| 7151 |
186 Michener Jul 71 A Network Graphics Loader |
| 7152 |
|
| 7153 |
The Network Graphics Loader described in this document proposes to |
| 7154 |
permit remote users on the ARPA network to obtain graphics output |
| 7155 |
from programs they write for the Evans and Sutherland Line Drawing |
| 7156 |
System. |
| 7157 |
|
| 7158 |
185 North Jul 71 NIC Distribution of Manuals and |
| 7159 |
Handbooks |
| 7160 |
|
| 7161 |
The NIC request that sites send copies of manuals and handbooks to |
| 7162 |
them. |
| 7163 |
|
| 7164 |
|
| 7165 |
|
| 7166 |
|
| 7167 |
<span class="grey">Reynolds & Postel [Page 128]</span></pre> |
| 7168 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-129" ></span> |
| 7169 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 7170 |
|
| 7171 |
|
| 7172 |
184 Kelley Jul 71 Proposed Graphic Display Modes |
| 7173 |
|
| 7174 |
The ARPA Network node at the University of Illinois' Center for |
| 7175 |
Advanced Computation is different from other nodes. It is not |
| 7176 |
just a simple attachment to the net. Establishment of the |
| 7177 |
computer system specifically for use of the ILLIAC IV and the |
| 7178 |
network is in process. This paper describes the operating |
| 7179 |
systems, network interface and utility routines, and ILLIAC IV |
| 7180 |
routines to be used over the network. |
| 7181 |
|
| 7182 |
183 Winett Jul 71 The EBCDIC Codes and Their Mapping |
| 7183 |
to ASCII |
| 7184 |
|
| 7185 |
This document defines and describes the IBM Standard Extended BCD |
| 7186 |
Interchange Code. This is done in order to uniquely map the ASCII |
| 7187 |
codes into corresponding EBCDIC codes in a consistent manner |
| 7188 |
throughout the ARPA Network. |
| 7189 |
|
| 7190 |
182 North Jun 71 Compilation of List of Relevant Site |
| 7191 |
Reports |
| 7192 |
|
| 7193 |
A Network Information Center compilation list of all site-produced |
| 7194 |
reports which are of interest to Network participants. |
| 7195 |
|
| 7196 |
181 McConnell Jun 71 Modifications to <a href="./rfc177">RFC 177</a> |
| 7197 |
|
| 7198 |
This document is intended to modify the proposal for a device |
| 7199 |
independent graphical display description discussed in <a href="./rfc177">RFC 177</a>. |
| 7200 |
The main changes are in the definition of coordinate areas to |
| 7201 |
avoid one problem encountered with the old definition and to |
| 7202 |
provide more flexibility. |
| 7203 |
|
| 7204 |
180 McKenzie Jun 71 File System Questionnaire |
| 7205 |
|
| 7206 |
An attempt to gather information about local file and data |
| 7207 |
conventions. |
| 7208 |
|
| 7209 |
179 McKenzie Jun 71 Link Number Assignments |
| 7210 |
|
| 7211 |
This RFC has been replaced by RFCs 997 and 990. |
| 7212 |
|
| 7213 |
178 Cotton Jun 71 Network Graphic Attention Handling |
| 7214 |
|
| 7215 |
The process of attention handling is briefly described, various |
| 7216 |
graphic configurations are discussed, input devices are surveyed |
| 7217 |
to identify the types of data which they produce, and an attention |
| 7218 |
protocol is proposed. |
| 7219 |
|
| 7220 |
|
| 7221 |
|
| 7222 |
|
| 7223 |
<span class="grey">Reynolds & Postel [Page 129]</span></pre> |
| 7224 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-130" ></span> |
| 7225 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 7226 |
|
| 7227 |
|
| 7228 |
177 McConnell Jun 71 A Device Independent Graphical |
| 7229 |
Display Description |
| 7230 |
|
| 7231 |
As more nodes are connected to the ARPA network, the types of |
| 7232 |
graphical display processors available to users is quite varied. |
| 7233 |
To attempt to facilitate the transmission of graphical information |
| 7234 |
over the network, a device independent description of a display is |
| 7235 |
described. |
| 7236 |
|
| 7237 |
176 Bhushan Jun 71 Comments on Byte Size for |
| 7238 |
Connections |
| 7239 |
|
| 7240 |
This document points out three views on the use of byte size for |
| 7241 |
network connections: 1) Byte size should not be used at all. 2) |
| 7242 |
Byte size is solely for the convenience of NCP's. 3) Byte size |
| 7243 |
choice is a user-level prerogative. |
| 7244 |
|
| 7245 |
175 Harslem Jun 71 Comments on "Socket Conventions |
| 7246 |
Reconsidered" |
| 7247 |
|
| 7248 |
Pro and con discussion regarding <a href="./rfc167">RFC 167</a>. |
| 7249 |
|
| 7250 |
174 Postel Jun 71 UCLA-Computer Science Graphics |
| 7251 |
Overview |
| 7252 |
|
| 7253 |
This document provides an overview of the hardware, software, and |
| 7254 |
intentions of the UCLA Computer Science Department's Graphics |
| 7255 |
project. |
| 7256 |
|
| 7257 |
173 Karp Jun 71 Network Data Management Committeee |
| 7258 |
Meeting Announcement |
| 7259 |
|
| 7260 |
A report on the formation of a data managment committee and on its |
| 7261 |
first meeting. |
| 7262 |
|
| 7263 |
172 Bhushan Jun 71 The File Transfer Protocol |
| 7264 |
|
| 7265 |
This protocol is a user-level protocol for file transfer between |
| 7266 |
host computers (including terminal IMPs), on the ARPA computer |
| 7267 |
network. The File Transfer Protocol (FTP) uses the data transfer |
| 7268 |
protocol described in <a href="./rfc171">RFC 171</a>. This paper assumes knowledge of |
| 7269 |
<a href="./rfc171">RFC 171</a>. |
| 7270 |
|
| 7271 |
171 Bhushan Jun 71 The Data Transfer Protocol |
| 7272 |
|
| 7273 |
Definition of a low-level Data Transfer Protocol (DTP) to be used |
| 7274 |
for transfer of data in file transfer, remote job entry, and other |
| 7275 |
applications oriented protocols. A companion paper (<a href="./rfc172">RFC 172</a>) |
| 7276 |
describes file transfer protocol. |
| 7277 |
|
| 7278 |
|
| 7279 |
<span class="grey">Reynolds & Postel [Page 130]</span></pre> |
| 7280 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-131" ></span> |
| 7281 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 7282 |
|
| 7283 |
|
| 7284 |
170 NIC Jun 71 RFC List by Number |
| 7285 |
|
| 7286 |
A list of RFCs 1-170. |
| 7287 |
|
| 7288 |
168 North May 71 ARPA Network Mailing Lists |
| 7289 |
|
| 7290 |
Distribution list for RFCs. |
| 7291 |
|
| 7292 |
167 Bhushan May 71 Socket Conventions Reconsidered |
| 7293 |
|
| 7294 |
The recent NCP Protocol said nothing about how hosts should assign |
| 7295 |
socket numbers to process ports, except that the low-order bit is |
| 7296 |
to specify socket gender. This document discusses two recent |
| 7297 |
proposals that call for additional network-wide conventions on the |
| 7298 |
32-bit socket number. |
| 7299 |
|
| 7300 |
166 Anderson May 71 Data Reconfiguration Service - An |
| 7301 |
Implementation Specification |
| 7302 |
|
| 7303 |
This DRS experiment involved a software mechanism to reformat |
| 7304 |
Network data streams. The mechanism can be adapted to numerous |
| 7305 |
Network application programs. |
| 7306 |
|
| 7307 |
165 Postel May 71 A Proferred Official Initial |
| 7308 |
Connection Protocol |
| 7309 |
|
| 7310 |
This document specifies the third level protocol used to connect a |
| 7311 |
user process at one site with a server process at another site. |
| 7312 |
|
| 7313 |
164 Heafner May 71 Minutes of Network Working Group |
| 7314 |
Meeting |
| 7315 |
|
| 7316 |
A 38 page reference on the discussions held at the Network Working |
| 7317 |
Group Meeting. |
| 7318 |
|
| 7319 |
163 Cerf May 71 Data Transfer Protocols |
| 7320 |
|
| 7321 |
An informal statement on Data Transfer Protocols, in relation to |
| 7322 |
material discussed at the SJCC. |
| 7323 |
|
| 7324 |
162 Kampe May 71 NETBUGGER3 |
| 7325 |
|
| 7326 |
Discussion of NETBUGGER3 as a third level program for the |
| 7327 |
debugging of second and third level programs, experimentation with |
| 7328 |
and simulation of third level protocols. |
| 7329 |
|
| 7330 |
|
| 7331 |
|
| 7332 |
|
| 7333 |
|
| 7334 |
|
| 7335 |
<span class="grey">Reynolds & Postel [Page 131]</span></pre> |
| 7336 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-132" ></span> |
| 7337 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 7338 |
|
| 7339 |
|
| 7340 |
161 Shoshani May 71 A Solution to the Race Condition in |
| 7341 |
the ICP |
| 7342 |
|
| 7343 |
A proposed solution to a problem that arose out of <a href="./rfc143">RFC 143</a>. |
| 7344 |
|
| 7345 |
160 NIC May 71 RFC Brief List |
| 7346 |
|
| 7347 |
Title or Partial Title RFC List (1-160) |
| 7348 |
|
| 7349 |
159 Never Issued. |
| 7350 |
|
| 7351 |
158 O'Sullivan May 71 Proposed Telnet Protocol |
| 7352 |
|
| 7353 |
Solicitation of comments, evaluation, and requests for |
| 7354 |
modification of the proposed Telnet protocol. |
| 7355 |
|
| 7356 |
157 Cerf May 71 Invitation to the Second Symposium |
| 7357 |
on Problems in the Optimization of |
| 7358 |
Data Communication Systems |
| 7359 |
|
| 7360 |
Announcement of an ACM/IEEE conference on data communication. |
| 7361 |
|
| 7362 |
156 Bouknight Apr 71 Status of the Illinois Site |
| 7363 |
(Response to <a href="./rfc116">RFC 116</a>) |
| 7364 |
|
| 7365 |
Discusses the status of the operational hardware at the Illinois |
| 7366 |
site. |
| 7367 |
|
| 7368 |
155 NIC May 71 List to Receive RFCs |
| 7369 |
|
| 7370 |
Mailing list of people who are receiving the initial distribution |
| 7371 |
of RFCs. |
| 7372 |
|
| 7373 |
154 Crocker May 71 Exposition Style |
| 7374 |
|
| 7375 |
A note on style in documentation. |
| 7376 |
|
| 7377 |
153 Melvin May 71 SRI ARC-NIC Status |
| 7378 |
|
| 7379 |
Discusses the current computer and network status of the SRI |
| 7380 |
ARC-NIC. |
| 7381 |
|
| 7382 |
152 Wilber May 71 SRI Artificial Intelligence Status |
| 7383 |
Report |
| 7384 |
|
| 7385 |
Status report on SRAI's connection to the ARPANET as a research |
| 7386 |
center. |
| 7387 |
|
| 7388 |
|
| 7389 |
|
| 7390 |
|
| 7391 |
<span class="grey">Reynolds & Postel [Page 132]</span></pre> |
| 7392 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-133" ></span> |
| 7393 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 7394 |
|
| 7395 |
|
| 7396 |
151 Shoshani May 71 Comments on a Proferred Official ICP |
| 7397 |
(RFCs 123,127) |
| 7398 |
|
| 7399 |
Specific and general remarks regarding the ICP. |
| 7400 |
|
| 7401 |
150 Kalin May 71 The Use of IPC Facilities |
| 7402 |
|
| 7403 |
A working paper discussing the exposition of the types of usage to |
| 7404 |
which an IPC facility would be subjected. This document hopes to |
| 7405 |
clarify the goals being pursued and should provide a benchmark for |
| 7406 |
gauging various implementation strategies. |
| 7407 |
|
| 7408 |
149 Crocker May 71 The Best Laid Plans... |
| 7409 |
|
| 7410 |
Changes to the topics and attendees of the upcoming NWG meeting. |
| 7411 |
|
| 7412 |
148 Bhushan May 71 Comments on <a href="./rfc123">RFC 123</a> |
| 7413 |
|
| 7414 |
Regarding the byte size requirements for the initial connection. |
| 7415 |
|
| 7416 |
147 Winett May 71 The Definition of a Socket |
| 7417 |
|
| 7418 |
Defining, specifying, and identifying sockets. |
| 7419 |
|
| 7420 |
146 Karp May 71 Views on Issues Relevant to Data |
| 7421 |
Sharing on Computer Networks |
| 7422 |
|
| 7423 |
Concurrence with the views presented in <a href="./rfc140">RFC 140</a>. |
| 7424 |
|
| 7425 |
145 Postel May 71 Initial Connection Protocol Control |
| 7426 |
Commands |
| 7427 |
|
| 7428 |
An interpretation of the exchange between NCP's which would be |
| 7429 |
necessary to carry out the Initial Connection Protocol (ICP) of |
| 7430 |
<a href="./rfc123">RFC 123</a>. |
| 7431 |
|
| 7432 |
144 Shoshani Apr 71 Data Sharing on Computer Networks |
| 7433 |
|
| 7434 |
An introductory paper for the upcoming NWG meeting in Atlantic |
| 7435 |
City. |
| 7436 |
|
| 7437 |
143 Naylor May 71 Regarding Proferred Official ICP |
| 7438 |
|
| 7439 |
Comments on a race condition discovered in the ICP as proposed in |
| 7440 |
<a href="./rfc123">RFC 123</a>. |
| 7441 |
|
| 7442 |
|
| 7443 |
|
| 7444 |
|
| 7445 |
|
| 7446 |
|
| 7447 |
<span class="grey">Reynolds & Postel [Page 133]</span></pre> |
| 7448 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-134" ></span> |
| 7449 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 7450 |
|
| 7451 |
|
| 7452 |
142 Kline May 71 Time-out Mechanism in the Host-Host |
| 7453 |
Protocol |
| 7454 |
|
| 7455 |
Discussion on potential situations that can occur when sending a |
| 7456 |
message to a foreign site. |
| 7457 |
|
| 7458 |
141 Harslem Apr 71 Comments on <a href="./rfc114">RFC 114</a> (A File Transfer |
| 7459 |
Protocol) |
| 7460 |
|
| 7461 |
Further discussion on the File Transfer Protocol. |
| 7462 |
|
| 7463 |
140 Crocker May 71 Agenda for the May NWG Meeting |
| 7464 |
|
| 7465 |
A list of topics to be discussed at the upcoming meeting, plus a |
| 7466 |
listing of relevant RFCs that should be reviewed prior to the |
| 7467 |
meeting. |
| 7468 |
|
| 7469 |
139 O'Sullivan May 71 Discussion of Telnet Protocol |
| 7470 |
|
| 7471 |
An extension of <a href="./rfc137">RFC 137</a>. |
| 7472 |
|
| 7473 |
138 Anderson Apr 71 Status Report on Proposed Data |
| 7474 |
Reconfiguration Service |
| 7475 |
|
| 7476 |
Provides a description of a proposed Network experiment and to |
| 7477 |
solicit comments on any aspect of the experiment. |
| 7478 |
|
| 7479 |
137 O'Sullivan Apr 71 Telnet Protocol - A Proposed |
| 7480 |
Document |
| 7481 |
|
| 7482 |
Solicitation for review and comment before the Atlantic City NWG |
| 7483 |
meetings. |
| 7484 |
|
| 7485 |
136 Kahn Apr 71 Host Accounting and Administrative |
| 7486 |
Procedures |
| 7487 |
|
| 7488 |
Discussion of a plan to be formulated and accepted for the |
| 7489 |
development of a Host accounting system in the ARPA Network. |
| 7490 |
|
| 7491 |
135 Hathaway Apr 71 Response to <a href="./rfc110">RFC 110</a> |
| 7492 |
|
| 7493 |
Comments and proposals of new conventions to replace the ones |
| 7494 |
proposed in <a href="./rfc110">RFC 110</a>. |
| 7495 |
|
| 7496 |
134 Vezza Apr 71 Network Graphics Meeting |
| 7497 |
|
| 7498 |
Announcement of the next Network Graphics Meeting at Project MAC |
| 7499 |
in July 1971. |
| 7500 |
|
| 7501 |
|
| 7502 |
|
| 7503 |
<span class="grey">Reynolds & Postel [Page 134]</span></pre> |
| 7504 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-135" ></span> |
| 7505 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 7506 |
|
| 7507 |
|
| 7508 |
133 Sundberg Apr 71 File Transfer and Error Recovery |
| 7509 |
|
| 7510 |
Sample interchanges and comments on file transfer and errors. |
| 7511 |
|
| 7512 |
132 White Apr 71 Typographical Error in <a href="./rfc107">RFC 107</a> |
| 7513 |
|
| 7514 |
Points out an error in <a href="./rfc107">RFC 107</a>. |
| 7515 |
|
| 7516 |
131 Harslem Apr 71 Response to <a href="./rfc116">RFC 116</a> (May NWG |
| 7517 |
Meeting) |
| 7518 |
|
| 7519 |
A description of networr plans at RAND, including the data |
| 7520 |
reconfiguration service, and a comment on the role of the NWG. |
| 7521 |
|
| 7522 |
130 Heafner Apr 71 Response to <a href="./rfc111">RFC 111</a> (Pressure from |
| 7523 |
the Chairman) |
| 7524 |
|
| 7525 |
Discussion of RAND's role in testing other host implementations |
| 7526 |
and schedule dependences. |
| 7527 |
|
| 7528 |
129 Harslem Apr 71 A Request for Comments on Socket |
| 7529 |
Name Structure |
| 7530 |
|
| 7531 |
Comments on several suggested socket name structures. |
| 7532 |
|
| 7533 |
128 Postel Apr 71 Bytes |
| 7534 |
|
| 7535 |
Discussion of the Byte size parameter allowed by the 2nd level |
| 7536 |
protocol. |
| 7537 |
|
| 7538 |
127 Postel Apr 71 Comments on <a href="./rfc123">RFC 123</a> |
| 7539 |
|
| 7540 |
Continued interpretations of the exchange between NCP's which |
| 7541 |
would be necessary to carry out the Initial Connection Protocol of |
| 7542 |
<a href="./rfc123">RFC 123</a>. |
| 7543 |
|
| 7544 |
126 McConnell Apr 71 Ames Graphics Facilities at Ames |
| 7545 |
Research Center |
| 7546 |
|
| 7547 |
Discusses the graphical facilities at Ames for the IBM 360/67 TSS. |
| 7548 |
|
| 7549 |
125 McConnell Apr 71 Response to <a href="./rfc86">RFC 86</a>, Proposal for |
| 7550 |
Network Standard Format for a |
| 7551 |
Graphics Data Stream |
| 7552 |
|
| 7553 |
Improves and updates <a href="./rfc86">RFC 86</a>. |
| 7554 |
|
| 7555 |
|
| 7556 |
|
| 7557 |
|
| 7558 |
|
| 7559 |
<span class="grey">Reynolds & Postel [Page 135]</span></pre> |
| 7560 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-136" ></span> |
| 7561 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 7562 |
|
| 7563 |
|
| 7564 |
124 Melvin Apr 71 Typographical Error in <a href="./rfc107">RFC 107</a> |
| 7565 |
|
| 7566 |
Points out an error in <a href="./rfc107">RFC 107</a>. |
| 7567 |
|
| 7568 |
123 Crocker Apr 71 A Proferred Official ICP |
| 7569 |
|
| 7570 |
Description of a family of ICPs (Initial Connection Protocol) |
| 7571 |
suitable for establishing one pair of connections (one in each |
| 7572 |
direction) between any user process and any server process, and |
| 7573 |
proposes a particular subset of this family as the standard ICP |
| 7574 |
for connecting user processes to loggers on systems which accept |
| 7575 |
teletype-like devices. |
| 7576 |
|
| 7577 |
122 White Apr 71 Network Specifications for UCSB's |
| 7578 |
Simple-Minded File System |
| 7579 |
|
| 7580 |
UCSB's Simple Minded File System (SMFS) which will provide file |
| 7581 |
storage for network users. This document provides programmers |
| 7582 |
with the information necessary to communicate with SMFS. |
| 7583 |
|
| 7584 |
121 Krilanovich Apr 71 Network On-Line Operators |
| 7585 |
|
| 7586 |
Descriptions of operators that have been implemented within UCSB's |
| 7587 |
On-Line System and make the network (via NCP) accessible to |
| 7588 |
On-Line system users. |
| 7589 |
|
| 7590 |
120 Krilanovich Apr 71 Network PL1 Subprograms |
| 7591 |
|
| 7592 |
Descriptions of subroutines that have been implemented at UCSB and |
| 7593 |
make the network (via NCP) accessible to PL1 programs executing in |
| 7594 |
the IBM 360/75. |
| 7595 |
|
| 7596 |
119 Krilanovich Apr 71 Network FORTRAN Subprograms |
| 7597 |
|
| 7598 |
Descriptions of a set of assembly-language subprograms, their |
| 7599 |
functions and calling sequences. |
| 7600 |
|
| 7601 |
118 Watson Apr 71 Information Required for Each |
| 7602 |
Service Available to the Network |
| 7603 |
|
| 7604 |
Cites two classes of information which each site needs to provide |
| 7605 |
for every service or process it makes available over the ARPA |
| 7606 |
network. |
| 7607 |
|
| 7608 |
117 Wong Apr 71 Some Comments on the Official |
| 7609 |
Protocol |
| 7610 |
|
| 7611 |
Cites weaknesses in <a href="./rfc107">RFC 107</a>, and provides suggestions for |
| 7612 |
correction and handling. |
| 7613 |
|
| 7614 |
|
| 7615 |
<span class="grey">Reynolds & Postel [Page 136]</span></pre> |
| 7616 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-137" ></span> |
| 7617 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 7618 |
|
| 7619 |
|
| 7620 |
116 Crocker Apr 71 Structure of the May NWG Meeting |
| 7621 |
|
| 7622 |
Proposed meeting agenda centering around discussions of advertised |
| 7623 |
topics, with published status reports and position papers. |
| 7624 |
|
| 7625 |
115 Watson Apr 71 Some Network Information Center |
| 7626 |
Policies on Handling Documents |
| 7627 |
|
| 7628 |
Discusses current document policies between the Network |
| 7629 |
Information Center and sites on the network. |
| 7630 |
|
| 7631 |
114 Bhushan Apr 71 A File Transfer Protocol |
| 7632 |
|
| 7633 |
Proposed file transfer mechanisms that have been developed for |
| 7634 |
immediate implementation on hosts at MIT. |
| 7635 |
|
| 7636 |
113 Harlsem Apr 71 Network Activity Report: UCSB and |
| 7637 |
RAND |
| 7638 |
|
| 7639 |
Report on the network use and validity between UCSB's RJE and RJOR |
| 7640 |
systems and RAND. |
| 7641 |
|
| 7642 |
112 O'Sullivan Apr 71 User/Server Site Protocol Network |
| 7643 |
HOST Questionnaire |
| 7644 |
|
| 7645 |
A summary of the responses to the referenced questionnaire. |
| 7646 |
|
| 7647 |
111 Crocker Mar 71 Pressure from the Chairman |
| 7648 |
|
| 7649 |
Proposed scheduling for the implementation of NCPs and Telnets. |
| 7650 |
|
| 7651 |
110 Winett Mar 71 Conventions for Using an IBM 2741 |
| 7652 |
Terminal as a User Console for |
| 7653 |
Access to Network Server Hosts |
| 7654 |
|
| 7655 |
Telnet implementation and the 2741. |
| 7656 |
|
| 7657 |
109 Winett Mar 71 Level III Server Protocol for the |
| 7658 |
Lincoln Laboratory 360/67 Host |
| 7659 |
|
| 7660 |
Telnet implementation and the 360/67. |
| 7661 |
|
| 7662 |
108 Watson Mar 71 Attendance List at the Urbana NWG |
| 7663 |
Meeting, 17-19 February 1971 |
| 7664 |
|
| 7665 |
Lists attendees at the NWG meeting held February 1971. |
| 7666 |
|
| 7667 |
|
| 7668 |
|
| 7669 |
|
| 7670 |
|
| 7671 |
<span class="grey">Reynolds & Postel [Page 137]</span></pre> |
| 7672 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-138" ></span> |
| 7673 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 7674 |
|
| 7675 |
|
| 7676 |
107 Bressler Mar 71 Output of the Host-Host Protocol |
| 7677 |
Glitch Cleaning Committee |
| 7678 |
|
| 7679 |
The second meeting of the Host-Host Protocol Glitch Cleaning |
| 7680 |
committee. |
| 7681 |
|
| 7682 |
106 O'Sullivan Mar 71 USER/SERVER Site Protocol Network |
| 7683 |
Host Questionnaire |
| 7684 |
|
| 7685 |
An attempt to gather information for creating the Telnet Protocol. |
| 7686 |
|
| 7687 |
105 White Mar 71 Network Specification for Remote Job |
| 7688 |
Entry and Remote Job Output |
| 7689 |
Retrieval at UCSB |
| 7690 |
|
| 7691 |
Describes the remote job entry service at UCSB. |
| 7692 |
|
| 7693 |
104 Postel Feb 71 Link 191 |
| 7694 |
|
| 7695 |
General agreement to reserve a link for use in measurements. |
| 7696 |
Therefore, Link 191 will be assigned for measurement use. |
| 7697 |
|
| 7698 |
103 Kalin Feb 71 Implementation of Interrupt Keys |
| 7699 |
|
| 7700 |
This paper discusses the problems and solutions that are simple to |
| 7701 |
implement in the current protocol specifications that contain |
| 7702 |
serious logical errors in the interrupt functions. |
| 7703 |
|
| 7704 |
102 Crocker Feb 71 Output of the HOST/HOST Protocol |
| 7705 |
Glitch Cleaning Committee |
| 7706 |
|
| 7707 |
Numerous topics were discussed. |
| 7708 |
|
| 7709 |
101 Watson Feb 71 Notes on the Network Working Group |
| 7710 |
Meeting |
| 7711 |
|
| 7712 |
Transcript of the Network Working Group Meeting, February 1970. |
| 7713 |
|
| 7714 |
100 Karp Feb 71 Categorization and Guide to NWG/RFCs |
| 7715 |
|
| 7716 |
Categorizes, identifies, and summarizes RFCS 1-100. |
| 7717 |
|
| 7718 |
099 Karp Feb 71 Network Meeting |
| 7719 |
|
| 7720 |
Announcement of the next meeting of the Network Working Group for |
| 7721 |
20 May 1970. |
| 7722 |
|
| 7723 |
|
| 7724 |
|
| 7725 |
|
| 7726 |
|
| 7727 |
<span class="grey">Reynolds & Postel [Page 138]</span></pre> |
| 7728 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-139" ></span> |
| 7729 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 7730 |
|
| 7731 |
|
| 7732 |
098 Meyer Feb 71 Logger Protocol Proposal |
| 7733 |
|
| 7734 |
This "network logger protocol" is intended to specify how the |
| 7735 |
existing logger of a network host is to interface to the network |
| 7736 |
so as to permit a login from a console attached to another host. |
| 7737 |
|
| 7738 |
097 Melvin Feb 71 A First Cut at a Proposed Telnet |
| 7739 |
Protocol |
| 7740 |
|
| 7741 |
This document was motivated by the need to set specifications for |
| 7742 |
a protocol which would allow on-line access to the Network |
| 7743 |
Information Center (NIC). |
| 7744 |
|
| 7745 |
096 Watson Feb 71 An Interactive Network Experiment to |
| 7746 |
Study Modes of Access to the Network |
| 7747 |
Information Center |
| 7748 |
|
| 7749 |
Outlines the framework for a simple interactive experiment to |
| 7750 |
study modes of access to the Network Information Center (NIC). |
| 7751 |
|
| 7752 |
095 Crocker Feb 71 Distribution of NWG/RFC's Through |
| 7753 |
the NIC |
| 7754 |
|
| 7755 |
Standards for establishing lines of communication of all of the |
| 7756 |
sites with the Network Information Center, in regards to |
| 7757 |
distribution of RFC's. |
| 7758 |
|
| 7759 |
094 Harslem Feb 71 Some Thoughts on Network Graphics |
| 7760 |
|
| 7761 |
Discussion of the initial reaction to <a href="./rfc86">RFC 86</a>, whose purpose was to |
| 7762 |
provide a basis for discussion and development of Network |
| 7763 |
graphics. |
| 7764 |
|
| 7765 |
093 McKenzie Jan 71 Initial Connection Protocol |
| 7766 |
|
| 7767 |
A review of the Initial Connection Protocol (ICP), first described |
| 7768 |
in <a href="./rfc66">RFC 66</a> and restated in <a href="./rfc80">RFC 80</a>. |
| 7769 |
|
| 7770 |
092 Never Issued. |
| 7771 |
|
| 7772 |
091 Mealy Dec 70 A Proposed User-User Protocol |
| 7773 |
|
| 7774 |
Discussion of UCLA's Campus Computing Network of services and |
| 7775 |
implementation priorities. |
| 7776 |
|
| 7777 |
|
| 7778 |
|
| 7779 |
|
| 7780 |
|
| 7781 |
|
| 7782 |
|
| 7783 |
<span class="grey">Reynolds & Postel [Page 139]</span></pre> |
| 7784 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-140" ></span> |
| 7785 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 7786 |
|
| 7787 |
|
| 7788 |
090 Braden Jan 71 CCN as a Network Service Center |
| 7789 |
|
| 7790 |
Discussion of UCLA's Campus Computing Network of services and |
| 7791 |
implementation priorities. |
| 7792 |
|
| 7793 |
089 Metcalfe Jan 71 Some Historic Moments in Networking |
| 7794 |
|
| 7795 |
Noteworthy achievements for the MIT-Project MAC Dynamic |
| 7796 |
Modeling/Computer Graphics PDP-6/10 System, while awaiting the |
| 7797 |
completion of an interim network control program. |
| 7798 |
|
| 7799 |
088 Braden Jan 71 NETRJS - A Third Level Protocol for |
| 7800 |
Remote Job Entry |
| 7801 |
|
| 7802 |
Description of NETRJS, which is the name for a message protocol |
| 7803 |
and a set of control conventions which will allow users at remote |
| 7804 |
Hosts to access the RJS remote batch subsystem of UCLA/CCN. |
| 7805 |
|
| 7806 |
087 Vezza Jan 71 Topic for Discussion at the Next |
| 7807 |
Network Working Group Meeting |
| 7808 |
|
| 7809 |
Suggests Network Working Group discussion on topics germane to |
| 7810 |
network graphics. |
| 7811 |
|
| 7812 |
086 Crocker Jan 71 Proposal for a Network Standard |
| 7813 |
Format for a Data Stream to Control |
| 7814 |
Graphics Display |
| 7815 |
|
| 7816 |
Proposes specifying the form of an output stream for the case that |
| 7817 |
the output portion of the console (which is attached to a computer |
| 7818 |
at the user's site) is a typical refresh display with point, |
| 7819 |
vector, and character drawing capability. |
| 7820 |
|
| 7821 |
085 Crocker Dec 70 Network Working Group Meeting |
| 7822 |
|
| 7823 |
Announcement of regularly scheduled Network Working Group Meetings |
| 7824 |
every three months. |
| 7825 |
|
| 7826 |
084 North Dec 70 List of NWG/RFCs 1-80 |
| 7827 |
|
| 7828 |
Lists RFCs 1-80. |
| 7829 |
|
| 7830 |
083 Anderson Dec 70 Language-Machine for Data |
| 7831 |
Reconfiguration |
| 7832 |
|
| 7833 |
Describes a syntax-driven interpreter that operates on a grammar |
| 7834 |
which is an orderd set of replacement rules for the Form Machine. |
| 7835 |
|
| 7836 |
|
| 7837 |
|
| 7838 |
|
| 7839 |
<span class="grey">Reynolds & Postel [Page 140]</span></pre> |
| 7840 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-141" ></span> |
| 7841 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 7842 |
|
| 7843 |
|
| 7844 |
082 Meyer Dec 70 Network Meeting Notes |
| 7845 |
|
| 7846 |
A transcribed summary of the Fall 1970 network meeting notes. |
| 7847 |
|
| 7848 |
081 Bouknight Dec 70 Request for Reference Information |
| 7849 |
|
| 7850 |
Request for documents in the subject areas of data communications |
| 7851 |
and communications theory. |
| 7852 |
|
| 7853 |
080 Harslem Dec 70 Protocol and Data Formats |
| 7854 |
|
| 7855 |
Proposes general solutions concerning Initial Connection |
| 7856 |
Protocols, Pre-specificed Data Formats, and Adaptable Mechanisms. |
| 7857 |
|
| 7858 |
079 Meyer Nov 70 Logger Protocol Error |
| 7859 |
|
| 7860 |
078 Harslem Nov 70 NCP Status Report: UCSB/Rand |
| 7861 |
|
| 7862 |
Conducted an excercise between UCSB console to/from RAND console |
| 7863 |
validation of the respective NCPs. |
| 7864 |
|
| 7865 |
077 Postel Nov 70 Network Meeting Report |
| 7866 |
|
| 7867 |
Report on three Network Working Group meetings held during |
| 7868 |
November 16, 17, and 18. |
| 7869 |
|
| 7870 |
076 Bouknight Oct 70 Connection-by-Name: User-Oriented |
| 7871 |
Protocol |
| 7872 |
|
| 7873 |
Suggests a user level interface to network protocol where all user |
| 7874 |
protocol is handled symbolically with system procedures making the |
| 7875 |
translation into host-to-host protocol. Proposes general |
| 7876 |
solutions. |
| 7877 |
|
| 7878 |
075 Crocker Oct 70 Network Meeting |
| 7879 |
|
| 7880 |
Announcement of the next scheduled meeting of the Network Working |
| 7881 |
Group for 16 Nov 70. |
| 7882 |
|
| 7883 |
074 White Oct 70 Specifications for Network Use of |
| 7884 |
the UCSB On-Line System |
| 7885 |
|
| 7886 |
Announcement of UCSB's On-Line System (OLS) availability to ARPA |
| 7887 |
Network users. |
| 7888 |
|
| 7889 |
|
| 7890 |
|
| 7891 |
|
| 7892 |
|
| 7893 |
|
| 7894 |
|
| 7895 |
<span class="grey">Reynolds & Postel [Page 141]</span></pre> |
| 7896 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-142" ></span> |
| 7897 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 7898 |
|
| 7899 |
|
| 7900 |
073 Crocker Sep 70 Response to <a href="./rfc67">RFC 67</a> |
| 7901 |
|
| 7902 |
General agreement with proposed policy. |
| 7903 |
|
| 7904 |
072 Bressler Sep 70 Proposed Moratorium on Changes to |
| 7905 |
Network Protocol |
| 7906 |
|
| 7907 |
Cites critical changes that could occur in hardware/software |
| 7908 |
development efforts and advanced debugging if changes in the |
| 7909 |
Network Protocol aren't kept in check. |
| 7910 |
|
| 7911 |
071 Schipper Sep 70 Reallocation in Case of Input Error |
| 7912 |
|
| 7913 |
Discussion of how to resynchronize flow control using a proposed |
| 7914 |
protocol for the CCN-Host at UCLA. |
| 7915 |
|
| 7916 |
070 Crocker Oct 70 A Note on Padding |
| 7917 |
|
| 7918 |
Discussion of padding on a message. |
| 7919 |
|
| 7920 |
069 Bhushan Sep 70 Distribution List Change for MIT. |
| 7921 |
|
| 7922 |
Announcement of name change. |
| 7923 |
|
| 7924 |
068 Elie Aug 70 Comments on Memory Allocation |
| 7925 |
Control Commands (CEASE, ALL, GVB, |
| 7926 |
RET) and RFNM |
| 7927 |
|
| 7928 |
Provides a scheme for buffer allocation. |
| 7929 |
|
| 7930 |
067 Crowther Undated Proposed Change to Host/IMP Spec to |
| 7931 |
Eliminate Marking |
| 7932 |
|
| 7933 |
Proposed change to eliminate marking, per Walden's comments. |
| 7934 |
|
| 7935 |
066 Crocker Aug 70 3rd Level Ideas and Other Noise |
| 7936 |
|
| 7937 |
Meeting notes from 12 Aug 70 between Crocker and representatives |
| 7938 |
from BBN and MIT regarding the third level protocol. |
| 7939 |
|
| 7940 |
065 Walden Aug 70 Comments on Host-Host Protocol |
| 7941 |
Document Number 1 (Crocker, |
| 7942 |
3 August 70) |
| 7943 |
|
| 7944 |
Critique and suggestions for improvement of the Host-Host Protocol |
| 7945 |
document. |
| 7946 |
|
| 7947 |
|
| 7948 |
|
| 7949 |
|
| 7950 |
|
| 7951 |
<span class="grey">Reynolds & Postel [Page 142]</span></pre> |
| 7952 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-143" ></span> |
| 7953 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 7954 |
|
| 7955 |
|
| 7956 |
064 Elie Undated Getting Rid of Marking |
| 7957 |
|
| 7958 |
Suggests simple modifications and solutions to the IMP-HOST |
| 7959 |
interface which would be a better solution than marking. |
| 7960 |
|
| 7961 |
063 Cerf Jul 70 Belated Network Meeting Report |
| 7962 |
|
| 7963 |
Network meeting report of the Network Working Group from 8 May 70. |
| 7964 |
|
| 7965 |
062 Walden Aug 70 A System for Interprocess |
| 7966 |
Communication in a Resource Sharing |
| 7967 |
Computer Network |
| 7968 |
|
| 7969 |
Supercedes <a href="./rfc61">RFC 61</a>. |
| 7970 |
|
| 7971 |
061 Walden Jul 70 A Note on Interprocess Communication |
| 7972 |
in a Resource Sharing Computer |
| 7973 |
Network |
| 7974 |
|
| 7975 |
A draft request for comments of a resource sharing study that may |
| 7976 |
be of general interest to network participants. |
| 7977 |
|
| 7978 |
060 Kalin Jul 70 A Simplified NCP Protocol |
| 7979 |
|
| 7980 |
Definition of a new NCP Protocol that is simple enough to be |
| 7981 |
implemented on a very small computer, yet can be extended for |
| 7982 |
efficient operation on large timesharing machines. |
| 7983 |
|
| 7984 |
059 Meyer Jun 70 Flow Control-Fixed Versus Demand |
| 7985 |
Allocation |
| 7986 |
|
| 7987 |
Discussion of the advantages and disadvantages of the method of |
| 7988 |
flow control as described in <a href="./rfc54">RFC 54</a>. |
| 7989 |
|
| 7990 |
058 Skinner Jun 70 Logical Message Synchronization |
| 7991 |
|
| 7992 |
A discussion on a question raised at the last network meeting |
| 7993 |
regarding the question of logical and physical message |
| 7994 |
distinctions. |
| 7995 |
|
| 7996 |
057 Kraley Jun 70 Thoughts and Reflections on <a href="./rfc54">RFC 54</a> |
| 7997 |
|
| 7998 |
056 Belove Jun 70 Third Level Protocol |
| 7999 |
|
| 8000 |
All explanations in this RFC are meant to describe functional |
| 8001 |
characteristics rather than design. |
| 8002 |
|
| 8003 |
|
| 8004 |
|
| 8005 |
|
| 8006 |
|
| 8007 |
<span class="grey">Reynolds & Postel [Page 143]</span></pre> |
| 8008 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-144" ></span> |
| 8009 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 8010 |
|
| 8011 |
|
| 8012 |
055 Newkirk Jun 70 A Prototypical Implementation of the |
| 8013 |
NCP |
| 8014 |
|
| 8015 |
A prototypical specification in a prose format of what the NCP |
| 8016 |
could look like. |
| 8017 |
|
| 8018 |
054 Crocker Jun 70 An Official Protocol Proffering |
| 8019 |
|
| 8020 |
Submission of the Official Protocol for comments and suggestions. |
| 8021 |
|
| 8022 |
053 Crocker Jun 70 An Official Protocol Mechanism |
| 8023 |
|
| 8024 |
Group discussion on rules for establishing and modifying an |
| 8025 |
official Host-Host protocol. |
| 8026 |
|
| 8027 |
052 Postel Jul 70 Updated Distribution List |
| 8028 |
|
| 8029 |
Mailing list for distributing the RFCs. |
| 8030 |
|
| 8031 |
051 Elie May 70 Proposal for a Network Interchange |
| 8032 |
Language |
| 8033 |
|
| 8034 |
A proposal to specify a high level programming language for |
| 8035 |
computer networks, specifically the ARPA network. |
| 8036 |
|
| 8037 |
050 Harslem Apr 70 Comments on the Meyer Proposal |
| 8038 |
|
| 8039 |
General acceptance on <a href="./rfc46">RFC 46</a>, plus comments on the seven issues |
| 8040 |
raised in <a href="./rfc47">RFC 47</a>. |
| 8041 |
|
| 8042 |
049 Meyer Apr 70 Conversations with Steve Crocker |
| 8043 |
(UCLA) |
| 8044 |
|
| 8045 |
Discussion of telephone conversations relating to the Network |
| 8046 |
Protocol, specifically regarding Meyer's proposal in <a href="./rfc46">RFC 46</a>. |
| 8047 |
|
| 8048 |
048 Postel Apr 70 A Possible Protocol Plateau |
| 8049 |
|
| 8050 |
Reporting activities since the Network meeting of 17 March 1970. |
| 8051 |
|
| 8052 |
047 Postel Apr 70 BBN's Comments on <a href="./rfc33">RFC 33</a> |
| 8053 |
|
| 8054 |
Comments from BBN regarding <a href="./rfc33">RFC 33</a> (New HOST-HOST Protocol). |
| 8055 |
|
| 8056 |
046 Meyer Apr 70 ARPA Network Protocol Notes |
| 8057 |
|
| 8058 |
Comments and suggestions from the NWG at Project MAC, based upon |
| 8059 |
the protocol outlined in RFCs 33,36. |
| 8060 |
|
| 8061 |
|
| 8062 |
|
| 8063 |
<span class="grey">Reynolds & Postel [Page 144]</span></pre> |
| 8064 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-145" ></span> |
| 8065 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 8066 |
|
| 8067 |
|
| 8068 |
045 Postel Apr 70 New Protocol is Coming |
| 8069 |
|
| 8070 |
Announcement of a new version of the Network Protocol. |
| 8071 |
|
| 8072 |
044 Shoshani Apr 70 Comments on RFCs 33,36 |
| 8073 |
|
| 8074 |
General discussion and suggestions for refinements to the |
| 8075 |
HOST-HOST Protocol. |
| 8076 |
|
| 8077 |
043 Nemeth Mar 70 Proposed Meeting |
| 8078 |
|
| 8079 |
An announcement of a meeting to discuss the Local Interaction |
| 8080 |
Language system. |
| 8081 |
|
| 8082 |
042 Ancona Mar 70 Message Data Types |
| 8083 |
|
| 8084 |
A proposal that the first eight bits of a normal message be |
| 8085 |
reserved for a message data type. |
| 8086 |
|
| 8087 |
041 Melvin Mar 70 IMP/IMP Teletype Communication |
| 8088 |
|
| 8089 |
Comments that transmitting IMP sites should use 24 hour time and |
| 8090 |
include the time zone designation. |
| 8091 |
|
| 8092 |
040 Harslem Mar 70 More Comments on the Forthcoming |
| 8093 |
Protocol |
| 8094 |
|
| 8095 |
Further elaborations on the errors, queries, and Host status that |
| 8096 |
were mentioned in <a href="./rfc39">RFC 39</a>. |
| 8097 |
|
| 8098 |
039 Harslem Mar 70 Comments on Network Protocol |
| 8099 |
(<a href="./rfc36">RFC 36</a>) |
| 8100 |
|
| 8101 |
More suggestions to be considered as additions to <a href="./rfc36">RFC 36</a> - Network |
| 8102 |
Protocol. |
| 8103 |
|
| 8104 |
038 Wolfe Mar 70 Comments on Network Protocol |
| 8105 |
(<a href="./rfc36">RFC 36</a>) |
| 8106 |
|
| 8107 |
Continued discussion on the proposed Network Protocol. |
| 8108 |
|
| 8109 |
037 Crocker Mar 70 Network Meeting Epilogues, etc. |
| 8110 |
|
| 8111 |
Network Meeting notes from 17 March 1970. |
| 8112 |
|
| 8113 |
|
| 8114 |
|
| 8115 |
|
| 8116 |
|
| 8117 |
|
| 8118 |
|
| 8119 |
<span class="grey">Reynolds & Postel [Page 145]</span></pre> |
| 8120 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-146" ></span> |
| 8121 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 8122 |
|
| 8123 |
|
| 8124 |
036 Crocker Mar 70 Protocol Notes |
| 8125 |
|
| 8126 |
A three part overview of the Network Protocol. |
| 8127 |
|
| 8128 |
035 Crocker Mar 70 Network Meeting |
| 8129 |
|
| 8130 |
Announcement of a network meeting: date, time, place, and proposed |
| 8131 |
agenda. |
| 8132 |
|
| 8133 |
034 English Feb 70 Some Brief Preliminary Notes on the |
| 8134 |
ARC Clock |
| 8135 |
|
| 8136 |
Describes the ARC Clock system. |
| 8137 |
|
| 8138 |
033 Crocker Feb 70 New Host-Host Protocol |
| 8139 |
|
| 8140 |
Revises <a href="./rfc11">RFC 11</a>, and indicates numerous changes in the old |
| 8141 |
protocol. |
| 8142 |
|
| 8143 |
032 Cole Feb 70 Some Thoughts on SRI's Proposed Real |
| 8144 |
Time Clock |
| 8145 |
|
| 8146 |
References and comments on RFCs 28,29. |
| 8147 |
|
| 8148 |
031 Bobrow Feb 68 Binary Message Forms in Computer |
| 8149 |
Networks |
| 8150 |
|
| 8151 |
Suggest alternative approaches and methods for describing |
| 8152 |
messages. |
| 8153 |
|
| 8154 |
030 Crocker Feb 70 Documentation Conventions |
| 8155 |
|
| 8156 |
Revises the definition of style, content, form, and distribution |
| 8157 |
of the Network Working Group's notes. Replaces RFCs 10,16,24,27. |
| 8158 |
|
| 8159 |
029 Kahn Jan 70 Note in Response to Bill English's |
| 8160 |
Request for Comments |
| 8161 |
|
| 8162 |
Comments in response to English's question which was raised in |
| 8163 |
<a href="./rfc28">RFC 28</a>. |
| 8164 |
|
| 8165 |
028 English Jan 70 Time Standards |
| 8166 |
|
| 8167 |
Request for comments relative to Network time standards. |
| 8168 |
|
| 8169 |
|
| 8170 |
|
| 8171 |
|
| 8172 |
|
| 8173 |
|
| 8174 |
|
| 8175 |
<span class="grey">Reynolds & Postel [Page 146]</span></pre> |
| 8176 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-147" ></span> |
| 8177 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 8178 |
|
| 8179 |
|
| 8180 |
027 Crocker Dec 69 Documentation Conventions |
| 8181 |
|
| 8182 |
Revises the definition of style, content, form, and distribution |
| 8183 |
of the Network Working Group's notes. Replaces RFCs 10,16,24. |
| 8184 |
|
| 8185 |
026 Never Issued. |
| 8186 |
|
| 8187 |
025 Crocker Oct 69 No High Link Numbers |
| 8188 |
|
| 8189 |
Suggests that no link number over 63 be used. |
| 8190 |
|
| 8191 |
024 Crocker Nov 69 Documentation Conventions |
| 8192 |
|
| 8193 |
Revises the definition of style, content, form, and distribution |
| 8194 |
of the Network Working Group's notes. Replaces RFCs 10,16. |
| 8195 |
|
| 8196 |
023 Gregg Oct 69 Transmission of Multiple Control |
| 8197 |
Messages |
| 8198 |
|
| 8199 |
Discusses how a network program at a site should be prepared to |
| 8200 |
send or receive more than one control message in a single control |
| 8201 |
communication. |
| 8202 |
|
| 8203 |
022 Cerf Oct 69 Host-Host Control Message Formats |
| 8204 |
|
| 8205 |
Reports on a new control message format which does not use the |
| 8206 |
7-bit ASCII character mode of transmission. |
| 8207 |
|
| 8208 |
021 Cerf Oct 69 Report on Network Meeting |
| 8209 |
|
| 8210 |
Attendance list and topics discussed. |
| 8211 |
|
| 8212 |
020 Cerf Oct 69 ASCII Format for Network Interchange |
| 8213 |
|
| 8214 |
Discusses the use of standard 7-bit ASCII embedded in an 8-bit |
| 8215 |
byte whose high order bit is always 1. |
| 8216 |
|
| 8217 |
019 Kreznar Oct 69 Two Protocol Suggestions to Reduce |
| 8218 |
Congestion at Swap-Bound Nodes |
| 8219 |
|
| 8220 |
Suggests alternatives in reducing congestion at swap-bound nodes. |
| 8221 |
|
| 8222 |
018 Cerf Sep 69 Comments Re: Host-Host control link |
| 8223 |
|
| 8224 |
Suggestions regarding the Host-Host control link. |
| 8225 |
|
| 8226 |
|
| 8227 |
|
| 8228 |
|
| 8229 |
|
| 8230 |
|
| 8231 |
<span class="grey">Reynolds & Postel [Page 147]</span></pre> |
| 8232 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-148" ></span> |
| 8233 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 8234 |
|
| 8235 |
|
| 8236 |
017a Kahn Aug 69 Some Comments Re: HOST-IMP Protocol |
| 8237 |
|
| 8238 |
Comments in response to Kreznar's questions which were raised in |
| 8239 |
<a href="./rfc17">RFC 17</a>. |
| 8240 |
|
| 8241 |
017 Kreznar Aug 69 Some Questions Re: HOST-IMP Protocol |
| 8242 |
|
| 8243 |
Queries and opinions regarding the HOST-IMP Protocol. |
| 8244 |
|
| 8245 |
016 Crocker Aug 69 M.I.T. |
| 8246 |
|
| 8247 |
Announcement that MIT is now to receive all Network Working Group |
| 8248 |
memos. |
| 8249 |
|
| 8250 |
015 Carr Sep 69 Network Subsystem for Time Sharing |
| 8251 |
Hosts |
| 8252 |
|
| 8253 |
Proposes a subsystem called "Telnet", which would be a shell |
| 8254 |
program around the network system primitives, allowing a teletype |
| 8255 |
or similar terminal at a remote host to function as a teletype at |
| 8256 |
the serving host. |
| 8257 |
|
| 8258 |
014 Never Issued. |
| 8259 |
|
| 8260 |
013 Cerf Aug 69 Referring to <a href="./rfc11">RFC 11</a> |
| 8261 |
|
| 8262 |
Proposes a zero text length EOF (End-Of-File) message. |
| 8263 |
|
| 8264 |
012 Wingfield Aug 69 IMP-HOST Interface Flow Diagrams |
| 8265 |
|
| 8266 |
Flow diagrams that indicate the logical sequence of hardware |
| 8267 |
operations which occur within the IMP-HOST interface. |
| 8268 |
|
| 8269 |
011 Deloche Aug 69 Implementation of the Host-Host |
| 8270 |
Software Procedures in GORDO |
| 8271 |
|
| 8272 |
Discussion of Host-Host Procedures and GORDO as a time-sharing |
| 8273 |
system that was implemented on a SDS Sigma 7. |
| 8274 |
|
| 8275 |
010 Crocker Jul 69 Documentation Conventions |
| 8276 |
|
| 8277 |
Revises the definition of style, content, form, and distribution |
| 8278 |
of the Network Working Group's notes. Replaces <a href="./rfc3">RFC 3</a>. |
| 8279 |
|
| 8280 |
009 Deloche May 69 Host Software |
| 8281 |
|
| 8282 |
Discusses the Host-Host Protocol, Network Service Calls, and Data |
| 8283 |
Structures. |
| 8284 |
|
| 8285 |
|
| 8286 |
|
| 8287 |
<span class="grey">Reynolds & Postel [Page 148]</span></pre> |
| 8288 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-149" ></span> |
| 8289 |
<span class="grey"><a href="./rfc1000">RFC 1000</a> - Request for Comments Reference Guide August 1987</span> |
| 8290 |
|
| 8291 |
|
| 8292 |
008 Deloche May 69 ARPA Network Functional |
| 8293 |
Specifications |
| 8294 |
|
| 8295 |
Discusses transmission features, functional software |
| 8296 |
specifications, and the Link establishment procedure. |
| 8297 |
|
| 8298 |
007 Deloche May 69 HOST-IMP Interface |
| 8299 |
|
| 8300 |
Discusses Host-IMP interface issues. |
| 8301 |
|
| 8302 |
006 Crocker Apr 69 Conversation with Bob Kahn |
| 8303 |
|
| 8304 |
Conversations regarding code conversion in the IMP's, IMP-HOST |
| 8305 |
communication, and HOST software. |
| 8306 |
|
| 8307 |
005 Rulifson Jun 69 DEL |
| 8308 |
|
| 8309 |
Details the machine independent language DEL (Decode-Encode |
| 8310 |
Language). |
| 8311 |
|
| 8312 |
004 Shapiro Mar 69 Network Timetable |
| 8313 |
|
| 8314 |
Discusses installation, configuration, network checkout, and test |
| 8315 |
messages run between SRI and UCLA. |
| 8316 |
|
| 8317 |
003 Crocker Apr 69 Documentation Conventions |
| 8318 |
|
| 8319 |
Establishes a definition of style, content, form, and distribution |
| 8320 |
of the Network Working Group's notes (Obsoleted by <a href="./rfc10">RFC 10</a>). |
| 8321 |
|
| 8322 |
002 Duvall Apr 69 Links |
| 8323 |
|
| 8324 |
Discusses various types of Links, including Control, Primary, and |
| 8325 |
Auxilliary Links. |
| 8326 |
|
| 8327 |
001 Crocker Apr 69 Host Software |
| 8328 |
|
| 8329 |
Discusses the Host software and initial experiments on the ARPA |
| 8330 |
Network. |
| 8331 |
|
| 8332 |
|
| 8333 |
|
| 8334 |
|
| 8335 |
|
| 8336 |
|
| 8337 |
|
| 8338 |
|
| 8339 |
|
| 8340 |
|
| 8341 |
|
| 8342 |
|
| 8343 |
Reynolds & Postel [Page 149] |
| 8344 |
</pre> |