RFC 1000
Request For Comments reference guide
RFC 1000: THE REQUEST FOR COMMENTS REFERENCE GUIDE โจ
okay bestie, let's start with the title block ๐ This is RFC 1000, published by the Network Working Group in August 1987. The authors are J. Reynolds and J. Postel, both from ISI ๐ It obsoletes RFCs 084, 100, 160, 170, 200, 598, 699, 800, 899, and 999. The title is THE REQUEST FOR COMMENTS REFERENCE GUIDE ๐
Status of This Memo ๐ฆ
This RFC is a reference guide for the Internet community that summarizes all the Request for Comments issued between April 1969 and March 1987. It also sorts the RFCs by topic ๐ธ
Introduction ๐
This RFC Reference Guide is meant to give a historical account. It does this by sorting and summarizing the Request for Comments numbers 1 through 999, which were issued between 1969 and 1987 ๐ง These documents have been cross-referenced so you can see which RFCs are current, obsolete, or revised. Distribution of this memo is unlimited ๐ซถ
The Origins of RFCs - by Stephen D. Crocker ๐
okay so this part is written by Stephen D. Crocker himself, and it's the origin story of the whole RFC thing ๐ญ The DDN community now has hundreds of nodes and thousands of users, but once upon a time it was just a gleam in Larry Roberts' eye โจ A lot of the development went according to a grand plan, but honestly the design of the protocols and the creation of the RFCs was mostly accidental ๐
The procurement of the ARPANET kicked off in the summer of 1968. Remember Vietnam, flower children, etc? ๐ผ There had been earlier experiments at various ARPA sites to link computer systems together, but this was the first version to explore packet-switching on a grand scale. ("ARPA" didn't become "DARPA" until 1972.) Unlike most ARPA/IPTO procurements of the day, this one was competitive ๐ The contract called for four IMPs to be delivered to UCLA, SRI, UCSB, and The University of Utah. These sites ran a Sigma 7 with the SEX operating system, an SDS 940 with the Genie operating system, an IBM 360/75 with OS/MVT (or perhaps OS/MFT), and a DEC PDP-10 with the Tenex operating system ๐ Options existed for additional nodes if the first experiments went well. BBN won the procurement in December 1968, but that gets ahead of this story ๐
These four sites were picked partly because they were already ARPA computer science research contractors. The exact usage of the ARPANET wasn't spelled out in advance, and the research community could be counted on to take some initiative ๐ฅ To get things moving, a meeting was called during the summer with reps from the selected sites, chaired by Elmer Shapiro from SRI. If memory serves, Jeff Rulifson came from SRI, Ron Stoughton from UCSB, Steve Carr from Utah, and Stephen came from UCLA. (Apologies to anyone left out, since records are inaccessible or lost at this point ๐) At this point they only knew the network was coming, but the precise details weren't known yet ๐ฆ
That first meeting was seminal โจ They had SO many questions: how IMPs and hosts would be connected, what hosts would say to each other, and what applications would be supported. Nobody had answers, but the prospects felt exciting ๐ They kept imagining all kinds of possibilities, like interactive graphics, cooperating processes, automatic database queries, and electronic mail, but nobody knew where to begin ๐ธ They weren't sure there was really room to think hard about these problems, and figured someone from the east would be along by and by to bring the word. But they did come to one conclusion: they ought to meet again ๐ Over the next several months they turned that idea into a series of exchange meetings at each of their sites, which set the most important precedent in protocol design ๐
The first few meetings were pretty tenuous ๐ฅบ There was no official charter. Most of them were grad students who expected a professional crew to show up eventually and take over the problems they were dealing with ๐ง Without a clear definition of what the host-IMP interface would look like, or even what functions the IMP would provide, they focused on exotic ideas. They imagined application-specific protocols with code downloaded to user sites, and they took a crack at designing a language to support this ๐ฅ The first version was called DEL, for "Decode-Encode Language," and a later version was called NIL, for "Network Interchange Language." When the IMP contract was finally let and BBN shared definite information on the host-IMP interface, all attention shifted to low-level matters, and the ambitious ideas for automatic downloading of code evaporated ๐ญ It was several years before ideas like remote procedure calls and typed objects came back ๐
In February of 1969 they met with BBN for the first time. Stephen says none of them were prepared for that meeting ๐ The BBN folks, led by Frank Heart, Bob Kahn, Severo Ornstein, and Will Crowther, found themselves talking to a crew of grad students they hadn't expected. And the students found themselves talking to people whose first concern was how to get bits to flow quickly and reliably, who hadn't, of course, spent any time thinking about the thirty or forty layers of protocol above the link level ๐ And while BBN didn't take over the protocol design process, they kept expecting an official protocol design team to announce itself ๐ซถ
A month later, after a particularly delightful meeting in Utah, it became clear they had better start writing down their discussions โจ They had collected some notes on the design of DEL and other matters, so they put them together into a set of notes. Stephen remembers having great fear that they'd offend whoever the official protocol designers were, and he spent a sleepless night composing humble words for their notes ๐ฅน The basic ground rules were that anyone could say anything and that nothing was official. To drive the point home, Stephen labeled the notes "Request for Comments." He never dreamed these notes would be distributed through the very medium they were discussing in them. Talk about Sorcerer's Apprentice! ๐งโโ๏ธ๐
Over the spring and summer of 1969 they wrestled with the detailed problems of protocol design ๐ช They had a vision of the huge potential for intercomputer communication, but designing usable protocols was a whole other beast. A custom hardware interface and custom intrusion into the operating system was going to be required for anything they designed, and they expected serious difficulty at each site ๐ธ They looked for existing abstractions to use. It would've been convenient to make the network look like a tape drive to each host, but they knew that wouldn't cut it ๐
It was clear they needed to support remote login for interactive use (later known as Telnet), and they needed to move files from machine to machine ๐ฆ They also knew they needed a more fundamental point of view for building a bigger array of protocols. Unfortunately, operating systems of that era tended to see themselves as the center of the universe, and symmetric cooperation didn't fit into the concepts available in those systems ๐ Time was also pressing: the first IMP was due at UCLA on September 1, 1969, and the rest were scheduled at monthly intervals โฐ
At UCLA they scrambled to build a host-IMP interface. SDS, the builder of the Sigma 7, wanted many months and many dollars to do the job ๐ธ Then Mike Wingfield, another grad student at UCLA, stepped in and offered to get the interface built in six weeks for a few thousand dollars. He had a gorgeous, fully instrumented interface working in five and a half weeks ๐ Stephen was in charge of the software, and they were naturally running a bit late. September 1 was Labor Day, so Stephen figured he had a couple of extra days to debug the software. He'd also heard BBN was having some timing troubles, so he had hope they'd miss the ship date ๐ค And he figured that first some Honeywell people would install the hardware (IMPs were built out of Honeywell 516s back then), and then BBN people would come in a few days later to shake down the software. An easy couple of weeks of grace ๐ง
BBN fixed their timing trouble, air-shipped the IMP, and it arrived on UCLA's loading dock on Saturday, August 30. They wheeled it into the computer room and plugged it in, and the software restarted from where it had been when the plug was pulled in Cambridge. Still Saturday, August 30. Panic time at UCLA ๐ฑ๐
The second IMP was delivered to SRI at the beginning of October, and ARPA's interest was intense ๐ฅ Larry Roberts and Barry Wessler came by for a visit on November 21, and they actually managed to demonstrate a Telnet-like connection to SRI ๐
With the pressure to get something working, and the general confusion about how to reach the high generality they all wanted, they punted. They defined the first set of protocols to include only Telnet and FTP functions. Specifically, only asymmetric, user-server relationships were supported ๐ In December 1969 they met with Larry Roberts in Utah and got their first direct experience with "redirection." Larry made it abundantly clear that their first step wasn't big enough, so they went back to the drawing board ๐ค Over the next few months they designed a symmetric host-host protocol and defined an abstract implementation of it known as the Network Control Program. ("NCP" later came to be used as the name for the protocol, but it originally meant the program within the operating system that managed connections. The protocol itself was known blandly only as the host-host protocol.) Along with the basic host-host protocol, they also envisioned a hierarchy of protocols, with Telnet, FTP, and some splinter protocols as the first examples. Stephen jokes that if they'd only consulted the ancient mystics, they would have immediately seen that seven layers were required ๐ฎ๐
The initial experiment was declared an immediate success, and the network kept growing ๐ฑ More and more people started coming to meetings, and the Network Working Group began to take shape. Working Group meetings started having 50 and 100 people instead of the half dozen they'd had in 1968 and early 1969 ๐ฅณ They held one meeting in conjunction with the Spring Joint Computer Conference in Atlantic City in 1971. In October 1971 everyone convened at MIT for a major protocol "fly-off" ๐ซ Reps from each site were on hand, and everyone tried to log in to everyone else's site. Except for one site that was completely down, the matrix was almost entirely filled in, and they'd reached a major milestone in connectivity ๐๐
The rapid growth of the network and the working group also led to a big pile of RFCs ๐ When the 100th RFC was in sight, Peggy Karp took on the job of indexing them. That seemed like a huge task back then, and they could hardly have anticipated seeing more than 1000 RFCs several years later ๐ณ
Where will it end? The network has exceeded all estimates of its growth ๐ It has been transformed, extended, cloned, renamed, and reimplemented. Stephen doubts there's a single computer still on the network that was on it in 1971 ๐ฅ๏ธ But the RFCs march on ๐ซก Maybe Stephen will write a few words for RFC 10,000 ๐๐ฆโจ
The RFCs are sorted into broad groups, and each group gets split up by topic. Like, every RFC about file transfer lives in 5 (Applications) c (File Transfer), so you always know where to look ๐ฆ
1. Administrative ๐
1a. Assigned Numbers RFCs
997, 990, 960, 943, 923, 900, 870, 820, 790, 776, 770, 762,
758, 755, 750, 739, 717, 604, 503, 433, 349, 322, 317, 204,
179, 175, 167.1b. Official Protocols RFCs
991, 961, 944, 924, 901, 880, 840, 694, 661, 617, 582, 580,
552.
774 - Internet Protocol Handbook Table of Contents1c. Meeting Notes and Minutes ๐
898 - Gateway Special Interest Group Meeting Notes
808, 805, 469 - Computer Mail Meeting Notes
910, 807 - Multimedia Mail Meeting Notes
585 - ARPANET Users Interest Working Group Meeting
549, 396, 282, 253 - Graphics Meeting Notes
371 - International Computer Communications Conference
327 - Data and File Transfer Workshop Notes
316 - Data Management Working Group Meeting Report
164, 131, 116, 108, 101, 082, 077, 066, 063, 037, 021 - Network
Working Group Meeting1d. Meeting Announcements and Group Overviews ๐ฃ
828 - Data Communications: IFIP's International "Network" of
Experts
631 - Call for Papers: International Meeting on Minicomputers
and Data Communication
584 - Charter for ARPANET Users Interest Working Group
537 - Announcement of NGG Meeting
526 - Technical Meeting - Digital Image Processing Software
Systems
504 - Workshop Announcement
483 - Cancellation of the Resource Notebook Framework Meeting
474, 314, 246, 232, 134 - Network Graphics Working Group
471 - Announcement of a (Tentative) Workshop on Multi-Site
Executive Programs
461 - Telnet Meeting Announcement
457 - TIPUG
456 - Memorandum
454 - File Transfer Protocol Meeting Announcement
453 - Meeting Announcement to Discuss a Network Mail System
374 - IMP System Announcement
359 - The Status of the Release of the New IMP System (2600)
343, 331 - IMP System Change Notification
324 - RJE Protocol Meeting
323 - Formation of Network Measurement Group (NMG)
320 - Workshop on Hard Copy Line Graphics
309 - Data and File Transfer Workshop Announcement
299 - Information Management System
295 - Report of the Protocol Workshop
291, 188, 173 - Data Management Meetings
245, 234, 207, 188, 173, 140, 116, 099, 087, 085, 075, 043, 035
- Network Working Group Meetings
222 - System Programmer's Workshop
212 - NWG Meeting on Network Usage
157 - Invitation to the Second Symposium on Problems in the
Optimization of Data Communication Systems
149 - The Best Laid Plans...
147 - The Definition of a Socket
111 - Pressure from the Chairman
048 - A Possible Protocol Plateau
046 - ARPA Network Protocol Notes1e. Distribution List ๐ฌ
402, 363, 329, 303, 300, 211, 168, 155 - ARPA Network Mailing
Lists
069 - Distribution List Change for MIT
052 - Updated Distribution List1f. Policies ๐
980 - Protocol Document Order Form
952, 810, 608 - Host Table Specification
945 - A DoD Statement on the NRC Report
902 - ARPA-Internet Protocol Policy
849 - Suggestions for Improved Host Table Distribution
678 - Document Formats
602 - The Stockings Were Hung by the Chimney With Care
115 - Some Network Information Center Policies on Handling
Documents
053 - An Official Protocol Mechanism1g. Request for Comments Administrative ๐๏ธ
999, 899, 800, 699 - Requests for Comments Summary
825 - Request for Comments on Requests for Comments
629 - Scenario for Using the Network Journal
628 - Status of RFC Numbers and a Note on Pre-assigned Journal
Numbers
598, 200, 170, 160, 100, 084 - RFC Index1h. Bibliographies ๐
829 - Packet Satellite Technology Reference Sources
290 - Computer Network and Data Sharing: A Bibliography
243 - Network and Data Sharing Bibliography1i. Other ๐
637 - Change of Network Address for SU-DSL
634 - Change in Network Address for Haskins Lab
616 - Latest Network Maps
609 - Statement of Upcoming Move of NIC/NLS Service
590 - MULTICS Address Change
588 - London Node is Now Up
551 - NYU, ANL, and LBL Joining the Net
544 - Locating On-Line Documentation at SRI-ARC
543 - Network Journal Submission and Delivery
518 - ARPANET Accounts
511 - Enterprise Phone Service to NIC From ARPANET Sites
510 - Request for Network Mailbox Addresses
432 - Network Logical Map
423, 389 - UCLA Campus Computing Network Liaison Staff for APRA
Network
421 - A Software Consulting Service for Network Users
419 - MIT-DMS on Vacation
416 - The ARC System will be Unavailable for Use During
Thanksgiving Week
405 - Correction to RFC 404
404 - Host Address Changes Involving Rand and ISI
403 - Desirability of a Network 1108 Service
386 - Letter to TIP Users - 2
384 - Official Site IDENTS for Organizations in the ARPA
Networks
381 - Three Aids to Improved Network Operation
356 - ARPA Network Control Center
334 - Network Use on May 8
305 - Unknown Host Numbers
301 - BBN IMP No. 5 and NCC Schedule for March 4, 1972
276 - NIC Course
249 - Coordination of Equipment and Supplies Purchase
223 - Network Information Center Schedule for Network Users
185 - NIC Distribution of Manuals and Handbooks
154 - Exposition Style
136 - Host Accounting and Administrative Procedures
118 - Information Required for Each Service Available to the
Network
095 - Distribution of NWG/RFC's Through the NIC
016 - MIT2. ARPANET Host to Host Protocol ๐
2a. Network Control Protocol
801 - NCP/TCP Transition Plan
773 - Comments on NCP/TCP Mail Service Transition Strategy
714 - A Host/Host Protocol for an ARPANET-type Network
689 - Tenex NCP Finite State Machine for Connections
663 - A Lost Message Detection and Recovery Protocol
636 - TIP/TENEX Reliability Improvements
635 - An Assessment of ARPANET Protocols
534, 516, 512 - Lost Message Detection
492, 467 - Proposed Change to Host-Host Protocol
Resynchronization of Connection Status
489 - Comment on Resynchronization of Connection Status
Proposal
425 - "But my NCP Costs $500 a day..."
210 - Improvement of Flow Control
197 - Initial Connection Protocol - Revised
176 - Comments on Byte Size for Connections
165 - A Proferred Official Initial Connection Protocol
147 - The Definition of a Socket
142 - Time-out Mechanism in the Host-Host Protocol
132, 124, 107, 102 - Output of the Host-Host Protocol Glitch
Cleaning Committee
129 - A Request for Comments on Socket Name Structure
128 - Bytes
117 - Some Comments on the Official Protocol
072 - Proposed Moratorium on Changes to Network Protocol
068 - Comments on Memory Allocation Control Commands (CEASE,
ALL, GVB, RET) and RFNM
065 - Comments on Host-Host Protocol Document Number 1
060 - A Simplified NCP Protocol
059 - Flow Control-Fixed Versus Demand Allocation
058 - Logical Message Synchronization
057, 054 - An Official Protocol Proffering
056 - Third Level Protocol
055 - A Prototypical Implementation of the NCP
050, 049, 048, 047, 046, 045, 044, 040, 039, 038, 036, 033 -
New Host-Host Protocol
042 - Message Data Types
023 - Transmission of Multiple Control Messages
022 - Host-Host Control Message Formats
018 - Comments Re: Host-Host control link
015 - Network Subsystem for Time Sharing Hosts
011 - Implementation of the Host-Host Software Procedures in
GORDO
009, 001 - Host Software
008 - ARPA Network Functional Specifications
005 - DEL
002 - Links2b. Initial Connection Protocol
202 - Possible Deadlock in ICP
197 - Initial Connection Protocol - Revised
161 - A Solution to the Race Condition in the ICP
151, 148, 143, 127, 123 - A Proferred Official ICP
150 - The Use of IPC Facilities
145 - Initial Connection Protocol Control Commands
093 - Initial Connection Protocol
080 - Protocol and Data Formats
066 - 3rd Level Ideas and Other Noise3. Internet Level ๐
3a. Internet Protocol
815 - IP Datagram Reassembly Algorithms
791, 760 - Internet Protocol (IP)
781 - A Specification of the Internet Protocol IP Timestamp
Option3b. Internet Control Message Protocol
792, 777 - Internet Control Message Protocol (ICMP)3c. Gateway Protocols ๐ช
985 - Requirements for Internet Gateways
975 - Autonomous Confederations
970 - On Packet Switches With Infinite Storage
911 - EGP Gateway under Berkeley Unix
904, 890, 888, 827 - Exterior Gateway Protocol
875 - Gateways, Architectures, and Heffalumps
823 - Gateway Gateway Protocol3d. Other
986 - Working Draft - Guidelines for the Use of Internet-IP
Addressing in the ISO Connectionless-Mode Network
981 - An Experimental Multiple-Path Routing Algorithm
963 - Some Problems with the Specification of the Military
Standard Internet Protocol
950 - Internet Standard Subnetting Procedure
947 - Multi-Network Broadcasting Within the Internet
940, 917, 925, 932, 936, 922 - Internet Subnets Protocol
925, 917, 826 - Multi-LAN Address Resolution Protocol
919, 922 - Broadcasting Internet Datagrams
891 - DCN Local-Network Protocols
871 - A Perspective on the ARPANET Reference Model
831 - Backup Access to the European Side of SATNET
817 - Modularity and Efficiency in Protocol Implementation
816 - Fault Isolation and Recovery
814 - Name, Addresses, Ports, and Routes
796 - Address Mapping
795 - Service Mappings
730 - Extensible Field Addressing4. Host Level ๐ฅ๏ธ
4a. User Datagram Protocol
768 - User Datagram Protocol4b. Transmission Control Protocol ๐
983 - ISO Transport Services on Top of the TCP
964 - Some Problems with the Specification of the Military
Standard Transmission Control Protocol
896 - Congestion Control in IP/TCP Internetworks
889 - Internet Delay Experiments
879 - The TCP Maximum Segment Size and Related Topics
872 - TCP-ON-A-LAN
817 - Modularity and Efficiency in Protocol Implementation
816 - Fault Isolation and Recovery
814 - Name, Addresses, Ports, and Routes
794 - Pre-Emption
793, 761, 675 - Transmission Control Protocol
721 - Out of Band Control Signals in a Host to Host Protocol
700 - A Protocol Experiment4c. Transaction Protocols and Distributed Operating Systems ๐ง
- 955 - Towards a Transport Service for Transaction Processing Applications
- 938 - Internet Reliable Transaction Protocol Functional and Interface Specification
- 908 - Reliable Data Protocol
- 722 - Thoughts on Interactions in Distributed Services
- 713 - MSDTP -- Message Services Data Transmission Protocol
- 712 - A Distributed Capability Computing System DCCS
- 708 - Elements of a Distributed Programming System
- 707 - A High-Level Framework for Network-Based Resource Sharing
- 684 - A Commentary on Procedure Calling as A Network Protocol
- 677 - The Maintenance of Duplicate Databases
- 674 - Procedure Call Documents--Version 2
- 672 - A Multi-Site Data Collection Facility
- 671 - A Note on Reconnection Protocol
- 645 - Network Standard Data Specification Syntax
- 615 - Proposed Network Standard Data Pathname Syntax
- 610 - Further Datalanguage Design Concepts
- 592 - Some Thoughts on System Design to Facilitate Resource Sharing
- 578 - Using MIT-MATHLAB MACSYMA From MIT-DMS Muddle - An Experiment in Automated Resource Sharing
- 515 - Specifications for Datalanguage, Version 0/9
- 500 - The Integration of Data Management Systems on a Computer Network
- 441 - Inter-Entity Communication - An Experiment
- 437 - Data Reconfiguration Service at UCSB
- 203 - Achieving Reliable Communication
- 076 - Connection-by-Name: User-Oriented Protocol
- 062 - A System for Interprocess Communication in a Resource Sharing Computer Network
- 061 - A Note on Interprocess Communication in a Resource Sharing Computer Network
- 051 - Proposal for a Network Interchange Language
- 031 - Binary Message Forms in Computer Networks
- 005 - DEL
- 001 - Host Software
4d. Other ๐
- 998, 969 - NETBLT: A Bulk Data Transfer Protocol
- 988 - Host Extensions for IP Multicasting
- 979 - PSN End-to-End Functional Specification
- 966 - A Multicast Extension to the Internet Protocol
- 869 - Host Monitoring Protocol
- 741 - Specifications for the Network Voice Protocol NVP
- 643 - Cross Net Debugger
- 162 - NETBUGGER3
5. Application Level โจ
5a. Telnet Protocol ๐
- 854, 764 - Telnet Protocol Specification
- 818 - The Remote User Telnet Service
- 801 - NCP/TCP Transition Plan
- 782 - A Virtual Terminal Management Model
- 764 - Telnet Protocol Specification
- 728 - A Minor Pitfall in the Telnet Protocol
- 688 - Tentative Schedule for the New Telnet Implementation for the TIP
- 681 - Network Unix
- 600 - Interfacing an Illinois Plasma Terminal to the ARPANET
- 596 - Second Thoughts on Telnet Go-Ahead
- 595 - Some Thoughts in Defense of the Telnet Go-Ahead
- 593 - Telnet and FTP Implementation Schedule Change
- 576 - Proposal for Modifying Linking
- 570 - Experimental Input Mapping Between NVT ASCII and UCSB Online System
- 562 - Modifications to the Telnet Specification
- 559 - Comments on the New Telnet Protocol and Its Implementation
- 529 - A Note on Protocol Synch Sequences
- 513 - Comments on the New Telnet Specifications
- 495 - Telnet Protocol Specification
- 466 - Telnet Logger/Server for Host LL-67
- 461 - Telnet Meeting Announcement
- 452 - Telnet Command at Host LL
- 435 - Telnet Issues
- 426 - Reconnection Protocol
- 393 - Comments on Telnet Protocol Changes
- 377 - Using TSO Via ARPA Network Virtual Terminal
- 357 - An Echoing Strategy for Satellite Links
- 355, 346 - Satellite Considerations
- 340 - Proposed Telnet Changes
- 339 - MLTNET - A "Multi-Telnet" Subsystem for TENEX
- 328 - Suggested Telnet Protocol Changes
- 318 - Ad Hoc Telnet Protocol
- 216 - Telnet Access to UCSB's On-Line System
- 215 - NCP, ICP, and Telnet: The Terminal IMP Implementation
- 206 - A User Telnet Description of an Initial Implementation
- 205 - NETCRT - A Character Display Protocol
- 190 - DEC PDP-10 - IMLAC Communication System
- 158 - Proposed Telnet Protocol
- 139 - Discussion of Telnet Protocol
- 137 - Telnet Protocol - A Proposed Document
- 135, 110 - Conventions for Using an IBM 2741 Terminal as a User Console for Access to Network Server Hosts
- 103 - Implementation of Interrupt Keys
- 097 - A First Cut at a Proposed Telnet Protocol
- 091 - A Proposed User-User Protocol
- 015 - Network Subsystem for Time Sharing Hosts
5b. Telnet Options ๐ฆ
- 946 - Telnet Terminal Location Number Option
- 933 - Output Marking Telnet Option
- 930 - Telnet Terminal Type Option
- 927 - TACACS User Identification Telnet Option
- 885 - Telnet End of Record Option
- 884 - Telnet Terminal Type Option
- 861 - Telnet Extended Options - List Option
- 860 - Telnet Timing Mark Option
- 859 - Telnet Status Option
- 858 - Telnet Suppress Go Ahead Option
- 857 - Telnet Echo Option
- 856 - Telnet Binary Transmission
- 855 - Telnet Option Specifications
- 854 - Telnet Protocol Specifications
- 779 - Telnet Send-Location Option
- 749 - Telnet SUPDUP-OUTPUT Option
- 748 - Telnet Randomly-Lose Option
- 736 - Telnet SUPDUP Option
- 735 - Revised Telnet Byte Macro Option
- 734 - SUPDUP Protocol
- 747 - Recent Extensions to the SUPDUP Protocol
- 746 - The SUPDUP Graphics Extension
- 732 - Telnet Data Entry Terminal Option
- 731 - Telnet Data Entry Terminal Option
- 729 - Telnet Byte Macro Option
- 727 - Telnet Logout Option
- 726 - Remote Controlled Transmission and Echoing Telnet Option
- 719 - Discussion on RCTE
- 718 - Comments on RCTE from the Tenex Implementation Experience
- 703, 702, 701 - Survey of New-Protocol Telnet Servers
- 698 - Telnet Extended ASCII Option
- 679 - February, 1975, Survey of New-Protocol Telnet Servers
- 669 - November 1974, Survey of New-Protocol Telnet Servers
- 659 - Announcing Additional Telnet Options
- 658 - Telnet Output Line Feed Disposition
- 657 - Telnet Output Vertical Tab Disposition Option
- 656 - Telnet Output Vertical Tab Stops Option
- 655 - Telnet Output Form Feed Disposition Option
- 654 - Telnet Output Horizontal Tab Disposition Option
- 653 - Telnet Output Horizontal Tab Stops Option
- 652 - Telnet Output Carriage Return Disposition Option
- 651 - Revised Telnet Status Option
- 587 - Announcing New Telnet Options
- 581 - Corrections to RFC 560 - Remote Controlled Transmission and Echoing Telnet Option
- 563 - Comments on the RCTE Telnet Option
- 560 - Remote Controlled Transmission and Echoing Telnet Option
5c. File Transfer Protocol ๐
- 987 - Mapping Between X.400 and RFC 822
- 959, 542, 354, 265, 172, 114 - The File Transfer Protocol
- 949 - FTP Unique-Named Store Command
- 913 - Simple File Transfer Protocol
- 906 - Bootstrap Loading Using TFTP
- 822 - Standard for the Format of ARPA Internet Text Messages
- 821, 788 - Simple Mail Transfer Protocol
- 783, 768, 764 - The TFTP Protocol Revision 2
- 775 - Directory Oriented FTP Commands
- 743 - FTP Extension: XRSQ/XRCP
- 737 - FTP Extension: XSEN
- 697 - CWD Command of FTP
- 691 - One More Try on the FTP
- 686 - Leaving Well Enough Alone
- 683 - FTPSRV -- Tenex Extension for Paged Files
- 678 - Document File Format Standards
- 662 - Performance Improvement in ARPANET File Transfers from Multics
- 640 - Revised FTP Reply Codes
- 630 - FTP Error Code Usage for More Reliable Mail Service
- 624 - Comments on the File Transfer Protocol
- 614 - Response to RFC 607 - Comments on the FTP
- 607 - NIC-21255 Comments on the File Transfer Protocol
- 573 - Data and File Transfer - Some Measurement Results
- 571 - Tenex FTP Problem
- 535 - Comments on File Access Protocol
- 532 - The UCSD-CC Server-FTP Facility
- 520 - Memo to FTP Group (Proposal for File Access Protocol)
- 506 - An FTP Command Naming Problem
- 505 - Two Solutions to a File Transfer Access Problem
- 501 - Un-Muddling "Free File Transfer"
- 487 - Host-Dependent FTP Parameters
- 486 - Data Transfer Revisited
- 480 - Host-Dependent FTP Parameters
- 479 - Use of FTP by the NIC Journal
- 478 - FTP Server-Server Interaction - II
- 475 - FTP and the Network Mail System
- 468 - FTP Data Compression
- 463 - FTP Comments and Response to RFC 430
- 458 - Mail Retrieval via FTP
- 454 - File Transfer Protocol - Meeting Announcement and a New Proposed Document
- 448 - Print Files in FTP
- 438 - FTP Server-Server Interaction
- 430 - Comments on File Transfer Protocol
- 418 - Server File Transfer Under TSS/360 at NASA/Ames Research Center
- 414 - File Transfer Protocols (FTP): Status and Further Comments
- 412 - User FTP Documentation
- 385 - Comments on the File Transfer Protocol (RFC 354)
- 310 - Another Look at Data and File Transfer Protocols
- 294 - The Use of "Set Data Type" Transaction in the File Transfer Protocol
- 281 - A Suggested Addition to File Transfer Protocol
- 269 - Some Experience with File Transfer
- 264, 171 - The Data Transfer Protocol
- 250 - Some Thoughts on File Transfer
- 242 - Data Descriptive Language for Shared Data
- 238 - Comments on DTP and FTP Protocols
- 163 - Data Transfer Protocols
- 141 - Comments on RFC 114 (A File Transfer Protocol)
- 133 - File Transfer and Error Recovery
5d. Domain Name System ๐ธ
- 974 - Mail Routing and the Domain System
- 973 - Domain System Changes and Observations
- 953, 811, 810 - HOSTNAME Protocol
- 921, 897 - Domain Name System Implementation Schedule
- 920 - Domain Requirements
- 883 - Domain Names - Implementation and Specification
- 882 - Domain Names - Concepts and Facilities
- 881 - The Domain Names Plan and Schedule
- 830 - A Distributed System for Internet Name Service
- 819 - The Domain Naming Convention for Internet User Applications
- 799 - Internet Name Domains
- 756 - The NIC Name Server -- A Datagram-Based Information Utility
- 752 - A Universal Host Table
5e. Mail and Message Systems โ๏ธ
okay the mail list is still going, bestie ๐ฌ๐
994, 983 - PCMAIL: A Distributed Mail System
977 - Network News Transfer Protocol
976 - UUCP Mail Interchange Format Standard
974 - Mail Routing and the Domain System
934 - Proposed Standard for Message Encapsulation
915 - Network Mail Path Service
886 - Proposed Standard for Message Header Munging
850 - Standard for Interchange of USENET Messages
841 - Specification for Message Format for Computer Based
Message Systems
822 - Standard for the Format of ARPA Internet Text Messages
821 - Simple Mail Transfer Protocol
806 - Specification for Message Format for Computer Based
Message Systems
780, 772 - Mail Transfer Protocol
786 - Mail Transfer Protocol - ISI TOPS-20 MTP-NIMAIL Interface
785 - Mail Transfer Protocol - ISI TOPS-20 File Definitions
784 - Mail Transfer Protocol - ISI TOPS-20 Implementation
771 - Mail Transition Plan
763 - Role Mailboxes
757 - A Suggested Solution to the Naming, Addressing, and
Delivery Problem for ARPANET Message Systems
754 - Out-of-Net Host Addresses for Mail
753 - Internet Message Protocol
751 - Survey of FTP Mail and MLFL
733 - Standard for the Format of ARPA Network Text Messages
724 - Proposed Official Standard for the Format of ARPA Network
Messages
720 - Address Specification Syntax for Network Mail
706 - On the Junk Mail Problem
680 - Message Transmission Protocol
644 - On the Problem of Signature Authentication for Network
Mail
577 - Mail Priority
574 - Announcement of a Mail Facility at UCSB
561 - Standardizing Network Mail Headers
555 - Responses to Critiques of the Proposed Mail Protocol
539, 524 - A Proposed Mail Protocol
498 - On Mail Service to CCN
491 - What is "Free"?
475 - On FTP and the Network Mail System
458 - Mail Retrieval via FTP
333 - A Proposed Experiment with a Message Switching Protocol
278, 224, 221, 196 - A Mail Box Protocol5f. Facsimile and Bitmaps ๐
809 - UCL Facsimile System
804 - Facsimile Formats
803 - Dacom 450/500 Facsimile Date Transcoding
798 - Decoding Facsimile Data From the Rapicom 450
797 - Bitmap Formats
769 - Rapicom 450 Facimile File Format5g. Graphics ๐จ
965 - A Format for a Graphical Communication Protocol
553 - Draft Design for a Text/Graphics Protocol
493 - Graphics Protocol
401 - Conversion of NGP-0 Coordinates to Device Specific
Coordinates
398 - UCSB Online Graphics
387 - Some Experiences in Implementing Network Graphics
Protocol Level 0
351 - Information Form for the ARPANET Graphics Resources
Notebook
336 - Level 0 Graphics Input Protocol
296 - DS-1 Display System
292 - Graphics Protocol - Level 0 only
285 - Network Graphics
268 - Graphics Facilities Information
199 - Suggestions for a Network Data-Telnet Graphics Protocol
192 - Some Factors Which a Network Graphics Protocol Must
Consider
191 - Graphics Implementation and Conceptualization at ARC
186 - A Network Graphics Loader
184 - Proposed Graphic Display Modes
181, 177 - A Device Independent Graphical Display Description
178 - Network Graphics Attention Handling
125, 086 - Proposal for a Network Standard Format for a Data
Stream to Control Graphics Display
094 - Some Thoughts on Network Graphics5h. Data Management ๐๏ธ
304 - A Data Management System Proposal for the ARPA Network
195 - Data Computers - Data Descriptions and Access Language
194 - The Data Reconfiguration Service - Compiler/Interpreter
Implementation Notes
166 - Data Reconfiguration Service - An Implementation
Specification
144 - Data Sharing on Computer Networks
138 - Status Report on Proposed Data Reconfiguration Service
083 - Language-Machine for Data Reconfiguration5i. Remote Job Entry ๐
740, 599, 589, 325, 189, 088 - CCN Network Remote Job Entry
Program - NETRJS
725 - An RJE Protocol for a Resource Sharing Network
499 - Harvard's Network RJE
490 - Surrogate RJS for UCLA-CCN
477, 436 - Remote Job Service at UCSB
407 - Remote Job Entry
368 - Comments on "Proposed Remote Job Entry Protocol"
360 - Proposed Remote Job Entry Protocol
338 - EBCDIC/ASCII Mapping for Network RJE
307 - Using Network Remote Job Entry
283 - NETRJT - Remote Job Service Protocol for TIPS
105 - Network Specification for Remote Job Entry and Remote Job
Output Retrieval at UCSB5j. Time โฐ
958, 957, 956 - Network Time Protocol
868 - Time Server Protocol
867 - Daytime Protocol
778 - DCNET Time Server Protocol
738 - Time Server
685 - Response Time in Cross-network Debugging
034 - Some Brief Preliminary Notes on the ARC Clock
032 - Some Thoughts on SRI's Proposed Real Time Clock
028 - Time Standards5k. Other ๐
978 - Voice File Interchange Protocol (VFIP)
972 - Password Generator Protocol
954, 812 - Whois Protocol
951 - Bootstrap Protocol
937, 918 - Post Office Protocol
931, 912 - Authentication Service
913 - Simple File Transfer Protocol
909 - Loader Debugger Protocol
891 - DCN Local Net Protocol
887 - Resource Location Protocol
866 - Active Users Protocol
865 - Quote of the Day Protocol
864 - Character Generator Protocol
863, 361, 348 - Discard Protocol
862, 361, 347 - Echo Protocol
821, 822 - Simple Mail Transfer Protocol
783 - Trivial File Transfer Protocol
767 - Document Formats
759 - Internet Message Protocol
742 - Finger Protocol
734 - SUPDUP Protocol
726 - Remote Controlled Transmission and Echoing Telnet Option
666 - Specification of the Unified User-Level Protocol
621 - NIC User Directories at SRI-ARC
569 - Network Standard Text Editor
470 - Change in Socket for TIP News Facility
451 - Tentative Proposal for a Unified User Level Protocol
098, 079 - Logger Protocol
029 - Note in Response to Bill English's Request for Comments6. Program Documentation โจ
6a. General ๐ป
496 - A TNLS Quick Reference Card is Available
494 - Availability of MIX and MIXAL in the Network
488 - NLS Classes at Network Sites
485 - MIS and MIXAL at UCSB
431 - Update on SMFS Login and Logout
411 - New Multics Network Software Features
409 - TENEX Interface to UCSB's Simple-Minded File System
399 - SMFS Login and Logout
390 - TSO Scenario Batch Compilation and Foreground Execution
382 - Mathematical Software on the ARPA Network
379 - Using TSO at CCN
373 - Arbitrary Character Sets
350 - User Accounts for UCSB On-Line System
345 - Interest Mixed Integer Programming (MPSX on 360/91 at
CCN)
321 - CBI Networking Activity at MITRE
317 - Official Host-Host Protocol Modification: Assigned Link
Numbers
311 - New Console Attachments to the UCSB Host
251 - Weather Data
223 - Network Information Center Schedule for Network Users
217 - Specification Changes for OLS, RJE/RJOR, and SMFS
174 - UCLA-Computer Science Graphics Overview
122 - Network Specifications for UCSB's Simple-Minded File
System
121 - Network On-Line Operators
120 - Network PL1 Subprograms
119 - Network FORTRAN Subprograms
074 - Specifications for Network Use of the UCSB On-Line System7. Network Specific ๐ฐ๏ธ
7a. ARPANET ๐ฆ
the next bit is all about ARPANET, and it's giving pure history ๐
Okay so this is where the ARPANET crew really gets going ๐ธ Here's the next batch of the host access RFC list, all still in its original form ๐
878, 851, 802 - The ARPANET 1822L Host Access Protocol
852 - The ARPANET Short Blocking Feature
789 - Vulnerabilities of Network Control Protocols: An Example
716 - Interim Revision to Appendix F of BBN 1822
704 - IMP/Host and Host/IMP Protocol Change
696 - Comments on the IMP/HOST and HOST/IMP Protocol Changes
695 - Official Change in Host-Host Protocol
692 - Comments on IMP/Host Protocol Changes
690 - Comments on the Proposed Host/IMP Protocol Changes
687 - IMP/Host and Host/IMP Protocol
667 - BBN Host Ports
660 - Some Changes to the IMP and the IMP/Host Interface
642 - Ready Line Philosophy and Implementation
638, 633 - IMP/TIP Preventive Maintenance Schedule
632 - Throughput Degradation for Single Packet Message
627 - ASCII Text File of Hostnames
626 - On a possible Lockup Condition in IMP Subnet due to
Message Sequencing
625 - On Line Hostnames Service
623 - Comments on On-line Host Name Service
622 - Scheduling IMP/TIP Down Time
620 - Request for Monitor Host Table Updates
619 - Mean Round-Trip Times in the ARPANET
613 - Network Connectivity: A Response to RFC 603
611 - Two Changes to the IMP/Host Protocol
606 - Host Names On-Line
594 - Speedup of Host-IMP Interface
591 - Addition to the Very Distant Host Specification
568, 567 - Cross-Country Network Bandwidth
548 - Hosts Using the IMP Going Down Message Specification
547 - Change to the Very Distant Host Specification
533 - Message-ID Numbers
534 - Lost Message Detection
528 - Software Checksumming in the IMP and Network Reliability
521 - Restricted Use of IMP DDT
508 - Real-Time Data Transmission on the ARPANET
476, 434 - IMP/TIP Memory Retrofit Schedules
449, 442 - The Current Flow-Control Scheme for IMPSYS
447, 445 - IMP/TIP Preventive Maintenance Schedule
417 - LINK Usage Violation
410 - Removal of the 30-second Delay When Hosts Come Up
406 - Scheduled IMP Software Releases
395 - Switch Settings on IMPs and TIPs
394 - Two Proposed Changes to the IMP-HOST Protocol
369 - Evaluation of ARPANET Services (January through March,
1972)
335 - New Interface-IMP/360
312 - Proposed Change in IMP-to-Host Protocol
297 - TIP Message Buffers
280 - A Draft Set of Host Names
274 - Establishing a Local Guide for Network Usage
271 - IMP System Change Notification
270 - Correction to the BBN Report No. 1822
263 - "Very Distant" Host Interface
254 - Scenarios for Using ARPANET Computers
247 - Proffered Set of Standard Host Names
241 - Connecting Computers to NLC Ports
239 - Host Mnemonics Proposed in RFC 226
237 - The NIC's View of Standard Host Names
236 - Standard Host Names
233 - Standardization of Host Call Letters
230 - Toward Reliable Operation of Minicomputer-based Terminals
on a TIP
229 - Standard Host Names
228 - Clarification
226 - Standardization of Host Mnemonics
218 - Changing the IMP Status Reporting
213 - IMP System Change Notification
209 - Host/IMP Interface Documentation
208 - Address Tables
073, 067 - Proposed Change to Host/IMP Spec to Eliminate
Marking
071 - Reallocation in Case of Input Error
070 - A Note On Padding
064 - Getting Rid of Marking
041 - IMP/IMP Teletype Communication
025 - No High Link Numbers
019 - Two Protocol Suggestions to Reduce Congestion at
Swap-Bound Nodes
017a, 017 - Some Questions Re: HOST-IMP Protocol
012 - IMP-HOST Interface Flow Diagrams
007 - HOST-IMP Interface
006 - Conversation with Bob Kahn7b. Internet Protocol On Networks
Next up, the Internet Protocol on networks crew ๐๐
948 - Two Methods for the Transmission of IP Datagrams Over
IEEE 802.3 Networks
907 - Host Access Protocol
903 - A Reverse Address Resolution Protocol
895 - A Standard for the Transmission of IP Datagrams over
Experimental Ethernet Networks
894 - A Standard for the Transmission of IP Datagrams over
Ethernet Networks
893 - Trailer Encapsulations
891 - Internet Protocol on DC Networks
877 - A Standard for the Transmission of IP Datagrams Over
Public Data Networks
826 - Address Resolution Protocol
796 - Address Mappings
795 - Service Mappings7c. Host Front End Protocols
929, 928, 705, 647 - Host-Front End Protocol7d. Other
935 - Reliable Link Layer Protocols
916 - Reliable Asynchronous Transfer Protocol
914 - Thinwire Protocol
824 - The Cronus Virtual Local Network8. Measurement ๐
Now we're in the measurement era, bestie. Numbers, numbers everywhere ๐ฅ
8a. General
573 - Data and File Transfer - Some Measurement Results
557 - Revelations in Network Host Measurements
546 - Tenex Load Averages for July 1973
462 - Responding to User Needs
415 - TENEX Bandwidth
392 - Measurement of Host Costs for Transmitting Network Data
352 - TIP Site Information Form
308 - ARPANET Host Availability Data
286 - Network Library Information System
274 - Establishing a Local Guide for Network Usage
214, 193 - Network Checkout
198 - Site Certification - Lincoln Labs
182 - Compilation of List of Revelant Site Reports
180 - File System Questionnaire
156 - Status of the Illinois Site (Response to RFC 116)
153 - SRI ARC-NIC Status
152 - SRI Artificial Intelligence Status Report
126 - Ames Graphics Facilities at Ames Research Center
112 - User/Server Site Protocol Network HOST Questionnaire
104 - Link 191
106 - USER/SERVER Site Protocol Network Host Questionnaire8b. Surveys
Survey time ๐ฆ so many questionnaires, so little time ๐
971 - A Survey of Data Representation Standards
876 - Survey of SMTP Implementations
848 - Who Provides the "Little" TCP Services?
847 - Summary of Smallberg Surveys
844 - Who Talks ICMP, too? Survey of 18 February 1983
846, 845, 843, 842, 839, 838, 837, 836, 835, 834, 833, 832 -
Who Talks TCP?
787 - Connectionless Data Transmission Survey/Tutorial
703, 702, 701, 679, 669 - Survey of New-Protocol Telnet Servers
565 - Storing Network Survey Data at the Datacomputer
545 - Of What Quality be the UCSB Resource Evaluators?
530 - A Report on the SURVEY Project
523 - SURVEY is in Operation Again
519 - Resource Evaluation
514 - Network Make-Work
464 - Resource Notebook Framework
460 - NCP Survey
459 - Network Questionnaire
450 - Multics Sampling Timeout Change
446 - Proposal to Consider a Network Program Resource Notebook
096 - An Interactive Network Experiment to Study Modes of
Access to the Network Information Center
090 - CCN as a Network Service Center
081 - Request for Reference Information
078 - NCP Status Report: UCSB/Rand8c. Statistics
996 - Statistics Server
618 - A Few Observations on NCP Statistics
612, 601, 586, 579, 566, 556, 538, 522, 509, 497, 482, 455,
443, 422, 413, 400, 391, 378 - Traffic Statistics
603, 597, 376, 370, 367, 366, 362, 352, 344, 342, 332, 330,
326, 319, 315, 306, 298, 293, 288, 287, 267, 266 -
Network Host Status
550 - NIC NCP Experiment
388 - NCP Statistics
255, 252, 240, 235 - Site Status9. Network Experience and Demonstrations ๐ฌ
Time for the fun stuff, the stories and demos that made people go "wait, the network can do THAT?" โจ
9a. General
968 - 'Twas the Night Before Start-up
967 - All Victims Together
573 - Data and File Transfer - Some Measurement Results
527 - ARPAWOCKY
525 - MIT-Mathlab Meets UCSB-OLS
439 - PARRY Encounters the Doctor
420 - CCA ICC Weather Demo
372 - Notes on a Conversation with Bob Kahn on the ICCC
364 - Serving Remote Users on the ARPANET
302 - Excercising the ARPANET
231 - Service Center Standards for Remote Usage - A User's View
227 - Data Transfer Rates (RAND/UCLA)
113 - Network Activity Report: UCSB and Rand
089 - Some Historic Moments in Networking
004 - Network Timetable10. Site Documentation ๐
10a. General
30, 27, 24, 16, 10, 3 - Documentation Conventions11. Other Standards ๐
Okay this section is a whole mix of standards bodies, and I'm obsessed ๐ซถ
11a. ANSI
570 - Experimental Input Mapping Between NVT ASCII and UCSB
Online System
183 - The EBCDIC Codes and Their Mapping to ASCII
020 - ASCII Format for Network Interchange11b. CCITT
987 - Mapping Between X.400 and RFC 822
874 - A Critique of X.2511c. NRC
942 - Transport Protocols for Department of Defense Data
Networks
939 - Executive Summary of the NRC Report on Transport
Protocols for Department of Defense Data Networks11d. ISO
995 - End System to Intermediate System Routing Exchange
Protocol for Use in Conjunction with ISO 8473
994 - Final Text of DIS 8473, Protocol for Providing the
Connectionless Mode Network Service
982 - Guidelines for the Specification of the Structure of the
Domain Specific Part (DSP) of the ISO Standard NSAP
Address
941 - Addendum to the Network Service Definition Covering
Network Layer Addressing
926 - Protocol for Providing the Connectionless-Mode Network
Services
905 - ISO Transport Protocol Specification (ISO DP 8073)
892 - ISO Transport Protocol
873 - The Illusion of Vendor Support12. Never Issued ๐ป
These ones were reserved but never actually made it out into the world, so spooky ๐
12a. Never Issued
014, 026, 092, 159, 201, 220, 244, 248, 257, 258, 259, 260,
261, 262, 272, 275, 277, 279, 284, 337, 341, 358, 375, 380,
383, 397, 424, 427, 428, 444, 465, 481, 484, 502, 507, 517,
536, 540, 541, 554, 558, 564, 572, 575, 583, 605, 639, 641,
646, 648, 649, 650, 664, 665, 668, 670, 673, 676, 682, 693,
709, 710, 711, 715, 723, 853.REQUEST FOR COMMENTS LIST WITH ABSTRACTS โจ
Last stop for this part: the list of RFCs with their abstracts ๐ Here's the table, kept exactly as it is:
RFC Author Date Title
--- ------ ---- -----
999 Westine Mar 87 Requests For Comments Summary
A summary of the Request for Comments Documents from RFC 900-999.
998 Lambert Mar 87 NETBLT: A Bulk Data Transfer
Protocol
This document is a description of and a specification for the
NETBLT protocol. It is a revision of the specification published
in RFC-969. NETBLT (NETwork BLock Transfer) is a transport level
protocol intended for the rapid transfer of a large quantity of
data between computers. It provides a transfer that is reliable
and flow controlled, and is designed to provide maximum throughput
over a wide variety of networks. Although NETBLT currently runs
on top of the Internet Protocol (IP), it should be able to operate
on top of any datagram protocol similar in function to IP.And here's what those abstracts are saying, in plain-ish girl talk ๐
RFC 999 is the summary by Westine from Mar 87, and it's basically the recap of every Request for Comments document from RFC 900-999 ๐ง
RFC 998 is by Lambert, also from Mar 87, and it's all about NETBLT ๐ฆ It's a revision of the spec that came out in RFC-969. NETBLT (NETwork BLock Transfer) is a transport level protocol built for moving a huge amount of data between computers really fast ๐จ It's reliable, it's flow controlled, and it's designed to get maximum throughput over a wide variety of networks ๐ฅ Right now it runs on top of the Internet Protocol (IP), but it should be able to operate on top of any datagram protocol that works similarly to IP. Main character energy ๐
This is the leftover bit from the entry above, and it's giving "not ready yet, bestie" ๐ซ This document is published for discussion and comment, and it doesn't count as a standard. The proposal may change, some parts of the protocol aren't specified yet, so implementing it is not advised ๐ โโ๏ธ
997 ยท Reynolds ยท Mar 87 ยท Internet Numbers
This is an official status report on the network numbers the Internet community uses ๐ข As of 1-Mar-87, the Network Information Center (NIC) at SRI International took over assigning Network Numbers and Autonomous System Numbers, so this RFC records the assignments that existed at the moment of that handoff ๐โจ
996 ยท Mills ยท Feb 87 ยท Statistics Server
This RFC is a standard for the ARPA Internet community ๐ Hosts and gateways on the DARPA Internet that want a remote statistics monitoring facility can use this protocol to send their statistics data, when requested, to a monitoring center or debugging host ๐ต๏ธโโ๏ธ๐
995 ยท ANSI ยท Apr 86 ยท End System to Intermediate System Routing Exchange Protocol for use in conjunction with ISO 8473.
This is one of a set of International Standards made to help open systems talk to each other ๐ The set covers the services and protocols needed to make that interconnection happen ๐ซถ
It sits in the layers defined by the Reference Model for Open Systems Interconnection (ISO 7498) and the structure in the Internal Organization of the Network Layer (DIS 8648). Basically, it's a Network Layer protocol ๐ฆ It lets End Systems and Intermediate Systems swap configuration and routing info, which keeps the routing and relaying functions of the Network Layer running smoothly ๐ฆ
994 ยท ANSI ยท Mar 86 ยท Final Text of DIS 8473, Protocol for Providing the Connectionless Mode Network Service
Also one of the International Standards set for open-systems interconnection ๐ธ It covers the services and protocols needed for that. โจ
It's positioned by the layers in the Reference Model for Open Systems Interconnection (ISO 7498), and it's a Network Layer protocol ๐ง It can be used between network-entities in end systems, in Network Layer relay systems, or in both ๐ It provides the Connectionless-mode Network Service defined in Addendum 1 to the Network Service Definition Covering Connectionless-mode Transmission (ISO 8348/AD1) ๐
993 ยท Clark ยท Dec 86 ยท PCMAIL: A Distributed Mail System for Personal Computers
This document talks about the PCMAIL workstation-based distributed mail system ๐ฌ It's a revision of the design in NIC RFC 984 ๐ The changes came from discussion and comments from a bunch of places, plus more research into interactive PCMAIL clients and running client code on machines that aren't IBM PCs ๐ฅ๏ธ Since this design may change, implementing this document is not advised ๐
992 ยท Birman ยท Nov 86 ยท On Communication Support for Fault-Tolerant Process Groups
This memo describes a set of multicast communication primitives that come with a way to handle process failure and recovery ๐ก๏ธโจ These primitives make it easier to build fault-tolerant process groups, which can deliver distributed services in an environment with non-malicious crash failures ๐
Here's the argument: the "best effort" reliability that host groups offer may not meet the needs of researchers building fault-tolerant software ๐ฅบ The basic premise is that handling failures, recoveries, and dynamic process migration reliably matters a lot for distributed programming. If communication support behaves unpredictably when those events happen, higher-level applications end up carrying an unbearable complexity burden ๐ญ That complexity doesn't show up when you use the fault-tolerant process group approach ๐
991 ยท Reynolds ยท Nov 86 ยท Official ARPA-Internet Protocols
This RFC names the documents that specify the official protocols used on the Internet, and comments note any revisions or changes that are planned ๐๏ธ It's an official status report on the numbers used in protocols across the ARPA-Internet community ๐ฅ This memo obsoletes RFCs 961, 944, 924, 901, 880, 840, 694, 661, 617, 582, 580, 552. Bye bye, old ones ๐
990 ยท Reynolds ยท Nov 86 ยท Assigned Numbers
This Network Working Group Request for Comments lists the currently assigned values from several series of numbers used in network protocol implementations ๐ข๐ It's also an official status report on the numbers used in protocols in the ARPA-Internet community ๐ This memo obsoletes RFCs 960, 943, 923, 900, 870, 820, 790, 776, 770, 762, 758, 755, 750, 739, 717, 604, 503, 433, 349, 322, 317, 204, 179, 175, 167. That's a lot of retirements ๐ค
989 ยท Linn ยท Feb 87 ยท Privacy Enhancement for Internet Electronic Mail: Part I: Message Encipherment and Authentication Procedures
This RFC proposes a protocol for the Internet community and asks for discussion and suggestions for improvements ๐ It grew out of a series of IAB Privacy Task Force meetings and the internal working papers passed around for them ๐๏ธ It defines message encipherment and authentication procedures as the first phase of privacy enhancement services for electronic mail transfer on the Internet ๐ The procedures are meant to work with a wide range of key management approaches, including both conventional (symmetric) and public-key (asymmetric) approaches for encrypting data encrypting keys ๐๏ธ
Using conventional cryptography for message text encryption and/or authentication is anticipated ๐ง
Privacy enhancement services (confidentiality, authentication, and message integrity assurance) come from end-to-end cryptography between the originator and recipient User Agent processes ๐ธ There are no special processing requirements on the Message Transfer System at endpoints or at intermediate relay sites, so privacy features can be added site-by-site or user-by-user without affecting other Internet entities ๐ Interoperability among heterogeneous components and mail transport facilities is supported too ๐ซง
988 ยท Deering ยท Jul 86 ยท Host Extensions for IP Multicasting
This memo specifies the extensions a host implementation of the Internet Protocol (IP) needs to support internetwork multicasting ๐ก It supersedes the specification in RFC 966 and is a proposed protocol standard for IP multicasting in the ARPA-Internet ๐ซ If you want the motivation and rationale behind the multicasting extension, go read RFC 966 ๐
987 ยท Kille ยท Jun 86 ยท Mapping Between X.400 and RFC 822
X.400 is a series of protocols CCITT defined for an Interpersonal Messaging Service (IPMS), using a store-and-forward Message Transfer Service ๐ฎ It's expected to get implemented very widely ๐ This document describes mappings that let systems running X.400 talk to systems using RFC 822 mail protocols, or protocols derived from RFC 822 ๐ It proposes a protocol for the ARPA-Internet community and asks for discussion and suggestions for improvements ๐ฌ
986 ยท Callon ยท Jun 86 ยท Working Draft -- Guidelines for the Use of Internet-IP addressing in the ISO Connectionless-Mode Network Protocol
This RFC suggests a way to let existing IP addressing, including the IP protocol field, be used for the ISO Connectionless Network Protocol (CLNP) ๐งฉ It's a draft fix for one of the problems with "ISO-grams" in the DoD Internet, and related issues will be covered in later RFCs ๐ฏ It proposes a protocol for the ARPA-Internet community and asks for discussion and suggestions for improvements โจ
985 ยท Mills ยท May 86 ยท Requirements for Internet Gateways
This RFC sums up the requirements for gateways used on networks that support the DARPA Internet protocols ๐ Even though it's aimed at the National Science Foundation research programs, the requirements are written in a general way and are believed to apply across the Internet community ๐ซถ It's guidance for vendors selling products that might be used, or adapted, in an Internet application ๐ It lists the protocols required and points to RFCs and other documents describing the current specs ๐ Suggestions and comments are welcome, and can be sent to Dave Mills (Mills@D.ISI.EDU) or Dave Farber (Farber@HUEY.UDEL.EDU) ๐
984 ยท Clark ยท May 86 ยท PCMAIL: A Distributed Mail System for Personal Computers
This is a preliminary discussion of the design of a personal-computer-based distributed mail system ๐ป PCMAIL gives mail service to an arbitrary number of users, each of whom owns one or more personal computers (PCs) ๐งธ It's split into two halves. The first is a single entity called the "repository" ๐ It's the storage center for incoming mail, which can arrive from the Internet or from other repository users ๐ฅ The repository also keeps a stable copy of each user's mail state, so it's typically a computer with a big pile of disk storage ๐พ It's published for discussion and comment and does not constitute a standard, and since the proposal may change, implementing this document is not advised ๐
983 ยท Cass ยท Apr 86 ยท ISO Transport Services on Top of the TCP
Next up, we'll get the rest of this one! ๐ง๐
Okay bestie, the RFC list is still going strong, so let's keep vibing through it ๐
The ISO and CCITT crowd cooked up a bunch of session, presentation, and application recommendations, and the international community plus loads of vendors adopted them. Honestly it makes so much sense to offer these higher-level services straight over the ARPA-Internet without breaking the stuff that already works ๐ฆ That way people can build real expertise with ISO and CCITT applications that were never available on the ARPA-Internet before. The plan is that hosts on the ARPA-Internet that choose to run ISO TSAP services on top of TCP are expected to adopt and implement this standard. Suggestions for improvement are super welcome ๐
982 ANSI Apr 86 Guidelines for the Specification of
the Structure of the Domain Specific
Part (DSP) of the ISO Standard NSAP
AddressThis is a draft working document from ANSI, the "Guidelines for the Specification of the Structure of the Domain Specific Part (DSP) of the ISO Standard NSAP Address" ๐๏ธ It gives private address administration authorities advice on preferred formats and semantics for the Domain Specific Part (DSP) of an NSAP address. It explains how the DSP can be built so address assignment stays efficient. It's for informational purposes only, its distribution is unlimited, and it does not specify a standard of the ARPA-Internet.
981 Mills Mar 86 An Experimental Multiple-Path
Routing AlgorithmThis doc introduces wiretap algorithms, a class of experimental multiple routing algorithms that compute quasi-optimum routes for stations sharing a packet-radio broadcast channel ๐ก The primary route (a minimum-distance path) gets computed, along with extra paths ordered by distance, which serve as alternate routes if the primary route fails. This prototype is an example of a class of routing algorithms and data-base management techniques that might find wider use in the Internet community. Discussions and suggestions for improvements are welcomed โจ
980 Jacobsen Mar 86 Protocol Document Order InformationThis RFC shows how to get your hands on various protocol documents used in the DARPA research community ๐ It includes an overview of the new 1985 DDN Protocol Handbook and available sources for related documents, like DOD, ISO, and CCITT.
979 Malis Mar 86 PSN End-to-End Functional
SpecificationThis memo is an updated version of BBN Report 5775, "End-to-End Functional Specification" ๐ฅ It describes important changes to the functionality of the interface between a host and the PSN (Packet Switch Node), and anyone supporting a host on either the ARPANET or MILNET should review it carefully. The new End-to-End Protocol (EE) is being developed to fix a bunch of deficiencies in the old End-to-End Protocol, boost its performance and overall throughput, and better equip the Packet Switch Node (also known as the IMP) to support its current and anticipated host population.
978 Reynolds Feb 86 Voice File Interchange Protocol
(VFIP)The Voice File Interchange Protocol (VFIP) exists so different systems in the ARPA-Internet community can swap various types of speech files ๐๏ธ Suggestions for improvement are encouraged.
977 Kantor Feb 86 Network News Transfer ProtocolNNTP specifies a protocol for distributing, querying, retrieving, and posting news articles, using reliable stream-based transmission among the ARPA-Internet community ๐ฐ NNTP is designed so news articles live in a central database, letting a subscriber pick out only the items they want to read. Indexing, cross-referencing, and expiration of aged messages are provided too. This RFC suggests a proposed protocol for the ARPA-Internet community and requests discussion and suggestions for improvements.
976 Horton Feb 86 UUCP Mail Interchange Format
StandardThis doc defines the standard format for sending mail messages between computers in the UUCP Project ๐ It does not, however, cover how messages get stored on one machine, nor the lower-level transport mechanisms used to move the data from one machine to the next. It represents a standard for conformance by hosts in the UUCP zone.
975 Mills Feb 86 Autonomous ConfederationsThis RFC proposes enhancements to the Exterior Gateway Protocol (EGP) to support a simple, multiple-level routing capability while preserving the robustness features of the current EGP model ๐ธ The enhancements generalize the concept of core system to include multiple communities of autonomous systems, called autonomous confederations. Discussion and suggestions for improvement are requested.
974 Partridge Jan 86 Mail Routing and the Domain SystemThis RFC describes how mail systems on the Internet are expected to route messages based on information from the domain system ๐ง It discusses how mailers interpret MX RRs, which are used for message routing.
973 Mockapetris Jan 86 Domain System Changes and
ObservationsThis RFC documents updates to Domain Name System specifications RFC-882 and RFC-883, suggests some operational guidelines, and discusses some experiences and problem areas in the present system ๐
972 Wancho Jan 86 Password Generator ProtocolThis RFC specifies a standard for the ARPA-Internet community. The Password Generator Service (PWDGEN) provides a set of six randomly generated eight-character "words" with a reasonable level of pronounceability, using a multi-level algorithm ๐ Hosts on the ARPA-Internet that choose to implement a password generator service are expected to adopt and implement this standard.
971 DeSchon Dec 85 A Survey of Data Representation
StandardsThis RFC is a comparison of several data representation standards that are currently in use ๐ The standards discussed are the CCITT X.409 recommendation, the NBS Computer Based Message System (CBMS) standard, DARPA Multimedia Mail system, the Courier remote procedure call protocol, and the SUN Remote Procedure Call package. No proposals in this document are intended as standards for the ARPA-Internet at this time. Instead, the hope is that a general consensus will emerge on the right approach to a data representation standard, eventually leading to the adoption of an ARPA-Internet standard.
970 Nagle Dec 85 On Packet Switches With Infinite
StorageThe purpose of this RFC is to focus discussion on one particular problem in the ARPA-Internet and possible ways to solve it ๐ Most prior work on congestion in datagram systems focuses on buffer management. This memo considers a packet switch with infinite storage. Such a packet switch can never run out of buffers, but it can still become congested, and the meaning of congestion in an infinite-storage system is explored. An unexpected result is found: a datagram network with infinite storage, first-in-first-out queuing, at least two packet switches, and a finite packet lifetime will, under overload, drop all packets ๐ญ By attacking the problem of congestion for the infinite-storage case, new solutions applicable to switches with finite storage may be found. No proposed solutions in this document are intended as standards for the ARPA-Internet at this time.
969 Clark Dec 85 NETBLT: A Bulk Data Transfer
ProtocolThis RFC has been replaced by RFC 998 ๐ซ It's a preliminary discussion of the Network Block Transfer (NETBLT) protocol. NETBLT is intended for the rapid transfer of a large quantity of data between computers. It provides a transfer that is reliable and flow controlled, and it's structured to give maximum throughput over a wide variety of networks. This description is published for discussion and comment, and does not constitute a standard. As the proposal may change, implementation of this document is not advised.
968 Cerf Dec 85 'Twas the Night Before Start-upThis memo talks about problems that pop up and debugging techniques used when bringing a new network into operation ๐
967 Padlipsky Dec 85 All Victims TogetherThis RFC proposes a new set of RFCs on how the networking code is integrated with various operating systems ๐ฅ๏ธ It seems this topic hasn't gotten enough exposure in the literature. Comments and suggestions are encouraged.
966 Deering Dec 85 A Multicast Extension to the
Internet ProtocolThis RFC defines a model of service for Internet multicasting and proposes an extension to the Internet Protocol (IP) to support such a multicast service ๐ฃ Discussion and suggestions for improvements are requested.
965 Aguilar Dec 85 A Format for a Graphical
Communication ProtocolThis RFC describes requirements for a graphical format to base a graphical on-line communication protocol on ๐จ It proposes an Interactive Graphical Communication Format using the GKSM session metafile. The hope is that this contribution encourages discussion of multimedia data exchange and proposals of solutions โจ
964 Sidhu Nov 85 Some Problems with the Specification
of the Military Standard
Transmission Control ProtocolThe purpose of this RFC is to give helpful info on the Military Standard Transmission Control Protocol (MIL-STD-1778), so that you can get a reliable implementation of this protocol standard ๐ ๏ธ This note points out three errors with the specification and also proposes solutions to these problems.
963 Sidhu Nov 85 Some Problems with the Specification
of the Military Standard Internet
ProtocolThe purpose of this RFC is to give helpful info on the Military Standard Internet Protocol (MIL-STD-1777), so that you can get a reliable implementation of this protocol ๐ This paper points out several problems in the specification. This note also proposes solutions to these problems.
962 Padlipsky Nov 85 TCP-4 PrimeThis memo is in response to Bob Braden's call for a transaction oriented protocol (RFC-955), and continues the discussion of a possible transaction oriented transport protocol. This memo does not propose a standard. ๐ฆ
961 Reynolds Dec 85 Official ARPA-Internet ProtocolsThis one's been replaced by RFC 991, so go check that one instead ๐
960 Reynolds Dec 85 Assigned NumbersAlso replaced, this time by RFCs 997 and 990 ๐ซถ
959 Postel Oct 85 File Transfer Protocol (FTP)This is the official FTP spec for the DARPA-Internet community โจ The main goal is to clarify and fix the documentation, not to change the protocol itself. It adds some new optional commands: Change to Parent Directory (CDUP), Structure Mount (SMNT), Store Unique (STOU), Remove Directory (RMD), Make Directory (MKD), Print Directory (PWD), and System (SYST). And yes, it's compatible with the previous edition, so no drama ๐ธ
958 Mills Sep 85 Network Time Protocol (NTP)NTP is giving clock synchronization queen ๐ It syncs a bunch of network clocks using a set of distributed clients and servers. It's built on UDP, which is connectionless transport. It evolved from the Time Protocol and the ICMP Timestamp message, and it's a suitable replacement for both, so those two are kinda retired now ๐ This RFC suggests a proposed protocol for the ARPA-Internet community and asks for discussion and suggestions for improvements ๐
957 Mills Sep 85 Experiments in Network Clock
SynchronizationThis one covers some clock synchronization experiments in the ARPA-Internet community, and it's also asking for feedback โจ Okay so here's the tea: a high-quality time-of-day clock that makes accurate timestamps with small errors compared to one-way network delays is something people totally ignore when designing networks ๐ It'd be super useful for tracing complex transactions, syncing cached databases, monitoring performance, and isolating problems. This memo describes one clock service design and assesses how well it performs. The design is already built into the routing and control protocols of the Distributed Computer Network (DCnet) architecture, so it's not just theory, it's real ๐ง
956 Mills Sep 85 Algorithms for Synchronizing Network
ClocksThis RFC talks about clock synchronization algorithms for the ARPA-Internet community, and again, feedback welcome ๐ Lowkey the reason everyone's suddenly obsessed with getting accurate time from a bunch of mutually suspicious network clocks is that usually reliable clock servers kept messing up after thunderstorms knocked out their power ๐ญ Add in malfunctioning hardware, buggy software, operator mistakes, and random errors in how clocks get set and synced, and yeah, it's a lot. This report proposes a stochastic model and algorithms for computing a good estimator from time-offset samples measured between clocks connected by network links. It also describes some experiments that show how well the algorithms work ๐ฅ
955 Braden Sep 85 Towards a Transport Service for
Transaction Processing ApplicationsOkay the transport layer situation is kind of a love triangle ๐ The DoD Internet Protocol Suite has two transport service protocols, TCP and UDP. TCP gives you virtual circuit service, and UDP gives you datagram service. These two sit really far apart on the list of possible transport attributes. This memo looks at an important class of applications, the ones often called "transaction processing." The communication needs of these apps land in the gap "between" TCP and UDP, and honestly neither protocol is a great fit. Main character energy for a brand new transport service ๐ฆ
954 Harrenstien Oct 85 NICNAME/WHOISThis RFC is the official spec for the NICNAME/WHOIS protocol โจ It describes both the protocol and the service. It's an update of RFC 812, and it obsoletes RFC 812, so bye bye old version ๐
953 Harrenstien Oct 85 Hostname ServerThis is the official spec for the Hostname Server Protocol ๐ This edition includes minor revisions to RFC 811 to bring it up to date. It obsoletes RFC 811 too ๐
952 Harrenstien Oct 85 DoD Internet Host Table
SpecificationThis RFC is the official spec for the format of the Internet Host Table ๐ง This edition has minor revisions to RFC 810 to bring it up to date. It obsoletes RFCs 810 and 608, so those are officially in the past now ๐
951 Croft Sep 85 Bootstrap Protocol (BOOTP)Okay this one is so cool ๐คฉ BOOTP is an IP/UDP bootstrap protocol that lets a diskless client machine figure out its own IP address, the address of a server host, and the name of a file to load into memory and run โจ The bootstrap is basically two phases. This RFC covers the first phase, which you could call address determination and bootfile selection. Once it has that address and filename info, control moves to the second phase, where a file transfer happens. That transfer will usually use TFTP, since both phases are meant to live in PROM on the client. BOOTP could also work with other protocols like SFTP or FTP though ๐ซถ This RFC suggests a proposed protocol for the ARPA-Internet community and asks for discussion and suggestions for improvements.
950 Mogul Aug 85 Internet Standard Subnetting
ProcedureThis memo is all about "subnets," which are logically visible sub-sections of a single Internet network ๐ Lots of organizations chose to split one Internet network into several subnets instead of getting a bunch of Internet network numbers, usually for admin or technical reasons. This memo specifies the procedures for using subnets. These procedures are for hosts, like workstations. The procedures used in and between subnet gateways aren't fully described here. For the important motivation and background, check out RFC-940. This RFC specifies a protocol for the ARPA-Internet community, and it's strongly recommended that you follow these procedures if you implement subnetting ๐
949 Padlipsky Jul 85 FTP Unique-Named Store CommandThere are situations where you'd want an FTP command that works like the present STOR, but instead of making you specify a file name, it gives the resulting file a unique name relative to the current directory ๐ฆ This RFC proposes that extension to the File Transfer Protocol for the ARPA-Internet community and asks for discussion and suggestions for improvements โจ
948 Winston Jun 85 Two Methods for the Transmission of
IP Datagrams Over IEEE 802.3
NetworksShort and sweet ๐ This memo describes two methods for encapsulating Internet Protocol (IP) datagrams on an IEEE 802.3 network ๐ธ
947 Lebowitz Jun 85 Multi-Network Broadcasting Within
the InternetThis RFC explains how to extend a network's broadcast domain so it covers more than one physical network, using a broadcast packet repeater ๐ง Iconic ๐
946 Nedved May 85 Telnet Terminal Location Number
OptionOkay so many systems let you find out where a user is logged in from, usually with info like telephone extensions and office occupants' names ๐ That's super handy for finding people physically or calling them. In 1982, CMU designed and built a terminal location database and changed existing network software to handle a 64-bit number called the Terminal Location Number (or TTYLOC) ๐ Now it makes sense to bring this mechanism into the TCP-based network protocol family. It's not meant to replace the Terminal Location Telnet Option (SEND-LOCATION). Instead it's a shorthand way to share terminal location info between hosts in a localized community. This RFC proposes a new Telnet option for the ARPA-Internet community and asks for discussion and suggestions for improvements ๐
945 Postel May 85 A DoD Statement on the NRC ReportOkay, backstory time ๐ In May 1983, the National Research Council (NRC) was asked by the DoD and NBS to study the issues and recommend a course of action. The NRC committee's final report came out in February 1985 (see RFC-942) ๐ This RFC reproduces a letter from the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (ASDC3I) to the Director of the Defense Communications Agency (DCA). The enclosed letter is from Donald C. Latham (ASDC3I) to DCA, and it transmits the NRC report and requests specific actions based on its recommendations. This letter is distributed for information only ๐
944 Reynolds Apr 85 Official ARPA-Internet ProtocolsReplaced by RFC 991, so that's the one to read now ๐ซถ
943 Reynolds Apr 85 Assigned NumbersReplaced by RFCs 997 and 990 โจ
942 NRC Feb 85 Transport Protocols for Department
of Defense Data NetworksThis RFC reproduces the National Research Council report from a study of the DoD Internet Protocol (IP) and Transmission Control Protocol (TCP). The study compares them with the ISO Internet Protocol (ISO-IP) and Transport Protocol level 4 (TP-4) ๐ง It's basically a big showdown ๐
941 ISO Apr 85 Addendum to the Network Service
Definition Covering Network Layer
AddressingThis addendum to the Network Service Definition Standard, ISO 8348, defines the abstract syntax and semantics of the Network Address (Network Service Access Point Address) ๐ธ The Network Address here is the address that shows up in the primitives of the connection-mode Network Service as the calling address, called address, and responding address parameters. It also shows up in the primitives of the connectionless-mode Network Service as the source address and destination address parameters ๐ค
This document is distributed as an RFC for information only. It does not specify a standard for the ARPA-Internet ๐
RFC 940 โจ Toward an Internet Standard Scheme for Subnetting
940 GADS Apr 85 Toward an Internet Standard Scheme
for Subnettingokay so picture a bunch of local links hanging off the Internet through one gateway ๐ธ the inside stuff is honestly none of the rest of the Internet's business. one way to organize all that is to copy what the Internet already does for networks: treat each link as its own entity (like a network) and connect the links with routing devices (like gateways). this is called subnetting ๐ฆ the links are subnets and the connecting devices are subgateways (or bridges, or gateways, depending on who you ask ๐ ). this RFC is about standardizing the protocol used in subnetted setups on the ARPA-Internet. distribution is unlimited ๐ the author is the Gateway Algorithms and Data Structures (GADS) Task Force, chaired by David L. Mills ๐
RFC 939 ๐ Executive Summary of the NRC Report on Transport Protocols for Department of Defense Data Networks
939 NRC Feb 85 Executive Summary of the NRC Report
on Transport Protocols for
Department of Defense Data Networksthis one is a reprint of the "front pages" of a National Research Council report ๐ the report compared the DOD Internet Protocol (IP) and Transmission Control Protocol (TCP) with the ISO Internet Protocol (ISO-IP) and Transport Protocol level 4 (TP-4). the whole point is just getting the Executive Summary out there quickly ๐โโ๏ธโจ the order of presentation got shuffled and the pagination changed, so heads up ๐
RFC 938 ๐ Internet Reliable Transaction Protocol Functional and Interface Specification
938 Miller Feb 85 Internet Reliable Transaction
Protocol Functional and Interface
Specificationthis one went out to the DARPA research community to collect reactions to the proposals inside ๐ซถ the topics might not be directly relevant to what the DARPA folks are working on, but plenty of researchers and implementors might find them interesting. it suggests a proposed protocol for the ARPA-Internet community and asks for discussion and ideas for improvements ๐
RFC 937 ๐ฆ Post Office Protocol - Version 2
937 Reynolds Feb 85 Post Office Protocol - Version 2this is giving "simple and effective" ๐ it suggests a straightforward way for workstations to grab mail from a mailbox server whenever they need it ๐ฌ it's a proposed protocol for the ARPA-Internet community, so discussion and improvement suggestions are very welcome โจ and yes, this memo revises RFC 918 ๐
RFC 936 ๐ธ Another Internet Subnet Addressing Scheme
936 Karels Feb 85 Another Internet Subnet Addressing
Schemeokay this one is a whole mood ๐ฅน there have been a bunch of ideas for letting one Internet network number stand in for a group of physical networks under the same administration, all reachable from outside by a common route. the upside is that hosts and gateways outside the group see a simplified view of what would otherwise be a messy topology. the number and type of those networks, plus the routing to them, stay local ๐ก so changes in configuration don't cause any detectable change or service interruption, since routing and other info doesn't have to slowly propagate outside the local environment ๐ซง admins win too, because adding a new cable doesn't mean allocating a new network number every time ๐
this proposal is the alternative scheme, one that's been in use at the University of California, Berkeley since April 1984 ๐ it's a proposed protocol for the ARPA-Internet community, so yes, discussion and suggestions are requested ๐
RFC 935 ๐ Reliable Link Layer Protocols
935 Robinson Jan 85 Reliable Link Layer Protocolsthis one talks about protocols proposed in RFCs 914 and 916 and suggests a new one that could meet the same needs ๐ง the need is reliable communication between two programs over a full-duplex, point-to-point link, especially over an asynchronous link at relatively low speeds. the suggested protocol borrows methods from existing national and international data link layer standards ๐ง it's another proposed protocol for the ARPA-Internet community, with the usual request for discussion and improvements โจ
RFC 934 ๐ Proposed Standard for Message Encapsulation
934 Rose Jan 85 Proposed Standard for Message
Encapsulationthis memo is all about message forwarding, which you can think of as wrapping one or more messages inside another ๐ forwarding old correspondence to new people is handy, but without bursting (the decapsulation process) the forwarded messages are kind of useless, since recipients can't distribute, forward, reply to, or otherwise handle them as separate messages ๐ญ to burst a message you have to know how the component messages were encapsulated in the draft. and rn there's no unambiguous standard for interest group digests ๐ this RFC proposes a proposed protocol for the ARPA-Internet community and asks for discussion and suggestions for improvements ๐ซถ
RFC 933 ๐ Output Marking Telnet Option
933 Silverman Jan 85 Output Marking Telnet Optionthis proposed option would let a Server-Telnet send a banner to a User-Telnet, so the banner shows up on the workstation screen no matter what application is running on the Server-Telnet ๐ฅ๏ธโจ very main character energy for banners, ngl ๐
RFC 932 ๐ฆ A Subnetwork Addressing Scheme
932 Clark Jan 85 A Subnetwork Addressing Schemethis RFC proposes another addressing scheme for subnets ๐ท the big selling point is that in most cases it needs no modification to host software whatsoever ๐ the drawbacks: the total number of subnets in any one network is limited, and every gateway has to be modified ๐ฌ
RFC 931 ๐ Authentication Server
931 StJohns Jan 85 Authentication Serverthis one suggests a proposed protocol for the ARPA-Internet community and asks for discussion and suggestions for improvement ๐ this is the second draft of the proposal (it supersedes RFC 912) and it's more formal about the syntax of the request and response dialog ๐ it also changes things so the type of user identification returned is specified ๐ชช
RFC 930 ๐ Telnet Terminal Type Option
930 Solomon Jan 85 Telnet Terminal Type Optionthis RFC specifies a standard for the ARPA-Internet community ๐ hosts that exchange terminal type info within Telnet are expected to adopt and implement it. distribution is unlimited ๐ this standard supersedes RFC 884, and the only change is that the TERMINAL-TYPE IS sub-negotiation should be sent only in response to the TERMINAL-TYPE SEND sub-negotiation ๐ฏ very specific, very iconic ๐ค
RFC 929 ๐ธ Proposed Host-Front End Protocol
929 Lilienkamp Dec 84 Proposed Host-Front End Protocolthis memo describes in detail the Host-Front End Protocol that RFC 928 introduced ๐ first order of business: THIS IS A PROPOSAL, NOT A FINAL STANDARD ๐จ second order of business: anyone reading who can do test implementations, please (a) do it and (b) coordinate with the author ๐ค it's a proposed protocol for the ARPA-Internet community, so discussion and improvements are requested ๐
RFC 928 ๐ง Introduction to Proposed DOD Standard H-FP
928 Padlipsky Dec 84 Introduction to Proposed DOD
Standard H-FPthe broad outline of the Host-Front End Protocol (H-FP) here, which RFC 929 covers in detail, came out of a committee of experienced H-FP designers who sat as part of the DoD Protocol Standards Technical Panel ๐๏ธ the designers want the protocol to get multiple test implementations and probably some iteration before anyone agrees on it as any sort of "standard" ๐ so, again: THIS IS A PROPOSAL, NOT A FINAL STANDARD ๐ readers who can do test implementations, please (a) do and (b) coordinate with the author ๐ it's a proposed protocol for the ARPA-Internet community, with discussion and suggestions welcome โจ
RFC 927 ๐ TACACS User Identification Telnet Option
927 Anderson Dec 84 TACACS User Identification Telnet
Optionthis is a Telnet option built to help avoid double login ๐ โโ๏ธ๐ it's mainly meant for TAC connections to target hosts on behalf of TAC users, but any two consenting hosts can use it. for example, all the hosts at one site (like BBN) could use it so you don't have to log in twice when TELNETing to each other ๐ it suggests a proposed protocol for the ARPA-Internet community and asks for discussion and suggestions for improvements ๐
RFC 926 ๐ Protocol for Providing the Connectionless-Mode Network Services
926 ISO Dec 84 Protocol for Providing the
Connectionless-Mode Network Servicesthis note is a draft ISO protocol that's roughly similar to the DoD Internet Protocol ๐ it was made by retyping the text of ISO DIS 8473 of May 1984, which was going through voting within ISO as a Draft International Standard (DIS) at the time ๐ณ๏ธ this document is distributed as an RFC for information only, and it does not specify a standard for the ARPA-Internet ๐ซถ
RFC 925 ๐ธ Multi-LAN Address Resolution
925 Postel Oct 84 Multi-LAN Address Resolutiontreating a set of local area networks (LANs) as one Internet network has gotten people interested and a bit worried ๐ฌ it's not OK to give each LAN at a site its own ARPA-Internet network number, and it would be nice to hide the interconnection details from people, gateways, and hosts outside the site ๐ in RFC 917, Jeffery Mogul argues for "explicit subnets" in a multi-LAN setup, which basically means recursively applying the same mechanisms the ARPA-Internet uses to manage networks to managing LANs inside one network ๐ this note urges a different approach: "transparent subnets" supported by a multi-LAN extension of the Address Resolution Protocol ๐ฆ it's a proposed protocol for the ARPA-Internet community, so discussion and suggestions are requested ๐
RFC 924 ๐ซง Official ARPA-Internet Protocols
924 Reynolds Oct 84 Official ARPA-Internet Protocolsthis RFC has been replaced by RFC 991 ๐ bye bye, 924 ๐
RFC 923 ๐ข Assigned Numbers
923 Reynolds Oct 84 Assigned Numbersthis RFC has been replaced by RFCs 997 and 990 ๐ two replacements, we're eating well today ๐
RFC 922 ๐ Broadcasting Internet Datagrams in the Presence of Subnets
922 Mogul Oct 84 Broadcasting Internet Datagrams in
the Presence of SubnetsOkay bestie, the broadcast rules keep going ๐ก We're proposing simple rules for sending Internet datagrams on local networks that actually support broadcast, for how broadcast addresses get written, and for how gateways should handle them ๐ This RFC suggests a proposed protocol for the ARPA-Internet community and literally begs everyone for discussion and suggestions for improvements ๐ซถ
921 Postel Oct 84 Domain Name System Implementation
Schedule - RevisedOkay, so this memo is a policy statement about rolling out the Domain Style Naming System across the ARPA-Internet ๐ธ It's an update of RFC 881 and RFC 897. It's an official policy statement from the IAB and the DARPA. The whole point is to lay out the implementation schedule. How the system actually works? That's in the references, so go check there ๐ง
920 Postel Oct 84 Domain RequirementsThis memo lays out the requirements for setting up a Domain and introduces the limited set of top level domains ๐ It's a policy statement on what you need to establish a new domain in the ARPA-Internet and the DARPA research community. Also an official policy statement from the IAB and the DARPA, so it's serious business ๐
919 Mogul Oct 84 Broadcasting Internet DatagramsThis RFC proposes simple rules for broadcasting Internet datagrams on local networks that support broadcast, for addressing broadcasts, and for how gateways should handle them โจ It suggests a proposed protocol for the ARPA-Internet community and asks for discussion and suggestions for improvements ๐
918 Reynolds Oct 84 Post Office Protocol (POP)Updated by RFC 937. ๐
917 Mogul Oct 84 Internet SubnetsLowkey one of my faves ๐ฆ This memo talks about subnets and proposes how to use them, including ways to solve the problems that pop up, especially routing ("routing is the actual boss" energy ๐ ). A subnet is a logically visible sub-section of a single Internet network. For administrative or technical reasons, lots of organizations split one Internet network into several subnets instead of getting a whole set of Internet network numbers ๐ This RFC suggests a proposed protocol for the ARPA-Internet community and requests discussion and suggestions for improvements ๐ซถ
916 Finn Oct 84 Reliable Asynchronous Transfer
Protocol (RATP)This paper proposes and specifies a protocol that lets two programs talk to each other reliably over a communication link ๐ฅ It makes sure that data going in one end of the link, if received, comes out the other end intact and unaltered. The protocol, called RATP, is built to run over a full duplex point-to-point connection, and it has some features that are tailored to the RS-232 links everyone's using right now ๐ง This RFC suggests a proposed protocol for the ARPA-Internet community and requests discussion and suggestions for improvements ๐
915 Elvy Dec 84 Network Mail Path ServiceThe network mail path service is giving exactly what people need ๐ธ It helps you find mailbox addresses for hosts that aren't part of the ARPA-Internet but can still be reached through one or more relay hosts with Unix to Unix Copy (UUCP) mail, CSNET mail, MAILNET mail, BITNET mail, and so on. Anyone can use it as long as they have TCP/TELENET to one of the hosts with a mail path server ๐ฌ This RFC proposes a new service for the ARPA-Internet community and requests discussion and suggestions for improvements โจ
914 Farber Sep 84 A Thinwire ProtocolThis document focuses the discussion on the specific problems of low speed network interconnection with personal computers in the ARPA-Internet, plus possible ways to solve them ๐ None of the proposed solutions here are meant to be standards for the ARPA-Internet. The hope is that a general consensus forms about the right solution, which could eventually lead to standards being adopted ๐ซถ
913 Lottor Sep 84 Simple File Transfer ProtocolThis memo describes a proposed Simple File Transfer Protocol (SFTP) ๐ It's for people who want something more useful than TFTP but easier to implement (and less powerful) than FTP. SFTP supports user access control, file transfers, directory listing, directory changing, file renaming, and deleting ๐ Discussion is encouraged, and suggestions for improvements may be sent to the author ๐
912 StJohns Sep 84 Authentication ServiceThis memo describes a proposed authentication protocol for verifying the identity of a user of a TCP connection ๐ Given a TCP port number pair, it returns a character string that identifies the owner of that connection on the server's system. Suggested uses include automatic identification and verification of a user during an FTP session, extra verification for a TAC dial up user, and access verification for a generalized network file server ๐
911 Kirton Aug 84 EGP Gateway under Berkeley Unix 4.2This memo describes an implementation of the Exterior Gateway Protocol (EGP). In that sense it's a status report ๐ It also talks about some possible extensions and some design issues, so in that sense it's an invitation for further discussion ๐ฆ
910 Forsdick Aug 84 Multimedia Mail Meeting NotesThis memo is a report on a meeting about the experimental multimedia mail system, and kind of a status report on that experiment too ๐๏ธ The meeting was held at Bolt Beranek and Newman on 23-24 July 1984 to discuss recent progress by groups building multimedia mail systems and to talk through a bunch of issues for the future of multimedia systems ๐ Representatives came from BBN, ISI, SRI and Linkabit. Distribution of this memo is unlimited ๐
909 Welles Jul 84 Loader Debugger ProtocolThe Loader Debugger Protocol (LDP) is an application layer protocol for loading, dumping, and debugging target machines from hosts in a network environment ๐ ๏ธ This RFC specifies a proposed protocol for the ARPA-Internet and DARPA research community, and requests discussion and suggestions for improvements ๐ซถ
908 Velten Jul 84 Reliable Data ProtocolThe Reliable Data Protocol (RDP) is designed to give packet-based applications a reliable data transport service ๐ This RFC specifies a proposed protocol for the ARPA-Internet and DARPA research community, and requests discussion and suggestions for improvements โจ
907 Storch Jul 84 Host Access Protocol SpecificationThis document specifies the Host Access Protocol (HAP) ๐ฐ๏ธ HAP was first designed as the network-access level protocol for the DARPA/DCA sponsored Wideband Packet Satellite Network. The plan is for it to evolve into a standard interface for SATNET and TACNET (aka MATNET), as well as the Wideband Network. HAP is an experimental protocol and will go through more revisions as new capabilities get added and/or different satellite networks get supported ๐ฅ Anyone implementing HAP should coordinate with satellite network development and operations personnel ๐
906 Finlayson Jun 84 Bootstrap Loading Using TFTPIt's often super convenient to be able to bootstrap a computer system from a communications network ๐ธ This RFC proposes using the IP/TFTP protocol for bootstrap loading in that case ๐
905 ISO Apr 84 ISO Transport Protocol Specification
(ISO DP 8073)This is the current specification of the ISO Transport Protocol ๐ง This document is the text of ISO/TC97/SC16/N1576 as corrected by ISO/TC97/SC16/N1695. It's the specification being voted on in ISO as a Draft International Standard (DIS). This document is distributed as an RFC for your information only. It does not specify a standard for the ARPA-Internet or DARPA research community ๐ Huge thanks to Alex McKenzie of BBN for making this online version available. And please note the size, because the file contains 258,729 characters ๐ญ
904 Mills Apr 84 Exterior Gateway Protocol Formal
SpecificationThis is the specification of the Exterior Gateway Protocol (EGP) ๐ This memo updates portions of RFC 888 and RFC 827. This RFC specifies an official protocol of the DARPA community for use between gateways of different autonomous systems in the ARPA-Internet ๐ซถ
903 Finlayson Jun 84 A Reverse Address Resolution
ProtocolThis RFC suggests a method for workstations to dynamically find their protocol address (e.g., their Internet Address) when they only know their hardware address (e.g., their attached physical network address) ๐คฏ This RFC specifies a proposed protocol for the ARPA-Internet community and requests discussion and suggestions for improvement ๐
902 Postel Jul 84 ARPA-Internet Protocol PolicyThe purpose of this memo is to explain how protocol standards get adopted for the ARPA-Internet and the DARPA research community ๐ There are three big aspects: the process, the authority, and the complicated relationship between the DARPA community and the DDN community. This memo is a policy statement on how protocols become official standards for the ARPA-Internet and the DARPA research community. It's an official policy statement from the ICCB and the DARPA ๐
901 Reynolds Jun 84 Official ARPA-Internet ProtocolsThis RFC has been replaced by RFC 991. ๐
900 Reynolds Jun 84 Assigned NumbersThis RFC has been replaced by RFCs 997 and 990. ๐
899 Postel Apr 84 Requests For Comments SummaryA summary of the Request for Comments documents from RFC 800-898 ๐
898 Hinden Apr 84 Gateway Special Interest Group
Meeting NotesThis memo is a report on the Gateway Special Interest Group Meeting that was held at ISI on 28 and 29 February 1984 ๐ Robert Hinden of BBNCC chaired, and Jon Postel of ISI hosted. Approximately 35 gateway designers and implementors attended ๐ These notes are based on the recollections of Jon Postel and Mike Muuss. Under each topic area are Jon Postel's brief notes, plus additional details from Mike Muuss. This memo is a report on the meeting. No conclusions, decisions, or policy statements are documented in this note ๐
897 Postel Feb 84 Domain Name System Implementation
ScheduleThis memo is a policy statement on the implementation of the Domain Style Naming System in the ARPA-Internet. It's a partial update of RFC 881. The goal is to lay out the schedule for moving to Domain style names, which will replace the old host names. Hosts will start using Domain style names on 14-Mar-84, and old style names will be completely phased out before 2-May-84. This applies to both the ARPA research hosts and the DDN operational hosts. It's an official policy statement of the ICCB and the DARPA. ๐ธ๐ โจ
896 Nagle Jan 84 Congestion Control in IP/TCP
InternetworksThis memo talks about some aspects of congestion control in IP/TCP Internetworks. It's meant to spark thought and further discussion on the topic. It makes some specific suggestions for better congestion control implementations, but it does not specify any standards. Think of it as a brainstorm, not a rulebook. ๐ง ๐ญ๐ฆ
895 Postel Apr 84 A Standard for the Transmission of
IP Datagrams over Experimental
Ethernet NetworksThis RFC specifies a standard way to encapsulate Internet Protocol (IP) datagrams on an Experimental Ethernet. It's a standard protocol for the ARPA-Internet community. Iconic behavior, honestly. ๐๐
894 Hornig Apr 84 A Standard for the Transmission of
IP Datagrams over Ethernet NetworksThis RFC specifies a standard way to encapsulate Internet Protocol (IP) datagrams on an Ethernet. It's also a standard protocol for the ARPA-Internet community. It's basically the sibling of 895, but for regular Ethernet. Sisters, okay ๐ซถ๐
893 Leffler Apr 84 Trailer EncapsulationsThis RFC talks about why "trailer encapsulations" are used on local-area networks and describes how that encapsulation is implemented on various media. It's for information only. It is NOT an official protocol for the ARPA-Internet community, so don't go treating it like one ๐๐
892 ISO Dec 83 ISO Transport Protocol SpecificationThis is a draft version of the transport protocol that ISO was standardizing. It also appeared in the ACM SIGCOMM Computer Communication Review (V.12, N.3-4) July-October 1982. This version is now out of date, so it's a historical moment, not the current spec. ๐ฐ๏ธ๐
891 Mills Dec 83 DCN Local-Network ProtocolsThis RFC describes the DCN protocols for keeping connectivity, routing, and clock information in a local network. Designers and implementers of other local networks might find these procedures interesting. Literally a masterclass ๐โฐ
890 Postel Feb 84 Exterior Gateway Protocol
Implementation ScheduleThis memo is a policy statement on the implementation of the Exterior Gateway Protocol (EGP) in the ARPA-Internet. It's an official policy statement of ICCB and DARPA. After 1-Aug-84 there shall be no dumb gateways in the Internet. Every gateway must be a member of some autonomous system. Each autonomous system must have some gateway that exchanges routing information with some gateway of the core autonomous system using the Exterior Gateway Protocol. The no-dumb-gateways era is coming, bestie ๐๐ช
889 Mills Dec 83 Internet Delay ExperimentsThis memo reports on some measurements of round-trip times in the Internet. It suggests some possible improvements to the TCP retransmission timeout calculation. It's both a status report on the ARPA-Internet and advice to TCP implementers. Data and vibes together ๐โฑ๏ธโจ
888 Seamonson Jan 84 "Stub" Exterior Gateway ProtocolThis RFC describes the Exterior Gateway Protocol (EGP) used to connect Stub Gateways to an Autonomous System of core Gateways. It specifies the working protocol and defines an ARPA official protocol. All implementers of Gateways should carefully review this document. Please read it, I'm begging you ๐ฅบ๐ฅ
887 Accetta Dec 83 Resource Location ProtocolThis RFC specifies a draft standard for the ARPA-Internet community. It describes a resource location protocol for use in the ARPA-Internet. It's most useful on networks that support some method of broadcast addressing, but it can also be used on other types of networks. For maximum benefit, all hosts that provide significant resources or services to other hosts on the ARPA-Internet should implement this protocol. Hosts that don't implement the Resource Location Protocol risk being ignored by other hosts trying to locate resources on the ARPA-Internet. Ghosted by the network, not it ๐๐
886 Rose Dec 83 Proposed Standard for Message Header
MungingThis RFC specifies a draft standard for the ARPA-Internet community. It describes the rules for transforming mail from the conventions of one message system to those of another. In particular, it specifies the treatment of header fields and recipient addresses. Message header makeovers, but make it a protocol ๐โจ
885 Postel Dec 83 Telnet End of Record OptionThis RFC specifies a standard for the ARPA-Internet community. It describes a method for marking the end of records in data transmitted on Telnet connections. Marking the end, periodt ๐๐ธ
884 Solomon Dec 83 Telnet Terminal Type OptionThis RFC specifies a standard for the ARPA-Internet community. It describes a method for exchanging terminal type information in the Telnet protocol. Terminal type swaps, the way that they're organized ๐ป๐
883 Mockapetris Nov 83 Domain Names - Implementation and
SpecificationThis RFC discusses how domain name servers and resolvers are implemented. It specifies the format of transactions and discusses the use of domain names in the context of existing mail systems and other network software. This one is giving implementation deep dive, and I'm obsessed ๐ง๐ฌ
882 Mockapetris Nov 83 Domain Names - Concepts and
FacilitiesThis RFC introduces domain style names, how they're used for DDN/ARPA-Internet mail and host address support, and the protocol and servers used to implement domain name facilities. The concepts piece that sets up 883. Start here, bestie ๐๐บ๏ธ
881 Postel Nov 83 The Domain Names Plan and ScheduleThis RFC outlines a plan and schedule for implementing domain style names throughout the DDN/ARPA-Internet community. The introduction of domain style names will impact all hosts on the DDN/ARPA-Internet. Okay, the whole network is about to glow up ๐๐
880 Reynolds Oct 83 Official ProtocolsThis RFC has been replaced by RFC 991. Retired, but still iconic ๐
879 Postel Nov 83 The TCP Maximum Segment Size and
Related TopicsThis RFC discusses the TCP Maximum Segment Size Option and related topics. The purpose is to clarify some aspects of TCP and how it interacts with IP. This memo is a clarification to the TCP specification, and it contains information that may be considered "advice to implementers." Clarity queen behavior ๐ ๐ซง
878 Malis Dec 83 The ARPANET 1822L Host Access
ProtocolThis RFC specifies the ARPANET 1822L Host Access Protocol, which is a successor to the existing 1822 Host Access Protocol. The 1822L procedure lets ARPANET hosts use logical identifiers as well as 1822 physical interface identifiers to address each other. Logical names AND physical IDs, both allowed, no drama ๐ฆ๐ฐ๏ธ
877 Korb Sep 83 A Standard for the Transmission of
IP Datagrams Over Public Data
NetworksThis RFC specifies a standard adopted by CSNET, the VAN gateway, and other organizations for transmitting IP datagrams over the X.25-based public data networks. Multiple orgs agreeing on one standard? That's main character energy ๐ค๐
876 Smallberg Sep 83 Survey of SMTP ImplementationsThis RFC is a survey of implementation status. It doesn't specify an official protocol. Instead, it notes the status of implementation of aspects of a protocol. The status of the hosts reported on is expected to change. This information must be treated as a snapshot of the state of these implemetations. Snapshot energy, so don't treat it as forever ๐ธโณ
875 Padlipsky Sep 82 Gateways, Architectures, and
HeffalumpsThis RFC is a discussion of the role of gateways in an internetwork, especially the problems of translating or mapping protocols between different protocol suites. The discussion notes possible functionality mismatches, undesirable routing "singularity points," flow control issues, and the high cost of translating gateways. Originally published as M82-51 by the MITRE Corporation, Bedford, Massachusetts. Heffalumps have never been more relevant ๐งธ๐
874 Padlipsky Sep 82 A Critique of X.25This RFC is an analysis of X.25 that points out some problems in its conceptual model, particularly the conflict between the interface aspects and the end-to-end aspects. The memo also touches on security and implementation issues. Originally published as M82-50 by the MITRE Corporation, Bedford, Massachusetts. Honest critique, no filter ๐๐
873 Padlipsky Sep 82 The Illusion of Vendor SupportThis memo takes issue with the claim that international standards in computer protocols currently provide a basis for low-cost, vendor-supported protocol implementations. Originally published as M82-49 by the MITRE Corporation, Bedford, Massachusetts. Calling out the hype, iykyk ๐ โโ๏ธ๐ซ
872 Padlipsky Sep 82 TCP-ON-A-LANThis memo attacks the notion that TCP cannot be appropriate for use on a Local Area Network. Originally published as M82-48 by the MITRE Corporation, Bedford Massachusetts. Spicy take, and it slaps ๐ถ๏ธ๐
871 Padlipsky Sep 82 A Perspective on the Arpanet
Reference ModelThis RFC is mainly a perspective on the ARM. It points out some differences between the ARM and the ISORM, which members expressed in NWG general meetings, NWG protocol design committee meetings, the ARPA-Internet Working Group, and private conversations over the intervening years. Originally published as M82-47 by the MITRE Corporation, Bedford, Massachusetts. Old-school receipts, lowkey iconic ๐๐
870 Reynolds Oct 83 Assigned NumbersThis RFC has been replaced by RFCs 997 and 990. Passing the torch, no cap ๐ฏ๏ธ
869 Hinden Dec 83 A Host Monitoring ProtocolThis RFC specifies the Host Monitoring Protocol, which is used to collect information from various types of hosts in the Internet. Designers of Internet communications software are encouraged to consider this protocol as a way to monitor how their creations behave. Watch your babies, fr fr ๐๐
868 Postel May 83 Time ProtocolThis RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet that choose to implement a Time Protocol are expected to adopt and implement this standard. The protocol provides a site-independent, machine-readable date and time. The Time service sends back to the originating source the time in seconds since midnight on January first 1900. Time, but make it 1900 โฐ๐ง
867 Postel May 83 Daytime ProtocolThis RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet that choose to implement a Daytime Protocol are expected to adopt and implement this standard. The Daytime service simply sends the current date and time as a character string, without regard to the input. Simple, clean, and honestly so slay ๐ธโ๏ธ
866 ยท Postel ยท May 83 ยท Active Users ๐ Okay bestie, this one is giving a standard for the ARPA-Internet community! ๐ Hosts on the ARPA-Internet that choose to implement an Active Users Protocol are expected to adopt and implement this standard. The Active Users service just sends back a list of the currently active users on the host, no matter what input it gets ๐
865 ยท Postel ยท May 83 ยท Quote of the Day Protocol ๐ธ This one is a standard for the ARPA-Internet community too โจ Hosts that choose to implement a Quote of the Day Protocol are expected to adopt and implement this standard. The Quote of the Day service simply sends a short message, ignoring whatever input it gets ๐ซถ
864 ยท Postel ยท May 83 ยท Character Generator Protocol ๐ฆ Same energy: a standard for the ARPA-Internet community ๐ Hosts that choose to implement a Character Generator Protocol are expected to adopt and implement this standard. The Character Generator service simply sends data without regard to the input ๐ฅ
863 ยท Postel ยท May 83 ยท Discard Protocol ๐ Standard for the ARPA-Internet community, obviously ๐ Hosts that choose to implement a Discard Protocol are expected to adopt and implement this standard. The Discard service simply throws away any data it receives. Iconic, honestly ๐
862 ยท Postel ยท May 83 ยท Echo Protocol ๐ง A standard for the ARPA-Internet community โจ Hosts that choose to implement a Echo Protocol are expected to adopt and implement this standard. The Echo service simply sends back to the originating source any data it receives. It's giving mirror, bestie ๐ช
861 ยท Postel ยท May 83 ยท Telnet Extended Options - List Option ๐ This is a Telnet Option, and it provides a mechanism for extending the set of possible options ๐ This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet are expected to adopt and implement this standard. Obsoletes NIC 16239. ๐
860 ยท Postel ยท May 83 ยท Telnet Timing Mark Option โฑ๏ธ Another Telnet Option! โจ This one provides a way to check the roundtrip path between two Telnet modules. This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet are expected to adopt and implement this standard. Obsoletes NIC 16238. ๐
859 ยท Postel ยท May 83 ยท Telnet Status Option ๐ This Telnet Option provides a way to figure out the other Telnet module's view of the status of options ๐ซถ This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet are expected to adopt and implement this standard. Obsoletes RFC 651 (NIC 31154). ๐ธ
858 ยท Postel ยท May 83 ยท Telnet Suppress Go Ahead Option ๐ฆ This Telnet Option disables the exchange of go-ahead signals between the Telnet modules, which is lowkey iconic ๐ This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet are expected to adopt and implement this standard. Obsoletes NIC 15392. โจ
857 ยท Postel ยท May 83 ยท Telnet Echo Option ๐ This Telnet Option enables remote echoing by the other Telnet module ๐ฅ This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet are expected to adopt and implement this standard. Obsoletes NIC 15390. ๐
856 ยท Postel ยท May 83 ยท Telnet Binary Transmission ๐ This Telnet Option turns on a binary data mode between the Telnet modules ๐ This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet are expected to adopt and implement this standard. Obsoletes NIC 15389. ๐ซถ
855 ยท Postel ยท May 83 ยท Telnet Option Specifications ๐ This memo lays out the general form for Telnet options and the directions for how to specify them, so it's basically the rulebook ๐ This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet are expected to adopt and implement this standard. Obsoletes RFC 651, NIC 18640. โจ
854 ยท Postel ยท May 83 ยท Telnet Protocol Specifications ๐ Okay, this is the main event ๐ญ It's the specification of the Telnet protocol used for remote terminal access in the ARPA-Internet. The purpose of Telnet is to provide a fairly general, bi-directional, eight-bit byte oriented communications facility. Its primary goal is to allow a standard way of hooking up terminal devices and terminal-oriented processes to each other. The protocol may also be used for terminal-terminal communication ("linking") and process-process communication (distributed computation), which is very main character energy ๐ This RFC specifies a standard for the ARPA-Internet community. Hosts on the ARPA-Internet are expected to adopt and implement this standard. Obsoletes NIC 18639. ๐ฆ
853 ยท Never Issued. ๐ Yep, 853 never got issued, so it's just a gap in the numbering ๐
852 ยท Malis ยท Apr 83 ยท The ARPANET Short Blocking Feature ๐ง This RFC specifies the ARPANET Short Blocking Feature, which lets ARPANET hosts optionally shorten the IMP's host blocking timer โจ This Feature replaces the ARPANET non-blocking host interface, which was never implemented, and it's available to hosts using either the 1822 or 1822L Host Access Protocol. This RFC is also presented as a solicitation of comments on the Short Blocking Feature, especially from host network software implementers and maintainers. Your input is literally wanted, bestie ๐ซถ
851 ยท Malis ยท Apr 83 ยท The ARPANET 1822L Host Access Protocol ๐ This RFC specifies the ARPANET 1822L Host Access Protocol, which is a successor to the existing 1822 Host Access Protocol ๐ฅ 1822L lets ARPANET hosts use logical names as well as 1822's physical port locations to address each other, which is so cute ๐ This RFC is also presented as a solicitation of comments on 1822L, especially from host network software implementers and maintainers. Obsoletes RFC 802. ๐ธ
850 ยท Horton ยท Jun 83 ยท Standard for Interchange of USENET Messages ๐ฎ Real talk, this memo is distributed as an RFC only so researchers in the ARPA-Internet community can easily access the info ๐ It does not specify an Internet standard. What it does do is define the standard format for interchanging Network News articles among USENET sites โจ It describes the format for the articles themselves and gives partial standards for transmission of news. Transmission isn't fully standardized, so hosts get a good deal of flexibility to choose their transmission hardware and software, and whether to batch news and so on ๐
849 ยท Crispin ยท May 83 ยท Suggestions for Improved Host Table Distribution ๐๏ธ This RFC is actually a request for comments ๐ The issue is a naming registry update procedure, both as it exists now and what could exist in the future. None of the proposed solutions are intended as standards at this time. Instead, the hope is that a general consensus will emerge as the appropriate solution, which could eventually lead to standards ๐ฆ
848 ยท Smallberg ยท Mar 83 ยท Who provides the "Little" TCP Services? ๐ต๏ธโโ๏ธ This RFC lists the hosts that provide any of these "little" TCP services ๐ The host list was taken from the NIC hostname table of 24-Feb-83. The tests were run on February 23 and 24, and March 3 and 5 from ISI-VAXA.ARPA. Detective era, honestly โจ
847 ยท Westine ยท Feb 83 ยท Summary of Smallberg Surveys ๐ This is a summary of the surveys of Telnet, FTP and Mail (SMTP) servers that David Smallberg ran in December 1982, January and February 1983, as reported in RFC 832-843, 845-846 ๐ This memo pulls out the number of hosts that accepted the connection to their server for each of Telnet, FTP, and SMTP, and compares it to the total host count in the ARPA-Internet (not counting TACs or ECHOS). The math is giving ๐งฎ
846 ยท Smallberg ยท Feb 83 ยท Who Talks TCP? -- Survey of 22 February 1983 ๐ธ This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP ๐ซถ The host list was taken from the NIC hostname table of 18-Feb-83. The tests were run on 22-Feb-83 from ISI-VAXA.ARPA. ๐
845 ยท Smallberg ยท Feb 83 ยท Who Talks TCP? -- Survey of 15 February 1983 ๐ Same vibe: a survey of hosts checking the implementation status of Telnet, FTP, and Mail on TCP ๐ The host list was taken from the NIC hostname table of 3-Feb-83. The tests were run on 15-Feb-83 from ISI-VAXA.ARPA. โจ
844 ยท Clements ยท Feb 83 ยท Who Talks ICMP, too? Survey of 18 February 1983 ๐ฆ This survey figures out how many hosts can respond to Telnet connections from a user at a class C site ๐ That requires, in addition to IP and TCP, taking part in gateway routing via ICMP and handling Class C addresses ๐ฅ The host list was taken from RFC 843, keeping only the hosts listed there as accepting Telnet connections. The tests were run on 18-Feb-83. ๐
843 ยท Smallberg ยท Feb 83 ยท Who Talks TCP? -- Survey of 8 February 1983 ๐ง This RFC is a survey of hosts checking the implementation status of Telnet, FTP, and Mail on TCP ๐ซถ The host list was taken from the NIC hostname table of 3-Feb-83. The tests were run on 8-Feb-83 and on 9-Feb-83 from ISI-VAXA.ARPA. ๐ธ
842 ยท Smallberg ยท Feb 83 ยท Who Talks TCP? -- Survey of 1 February 1983 ๐ Another survey of hosts looking at the implementation status of Telnet, FTP, and Mail on TCP โจ The host list was taken from the NIC hostname table of 28-Jan-83. The tests were run on 1-Feb-83 and on 2-Feb-83 ISI-VAXA.ARPA. ๐
841 ยท FIPS PUB 98 ยท Jan 83 ยท Specification for Message Format for Computer Based Message Systems ๐จ This RFC is FIPS 98 ๐ The point of distributing it as an RFC is to make it easily accessible to the ARPA research community. This RFC does not specify a standard for the ARPA-Internet. Obsoletes RFC 806. ๐ฆ
840 ยท Postel ยท Apr 83 ยท Official Protocols ๐ Plot twist: this RFC has been replaced by RFC 991 ๐
839 ยท Smallberg ยท Jan 83 ยท Who Talks TCP? ๐ This RFC is a survey of hosts checking the implementation status of Telnet, FTP, and Mail on TCP ๐ The host list was taken from the NIC hostname table of 31-Dec-82. The tests were run on 25-Jan-83. ๐ซถ
838 ยท Smallberg ยท Jan 83 ยท Who Talks TCP? ๐ธ Same survey energy, different date ๐ This RFC is a survey of hosts checking the implementation status of Telnet, FTP, and Mail on TCP. The host list was taken from the NIC hostname table of 31-Dec-82. The tests were run on 18-Jan-83. โจ
837 ยท Smallberg ยท Jan 83 ยท Who Talks TCP? ๐ฆ Still the same survey, just another run ๐ This RFC is a survey of hosts checking the implementation status of Telnet, FTP, and Mail on TCP. The host list was taken from the NIC hostname table of 31-Dec-82. The tests were run on 11-Jan-83. ๐
836 ยท Smallberg ยท Jan 83 ยท Who Talks TCP? ๐ง
okay so this survey is basically a check-up on whether hosts can actually talk Telnet, FTP, and Mail over TCP ๐
the host list came from the NIC hostname table of 20-Dec-82, and the tests ran from 4-Jan-83 through 5-Jan-83 ๐ซถ
835 Smallberg Dec 82 Who Talks TCP?bestie this is the same Telnet, FTP, and Mail on TCP survey, but with an older hostname table from 2-Dec-82 and tests that ran from 28-Dec-82 through 5-Jan-83 ๐ฆ very thorough, very iconic ๐
834 Smallberg Dec 82 Who Talks TCP?same survey again ๐ธ using the 2-Dec-82 NIC hostname table, but this time the tests only ran on 22-Dec-82 โจ
833 Smallberg Dec 82 Who Talks TCP?yep, the same Telnet, FTP, and Mail on TCP check, built from the 2-Dec-82 NIC hostname table. this round of tests was run on 14-Dec-82 ๐
832 Smallberg Dec 82 Who Talks TCP?one more time with the Telnet, FTP, and Mail on TCP survey ๐ the hosts came from the 2-Dec-82 NIC hostname table, and the tests ran on 7-Dec-82 ๐
831 Braden Dec 82 Backup Access to the European Side
of SATNETthis one is all about focusing the conversation on a specific Internet problem ๐ง when SATNET gets partitioned, the European sector needs a backup path so its software can still be maintained. the proposal uses the Source Routing option of IP to reach European Internet sites through the VAN Gateway and UCL. it's not meant to be a standard yet โญ
830 Zaw-Sing Su Oct 82 A Distributed System for Internet
Name Servicethis RFC proposes a distributed name service for ARPA-Internet, and the whole point is to kickstart discussion ๐ฃ๏ธ the hope is that a general consensus shows up eventually and leads to standards ๐ฅ
829 Cerf Oct 82 Packet Satellite Technology
Reference Sourcesthis one briefly describes the packet satellite tech that DARPA and several other participating orgs in the U.K. and Norway developed ๐ฐ๏ธ it also has a bibliography of papers for researchers who want to dig into the experimental and operational experience with this dynamic satellite-sharing technique ๐โจ
828 Owen Aug 82 Data Communications: IFIP's
International "Network" of Expertssent out to keep the ARPA-Internet community in the loop on what the IFIP technical committee on Data Communications is up to ๐ it also wants people to jump in and participate ๐
827 Rosen Oct 82 Exterior Gateway Protocol (EGP)okay this one is giving gateways drama ๐ญ it's proposed as a standard for Gateway to Gateway procedures, where the gateways are basically allowed to be mutually suspicious lol ๐ this document is a DRAFT for that standard, and comments are strongly encouraged ๐
826 Plummer Nov 82 An Ethernet Address Resolution
Protocolthis RFC lays out a method for converting protocol addresses (like IP addresses) into local network addresses (like Ethernet addresses) ๐ everyone in the ARPA-Internet community was worried about this at the time, so it's here for your consideration and comment. it is not the specification of an ARPA-Internet Standard, so no pressure ๐ซถ
825 Postel Nov 82 Request for Comments on Requests for
Commentsthis is Postel being a whole mood ๐ง it clarifies what the status of RFCs is and gives authors some guidance for future RFCs. in a sense it's a specification for RFCs themselves, which is so meta it's giving main character energy ๐
824 MacGregor Aug 82 The Cronus Virtual Local Networkthis note describes the CRONUS Virtual Local Network, especially the addressing features ๐ฆ those include a way to map between Internet Addresses and Local Network addresses, which was a hot topic in the ARPA-Internet community at the time. it's meant to spark discussion and is not a specification of an ARPA-Internet Standard ๐
823 Hinden Sep 82 The DARPA Internet Gatewaythis RFC is a status report on the Internet Gateway that BBN developed, as it stood in September 1982 ๐ธ it goes deep into message formats and gateway procedures, but it's not an implementation specification, so those details can still change โจ
822 Crocker Aug 82 Standard for the Format of ARPA
Internet Text Messagesthis document revises RFC 733 so it can handle the bigger, more complicated ARPA-Internet ๐ some of 733's features didn't get enough acceptance, so they were cut to simplify the standard and the software built on it. there's a new addressing scheme for internetwork mail, and the concept of re-transmission was added ๐ฅ it obsoletes RFC 733, NIC 41952 ๐
821 Postel Aug 82 Simple Mail Transfer ProtocolSMTP's whole objective is to transfer mail reliably and efficiently ๐ฌ it doesn't care what transmission subsystem is underneath, it only needs a reliable, ordered data stream channel. it obsoletes RFCs 788, 780, 772 ๐
820 Postel Jan 82 Assigned Numbersthis RFC is is replaced by RFCs 997 and 990 ๐ซถ so if you're looking for it, go check those two instead ๐
819 Zaw-Sing Su Aug 82 The Domain Naming Convention for
Internet User Applicationsthis one tries to clarify the generalization of the Domain Naming Convention and the Internet Naming Convention ๐ง it also explores what adopting it would mean for ARPA-Internet name service and user applications. very big brain โจ
818 Postel Nov 82 The Remote User Telnet Servicethis is the spec for an application protocol, and any host that implements this application-level service has to follow this protocol ๐ฅ no skipping the rules, bestie ๐
817 Clark Jul 82 Modularity and Efficiency in
Protocol Implementationthis one talks about some of the common reasons protocol implementations end up running slowly ๐ข very relatable content tbh ๐ญ
816 Clark Jul 82 Fault Isolation and Recoverythis RFC covers the part of fault isolation and recovery that belongs to the host ๐ ๏ธ the host is the one responsible for this piece ๐
815 Clark Jul 82 IP Datagram Reassembly Algorithmsthis one offers an alternate way to handle reassembly that cuts the bookkeeping problem down to almost nothing ๐ฆ it only needs one buffer, equal in size to the final datagram being reassembled. it can rebuild a datagram from any number of fragments arriving in any order, with any possible pattern of overlap and duplication, and it works for almost any kind of operating system โจ literally so clever ๐คฏ
814 Clark Jul 82 Name, Addresses, Ports, and Routesthis RFC gives suggestions and guidance for designing the tables and algorithms you need to track these different kinds of identifiers inside a host implementation of TCP/IP ๐๏ธ it's basically a how-to for keeping your identifiers organized ๐
813 Clark Jul 82 Window and Acknowledgement Strategy
in TCPthis RFC covers implementation strategies for two TCP mechanisms: the window and the acknowledgement ๐ it also presents a set of algorithms that got tested in the field and seem to work well together. with more experience, these algorithms might become part of the formal specification, but only once their use is recommended ๐
812 Harrenstien Mar 82 NICNAME/WHOISthis RFC describes what the NICNAME/WHOIS Server is and how to access it ๐ together with the matching Identification Data Base, it gives online directory look-up that's equivalent to the ARPANET Directory ๐ธ
811 Harrenstien Mar 82 Hostnames Serverthis one explains what the Hostnames Server is and how to access it ๐ง its job is to deliver machine-readable name/address info about networks, gateways, hosts, and eventually domains inside the Internet environment ๐
810 Feinler Mar 82 DoD Internet Host Table
Specificationthis RFC specifies a new host table format that works for both ARPANET and Internet needs ๐ besides host name to host address translation and selected protocol info, it also includes network and gateway name to address correspondence, plus host operating system information ๐ it obsoletes the host table described in RFC 608 โจ
809 Chang Feb 82 UCL Facsimile Systemthis one describes the features of the computerised facsimile system that the Department of Computer Science at UCL developed ๐ it starts with its functions and the related experimental work, then gets into the disciplines for system design. the implementation of the system is described last, with the detailed descriptions in appendices ๐
808 Postel Mar 82 Summary of Computer Mail Services
Meeting Held at BBN on 10 January
1979this is a very belated attempt to document a meeting that happened three years earlier, to talk about the state of computer mail in the ARPA community ๐ฎ the goal was to reach some conclusions that would guide further mail system development, so a coherent total mail service would keep being provided ๐ซถ
807 Postel Feb 82 Multimedia Mail Meeting Notesthis RFC is the notes from a meeting held at USC/Information Sciences Institute on the 12th of January ๐๏ธ the topic was common interests in multimedia computer mail issues, and the group agreed on some specific initial experiments ๐งช
806 NBS Sep 81 Specification for Message Format for
Computer Based Message Systemsthis RFC is about Computer Based Message systems, which give a basis for interaction between different CBMS by defining the format of messages passed between them ๐ it's replaced by RFC 841 now, so check that one out too ๐ท
805 Postel Feb 82 Computer Mail Meeting Notesthese are notes from a meeting held at USC/Information Sciences Institute on 11 January 1982, all about addressing issues in computer mail ๐ง the big conclusion was to extend the username@hostname mailbox format to username@host.domain, where the domain itself can be structured further ๐ literally a whole new era of email addresses ๐
804ยทCCITTยทJan 82ยท CCITT Draft Recommendation T.4 ๐- okay so this is the CCITT standard for group 3 facsimile encoding ๐ basically how fax machines squish bitmap data. it's useful for data compression of bit map data ๐ธ
803ยทAgarwalยทNov 81ยท Dacom 450/500 Facsimile Data Transcoding ๐- part one dives deep into the Dacom 450 data compression algorithms, and it's an update and correction to an earlier memo ๐ซถ. part two gives a quick look at the Dacom 500 algorithm, the one used by the INTELPOST electronic-mail network that the US Postal Service and several foreign administrators were building ๐ฌ
802ยทMalisยทNov 81ยท The ARPANET 1822L Host Access Protocol โจ- this one proposed two big glow-ups to the ARPANET host access protocol ๐ . first, hosts could use logical addressing (host addresses that don't depend on where they physically sit on the ARPANET) to talk to each other ๐ฆ. second, a host could cut down how long its IMP is allowed to block it after it hands over a message. right now the IMP can block further input from a host for up to 15 seconds, which is giving "wait your turn" energy ๐. see RFCs 852 and 851 ๐
801ยทPostelยทNov 81ยท NCP/TCP Transition Plan ๐- this RFC is about moving hosts from NCP over to TCP ๐ฅ. it also makes the main services available: Telnet, File Transfer, and Mail ๐. these protocols let every host in the ARPA community share one common interprocess communication environment ๐ซถ
800ยทPostelยทNov 82ยท Requests for Comments Summary ๐799ยทMillsยทSep 81ยท Internet Name Domains ๐- as the Internet keeps growing, host names can't stay one flat space of globally unique names ๐ญ. so a hierarchy of name domains has to be introduced. see also RFC 822 ๐
798ยทKatzยทSep 81ยท Decoding Facsimile Data From the Rapicom 450 ๐- describes how to encode and decode data for the Rapicom 450 fax machine ๐ธ
797ยทKatzยทSep 81ยท Format for Bitmap Files ๐ผ๏ธ- a simple file format for bitmap data, very clean and no-nonsense ๐
796ยทPostelยทSep 81ยท Address Mappings ๐บ๏ธ- shows how the addresses of a few real networks get mapped into internet addresses ๐ฆ
795ยทPostelยทSep 81ยท Service Mappings ๐- shows how the internet type of service maps onto the actual service parameters of a few particular networks, and also how it works the other way around ๐
794ยทCerfยทSep 81ยท Pre-Emption ๐ฆ- talks about how pre-emption of a TCP connection can be implemented. this one replaces IEN 125 ๐ซถ
793ยทPostelยทSep 81ยท Transmission Control Protocol ๐- the spec for TCP, the queen of the protocols ๐ it replaces RFCs 761 and 675 ๐
792ยทPostelยทSep 81ยท Internet Control Message Protocol ๐จ- the spec for ICMP. it replaces RFCs 777 and 760 โจ
791ยทPostelยทSep 81ยท Internet Protocol ๐- an updated spec for IP ๐. it replaces RFC 760 ๐
790ยทPostelยทSep 81ยท Assigned Numbers ๐ข- this RFC is replaced by RFCs 997 and 990 ๐
789ยทRosenยทJul 81ยท Vulnerabilities of Network Control Protocols: An Example ๐ฑ- this one describes an outage in ARPANET service and the process of figuring out what caused it ๐ต๏ธ. it also gets into the subtleties of designing network protocols, which is so real ๐
788ยทPostelยทNov 81ยท Simple Mail Transfer Protocol ๐ง- an old version. see RFC 821 ๐
787ยทChapinยทJul 81ยท Connectionless Data Transmission Survey/Tutorial ๐- a discussion of datagram service ๐ฆ. it was meant to be submitted to international standards bodies ๐
786ยทSluizerยทJul 81ยท Mail Transfer Protocol: ISI TOPS-20 MTP-NIMAIL Interface ๐ฌ- describes how mail gets passed between the MTP and the NIMAIL programs in ISI TOPS-20. it's outdated ๐ฅ
785ยทSluizerยทJul 81ยท Mail Transfer Protocol: ISI TOPS-20 File Definitions ๐- the file format for passing mail to the MTP program from user mail programs in ISI TOPS-20. also outdated ๐ฅ
784ยทSluizerยทJul 81ยท Mail Transfer Protocol: ISI TOPS-20 Implementation ๐ ๏ธ- the program structure for the MTP implementation in ISI TOPS-20. outdated, sorry bestie ๐ฅ
783ยทSollinsยทJun 81ยท The TFTP Protocol Revision 2 ๐ฆ- the spec for TFTP. it replaces RFCs 768, 764 and IEN 133 ๐ซถ
782ยทNabielskyยทundatedยท A Virtual Terminal Management Model ๐ฅ๏ธ- describes the elements of a virtual terminal and how communications between them get managed ๐ง
781ยทSuยทMay 81ยท A Specification of the Internet Protocol IP Timestamp Option โฐ- describes the IP Timestamp option. it's now included in the IP spec (RFC 791) so it's basically part of the main character ๐
780ยทSluizerยทMay 81ยท Mail Transfer Protocol ๐ฌ- an outdated mail protocol. see RFC 821 ๐ฅ
779ยทKillianยทApr 81ยท Telnet Send-Location Option ๐- defines this Telnet option ๐
778ยทMillsยทApr 81ยท DCNet Internet Clock Service โฑ๏ธ- specifies a format and procedure for exchanging messages so clocks stay synchronized ๐ซถ
777ยทPostelยทApr 81ยท Internet Control Message Protocol ๐จ- an old version. see RFC 792 ๐
776ยทPostelยทJan 81ยท Assigned Numbers ๐ข- this RFC has been replaced by RFCs 997 and 990 ๐
775ยทMankinsยทDec 80ยท Directory Oriented FTP Commands ๐- defines extra FTP commands for directory management ๐ฆ
774ยทPostelยทOct 80ยท Internet Protocol Handbook Table of Contents ๐- an out-of-date table of contents for an Internet Protocol Handbook ๐ฅ
773ยทCerfยทOct 80ยท Comments on NCP/TCP Mail Service Transition Strategy ๐ญ- a discussion of issues in the move from NCP to TCP, especially the MAIL Service part ๐ฌ
772ยทSluizerยทSep 80ยท Mail Transfer Protocol ๐ฌ- an old version of a Mail Protocol. see RFC 821 ๐
771ยทCerfยทSep 80ยท Mail Transition Plan ๐๏ธ- a plan for supporting mail service during the move from NCP to TCP. see also RFC 801 โจ
770ยทPostelยทSep 80ยท Assigned Numbers ๐ข- this RFC has been replaced by RFCs 997 and 990 ๐
769ยทPostelยทSep 80ยท Rapicom 450 Facsimile File Format ๐- defines the exchange format for the encoded facsimile data of the Rapicom 450. see also RFC 798 ๐ธ
768ยทPostelยทAug 80ยท User Datagram Protocol ๐ฆ- the spec for UDP ๐
767ยทPostelยทAug 80ยท A Structured Format for Transmission of Multi-Media Documents ๐๏ธ- defines the format for the document inside a multimedia message ๐
766ยทPostelยทJul 80ยท Internet Protocol Handbook ๐- an out-of-date table of contents for the Internet Protocol Handbook ๐ฅ
765ยทPostelยทJun 80ยท File Transfer Protocol Specification ๐- the spec for FTP ๐ซถ
764ยทPostelยทJun 80ยท Telnet Protocol Specification ๐ฅ๏ธ- the spec for Telnet ๐
763ยทAbramsยทMay 80ยท Role Mailboxes ๐ฎ- a call for mailboxes with role names, like "Management" ๐
762ยทPostelยทJan 80ยท Assigned Numbers ๐ข- this RFC has been replaced by RFCs 997 and 990 ๐
761ยทPostelยทJan 80ยท DOD Standard Transmission Protocol ๐ชฆ- an old version. see RFC 793 ๐
760ยทPostelยทJan 80ยท DOD Standard Internet Protocol ๐ชฆ- an old version. see RFC 791 ๐
759ยทPostelยทAug 80ยท Internet Message Protocol ๐- defines the protocol and format for exchanging multimedia mail. it replaces RFC 753 ๐
758ยทPostelยทAug 79ยท Assigned Numbers ๐ข- this RFC has been replaced by RFCs 997 and 990 ๐
757ยทDeutschยทSep 79ยท A Suggested Solution to the Naming, Addressing, and Delivery Problem for ARPANET Message Systems ๐งฉ- talks through several proposals for turning a name into an address so computer mail can be routed ๐ฌ. it favors a solution built on unique-ids and a database. see also RFCs 759, 821 and 822 ๐
756ยทPickensยทJul 79ยท The NIC Name server--A Datagram-Based Information Utility ๐- describes a Host Name to Address look up service ๐ซถ
755ยทPostelยทMay 79ยท Assigned Numbers ๐ข- this RFC has been replaced by RFCs 997 and 990 ๐
754ยทPostelยทApr 79ยท Out-of-Net Host Addresses for Mail ๐- a discussion of options for addressing computer mail beyond the ARPANET ๐ญ
753ยทPostelยทMar 79ยท Internet Message Protocol ๐- an old version. see RFC 759 ๐
752ยทCrispinยทJan 79ยท A Universal Host Table ๐๏ธ- describes the host table used at MIT and Stanford ๐ซ. it has several extensions and generalizations on top of the NIC standard and the table most Tenex and TOPS20 hosts use ๐
751ยทLeblingยทDec 78ยท Survey of FTP Mail and MLFL ๐ฌ- a survey of how hosts responded when they were probed through their FTP servers ๐ต๏ธ. the probes checked whether servers (a) accept mail for unknown users and (b) support the MAIL and MLFL commands ๐ซฃ
750ยทPostelยทSep 78ยท Assigned Numbers ๐ข- this RFC has been replaced by RFCs 997 and 990 ๐
749ยทGreenbergยทSep 78ยท Telnet SUPDUP-OUTPUT Option ๐จ๏ธ- updates RFC 736. see also RFCs 734, 746, and 747 โจ
748ยทCrispinยทApr 78ยท Telnet Randomly-Lose Option ๐ฒ- defines this Telnet option. note the date of this memo ๐ it's giving April Fools, no cap ๐ญ
747ยทCrispinยทMar 78ยท Recent Extensions to the SUPDUP Protocol ๐- an update to the SUPDUP protocol (RFC 734). see also RFCs 749, 746 and 736 ๐
746ยทStallmanยทMar 78ยท The SUPDUP Graphics Extension ๐จ- an extension of SUPDUP for Graphics. see also RFCs 734, 736, 747 and 749 ๐
745ยทBeelerยทMar 78ยท JANUS Interface Specifications ๐- the spec for a symmetrical 1822-style interface ๐ฆ
744ยทSattleyยทJan 78ยท MARS - A Message Archiving and Retrieval Service ๐๏ธ- describes a database service for computer mail messages, and it operates via computer mail itself ๐ฌ very meta, I love it ๐
543ยทHarrenstienยทDec 77ยท FTP Extension: XRSQ/XRCP ๐ค- an extension to FTP mail that allows more efficient transmission of computer mail ๐. it's now incorporated into SMTP; see RFC788 โจ
742ยทHarrenstienยทDec 77ยท NAME/FINGER Protocol ๐- defines the Name or Finger Protocol, which lets you ask another host "who is on" or "where is user x" ๐ซฃ main character research energy ๐
741ยทCohenยทNov 77ยท Specifications for the Network Voice Protocol NVP ๐๏ธ- defines the protocol used in the ARPANET packet speech experiments ๐ฃ๏ธ. it was replaced by NVP-II and ST for Internet packet speech experiments. ST is documented in ISN 119, and NVP-II is documented in an ISI Internal memo ๐
740ยทBradenยทNov 77ยท NETRJS Protocol ๐ง
Okay so the first bit here is the tail end of the RFC 740 entry, which explains the Remote Job Entry protocol for the UCLA CCN IBM system ๐ฅ๏ธ and replaces RFCs 599 and 189. Bye bye old versions ๐
739 Postel Nov 77 Assigned Numbers
Replaced by RFCs 997 and 990, so go read those instead ๐ซถ
738 Harrenstien Oct 77 Time Server
Defines the Time Server Protocol ๐ฐ๏ธ. For the TCP and VDP versions, check out IEN 142 โจ
737 Harrenstien Oct 77 FTP Extension: XSEN
An extension to the Mail procedures that got folded into SMTP ๐. Also see RFC 821.
736 Crispin Oct 77 Telnet SUPDUP Option
Explains how to negotiate the SUPDUP protocol as a Telnet option ๐. Also see RFCs 734, 746, 747 and 749.
735 Crocker Nov 77 Revised Telnet Byte Macro Option
A Telnet option for assigning codes that stand in for strings in Telnet connections ๐ง. It replaces RFC 729 and obsoletes NIC 40306.
734 Crispin Oct 77 SUPDUP Protocol
A terminal control protocol used at Stanford and MIT ๐ฅ๏ธ. Also see RFCs 736, 746-749.
733 Crocker Nov 77 Standard for the Format of ARPA Network Text Messages
This is the format for headers on computer mail ๐ง. It's an old version, so RFC 822 is the one to read.
732 Day Sep 77 Telnet Data Entry Terminal Option
A Telnet option for controlling a data entry display terminal โจ๏ธ. It replaces RFC 731.
731 Day Jun 77 Telnet Data Entry Terminal Option
Old version alert ๐จ, so see RFC 732.
730 Postel May 77 Extensible Field Addressing
Some addressing ideas that pop up when you move from 8-bit to 24-bit network addresses ๐.
729 Crocker May 77 Telnet Byte Macro Option
Old version, so see RFC 735.
728 Day Apr 77 A Minor Pitfall in the Telnet Protocol
Heads up ๐ฌ about a possible surprise in Telnet, where option subnegotiations interact with the Telnet SYNCH operation.
727 Crispin Apr 77 Telnet Logout Option
A Telnet option that makes you log out ๐ช.
726 Postel Mar 77 Remote Controlled Transmission and Echoing Telnet Option
A Telnet option for controlling how data is transmitted and echoed, so responses feel smoother in high transmission delay environments โณ. Also see RFCs 719 and 718.
725 Day Mar 77 An RJE Protocol for a Resource Sharing Network
A possible Remote Job Entry protocol ๐งฉ.
724 Crocker May 77 Proposed Official Standard for the Format of ARPA Network Messages
Old version, so see RFC 822.
723 Never Issued.
722 Haverty Sep 76 Thoughts on Interactions in Distributed Services
A discussion of how to design interactive distributed services and what kinds of primitive operations they need ๐ง .
721 Garlick Sep 76 Out of Band Control Signals in a Host to Host Protocol
Talks about control signals in transport protocols, like NCP's Interrupt or TCP's Urgent (e.g., NCP's Interrupt or TCP's Urgent) ๐.
720 Crocker Aug 76 Address Specification Syntax for Network Mail
A chat about computer mail addresses, including real names vs. mailboxes and mailing lists ๐ฌ. Also see RFC 819.
719 Postel Jul 76 Discussion on RCTE
A short look at RCTE implementation issues ๐ ๏ธ. Also see RFCs 726 and 718.
718 Postel Jun 76 Comments on RCTE from the Tenex Implementation Experience
A quick note on the Tenex implementation of RCTE ๐. Also see RFCs 726 and 719.
717 Postel Jul 76 Assigned Network Numbers
Replaced by RFC 997 and 990.
716 Levin May 76 Interim Revision to Appendix F of BBN 1822
A short update to the specification of the Very Distant Host 1822 interface ๐ฐ๏ธ.
715 Never Issued.
714 McKenzie Apr 76 A Host/Host Protocol for an ARPANET-type Network
An NCP-like protocol for an ARPA-like network ๐ธ๏ธ. It's fun to compare it with the NCP specification and see what the author would do differently ๐.
713 Haverty Apr 76 MSDTP -- Message Services Data Transmission Protocol
A set of Data Primitives for building interactive services ๐งฑ.
712 Donnelley Feb 76 A Distributed Capability Computing System DCCS
A description of a distributed, capability-based computing system ๐.
711 Never Issued.
710 Never Issued.
709 Never Issued.
708 White Jan 76 Elements of a Distributed Programming System
A description of a distributed programming system. Also see RFC 707.
707 White Dec 75 A High-Level Framework for Network-Based Resource Sharing
A programming environment for network-based programs ๐ฅ๏ธ. Also see RFC 708.
706 Postel Nov 75 On the Junk Mail Problem
A short note pointing out that the ARPANET maybe subject to a "denial of service" attack by a misbehaving host ๐ซ.
705 Bryan Nov 75 Front-End Protocol
This one covers a protocol between a PDP-11 (the ARPANET front end) and a B6700 that supports network communication ๐.
704 Santos Sep 75 IMP/Host and Host/IMP Protocol Change
Changes to the 1822 interface that get rid of the restriction of 63 IMPs ๐.
703 Dodds Jul 75 Survey of New-Protocol Telnet Servers
A poll of Telnet servers to check their implementation status and Telnet options ๐. Updates RFCs 702, 701, 679 and 669.
702 Dodds Sep 74 Survey of New-Protocol Telnet Servers
An earlier poll of Telnet server implementation status ๐. See also RFC's703, 701, 679, and 669.
701 Dodds Aug 74 Survey of New-Protocol Telnet Servers
An earlier poll of Telnet server implementation status ๐. See also RFCs 703, 702, 679 and 669.
700 Mader Aug 74 A Protocol Experiment
A protocol loosely based on a very early version of TCP, used to send data to a printer server ๐จ๏ธ.
699 Postel Nov 82 Requests for Comments Summary Notes: 600-699
A summary of the Request for Comments documents from RFC 600-699 ๐.
698 Tovar Jul 75 Telnet Extended ASCII Option
An option that allows a special kind of extended ASCII used at the Stanford AI and MIT AI Labs ๐ค.
697 Lieb Jul 75 CWD Command of FTP
A look at FTP login access to "files only" directories ๐.
696 Cerf Jul 75 Comments on the IMP/HOST and HOST/IMP Protocol Changes
Observations on current international standards recommendations from IFIP working group 6.1 ๐. Also see RFCs 692, 690 687.
695 Krilanovich Jul 75 Official Change in Host-Host Protocol
Fixes an ambiguity about the ERR command ๐ง. It changes NIC 8246 and NIC 7104.
694 Postel Jun 75 Protocol Information
Replaced by RFC 991.
693 Never Issued.
692 Wolfe Jun 75 Comments on IMP/Host Protocol Changes
A proposed solution to the problem of the combined length of IMP and Host leaders ๐งฉ. Also see RFCs 696, 690 and 687.
691 Harvey May 75 One More Try on the FTP
A slight revision of RFC 686 about print files ๐จ๏ธ. Also see RFCs 640, 630, 542, 454, 448, 414, 385 and 354.
690 Postel Jun 75 Comments on the Proposed Host/IMP Protocol Changes
Comments on suggestions in RFC 687 ๐ฌ. Also see RFCs 692 and 696.
689 Clements May 75 Tenex NCP Finite State Machine for Connections
The internal states of an NCP connection in the Tenex implementation ๐.
688 Walden Jun 75 Tentative Schedule for the New Telnet Implementation for the TIP
687 Walden Jun 75 IMP/Host and Host/IMP Protocol Changes
This one talks about addressing hosts on more than 63 IMPs, plus other backwards compatible expansions ๐. Also see RFCs 690 and 692.
686 Harvey May 75 Leaving Well Enough Alone
The differences between early and later versions of FTP ๐ฐ๏ธ. Also see RFCs 691, 640, 630, 542, 454, 448, 414, 385 and 354.
685 Beeler Apr 75 Response Time in Cross-network Debugging
How ARPANET communication contributes to response time โฑ๏ธ.
684 Schantz Apr 75 A Commentary on Procedure Calling as a Network Protocol
Issues in designing distributed computing systems ๐ง . It covers shortcomings of RFC 674, and also see RFCs 542 and 354.
683 Clements Apr 75 FTPSRV -- Tenex Extension for Paged Files
An extension to FTP for page-mode transfers between Tenex systems ๐. It also discusses file transfer reliability.
682 Never Issued.
681 Holmgren May 75 Network Unix
Capabilities as an ARPANET Mini-Host ๐งธ: standard I/O, Telnet, NCP, Hardware/Software requirements, reliability, and availability.
680 Myer Apr 75 Message Transmission Protocol
Extends the message field definition beyond RFC 561 and tries to set syntactic and semantic standards for ARPANET ๐. Also see RFCs 733 and 822.
679 Dodds Feb 75 February, 1975, Survey of New-Protocol Telnet Servers
An earlier poll of Telnet server implementation status ๐. It updates RFCs 701, 702 and 669, and also see RFC 703.
678 Postel Dec 74 Standard File Formats
For sending documents across different environments ๐จ.
677 Johnson Jan 75 The Maintenance of Duplicate Databases
676 Never Issued.
675 Cerf Dec 74 Specification of Internet Transmission Control Program (TCP)
The first detailed specification of TCP ๐. See RFC 793.
674 Postel Dec 74 Procedure Call Documents--Version 2
A host-level protocol used in the NSW, which is a slightly constrained version of the ARPANET Host-to-Host protocol ๐งต. It affects allocation, RFNM wait, and retransmission. Also see RFC 684.
673 Never Issued.
672 Schantz Dec 74 A Multi-Site Data Collection Facility
Applicability of TIP/Tenex protocols beyond TIP accounting.
671 Schantz Dec 74 A Note on Reconnection Protocol
Experience with implementation in RSEXEC context.
670 Never Issued.
669 Dodds Dec 74 November 1974, Survey of
New-Protocol Telnet Servers
An earlier poll of Telnet server implementation status. Updates
RFC 702; see also RFCs 703 and 679.
668 Never Issued.
667 Chipman Dec 74 BBN Host Ports
Approved scheme to connect host ports to the network.
666 Padlipsky Nov 74 Specification of the Unified
User-Level Protocol
Discusses and proposes a common command language.
665 Never Issued.
664 Never Issued.
663 Kanodia Nov 74 A Lost Message Detection and
Recovery Protocol
Proposed extension of host-host protocol; see also RFCs 534, 516,
512, 492 and 467.
662 Kanodia Nov 74 Performance Improvement in ARPANET
File Transfers from Multics
Experimenting with host output buffers to improve throughput.
661 Postel Nov 74 Protocol Information
This RFC has been replaced by RFC 991.
660 Walden Oct 74 Some Changes to the IMP and the
IMP/Host Interface
Decoupling of message number sequences of hosts; host-host access
control; message number window; messages outside normal mechanism;
see also BBN 1822.
659 Postel Oct 74 Announcing Additional Telnet Options
Options defined in RFCs 651-658.
658 Crocker Oct 74 Telnet Output Line Feed Disposition
Defines a Telnet option for specific control of Line Feed.
657 Crocker Oct 74 Telnet Output Vertical Tab
Disposition Option
Defines a Telnet option for specific control of Vertical Tab.
656 Crocker Oct 74 Telnet Output Vertical Tab Stops
Option
Defines a Telnet option for setting the stops for Vertical Tab.
655 Crocker Oct 74 Telnet Output Form Feed Disposition
Option
Defines a Telnet option for specific control of Form Feed.
654 Crocker Oct 74 Telnet Output Horizontal Tab
Disposition Option
Defines a Telnet option for specific control of Horizontal Tab.
653 Crocker Oct 74 Telnet Output Horizontal Tab Stops
Option
Defines a Telnet option for setting the stops for Horizontal Tab.
652 Crocker Oct 74 Telnet Output Carriage Return
Disposition Option
Defines a Telnet option for specific control of Carriage Return.
651 Crocker Oct 74 Revised Telnet Status Option
Revises the Telnet Option for communicating the status of all
Telnet options over the network.
650 Never Issued.
649 Never Issued.
648 Never Issued.
647 Padlipsky Nov 74 A Proposed Protocol for Connecting
Host Computers to ARPA-Like Networks
via Front End Processors
Approaches to Front-End protocol processing using available
hardware and software.
646 Never Issued.
645 Crocker Jun 74 Network Standard Data Specification
Syntax
Providing a mechanism for specifying all attributes of a
collection of bits; see also RFC 615.
644 Thomas Jul 74 On The Problem of Signature
Authentication for Network Mail
Proposes that the mail sender be an authorized system process and
that the mail sender and mail receiver processes exchange a
password. The sender process takes responsibility for
authentication of the signature on the mail.
643 Mader Jul 74 Network Debugging Protocol
To be used in an implementation of a PDP-11 network bootstrap
device and a cross-network debugger.
642 Burchfiel Jul 74 Ready Line Philosophy and
Implementation
641 Never Issued.
640 Postel Jun 74 Revised FTP Reply Codes
Updates RFC 542.
639 Never Issued.
638 McKenzie Apr 74 IMP/TIP Preventive Maintenance
Schedule
Corrects RFC 633.
637 McKenzie Apr 74 Change of Network Address for SU-DSL
A host at Stanford changes its address from 2/2 to 2/3.
636 Burchfiel Jun 74 TIP/TENEX Reliability Improvements
Obtaining/maintaining connections; recovery from lost connections;
connection-state changes.
635 Cerf Apr 74 An Assessment of ARPANET Protocols
Theoretical and practical motivation for redesign. Multipacket
messages; host retransmission; duplicate detection; sequencing;
acknowledgement.
634 McKenzie Apr 74 Change in Network Address for
Haskins Lab.
A host a Haskins Lab changes its address from 5/3 to 9/3.
633 McKenzie Mar 74 IMP/TIP Preventive Maintenance
Schedule
An old version; see RFC 638.
632 Opderbeck May 74 Throughput Degradations for Single
Packet Messages
A study of packet throughput.
631 Danthine Apr 74 Call for Papers: International
Meeting on Minicomputers and Data
Communication
A meeting on data communications held January 1975 in Liege,
Belgium.
630 Sussman Apr 74 FTP Error Code Usage for More
Reliable Mail Service
Describes FTP reply-code usage in TENEX mail processing.
629 North Mar 74 Scenario for Using the Network
Journal
An example of how to access information in the NIC's Journal
database.
628 Keeney Mar 74 Status of RFC Numbers and a Note on
Pre-assigned Journal Numbers
A method for getting the next RFC number to use on a new memo.
627 Feinler Mar 74 ASCII Text File of Hostnames
See also RFCs 606, 608, 623 and 625.
626 Kleinrock Mar 74 On a possible Lockup Condition in
IMP Subnet due to Message Sequencing
A potential problem in the IMP processing of messages. A detailed
description of how this condition can arise.
625 Feinler Mar 74 On Line Hostnames Service
See also RFCs 606, 608, 623 and 627.
624 Krilanovich Feb 74 Comments on the File Transfer
Protocol
Design changes and slight modifications. Replaces RFC 607; see
also RFCs 614, 542 and 640.
623 Krilanovich Feb 74 Comments on On-Line Host Name
Service
See also RFCs 627, 625, 608 and 606.
622 McKenzie Mar 74 Scheduling IMP/TIP Down Time
Modification of previous policy.
621 Kudlick Mar 74 NIC User Directories at SRI-ARC
Changes in user accounts at the NIC.
620 Ferguson Mar 74 Request for Monitor Host Table
Updates
Changes in the hosts Office-1 and SRI-ARC.
619 Naylor Mar 74 Mean Round-Trip Times in the ARPANET
Actual measurements of round-trip times.
618 Taft Feb 74 A Few Observations on NCP Statistics
Distribution of NCP and IMP message types by actual measurement.
617 Taft Feb 74 A Note on Socket Number Assignment
Danger of imposing more fixed socket number requirements; see also
RFCs 542, 503 and 451.
616 Walden Feb 74 Latest Network Maps
Geographic ad Topologic maps of the ARPANET of January 1974.
615 Crocker Mar 74 Proposed Network Standard Data
Pathname Syntax
A suggestion for a network wide standard for naming data (such as
files).
614 Pogran Jan 74 Response to RFC 607 (NIC-21255),
"Comments on the FTP"
See also RFCs 624, 542 and 640.
613 McKenzie Jan 74 Network Connectivity: A Response to
RFC 603
Remarks about connectivity and robustness of networks.
612 McKenzie Jan 74 Traffic Statistics
A report on Host traffic statistics for the month of December
1973. Updates RFC 601.
611 Walden Feb 74 Two Changes to the IMP/Host Protocol
Expansion of Host-Going-Down and addition of Dead-Host-Status
Message.
610 Winter Dec 73 Further Datalanguage Design Concepts
Preliminary results of the language design; a model for data
languagea semantics; future considerations.
609 Ferguson Jan 74 Statement of Upcoming Move of
NIC/NLS Service
See also RFCs 621 and 620.
608 Feinler Jan 73 Host Names On-Line
Response to RFC 606; see also RFCs 627, 625 and 623.
607 Krilanovich Jan 73 NIC-21255 Comments on the File
Transfer Protocol
An old version; see RFC 624; see also RFCs 614, 542 and 640.
606 Deutsch Dec 73 Host Names On-Line
Resolving differences in hostname-address mappings; see also RFCs
627, 625, 623 and 608.
605 Never Issued.
604 Postel Dec 73 Assigned Link Numbers
Modifies official host-host protocol. Replaced by RFCs 997 and
990.
603 Burchfiel Dec 73 Response to RFC 597: Host Status
Questions about the ARPANET topology described in RFC 597.
602 Metcalfe Dec 73 "The Stockings Were Hung by the
Chimney With Care"
Susceptibility of ARPANET to security violations.
601 McKenzie Dec 73 Traffic Statistics
A report on Host traffic statistics for the month of November
1973. Updates RFC 586.
600 Berggreen Nov 73 Interfacing an Illinois Plasma
Terminal to the ARPANET
Discusses plans to map Plato terminal codes to network ASCII for
accessing the Plato system via the network using Telnet.
599 Braden Dec 73 Update on NETRJS
A status report and update on UCLA-CCN's remote job entry service.
598 NICSTA Dec 73 RFC Index - December 5, 1973
Lists RFCs 1-593.
597 Neigus Dec 73 Host Status
This RFC provides the most current network maps, geographic and
logical, plus a list of hosts connected to the ARPANET.
596 Taft Dec 73 Second Thoughts on Telnet Go-Ahead
Cited objections to the requirement that hosts implement the
Telnet Go-Ahead (GA) command, as specified in the Telnet Protocol
Specification.
595 Hathaway Dec 73 Some Thoughts in Defense of the
Telnet Go-Ahead
This RFC is in reply to RFC 596.
594 Burchfiel Dec 73 Speedup of Host-IMP InterfacePure index vibes this part, bestie ๐๏ธโจ the list keeps marching backwards through 1973โ74 and I'm here for every entry ๐
A discussion on how to make the full performance capabilities of the subnet available for interprocess communication. ๐โจ
- 593 ยท
McKenzieยทNov 73ยท Telnet and FTP Implementation Schedule Change ๐ - 592 ยท
WatsonยทNov 73ยท Some Thoughts on System Design to Facilitate Resource Sharing ๐ง- Okay, so this one proposes a system interconnection approach that would help us move toward more resource sharing on the ARPANET. ๐๐
- 591 ยท
WaldenยทNov 73ยท Addition to the Very Distant Host Specification ๐- A sentence correction notation that should go into Appendix F of BBN Report 1822. Tiny edit, big vibes. โ๏ธ
- 590 ยท
PadlipskyยทNov 73ยท MULTICS Address Change ๐- Announces a plan to change the address of MIT Multics. Moving house, but make it networking. ๐ฆ
- 589 ยท
BradenยทNov 73ยท CCN NETRJS Server Messages to Remote User ๐ฌ- Describes the messages sent to the user by UCLA-CCN's remote job entry service. Very behind-the-scenes, very iconic. ๐ฌ
- 588 ยท
StokesยทOct 73ยท London Node is now up ๐ฌ๐ง- Notice that an ARPANET node is now operational at University College, London. The network just got a new bestie! ๐ซถ
- 587 ยท
PostelยทNov 73ยท Announcing New Telnet Options ๐- Announces Negotiate About Output Line Width (NAOL) and Negotiate About Output Page Size (NAOP). Two new options, both serving looks. ๐
- 586 ยท
McKenzieยทNov 73ยท Traffic Statistics ๐- A report on the Host traffic statistics for the month of October 1973. Updates RFC 579. Numbers, numbers, numbers. ๐ข
- 585 ยท
CrockerยทNov 73ยท ARPANET Users Interest Working Group Meeting ๐๏ธ- Meeting notes from the first Users Interest Working Group. The very first meeting, so it's historic. ๐
- 584 ยท
IseliยทNov 73ยท Charter for ARPANET Users Interest Working Group ๐- Describes the background, membership, and scope of the newly formed Users Interest Working Group. Official start of the squad! ๐ฏโโ๏ธ
- 583 ยท Never Issued. ๐ซฅ
- 582 ยท
ClementsยทNov 73ยท Comments on RFC 580 - Machine Readable Protocols ๐ โโ๏ธ- Cites objections to the phrase "preferably NLS files." Not everyone was vibing with that one. ๐
- 581 ยท
CrockerยทNov 73ยท Corrections to RFC 560 - Remote Controlled Transmission and Echoing Telnet Option ๐ฉน- This RFC contains corrections to RFC 560, which described the Remote Controlled Transmission and Echoing Telnet Option. Fixing the fix, lowkey iconic. โจ
- 580 ยท
PostelยทOct 73ยท Note to Protocol Designers and Implementers ๐ฃ- Announces that future proposed protocols will be submitted as on-line documents, preferably in NLS files, to the Network Information Center. Going digital, bestie! ๐ป
- 579 ยท
McKenzieยทOct 73ยท Traffic Statistics ๐- A report on the Host traffic statistics for the month of September 1973. Updates RFC 566. Stats never sleep. ๐ดโ
- 578 ยท
BhushanยทOct 73ยท Using MIT-MATHLAB MACSYMA From MIT-DMS Muddle - An Experiment in Automated Resource Sharing ๐งฎ- This paper describes an experiment in non-trivial automated resource sharing between dissimilar systems. The goal was to interface the Muddle system at MIT-DMS to the MACSYMA system at MIT-Mathlab. Two totally different systems, talking to each other. Main character energy. ๐ฅ
- 577 ยท
CrockerยทOct 73ยท Mail Priority ๐ฌ - 576 ยท
VictorยทSep 73ยท Proposal for Modifying Linking ๐- Presents a plan to modify the link jsys in Tenex so it works better for the user interface. UX glow-up. ๐ซ
- 575 ยท Never Issued. ๐ซฅ
- 574 ยท
KrilanovichยทSep 73ยท Announcement of a Mail Facility at UCSB ๐ฎ- An announcement of a server program that supports the subset of the File Transfer Protocol needed for mail delivery. Just the essentials, no extra drama. ๐
- 573 ยท
BhushanยทSep 73ยท Data and File Transfer - Some Measurement Results ๐- A report on the performance results of MIT-DM's FTP-user and FTP-server programs. Receipts, bestie. ๐งพ
- 572 ยท Never Issued. ๐ซฅ
- 571 ยท
BradenยทNov 73ยท Tenex FTP Problem ๐- A report on a problem in the current Tenex implementation that is likely to cause incorrect results when transferring files to a non-Tenex site. Not it. ๐ โโ๏ธ
- 570 ยท
PickensยทOct 73ยท Experimental Input Mapping Between NVT ASCII and UCSB Online System ๐งช- This RFC updates RFC 216. It describes proposed solutions from requests to improve the human interface to the UCSB On-Line System. Making the interface less painful, one request at a time. ๐ซถ
- 569 ยท
PadlipskyยทOct 73ยท NETED: A Common Editor for the ARPA Network โ๏ธ- Defines a simple line style text editor and suggests it be made available on every host in the network. Everyone gets an editor, no exceptions. ๐
- 568 ยท
McQuillanยทSep 73ยท Response to RFC 567 - Cross-Country Network Bandwidth ๐โโ๏ธ- A brief correction to several fundamental errors in RFC 567. Oops, but make it accountable. ๐ซฃ
- 567 ยท
DeutschยทSep 73ยท Cross-Country Network Bandwidth ๐- Computes cross-country network bandwidth. The math is giving confidence. ๐งฎ
- 566 ยท
McKenzieยทSep 73ยท Traffic Statistics ๐- A report on the Host traffic statistics for the month of August 1973. Updates RFC 556. Another month, another stats drop. ๐
- 565 ยท
CantorยทAug 73ยท Storing Network Survey Data at the Datacomputer ๐๏ธ- A project summary describing the programs developed and implemented that have been running successfully with the datacomputer since July 10. Working, and working well. ๐
- 564 ยท Never Issued. ๐ซฅ
- 563 ยท
DavidsonยทAug 73ยท Comments on the RCTE Telnet Option ๐ง- A critique based on inferences drawn from the sample Tenex interaction in RFC 560. Sharp eyes, no mercy. ๐
- 562 ยท
McKenzieยทAug 73ยท Modifications to the Telnet Specification ๐ง- Presents two documents that update RFC 495, plus a summary of the changes. Two docs, one tidy recap. ๐
- 561 ยท
BhushanยทSep 73ยท Standardizing Network Mail Headers ๐ท๏ธ- A proposed document for explicitly specifying header information such as author, title, and date within the current FTP mail protocol. Labels, labels, everywhere. ๐
- 560 ยท
CrockerยทAug 73ยท Remote Controlled Transmission and Echoing Telnet Option ๐๏ธ- Defines a Telnet option for detailed control of echoing, to make interactive use over long delay paths smoother. Long-distance connection, but make it cute. ๐
- 559 ยท
BhushanยทAug 73ยท Comments on the New Telnet Protocol and Its Implementation ๐ฃ๏ธ- Describes the experience MIT-DM had implementing the new Telnet protocol, for both server and user. Real talk from the implementers. ๐ฌ
- 558 ยท Never Issued. ๐ซฅ
- 557 ยท
WesslerยทAug 73ยท Revelations in Network Host Measurements ๐- A report to the RFC community on the current network host measurements. The tea is spilled. โ
- 556 ยท
McKenzieยทAug 73ยท Traffic Statistics ๐- A report on the Host traffic statistics for the month of July 1973. Updates RFC 538. Stats for days. ๐
- 555 ยท
WhiteยทJul 73ยท Response to Critiques of the Proposed Mail Protocol ๐- A response to the proposal for a Mail Protocol (RFC 524). Defending the crush, respectfully. ๐ซถ
- 554 ยท Never Issued. ๐ซฅ
- 553 ยท
ThomasยทJul 73ยท Draft Design for a Text/Graphics Protocol ๐จ- Proposed as a synthesis of existing ideas rather than an attempt to put forth new ones. It draws on the concerns about the lack of text-handling capabilities of the protocol suggested in RFC 493. Remix era, not a new song. ๐ถ
- 552 ยท
OwenยทJul 73ยท Single Access to Standard Protocols ๐ช- Queries and statements about a socket number assignment for a single access protocol before the proposed mail protocol becomes official. Who gets the door, and when? ๐ค
- 551 ยท
FeinrothยทAug 73ยท NYU, ANL, and LBL Joining the Net ๐- Announces the intent of several Atomic Energy Commission installations to enter the network. Guest list expanding! ๐ฅณ
- 550 ยท
DeutschยทAug 73ยท NIC NCP Experiment ๐งช- Statistics on total incoming messages, incoming host-host control opcodes, and size of outgoing messages. Data is the new tea. ๐ซ
- 549 ยท
MichenerยทJul 73ยท Minutes of Network Graphics Group Meeting ๐ผ๏ธ- Describes a graphics meeting held in July 1973. Pretty pictures, pretty notes. ๐ธ
- 548 ยท
WaldenยทAug 73ยท Hosts Using the IMP Going Down Message ๐- Discusses the use and intention of the ARPANET IMP's "going down" message. Warning, but make it polite. ๐
- 547 ยท
WaldenยทAug 73ยท Change to the Very Distant Host Specification ๐- A document on a new version of figure F-4 for BBN Report 1822. Fresh figure, fresh look. โจ
- 546 ยท
ThomasยทAug 73ยท Tenex Load Averages for July 1973 โ๏ธ- Reports on the load on two of the key service computers on the ARPANET. Keeping the vibes balanced. ๐งโโ๏ธ
- 545 ยท
PickensยทJul 73ยท Of What Quality be the UCSB Resource Evaluators? ๐ง- This memo is in response to RFC 531. Respectfully side-eyeing the evaluators. ๐
- 544 ยท
MeyerยทJul 73ยท Locating On-Line Documentation at SRI-ARC ๐บ๏ธ- An updated memo on how to access on-line documentation at the NIC. Map to the docs, bestie. ๐
- 543 ยท
MeyerยทJul 73ยท Network Journal Submission and Delivery ๐ฐ- Announces that the first implementation of a Network Journal Submission and Delivery system is now experimentally up. Journal drop, live! ๐ฅ
- 542 ยท
NeigusยทJul 73ยท File Transfer Protocol ๐- States there are considerable changes from the last "official" version of FTP, but the gross structure still remains the same. References RFCs 354, 454, and 495. A glow-up with the same bones. ๐
- 541 ยท Never Issued. ๐ซฅ
- 540 ยท Never Issued. ๐ซฅ
- 539 ยท
CrockerยทJul 73ยท Thoughts on the Mail Protocol Proposed in RFC 524 ๐ง- Responds to RFC 524. The authors feel the protocol is extremely rich, but there are some minor and some major problems. Love it, but we need to talk. ๐ซถ
- 538 ยท
McKenzieยทJul 73ยท Traffic Statistics ๐- A report on the Host traffic statistics for the month of June 1973. Updates RFC 522. Stats, served hot. ๐ฅ
- 537 ยท
BunchยทJun 73ยท Announcement of NGG Meeting ๐ฃ- Arrangement details for a graphics meeting held July 1973. See RFC 549. Save the date! ๐
- 536 ยท Never Issued. ๐ซฅ
- 535 ยท
ThomasยทJul 73ยท Comments on File Access Protocol ๐ฌ- This memo is in response to RFC 420. Commentary with receipts. ๐งพ
- 534 ยท
WaldenยทJul 73ยท Lost Message Detection ๐ต๏ธโโ๏ธ- Presents three suggestions for detecting the loss of messages by the communications subsystem. Missing messages, found. โจ
- 533 ยท
WaldenยทJul 73ยท Message-ID Numbers ๐ข- Notice that the ARPANET link field of 8-bits has been expanded to 12-bits and renamed the message-id field. Bigger field, same energy. ๐ฆ
- 532 ยท
MerrymanยทJul 73ยท The UCSD-CC Server-FTP Facility ๐ฅ๏ธ- A description of the FTP service at UCSD. Their server, their rules. ๐
- 531 ยท
PadlipskyยทJun 73ยท Feast or Famine? - A Response to Two Recent RFC's About Network Information ๐ฝ๏ธ- This memo is in response to RFCs 514 and 519. Feast mode, or famine mode? You decide. ๐
- 530 ยท
BhushanยทJun 73ยท A Report on the SURVEY Project ๐ง
The paper's whole purpose is 1) to share where the SURVEY project and its data stand, 2) to tell the ARPANET crew what services come with it, 3) to spill the plans for what's next, and 4) to ask everyone for suggestions and improvements ๐ซถ
529 ยท McKenzie ยท Jun 73 ยท A Note on Protocol Synch Sequences
A response to RFC 513. ๐ฌ
528 ยท McQuillan ยท Jun 73 ยท Software Checksumming in the IMP and Network Reliability
This one walks through some recent changes made to the IMP and TIP programs. Network reliability glow-up ๐ฅ
527 ยท Merryman ยท Jun 73 ยท ARPAWOCKY
A parody by D. L. Covill of the ARPANET, based on the Jabberwocky of Lewis Carroll. The poetry era is undefeated ๐ง
526 ยท Pratt ยท Jun 73 ยท Technical Meeting - Digital Image Processing Software Systems
An announcement of a technical meeting on digital image processing software systems. Bring your best image-processing fit ๐ธ
525 ยท Parrish ยท Jun 73 ยท MIT-Mathlab Meets UCSB-OLS
This one describes solving problems with both the MIT-P1ACSYM system and the UCSB-OLS system. It's a whole crossover episode ๐
524 ยท White ยท Jun 73 ยท A Proposed Mail Protocol
A proposed specification for handling mail across the ARPA network. Mail, but make it a protocol ๐
523 ยท Bhushan ยท Jun 73 ยท SURVEY is in Operation Again
This RFC is here to tell the network community that the survey program on the MIT-DMCG computer system is up and running again. We're so back ๐ฆ
522 ยท McKenzie ยท Jun 73 ยท Traffic Statistics
A report on Host traffic statistics for May 1973. This one updates RFC 509. ๐
521 ยท McKenzie ยท May 73 ยท Restricted Use of IMP DDT
This proposes restricting how IMP DDT gets used. Several sites felt that uncontrolled use made access control mechanisms too easy to intercept or tamper with, so, not it ๐ โโ๏ธ
520 ยท Day ยท Jun 73 ยท Memo to FTP Group (Proposal for File Access Protocol)
This document looks at the File Access Protocol as an extension to FTP. FTP glow-up arc ๐
519 ยท Pickens ยท Jun 73 ยท Resource Evaluation
UCSB announces a new test group based on RFC 369. The group digs into specific network resources and works toward initial site dependent and function dependent MINIMAN's. Resource-hunting era ๐ธ
518 ยท Feinler ยท Jun 73 ยท ARPANET Accounts
A memo with info on opening an account at a given site on the ARPANET. Account setup, done โ
517 ยท Never Issued.
Not a single word, not a single RFC. Ghosted by history ๐ป
516 ยท Postel ยท May 73 ยท Lost Message Detection
This RFC is replaced by RFC 534. Plot twist, read the new one ๐
515 ยท Winter ยท Jun 73 ยท Specifications for Datalanguage, Version 0/9
Honest tea: this Datalanguage spec is extremely primitive ๐ But Version 0/9 is already running at CCA, and it's a chance to get hands-on experience with the Datacomputer and the basic Datalanguage concepts. Baby steps are still steps ๐
514 ยท Kantrowitz ยท Jun 73 ยท Network Make-Work
Updates RFC 459. ๐ง
513 ยท Hathaway ยท May 73 ยท Comments on the New Telnet Specifications
A discussion of the Telnet Protocol. Telnet, the iconic one ๐
512 ยท Hathaway ยท May 73 ยท Lost Message Detection
This RFC is replaced by RFC 534. Same drama as 516, different author ๐
511 ยท North ยท May 73 ยท Enterprise Phone Service to NIC From ARPANET Sites
A look at the cost and the alternatives for special telephone numbers for the NIC. Ringing up the budget committee ๐
510 ยท White ยท May 73 ยท Request for Network Mailbox Addresses
This one announces that the NIC is delivering the Network Journal, and asks for updated or additional network mailbox addresses. Send your addresses in, bestie ๐ฌ
509 ยท McKenzie ยท May 73 ยท Traffic Statistics
A report on Host traffic statistics for April 1973. This one updates RFC 497. ๐
508 ยท Pfeifer ยท May 73 ยท Real-Time Data Transmission on the ARPANET
A discussion of the pros and cons of supporting real-time processes on the ARPA Network. Real-time is giving high stakes ๐ณ
507 ยท Never Issued.
Gone before it got started. Bestie, the vanishing act is iconic ๐ซฅ
506 ยท Padlipsky ยท Jun 73 ยท An FTP Command Naming Problem
This RFC points out a problem with the File Transfer Protocol: the names chosen for two crucial commands are faulty. Naming is hard, and the group chat has notes ๐
505 ยท Padlipsky ยท Jun 73 ยท Two Solutions to a File Transfer Access Problem
This memo responds to RFCs 487 and 501. Two solutions, zero drama ๐
504 ยท Thomas ยท May 73 ยท Workshop Announcement
Detailed plans for a workshop on Automated Resource Sharing, held in May 1973. Workshop szn ๐
503 ยท Neigus ยท Apr 73 ยท Socket Number List
This RFC has been replaced by RFCs 997 and 990. Upgrade time ๐ฆ
502 ยท Never Issued.
Ghost RFC number, spotted it ๐ป
501 ยท Pogran ยท May 73 ยท Un-Muddling "Free File Transfer"
A response to RFC 487, where the muddle gets sorted out ๐งน
500 ยท Shoshani ยท Apr 73 ยท The Integration of Data Management Systems on a Computer Network
This paper focuses on one approach to integrating data management systems on a computer network so that data can be shared. Five hundred and iconic ๐
499 ยท Reussow ยท Apr 73 ยท Harvard's Network RJE
A description of the remote job entry service at Harvard. Crimson-coded remote jobs ๐
498 ยท Braden ยท Apr 73 ยท On Mail Service to CCN
A description of the electronic mail service at UCLA-CCN. Mail with a West Coast accent ๐
497 ยท McKenize ยท Apr 73 ยท Traffic Statistics
A report on Host traffic statistics for March 1973. This one updates RFC 482. ๐
496 ยท Auerbach ยท Apr 73 ยท A TNLS Quick Reference Card is Available
Announcing a new TNLS Quick Reference Card. Cheat sheet unlocked ๐
495 ยท McKenize ยท May 73 ยท Telnet Protocol Specification
The results of an open meeting about Telnet, with two attached documents reporting what came out of it. Open meeting, real outcomes ๐ซถ
494 ยท Walden ยท Apr 73 ยท Availability of MIX and MIXAL in the Network
A list of hosts that support programming in MIX and MIXAL. Who knew the network had this many MIX fans? ๐ง
993 ยท Michener ยท Apr 73 ยท Graphics Protocol
This one covers the opinions and decisions from the second meeting of the Network Graphics Group. Graphics, but make it a group decision ๐จ
492 ยท Meyer ยท Apr 73 ยท Response to RFC 467
A short description of the problems and proposed solutions, plus comments and alternative suggestions in response to RFC 467. Respectfully, the alternatives are giving ๐
491 ยท Padlipsky ยท Apr 73 ยท What is "Free"?
This memo digs into the claim that network mail should be free, meaning no login or USER command should be required. The free mail debate is LIVE ๐
490 ยท Pickens ยท Mar 73 ยท Surrogate RJS for UCLA-CCN
A description of how UCLA's RJS can be reached from UCSB's standard remote job entry service. Surrogate energy ๐ธ
489 ยท Postel ยท Mar 73 ยท Comment on Resynchronization of Connection Status Proposal
Comments on ideas proposed in RFC 467. Postel showing up with the notes ๐
488 ยท Auerbach ยท Mar 73 ยท NLS Classes at Network Sites
This RFC asks the network community whether on-site classes are wanted. Class is in session ๐
487 ยท Bressler ยท Mar 73 ยท Host-Dependent FTP Parameters
This memo responds to RFC 430. Parameter drama continues ๐ญ
486 ยท Bressler ยท Apr 73 ยท Data Transfer Revisited
A proposal to base RJE and FTP on a common data transfer protocol. One protocol to rule them all ๐
485 ยท Pickens ยท Mar 73 ยท MIX and MIXAL at UCSB
A response to Walden's MIX query (RFC 473). MIX queries get answers ๐ค
484 ยท Never Issued.
Vanished, no notes. Iconic in its own way ๐ซฅ
483 ยท Kudlick ยท Mar 73 ยท Cancellation of the Resource Notebook Famework Meeting
No abstract given, so the meeting is officially cancelled ๐ โโ๏ธ
482 ยท McKenzie ยท Mar 73 ยท Traffic Statistics
A report on Host traffic statistics for February 1973. This one updates RFC 455. ๐
481 ยท Never Issued.
Another empty slot in the lineup ๐ป
480 ยท White ยท Mar 73 ยท Host-Dependent FTP Parameters
This memo responds to RFC 430. Same parameter saga, new author ๐
479 ยท White ยท Mar 73 ยท Use of FTP by the NIC Journal
This RFC lays out how the NIC described its requirements for putting FTP to work on Journal delivery and submission. Requirements arc, unlocked ๐
478 ยท Bressler ยท Mar 73 ยท FTP Server-Server Interaction - II
This discusses server-to-server interaction in a typical situation: a user talking to two servers wants to grab a file from one site and send it to another. Three-way FTP is so main character ๐ฌ
477 ยท Krilanovich ยท May 73 ยท Remote Job Service at UCSB
This RFC is the follow-up to RFC 436. It restates the essentials of the official RJE Protocol, then documents UCSB's implementation of it in detail. It also obsoletes RFC 436, so, sorry 436 ๐
476 ยท McKenzie ยท Mar 73 ยท IMP/TIP Memory Retrofit Schedules (Revision 2)
Plans and a schedule for upgrading IMPs and TIPs. Retrofit era has arrived โฐ
475 ยท Bhushan ยท Mar 73 ยท FTP and the Network Mail System
The author shares their understanding of what came out of the Network Mail System meeting, and what it means for FTP. Mail and FTP, the power couple ๐
474 ยท Bunch ยท Mar 73 ยท Announcement of Forthcoming Meeting of the Network Graphics Working Group and Call for RFC's.
Plans for a graphics meeting in May 1973, plus a call for RFCs. Graphics and RFCs, let's gooo ๐จ
473 ยท Walden ยท Feb 73 ยท MIX and MIXAL?
No abstract given, just the question. Asking the important questions ๐ค
472 ยท Bunch ยท Mar 73 ยท Illinois' Reply to Maxwell's Request for Graphics Information
This RFC is the author's response to NIC document 14925. Illinois showing up with receipts ๐
471 ยท Thomas ยท Mar 73 ยท Announcement of a (Tenative) Workshop on Multi-Site Executive Programs
A suggestion for a workshop, plus a query to see who's interested. Who's in? ๐โโ๏ธ
470 ยท Thomas ยท Mar 73 ยท Change in Socket for TIP News Facility
No abstract given, so the socket change speaks for itself ๐
469 ยท Kudlick ยท Mar 73 ยท Network Mail Meeting Summary
A description of a mail meeting held in February 1973. Meeting recap, served ๐ต
468 ยท Braden ยท Mar 73 ยท FTP Data Compression
This RFC defines the "HASP" or compressed mode. Squeeze it, squeeze it ๐๏ธ
467 ยท Burchfiel ยท Feb 73 ยท Proposed Change to Host-Host Protocol Resynchronization of Connection Status
To get resynchronization of allocation working, this RFC proposes adding two commands to the host-host protocol. Two new commands, one big glow-up โจ
466 ยท Winett ยท Feb 73 ยท Telnet Logger/Server for Host LL-67
Writeup documents for the Telnet Logger/Server on the CP/CMS system on the Lincoln Laboratory 360/67. Vintage hardware, modern vibes ๐ฅ๏ธ
465 ยท Never Issued.
Didn't make it out the door ๐ป
464 ยท Kudlick ยท Feb 73 ยท Resource Notebook Framework
This document presents a framework for coordinating all the surveys and data-gathering efforts around "resource notebook" style information. Organized bestie, I love to see it ๐
463 ยท Bhushan ยท Feb 73 ยท FTP Comments and Response to RFC 430
The author responds to RFC 430 and other similar views. Ratio'd, respectfully ๐
462 ยท Iseli ยท Feb 73 ยท Responding to User Needs
A proposal to have network documentation maintained at the source, meaning by each site, and made available as a distributed database. Docs straight from the source ๐
461 ยท McKenzie ยท Feb 73 ยท Telnet Meeting Announcement
Plans for a Telnet meeting in March 1973. Telnet, but make it a calendar event ๐
460 ยท Kline ยท Feb 73 ยท NCP Survey
This is the first in a series of RFCs requesting information on how the host-to-host protocol is implemented. Part one of the saga begins ๐ฌ
459 ยท Kantrowitz ยท Feb 73 ยท Network Questionnaires
Suggests that there's too much going on, or too many different people trying to gather data from all the other sites. ๐ฉ
- 458 ยท Bressler ยท Feb 73 ยท Mail Retrieval via FTP ๐ฌ Bressler proposes two brand-new FTP commands,
ReaDMailFileandReaDMail. ๐ - 457 ยท Walden ยท Feb 73 ยท TIPUG ๐ Walden explains how to get updates to the TIP Users Guide.
- 456 ยท NIC ยท Feb 73 ยท Memorandum โฐ The meeting time changes for the Network Mail meeting discussed in RFC 453.
- 455 ยท McKenzie ยท Feb 73 ยท Traffic Statistics ๐ Host traffic stats for January 1973. Updates RFC 443.
- 454 ยท McKenzie ยท Feb 73 ยท File Transfer Protocol (Meeting Announcement and a New Proposed Document ๐๏ธ The File Transfer Protocol gets specified, and there's an announcement for a March 1973 meeting to discuss it.
- 453 ยท Kudlick ยท Feb 73 ยท Meeting Announcement to Discuss a Network Mail System ๐ Plans for an electronic mail meeting held in February 1973. See RFC 469.
- 452 ยท Winett ยท Feb 73 ยท Telnet Command at Host LL ๐ฅ๏ธ Documents how to use the Telnet command at Host LL for CP/CMS time-sharing system uses.
- 451 ยท Padlipsky ยท Feb 73 ยท Tentative Proposal for a Unified User Level Protocol ๐ฌ The idea of a network standard command language for interactive systems, served up as a suggestion.
- 450 ยท Padlipsky ยท Feb 73 ยท Multics Sampling Timeout Change โจ Better service announced for experimental users of MIT Multics.
- 449 ยท Walden ยท Jan 73 ยท The Current Flow-Control Scheme for IMPSYS ๐ Updates RFC 442.
- 448 ยท Braden ยท Feb 73 ยท Print Files in FTP ๐จ๏ธ Reviews the problem of print files.
- 447 ยท McKenzie ยท Jan 73 ยท IMP/TIP Memory Retrofit Schedule ๐ ๏ธ Updates RFC 434.
- 446 ยท Deutsch ยท Jan 73 ยท Proposal to Consider a Network Program Resource Notebook ๐
- 445 ยท McKenzie ยท Jan 73 ยท IMP/TIP Preventive Maintenance Schedule ๐งฐ
- 444 ยท Never Issued. ๐ซฅ
- 443 ยท McKenzie ยท Jan 73 ยท Traffic Statistics ๐ Host traffic stats for December 1972. Updates RFC 422.
- 442 ยท Cerf ยท Jan 73 ยท The Current Flow-Control Scheme for IMPSYS ๐ Discusses the current flow-control scheme for IMPSYS.
- 441 ยท Bressler ยท Jan 73 ยท Inter-Entity Communication - An Experiment ๐ฌ A status report on an experiment built on users wanting to chat with each other from their consoles and get some debugging help. ๐
- 440 ยท Walden ยท Jan 73 ยท Scheduled Network Software Maintenance โณ Lays out the plans and schedule for IMP software maintenance, and expands the normal time slot.
- 439 ยท Cerf ยท Jan 73 ยท PARRY Encounters the Doctor ๐ค A lighthearted write-up of a session that actually happened on September 18, 1972. ๐ฉบ
- 438 ยท Thomas ยท Jan 73 ยท FTP Server-Server Interaction ๐ค A simple FTP extension that lets a user's FTP process at one site arrange for FTP server processes at other sites to work together on its behalf.
- 437 ยท Faeh ยท Jun 73 ยท Data Reconfiguration Service at UCSB ๐ฃ The Data Reconfiguration Service (DRS) is now available at UCSB.
- 436 ยท Krilanovich ยท Jan 73 ยท Announcement of RJS at UCSB ๐ฃ RJS is now available at UCSB.
- 435 ยท Cosell ยท Jan 73 ยท Telnet Issues ๐ A bunch of Telnet issues, with the big drama being echoing.
- 434 ยท McKenzie ยท Jan 73 ยท IMP/TIP Memory Retrofit Schedule ๐ ๏ธ Explains plans and schedule for IMP and TIP upgrades.
- 433 ยท Postel ยท Dec 72 ยท Socket Number List ๐ Assigned socket numbers for public functions get established here. This RFC has been replaced by RFC 997 and 990.
- 432 ยท Neigus ยท Dec 72 ยท Network Logical Map ๐บ๏ธ Attaches the network logical map as of December 30, 1972.
- 431 ยท Krilanovich ยท Dec 72 ยท Update on SMFS Login and Logout ๐ This doc obsoletes RFC 399, which introduced the Login and Logout commands for UCSB's SMFS but was incomplete. RFC 399 is restated more fully in this RFC.
- 430 ยท Braden ยท Feb 73 ยท Comments on File Transfer Protocol ๐ง Discusses several FTP issues.
- 429 ยท Postel ยท Dec 72 ยท Character Generator Process ๐ค A proposal for a standard process, implemented on whatever hosts want it, that generates character data without any regard to input.
- 428 ยท Never Issued. ๐ซฅ
- 427 ยท Never Issued. ๐ซฅ
- 426 ยท Thomas ยท Jan 73 ยท Reconnection Protocol ๐ Describes several situations where being able to reconnect is useful, presents a mechanism to achieve reconnections, sketches how it could be added to the Host-Host or Telnet protocol, and recommends a place for it in the protocol hierarchy.
- 425 ยท Bressler ยท Dec 72 ยท "But my NCP costs $500 a day..." ๐ธ Discussion on the cost of network software and network use.
- 424 ยท Never Issued. ๐ซฅ
- 423 ยท Noble ยท Dec 72 ยท UCLA Campus Computing Network Liaison Staff for ARPA Network ๐ A list of ARPA network contacts at CCN. Updates RFC 389.
- 422 ยท McKenzie ยท Dec 72 ยท Traffic Statistics ๐ Host traffic stats for November 1972. Updates RFC 413.
- 421 ยท McKenzie ยท Nov 72 ยท A Software Consulting Service for Network Users ๐งโ๐ป Announces a BBN software consulting service set up for ARPA network users.
- 420 ยท Murray ยท Jan 73 ยท CCA ICCC Weather Demo โ๏ธ The weather demo for the ICCC show is now generally available.
- 419 ยท Vezza ยท Dec 72 ยท MIT-DMS on Vacation ๐๏ธ The MIT Dynamic Modeling System will be down for 2-4 weeks.
- 418 ยท Hathaway ยท Nov 72 ยท Server File Transfer Under TSS/360 at NASA/Ames Research Center ๐ Describes the initial implementation of Server File Transfer at NASA-Ames Research Center.
- 417 ยท Postel ยท Nov 72 ยท LINK Usage Violation ๐ The protocol police issue a citation.
- 416 ยท Norton ยท Nov 72 ยท The ARC System will be Unavailable for Use During Thanksgiving Week ๐ฆ The SRI-ARC machine will be down for 9-10 days.
- 415 ยท Murray ยท Nov 72 ยท TENEX Bandwidth ๐ถ Considers the performance of each host. References RFC 392.
- 414 ยท Bhushan ยท Nov 72 ยท File Transfer Protocols (FTP) Status and Further Comments ๐ก A status report on working server and user FTPs.
- 413 ยท McKenzie ยท Nov 72 ยท Traffic Statistics ๐ Three sets of network traffic statistic reports. Updates RFC 400.
- 412 ยท Hicks ยท Nov 72 ยท User FTP Documentation ๐ A "help" file for the Utah-10 implementation of the User FTP process.
- 411 ยท Padlipsky ยท Nov 72 ยท New Multics Network Software Features โจ Discusses two recently installed features of the Multics network software.
- 410 ยท McQuillan ยท Nov 72 ยท Removal of the 30-Second Delay When Hosts Come Up โฑ๏ธ Proposes getting rid of the 30-second delay altogether.
- 409 ยท White ยท Dec 72 ยท TENEX Interface to UCSB's Simple-Minded File System ๐ป Gives users the info they need to use SMFS from a terminal. The reader is assumed to be familiar with Tenex.
- 408 ยท Owen ยท Oct 72 ยท NETBANK ๐ฆ A proposed protocol (or service) to help new users get going on the network.
- 407 ยท Bressler ยท Oct 72 ยท Remote Job Entry Protocol ๐ The official Remote Job Entry Protocol release, per the ARPA office.
- 406 ยท McQuillan ยท Oct 72 ยท Scheduled IMP Software Releases ๐๏ธ Explains plans and schedule for IMP software maintenance.
- 405 ยท McKenzie ยท Oct 72 ยท Correction to RFC 404 โ๏ธ Typographical error notation. Obsoletes RFC 404.
- 404 ยท McKenzie ยท Oct 72 ยท Host Address Changes Involving Rand and ISI ๐ ISI's new address is IMP 22, and RAND's new address is IMP 7.
d
- 403 ยท Hicks ยท Jan 73 ยท Desirability of a Network 1108 Service ๐ง
- 402 ยท NIC ยท Oct 72 ยท ARPA Network Mailing Lists ๐ฌ Obsoletes RFC 363.
- 401 ยท Hansen ยท Oct 72 ยท Conversion of NGP-0 Coordinates to Device Specific Coordinates ๐งฎ Describes a way to convert NGP coordinates to integer coordinates in the range zero to M, where M is the maximum address of the device screen on a machine using 2's complement arithmetic.
- 400 ยท McKenzie ยท Oct 72 ยท Traffic Statistics ๐ Host traffic stats for September 1972. Updates RFC 391.
- 399 ยท Krilanovich ยท Sep 72 ยท SMFS Login and Logout ๐
- 398 ยท Pickens ยท Sep 72 ยท UCSB Online Graphics ๐จ Users with Tektronix or IMLAC terminals, or with systems that support the proposed Level 0 graphics protocol, can access UCSB graphics.
- 397 ยท Never Issued. ๐ซฅ
- 396 ยท Bunch ยท Nov 72 ยท Network Graphics Working Group Meeting - Second Iteration ๐ผ๏ธ
- 395 ยท McQuillan ยท Oct 72 ยท Switch Settings on IMPs and TIPs ๐๏ธ Discusses the switches on the front panel of IMPs and TIPs that are important to the correct operation of the network software.
- 394 ยท McQuillan ยท Sep 72 ยท Two Proposed Changes to the IMP-HOST Protocol ๐ง Updates RFC 381. Describes two changes to the IMP-Host communication protocol described in BBN Report 1822.
- 393 ยท Winett ยท Oct 72 ยท Comments on Telnet Protocol Changes ๐ โโ๏ธ Comments and objections to two of the three recent suggestions for changing the Telnet protocol described in RFC 328.
- 392 ยท Hicks ยท Sep 72 ยท Measurement of Host Costs for Transmitting Network Data ๐ฐ Discusses Utah's program to use the Remote Job Service System (RJS) at UCLA-CCN alongside Utah's "batch" users.
- 391 ยท McKenzie ยท Sep 72 ยท Traffic Statistics ๐ Host traffic stats for August 1972. Updates RFC 378.
- 390 ยท Braden ยท May 72 ยท TSO Scenario Batch Compilation and Foreground Execution ๐ฅ๏ธ An example session with TSO on UCLA-CCN.
- 389 ยท Noble ยท Aug 72 ยท UCLA Campus Computing Network Liaison Staff for ARPA Network ๐ A list of ARPA Network contacts at UCLA/CCN.
- 388 ยท Cerf ยท Aug 72 ยท NCP Statistics ๐
388 (see above)
387 Kelley Aug 72 Some Experiences in Implementing
Network Graphics Protocol Level 0
386 Cosell Aug 72 Letter to TIP Users - 2
385 Bhushan Aug 72 Comments on the File Transfer
Protocol (RFC 354)
384 North Aug 72 Official Site IDENTS for
Organizations in the ARPA Network
383 Never Issued.
382 McDaniel Aug 72 Mathematical Software on the ARPA
Network
381 McQuillan Jul 72 Three Aids to Improved Network
Operation
380 Never Issued.
379 Braden Aug 72 Using TSO at CCN
378 McKenzie Aug 72 Traffic Statistics
377 Braden Aug 72 Using TSO Via ARPA Network Virtual
Terminal
376 Westheimer Aug 72 Network Host Status
375 Never Issued.
374 McKenzie Jul 72 IMP System Announcement
373 McCarthy Jul 72 Arbitrary Character Sets
372 Watson Jul 72 Notes on a Conversation with Bob
Kahn on the ICCC
371 Kahn Jul 72 Demonstration at International
Computer Communications Conference
370 Westheimer Jul 72 Network Host Status
369 Pickens Jul 72 Evaluation of ARPANET Services
(January through March, 1972)
368 Braden Jul 72 Comments on "Proposed Remote Job
Entry Protocol"
367 Westheimer Jul 72 Network Host Status
366 Westheimer Jul 72 Network Host Status
365 Walden Jul 72 A Letter to All TIP Users
364 Abrams Jul 72 Serving Remote Users on the ARPANET
363 NIC Aug 72 ARPA Network Mailing Lists
362 Westheimer Jun 72 Network Host Status
361 Bressler Jul 72 In Response to RFCs 347 and 348
360 Holland Jun 72 Proposed Remote Job Entry Protocol
359 Walden Jun 72 The Status of the Release of the New
IMP System (2600)
358 Never Issued.
357 Davidson Jun 72 An Echoing Strategy for Satellite
Links
356 Alter Jun 72 ARPA Network Control Center
355 Davidson Jun 72 Response to RFC 346
354 Bhushan Jul 72 The File Transfer Protocol
353 Westheimer Jun 72 Network Host Status
352 Crocker Jun 72 TIP Site Information Form (Graphics)
351 Crocker Jun 72 (Graphics) Information Form for the
ARPANET Graphics Resources Notebook
350 Stoughton May 72 User Accounts for UCSB On-Line
System
349 Postel May 72 Proposed Standard Socket Numbers
348 Postel May 72 Discard Process
347 Postel May 72 Echo Process
346 Postel May 72 Satellite Considerations
345 Kelly May 72 Interest in Mixed Integer
Programming (MPSX on 360/91 at CCN)
344 Westheimer May 72 Network Host Status
343 McKenzie May 72 IMP System Change Notification
342 Westheimer May 72 Network Host Status
341 Never Issued.
340 O'Sullivan May 72 Proposed Telnet Changes
339 Thomas May 72 MLTNET - A "Multi-Telnet" Subsystem
for TENEX
338 Braden May 72 EBCDIC/ASCII Mapping for Network RJE
337 Never Issued.
336 Cotton May 72 Level 0 Graphic Input Protocol
335 Bryan May 72 New Interface-IMP/360
334 McKenzie May 72 Network Use on May 8
333 Bressler May 72 A Proposed Experiment with a Message
Switching Protocol
332 Westheimer Apr 72 Network Host Status
331 McQuillan Apr 72 IMP System Change Notification
330 Westheimer Apr 72 Network Host Status
329 NIC May 72 ARPA Network Mailing Lists
328 Postel Apr 72 Suggested Telnet Protocol Changes
327 Bhushan Apr 72 Data and File Transfer Workshop
Notes
326 Westheimer Apr 72 Network Host Status
325 Hicks Apr 72 Network Remote Job Entry Program -
NETRJS
324 Postel Apr 72 RJE Protocol Meeting
323 Cerf Mar 72 Formation of Network Measurement
Group (NMG)
322 Cerf Mar 72 Well Known Socket Numbers
321 Karp Mar 72 CBI Networking Activity at MITRE
320 Reddy Mar 72 Workshop on Hard Copy Line Graphics
319 Westheimer Mar 72 Network Host Status
318 Postel Apr 72 Ad Hoc Telnet Protocol
317 Postel Mar 72 Official Host-Host Protocol
Modification: Assigned Link Numbers
316 McKay Feb 72 ARPA Network Data Management Working
Group Meeting ReportOkay bestie, so the bit at the very top is the tail end of RFC 388 ๐ฆ It says it Updates RFC 323 and it's UCLA/NMC announcing they're ready to gather NCP statistics every single day ๐โจ
- 387, Kelley: Some Experiences in Implementing Network Graphics Protocol Level 0 ๐ Just a real-life diary of implementing it ๐
- 386, Cosell: Letter to TIP Users - 2 ๐ A second follow-up note for TIP users. It Updates RFC 365 ๐ธ
- 385, Bhushan: Comments on the File Transfer Protocol (RFC 354) ๐ง Errata, more discussion, emphasis points, and extra additions to the protocol ๐ซถ It Updates RFC 354 ๐
- 384, North: Official Site IDENTS for Organizations in the ARPA Network ๐๏ธ Two lists in one go, alphabetical and sorted by site address ๐ฅ It Obsoletes RFC 289 ๐
- 383: Never Issued. ๐
- 382, McDaniel: Mathematical Software on the ARPA Network ๐งฎ Thoughts on building high quality libraries of math and stats subroutines ๐
- 381, McQuillan: Three Aids to Improved Network Operation ๐ Covers software maintenance schedules, IMP-to-Host communication, and network news service. Literally three helpers in one ๐
- 380: Never Issued. ๐
- 379, Braden: Using TSO at CCN ๐ IBM's Time Sharing Option is now running on a regular schedule at UCLA/CCN โจ
- 378, McKenzie: Traffic Statistics ๐ The traffic numbers for July 1972 ๐
- 377, Braden: Using TSO Via ARPA Network Virtual Terminal ๐ฆ TSO is available at UCLA/CCN on Socket 1, using the standard Telnet protocol. Iconic ๐ญ
- 376, Westheimer: Network Host Status ๐ฐ๏ธ Status of Network Hosts from July 31 to August 4. It Updates RFC 370 ๐
- 375: Never Issued. ๐
- 374, McKenzie: IMP System Announcement ๐ฃ It Updates RFCs 331,343,359 ๐ฅ
- 373, McCarthy: Arbitrary Character Sets ๐ธ How to store any character set in computers and then show it on any CRT, type it with any keyboard, and print it on any printer. Main character energy ๐
- 372, Watson: Notes on a Conversation with Bob Kahn on the ICCC ๐ Some talk about aspects of the ICCC meeting demo ๐ฌ
- 371, Kahn: Demonstration at International Computer Communications Conference ๐ Observations and notes on that ICCC demo โจ
- 370, Westheimer: Network Host Status ๐ฐ๏ธ Status from July 17 to July 28. It Updates RFC 367 ๐
- 369, Pickens: Evaluation of ARPANET Services (January through March, 1972) ๐ Descriptions, surveys, critiques of ARPANET services, plus ideas for making them better. Honest and iconic ๐ซถ
- 368, Braden: Comments on "Proposed Remote Job Entry Protocol" ๐ก Suggestions for polishing the final RJE standard. It references RFC 360 ๐ง
- 367, Westheimer: Network Host Status ๐ฐ๏ธ Status from July 1 to July 16. It Updates RFC 366 ๐
- 366, Westheimer: Network Host Status ๐ฐ๏ธ Status from June 19 to June 30. It Updates RFC 362 ๐ธ
- 365, Walden: A Letter to All TIP Users ๐ New commands added to the "TIP Users Guide," explained ๐
- 364, Abrams: Serving Remote Users on the ARPANET ๐ฆ Says there's a real problem serving remote users, and offers some suggestions to make it better ๐
- 363, NIC: ARPA Network Mailing Lists ๐ฌ It Obsoletes RFC 329 ๐ฅ
- 362, Westheimer: Network Host Status ๐ฐ๏ธ Status from June 5 to June 16. It Updates RFC 353 โจ
- 361, Bressler: In Response to RFCs 347 and 348 ๐ About Deamon Processes on Host 106 ๐ง
- 360, Holland: Proposed Remote Job Entry Protocol ๐ This one sets out the Network's standard procedures for remote job entry, where a user in one place makes a batch job run somewhere else ๐ซถ
- 359, Walden: The Status of the Release of the New IMP System (2600) ๐ It Obsoletes RFC 343 ๐
- 358: Never Issued. ๐
- 357, Davidson: An Echoing Strategy for Satellite Links ๐ฐ๏ธ This one kills the delay from simple echoing, so the transmission delay only shows up as the cost of computation โจ It's an optional extra for existing User Telnets, and it needs a cooperating server process to actually work ๐ค
- 356, Alter: ARPA Network Control Center ๐ฐ๏ธ Announces the NCC's new operation schedule ๐
- 355, Davidson: Response to RFC 346 ๐ฌ
- 354, Bhushan: The File Transfer Protocol ๐ It obsoletes RFCs 264,265. FTP is for moving files between HOSTs on the ARPANET. Its main job is to transfer files efficiently and reliably, and to make remote file storage easy to use ๐ Iconic protocol behaviour ๐ญ
- 353, Westheimer: Network Host Status ๐ฐ๏ธ Status of most Network Hosts from May 22 to June 2. It Updates RFC 344 ๐
- 352, Crocker: TIP Site Information Form (Graphics) ๐ An info form with extra details for TIP users of the NET ๐
- 351, Crocker: (Graphics) Information Form for the ARPANET Graphics Resources Notebook ๐จ A questionnaire about what graphics resources different sites have ๐
- 350, Stoughton: User Accounts for UCSB On-Line System ๐ New login parameters for the UCSB On-Line System ๐
- 349, Postel: Proposed Standard Socket Numbers ๐ A proposal to officially standardise socket number assignments ๐ง
- 348, Postel: Discard Process ๐๏ธ Debugging and measurement for hosts willing to build a "Discard" process. This is the old version, so see RFC 863 instead ๐
- 347, Postel: Echo Process ๐ Same deal with the "Echo" process for debugging and measurement. Old version, so see RFC 862 โจ
- 346, Postel: Satellite Considerations ๐ฐ๏ธ Talks about using space satellite links in the ARPANET ๐
- 345, Kelly: Interest in Mixed Integer Programming (MPSX on 360/91 at CCN) ๐งฎ Looking for interested folks to contact the author ๐
- 344, Westheimer: Network Host Status ๐ฐ๏ธ Updates RFC 342 ๐
- 343, McKenzie: IMP System Change Notification ๐ฃ It Obsoletes RFC 331. The IMPSYS 2600 release didn't work out ๐ญ
- 342, Westheimer: Network Host Status ๐ฐ๏ธ Updates RFC 332 ๐
- 341: Never Issued. ๐
- 340, O'Sullivan: Proposed Telnet Changes ๐ A change to Telnet that asks for one standard protocol and drops the idea of a minimum implementation ๐ซถ
- 339, Thomas: MLTNET - A "Multi-Telnet" Subsystem for TENEX ๐งฉ A Telnet-like facility for Tenex that lets a user control a bunch of jobs running on different ARPANET hosts. It's currently a subsystem on the BBN-Tenex host ๐ธ
- 338, Braden: EBCDIC/ASCII Mapping for Network RJE ๐ค This one suggests telling all NETRJS users about the changed ASCII mapping, raising the issue with the Network RJE Protocol committee, and supporting Joel Winett's pioneering work in this area ๐
- 337: Never Issued. ๐
- 336, Cotton: Level 0 Graphic Input Protocol ๐ฑ๏ธ A description of the graphics input protocol, as discussed at a Network Graphics Working Group meeting ๐จ
- 335, Bryan: New Interface-IMP/360 ๐ Announces a new interface, and asks folks to report any trouble they run into while using UCSB ๐
- 334, McKenzie: Network Use on May 8 ๐
- 333, Bressler: A Proposed Experiment with a Message Switching Protocol ๐งช Sketches how the lowest level host-host protocol in the ARPANET could be organised around Message Switching Protocols (MSPs), and how that would change host software ๐
- 332, Westheimer: Network Host Status ๐ฐ๏ธ Updates RFC 330 ๐
- 331, McQuillan: IMP System Change Notification ๐ฃ Announces the release of IMPSYS 2600 ๐
- 330, Westheimer: Network Host Status ๐ฐ๏ธ Updates RFC 326 ๐
- 329, NIC: ARPA Network Mailing Lists ๐ฌ
- 328, Postel: Suggested Telnet Protocol Changes ๐ Proposes some changes to the Telnet protocol โจ
- 327, Bhushan: Data and File Transfer Workshop Notes ๐
- 326, Westheimer: Network Host Status ๐ฐ๏ธ Updates RFC 319 ๐
- 325, Hicks: Network Remote Job Entry Program - NETRJS ๐ฅ๏ธ A report on NETRJS running at the University of Utah ๐
- 324, Postel: RJE Protocol Meeting ๐ Announces an RJE Protocol meeting at UCLA ๐
- 323, Cerf: Formation of Network Measurement Group (NMG) ๐ Describes some network measurement results, some plans for more measurement, and the formation of an interest group ๐
- 322, Cerf: Well Known Socket Numbers ๐ Announces plans to catalogue all the sockets that are supposed to be well-known ๐
- 321, Karp: CBI Networking Activity at MITRE ๐ฌ A response to RFC 313, with comments on Computer Based Instruction ๐ง
- 320, Reddy: Workshop on Hard Copy Line Graphics ๐จ๏ธ A one day workshop on the XCRIBL system at CMU ๐
- 319, Westheimer: Network Host Status ๐ฐ๏ธ Updates RFC 315 ๐
- 318, Postel: Ad Hoc Telnet Protocol ๐ซถ Obsoletes RFC 158. This Telnet specification worked well for several years ๐
- 317, Postel: Official Host-Host Protocol Modification: Assigned Link Numbers ๐ Lists the current Link number assignments. This RFC has been replaced by RFCs 997 and 990 ๐
- 316, McKay: ARPA Network Data Management Working Group Meeting Report ๐๏ธ
RFC 315 ยท Westheimer ยท Mar 72 ยท Network Host Status Okay bestie, this one updates RFC 306 ๐ so it's basically the next chapter of the host status saga ๐ธ
RFC 314 ยท Cotton ยท Mar 72 ยท Next Network Graphics Working Group Meeting Plans for a graphics meeting happening in April 1972 ๐จโจ
RFC 313 ยท O'Sullivan ยท Mar 72 ยท Computer Based Instruction Okay so this paper has two goals ๐ง . First, it's asking the NWG and everyone else for opinions on how different kinds of resources on a General Purpose Network could be used for Computer Based Instruction ๐. Second, it's trying to start a conversation between anyone who's interested in the whole Computer Base Instruction problem ๐ฌ. Brainy and iconic ๐
RFC 312 ยท McKenzie ยท Mar 72 ยท Proposed Change in IMP-to-Host Protocol This one proposes redefining the IMP-to-Host error message types and adding some brand new ones ๐จ. The goal is to help Hosts figure out what recovery action to take, without causing any serious reprogramming problems ๐ซถ (no one wants a reprogramming meltdown ๐)
RFC 311 ยท Bryan ยท Feb 72 ยท New Console Attachments to the UCSB Host Describes the types of terminals used at UCSB ๐ฅ๏ธ๐
RFC 310 ยท Bhushan ยท Apr 72 ยท Another Look at Data and File Transfer Protocols This paper suggests some specific changes to DTP and FTP ๐ฆ. The vibe is making them more useful and/or simpler to implement, which is giving clean glow-up energy โจ
RFC 309 ยท Bhushan ยท Mar 72 ยท Data and File Tranfer Workshop Announcement Announces plans for a meeting about FTP, happening April 1972 ๐ฃ๐
RFC 308 ยท Seriff ยท Mar 72 ยท ARPANET Host Availability Data A SURVEY program is up and running ๐ to help gather info on which Hosts on the ARPANET are available. Very detective-core ๐ต๏ธโโ๏ธ
RFC 307 ยท Harslem ยท Feb 72 ยท Using Network Remote Job Entry Announces a program on a PDP-10 that lets you access the Remote Job Service (RJS) at UCLA ๐ป๐ง
RFC 306 ยท Westheimer ยท Feb 72 ยท Network Host Status Updates RFC 298 ๐
RFC 305 ยท Alter ยท Jan 72 ยท Unknown Host Numbers This one talks about testing IMPs and points out that it might cause some hosts to get messages from unregistered addresses ๐ not me getting mystery mail ๐
RFC 304 ยท McKay ยท Feb 72 ยท A Data Management System Proposal for the ARPA Network A proposal for a framework so the ARPA community can recognize and build the tools they need in a unified way ๐งฉ. The big idea is letting the network manage its resources for the best possible outcome for the user ๐
RFC 303 ยท NIC ยท Feb 72 ยท ARPA Network Mailing List Obsoletes RFC 300 ๐ซก
RFC 302 ยท Bryan ยท Feb 72 ยท Excercising the ARPANET Describes a class project that tries out hosts on the ARPANET ๐โญ
RFC 301 ยท Alter ยท Feb 72 ยท BBN IMP (No. 5) and NCC Schedule for March 4, 1972 The BBN host is going to be down for one day so they can move equipment ๐ bye bye connection, see you tomorrow ๐ฅฒ
RFC 300 ยท NIC ยท Jan 72 ยท ARPA Network Mailing Lists Obsoletes RFC 211 ๐
RFC 299 ยท Hopkin ยท Feb 72 ยท Information Management System Announces the intent to build an Information Management and Statistical System for the ILLIAC IV ๐ very ambitious, I'm obsessed ๐ญ
RFC 298 ยท Westheimer ยท Feb 72 ยท Network Host Status Updates RFC 293 ๐ฆ
RFC 297 ยท Walden ยท Jan 72 ยท TIP Message Buffers A discussion about how big the TIP's message buffers are ๐ฆ the tiny details are everything, periodt ๐
RFC 296 ยท Liddle ยท Jan 72 ยท DS-1 Display System This RFC describes a proposed modular graphic/alphanumeric display system ๐ผ๏ธโจ. It has a 512 by 512 line, 60 line per inch plasma display/memory panel, plus a minprocessor ๐ง . The goal is to mix the best parts of display memory and local processing power across three general modes ๐ฅ
RFC 295 ยท Postel ยท Oct 71 ยท Report of the Protocol Workshop This is a report on the decisions made at the protocol workshop, which ran alongside the NWG meeting of 10 October 1971 ๐๏ธ๐
RFC 294 ยท Bhushan ยท Jan 72 ยท The Use of "Set Data Type" Transaction in File Transfer Protocol Updates RFC 265 ๐
RFC 293 ยท Westheimer ยท Jan 72 ยท Network Host Status Updates RFC 288 ๐ธ
RFC 292 ยท Michener ยท Jan 72 ยท Graphics Protocol - Level 0 only This is a description of part of the proposed Network Standard Graphics Protocol, which is used to send graphics data around the ARPA network ๐จ. The bit covered here is the form and content of graphics info sent from a source to a display package, so it can be output to a graphics console ๐ฅ๏ธ
RFC 291 ยท McKay ยท Jan 72 ยท Data Management Meeting Announcement A data management meeting is happening February 1972 ๐ ๐ซถ
RFC 290 ยท Mullery ยท Jan 72 ยท Computer Network and Data Sharing: A Bibliography Updates RFC 243 ๐๐งก
RFC 289 ยท Watson ยท Dec 71 ยท What We Hope is an Official List of Host Names This is an accepted list of official formal host names and nicknames ๐ท๏ธ๐
RFC 288 ยท Westheimer ยท Jan 72 ยท Network Host Status Updates RFC 287 ๐
RFC 287 ยท Westheimer ยท Dec 71 ยท Network Host Status Reports on tests of host availability from 6 Dec to 18 Dec 1971 ๐
RFC 286 ยท Forman ยท Dec 71 ยท Network Library Information System This RFC is inviting people in the ARPA community to form a working group ๐ค. The group's interests include building a new system so computers can query library holdings ๐. Georgetown University is designing a Learning Resource Center right now, and that could be the prototype for the proposed working group ๐
RFC 285 ยท Huff ยท Dec 71 ยท Network Graphics This paper is trying to bring together the current state of graphics on the NET ๐๏ธ, so newcomers can catch up, plus it adds a little more documentation to the ground ARPA graphics research has already covered ๐
RFC 284 ยท Never Issued.
RFC 283 ยท Braden ยท Dec 71 ยท NETRJT - Remote Job Service Protocol for TIPS This one talks about how it might be possible in the future to use TIPS for remote job entry, in one or more of three ways ๐งฉ. You could attach local card readers, a line printer, and card punches straight to TIP ports ๐จ๏ธ. You could hook a remote batch terminal up to a full-duplex TIP port through a communication line ๐ก. And/or you could use the tape drive, and do card-to-tape and/or tape-to-print on another computer ๐พ. Very multitasking, very iconic ๐
RFC 282 ยท Padlipsky ยท Dec 71 ยท Graphics Meeting Report A report on a graphics meeting that was held November 1972 ๐
RFC 281 ยท McKenzie ยท Dec 71 ยท A Suggested Addition to File Transfer Protocol Suggests an improved restart procedure in FTP ๐โจ
RFC 280 ยท Watson ยท Nov 71 ยท A Draft Set of Host Names A proposed list of names for hosts ๐
RFC 279 ยท Never Issued.
RFC 278 ยท Bhushan ยท Nov 71 ยท Revision of the Mail Box Protocol This paper obsoletes RFC 221. The changes to RFC 221 are all presented in this document. The protocol is also restated so people can review it ๐ฌ๐ซถ
RFC 277 ยท Never Issued.
RFC 276 ยท Watson ยท Nov 71 ยท NIC Course A course announcement from the NIC about how to use its Online System (NLS) ๐๐ป
RFC 275 ยท Never Issued.
RFC 274 ยท Forman ยท Nov 71 ยท Establishing a Local Guide for Network Usage A discussion of the best solutions to the general problem of interfacing Hosts to IMPs ๐๐ฆ
RFC 273 ยท Watson ยท Oct 71 ยท More on Standard Host Names A discussion of the best way to set up naming schemes for standard Host names ๐ท๏ธ๐
RFC 272 ยท Never Issued.
RFC 271 ยท Cosell ยท Jan 72 ยท IMP System Change Notification Announces a new version of the IMP System, Version 2514 ๐๐ฅ
RFC 270 ยท McKenzie ยท Jan 72 ยท Correction to BBN Report No. 1822 Updates pages 25 and 26 of BBN report 1822 ๐
RFC 269 ยท Brodie ยท Dec 71 ยท Some Experience with File Transfer Updates RFCs 122, 238, 172 ๐
RFC 268 ยท Postel ยท Nov 71 ยท Graphic Facilities Information A request for graphics information ๐โโ๏ธ๐จ
RFC 267 ยท Westheimer ยท Nov 71 ยท Network Host Status Reports on tests of host availability from 8 Nov to 19 Nov 1971 ๐
RFC 266 ยท Westheimer ยท Nov 71 ยท Network Host Status Reports on tests of host availability from 25 Oct to 5 Nov 1971 ๐
RFC 265 ยท Bhushan ยท Nov 71 ยท The File Transfer Protocol This paper is a revision of RFC 172. The changes to RFC 172 are all presented in this document. The protocol is also restated for additional review ๐ซถโจ
RFC 264 ยท Bhushan ยท Nov 71 ยท The Data Transfer Protocol This paper is a revision of RFC 171. The changes to RFC 171 are all presented in this document. The protocol is also restated for additional review ๐ซถโจ
RFC 263 ยท McKenzie ยท Dec 71 ยท "Very Distant" Host Interface A discussion of the best solutions to the general problem of interfacing Hosts to IMPs, but for the "very distant" case ๐๐
RFC 262 ยท Never Issued.
RFC 261 ยท Never Issued.
RFC 260 ยท Never Issued.
RFC 259 ยท Never Issued.
RFC 258 ยท Never Issued.
RFC 257 ยท Never Issued.
RFC 256 ยท Cosell ยท Nov 71 ยท IMPSYS Change Notification Announces a new version of the IMP system, Version 2513 ๐๐
RFC 255 ยท Westheimer ยท Oct 71 ยท Site Status Updates RFC 252 ๐ธ
RFC 254 ยท Bhushan ยท Oct 71 ยท Scenarios for Using ARPANET Computers This document is here to help people use ARPANET host computer systems over the ARPANET ๐ฅ๏ธ๐ง. The goal of these scenarios is to help a user sample host computers on the ARPANET, so they get excited about using it ๐คฉ
RFC 253 ยท Moorer ยท Oct 71 ยท Second Network Graphics Meeting Details Plans for a graphics meeting happening November 1971. See RFC 282 ๐จ๐
RFC 252 ยท Westheimer ยท Oct 71 ยท Site Status Updates RFC 240 ๐
RFC 251 ยท Stern ยท Oct 71 ยท Weather Data Announces the USAF Environmental Technical Application Center (ETAC) services, which provide weather data for the ARPA Network โ ๐ค๏ธ
RFC 250 ยท Brodie ยท Oct 71 ยท Some Thoughts on File Transfer Further clarification and a proposed revision of several aspects of the proposed Data Transfer Protocol and the File Transfer Protocol ๐ญโจ
RFC 249 ยท Borelli ยท Oct 71 ยท Coordination of Equipment and Supplies Purchase Announces an agreement about studying whether a coordinating point for buying equipment and supplies for use on the network is feasible ๐๐
RFC 248 ยท Never Issued.
RFC 247 ยท Karp ยท Oct 71 ยท Proffered Set of Standard Host Names Proposes a general set of rules for forming Host Names ๐. It obsoletes RFC 226 ๐ซก
RFC 246 ยท Vezza ยท Oct 71 ยท Networks Graphics Meeting
RFC 245 ยท Falls ยท Oct 71 ยท Reservations for Network Group Meeting
RFC 244 ยท Never Issued.
RFC 243 ยท Mullery ยท Oct 71 ยท Network and Data Sharing Bibliography Updated by RFC 290 ๐๐ฆ
RFC 242 ยท Haibt ยท Jul 71 ยท Data Descriptive Language for Shared Data Discusses representation differences, and defines three categories: very local representation, representation of collections of data, and other more complex structures that data collections may have ๐ง ๐
241 McKenzie Sep 71 Connecting Computers to MLC Ports
240 McKenzie Sep 71 Site Status
239 Braden Sep 71 Host Mnemonics Proposed in RFC 226
238 Braden Sep 71 Comments on DTP and FTP Protocols
237 Watson Sep 71 The NIC's View of Standard Host
Names
236 Postel Sep 71 Standard Host Names
235 Westheimer Sep 71 Site Status
234 Vezza Oct 71 Network Working Group Meeting
Schedule
233 Bhushan Sep 71 Standardization of Host Call Letters
232 Vezza Sep 71 Announcement of the next Network
Graphics Meeting
231 Heafner Sep 71 Service Center Standards for Remote
Usage - A User's View
230 Pyke Sep 71 Toward Reliable Operation of
Minicomputer-based Terminals on a
TIP
229 Postel Sep 71 Standard Host Names
228 Walden Sep 71 Clarification
227 Heafner Sep 71 Data Transfer Rates (RAND/UCLA)
226 Karp Sep 71 Standardization of Host Mnemonics
225 Harslem Sep 71 RAND/UCSB Network Graphics
Experiment
224 McKenzie Sep 71 Comments on Mailbox Protocol
223 Melvin Sep 71 Network Information Center Schedule
for Network Users
222 Metcalfe Sep 71 System Programmer's Workshop
221 Watson Aug 71 A Mail Box Protocol, Version-2
220 Never Issued
219 Winter Sep 71 User's View of the Datacomputer
218 Cosell Sep 71 Changing the IMP Status Reporting
217 White Sep 71 Specification Changes for OLS,
RJE/RJOR, and SMFS
216 White Sep 71 Telnet Access to UCSB's On-Line
System
215 McKenzie Aug 71 NCP, ICP, and Telnet: The Terminal
IMP Implementation
214 Harslem Aug 71 Network Checkout
213 Cosell Aug 71 IMP System Change Notification
212 Vezza Aug 71 NWG Meeting on Network Usage
211 NIC Aug 71 ARPA Network Mailing List
210 Conrad Aug 71 Improvement of Flow Control
209 Cosell Aug 71 Host/IMP Interface Documentation
208 McKenzie Aug 71 Address Tables
207 Vezza Aug 71 A September Network Working Group
Meeting
206 White Aug 71 A User Telnet Description of an
Initial Implementation
205 Braden Aug 71 NETCRT - A Character Display
Protocol
204 Postel Aug 71 Sockets in use
203 Kalin Aug 71 Achieving Reliable Communication
202 Wolfe Jul 71 Possible Deadlock in ICP
201 Never Issued.
200 NIC Aug 71 RFC List by Number
199 Williams Jul 71 Suggestions for a Network
Data-Tablet Graphics Protocol
198 Heafner Jul 71 Site Certification - Lincoln Labs
360/67
197 Shoshani Jul 71 Initial Connection Protocol -
Revised
196 Watson Jul 71 A Mail Box Protocol
195 Mealy Jul 71 Data Computers - Data Descriptions
and Access Language
194 Cerf Jul 71 The Data Reconfiguration Service -
Compiler/Interpreter Implementation
Notes
193 Harslem Jul 71 Network Checkout
192 Watson Jul 71 Some Factors Which a Network
Graphics Protocol Must Consider
191 Irby Jul 71 Graphics Implementation and
Conceptualization at ARC
190 Deutsch Jul 71 DEC PDP-10 - IMLAC Communication
System
189 Braden Jul 71 Interim NETRJS Specifications
188 Karp Jan 71 Data Management Meeting Announcement
187 McKay Jul 71 A Network/440 Protocol Concept
186 Michener Jul 71 A Network Graphics Loader
185 North Jul 71 NIC Distribution of Manuals and
Handbooks
184 Kelley Jul 71 Proposed Graphic Display Modes
183 Winett Jul 71 The EBCDIC Codes and Their Mapping
to ASCII
182 North Jun 71 Compilation of List of Relevant Site
Reports
181 McConnell Jun 71 Modifications to RFC 177- 241 ๐โจ: Chatting about the pros and cons of hooking computers up through serial lines to ports on the Terminal IMP's Multi-Line Controller (MLC). Very wired, very iconic ๐
- 240 ๐ธ: A reissue of RFC 235, minus the typos. Clean girl energy ๐
- 239 ๐: Discussion and comments on RFC 226.
- 238 ๐ฆ: This RFC updates RFCs 171,172. Lowkey a glow-up for those two ๐
- 237 ๐: The NIC is strongly into standardizing host names, no cap ๐ They're proposing that any standard naming scheme take a few key considerations into account.
- 236 ๐: An update of RFC 229, with some modifications included.
- 235 โญ: Starting with this one, BBN will report on the status of most Network Hosts. Main character update ๐ก
- 234 ๐ง: Plans for a Network Working Group meeting in October 1971.
- 233 ๐: A currently recommended list of call letters, so everyone knows who's who ๐
- 232 ๐: Schedule conflict, so the graphics meeting got postponed. Not me rescheduling my whole life ๐
- 231 ๐: A statement of views on service center standards, served as an input to the service center panel discussion at the October Network meeting. Opinions with receipts ๐ซถ
- 230 ๐ฅ: Points out that the current protocol for communication between a TIP and attached terminals has inadequate error detection and not enough initiation of corrective measures. It's giving "fix this please." References RFC 203.
- 229 ๐: A suggestion of eight character names, plus a proposed list of names. Eight is giving iconic ๐
- 228 ๐ธ: A correction to RFC 70. Bestie fixing the record โจ
- 227 โญ: A memo on data rates typical of the RJS use at UCLA CCN. Numbers don't lie ๐ฅ
- 226 ๐ฆ: A list of Host Mnemonics is provided. Nicknames for every machine, obsessed ๐
- 225 ๐: Describes RAND's use of the UCSB-OLS system. Network graphics era, we're so back ๐จ
- 224 ๐: Comments on electronic mail and TIP's. Mailbox drama, ngl ๐
- 223 ๐ฐ๏ธ: The access schedule for remote users of the NIC. Plan your visit accordingly ๐
- 222 ๐ป: Announcement of the next workshop. Mark your calendars, babe ๐
- 221 ๐ฌ: Discussion of the initial reaction to RFC 196. The mailbox protocol got feedback ๐ญ
- 220 ๐ซฅ: Never Issued. Ghosted by the numbering system fr fr
- 219 ๐ง : A description of the Datacomputer. Big brain energy ๐ง
- 218 ๐: A change in internal procedures for the ARPANET status reports from the IMPs to the NIC. Behind-the-scenes glow-up ๐
- 217 ๐: A current listing of documents that have been revised. Receipts for every spec ๐งพ
- 216 ๐ฅ๏ธ: Discusses implementing a teletype-compatible interface to UCSB's On-Line System. Teletype bestie era ๐
- 215 ๐ฆโจ: Announces six Terminal IMPs joining the Network, with more Terminal IMPs scheduled for delivery. The guest list keeps growing ๐
- 214 โ : A notice that certain sites have been verified. Checked off the list ๐
- 213 ๐ง: Several changes in IMP internal procedures. Quiet upgrades ๐ซถ
- 212 ๐ฎ: A mailing list for RFC distribution. Get on the list, obviously ๐
- 211 ๐: The ARPA Network Mailing List, title only, no abstract. Sometimes a title is just iconic enough ๐ธ
- 210 ๐: Discussion of the current "give back" - "return" scheme for flow control. Ping-pong vibes ๐
- 209 ๐: A discussion of a change to the IMP and its documentation (BBN report 1822). Paperwork can be cute too ๐
- 208 ๐บ๏ธ: A table of hosts on or soon to be on the ARPANET. Who's in the group chat ๐
- 207 ๐ : Next meeting announcement for a September Network Working Group meeting. Save the date ๐
- 206 ๐ป๐ฆ: Describes a program that makes an Online System terminal look, to any teletype-compatible time-sharing system in the Network, like it's directly connected. It's giving illusion, and it's working โจ
- 205 ๐: A significant revision of the character-display protocol (NETCRT), based on CCN's proposed NETCRT from the May NWG Meeting. Glow-up energy, literally ๐
- 204 ๐ข: A call to collect info on the use of socket numbers for standard service programs. Tell me your sockets ๐งฆ
- 203 ๐ก๏ธ: A non-standard protocol, suitable for either second or third level use, proposed to provide error-resistant and highly reliable communication channels. Reliability is her whole personality ๐
- 202 ๐: A note about a possible deadlock if both sides open their send or both sides open their receive sockets first. Nobody wants to be stuck in the lobby ๐
- 201 ๐ซฅ: Never Issued. Ghosted again ๐ป
- 200 ๐: RFC List by Number, covering RFC's 1-200. The original hall of fame ๐
- 199 ๐จ: SDC's comments on the discussion of a network graphics protocol. The focus is on two areas: non-interactive graphics and data-tablet graphics, as opposed to fully interactive graphics. Two lanes, both valid ๐๏ธ
- 198 โ : A report from RAND that the Lincoln Labs protocol implementations are correct. Certified and iconic ๐
- 197 ๐ ๏ธ: An attempt at a simple version of ICP, assuming one may add commands to the Host-Host protocol. Simplicity is the ultimate flex ๐
- 196 ๐จ๏ธ: The purpose of this protocol is to give each site a standard mechanism for receiving sequential files, for immediate or deferred printing or other uses. Organized, obsessed ๐ฌ
- 195 ๐๏ธ: Discusses some of the problems involved in the unified approach to Network data management, and suggests possible avenues toward resolving them. Big data brain ๐ง
- 194 ๐งฉ: Describes the new features of the language, the new syntax, the form interpreter, and the instruction set. Language glow-up ๐
- 193 ๐งช: A report from RAND on testing ten other hosts. Stress-testing the group chat ๐ซถ
- 192 ๐ผ๏ธ: A discussion of what any network graphics protocol should come to grips with. Homework, but make it aesthetic ๐ธ
- 191 ๐จ: A brief description of how graphics terminals are conceptualized and used at the Augmentation Research Center. Art department energy โจ
- 190 ๐บ: Describes an operational system for communicating textual display information between a main-site computer and a remote display processor. Screens talking to screens, iconic ๐
- 189 ๐จ๏ธ๐ธ: Describes the operation and protocol of the remote job entry service to CCN's 360 Model 91. It's an interim protocol that'll be a production service before the end of July, so it's giving soon ๐ฅ
- 188 ๐: Plans for a data management meeting to be held
Auguest 1971(it's August, bestie, the typo is just a little hiccup) ๐ - 187 ๐ง ๐: An information RFC meant to convey some of the thinking and philosophy behind IBM's network protocol and overall network design. Philosophy with a side of IBM ๐
- 186 ๐๏ธ: The Network Graphics Loader lets remote users on the ARPA network get graphics output from programs they write for the Evans and Sutherland Line Drawing System. Draw from anywhere, main character ๐
- 185 ๐: The NIC asks sites to send copies of manuals and handbooks. Library drop-off energy ๐
- 184 ๐ฆ๐ง: The ARPA Network node at the University of Illinois' Center for Advanced Computation is different from the others. It's not just a simple attachment to the net, because the computer system is being set up specifically for the ILLIAC IV and the network. This paper describes the operating systems, network interface, utility routines, and ILLIAC IV routines to be used over the network. Built different, iconic ๐
- 183 ๐ค: Defines and describes the IBM Standard Extended BCD Interchange Code, so that ASCII codes map consistently to EBCDIC codes throughout the ARPA Network. Translator era โจ
- 182 ๐๏ธ: The NIC's compilation list of all site-produced reports that are of interest to Network participants. A reading list, but make it cute ๐
- 181 ๐ผ๏ธ๐ : Modifies the device-independent graphical display description from RFC 177. The main changes are in the definition of coordinate areas, which avoids one problem with the old definition and adds more flexibility. Redesign with receipts ๐ฆ
180 McKenzie Jun 71 File System Questionnaireokay so RFC 180 is a questionnaire ๐ that tries to collect info about the local file and data conventions people were using. โจ
179 McKenzie Jun 71 Link Number AssignmentsRFC 179 has been replaced by RFCs 997 and 990. ๐ bestie, this one's retired, so go check those instead ๐
178 Cotton Jun 71 Network Graphic Attention Handlingthis one is giving serious main character energy ๐ It walks through how attention handling works, looks at different graphic setups, surveys input devices to see what kinds of data they spit out, and then proposes an attention protocol. ๐ฑ๏ธโจ
177 McConnell Jun 71 A Device Independent Graphical
Display Descriptionso as more nodes hopped onto the ARPA network, the graphical display processors people had were super varied ๐ญ To make it easier to send graphical info around, this RFC describes a device independent way to describe a display. ๐ผ๏ธ๐
176 Bhushan Jun 71 Comments on Byte Size for
Connectionsthis one lays out three views on byte size for network connections ๐ง 1) byte size should not be used at all, 2) byte size is only for the convenience of NCP's, and 3) byte size choice is a user-level prerogative. ๐ซถ
175 Harslem Jun 71 Comments on "Socket Conventions
Reconsidered"a pro and con debate about RFC 167 ๐ฅ bestie, both sides get a turn โจ
174 Postel Jun 71 UCLA-Computer Science Graphics
Overviewa quick tour of the UCLA Computer Science Department's Graphics project ๐ It covers the hardware, the software, and what they're trying to do with it. ๐ฅ๏ธ
173 Karp Jun 71 Network Data Management Committeee
Meeting Announcementthis is the report on forming a data management committee and how its very first meeting went ๐ (yes, "Committeee" with the extra e is in the actual title, iykyk ๐)
172 Bhushan Jun 71 The File Transfer Protocolokay this one is iconic ๐ It's a user-level protocol for moving files between host computers (including terminal IMPs) on the ARPA computer network. FTP uses the data transfer protocol from RFC 171, and this paper assumes you already know RFC 171 ๐ง so read that first, babe!
171 Bhushan Jun 71 The Data Transfer Protocolthis one defines a low-level Data Transfer Protocol (DTP) for moving data around in file transfer, remote job entry, and other application-oriented protocols ๐ RFC 172 is the companion paper that describes the file transfer protocol. ๐ฆ
170 NIC Jun 71 RFC List by Numbera list of RFCs 1-170, aka the ultimate็ดขๅผ ๐ (okay, the index of RFCs 1 through 170, obviously) ๐
168 North May 71 ARPA Network Mailing Liststhe distribution list for RFCs ๐ฌ who gets the mail, basically ๐ธ
167 Bhushan May 71 Socket Conventions Reconsideredso the recent NCP Protocol said nothing about how hosts should assign socket numbers to process ports ๐ญ The only rule it had was that the low-order bit specifies socket gender. This document talks through two recent proposals that want extra network-wide conventions on the 32-bit socket number. ๐ขโจ
166 Anderson May 71 Data Reconfiguration Service - An
Implementation Specificationthis DRS experiment was a software mechanism for reformatting Network data streams ๐ It can be adapted to tons of Network application programs. ๐
165 Postel May 71 A Proferred Official Initial
Connection Protocolthis one specifies the third level protocol for connecting a user process at one site with a server process at another site ๐ "Proferred" is the spelling in the actual title, not my typo ๐
164 Heafner May 71 Minutes of Network Working Group
Meetinga 38 page reference on all the discussions from the Network Working Group Meeting ๐ that's a lot of reading, but it's a whole vibe ๐ซถ
163 Cerf May 71 Data Transfer Protocolsan informal statement on Data Transfer Protocols, tied to material discussed at the SJCC ๐ฃ๏ธ casual but important ๐
162 Kampe May 71 NETBUGGER3NETBUGGER3 is a third level program for debugging second and third level programs ๐ It also covers experimenting with and simulating third level protocols. ๐งชโจ
161 Shoshani May 71 A Solution to the Race Condition in
the ICPa proposed fix for a problem that came out of RFC 143 ๐ ๏ธ race conditions are NOT it, honestly ๐
160 NIC May 71 RFC Brief Listthis is the title or partial title RFC list for RFCs 1-160 ๐ quick and clean ๐
159 Never Issued.RFC 159 was never issued. ๐ป it just doesn't exist, so don't go looking for it ๐
158 O'Sullivan May 71 Proposed Telnet Protocolthis one is asking for comments, evaluation, and requested changes to the proposed Telnet protocol ๐ฅ๏ธ๐ฌ bestie, speak up ๐ฃ
157 Cerf May 71 Invitation to the Second Symposium
on Problems in the Optimization of
Data Communication Systemsan announcement for an ACM/IEEE conference on data communication ๐๏ธ the invite is giving academia ๐
156 Bouknight Apr 71 Status of the Illinois Site
(Response to RFC 116)this one talks about the status of the operational hardware at the Illinois site ๐ซ it's a response to RFC 116, so keep that in mind ๐ง
155 NIC May 71 List to Receive RFCsthe mailing list of people getting the initial RFC distribution ๐จ you're in the group chat if you're on it ๐
154 Crocker May 71 Exposition Stylea little note on style in documentation โ๏ธ writing it cleanly is a whole art, periodt ๐
153 Melvin May 71 SRI ARC-NIC Statusthis one is about the current computer and network status of the SRI ARC-NIC ๐งโจ
152 Wilber May 71 SRI Artificial Intelligence Status
Reporta status report on SRAI's connection to the ARPANET as a research center ๐ค it's the update you didn't know you needed ๐
151 Shoshani May 71 Comments on a Proferred Official ICP
(RFCs 123,127)these are specific and general remarks about the ICP, and it's giving feedback on RFCs 123 and 127 ๐ bestie, read the comments ๐
150 Kalin May 71 The Use of IPC Facilitiesa working paper on the types of usage an IPC facility would be subjected to ๐งฉ It's trying to clarify the goals being pursued, and it should give you a benchmark for judging different implementation strategies. ๐ literally a must-read if you're building one ๐ฅ
149 Crocker May 71 The Best Laid Plans...changes to the topics and attendees for the upcoming NWG meeting ๐๏ธ plans change, it's fine ๐ซถ
148 Bhushan May 71 Comments on RFC 123this one is about the byte size requirements for the initial connection ๐ข it's comments on RFC 123, so it's a follow-up, not a standalone ๐ซ
147 Winett May 71 The Definition of a Socketthis is the one that defines, specifies, and identifies sockets ๐ the foundation, bestie, 100% ๐ฏ
146 Karp May 71 Views on Issues Relevant to Data
Sharing on Computer Networksthis one agrees with the views in RFC 140 ๐ค concurrence, aka we're on the same page ๐
145 Postel May 71 Initial Connection Protocol Control
Commandsthis one interprets the exchange between NCP's that you need in order to carry out the Initial Connection Protocol (ICP) of RFC 123 ๐ง it's the how-to for that exchange, lowkey iconic ๐
144 Shoshani Apr 71 Data Sharing on Computer Networksan introductory paper for the upcoming NWG meeting in Atlantic City ๐ it's giving "welcome to the topic" energy ๐
143 Naylor May 71 Regarding Proferred Official ICPcomments on a race condition they found in the ICP proposed in RFC 123 ๐๏ธ race conditions are NOT a vibe ๐ญ
142 Kline May 71 Time-out Mechanism in the Host-Host
Protocola discussion of the situations that can come up when you send a message to a foreign site โณ timeouts are the drama of networking, bestie ๐ญ
141 Harslem Apr 71 Comments on RFC 114 (A File Transfer
Protocol)more discussion on the File Transfer Protocol ๐ this is the sequel to the FTP drama ๐ฟ
140 Crocker May 71 Agenda for the May NWG Meetinga list of topics for the upcoming meeting, plus a list of relevant RFCs you should review before showing up ๐ homework, but make it cute ๐
139 O'Sullivan May 71 Discussion of Telnet Protocolan extension of RFC 137 ๐ฑ level up ๐
138 Anderson Apr 71 Status Report on Proposed Data
Reconfiguration Servicethis one describes a proposed Network experiment and asks for comments on any aspect of it ๐งช your feedback is welcome, babe ๐ซถ
137 O'Sullivan Apr 71 Telnet Protocol - A Proposed
Documenta request for review and comment before the Atlantic City NWG meetings ๐ get your thoughts in early ๐
136 Kahn Apr 71 Host Accounting and Administrative
Proceduresthis is a discussion of a plan that's meant to be formulated and accepted for developing a Host accounting system on the ARPA Network ๐งพ accounting, but make it networking ๐ฅ
135 Hathaway Apr 71 Response to RFC 110comments and proposals for new conventions to replace the ones proposed in RFC 110 ๐ glow-up era โจ
134 Vezza Apr 71 Network Graphics Meetingan announcement for the next Network Graphics Meeting at Project MAC in July 1971 ๐๏ธ save the date, bestie ๐
133 Sundberg Apr 71 File Transfer and Error Recoverysample interchanges plus comments on file transfer and errors ๐ errors happen, we recover, we slay ๐ช
132 White Apr 71 Typographical Error in RFC 107this one points out an error in RFC 107 ๐ oops, we all have those days
131 Harslem Apr 71 Response to RFC 116 (May NWG
Meeting)a description of network plans at RAND, including the data reconfiguration service, plus a comment on the role of the NWG ๐ข RAND is serving corporate-but-make-it-cool ๐ผ
130 Heafner Apr 71 Response to RFC 111 (Pressure from
the Chairman)this one discusses RAND's role in testing other host implementations, and the schedule dependences ๐๏ธ the chairman was feeling the pressure, lol ๐ญ
129 Harslem Apr 71 A Request for Comments on Socket
Name Structurecomments on several suggested socket name structures ๐ท๏ธ naming is the hardest part, honestly ๐
128 Postel Apr 71 Bytesa discussion of the byte size parameter allowed by the 2nd level protocol ๐ข short title, big energy ๐ง
127 Postel Apr 71 Comments on RFC 123more interpretations of the exchange between NCP's that you'd need to carry out the Initial Connection Protocol of RFC 123 ๐งฉ part two of the ICP saga ๐ฌ
126 McConnell Apr 71 Ames Graphics Facilities at Ames
Research Centerthis one discusses the graphical facilities at Ames for the IBM 360/67 TSS ๐ฅ๏ธ the TSS is giving old school ๐ฐ๏ธ
125 McConnell Apr 71 Response to RFC 86, Proposal for
Network Standard Format for a
Graphics Data Streamthis improves and updates RFC 86 โจ upgraded and iconic ๐
124 Melvin Apr 71 Typographical Error in RFC 107this one also points out an error in RFC 107 ๐ RFC 107 really got the typo treatment, lol
123 Crocker Apr 71 A Proferred Official ICPthis RFC describes a family of ICPs (Initial Connection Protocol) that can set up one pair of connections (one in each direction) between any user process and any server process ๐ it also proposes one particular subset of that family as the standard ICP for connecting user processes to loggers on systems that accept teletype-like devices. ๐จ๏ธโจ the main character of the ICP story ๐
122 White Apr 71 Network Specifications for UCSB's
Simple-Minded File Systemthis one is about UCSB's Simple Minded File System (SMFS), which provides file storage for network users ๐ It gives programmers the info they need to communicate with SMFS. ๐ง a classic, no cap ๐ฆ
okay bestie, the list keeps going and it's still giving history ๐ง๐
121 Krilanovich Apr 71 Network On-Line Operators
Descriptions of operators that have been implemented within UCSB's
On-Line System and make the network (via NCP) accessible to
On-Line system users.
120 Krilanovich Apr 71 Network PL1 Subprograms
Descriptions of subroutines that have been implemented at UCSB and
make the network (via NCP) accessible to PL1 programs executing in
the IBM 360/75.
119 Krilanovich Apr 71 Network FORTRAN Subprograms
Descriptions of a set of assembly-language subprograms, their
functions and calling sequences.
118 Watson Apr 71 Information Required for Each
Service Available to the Network
Cites two classes of information which each site needs to provide
for every service or process it makes available over the ARPA
network.
117 Wong Apr 71 Some Comments on the Official
Protocol
Cites weaknesses in RFC 107, and provides suggestions for
correction and handling.
116 Crocker Apr 71 Structure of the May NWG Meeting
Proposed meeting agenda centering around discussions of advertised
topics, with published status reports and position papers.
115 Watson Apr 71 Some Network Information Center
Policies on Handling Documents
Discusses current document policies between the Network
Information Center and sites on the network.
114 Bhushan Apr 71 A File Transfer Protocol
Proposed file transfer mechanisms that have been developed for
immediate implementation on hosts at MIT.
113 Harlsem Apr 71 Network Activity Report: UCSB and
RAND
Report on the network use and validity between UCSB's RJE and RJOR
systems and RAND.
112 O'Sullivan Apr 71 User/Server Site Protocol Network
HOST Questionnaire
A summary of the responses to the referenced questionnaire.
111 Crocker Mar 71 Pressure from the Chairman
Proposed scheduling for the implementation of NCPs and Telnets.
110 Winett Mar 71 Conventions for Using an IBM 2741
Terminal as a User Console for
Access to Network Server Hosts
Telnet implementation and the 2741.
109 Winett Mar 71 Level III Server Protocol for the
Lincoln Laboratory 360/67 Host
Telnet implementation and the 360/67.
108 Watson Mar 71 Attendance List at the Urbana NWG
Meeting, 17-19 February 1971
Lists attendees at the NWG meeting held February 1971.
107 Bressler Mar 71 Output of the Host-Host Protocol
Glitch Cleaning Committee
The second meeting of the Host-Host Protocol Glitch Cleaning
committee.
106 O'Sullivan Mar 71 USER/SERVER Site Protocol Network
Host Questionnaire
An attempt to gather information for creating the Telnet Protocol.
105 White Mar 71 Network Specification for Remote Job
Entry and Remote Job Output
Retrieval at UCSB
Describes the remote job entry service at UCSB.
104 Postel Feb 71 Link 191
General agreement to reserve a link for use in measurements.
Therefore, Link 191 will be assigned for measurement use.
103 Kalin Feb 71 Implementation of Interrupt Keys
This paper discusses the problems and solutions that are simple to
implement in the current protocol specifications that contain
serious logical errors in the interrupt functions.
102 Crocker Feb 71 Output of the HOST/HOST Protocol
Glitch Cleaning Committee
Numerous topics were discussed.
101 Watson Feb 71 Notes on the Network Working Group
Meeting
Transcript of the Network Working Group Meeting, February 1970.
100 Karp Feb 71 Categorization and Guide to NWG/RFCs
Categorizes, identifies, and summarizes RFCS 1-100.
099 Karp Feb 71 Network Meeting
Announcement of the next meeting of the Network Working Group for
20 May 1970.
098 Meyer Feb 71 Logger Protocol Proposal
This "network logger protocol" is intended to specify how the
existing logger of a network host is to interface to the network
so as to permit a login from a console attached to another host.
097 Melvin Feb 71 A First Cut at a Proposed Telnet
Protocol
This document was motivated by the need to set specifications for
a protocol which would allow on-line access to the Network
Information Center (NIC).
096 Watson Feb 71 An Interactive Network Experiment to
Study Modes of Access to the Network
Information Center
Outlines the framework for a simple interactive experiment to
study modes of access to the Network Information Center (NIC).
095 Crocker Feb 71 Distribution of NWG/RFC's Through
the NIC
Standards for establishing lines of communication of all of the
sites with the Network Information Center, in regards to
distribution of RFC's.
094 Harslem Feb 71 Some Thoughts on Network Graphics
Discussion of the initial reaction to RFC 86, whose purpose was to
provide a basis for discussion and development of Network
graphics.
093 McKenzie Jan 71 Initial Connection Protocol
A review of the Initial Connection Protocol (ICP), first described
in RFC 66 and restated in RFC 80.
092 Never Issued.
091 Mealy Dec 70 A Proposed User-User Protocol
Discussion of UCLA's Campus Computing Network of services and
implementation priorities.
090 Braden Jan 71 CCN as a Network Service Center
Discussion of UCLA's Campus Computing Network of services and
implementation priorities.
089 Metcalfe Jan 71 Some Historic Moments in Networking
Noteworthy achievements for the MIT-Project MAC Dynamic
Modeling/Computer Graphics PDP-6/10 System, while awaiting the
completion of an interim network control program.
088 Braden Jan 71 NETRJS - A Third Level Protocol for
Remote Job Entry
Description of NETRJS, which is the name for a message protocol
and a set of control conventions which will allow users at remote
Hosts to access the RJS remote batch subsystem of UCLA/CCN.
087 Vezza Jan 71 Topic for Discussion at the Next
Network Working Group Meeting
Suggests Network Working Group discussion on topics germane to
network graphics.
086 Crocker Jan 71 Proposal for a Network Standard
Format for a Data Stream to Control
Graphics Display
Proposes specifying the form of an output stream for the case that
the output portion of the console (which is attached to a computer
at the user's site) is a typical refresh display with point,
vector, and character drawing capability.
085 Crocker Dec 70 Network Working Group Meeting
Announcement of regularly scheduled Network Working Group Meetings
every three months.
084 North Dec 70 List of NWG/RFCs 1-80
Lists RFCs 1-80.
083 Anderson Dec 70 Language-Machine for Data
Reconfiguration
Describes a syntax-driven interpreter that operates on a grammar
which is an orderd set of replacement rules for the Form Machine.
082 Meyer Dec 70 Network Meeting Notes
A transcribed summary of the Fall 1970 network meeting notes.
081 Bouknight Dec 70 Request for Reference Information
Request for documents in the subject areas of data communications
and communications theory.
080 Harslem Dec 70 Protocol and Data Formats
Proposes general solutions concerning Initial Connection
Protocols, Pre-specificed Data Formats, and Adaptable Mechanisms.
079 Meyer Nov 70 Logger Protocol Error
078 Harslem Nov 70 NCP Status Report: UCSB/Rand
Conducted an excercise between UCSB console to/from RAND console
validation of the respective NCPs.
077 Postel Nov 70 Network Meeting Report
Report on three Network Working Group meetings held during
November 16, 17, and 18.
076 Bouknight Oct 70 Connection-by-Name: User-Oriented
Protocol
Suggests a user level interface to network protocol where all user
protocol is handled symbolically with system procedures making the
translation into host-to-host protocol. Proposes general
solutions.
075 Crocker Oct 70 Network Meeting
Announcement of the next scheduled meeting of the Network Working
Group for 16 Nov 70.
074 White Oct 70 Specifications for Network Use of
the UCSB On-Line System
Announcement of UCSB's On-Line System (OLS) availability to ARPA
Network users.
073 Crocker Sep 70 Response to RFC 67
General agreement with proposed policy.
072 Bressler Sep 70 Proposed Moratorium on Changes to
Network Protocol
Cites critical changes that could occur in hardware/software
development efforts and advanced debugging if changes in the
Network Protocol aren't kept in check.
071 Schipper Sep 70 Reallocation in Case of Input Error
Discussion of how to resynchronize flow control using a proposed
protocol for the CCN-Host at UCLA.
070 Crocker Oct 70 A Note on Padding
Discussion of padding on a message.
069 Bhushan Sep 70 Distribution List Change for MIT.
Announcement of name change.
068 Elie Aug 70 Comments on Memory Allocation
Control Commands (CEASE, ALL, GVB,
RET) and RFNM
Provides a scheme for buffer allocation.
067 Crowther Undated Proposed Change to Host/IMP Spec to
Eliminate Marking
Proposed change to eliminate marking, per Walden's comments.
066 Crocker Aug 70 3rd Level Ideas and Other Noise
Meeting notes from 12 Aug 70 between Crocker and representatives
from BBN and MIT regarding the third level protocol.
065 Walden Aug 70 Comments on Host-Host Protocol
Document Number 1 (Crocker,
3 August 70)
Critique and suggestions for improvement of the Host-Host Protocol
document.
064 Elie Undated Getting Rid of Marking
Suggests simple modifications and solutions to the IMP-HOST
interface which would be a better solution than marking.this index is so iconic, the way every single RFC gets its own little entry ๐๐ธ
Okay, the list keeps going, bestie, and these are the last entries ๐โจ
063 Cerf Jul 70 Belated Network Meeting Report
Network meeting report of the Network Working Group from 8 May 70.
062 Walden Aug 70 A System for Interprocess
Communication in a Resource Sharing
Computer Network
Supercedes RFC 61.
061 Walden Jul 70 A Note on Interprocess Communication
in a Resource Sharing Computer
Network
A draft request for comments of a resource sharing study that may
be of general interest to network participants.
060 Kalin Jul 70 A Simplified NCP Protocol
Definition of a new NCP Protocol that is simple enough to be
implemented on a very small computer, yet can be extended for
efficient operation on large timesharing machines.
059 Meyer Jun 70 Flow Control-Fixed Versus Demand
Allocation
Discussion of the advantages and disadvantages of the method of
flow control as described in RFC 54.
058 Skinner Jun 70 Logical Message Synchronization
A discussion on a question raised at the last network meeting
regarding the question of logical and physical message
distinctions.
057 Kraley Jun 70 Thoughts and Reflections on RFC 54
056 Belove Jun 70 Third Level Protocol
All explanations in this RFC are meant to describe functional
characteristics rather than design.
055 Newkirk Jun 70 A Prototypical Implementation of the
NCP
A prototypical specification in a prose format of what the NCP
could look like.
054 Crocker Jun 70 An Official Protocol Proffering
Submission of the Official Protocol for comments and suggestions.
053 Crocker Jun 70 An Official Protocol Mechanism
Group discussion on rules for establishing and modifying an
official Host-Host protocol.
052 Postel Jul 70 Updated Distribution List
Mailing list for distributing the RFCs.
051 Elie May 70 Proposal for a Network Interchange
Language
A proposal to specify a high level programming language for
computer networks, specifically the ARPA network.
050 Harslem Apr 70 Comments on the Meyer Proposal
General acceptance on RFC 46, plus comments on the seven issues
raised in RFC 47.
049 Meyer Apr 70 Conversations with Steve Crocker
(UCLA)
Discussion of telephone conversations relating to the Network
Protocol, specifically regarding Meyer's proposal in RFC 46.
048 Postel Apr 70 A Possible Protocol Plateau
Reporting activities since the Network meeting of 17 March 1970.
047 Postel Apr 70 BBN's Comments on RFC 33
Comments from BBN regarding RFC 33 (New HOST-HOST Protocol).
046 Meyer Apr 70 ARPA Network Protocol Notes
Comments and suggestions from the NWG at Project MAC, based upon
the protocol outlined in RFCs 33,36.
045 Postel Apr 70 New Protocol is Coming
Announcement of a new version of the Network Protocol.
044 Shoshani Apr 70 Comments on RFCs 33,36
General discussion and suggestions for refinements to the
HOST-HOST Protocol.
043 Nemeth Mar 70 Proposed Meeting
An announcement of a meeting to discuss the Local Interaction
Language system.
042 Ancona Mar 70 Message Data Types
A proposal that the first eight bits of a normal message be
reserved for a message data type.
041 Melvin Mar 70 IMP/IMP Teletype Communication
Comments that transmitting IMP sites should use 24 hour time and
include the time zone designation.
040 Harslem Mar 70 More Comments on the Forthcoming
Protocol
Further elaborations on the errors, queries, and Host status that
were mentioned in RFC 39.
039 Harslem Mar 70 Comments on Network Protocol
(RFC 36)
More suggestions to be considered as additions to RFC 36 - Network
Protocol.
038 Wolfe Mar 70 Comments on Network Protocol
(RFC 36)
Continued discussion on the proposed Network Protocol.
037 Crocker Mar 70 Network Meeting Epilogues, etc.
Network Meeting notes from 17 March 1970.
036 Crocker Mar 70 Protocol Notes
A three part overview of the Network Protocol.
035 Crocker Mar 70 Network Meeting
Announcement of a network meeting: date, time, place, and proposed
agenda.
034 English Feb 70 Some Brief Preliminary Notes on the
ARC Clock
Describes the ARC Clock system.
033 Crocker Feb 70 New Host-Host Protocol
Revises RFC 11, and indicates numerous changes in the old
protocol.
032 Cole Feb 70 Some Thoughts on SRI's Proposed Real
Time Clock
References and comments on RFCs 28,29.
031 Bobrow Feb 68 Binary Message Forms in Computer
Networks
Suggest alternative approaches and methods for describing
messages.
030 Crocker Feb 70 Documentation Conventions
Revises the definition of style, content, form, and distribution
of the Network Working Group's notes. Replaces RFCs 10,16,24,27.
029 Kahn Jan 70 Note in Response to Bill English's
Request for Comments
Comments in response to English's question which was raised in
RFC 28.
028 English Jan 70 Time Standards
Request for comments relative to Network time standards.
027 Crocker Dec 69 Documentation Conventions
Revises the definition of style, content, form, and distribution
of the Network Working Group's notes. Replaces RFCs 10,16,24.
026 Never Issued.
025 Crocker Oct 69 No High Link Numbers
Suggests that no link number over 63 be used.
024 Crocker Nov 69 Documentation Conventions
Revises the definition of style, content, form, and distribution
of the Network Working Group's notes. Replaces RFCs 10,16.
023 Gregg Oct 69 Transmission of Multiple Control
Messages
Discusses how a network program at a site should be prepared to
send or receive more than one control message in a single control
communication.
022 Cerf Oct 69 Host-Host Control Message Formats
Reports on a new control message format which does not use the
7-bit ASCII character mode of transmission.
021 Cerf Oct 69 Report on Network Meeting
Attendance list and topics discussed.
020 Cerf Oct 69 ASCII Format for Network Interchange
Discusses the use of standard 7-bit ASCII embedded in an 8-bit
byte whose high order bit is always 1.
019 Kreznar Oct 69 Two Protocol Suggestions to Reduce
Congestion at Swap-Bound Nodes
Suggests alternatives in reducing congestion at swap-bound nodes.
018 Cerf Sep 69 Comments Re: Host-Host control link
Suggestions regarding the Host-Host control link.
017a Kahn Aug 69 Some Comments Re: HOST-IMP Protocol
Comments in response to Kreznar's questions which were raised in
RFC 17.
017 Kreznar Aug 69 Some Questions Re: HOST-IMP Protocol
Queries and opinions regarding the HOST-IMP Protocol.
016 Crocker Aug 69 M.I.T.
Announcement that MIT is now to receive all Network Working Group
memos.
015 Carr Sep 69 Network Subsystem for Time Sharing
Hosts
Proposes a subsystem called "Telnet", which would be a shell
program around the network system primitives, allowing a teletype
or similar terminal at a remote host to function as a teletype at
the serving host.
014 Never Issued.
013 Cerf Aug 69 Referring to RFC 11
Proposes a zero text length EOF (End-Of-File) message.
012 Wingfield Aug 69 IMP-HOST Interface Flow Diagrams
Flow diagrams that indicate the logical sequence of hardware
operations which occur within the IMP-HOST interface.
011 Deloche Aug 69 Implementation of the Host-Host
Software Procedures in GORDO
Discussion of Host-Host Procedures and GORDO as a time-sharing
system that was implemented on a SDS Sigma 7.
010 Crocker Jul 69 Documentation Conventions
Revises the definition of style, content, form, and distribution
of the Network Working Group's notes. Replaces RFC 3.
009 Deloche May 69 Host Software
Discusses the Host-Host Protocol, Network Service Calls, and Data
Structures.
008 Deloche May 69 ARPA Network Functional
Specifications
Discusses transmission features, functional software
specifications, and the Link establishment procedure.
007 Deloche May 69 HOST-IMP Interface
Discusses Host-IMP interface issues.
006 Crocker Apr 69 Conversation with Bob Kahn
Conversations regarding code conversion in the IMP's, IMP-HOST
communication, and HOST software.
005 Rulifson Jun 69 DEL
Details the machine independent language DEL (Decode-Encode
Language).
004 Shapiro Mar 69 Network Timetable
Discusses installation, configuration, network checkout, and test
messages run between SRI and UCLA.
003 Crocker Apr 69 Documentation Conventions
Establishes a definition of style, content, form, and distribution
of the Network Working Group's notes (Obsoleted by RFC 10).
002 Duvall Apr 69 Links
Discusses various types of Links, including Control, Primary, and
Auxilliary Links.
001 Crocker Apr 69 Host Software
Discusses the Host software and initial experiments on the ARPA
Network.๐ฆ where this page comes from
- ietf: rfc1000 1987-08
- ๐ girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms