RFC 1099
Request for Comments Summary: RFC Numbers 1000-1099
Request for Comments Summary ✨
Okay bestie, let's do the vibes check first 💅 This is RFC 1099, called Request for Comments Summary (RFC Numbers 1000-1099). It came out of the Network Working Group 🌸 and was written by J. Reynolds at ISI in December 1991. It's basically an annotated list of the RFCs from 1000 through 1099 🦋 Its status is that it provides information for the Internet community and does not specify an Internet standard. Distribution is unlimited. The header doesn't list anything it obsoletes or updates, so there's nothing to chase down there 🫶
Status of This Memo 📜
So this memo is a slightly annotated list of the 100 RFCs from RFC 1000 through RFC 1099 🌈 It's a status report on those RFCs. It provides information for the Internet community, it does not specify an Internet standard, and distribution of it is unlimited 💖
The Index 📚
Here's the lineup, straight from the original table, so you can scroll and see everything at a glance:
RFC Author Date Title
--- ------ ---- -----
1099 Reynolds Dec 91 Requests For Comments Summary
1098 Case Apr 89 A Simple Network Management
Protocol (SNMP)
1097 Miller Apr 89 Telnet Subliminal-Message Option
1096 Marcy Mar 89 Telnet X Display Location Option
1095 Warrier Apr 89 The Common Management Information
Services and Protocol over TCP/IP
(CMOT)
1094 Sun Mar 89 NFS: Network File System
Protocol Specification
1093 Braun Feb 89 The NSFNET Routing Architecture
1092 Rekhter Feb 89 EGP and Policy Based Routing
in the New NSFNET Backbone
1091 VanBokkelen Feb 89 Telnet Terminal-Type Option
1090 Ullmann Feb 89 SMTP on X.25
1089 Schoffstall Feb 89 SNMP over Ethernet
1088 McLaughlin Feb 89 A Standard for the Transmission of IP
Datagrams over NetBIOS Networks
1087 IAB Jan 89 Ethics and the Internet
1086 Onions Dec 88 ISO-TP0 bridge between TCP and X.25
1085 Rose Dec 88 ISO Presentation Services
on top of TCP/IP-based internets
1084 Reynolds Dec 88 BOOTP Vendor Information Extensions
1083 IAB Dec 88 IAB Official Protocol Standards
1082 Rose Nov 88 Post Office Protocol - Version 3
Extended Service Offerings
1081 Rose Nov 88 Post Office Protocol - Version 3
1080 Hedrick Dec 88 Telnet Remote Flow Control Option
1079 Hedrick Dec 88 Telnet Terminal Speed Option
1078 Lottor Nov 88 TCP Port Service Multiplexer (TCPMUX)
1077 Leiner Nov 88 Critical Issues in High Bandwidth
Networking
1076 Trewitt Nov 88 HEMS Monitoring and Control Language
1075 Waitzman Nov 88 Distance Vector Multicast Routing
Protocol
1074 Rekhter Oct 88 The NSFNET Backbone SPF based Interior
Gateway Protocol
1073 Waitzman Oct 88 Telnet Window Size Option
1072 Jacobson Oct 88 TCP Extensions for Long-Delay Paths
1071 Braden Aug 88 Computing the Internet ChecksumThe Annotated Entries 💅
RFC 1099 · Requests For Comments Summary 🎀
Yes, this memo. The summary is summarizing itself. Iconic behavior, honestly 🙈
RFC 1098 · A Simple Network Management Protocol (SNMP) 🔥
This one is a re-release of RFC 1067, with a changed "Status of this Memo" section 🔁 It defines a simple protocol that lets management information for a network element be inspected or altered by logically remote users 🖥️ Paired with its companion memos (the ones describing how management information is structured and the initial management information base), it gives you a simple, workable architecture and system for managing TCP/IP-based internets and especially the Internet 🌐
RFC 1097 · Telnet Subliminal-Message Option 🫣
This one specifies a standard for the Internet community 💜 Hosts on the Internet that display subliminal messages within the Telnet protocol are expected to adopt and implement this standard. Yes, this is real 🙈
RFC 1096 · Telnet X Display Location Option 🖥️
Another standard for the Internet community ✨ Hosts that transmit the X display location within the Telnet protocol are expected to adopt and implement this standard.
RFC 1095 · The Common Management Information Services and Protocol over TCP/IP (CMOT) 🧚
This memo defines a network management architecture that uses ISO's (the International Organization for Standardization's) Common Management Information Services/Common Management Information Protocol (CMIS/CMIP) in a TCP/IP environment 🌸 It gives a way for control and monitoring information to be exchanged between a manager and a remote network element. It defines how to implement the Draft International Standard (DIS) version of CMIS/CMIP on top of Internet transport protocols, so it can carry management information defined in the Internet-standard management information base. DIS CMIS/CMIP is suitable for deployment in TCP/IP networks while CMIS/CMIP moves toward becoming an International Standard 💅 Together with the relevant ISO standards and the companion RFCs that describe the initial structure of management information and the management information base, these documents provide the basis for a comprehensive architecture and system for managing TCP/IP-based internets, and in particular the Internet 👑
RFC 1094 · NFS: Network File System Protocol Specification 📁
This one describes a protocol that Sun Microsystems, Inc., and others are using 💖 A new version is under development, but others may still benefit from the descriptions of the current protocol and the discussion of some design issues.
RFC 1093 · The NSFNET Routing Architecture 🛣️
This document describes the routing architecture for the NSFNET, centered around the new NSFNET Backbone. It puts specific emphasis on the interface between the backbone and its attached networks 🦋
RFC 1092 · EGP and Policy Based Routing in the New NSFNET Backbone 🧭
This memo discusses implementation decisions for routing issues in the NSFNET, especially in the NSFNET Backbone 💅 The big concern here is restricting routing information so that it only advertize*s* the best route as established by a policy decision.
RFC 1091 · Telnet Terminal-Type Option ⌨️
This one specifies a standard for the Internet community ⭐ Hosts on the Internet that exchange terminal type information within the Telnet protocol are expected to adopt and implement this standard. This standard supersedes RFC 930. A change is made to permit cycling through a list of possible terminal types and selecting the most appropriate one 🔄
RFC 1090 · SMTP on X.25 📬
This memo proposes a standard for SMTP on the virtual circuit facility provided by the X.25 standard of the CCITT 🌈
RFC 1089 · SNMP over Ethernet 🔌
This memo describes an experimental method for using the Simple Network Management Protocol (SNMP) over Ethernet MAC layer framing, instead of the Internet UDP/IP protocol stack 🧪 It's useful for LAN based network elements that support no higher layer protocols beyond the MAC sub-layer.
RFC 1088 · A Standard for the Transmission of IP Datagrams over NetBIOS Networks 📦
This document specifies a standard method of encapsulating Internet Protocol (IP) datagrams on NetBIOS networks 💜
RFC 1087 · Ethics and the Internet ⚖️
This memo is a statement of policy from the Internet Activities Board (IAB) about the proper use of the resources of the Internet 🫶 Ethics era, honestly.
RFC 1086 · ISO-TP0 bridge between TCP and X.25 🌉
This memo proposes a standard for the Internet community 💅 Hosts on the Internet that choose to implement ISO TP0 transport connectivity between TCP and X.25 based hosts are expected to experiment with this proposal. TCP port 146 is reserved for this proposal 🧚
RFC 1085 · ISO Presentation Services on top of TCP/IP-based internets 🎀
RFC 1006 describes a mechanism for providing the ISO transport service on top of TCP/IP ✨ Once that method is applied, you can implement "real" ISO applications on top of TCP/IP-based internets, just by implementing OSI session, presentation, and application services on top of the transport service access point that's provided on top of TCP. It's straightforward, but there are some environments where the richness of the OSI application layer is desired, and it's still impractical to implement the underlying OSI infrastructure (the presentation, session, and transport services on top of TCP) 😭 This memo describes an approach for providing "stream-lined" support of OSI application services on top of TCP/IP-based internets for those constrained environments. This memo proposes a standard for the Internet community 👑
RFC 1084 · BOOTP Vendor Information Extensions 🥾
This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville 🌸 The memo will be updated as more tags get defined. This edition introduces Tag 13 for Boot File Size. Comments and suggestions for improvements are sought, so bring your takes 🗣️
RFC 1083 · IAB Official Protocol Standards 📋
This memo describes the state of standardization of the protocols used in the Internet, as determined by the Internet Activities Board (IAB) 🗂️ It starts with an overview of the standards procedures, then covers the standardization process and the RFC document series, then explains the terms, then lists the protocols in each stage of standardization, and finally points you to references and contacts for more info. It's issued quarterly, so please be sure the copy you're reading is dated within the last three months 📅
RFC 1082 · Post Office Protocol - Version 3 Extended Service Offerings 📫
This memo suggests a simple method for workstations to dynamically access mail from a discussion group server. It's an extension to an earlier memo that dealt with dynamically accessing mail from a mailbox server using the Post Office Protocol - Version 3 (POP3) 💌 This RFC specifies a proposed protocol for the Internet community, and it requests discussion and suggestions for improvements. All of the extensions described in this memo to the POP3 are OPTIONAL 🫶
RFC 1081 · Post Office Protocol - Version 3 📮
This memo suggests a simple method for workstations to dynamically access mail from a mailbox server 💖 This RFC specifies a proposed protocol for the Internet community, and it requests discussion and suggestions for improvements.
RFC 1080 · Telnet Remote Flow Control Option 🚦
This RFC specifies a standard for the Internet community 🌈 Hosts on the Internet that do remote flow control within the Telnet protocol are expected to adopt and implement this standard.
RFC 1079 · Telnet Terminal Speed Option 🐢
This RFC specifies a standard for the Internet community 💜 Hosts on the Internet that exchange terminal speed information within the Telnet protocol are expected to adopt and implement this standard.
RFC 1078 · TCP Port Service Multiplexer (TCPMUX) 🔀
This RFC proposes an Internet standard that future TCP services can use instead of 'well-known ports' 🧚 Main character energy for port numbers.
RFC 1077 · Critical Issues in High Bandwidth Networking 🚀
This memo presents the results of a working group on High Bandwidth Networking 📊 This RFC is for your information, and you're encouraged to comment on the issues presented 🗣️
RFC 1076 · HEMS Monitoring and Control Language 🧰
This RFC specifies a query language for monitoring and controlling network entities. It supersedes RFC 1023, extending the query language and giving more discussion of the underlying issues 🔍 This language is a component of the High-Level Entity Monitoring System (HEMS), which is described in RFC 1021 and RFC 1022, so you might want to consult those when reading this one. RFC 1024 contains detailed assignments of numbers and structures used in this system. Portions of RFC 1024 that define query language structures are superseded by the definitions in this memo. This memo assumes you already know the ISO data encoding standard, ASN.1 🤓
RFC 1075 · Distance Vector Multicast Routing Protocol 📡
This RFC describes a distance-vector-style routing protocol for routing multicast datagrams through an internet 🛰️ It's derived from the Routing Information Protocol (RIP), and it implements multicasting as described in RFC-1054. This is an experimental protocol, and its implementation is not recommended at this time 🧪
RFC 1074 · The NSFNET Backbone SPF based Interior Gateway Protocol 🦴
This RFC is an implementation description of the standard ANSI IS-IS and ISO ES-IS routing protocols within the NSFNET backbone network 💅
RFC 1073 · Telnet Window Size Option 🪟
This RFC describes a proposed Telnet option that lets a client convey its window size to a Telnet server 🌸
RFC 1072 · TCP Extensions for Long-Delay Paths 🌙
This RFC proposes a set of extensions to the TCP protocol so it can operate efficiently over a path with a high bandwidth*delay product ✨ These extensions are not proposed as an Internet standard at this time. Instead, they're meant as a basis for further experimentation and research on transport protocol performance 🔬
RFC 1071 · Computing the Internet Checksum 🧮
This RFC summarizes techniques and algorithms for efficiently computing the Internet checksum 💖 It is not a standard, but a set of useful...
(to be continued in part 2 🧚✨)
...okay so the vibe is implementation techniques 💅 that's the whole intro, bestie 🫶
1070 Hagens Feb 89 Use of the Internet as a Subnetwork
for Experimentation with the OSI
Network LayerOkay this one is so experimental 🧪 It proposes a scenario for playing with the ISO OSI network layer protocols over the Internet, and it's literally asking everyone for discussion and suggestions to make the scenario better 💭 It also proposes creating an experimental OSI internet. To join that internet, a system has to abide by the agreements in this RFC 🎀
1069 Callon Feb 89 Guidelines for the use of Internet-IP
addresses in the ISO Connectionless-
Mode Network ProtocolThis one is giving addressing glow-up ✨ It suggests an addressing scheme for the ISO Connectionless Network Protocol (CLNP) in the Internet, which is a fix for one of the problems with using "ISO-grams" on the Internet 🌸 This memo is a revision of RFC 986. It suggests a proposed protocol for the Internet community, and it wants discussion and suggestions for improvements 💖
1068 DeSchon Aug 88 Background File Transfer Program
(BFTP)BFTP is so chill 🦋 It describes an Internet background file transfer service built on the third-party transfer model of FTP. No new protocols are involved, which is honestly iconic. The whole point is to get people talking about new Internet service modes 🍓
1067 Case Aug 88 A Simple Network Management ProtocolOkay SNMP is main character energy 👑 It defines a simple protocol that lets logically remote users inspect or alter the management information for a network element. Together with its companion memos about how management information is structured and the initial management information base, these give a simple, workable architecture and system for managing TCP/IP-based internets, and the Internet in particular 🎀
This memo specifies a draft standard for the Internet community. TCP/IP implementations in the Internet which are network manageable are expected to adopt and implement this specification 💅
1066 McCloghrie Aug 88 Management Information Base for Network
Management of TCP/IP-based internetsThis is the MIB era 🧚 It gives the initial version of the Management Information Base for use with network management protocols in TCP/IP-based internets, for the short term. With its companion memos about structure and the initial protocol, these make up a simple, workable architecture and system for managing TCP/IP-based internets, and the Internet in particular ✨
This memo specifies a draft standard for the Internet community. TCP/IP implementations in the Internet which are network manageable are expected to adopt and implement this specification 🫶
1065 Rose Aug 88 Structure and Identification of
Management Information for
TCP/IP-based internetsRose is serving structure 🌹 This one gives the common definitions for how management information is structured and identified in TCP/IP-based internets. Together with its companions, which cover the initial MIB and the initial network management protocol, it's a simple, working architecture and system for managing TCP/IP-based internets, and the Internet in particular 💜
This memo specifies a draft standard for the Internet community. TCP/IP implementation in the Internet which are network manageable are expected to adopt and implement this specification 🌈
1064 Crispin Jul 88 Interactive Mail Access Protocol -
Version 2Okay IMAP v2 is so cute 📬 It suggests a way for workstations to dynamically access mail from a mailbox server ("respository"). This RFC specifies a standard for the SUMEX-AIM community and a proposed experimental protocol for the Internet community. Discussion and suggestions for improvement are requested 🦋
1063 Mogul Jul 88 IP MTU Discovery OptionsMogul really brought the receipts 🧾 This describes a pair of IP options that can be used to learn the minimum MTU of a path through an internet, along with their possible uses. It's a proposal for an Experimental protocol 🔥
1062 Romano Aug 88 Internet NumbersThis one is the official status report on the network numbers and gateway autonomous system numbers used in the Internet community 📋 Very organized, very slay 💅
1061 Never issued.Okay this one is a ghost 👻 It was never issued, so there's no RFC here 💀
1060 Reynolds Mar 90 Assigned NumbersThis is a status report on the parameters (numbers and keywords) used in protocols in the Internet community. Distribution of this memo is unlimited 🎀
1059 Mills Jul 88 Network Time Protocol (Version 1)
Specification and ImplementationNTP is literally the clock queen ⏰ This memo describes the Network Time Protocol, specifies its formal structure, and summarizes information useful for implementing it. NTP syncs time and coordinates time distribution in a large, diverse internet operating at rates "from mundane to lightwave" 🌟 It uses a "returnable-time" design, where a distributed subnet of time servers works in a self-organizing, hierarchical master-slave configuration. Those servers sync logical clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute reference time via local routing algorithms and time daemons 💖
The architectures, algorithms and protocols that grew out of several years of implementation and refinement are all in here 🧚 The prototype has been in regular operation on the Internet for the last two years, and it's described in an Appendix along with performance data. That data shows timekeeping accuracy throughout most of the Internet can ordinarily stay within a few tens of milliseconds, even when clocks, time servers or nets fail or get disrupted 🫶 This is a Draft Standard for an Elective protocol 💜
1058 Hedrick Jun 88 Routing Information ProtocolRIP is giving classic 🛣️ This RFC describes an existing protocol for exchanging routing information among gateways and other hosts. It's meant to be a basis for developing gateway software for the Internet community 🌸
1057 Sun Jun 88 RPC: Remote Procedure Call Protocol
Specification Version 2This RFC describes a standard that Sun Microsystems and others are using, and it's one they want to propose for the Internet's consideration 🎀 This memo is not an Internet standard at this time 🙈
1056 Lambert Jun 88 PCMAIL: A Distributed Mail System
for Personal ComputersThis memo discusses the Pcmail workstation-based distributed mail system 📨 It's identical to the discussion in RFC-993, except a new, much simpler mail transport protocol is described. That new transport protocol came out of continued research into ease of protocol implementation and use issues 💅
1055 Romkey Jun 88 A Nonstandard for Transmission of
IP Datagrams over Serial Lines: SLIPOkay SLIP is so relatable 🔌 The TCP/IP protocol family runs over a bunch of network media: IEEE 802.3 (ethernet) and 802.5 (token ring) LANs, X.25 lines, satellite links, and serial lines. There are standard encapsulations for IP packets defined for many of those networks, but there's no standard for serial lines. SLIP, Serial Line IP, is currently a de facto standard, commonly used for point-to-point serial connections running TCP/IP 💜 It is not an Internet standard 🫶
1054 Deering May 88 Host Extensions for IP MulticastingThis memo specifies the extensions a host implementation of the Internet Protocol (IP) needs to support multicasting 📡 IP multicasting is the transmission of an IP datagram to a "host group", which is a set of hosts identified by a single IP destination address. A multicast datagram gets delivered to all members of its destination host group with the same "best-efforts" reliability as regular unicast IP datagrams 🌈 It's proposed as a standard for IP multicasting in the Internet. This specification is a major revision of RFC-988 🔥
1053 Levy Apr 88 Telnet X.3 PAD OptionThis RFC proposes a new option to Telnet for the Internet community, and it requests discussion and suggestions for improvements 🦋
1052 Cerf Apr 88 IAB Recommendations for the
Development of Internet Network
Management StandardsThis RFC is meant to share the Internet Activities Board (IAB) recommendations for developing network management protocols for use in the TCP/IP environment 🧠 This memo does NOT, in and of itself, define or propose an Official Internet Protocol. It does reflect the IAB's policy on further network management development in the short and long term 💅
1051 Prindeville Mar 88 A Standard for the Transmission of IP
Datagrams and ARP Packets over ARCNET
NetworksThis memo specifies a standard method for encapsulating Internet Protocol (IP) and Address Resolution Protocol (ARP) datagrams on an ARCNET 🧩 This RFC is a standard protocol for the Internet community ✨
1050 Sun Apr 88 RPC: Remote Procedure Call
Protocol SpecificationThis memo specifies a message protocol used in implementing Sun's Remote Procedure Call (RPC) package 🎀 It describes a standard that Sun Microsystems and others are using and want to propose for the Internet's consideration. It is not an Internet standard at this time 🙈
1049 Sirbu Mar 88 A Content-Type Header Field for
Internet MessagesThis memo suggests proposed additions to the Internet Mail Protocol, RFC-822, for the Internet community, and it requests discussion and suggestions for improvements 💌
1048 Prindeville Feb 88 BOOTP Vendor Information ExtensionsThis memo proposes an addition to the Bootstrap Protocol (BOOTP). Comments and suggestions for improvements are sought 🍓
1047 Partridge Feb 88 Duplicate Messages and SMTPThis RFC examines a synchronization problem in the Simple Mail Transfer Protocol (SMTP) that can cause a message to be delivered multiple times 📬 A method for avoiding this problem is suggested. Nodding familiarity with the SMTP specification, RFC-821, is required 🤓
1046 Prue Feb 88 A Queuing Algorithm to Provide
Type-of-Service for IP LinksThis memo explores how Type-of-Service might be implemented in the Internet 🚦 The proposal describes a queuing method that can provide different classes of service. The technique also stops one class of service from consuming excessive resources or excluding other classes of service. It's an "idea paper" and discussion is strongly encouraged 💬
1045 Cheriton Feb 88 VMTP: Versatile Message Transaction
Protocol Protocol SpecificationOkay VMTP is so versatile 🌸 This memo specifies the Versatile Message Transaction Protocol (VMTP) [Version 0.7 of 19-Feb-88], a transport protocol designed specifically to support the transaction model of communication, as exemplified by remote procedure call (RPC). The full function of VMTP, including
support for security, real-time, asynchronous message exchanges, streaming, multicast and idempotency, and that gives the VMTP user level a rich selection to choose from 💅✨ Subsettability is the real icon here. A VMTP module for a particular client or server can be specialised and simplified down to only the services it actually needs 🧚 Simple examples include PROM network bootload programs, network boot servers, data sensors and simple controllers, to name just a few 🍓 This RFC describes a protocol proposed as a standard for the Internet community 🫶
1044 Hardwick Feb 88 Internet Protocol on Network Systems
HYPERchannel Protocol SpecificationOkay bestie, this memo gives a complete rundown of how DoD standard Internet Protocol datagrams (plus their higher level protocols) get embedded on Network Systems Corporation's HYPERchannel equipment 🔥 It's written for network planners and implementors who already know the TCP/IP protocol suite and how TCP/IP traffic moves over common networks like the DDN or the Ethernet 💜 You don't need to be an NSC product expert, because there's an appendix that reviews NSC technologies and protocols 🌸
1043 Yasuda Feb 88 TELNET Data Entry Terminal Option
DODIIS ImplementationThis RFC suggests a proposed protocol for the TELNET Data Entry Terminal (DET) Option - DODIIS Implementation, for the Internet community ✨ It's meant to be compatible with the DET Option specified in RFC-732 🎀 Discussion and suggestions for improvements are encouraged, so spill your thoughts 🦋
1042 Postel Feb 88 A Standard for the Transmission of
IP Datagrams over IEEE 802 NetworksThis RFC specifies a standard way to encapsulate Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on IEEE 802 Networks 🧚 The whole point is that implementations stay compatible and interoperable 🫶 It's a protocol standard for the Internet community 💅
1041 Rekhter Jan 88 Telnet 3270 Regime OptionThis RFC specifies a proposed standard for the Internet community 🌈 Hosts that want to support the 3270 data stream within the Telnet protocol are expected to adopt and implement this standard. No cap, it's the expected move 😭
1040 Linn Jan 88 Privacy Enhancement for Internet
Electronic Mail: Part I Message
Encipherment and Authentication
ProceduresThis RFC is the outgrowth of a series of IAB Privacy Task Force meetings and the internal working papers handed out for them 🔐 This memo defines message encipherment and authentication procedures, which is the first phase of building privacy enhancement services for electronic mail transfer on the Internet ✨ The detailed key management mechanisms that support these procedures will come in a subsequent RFC 💖 A big goal of this first phase is that these procedures 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 integrity check computation is anticipated 🙈
1039 Latham Jan 88 A DoD Statement on Open Systems
Interconnection ProtocolsThis RFC reproduces a memorandum issued on 2-JUL-87 by the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (ASDC31) to the Director of the Defense Communications Agency (DCA) 📜 It's distributed for information only 🌸
1038 St. Johns Jan 88 Draft Revised IP Security OptionThis memo is a pre-publication draft of the revised Internet Protocol Security Option 🔒 This RFC reflects the version approved by the Protocol Standards Steering group, and it's provided for informational purposes only 💅 The final version will be available from Navy publications and should not differ from this document in any major fashion 👀 It will be published as a change to the MIL-STD 1777, "Internet Protocol" 🎀
1037 Greenberg Dec 87 NFILE - A File Access ProtocolThis document specifies the NFILE file access protocol and its underlying levels of protocol, the Token List Transport Layer and Byte Stream with Mark 🗂️ The goal is to get people talking about these ideas and to encourage designers of future file protocols to take advantage of them 💡 A secondary goal is to make the specification available to sites that might benefit from implementing NFILE 🦋
1036 Horton Dec 87 Standard for Interchange of
USENET MessagesThis RFC defines the standard format for exchanging network News messages among USENET hosts 📰 It updates and replaces RFC-850, reflecting version B2.11 of the News program ✨ It's distributed as an RFC so the information is easy for the Internet community to access, and it does not specify an Internet standard 🫶
1035 Mockapetris Nov 87 Domain Names - Implementation
SpecificationThis RFC is the revised specification of the protocol and format used to implement the Domain Name System 🌐 It obsoletes RFC-883 💀 This memo documents the details of communication between domain name clients and servers 🧚
1034 Mockapetris Nov 87 Domain Names - Concepts and
FacilitiesThis RFC is the revised basic definition of The Domain Name System 🌈 It obsoletes RFC-882 💅 It describes domain style names and their use for host address lookup and electronic mail forwarding 📬 It also covers the clients and servers in the domain name system and the protocol used between them 👑
1033 Lottor Nov 87 Domain Administrators Operations
GuideThis RFC gives guidelines for domain administrators who are running a domain server and maintaining their portion of the hierarchical database 🗄️ Familiarity with the domain system is assumed, so go read RFCs 1031, 1032, 1034, and 1035 first, iykyk 🙈
1032 Stahl Nov 87 Domain Administrators GuideDomains are administrative entities that provide decentralised management of host naming and addressing 🏰 The domain-naming system is distributed and hierarchical, which is so iconic 😭
This memo describes how to register a domain with the Network Information Center (NIC) of the Defense Data Network (DDN), and it offers guidelines for setting up and running a domain in line with the requirements in RFC-920 📋 The guidelines are recommended for domain administrators who are establishing and controlling second-level domains 💖 The domain administrator (DA) is basically the coordinator, manager, and technician all in one 👩💻 If his domain sits at the second level or lower in the tree, the domain administrator must register by working with the management of the domain directly above it ✨
1031 Lazear Nov 87 Milnet Name Domain TransitionThis RFC pulls together the information needed to implement domain style names across the DDN/MILNET Internet community 🧩 The introduction of domain style names will affect all hosts in the DDN/MILNET Internet 🌍 It's an aid for implementors and administrators, offering: 1) an overview of the transition from host tables to domains, 2) a timetable for the transition, and 3) references to documentation and software related to the domain system 📚
1030 Lambert Nov 87 On Testing the NETBLT Protocol over
Divers NetworksThis memo shares results from testing NETBLT over three networks with different bandwidths and round-trip delays 📊 The results aren't complete, and the info gathered so far hasn't been very promising 😬 NETBLT is specified in RFC-998, and this document assumes you understand the specification described there 🤓
1029 Parr May 88 A More Tolerant Approach to Address
Resolution for Multi-Lan system of
EthernetsThis memo discusses an extension to a Bridge Protocol that detects and reports changes in neighbouring host address parameters in a Multi-Lan system of Ethernets 🌉 The problem keeps showing up more and more as interconnected systems grow larger on Campuses and in Commercial Institutions 🏫 This RFC suggests a protocol enhancement for the Internet community, and it requests discussion and suggestions for improvements 🫶
1028 Davin Nov 87 A Simple Gateway Monitoring ProtocolThis memo defines a simple application-layer protocol that lets remote users inspect or alter management information for a gateway 🕹️ It's only meant as an interim response to immediate gateway monitoring needs ⏳
1027 Carl-Mitchell Oct 87 Using ARP to Implement Transparent
Subnet GatewaysThis RFC describes how subnet gateways use the Address Resolution Protocol (ARP) to let hosts on connected subnets communicate without being aware that subnets exist 🪄 It's done with the technique called "Proxy ARP" ✨
1026 Kille Sep 87 Addendum to RFC-987 (Mapping between
X.400 and RFC-882)This memo suggests a proposed protocol for the Internet community, and it requests discussion and suggestions for improvements 💌
1025 Postel Sep 87 TCP and IP Bake OffThis memo describes some of the procedures, scoring, and tests used in the TCP and IP bake offs held during the early development of these protocols 🏆 These procedures and tests may still be useful for testing newly implemented TCP and IP modules 🧪
1024 Partridge Oct 87 HEMS Variable DefinitionsThis memo assigns instruction codes and defines object formats and object semantics for use with the High-Level Monitoring and Control Language, which is defined in RFC-1023 📝 A general system was described in earlier memos (RFC-1021, RFC-1022), and it's called the High-Level Entity Management System (HEMS) 🧠 This memo is provisional, so the definitions are subject to change ⚠️ Readers should confirm with the authors that they have the most recent version 👀 This RFC assumes a working knowledge of the ISO data encoding standard, ASN.1, and a general understanding of the IP protocol suite 💜
1023 Partridge Oct 87 HEMS Monitoring and Control LanguageThis RFC specifies the High-Level Entity Management System (HEMS) Monitoring and Control Language 🎛️ The language defines the requests and replies used in HEMS 📨 This memo assumes you know the HEMS system described in RFC-1021, plus the ISO data encoding standard, ASN.1 🤓
1022 Partridge Oct 87 The High-Level Entity Management
Protocol (HEMP)This memo presents an application protocol for managing network entities such as hosts, gateways, and front end machines 🖥️ This protocol is a component of the High-Level Entity Management System (HEMS), which is described in RFC-1021 🧩 This memo also assumes you know the ISO data encoding standard, ASN.1 🎀
1021 Partridge Oct 87 The High-Level Entity Management
System (HEMS)This memo gives a general overview of the High-Level Entity Management System (HEMS) 🌟 This system is experimental, and it is currently
being tested in portions of the Internet. ✨
1020 · Internet Numbers 🔢
Author: Romano · Date: Nov 87
okay bestie, this one is the list of Assigned IP Network Numbers and EGP Autonomous System Numbers 🌸. It obsoletes RFC-997, so RFC-997 is officially old news 💅.
1019 · Report of the Workshop on Environments for Computational Mathematics 📐
Author: Arnon · Date: Sep 87
this one is a report on the discussion about how equations get represented, from a workshop at the ACM SIGGRAPH Conference in Anaheim, California on 30 July 1987 🎀.
1018 · Some Comments on SQuID 🤔
Author: McKenzie · Date: Aug 87
this memo chats about some ideas from RFC-1016 on Source Quench 💭. It splits the cause of gateway congestion into two vibes: "Funneling" and "Mismatch" 🦋. It's written in the same spirit as RFC-1016, meant to get everyone talking. The opinions are personal, not corporate, so no official stamp here 🫶.
1017 · Network Requirements for Scientific Research 🔬
Author: Leiner · Date: Aug 87
this RFC figures out what communication networks need in order to support scientific research 🧪. It suggests some specific areas for near-term work, plus some long-term goals 🌈. It's an "idea" paper, so discussion is strongly encouraged 💜.
1016 · Something a Host Could Do with Source Quench: The Source Quench Introduced Delay (SQuID) 🧚
Author: Prue · Date: July 87
this memo explores what a host could actually do with a source quench 👀. The proposal is that each source host IP module adds some delay between datagrams sent to the same destination host ⏳. It's a "crazy idea paper", so discussion is essential 🔥.
1015 · Implementation Plan for Interagency Research Internet 🌐
Author: Leiner · Date: July 87
this RFC proposes an Interagency Research Internet as the natural next chapter of the current Internet ✨. It's an "idea paper", and discussion is strongly encouraged 🫶.
1014 · XDR: External Data Representation Standard 🧩
Author: Sun · Date: Jun 87
XDR is a standard for describing and encoding data 💖. It's super useful for moving data between different computer architectures 🖥️. XDR fits into the ISO presentation layer and is roughly analogous in purpose to X.409, ISO Abstract Syntax Notation. The big difference is that XDR uses implicit typing, while X.409 uses explicit typing 🤓. This RFC is distributed for information only, so it does not establish an Internet standard 💅.
1013 · X Window System Protocol, Version 11-Beta 🪟
Author: Scheifler · Date: Jun 87
this RFC is shared with the Internet community for information only 📚. It does not establish an Internet standard. The X window system has been widely reviewed and tested 🙌, and the community is encouraged to experiment with it 🧪.
1012 · Bibliography of Requests for Comments 1-999 📖
Author: Reynolds · Date: Jun 87
this is a reference guide for the Internet community 🗂️. It gives a bibliographic summary of the Request for Comments numbers 1 through 999, issued between 1969 and 1987 🕰️.
1011 · Official Internet Protocols 🏛️
Author: Reynolds · Date: May 87
this memo is an official status report on the protocols used in the Internet community 📋. It identifies the documents that specify the official protocols used in the Internet, and the comments point out any revisions or changes planned 🔄.
1010 · Assigned Numbers 🔢
Author: Reynolds · Date: May 87
this memo is an official status report on the numbers used in protocols across the Internet community 🎯. It documents the currently assigned values from several series of numbers, including link, socket, port, and protocol, which are used in network protocol implementations ⚙️.
1009 · Requirements for Internet Gateways 🚪
Author: Braden · Date: Jun 87
this RFC sums up the requirements for gateways used between networks that support the Internet protocols 🌉. It's a formal statement of the requirements that gateways in the Internet system have to meet, so it's an official specification for the Internet community 👑.
1008 · Implementation Guide for the ISO Transport Protocol 📮
Author: McCoy · Date: Jun 87
this RFC went out to the Internet community to collect comments on the Implementors Guide 💬. It may not be directly relevant to the Internet's research problems, but it could be interesting to a bunch of researchers and implementors 🙈.
1007 · Military Supplement to the ISO Transport Protocol 🎖️
Author: McCoy · Date: Jun 87
this document supplements the Transport Service and Protocol of the International Standards Organization (ISO), which are IS 8072 and IS 8073 respectively, along with their formal descriptions 🧾. It does this by providing conventions, option selections, and parameter values ✨. This RFC went out to the Internet community to collect comments on the Draft Military Supplement. It may not be directly relevant to the Internet's research problems, but it could still interest some researchers and implementors 💅.
1006 · ISO Transport Services on top of the TCP Version: 3 🚀
Author: Rose · Date: May 87
this memo specifies a standard for the Internet community 👑. Hosts on the Internet that choose to implement ISO transport services on top of TCP are expected to adopt and implement this standard. TCP port 102 is reserved for hosts that implement this standard 🌈. This memo specifies version 3 of the protocol and supersedes RFC-983. The changes between the protocol described in RFC-983 and this memo are minor, but unfortunately incompatible 😭.
1005 · The ARPANET AHIP-E Host Access Protocol (Enhanced AHIP) 📡
Author: Khanna · Date: May 87
this RFC is a proposed specification for encoding Class A IP addresses on ARPANET-style networks such as the Milnet and Arpanet 🛰️. It also brings enhancements to the ARPANET AHIP Host Access Protocol (AHIP, formerly known as 1822) 🔧. The glow-up includes:
- a bigger PSN field 📈
- logical names, so ARPANET hosts can address each other by name 🏷️
- type-of-service information passed from the host to the PSN 🎀
- congestion feedback from the PSN to the host on a connection basis 💨
1004 · A Distributed-Protocol Authentication Scheme 🔐
Author: Mills · Date: Apr 87
the goal of this RFC is to get everyone discussing authentication problems on the Internet and possible ways to solve them 🗣️. The proposed solutions in this document are not intended as Internet standards at this time 🙅♀️. Instead, the hope is that a general consensus will emerge on the right fix, which could eventually lead to standards 💜. This document suggests mediated access-control and authentication procedures for cases when an association is set up between users in different trust environments 🤝.
1003 · Issues in Defining an Equations Representation Standard 🧮
Author: Katz · Date: Mar 87
this memo is here to identify and explore the issues in defining a standard for exchanging mathematical equations 📐. No complete definition is attempted, and more questions get asked than answered 🙈. Questions about the user interface are only covered to the extent that they affect interchange issues 💅.
1002 · Protocol Standard for A NetBIOS Service on a TCP/UDP Transport: Detailed Specifications 🪪
Author: NETBIOS · Date: Mar 87
this RFC defines a proposed standard protocol that supports NetBIOS services in a TCP/IP environment 🖧. Both local network and internet operation are supported. Various node types are defined to fit local and internet topologies, and to allow operation with or without IP broadcast 📡. This RFC gives the detailed specifications of the netBIOS-over-TCP packets, protocols, and defined constants and variables 🔍. For a more general overview, check out the companion RFC, "Protocol Standard For NetBIOS Service on TCP/UDP Transport: Concepts and Methods" 💖.
1001 · Protocol Standard for A NetBIOS Service on a TCP/UDP Transport: Concepts and Methods 🧠
Author: NETBIOS · Date: Mar 87
this RFC is the same kind of proposed standard for NetBIOS services in a TCP/IP environment 🌐. Both local network and internet operation are supported, and various node types are defined to accommodate local and internet topologies, with or without the use of IP broadcast 📢. This one describes the NetBIOS-over-TCP protocols in a general way, focusing on the underlying ideas and techniques 💡. The detailed specifications live in the companion RFC, "Protocol Standard For a NetBIOS Service on a TCP/UDP Transport: Detailed Specifications" 🎀.
1000 · The Request for Comments Reference Guide 🗺️
Author: Reynolds · Date: Aug 87
this Reference Guide gives a historical account by categorizing and summarizing the Request for Comments numbers 1 through 999, issued between 1969 and 1987 🕰️. These documents have been cross-referenced to show which RFCs are current, obsolete, or revised 🔁. Main character energy for the whole archive 👑.
Security Considerations 🔒
Security issues are not discussed in this memo 🙈.
Author's Address 🏡
Joyce K. Reynolds
University of Southern California
Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292
Phone: (310) 822-1511
EMail: JKREY@ISI.EDU📦 where this page comes from
- ietf: rfc1099 1991-12
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms