RFC 999
Requests For Comments summary notes: 900-999
Requests For Comments Summary 🎀
Title block, babe: this is RFC 999, titled Requests For Comments Summary, from the Network Working Group 💖. The authors are A. Westine and J. Postel, both at ISI, and it's dated April 1987 📅. The title block doesn't list any obsoletes or updates, and it doesn't name a category 🦋.
Status of this Memo ✨
Okay so this RFC is a slightly annotated list of the 100 RFCs from RFC-900 through RFC-999 📚. It's basically a status report on all of them, and distribution of this memo is unlimited 🌈.
RFC Author Date Title
--- ------ ---- -----
999 Westine Apr 87 Requests For Comments Summary
998 Lambert Mar 87 NETBLT: A Bulk Data Transfer
Protocol
997 Reynolds Mar 87 Internet Numbers
996 Mills Feb 87 Statistics Server
995 ANSI Apr 86 End System to Intermediate System
Routing Exchange Protocol for use in
conjunction with ISO 8473.
994 ANSI Mar 86 Final Text of DIS 8473, Protocol for
Providing the Connectionless Mode
Network Service
993 Clark Dec 86 PCMAIL: A Distributed Mail System for
Personal Computers
992 Birman Nov 86 On Communication Support for
Fault-Tolerant Process Groups
991 Reynolds Nov 86 Official ARPA-Internet Protocols
990 Reynolds Nov 86 Assigned Numbers
989 Linn Feb 87 Privacy Enhancement for Internet
Electronic Mail: Part I: Message
Encipherment and Authentication
Procedures
988 Deering Jul 86 Host Extensions for IP Multicasting
987 Kille Jun 86 Mapping between X.400 and RFC-822
986 Callon Jun 86 Working Draft -- Guidelines for the Use
of Internet-IP addressing in the ISO
Connectionless-Mode Network Protocol
985 Mills May 86 Requirements for Internet Gateways
984 Clark May 86 PCMAIL: A Distributed Mail System for
Personal Computers
983 Cass Apr 86 ISO Transport Services on Top of the
TCP
982 ANSI Apr 86 Guidelines for the Specification of the
Structure of the Domain Specific Part
(DSP) of the ISO Standard NSAP Address999 Westine, Apr 87: Requests For Comments Summary 🍓 This memo, obviously 💅.
998 Lambert, Mar 87: NETBLT, A Bulk Data Transfer Protocol 🚀 This is a description of, and a specification for, NETBLT, and it's a revision of the spec from RFC-969 🔥. NETBLT (NETwork BLock Transfer) is a transport level protocol for rapidly moving a large amount of data between computers ⚡. It's reliable and flow controlled, and it's designed for maximum throughput over a wide variety of networks 🌸. It runs on top of IP right now, but it should be able to operate on top of any datagram protocol that's similar in function to IP 🦋. This doc is published for discussion and comment, and it does not constitute a standard 🙈. The proposal may change, and some parts of the protocol haven't been specified yet, so implementation of this document is not advised 💀. It obsoletes RFC-969 💅.
997 Reynolds, Mar 87: Internet Numbers 🔢 This memo is an official status report on the network numbers used in the Internet community 👑. As of 1-Mar-87, the Network Information Center (NIC) at SRI International took over responsibility for assigning Network Numbers and Autonomous System Numbers 🎀. This RFC documents the current assignments at the time of that handoff 📜. It obsoletes RFC-990, 960, 943, 923 and 900 ✨.
996 Mills, Feb 87: Statistics Server 📊 This RFC specifies a standard for the ARPA Internet community 💜. Hosts and gateways on the DARPA Internet that choose to implement a remote statistics monitoring facility may use this protocol to send statistics data upon request to a monitoring center or a 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 interconnect 🌈. The set covers the services and protocols needed to achieve that interconnection. It sits in the layers defined by the Reference Model for Open Systems Interconnection (ISO 7498) and by the structure defined in the Internal Organization of the Network Layer (DIS 8648), and specifically it's a protocol of the Network Layer 🧠. It lets End Systems and Intermediate Systems swap configuration and routing information, which helps the routing and relaying functions of the Network Layer work 🔁.
994 ANSI, Mar 86: Final Text of DIS 8473, Protocol for Providing the Connectionless Mode Network Service 💌 This Protocol Standard is also one of a set of International Standards for interconnecting open systems 🫶. It's positioned by the layers in ISO 7498, and it's a protocol of the Network Layer 🌟. It may 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 doc discusses the Pcmail workstation-based distributed mail system 💻. It's a revision of the design published in NIC RFC-984 🔄. The revision is based on discussion and comment from a bunch of sources, plus more research into designing interactive Pcmail clients and using client code on machines other than IBM PCs 🌷. Since the design may change, implementation of this document is not advised 🙈. It obsoletes RFC-984 ✨.
992 Birman, Nov 86: On Communication Support for Fault-Tolerant Process Groups 🛡️ This memo describes a collection of multicast communication primitives, combined with a mechanism for handling process failure and recovery 🔥. These primitives make it easier to build fault-tolerant process groups, which can provide distributed services in an environment that's subject to non-malicious crash failures 💅.
991 Reynolds, Nov 86: Official ARPA-Internet Protocols 📖 This RFC identifies the documents that specify the official protocols used in the Internet 👑. Comments indicate any revisions or changes that are planned 🦋. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community 🎀. It obsoletes RFC-961, 944 and 924 💜.
990 Reynolds, Nov 86: Assigned Numbers 🔢 This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations ✨. It's an official status report on the numbers used in protocols in the ARPA-Internet community 📊. For the network numbers, see RFC-997 🧚. It obsoletes RFC-960, 943, 923 and 900 🌸.
989 Linn, Feb 87: Privacy Enhancement for Internet Electronic Mail, Part I, Message Encipherment and Authentication Procedures 🔐 This RFC suggests a proposed protocol for the Internet community, and it requests discussion and suggestions for improvements 🫶. It came out of a series of IAB Privacy Task Force meetings and the internal working papers distributed for them 📝. It defines message encipherment and authentication procedures as the first phase of an effort to provide privacy enhancement services for electronic mail transfer in the Internet 🌈. The procedures are meant to be compatible 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 💖.
988 Deering, Jul 86: Host Extensions for IP Multicasting 📡 This memo specifies the extensions required of a host implementation of IP to support internetwork multicasting 🌐. It supersedes the specification given in RFC-966, and it's a proposed protocol standard for IP multicasting in the ARPA-Internet 💅. If you want the motivation and rationale behind the multicasting extension, the reader is directed to RFC-966 📚.
987 Kille, Jun 86: Mapping between X.400 and RFC-822 📨 The X.400 series protocols were defined by CCITT to provide an Interpersonal Messaging Service (IPMS), using a store and forward Message Transfer Service 💌. This standard is expected to be implemented very widely 🌟. This document describes a set of mappings that enable interworking between systems running the X.400 protocols and systems using the RFC-822 mail protocol or protocols derived from it 🔁. This RFC suggests a proposed protocol for the ARPA-Internet community, and it requests 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 method that lets the existing IP addressing, including the IP protocol field, be used for the ISO Connectionless Network Protocol (CLNP) 🌸. It's a draft solution to one of the problems that come with using "ISO-grams" in the DOD Internet 🦋. Related issues will be discussed in later RFCs 🔜. It suggests a proposed protocol for the ARPA-Internet community, and it requests discussion and suggestions for improvements 💜.
985 Mills, May 86: Requirements for Internet Gateways 🚪 This RFC summarizes the requirements for gateways used on networks that support the DARPA Internet protocols 🌈. It applies specifically to National Science Foundation research programs, but the requirements are stated in a general context and are believed to apply throughout the Internet community 🫶. Its purpose is to give guidance to vendors making products that might be used or adapted for an Internet application 🛠️. It lists the protocols required and gives references to RFCs and other documents describing the current specifications 📚.
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 provides mail service to an arbitrary number of users, and each of them owns one or more personal computers (PCs) 🧸. The system is split into two halves 🌗. The first is a single entity called the "repository" 🗄️. The repository is a storage center for incoming mail, and mail for a Pcmail user can arrive from the Internet or from other repository users 📬. It also keeps a stable copy of each user's mail state, so it's typically a computer with a large amount of disk storage 💾. It's published for discussion and comment, and it does not constitute a standard 🙈. Since the proposal may change, implementation of this document is not advised 💀. See RFC-993 🔗.
983 Cass, Apr 86: ISO Transport Services on Top of the TCP 🚀 This memo describes a proposed protocol standard for the ARPA Internet community 💅. CCITT and ISO have defined various session, presentation, and application recommendations that the international community and lots of vendors have adopted 🌍. As much as possible, it's desirable to offer these higher level services directly in the ARPA Internet without disrupting existing facilities 🌸. That lets users build expertise with ISO and CCITT applications that weren't previously available in the ARPA Internet 🧠. The intention is that hosts in the ARPA-Internet that choose to implement ISO TSAP services on top of TCP are expected to adopt and implement this standard 🫶. Suggestions for improvement are encouraged 💖.
982 ANSI, Apr 86: Guidelines for the Specification of the Structure of the Domain Specific Part (DSP) of the ISO Standard NSAP Address 🏷️
okay so the ANSI bit up top is giving official draft energy 📜🎀. It's a working document from the ANSI "Guidelines for the Specification of the Structure of the Domain Specific Part (DSP) of the ISO Standard NSAP Address" 🌸. Its whole goal is helping private address admins pick nice formats and meanings for the DSP part of an NSAP address, and it spells out how to build the DSP so address assignment is efficient ✨. It's informational only, the distribution is unlimited, and it does not set a standard for the ARPA-Internet 💅.
Now the index! 📚 Each entry is a little RFC glow-up, so I've kept the headers exactly as they are, bestie 🫶.
981 Mills Mar 86 An Experimental Multiple-Path Routing
Algorithmokay so this one is experimental 🧪 and it's all about wiretap algorithms, a whole class of multiple routing algorithms that find quasi-optimum routes for stations sharing a packet-radio broadcast channel 📡. The primary route is a minimum-distance path, and then there are extra paths ordered by distance that act as backups if the primary dies 🦋. The prototype is an example of a family of routing algorithms and database management techniques that could go places in the Internet community 🚀. Discussions and suggestions for improvements are welcomed, so slide into those comments 💜.
980 Jacobsen Mar 86 Protocol Document Order Informationthis one is the ultimate shopping guide 🛍️ for protocol docs used in the DARPA research community 🧚. It has an overview of the new 1985 DDN Protocol Handbook and tells you where to grab related docs, like DOD, ISO, and CCITT ones 🍓.
9979 Malis Mar 86 PSN End-to-End Functional Specificationthis one is serious business 💀. It's an updated version of BBN Report 5775, and the original says "End-to-End Functional Specification and describes important changes to the functionality of the interface between a Host and the PSN, and should be carefully reviewed by anyone involved in supporting a host on either the ARPANET or MILNET" 👑. The new End-to-End protocol (EE) is being built to fix a bunch of problems with the old EE 🔧, boost performance and throughput 🚄, and help the Packet Switch Node (PSN, also known as the IMP) keep up with its current and future host population 🌈.
978 Reynolds Feb 86 Voice File Interchange Protocol (VFIP)the VFIP is all about letting different systems in the ARPA-Internet community swap different kinds of speech files 🎙️🦋. Suggestions for improvement are encouraged, so spill the tea ☕.
977 Kantor Feb 86 Network News Transfer ProtocolNNTP is giving news feed vibes 📰✨. It's a protocol for distributing, inquiring about, retrieving, and posting news articles, using reliable stream-based transmission across the ARPA-Internet community 💌. News articles get stored in a central database, so a subscriber can pick out only the items they actually want to read 🍿. It also covers indexing, cross-referencing, and expiration of old messages 🗑️. This RFC suggests it as a proposed protocol for the ARPA-Internet community and asks for discussion and suggestions for improvements 💖.
976 Horton Feb 86 UUCP Mail Interchange Format Standardthis one defines the standard format for sending mail messages between computers in the UUCP Project 📬. It doesn't cover how messages are stored on one machine, or the lower-level transport mechanisms that move the date from one machine to the next 🚚. It's a standard for conformance by hosts in the UUCP zone 🌸.
975 Mills Feb 86 Autonomous Confederationsooh this one is so pretty 🦋. It proposes enhancements to the Exterior Gateway Protocol (EGP) for simple, multiple-level routing, and it keeps the robustness features of the current EGP model 🛡️. The big idea is generalizing the concept of a 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 one explains how mail systems on the Internet are expected to route messages using information from the domain system 📮. It talks about how mailers interpret MX RRs, which are used for message routing 🗺️.
973 Mockapetris Jan 86 Domain System Changes and Observationsthis one documents updates to the Domain Name System specifications RFC-882 and RFC-883 🌐. It also suggests some operational guidelines and shares experiences and problem areas in the present system 🔍.
972 Wancho Jan 86 Password Generator Protocolthe Password Generator Service (PWDGEN) is literally so iconic 🔐✨. It gives you six randomly generated eight-character "words" with a reasonable level of pronounceability, using a multi-level algorithm 🎲. This RFC specifies a standard for the ARPA Internet community, and hosts that choose to implement a password generator service are expected to adopt and implement it 💅.
971 DeSchon Dec 85 A Survey of Data Representation
Standardsthis is a comparison of several data representation standards that are in use right now 📊. The ones covered 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 🧩. Nothing in it is meant as a standard for the ARPA-Internet at this time 🙈. The hope is that a general consensus forms about the right approach, which could eventually lead to an ARPA-Internet standard 🌈.
970 Nagle Dec 85 On Packet Switches With Infinite
Storagethis one is a plot twist 😭. Most earlier work on congestion in datagram systems focuses on buffer management, but this memo looks at a packet switch with infinite storage 🌊. That kind of switch can never run out of buffers, but it can still get congested 🚦. The memo explores what congestion even means in an infinite-storage system 🤯. The unexpected result: 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 💀. Attacking congestion in the infinite-storage case might reveal new solutions for switches with finite storage ✨. 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 one suggests a proposed protocol for the ARPA-Internet community and asks for discussion and suggestions for improvements 🚚💨. It's a preliminary discussion of the Network Block Transfer (NETBLT) protocol, which is built for rapidly moving a large quantity of data between computers 📦. It's reliable and flow controlled, and it's structured to give maximum throughput over a wide variety of networks 🌸. It's published for discussion and comment, and it does not constitute a standard 🙅. Since the proposal may change, implementing this document is not advised ⚠️. See RFC-998 🔗.
968 Cerf Dec 85 'Twas the Night Before Start-up'this memo is giving spooky-but-cute 🌙👻. It talks about the problems that come up, and the 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 gets integrated with various operating systems 🧑💻. It seems this topic hasn't gotten enough exposure in the literature yet, so comments and suggestions are encouraged 💜.
966 Deering Dec 85 A Multicast Extension to the Internet
Protocolmulticast is the main character here 📡💖. It defines a model of service for Internet multicasting and proposes an extension to the Internet Protocol (IP) to support that multicast service 🎀. Discussion and suggestions for improvements are requested 🫶. See RFC-988 🔗.
965 Aguilar Dec 85 A Format for a Graphical Communication
Protocolthis one lays out the requirements for a graphical format to base a graphical on-line communication protocol on 🎨. It proposes an Interactive Graphical Communication Format that uses the GKSM session metafile 🖼️. The authors hope it gets people talking about multimedia data exchange and coming up with solutions 🌈.
964 Sidhu Nov 85 Some Problems with the Specification of
the Military Standard Transmission
Control Protocolthe purpose here is to give helpful info on the Military Standard Transmission Control Protocol (MIL-STD-1778), so you can get a reliable implementation of that protocol standard 🛡️. It points out three errors in this specification 🙈 and also proposes solutions to those problems 💅.
963 Sidhu Nov 85 Some Problems with the Specification of
the Military Standard Internet Protocolsame energy as the one above 🫶. The purpose is to give helpful info on the Military Standard Internet Protocol (MIL-STD-1777), so you can get a reliable implementation 🔧. It points out several problems in this specification and also proposes solutions to them 🍓.
962 Padlipsky Nov 85 TCP-4 Primethis memo responds to Bob Braden's call for a transaction oriented protocol (RFC-955) 📞, and it keeps the conversation going about a possible transaction oriented transport protocol 🌷. It does not propose a standard 🙅♀️.
961 Reynolds Dec 85 Official ARPA-Internet Protocolsthis is the official source of truth 👑✨. It identifies the documents that specify the official protocols used in the Internet and comments on any revisions or changes that are planned 🗂️. This edition of the Official Protocols updates and obsoletes RFC-944 🔄. It's an official status report on the protocols used in the ARPA-Internet community, and it's a follow-up to RFC-991 🔗.
960 Reynolds Dec 85 Assigned Numbersthis memo documents the currently assigned values from several series of numbers used in network protocol implementations 🔢. This edition of Assigned Numbers updates and obsoletes RFC-943 🔄. It's an official status report on the numbers used in protocols in the ARPA-Internet community, and it sends you on to RFC-990 and 997 🗺️.
959 Postel Oct 85 File Transfer Protocol (FTP)the OG FTP spec, bestie 📁💚. This memo is the official specification of the File Transfer Protocol (FTP) for the DARPA Internet community 🎀. The main goal is to clarify and correct the FTP documentation, not to change the protocol 🙌. The following new optional commands show up in this edition: Change to Parent Directory (CDUP), Structure Mount (SMNT), Store Unique (STOU), Remove Directory (RMD), Make Directory (MKD), Print Directory (PWD), and System (SYST) 🧚. Also, this specification is compatible with the previous edition 🫶.
958 Mills Sep 85 Network Time Protocol (NTP)The NTP entry's header got cut off in the copy, so here's just its description 🕰️✨
Okay, so this one describes the Network Time Protocol (NTP) 💖, a way for a bunch of network clocks to stay in sync using a group of distributed clients and servers. NTP runs on top of UDP, which is connectionless transport, so no handshake drama 🦋. It evolved from the Time Protocol and the ICMP Timestamp message, and it's a suitable replacement for both 👑. This RFC proposes a protocol for the ARPA-Internet community and asks for discussion and suggestions for improvements 🎀.
957 Mills Sep 85 Experiments in Network Clock
SynchronizationNext up is Mills' experiments write-up 🧚. It talks about clock sync experiments in the ARPA-Internet community and, again, asks for discussion and suggestions for improvements. Here's the thing nobody talks about: a really good time-of-day clock that gives accurate timestamps with tiny errors compared to one-way network delays is so often ignored in network design 😭. It's super useful for tracing complex transactions, syncing cached databases, monitoring network 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 💅.
956 Mills Sep 85 Algorithms for Synchronizing Network
ClocksThis one covers clock sync algorithms for the ARPA-Internet community, also asking for discussion and suggestions for improvements 🌈. Why the big interest in finding accurate time from a set of mutually suspicious network clocks? Because usually reliable, accurate clock servers have been caught with errors after thunderstorms knocked out their power supply ⚡💀. Add malfunctioning hardware, buggy software, operator mistakes, and random errors in how clocks get set and synchronized, and you've got a lot of ways to go wrong 🙈. 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 includes experiments that show how well the algorithms work 💜.
955 Braden Sep 85 Towards a Transport Service for
Transaction Processing ApplicationsBraden is looking at the DoD Internet protocol suite, which has two transport options, TCP and UDP. TCP gives virtual circuit service and UDP gives datagram service 🍓. These two sit really far apart in the space of possible transport service attributes 🙃. The point is that transaction processing apps land in the gap between them, and neither protocol is a great fit for that 😤. The RFC is about possibly designing one or more new protocols for the ARPA-Internet to support applications that aren't well supported right now ✨. It's meant to spark discussion in the Internet research community about new protocols and/or concepts that could meet these unmet requirements 🫶. It is not a standard, and it's not even a concrete protocol proposal, just a conversation starter 🌸.
954 Harrenstien Oct 85 NICNAME/WHOISThis is the official spec for the NICNAME/WHOIS protocol 📚. It describes both the protocol and the service. It's an update of RFC-812 🎀.
953 Harrenstien Oct 85 Hostname ServerThis is the official spec for the Hostname Server Protocol 💅. This edition has minor revisions to RFC-811 that bring it up to date ✨.
952 Harrenstien Oct 85 DoD Internet Host Table SpecificationThis is the official spec for the format of the Internet Host Table 🌈. This edition has minor revisions to RFC-810 that bring it up to date 🦋.
951 Croft Sep 85 Bootstrap Protocol (BOOTP)BOOTP is an IP/UDP bootstrap protocol that lets a diskless client machine discover its own IP address, the address of a server host, and the name of a file to load into memory and execute 🫶. The bootstrap has TWO PHASES 😱. This RFC covers the first one, which you could call address determination and bootfile selection. Once that address and filename info is in hand, control moves to the second phase, where a file transfer happens 🔥. That transfer will typically 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 💖. 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 talks about why "subnets" are useful. Subnets are logically visible sub-sections of a single Internet network 🍓. For admin or technical reasons, lots of orgs split one Internet network into several subnets instead of getting a bunch of Internet network numbers 💜. This memo specifies procedures for using subnets, and they're meant for hosts like workstations 🖥️. How subnet gateways do their thing isn't fully described here 🙈. Motivation and background for a subnetting standard are in RFC-940 📖. This RFC specifies a protocol for the ARPA-Internet community. If you implement subnetting, it is strongly recommended that you follow these procedures 💅✨.
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 the sender name the file, 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 🌸. See RFC-959 🎀.
948 Winston Jun 85 Two Methods for the Transmission of IP
Datagrams Over IEEE 802.3 NetworksThis one describes two ways to encapsulate Internet Protocol (IP) datagrams on an IEEE 802.3 network 🌈. It suggests a proposed protocol for the ARPA-Internet community and asks for discussion and suggestions for improvements 🫶.
947 Lebowitz Jun 85 Multi-Network Broadcasting Within the
InternetThis RFC extends a network's broadcast domain so it covers more than one physical network, using a broadcast packet repeater 📡✨.
946 Nedved May 85 Telnet Terminal Location Number OptionLots of systems let you find out where a user is logged in, usually with the telephone extension and office occupant names 📞. That's great for physically finding people or calling them 💖. Back 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) 🧠. It now makes sense to bring this mechanism into the TCP-based network protocol family 🦋. It isn't meant to replace the Terminal Location Telnet Option (SEND-LOCATION), but works as a shorthand for sharing 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 ReportIn May 1983, the National Research Council (NRC) was asked by DoD and NBS to study the issues and recommend a course of action 📜. The NRC's final report came out in February 1985 (see RFC-942) 💅. The enclosed letter is from Donald C. Latham (ASDC3I) to DCA, sending the NRC report and asking for specific actions based on its recommendations 🍓. 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) 🎀. It's distributed for information only 👑.
944 Reynolds Apr 85 Official ARPA-Internet ProtocolsThis RFC identifies the documents that specify the official protocols used in the Internet 📚✨. This edition obsoletes RFC-924 and earlier editions 🙈. It'll be updated periodically, and you can get current info from Joyce Reynolds 💜. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991 🌈.
943 Reynolds Apr 85 Assigned Network NumbersThis Network Working Group RFC documents the currently assigned values from several series of numbers used in network protocol implementations 🔢. It'll be updated periodically, and current info can always come from Joyce Reynolds 🧚. Joyce also handles number assignments. If you're developing a protocol or application that needs a link, socket, port, protocol, network number, etc., contact Joyce to get one assigned 🫶. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-990 and 997 💅.
942 NRC Feb 85 Transport Protocols for Department of
Defense Data NetworksThis RFC reproduces the National Research Council report from a study comparing the DoD Internet Protocol (IP) and Transmission Control Protocol (TCP) with the ISO Internet Protocol (ISO-IP) and Transport Protocol level 4 (TP-4) 🔥.
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 connection-mode Network Service primitives as the calling address, called address, and responding address parameters, and in connectionless-mode Network Service primitives 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 🙃.
9
940 GADS Apr 85 Toward an Internet Standard Scheme for
SubnettingOkay bestie, so picture a bunch of sites with a whole cluster of local links, all hooked up to the Internet through one gateway 🌸 The inside stuff is kinda boring to everyone else out there, right? One way to organize all those local links is to copy the way the Internet organizes networks. You treat each link like its own entity (like a network) and connect them with devices that do the routing (like gateways) 🧚 This whole setup is called subnetting, the individual links are subnets, and the connecting devices are subgateways (or bridges, or gateways, depending on who you ask) 💅 This RFC is all about standardizing the protocol used in these subnetted environments in the ARPA-Internet ✨
939 NRC Feb 85 Executive Summary of the NRC Report on
Transport Protocols for Department of
Defense Data NetworksOkay this one is a big deal 📚 It reproduces the "front pages" from a National Research Council report that studied the DOD Internet Protocol (IP) and Transmission Control Protocol (TCP) next to the ISO Internet Protocol (ISO-IP) and Transport Protocol level 4 (TP-4). The whole point is to get the Executive Summary out to everyone quickly 🙌 The order got shuffled and the pagination changed, and it's distributed for information only. It does not establish any policy for the DARPA research community or the DDN operational community, so don't go reading it as a rule 💀
938 Miller Feb 85 Internet Reliable Transaction Protocol
Functional and Interface SpecificationThis one went out to members of the DARPA research community to get their reactions to the proposals inside 🦋 Yes, the issues might not be directly relevant to the research problems of the DARPA community, but a bunch of researchers and implementors might still find it super interesting. It suggests a proposed protocol for the ARPA-Internet community and asks for discussion and suggestions for improvements 🫶
937 Reynolds Feb 85 Post Office Protocol - Version 2Main character energy 👑 This RFC suggests a simple way for workstations to dynamically access mail from a mailbox server. It specifies a proposed protocol for the ARPA-Internet community and requests discussion and suggestions for improvement. Also, this memo is a revision of RFC-918, so it's the glow-up version 💖
936 Karels Feb 85 Another Internet Subnet Addressing
SchemeOkay so there have been a bunch of proposals for letting a single Internet network number stand in for a whole collection of physical networks under common administration, as long as they're reachable from the rest of the Internet by a common route 🌈 The payoff is a simplified view of a complicated topology for hosts and gateways outside that collection. The complexity of the number and type of those networks, plus the routing to them, stays local. So additions and changes in configuration cause no detectable change and no interruption of service, because routing and other information doesn't have to slowly propagate outside the local environment. These schemes also make administration easier, since changes don't need a new network number for every new cable installed 🔥 This proposal talks about an alternative scheme that has been in use at the University of California, Berkeley since April 1984. It suggests a proposed protocol for the ARPA-Internet community and requests discussion and suggestions for improvements.
935 Robinson Jan 85 Reliable Link Layer ProtocolsThis one looks at protocols proposed recently in RFCs 914 and 916, and suggests a proposed protocol that could meet the same needs those memos addressed ⭐ The stated need is reliable communication between two programs over a full-duplex, point-to-point communication link. The RFCs in particular care about that over an asynchronous link at relatively low speeds. The suggested protocol uses the methods of existing national and international data link layer standards, which is very iconic of it 💅 It's a proposed protocol for the ARPA-Internet community, so discussion and suggestions for improvements are welcome.
934 Rose Jan 85 Proposed Standard for Message
EncapsulationSo this memo is about message forwarding 📨 Forwarding is basically encapsulating one or more messages inside another. Handy for passing old correspondence along to new recipients, BUT without a decapsulation process (which this memo calls "bursting"), the forwarded messages are kinda useless to the people receiving them. They can't be distributed, forwarded, replied-to, or otherwise processed as separate individual messages 😭 To burst a message, you need to know how the component messages were encapsulated in the draft. Right now there's no unambiguous standard for interest group digests. This RFC proposes a proposed protocol for the ARPA-Internet community and requests discussion and suggestions for improvements.
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 software is running in the Server-Telnet 🎀
932 Clark Jan 85 A Subnetwork Addressing SchemeThis RFC proposes an alternative addressing scheme for subnets that, in most cases, needs zero changes to host software 🧚 The catch is that the total number of subnets in any one network is limited, and every gateway has to be modified 🙈
931 StJohns Jan 85 Authentication ServerBestie, this is the second draft of this proposal, and it supersedes RFC-912 🍓 It adds a more formal description of the syntax for the request and response dialog, plus a change to specify the type of user identification that gets returned. It's a proposed protocol for the ARPA-Internet community, so discussion and suggestions for improvements are requested.
930 Solomon Jan 85 Telnet Terminal Type OptionThis one specifies a standard for the ARPA Internet community 🌸 Hosts on the ARPA Internet that exchange terminal type information within the Telnet protocol are expected to adopt and implement this standard. It supersedes RFC-884. The only change is that the TERMINAL-TYPE IS sub-negotiation should be sent only in response to the TERMINAL-TYPE SEND sub-negotiation. That's a small change but it matters, so don't skip it 👀
929 Lilienkamp Dec 84 Proposed Host-Front End ProtocolThe Host-Front End Protocol introduced in RFC-928 gets described in detail here 💜 The first order of business is to declare that THIS IS A PROPOSAL, NOT A FINAL STANDARD. The second is to request that any readers who are able to do test implementations (a) do so and (b) coordinate their efforts with the author. It suggests a proposed protocol for the ARPA-Internet community and requests discussion and suggestions for improvements.
928 Padlipsky Dec 84 Introduction to Proposed DOD Standard
H-FPOkay so the broad outline of the Host-Front End Protocol introduced here (and described in RFC-929) came out of the deliberations of a bunch of experienced H-FP designers. They sat as a committee of the DoD Protocol Standards Technical Panel 🫡 The designers intend for the protocol to go through multiple test implementations and probable iteration before anyone agrees on it as any sort of "standard" 🔥
So, the first order of business is to declare that THIS IS A PROPOSAL, NOT A FINAL STANDARD, and the second is to request that any readers who are able to do test implementations (a) do so and (b) coordinate their efforts with the author. This RFC suggests a proposed protocol for the ARPA-Internet community and requests discussion and suggestions for improvements ✨
927 Anderson Dec 84 TACACS User Identification Telnet
OptionThis is a TELNET option designed to help with double login avoidance 🔐 It's mainly meant for TAC connections to target hosts on behalf of TAC users, but honestly it can be used between any two consenting hosts. For example, all hosts at one site (e.g., BBN) can use this option to avoid double login when TELNETing to one another 💖 It suggests a proposed protocol for the ARPA-Internet community and requests discussion and suggestions for improvements.
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 prepared by retyping the text of ISO DIS 8473 of May 1984, which is currently undergoing voting within ISO as a Draft International Standard (DIS). It's distributred as an RFC for information only, and it does not specify a standard for the ARPA-Internet. Read it, don't implement it as the rule 🙈
925 Postel Oct 84 Multi-LAN Address ResolutionHere's the tea ☕ Treating a set of local area networks (LANs) as one Internet network has gotten some interest and concern. Giving each LAN within a site its own distinct Internet network number is inappropriate. It's desirable to hide the details of the interconnections between the LANs within a site from people, gateways, and hosts outside that site. The question is how to do that, and even whether it can be done at all 🤔 In RFC-917, Jeffery Mogul makes a case for "explicit subnets" in a multi-LAN environment. The explicit subnet scheme is basically a call to recursively apply the mechanisms the Internet uses to manage networks to the problem of managing LANs within one network.
The author urges another approach: "transparent subnets" supported by a multi-LAN extension of the Address Resolution Protocol 🦋 This RFC suggests a proposed protocol for the ARPA-Internet community and requests discussion and suggestions for improvements.
924 Reynolds Oct 84 Official ARPA-Internet ProtocolsThis RFC identifies the documents specifying the official protocols used in the Internet 📋 This edition of Official ARPA-Internet Protocols obsoletes RFC-900 and earlier editions. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991 for more 💅
923 Reynolds Oct 84 Assigned NumbersThis RFC documents the currently assigned values from several series of numbers used in network protocol implementations 🔢 This edition of Assigned Numbers obsoletes RFC-900 and earlier editions. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-990, and 997 ✨
922 Mogul Oct 84 Broadcasting Internet Datagrams in the
Presence of SubnetsLast one in this batch, and it's a good one 📡 We propose 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 requests discussion and suggestions for improvements 🌈
921 · Domain Name System Implementation Schedule - Revised ✨
Author: Postel · Date: Oct 84 💅
okay bestie, this one is a policy statement 🎀 It's about the schedule for rolling out the Domain Style Naming System across the Internet. It updates RFC-881 and RFC-897. It's an official policy statement from the IAB and the DARPA, and the memo itself only covers the schedule. If you want to know how the system actually works, the references have you covered 📚
920 · Domain Requirements 🌸
Author: Postel · Date: Oct 84 🦋
this memo lays out what you need to set up a new domain 🌈 It also introduces the limited set of top level domains. It's a policy statement on the requirements for creating a new domain in the ARPA-Internet and the DARPA research community, and it's an official policy statement from the IAB and the DARPA. main character energy ✨
919 · Broadcasting Internet Datagrams 📡
Author: Mogul · Date: Oct 84 🫶
this RFC proposes simple rules for broadcasting Internet datagrams on local networks that support broadcast 💜 It also covers how broadcasts get addressed and how gateways should handle them. It's a proposed protocol for the ARPA-Internet community, and it's asking for discussion and suggestions for improvements. bring your ideas 🔥
918 · Post Office Protocol (POP) 💌
Author: Reynolds · Date: Oct 84 🧚
okay so this one is a simple way for workstations to grab mail from a mailbox server, dynamically, whenever they need to 📬 The Post Office Protocol (POP) lets a user's workstation access mail sitting on a mailbox server. Mail is expected to get posted from the workstation to that server over the Simple Mail Transfer Protocol (SMTP). It's a proposed protocol for the ARPA-Internet community, and it's asking for discussion and suggestions for improvement. The status is experimental, and it depends on TCP 🎀 it's giving very early-days vibes 🙈
917 · Internet Subnets 🍓
Author: Mogul · Date: Oct 84 ✨
this memo is all about subnets and proposes procedures for using them 🌸 It also looks at how to solve the problems that come up, especially the routing one, which is literally the hardest part 😭 A subnet is a logically visible sub-section of a single Internet network. For administrative or technical reasons, lots of organizations chose to split one Internet network into several subnets instead of getting a whole set of Internet network numbers. It's a proposed protocol for the ARPA-Internet community, and it wants discussion and suggestions for improvements 🦋
916 · Reliable Asynchronous Transfer Protocol (RATP) 🔥
Author: Finn · Date: Oct 84 💜
this one proposes and specifies a protocol that lets two programs communicate reliably over a communication link 🫶 The guarantee is that whatever data goes in one end of the link arrives at the other end intact and unaltered. RATP is designed to run over a full duplex point-to-point connection, and it has some features tuned for the RS-232 links that were super common at the time. It's a proposed protocol for the ARPA-Internet community, and it's asking for discussion and suggestions for improvements. reliability is the whole personality 👑
915 · Network Mail Path Service 🗺️
Author: Elvy · Date: Dec 84 🌈
this RFC proposed a new service for the ARPA-Internet community and asks for discussion and suggestions for improvements 💅 The network mail path service solves a real problem: figuring out mailbox addresses for hosts that aren't part of the ARPA-Internet but can still be reached through one or more relay hosts with UUCP (Unix to Unix Copy) mail, CSNET mail, MAILNET mail, BITNET mail, and so on. Anyone can use the service as long as they have TCP/TELENET access to one of the hosts with a mail path server. it's so helpful, ngl 🥹
914 · A Thinwire Protocol 💻
Author: Farber · Date: Sep 84 🌸
this one focuses the discussion on the particular problems of low speed network interconnection with personal computers in the ARPA-Internet, plus some 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. it's giving "let's figure it out together" energy 🫶
913 · Simple File Transfer Protocol 📁
Author: Lottor · Date: Sep 84 🦋
this 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 file deleting. Discussion is encouraged, and suggestions for improvements can be sent to the author 📬
912 · Authentication Service 🔐
Author: StJohns · Date: Sep 84 💜
this memo describes a proposed authentication protocol for verifying the identity of a user on 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 automatically identifying and verifying a user during an FTP session, extra verification for a TAC dial-up user, and access verification for a generalized network file server. verification era, bestie ✨
911 · EGP Gateway under Berkeley Unix 4.2 🌱
Author: Kirton · Date: Aug 84 🍓
this memo describes an implementation of the Exterior Gateway Protocol (EGP), so in that sense it's a status report 📊 It also discusses some possible extensions and design issues, so in that sense it's an invitation for more discussion 🫶
910 · Multimedia Mail Meeting Notes 🎞️
Author: Forsdick · Date: Aug 84 🌸
this memo is a report on a meeting about the experimental multimedia mail system, and in a way it's a status report on that experiment too 🦋 The meeting happened at Bolt Beranek and Newman on 23-24 July 1984. The goal was to talk about recent progress from groups building multimedia mail systems and to discuss a bunch of issues around developing multimedia systems further. Representatives came from BBN, ISI, SRI, and Linkabit. the guest list is iconic 👑
909 · Loader Debugger Protocol 🛠️
Author: Welles · Date: Jul 84 💖
okay so the Loader Debugger Protocol (LDP) is an application layer protocol for loading, dumping, and debugging target machines from hosts over a network 🧚 This RFC specifies a proposed protocol for the ARPA-Internet and DARPA research community, and it requests discussion and suggestions for improvements 💬
908 · Reliable Data Protocol 📦
Author: Velten · Date: Jul 84 ✨
the Reliable Data Protocol (RDP) is designed to provide a reliable data transport service for packet-based applications 🎀 This RFC specifies a proposed protocol for the ARPA-Internet and DARPA research community, and it requests discussion and suggestions for improvements 🫶
907 · Host Access Protocol Specification 🛰️
Author: Storch · Date: Jul 84 🌈
this 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 different satellite networks get supported. Anyone implementing HAP should coordinate with satellite network development and operations personnel 🔥
906 · Bootstrap Loading Using TFTP 🥾
Author: Finlayson · Date: Jun 84 💅
it's often really handy 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. simple but iconic 💖
905 · ISO Transport Protocol Specification (ISO DP 8073) 📜
Author: ISO · Date: Apr 84 🦋
this is the current specification of the ISO Transport Protocol 🌟 The document is the text of ISO/TC97/SC16/N1576, as corrected by ISO/TC97/SC16/N1695. It's the specification currently 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. Big thanks to Alex McKenzie of BBN for making this online version available 🫶
heads up, bestie: the file is huge. Please note the size of this document, the file contains 258,729 characters 🙈💀
904 · Exterior Gateway Protocol Formal Specification 🌐
Author: Mills · Date: Apr 84 💜
RFC-904 is the specification of the Exterior Gateway Protocol (EGP) 👑 It 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. it's official, it's formal, it's slay 💅
903 · A Reverse Address Resolution Protocol 🔄
Author: Finlayson · Date: Jun 84 🧚
this RFC suggests a method for workstations to dynamically find their protocol address (for example, their Internet Address) when all they know is their hardware address (for example, their attached physical network address) 🌸 This RFC specifies a proposed protocol for the ARPA Internet community, and it requests discussion and suggestions for improvements 🫶
902 · ARPA-Internet Protocol Policy 📋
Author: Postel · Date: Jul 84 🎀
this memo explains how protocol standards get adopted for the ARPA-Internet and the DARPA research community 💖 There are three important aspects: the process, the authority, and the complex relationship between the DARPA community and the DDN community 🌈 It's a policy statement on how protocols become official standards for the ARPA-Internet and the DARPA research community, and it's an official policy statement from the ICCB and the DARPA. this one's the rulebook, bestie 📖
901 · Official ARPA-Internet Protocols 📚
Author: Reynolds · Date: Jun 84 ✨
this RFC identifies the documents that specify the official protocols used in the ARPA-Internet 🦋 Annotations flag any revisions or planned changes. It's an official status report on the protocols used in the DARPA research community. See RFC-991 💜
900 · Assigned Numbers 🔢
Author: Reynolds · Date: Jun 84 🫶
this RFC specifies the parameter values used in the Internet family of protocols, like network numbers, well known ports, protocol types, and version numbers 🌟 It's an official status report on the protocol parameters used in the Internet protocol system. See RFC-990 and 997 🎀 that's the whole list, bestie 💅✨
📦 where this page comes from
- ietf: rfc999 1987-04
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms