Table of Contents
In 2019 I read one RFC a day in chronological order starting from the very first one. More on this project here.
Introduction RFC-1: Setting the stage RFC-2: A mystery, so soon?? RFC-3: Buckle up, it's about to get meta RFC-4: Planning the project RFC-5: DEL – the rich application layer that never was RFC-6: Syncing with BB&N RFC-7: Too long; didn't read RFC-8: An attempt at synthesis RFC-9: Host software, take 3
RFC-10: Shuffling the deck RFC-11: GORDO and the IMP RFC-12: Flowcharts RFC-13: End of file RFC-14: Miss Zarves RFC-15: Proposing TELNET RFC-16: M.I.T. RFC-17: Like email but slower RFC-18: Reducing congestion RFC-19: Some suggestions
RFC-20: ASCII RFC-21: Meeting minutes RFC-22: Revisions RFC-23: Multiple messages Update: scans of early RFCs RFC-24: Adding MITRE RFC-25: Link hygiene RFC-26: No RFC RFC-27: Adding Raytheon RFC-28: Time might be useful RFC-29: Milliseconds
RFC-30: Adding Stanford and Carnegie Mellon RFC-31: Down with long boxes RFC-32: Crystals RFC-33: New concepts for the network RFC-34: Absolute and relative time RFC-35: Save the date RFC-36: Updates to the protocol RFC-37: Meeting notes RFC-38: Multiplexing RFC-39: Error and status
RFC-40: Detailed errors and statuses RFC-41: Please provide timestamps RFC-42: A proposal for typed messages RFC-43: A meeting at Lincoln Laboratory RFC-44: A word from SDC RFC-45: See you in Atlantic City RFC-46: A power move RFC-47: Potential embarrassment RFC-48: Plateaus RFC-49: Levels
RFC-50: Converging on a protocol RFC-51: NIL RFC-52: More universities RFC-53: Making things official RFC-54: A proffering RFC-55: Squishy amoebas RFC-56: A bit of a hit-and-run RFC-57: Edge cases RFC-58: A big box of paper RFC-59: The case for perfect
RFC-60: A simpler NCP RFC-61: Another shot at interprocess communication RFC-62: A revision of another shot at interprocess communication RFC-63: Belated RFC-64: Marking considered harmful RFC-65: More marking RFC-66: Levels RFC-67: Wildly enthusiastic RFC-68: Acknowledging ACK RFC-69: Please unsubscribe
RFC-70: Padding math RFC-71: Enter the CCN RFC-72: Proposed moratorium RFC-73: Unnecessary changes RFC-74: A working NCP RFC-75: See you in Astroworld RFC-76: A new kind of Host RFC-77: A three-day meeting RFC-78: Human factors RFC-79: A conflict
RFC-80: Adaptive mechanisms RFC-81: Please send reading materials RFC-82: A fly on the wall RFC-83: A Language-Machine RFC-84: Reddy Dively RFC-85: Quarterly meetings RFC-86: A simple drawing format RFC-87: A network graphics meeting RFC-88: Punch cards and printers RFC-89: Historic moments
RFC-90: A resource to be shared RFC-91: Thinking about users RFC-92: Not issued RFC-93: Code zero RFC-94: Graphics suggestions RFC-95: Paper RFC-96: An experiment RFC-97: A Telnet protocol RFC-98: Logging in RFC-99: Atlantic City again
RFC-100: A catalog RFC-101: A winter meeting RFC-102: The Glitch Cleaning Committee RFC-103: Interrupting interrupts RFC-104: A reserved link RFC-105: Remote jobs RFC-106: A questionnaire RFC-107: An ultimatum RFC-108: Urbana attendance RFC-109: Connecting to Lincoln Lab
RFC-110: I have no characters yet I must type RFC-111: Under pressure RFC-112: Questionnaire results RFC-113: A success and some bugs RFC-114: FTP RFC-115: The NIC RFC-116: Atlantic City efficiency RFC-117: Glitches the Cleaning Committee missed RFC-118: One hundred copies RFC-119: Fortran subroutines
RFC-120: PL1 subroutines RFC-121: On-line operators RFC-122: Simple-minded RFC-123: Leading by example RFC-124: Found a typo RFC-125: A late reply from NASA RFC-126: NASA graphics RFC-127: Missing algorithm RFC-128: Bytes RFC-129: Socket names
RFC-130: Waiting on Telnet RFC-131: VIEWs on the network RFC-132: Off by one RFC-133: Sorry, forget it RFC-134: Endicott House RFC-135: Correspondence models RFC-136: Accounting RFC-137: Telnet for Atlantic City RFC-138: Data reconfiguration for Atlantic City RFC-139: Discussion of TELNET Protocol
RFC-140: Atlantic City agenda RFC-141: Nine comments on file transfer RFC-142: Time out RFC-143: Race conditions RFC-144: Data sharing RFC-145: Initial connection correction RFC-146: A data sharing committee RFC-147: Sockets RFC-148: Severe strains RFC-149: Accommodating Dr. Roberts
RFC-150: Interprocess communication RFC-151: Conflicts between levels RFC-152: Artificial intelligence online RFC-153: NIC Status RFC-154: Defensive pedantry RFC-155: More addressees RFC-156: Illinois status RFC-157: Optimization invitation RFC-158: Another pass at Telnet RFC-159: No RFC
RFC-160: A not-so-brief list RFC-161: Extra sockets RFC-162: NETBUGGER3 RFC-163: Notes from SJCC RFC-164: Extensive notes from SJCC RFC-165: A corrected ICP RFC-166: FML RFC-167: Sockets, reconsidered RFC-168: Air mail RFC-169: Other networks
RFC-170: Another list RFC-171: DTP RFC-172: FTP, again RFC-173: Sharing, or management? RFC-174: Wands, tablets, and fisheyes RFC-175: Socket length concerns RFC-176: The correct view RFC-177: Another crack at a graphics interface RFC-178: Interactive graphics RFC-179: New link numbers
RFC-180: Tell us about your file system RFC-181: Fractional displacements RFC-182: Compilations RFC-183: Character correspondences RFC-184: Supercomputer graphics RFC-185: Bring enough for the whole class RFC-186: Rotating cubes on the network RFC-187: An experimental network RFC-188: Data management meeting RFC-189: Some compliance with standards
RFC-190: Even more graphics description RFC-191: Split screens RFC-192: Graphics: the big picture RFC-193: Checking the boxes RFC-194: Stack machine RFC-195: Assumptions and their consequences RFC-196: Mail box RFC-197: Further ICP consideration RFC-198: Lincoln Labs checks in RFC-199: Data tablets
RFC-200: Another RFC list RFC-201: Not issued RFC-202: Deadlock RFC-203: Error-resistant communication RFC-204: The socket czar's opening gambit RFC-205: Telnet for text editors RFC-206: A Telnet client RFC-207: Meeting at Project MAC RFC-208: Addresses from the future RFC-209: Sorry about that, but also it's your fault
RFC-210: Fractions are bad RFC-211: More distribution lists RFC-212: Scheduling conflict RFC-213: BBN is walking on eggshells RFC-214: Checking more boxes RFC-215: TIP tips RFC-216: Putting two keyboards in one RFC-217: Changes to UCSB services RFC-218: Fake host RFC-219: The datacomputer
RFC-220: Not issued RFC-221: FTP for mail RFC-222: Grueling workshop RFC-223: Nine to five RFC-224: Renting mail boxes RFC-225: On-Line from afar RFC-226: Gee, this is swell Document: Gee Host Names and Numbers are Swell RFC-227: Transfer speed RFC-228: Someone's been reading the code RFC-229: Eight characters are better than six
RFC-230: Enter the minicomputer RFC-231: Let's keep standardizing RFC-232: Postponement RFC-233: Four characters is enough RFC-234: Map of MIT RFC-235: Mostly dead RFC-236: Programmers are lazy RFC-237: The NIC weighs in RFC-238: Encouraging explanations RFC-239: Combative about naming
RFC-240: Corrected statistics RFC-241: Our previous verbal comments RFC-242: A proposal from IBM RFC-243: A bibliography from IBM RFC-244: Not issued RFC-245: Group discounts RFC-246: New dates RFC-247: Actual comments RFC-248: Not issued RFC-249: Group discounts
RFC-250: Colliding ideas RFC-251: Weather data RFC-252: New week, same numbers RFC-253: Golden Pavillion RFC-254: A handbook RFC-255: An improvement RFC-256: IMP tests you RFC-257: Not issued RFC-258: Not issued RFC-259: Not issued
RFC-260: Not issued RFC-261: Not issued RFC-262: Not issued RFC-263: Long distances RFC-264: Data Transfer Protocol revisions RFC-265: File Transfer Protocol revisions RFC-266: Incremental improvement RFC-267: A new PDP-10 appears RFC-268: Requesting handbook information RFC-269: Simple minded experience
RFC-270: Missing attachment RFC-271: Reverting a change RFC-272: Not issued RFC-273: Let's settle this issue RFC-274: Another guidebook RFC-275: Not issued RFC-276: Online System course RFC-277: Not issued RFC-278: Electronic mail: potentially useful RFC-279: Not issued
RFC-280: Closure at last? RFC-281: Restart RFC-282: Quite hampering RFC-283: Jobs for TIPs RFC-284: Not issued RFC-285: Think creatively RFC-286: Network all the libraries RFC-287: Dismal results RFC-288: More dismal results RFC-289: Hope
RFC-290: More papers RFC-291: Speakers and protocols RFC-292: First pass at graphics RFC-293: More numbers RFC-294: Negotiating data types RFC-295: Protocols RFC-296: A computer that never was RFC-297: Stop your groaning RFC-298: Halfway online RFC-299: Information Management
RFC-300: List management RFC-301: IMP Goes Down RFC-302: A user test RFC-303: List management RFC-304: Data control facility RFC-305: Ghost hosts RFC-306: Network status RFC-307: A remote job frontend RFC-308: ARPANET Online RFC-309: Settling file transfer
RFC-310: Reconsidering FTP RFC-311: Graphics terminals RFC-312: Better Host-IMP error messages RFC-313: Computer based instruction RFC-314: Network graphics and cherry blossoms RFC-315: Network status RFC-316: Data management applications RFC-317: Reserving more links for measurement RFC-318: Neither clear nor succinct RFC-319: Network status
RFC-320: Network status RFC-321: Turtles RFC-322: Well known RFC-323: A ridiculously long discussion RFC-324: Meeting at UCLA RFC-325: An RJS client at Utah RFC-326: Network status RFC-327: Bye DTP RFC-328: Simplifying Telnet RFC-329: List management
RFC-330: Network status RFC-331: Distant hosts RFC-332: Network status RFC-333: Messaging switching: not just for IMPS anymore RFC-334: ARPA stress test RFC-335: Upgrading the rat's nest RFC-336: Level 0 graphics input RFC-337: Not issued RFC-338: The real world of users and servers RFC-339: Multiplexed Telnet
RFC-340: Telnet changes RFC-341: Not issued RFC-342: Network status RFC-343: No network on Tuesdays RFC-344: Network status RFC-345: Let's share the cost RFC-346: The network: in space! RFC-347: Echo process RFC-348: Discard process RFC-349: The socket czar
RFC-350: Accounting RFC-351: Graphics questionnaire RFC-352: TIP questionnaire RFC-353: Network status RFC-354: A fourth revision of FTP RFC-355: Re: satellites RFC-356: 24/7 support RFC-357: Remote controlled echoing RFC-358: Not issued RFC-359: Continued failure to upgrade
RFC-360: Finally, an RJE protocol RFC-361: Deamons [sic] RFC-362: Network status RFC-363: List management RFC-364: Our documentation sucks RFC-365: A letter