RFC 1199
Request for Comments Summary Notes: 1100-1199
Request for Comments Summary: RFC Numbers 1100-1199 ✨
okay bestie, let's get into the header first 🎀 this is Network Working Group, RFC 1199, written by J. Reynolds at ISI and dated December 1991. It's an informational RFC (it provides information for the Internet community and is not a standard), and its header doesn't list anything it obsoletes or updates 💖
Status of This Memo 💅
okay so this RFC is a lightly annotated list of the 100 RFCs from RFC 1100 through RFC 1199 🦋 it's a status report on those RFCs. This memo provides information for the Internet community, it does not specify an Internet standard, and distribution of this memo is unlimited ✨
Note 🎀
so ngl, lots of RFCs are Proposed Standards, Draft Standards, or Standards, but not all of them 💅 the status can change during standards processing, so this doc just notes that they're on the standards track. For the current state, check the latest edition of "IAB Official Protocol Standards" 🌸 in the list below, standards-track RFCs are marked [STANDARDS-TRACK] 🫶
The List 🦋
Here's the table header with the 1199 row, exactly as it's written:
RFC Author Date Title
--- ------ ---- -----
1199 Reynolds Dec 91 Requests For Comments Summary1198 · FYI on the X Window System 🖥️
Author: Scheifler · Date: Jan 91
this FYI RFC points you to the published standards of the MIT X Consortium 💜 it provides information for the Internet community and doesn't specify any Internet standard.
1197 · Using ODA for Translating Multimedia Information 🎞️
Author: Sherman · Date: Dec 90
the whole point here is to tell multimedia implementors about experiences using ISO 8613: Office Document Architecture (ODA) 🧚 ODA is being proposed as an encoding format for multimedia mail and file exchange, so implementors who want to use it in an open systems environment might get a lot out of these experiences. It provides information for the Internet community and doesn't specify any standard.
1196 · The Finger User Information Protocol 👀
Author: Zimmerman · Date: Dec 90
Finger is a simple protocol that gives you an interface to a remote user information program 💖 this memo is based on RFC 742 (the original Finger protocol description) and tries to clarify how the two ends of a Finger connection are expected to talk. It also tries not to invalidate the many existing implementations or add unnecessary restrictions to the original protocol definition 🫶 this edition corrects and clarifies, in a minor way, RFC 1194. [STANDARDS-TRACK]
1195 · Use of OSI IS-IS for Routing in TCP/IP and Dual Environments 🌈
Author: Callon · Date: Dec 90
this memo specifies an integrated routing protocol, based on the OSI Intra-Domain IS-IS Routing Protocol 👑 it can be used as an interior gateway protocol (IGP) to support TCP/IP as well as OSI. So one routing protocol can cover pure IP environments, pure OSI environments, and dual environments, which is honestly iconic 😭 it was developed by the IS-IS working group of the Internet Engineering Task Force. [STANDARDS-TRACK]
1194 · The Finger User Information Protocol 👀
Author: Zimmerman · Date: Nov 90
same protocol, same vibes 💅 it's a simple protocol that gives an interface to a remote user information program, and it's based on RFC 742. It tries to clarify expected communication between the two ends of a Finger connection, and it still doesn't invalidate existing implementations or add unnecessary restrictions. [STANDARDS-TRACK]
1193 · Client Requirements for Real-Time Communication Services 🎧
Author: Ferrari · Date: Nov 90
this memo describes client requirements for real-time communication services ✨ it provides information for the Internet community and requests discussion and suggestions for improvements. It does not specify any standard.
1192 · Commercialization of the Internet Summary Repor 💸
Author: Kahin · Date: Nov 90
this memo is based on a workshop held by the Science, Technology and Public Policy Program of the John F. Kennedy School of Government at Harvard University, March 1-3, 1990 🎓 it provides information for the Internet community and doesn't specify any standard.
1191 · Path MTU Discovery 🛤️
Author: Mogul · Date: Nov 90
this memo describes a technique for dynamically discovering the maximum transmission unit (MTU) of an arbitrary internet path 🔥 it specifies a small change to the way routers generate one type of ICMP message. For a path that goes through a router that hasn't been changed this way, the technique might not find the correct Path MTU, but it will always pick one as accurate as, and in many cases more accurate than, the one current practice would pick 🫶 [STANDARDS-TRACK]
1190 · Experimental Internet Stream Protocol, Version 2 (ST-II) 🌊
Author: Topolcic · Date: Oct 90
this memo defines a revised version of the Internet Stream Protocol, originally defined in IEN-119 [8] 🧜 it's based on results from experiments with the original version, plus later requests, discussion, and suggestions for improvements. This is a Limited-Use Experimental Protocol, so check the current "IAB Official Protocol Standards" for its standardization state and status 🍓
1189 · The Common Management Information Services and Protocols for the Internet 🗂️
Author: Warrier · Date: Oct 90
this memo defines a network management architecture that uses the International Organization for Standardization's (ISO) Common Management Information Services/Common Management Information Protocol (CMIS/CMIP) in the Internet 💅 [STANDARDS-TRACK]
1188 · A Proposed Standard for the Transmission of IP Datagrams over FDDI Networks 🌟
Author: Katz · Date: Oct 90
this memo defines a way to encapsulate Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on Fiber Distributed Data Interface (FDDI) Networks 🦋 [STANDARDS-TRACK]
1187 · Bulk Table Retrieval with the SNMP 📊
Author: Rose · Date: Oct 90
this memo reports an interesting family of algorithms for bulk table retrieval using the Simple Network Management Protocol (SNMP) 🧠 it describes an Experimental Protocol for the Internet community and requests discussion and suggestions for improvements. It does not specify a standard for the Internet community, so check the current "IAB Official Protocol Standards" for this protocol's status 💜
1186 · The MD4 Message Digest Algorithm 🔐
Author: Rivest · Date: Oct 90
this RFC is the specification of the MD4 Digest Algorithm 🫶 if you're going to implement MD4, the author suggests doing it this way. It's for informational use and does not constitute a standard.
1185 · TCP Extension for High-Speed Paths 🚀
Author: Jacobson · Date: Oct 90
this memo describes an Experimental Protocol extension to TCP for the Internet community, and it requests discussion and suggestions for improvements 💖 check the current "IAB Official Protocol Standards" for the standardization state and status of this protocol.
1184 · Telnet Linemode Option ⌨️
Author: Borman · Date: Oct 90
this RFC specifies a procedure for line-at-a-time terminal interaction based on the Telnet Protocol 🌸 it obsoletes RFC 1116. [STANDARDS-TRACK]
1183 · New DNS RR Definitions 🧭
Author: Everhart · Date: Oct 90
this memo defines five new DNS types for experimental purposes ✨ this RFC describes an Experimental Protocol for the Internet community and requests discussion and suggestions for improvements.
1182 · Never issued. 🫠
Author: (none listed)
this number was never issued, so there's nothing here, bestie 💀
1181 · RIPE Terms of Reference 🇪🇺
Author: Blokzijl · Date: Sep 90
this RFC describes the Terms of Reference of RIPE (Reseaux IP Europeens), which is the cooperation of European IP networks 🌍 it provides information for the Internet community and doesn't specify any standard.
1180 · A TCP/IP Tutorial 📚
Author: Socolofsky · Date: Jan 91
this RFC is a tutorial on the TCP-IP protocol suite, focusing especially on the steps in forwarding an IP datagram from source host to destination host through a router 🧚 it does not specify an Internet standard.
1179 · Line Printer Daemon Protocol 🖨️
Author: McLaughlin · Date: Aug 90
this RFC describes an existing print server protocol that's widely used on the Internet for communication between line printer daemons (both clients and servers) 💅 it's for informational purposes only and does not specify an Internet standard. Check the current edition of the "IAB Official Protocol Standards" for this protocol's status.
1178 · Choosing a Name for Your Computer 💻
Author: Libes · Date: Aug 90
this FYI RFC republishes a Communications of the ACM article with guidelines on what to do and what not to do when naming your computer 🙈 it provides information for the Internet community and does not specify any standard. [Also FYI 5.]
1177 · FYI on Questions and Answers: Answers to Commonly asked "New Internet User" Questions 🙋♀️
Author: Malkin · Date: Aug 90
this FYI RFC is one of three FYI's called "Questions and Answers" (Q/A), produced by the User Services Working Group (USWG) of the Internet Engineering Task Force (IETF) 🎀 the goal is to document the most commonly asked questions and answers on the Internet. It provides information for the Internet community and does not specify any standard. [Also FYI 4.]
1176 · Interactive Mail Access Protocol - Version 2 📬
Author: Crispin · Date: Aug 90
this RFC suggests a method for personal computers and workstations to dynamically access mail from a mailbox server ("repository") 💌 it obsoletes RFC 1064. It specifies an Experimental Protocol for the Internet community, and discussion and suggestions for improvement are requested. Check the current "IAB Official Protocol Standards" for the standardization state and status of this protocol 🦋
1175 · FYI on Where to Start - A Bibliography of Internetworking Information 📖
Author: Bowers · Date: Aug 90
this FYI RFC is a bibliography of information about TCP/IP internetworking, prepared by the User Services Working Group (USWG) of the Internet Engineering Task Force (IETF) 🧠 it provides information for the Internet community and does not specify any standard. [Also FYI 3.]
1174 · IAB Recommended Policy on Distributing Internet Identifier Assignment and IAB Recommended Policy Change to Internet "Connected" Status 🏛️
Author: Cerf · Date: Aug 90
this informational RFC represents the official view of the Internet Activities Board (IAB) 👑 it describes the recommended policies and procedures on distributing Internet identifier assignments and dropping the connected status requirement. This RFC does not specify a standard.
1173 · Responsibilities of Host and Network Managers: A Summary of the "Oral Tradition" of the Internet 🫶
Author: Van Bokkelen · Date: Aug 90
this informational RFC describes the conventions to be followed by the people in charge of networks and hosts in the Internet 🌸 it's a summary of the "oral tradition" of the Internet on this subject. [RFC Editor's note: This memo is a contribution by the author of his view of these conventions. It is expected that this RFC will provide a basis for the development of official policies in the future.] These conventions may be supplemented or amended by the policies of specific local and
regional components of the Internet. Anyway, bestie, this RFC does not specify a standard, or a policy of the IAB 💅
1172 Perkins Jul 90 The Point-to-Point Protocol (PPP)
Initial Configuration OptionsOkay so this memo specifies the Point-to-Point Protocol (PPP) Initial Configuration Options as a Proposed Standard Protocol for the Internet community 🎀 Once it becomes a full Standard, this protocol will be recommended for all TCP/IP implementations that communicate over serial links. Iconic 🔥
1171 Perkins Jul 90 The Point-to-Point Protocol for the
Transmission of Multi-Protocol Datagrams
Over Point-to-Point LinksThis memo specifies the Point-to-Point Protocol (PPP) as a Draft Standard Protocol for the Internet community 🦋 When it becomes a full Standard, this protocol will be recommended for all TCP/IP implementations that communicate over serial links. Same energy as 1172, just one step earlier in the pipeline ✨
1170 Fougner Jan 91 Public Key Standards and LicensesThis RFC is a public statement by Public Key Partners about Public Key Standards and Licenses 💜 It's for informational use only and does not constitute an Internet standard, so no vibes of being official, just a heads up from them 💅
1169 Cerf Aug 90 Explaining the Role of GOSIPThis informational RFC represents the official view of the Internet Activities Board (IAB), after coordination with the Federal Networking Council (FNC) 👑 It does not specify a standard. Bestie, this is the IAB getting its story straight 🙈
1168 Westine Jul 90 Intermail and Commercial Mail
Relay ServicesThis RFC talks about the history and evolution of the Intermail and Commercial mail systems 📬 It also covers the problems people ran into operating a store-and-forward mail relay between commercial systems such as Telemail, MCI Mail and Dialcom. It provides information for the Internet community and does not specify any standard 🌸
1167 Cerf Jul 90 Thoughts on the National Research and
Education NetworkThe memo gives a brief outline of a National Research and Education Network (NREN) 🧚 It provides information for the Internet community. It does not specify any standard, and it is not a statement of IAB policy or recommendations. Just vibes and ideas, no rules 🌈
1166 Kirkpatrick Jul 90 Internet NumbersThis memo is a status report on the network numbers and autonomous system numbers used in the Internet community 🔢 Very organized, very important, very ate 💅
1165 Crowcrowft Jun 90 Network Time Protocol (NTP)
over the OSI Remote Operations ServiceThis memo suggests an Experimental Protocol for the OSI and Internet communities ⭐ Hosts in either community, and in particular those on both, are encouraged to experiment with this mechanism. Go play bestie 🧪
1164 Honig Jun 90 Application of the Border Gateway
Protocol in the InternetThis RFC, together with its companion RFC-1163, "A Border Gateway Protocol (BGP)", specifies an inter-autonomous system routing protocol for the Internet 🛣️ It's on the [STANDARDS-TRACK], so it's serious business 😭
1163 Lougheed Jun 90 A Border Gateway Protocol (BGP)This RFC, together with its companion RFC-1164, "Application of the Border Gateway Protocol in the Internet", specifies the same inter-autonomous system routing protocol for the Internet 🫶 It's also on the [STANDARDS-TRACK]. Matching outfits, iconic duo.
1162 Satz Jun 90 Connectionless Network Protocol
(ISO 8473) and End System to
Intermediate System (ISO 9542)
Management Information BaseThis memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets 🧩 This memo does not specify a standard for the Internet community.
1161 Rose Jun 90 SNMP over OSIThis memo defines an experimental means for running the Simple Network Management Protocol (SNMP) over OSI transports 🦋 This memo does not specify a standard for the Internet community.
1160 Cerf May 90 The Internet Activities BoardThis RFC gives a history and description of the Internet Activities Board (IAB) and its subsidiary organizations 📚 It's for informational use and does not constitute a standard. It's a revision of RFC 1120, so this is the glow-up version 💖
1159 Nelson Jun 90 Message Send ProtocolThis RFC suggests an Experimental Protocol for the Internet community ✨ Hosts on the Internet that choose to implement a Message Send Protocol may experiment with this protocol. Experiment era, no commitments, pure curiosity 🌸
1158 Rose May 90 Management Information Base for
Network Management of TCP/IP-based
internets: MIB-IIThis memo defines the second version of the Management Information Base (MIB-II) for use with network management protocols in TCP/IP-based internets 👑 Together with its companion memos, which describe the structure of management information (RFC 1155) and the network management protocol (RFC 1157) for TCP/IP-based internets, these documents give you a simple, workable architecture and system for managing TCP/IP-based internets, and in particular the Internet community. It is so clean 😭 The MIB-II version also incorporates all of the technical content of RFC 1156 on MIB-I and extends it, without loss of compatibility. [STANDARDS-TRACK] 🔥
1157 Case May 90 A Simple Network Management
Protocol (SNMP)This RFC is a re-release of RFC 1098, with a changed "Status of this Memo" section plus a few minor typographical corrections 💅 This memo defines a simple protocol by which management information for a network element may be inspected or altered by logically remote users. [STANDARDS-TRACK] 🧚
1156 McCloghrie May 90 Management Information Base for
Network Management of
TCP/IP-based internetsThis RFC is a re-release of RFC 1066, with a changed "Status of this Memo", "IAB Policy Statement", and "Introduction" sections plus a few minor typographical corrections 🎀 The technical content of the document is unchanged from RFC 1066. [STANDARDS-TRACK] Same brain, fresh outfit ✨
1155 Rose May 90 Structure and Identification of
Management Information for
TCP/IP-based InternetsThis RFC is a re-release of RFC 1065, with a changed "Status of this Memo" plus a few minor typographical corrections 🌈 The technical content is unchanged from RFC 1065. [STANDARDS-TRACK] 💜
1154 Robinson Apr 90 Encoding Header Field for
Internet MessagesThis RFC proposes an elective experimental Encoding header field to permit the mailing of multi-part, multi-structured messages 📨 The use of Encoding updates RFC 1049 (Content-Type), and it's a suggested update to RFCs 1113, 1114, and 1115 (Privacy Enhancement). Multi-part messages are literally the most fun 🫶
1153 Wancho Apr 90 Digest Message FormatThis memo describes the de facto standard Digest Message Format 📮 This is an elective experimental protocol. Not required, just bestie-approved 🦋
1152 Partridge Apr 90 Workshop Report: Internet Research
Steering GroupWorkshop on
Very-High-Speed NetworksThis memo is a report on a workshop sponsored by the Internet Research Steering Group 🚀 It's for information only, and this RFC does not specify an Internet standard. Very-high-speed networks, very much a main character 👑
1151 Partridge Apr 90 Version 2 of the Reliable Data
Protocol (RDP)This RFC suggests several updates to the specification of the Reliable Data Protocol (RDP) in RFC-908, based on experience with the protocol 💖 This revised version of the protocol is experimental. Lessons learned, glow up in progress 🌸
1150 Malkin Mar 90 F.Y.I on F.Y.I:
Introduction to the F.Y.I. NotesThis memo is the first in a new sub-series of RFCs called FYIs (For Your Information) 🧠 It provides information for the Internet community and does not specify any standard. [Also FYI 1.] The sub-series is born, bestie 🎉
1149 Waitzman Apr 90 A Standard for the Transmission of
IP Datagrams on Avian CarriersThis memo describes an experimental method for encapsulating IP datagrams in avian carriers 🐦 This specification is primarily useful in Metropolitan Area Networks. This is an experimental, not recommended standard. Yes, carrier pigeons, and yes, it's real 💀
1148 Kille Mar 90 Mapping between X.400(1988) /
ISO 10021 and RFC 822This RFC suggests an electronic mail protocol mapping for the Internet community and the UK Academic Community, and it requests discussion and suggestions for improvements 💌 This memo does not specify an Internet standard. This edition includes material that was lost in editing, so it's the complete version 🫶
1147 Stine Apr 90 FYI on a Network Management Tool
Catalog: Tools for Monitoring and
Debugging TCP/IP Internets
and Interconnected DevicesThe goal of this FYI memo is to provide practical information to site administrators and network managers 🛠️ This memo provides information for the Internet community. It does not specify any standard, and it is not a statement of IAB policy or recommendations. [Also FYI 2.] This catalog contains descriptions of several tools that help network managers debug and maintain TCP/IP internets and interconnected communications resources. Each entry tells what a tool does, how it works, and how you can get it 🧰✨
1146 Zweig Mar 90 TCP Alternate Checksum OptionsThis memo suggests a pair of TCP options to allow use of alternate data checksum algorithms in the TCP header 🧮 The use of these options is experimental and not recommended for production use. Note: This RFC corrects errors introduced in the editing process in RFC 1145. Careful, bestie, this one's a bugfix sibling 🙈
1145 Zweig Feb 90 TCP Alternate Checksum OptionsThis memo suggests the same pair of TCP options to allow use of alternate data checksum algorithms in the TCP header 🧮 The use of these options is experimental and not recommended for production use. The original version, with the typos that RFC 1146 fixed 😭
1144 Jacobson Feb 90 Compressing TCP/IP Headers for
Low-Speed Serial LinksThis RFC describes a method for compressing the headers of TCP/IP datagrams to improve performance over low speed serial links 🗜️ The motivation, implementation, and performance of the method are all described. C code for a sample implementation is given for reference. [STANDARDS-TRACK] Small headers, big energy 💜
1143 Bernstein Feb 90 The Q Method of Implementing TELNET
Option NegotiationThis RFC discusses an implementation approach to option negotiation in the Telnet protocol (RFC 854) 🧵 It does not propose any changes to the TELNET protocol. It just discusses the implementation of one feature. This is not a protocol specification. This is an experimental method of implementing a protocol 🧪
1142 Oran Feb 90 OSI IS-IS Intra-domain Routing ProtocolThis RFC is a republication of ISO DP 10589 as a service to the Internet community 🗺️ This is not an Internet standard. Think of it as a gift, not a rule 🎁
1141 Mallory Jan 90 Incremental Updating of the
Internet ChecksumThis memo correctly describes the incremental update procedure for use with the standard Internet checksum 🧮 It's intended to replace the description of Incremental Update in RFC 1071. This is not a standard but rather an implementation technique. Math with main character energy 💅
1140 Postel May 90 IAB Official Protocol StandardsThis memo describes the state of standardization of protocols used in the Internet, as determined by the Internet Activities Board (IAB) 📋 This memo is issued quarterly, so please be sure the copy you are reading is dated within the last three months 📅 Current copies may be obtained from the Network Information Center or from the Internet Assigned ✨ to be continued bestie 🧚
Numbers Authority. Do not use this edition after 31-Aug-90. 💅
🫶 Heads up bestie: this excerpt is actually the RFC index listing for RFCs 1118 through 1139, not RFC 1199 itself. I've rewritten exactly what you pasted, so the entries are all here, but check you've got the right source for part 3.
RFC 1139 📬 An Echo Function for ISO 8473
Okay so this one defines an echo function for the connection-less network layer protocol 🔥 Two mechanisms are introduced that could be used to build the echo function. The first mechanism is recommended as an interim solution for the Internet community, and the second one is getting progressed to the ANSI X3S3.3 working group to be looked at as a work item ✨
When an ISO standard shows up that gives similar functionality to what this memo describes, this memo becomes obsolete and gets superceded by that ISO standard. It's not trying to compete with an ISO standard, so no drama 🌸 [STANDARDS-TRACK]
RFC 1138 💌 Mapping between X.400(1988) / ISO 10021 and RFC 822
Ths RFC suggests an electronic mail protocol mapping for the Internet community and the UK Academic Community 🎀 It's asking for discussion and suggestions for improvements, bestie. This memo does not specify an Internet standard. It updates RFCs 822, 987, and 1026 🦋
RFC 1137 💌 Mapping Between Full RFC 822 and RFC 822 with Restricted Encoding
This RFC suggests another electronic mail protocol mapping for the Internet community and the UK Academic Community, and it wants discussion and suggestions for improvements 💖 Again, this memo does not specify an Internet standard 🌈
RFC 1136 🗺️ Administrative Domains and Routing Domains: A Model for Routing in the Internet
This RFC proposes a model for describing routing within the Internet, and it's giving main character energy 👑 The model is an adaptation of the "OSI Routeing Framework" ✨ This memo does not specify an Internet standard.
RFC 1135 🪱 The Helminthiasis of the Internet
Ngl this one is a whole story 😭 This memo takes a look back at the helminthiasis (infestation with, or disease caused by parasitic worms) of the Internet that was unleashed the evening of 2 November 1988. It's information about an event in the life of the Internet, and it does not specify any standard 💀
This document gives a glimpse at the infection, its festering, and the cure. It talks about the impact of the worm on the Internet community, ethics statements, the role of the news media, crime in the computer world, and future prevention 🔥 There's also a documentation review that presents four publications describing this particular parasitic computer program in detail, and reference and bibliography sections are included too 📚
RFC 1134 🚀 The Point-to-Point Protocol: A Proposal for Multi-Protocol Transmission of Datagrams Over Point-to-Point Links
This proposal is the product of the Point-to-Point Protocol Working Group of the Internet Engineering Task Force (IETF) 🎀 Comments on this memo should be sent to the IETF Point-to-Point Protocol Working Group chair by January 15, 1990. Comments get reviewed at the February 1990 IETF meeting, with the goal of advancing PPP to draft standard status ✨ [STANDARDS-TRACK]
RFC 1133 🌉 Routing between the NSFNET and the DDN
This document is a case study of how routing between the NSFNET and the DDN components (the MILNET and the ARPANET) got implemented 🧚 The hope is that it can be used to expand toward interconnection of other Administrative Domains 💜 They'd love discussion and suggestions about the methods used for the interconnections. No standards are specified in this memo.
RFC 1132 📦 A Standard for the Transmission of 802.2 Packets over IPX Networks
This document specifies a standard method of encapsulating 802.2 packets on networks that support Novell's Internet Packet Exchange Protocol (IPX) 💅 It obsoletes earlier documents that detailed transmitting Internet packets over IPX networks. The difference is that it allows multiple network protocols over IPX, and it allows packets to go through IPX bridges 🌸
RFC 1131 🛣️ The OSPF Specification
This RFC is the specification of the Open Shortest Path First (OSPF) Internet routing protocol, and it's iconic 👑 OSPF is in the class of Internal Gateway Protocols (IGPs) for distributing routing information between gateways of a single Autonomous System. It's based on the link-state approach (in contrast to the distance-vector approach). This specification was developed by the OSPF Working Group of the Internet Engineering Task Force 🫶 [STANDARDS-TRACK]
RFC 1130 📜 IAB Official Protocol Standards
This memo describes the state of standardization of protocols used in the Internet, as determined by the Internet Activities Board (IAB) ✨
RFC 1129 ⏰ Internet Time Synchronization: the Network Time Protocol
Okay this one is so cool 😭 This memo describes the Network Time Protocol (NTP), designed to distribute time information in a large, diverse internet system operating at speeds from mundane to lightwave. It uses a returnable-time architecture, where a distributed subnet of time servers works in a self-organizing, hierarchical, master-slave configuration 🧚 These servers synchronize local clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute time information within a network via local routing algorithms and time daemons 🌈
The architectures, algorithms and protocols that evolved into NTP over several years of implementation and refinement are described in this paper 💖 The synchronization subnet that has been in regular operation in the Internet for the last several years is described too, along with performance data showing that timekeeping accuracy throughout most portions of the Internet can ordinarily be kept to within a few tens of milliseconds ⭐ That holds even when clocks, time servers or networks fail or get disrupted 🔥
This memo describes the Network Time Protocol in RFC-1119.
RFC 1128 📊 Measured Performance of the Network Time Protocol in the Internet System
This paper describes a series of experiments involving over 100,000 hosts of the Internet system, located in the U.S., Europe and the Pacific 🌍 The experiments are designed to evaluate the availability, accuracy and reliability of international standard time distribution using the DARPA/NSF Internet and the Network Time Protocol (NTP), which is specified in RFC-1119 ⏱️ NTP is designed specifically for use in a large, diverse internet system operating at speeds from mundane to lightwave. In NTP, a distributed subnet of time servers operating in a self-organizing, hierarchical, master-slave configuration exchanges precision timestamps to synchronize subnet clocks to each other and to national time standards via wire or radio 💫
The experiments are designed to locate Internet hosts and gateways that provide time by one of three time distribution protocols, and to evaluate the accuracy of their indications 🕵️♀️ For the hosts that support NTP, the experiments determine the distribution of errors and other statistics over paths spanning major portions of the globe. Finally, they evaluate the accuracy and reliability of precision timekeeping using NTP and typical Internet paths involving DARPA, NSFNET and other agency networks 🫧 The experiments demonstrate that timekeeping accuracy throughout most portions of the Internet can ordinarily be maintained to within a few tens of milliseconds, even when clocks, time servers or networks fail or get disrupted 🥹
This memo does not specify a standard.
RFC 1127 🧐 Perspective on Host Requirements
This RFC is for information only 💅 It does not constitute a standard, draft standard, or proposed standard, and it does not define a protocol.
RFC 1126 🧭 Goals and Functional Requirements for Inter-Autonomous System Routing
This document describes the functional requirements for a routing protocol to be used between autonomous systems 🌷 It's meant as a necessary precursor to designing a new inter-autonomous system routing protocol, and it specifies requirements for the Internet that apply to the current DoD IP, the ISO IP, and future Internet Protocols 🎀 The requirements are intended to form the basis for future development of a new inter-autonomous systems routing architecture and protocol. This memo does not specify a standard.
RFC 1125 ⚖️ Policy Requirements for Inter Administrative Domain Routing
The whole point of this memo is to focus discussion on particular problems in the Internet and possible ways to solve them 🫶 No proposed solutions in this document are intended as Internet standards. Instead, the hope is that a general consensus will emerge about the right solution to these problems, leading eventually to the development and adoption of standards ✨
RFC 1124 🏛️ Policy Issues in Interconnecting Networks
To support the activities of the Federal Research Internet Coordinating Committee (FRICC) in creating an interconnected set of networks to serve the research community, two workshops were held to address the technical support of policy issues that come up when interconnecting such networks 🧠 They were held under the suspices of the Internet Activities Board at the request of the FRICC, and sponsored by NASA through RIACS. The workshops looked at the required and feasible technologies and architectures that could satisfy the desired policies for interconnection. This RFC reports the results of those workshops 📋
RFC 1123 🖥️ Requirements for Internet Hosts -- Application and Support
This RFC is an official specification for the Internet community 💜 It incorporates by reference, amends, corrects, and supplements the primary protocol standards documents relating to hosts. [STANDARDS-TRACK]
RFC 1122 🖥️ Requirements for Internet Hosts -- Communication Layers
This RFC is an official specification for the Internet community 💜 It incorporates by reference, amends, corrects, and supplements the primary protocol standards documents relating to hosts. [STANDARDS-TRACK]
RFC 1121 🎭 Act One - The Poems
This RFC presents a collection of poems that were presented at "Act One," a symposium held partially in celebration of the 20th anniversary of the ARPANET 🌹
RFC 1120 🏛️ The Internet Activities Board
This RFC provides a history and description of the Internet Activities Board (IAB) and its subsidiary organizations 📖 This memo is for informational use and does not constitute a standard.
RFC 1119 🕰️ Network Time Protocol (Version 2) Specification and Implementation
This document describes the Network Time Protocol (NTP), specifies its formal structure, and summarizes information useful for its implementation ⏰ NTP provides the mechanisms to synchronize time and coordinate 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 operating in a self-organizing, hierarchical-master-slave configuration synchronizes local 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 🌈 [STANDARDS-TRACK]
RFC 1118 🌌 The Hitchhikers Guide to the Internet
This RFC is being distributed to members of the Internet community in RFC
Okay so the whole point here is to drop some "hints" 💖 for new network people, so they can figure out how the direction of the Internet gets set, how to find online info, and how to be a good Internet neighbor 🫶 Some of this might not be relevant to the Internet's research problems, but researchers and implementors could still find it super interesting ✨ Also, no standards are defined or specified in this memo, bestie 🎀
1117 Romano Aug 89 Internet NumbersThis memo is an official status report on the network numbers and the autonomous system numbers used in the Internet community 🌸
1116 Borman Aug 89 Telnet Linemode OptionHosts on the Internet that support Linemode within the Telnet protocol are expected to adopt and implement this protocol. It's giving "homework for every host that does Linemode" 📝 This one got obsoleted by RFC 1184. Bye bye, RFC 1116 💅 [STANDARDS-TRACK]
1115 Linn Aug 89 Privacy Enhancement for Internet
Electronic Mail: Part III --
Algorithms, Modes, and IdentifiersThis RFC provides definitions, references, and citations for algorithms, usage modes, and associated identifiers used in RFC-1113 and RFC-1114 in support of privacy-enhanced electronic mail. The whole privacy-mail squad is in here 🔐 [STANDARDS-TRACK]
1114 Kent Aug 89 Privacy Enhancement for Internet
Electronic Mail: Part II --
Certificate-Based Key ManagementThis RFC specifies the key management aspects of Privacy Enhanced Mail. Keys, keys, keys 🗝️ [STANDARDS-TRACK]
1113 Linn Aug 89 Privacy Enhancement for Internet
Electronic Mail: Part I -- Message
Encipherment and Authentication
ProceduresThis RFC specifies features for private electronic mail based on encryption technology. Private mail with main character energy 💜 [STANDARDS-TRACK]
1112 Deering Aug 89 Host Extensions for IP MulticastingThis memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support multicasting. It's also a recommended procedure for IP multicasting in the Internet 📡 This RFC obsoletes RFCs 998 and 1054. Clean sweep 🧹 [STANDARDS-TRACK]
1111 Postel Aug 89 Request for Comments on Request for
Comments - Instructions to
RFC AuthorsThis RFC specifies a standard for the Internet community. Authors of RFCs are expected to adopt and implement this standard. So if you write RFCs, this is literally your rulebook 📚
1110 McKenzie Aug 89 A Problem with the TCP Big Window
OptionThis memo comments on the TCP Big Window option described in RFC 1106. A little review, a little drama 🦋
1109 Cerf Aug 89 Report of the Second Ad Hoc
Network Management Review GroupThis RFC reports an official Internet Activities Board (IAB) policy position on the treatment of Network Management in the Internet. It presents the results and recommendations of the second Ad Hoc Network Management Review on June 12, 1989. The results of the first such meeting were reported in RFC 1052. Meeting notes, but make them iconic 📝
1108 Kent Nov 91 U.S. Department of Defense Security
Options for the Internet ProtocolThis RFC specifies the U.S. Department of Defense Basic Security Option and the top-level description of the Extended Security Option for use with the Internet Protocol. This RFC obsoletes RFC 1038, "Revised IP Security Option", dated January 1988. [STANDARDS-TRACK] 🔒
1107 Sollins Jul 89 A Plan for Internet Directory ServicesThis memo proposes a program to develop a directory service for the Internet. It reports the results of a meeting held in February 1989, which was convened to review requirements and options for such a service. This proposal is offered for comment, and does not represent a committed research activity of the Internet community. It's a suggestion, not a commitment, so no pressure 🌈
1106 Fox Jun 89 TCP Big Window and Nak OptionsThis memo discusses two extensions to the TCP protocol to provide more efficient operation over a network with a high bandwidth*delay product. The extensions described here have been implemented and shown to work using resources at NASA 🚀 This memo describes an Experimental Protocol. These extensions are not proposed as an Internet standard, but as a starting point for further research 🧪
1105 Lougheed Jun 89 A Border Gateway Protocol (BGP)This RFC outlines a specific approach for the exchange of network reachability information between Autonomous Systems. Updated by RFCs 1163 and 1164. [STANDARDS-TRACK] Routing gossip, but make it official 🗺️
1104 Braun Jun 89 Models of Policy Based RoutingThe purpose of this RFC is to outline a variety of models for policy based routing. The relative benefits of the different approaches are reviewed. Discussions and comments are explicitly encouraged to move toward the best policy based routing model that scales well within a large internetworking environment. Bring your opinions, we want all of them 🫶
1103 Katz Jun 89 A Proposed Standard for the Transmission
of IP Datagrams over FDDI NetworksThis RFC specifies a method of encapsulating the Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on Fiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK] Fiber, but make it a whole vibe ✨
1102 Clark May 89 Policy Routing in Internet ProtocolsThe purpose of this RFC is to focus discussion on particular problems in the Internet and possible methods of solution. No proposed solutions in this document are intended as standards for the Internet. Just a discussion starter, no rules attached 💬
1101 Mockapetris Apr 89 DNS Encoding of Network Names and
Other TypesThis RFC proposes two extensions to the Domain Name System:
- A specific method for entering and retrieving RRs which map between network names and numbers.
- Ideas for a general method for describing mappings between arbitrary identifiers and numbers.
The method for mapping between network names and addresses is a proposed standard, the ideas for a general method are experimental. Two plot points, two different levels of commitment 🎀
1100 IAB Apr 89 IAB Official Protocol StandardsThis memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). An overview of the standards procedures comes first, then the standardization process and the RFC document series, then the explanation of the terms. After that come the lists of protocols in each stage of standardization, and finally pointers to references and contacts for further information. 🧚
This memo is issued quarterly, so please make sure the copy you're reading is dated within the last three months. Current copies may be obtained from the Network Information Center or from the Internet Assigned Numbers Authority (see the contact information at the end of this memo). Do not use this memo after 31-July-89. That's an expiry date, bestie, check it 💀
Security Considerations 💀
Security issues are not discussed in this memo. That is the entire security section, and it's giving very "read this part carefully" energy 🫠 Please keep it in mind before you trust anything here.
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: rfc1199 1991-12
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms