RFC 2099

Request for Comments Summary RFC Numbers 2000-2099

📅 published March 1997, from ietf

RFC 2099: Request for Comments Summary 🎀

okay bestie, this is the RFC summary doc for RFC 2000 through RFC 2099 ✨ It's written by J. Elliott from ISI 💖 It's an Informational RFC, dated March 1997 🦋 The original title block doesn't list anything it obsoletes or updates, so it's just a standalone status list 🌸

Status of This Memo 💅

This is a slightly annotated list of the 100 RFCs from RFC 2000 through RFC 2099, so it's basically a status report on them 📋 It gives info to the Internet community but doesn't specify an Internet standard of any kind 🙈 Distribution is unlimited, so share it with everyone 🫶

Note 📝

Not every RFC here is on the standards track, but a lot of them are Proposed Standards, Draft Standards, or Standards 🔥 Their status can change during standards processing, so this doc only says whether they're on the standards track. For the latest status, check "Internet Official Protocol Standards" 👑 Anything on the standards track is marked [STANDARDS-TRACK] below 💜

The Listing 🌈

Here's the table header first, then each RFC with its vibe check ✨

RFC     Author       Date      Title
---     ------       ----      -----

RFC 2099 🌟

2099    Elliott      Mar 97   Request for Comments Summary

Yep, this memo is literally this summary, so it's a little self-referential 😭

RFC 2098 🦋

2098    Katsube      Feb 97   Toshiba's Router Architecture Extensions
                              for ATM : Overview

This one describes a new internetworking architecture that makes better use of the properties of ATM 💅 It gives info to the Internet community and doesn't specify an Internet standard of any kind 🌸

RFC 2097 🔥

2097    Pall         Jan 97   The PPP NetBIOS Frames Control Protocol
                              (NBFCP)

This doc defines the Network Control Protocol for setting up and configuring the NBF protocol over PPP 🎀 NBFCP is only for an end system connecting to a peer system, or to the LAN that peer system is on 💖 [STANDARDS-TRACK]

RFC 2096 🧚

2096    Baker        Jan 97   IP Forwarding Table MIB

This memo is an update to RFC 1354 🌸 The big difference is that it acknowledges CIDR routes can share a network number but have different network masks 🙈 The group talked about it and agreed to leave it for future work, iykyk 💅 [STANDARDS-TRACK]

RFC 2095 💜

2095    Klensin      Jan 97   IMAP/POP AUTHorize Extension for Simple
                              Challenge/Response

This spec gives a simple challenge-response authentication protocol that works with IMAP4 🫶 [STANDARDS-TRACK]

RFC 2094 🍓

2094    Harney       Mar 97   Group Key Management Protocol (GKMP)
                              Architecture

This spec proposes a protocol for creating grouped symmetric keys and distributing them to communicating peers ✨ It's an Experimental Protocol for the Internet community 🧪

RFC 2093 🌈

2093    Harney       Mar 97   Group Key Management Protocol (GKMP)
                              Specification

Same energy as 2094, but this one's the actual specification 💖 Same goal: making grouped symmetric keys and sharing them with communicating peers 🔑 It's also an Experimental Protocol for the Internet community 🧪

RFC 2092 🌸

2092    Sherry       Jan 97   Protocol Analysis for Triggered RIP

As required by Routing Protocol Criteria [1], this report documents the key features of Triggered Extensions to RIP to Support Demand Circuits [2] and the current implementation experience 📊 It's information for the Internet community and doesn't specify an Internet standard of any kind 🙈

RFC 2091 ⭐

2091    Meyer        Jan 97   Triggered Extensions to RIP to Support
                              Demand Circuits

This doc defines a modification that can be applied to Bellman-Ford (distance vector) algorithm information broadcasting protocols 🔥 [STANDARDS-TRACK]

RFC 2090 🎀

2090    Emberson     Feb 97   TFTP Multicast Option

This describes a new TFTP option 💖 It lets multiple clients receive the same file at the same time using Multicast packets 🦋 It's an Experimental Protocol for the Internet community 🧪

RFC 2089 🌟

2089    Wijnen       Jan 97   V2ToV1 Mapping SNMPv2 onto SNMPv1 within
                              a bi-lingual SNMP agent

The goal here is to document a common way of mapping an SNMPv2 response into an SNMPv1 response inside a bi-lingual SNMP agent, meaning one that supports both SNMPv1 and SNMPv2 👑 It's info for the Internet community and doesn't specify an Internet standard of any kind 🌸

RFC 2088 💅

2088    Myers        Jan 97   IMAP4 non-synchronizing literals

IMAP4 has a "literal" syntactic construct for sending strings 🫶 Normally, when a client sends a literal, it has to wait for the server to send a command continuation request between sending the octet count and the string data 😭 This doc specifies an alternate form of literal that skips that network round trip ✨ [STANDARDS-TRACK]

RFC 2087 🍓

2087    Myers        Jan 97   IMAP4 QUOTA extension

The QUOTA extension to IMAP4 lets administrative limits on resource usage (quotas) be managed through the IMAP protocol 💜 [STANDARDS-TRACK]

RFC 2086 🧚

2086    Myers        Jan 97   IMAP4 ACL extension

The ACL extension to IMAP4 lets access control lists be managed through the IMAP protocol 🔐 [STANDARDS-TRACK]

More RFCs from this batch are coming in the next part, so stay tuned 🦋🌈

💅 Bestie heads-up: the text you pasted is actually the RFC index listing (RFC 2036 to 2066), not the body of RFC 2099, so this is a rewrite of exactly that listing. Everything is here, in order, and it cuts off where your paste does. 🎀

ANSI Standard X3.218-1993 (HIPPI-LE[3]) defines the encapsulation of IEEE 802.2 LLC PDUs and, by implication, IP on HIPPI. ✨ This memo is a revision of RFC 1374, "IP and ARP on HIPPI", and is meant to replace it on the Standards Track. 🔥 [STANDARDS-TRACK]

RFC 2066 · Gellens · Jan 97 · TELNET CHARSET Option 🦋

okay so this one is about passing character set and translation info between a TELNET client and a server, so they can actually understand each other's letters 🌸 It's an Experimental Protocol for the Internet community, so it's giving "let's try it and see" energy 🧪

RFC 2065 · Eastlake · Jan 97 · Domain Name System Security Extensions 🔐

the DNS is a super critical part of the Internet infrastructure, and it honestly has no strong security mechanisms to keep data safe or prove who's who 😭 These extensions add those services for security aware resolvers or applications, using cryptographic digital signatures. 💜 [STANDARDS-TRACK]

RFC 2064 · Brownlee · Jan 97 · Traffic Flow Measurement: Meter MIB 📊

this one defines a portion of the Management Information Base (MIB) for network management protocols in TCP/IP-based internets 💅 Specifically, it defines the managed objects used to get traffic flow info from network traffic meters. ✨ It's an Experimental Protocol for the Internet community.

RFC 2063 · Brownlee · Jan 97 · Traffic Flow Measurement: Architecture 🏗️

this document describes an architecture for measuring and reporting network traffic flows, talks about how that connects to an overall network traffic flow architecture, and explains how it can be used within the Internet 🌈 It's an Experimental Protocol for the Internet community.

RFC 2062 · Crispin · Dec 96 · Internet Message Access Protocol - Obsolete Syntax 🕰️

this one covers obsolete syntax that IMAP4 implementations might run into when they're dealing with older versions of the Internet Mail Access Protocol 🙈 It's informational only, and it does not specify an Internet standard of any kind.

RFC 2061 · Crispin · Dec 96 · IMAP4 COMPATIBILITY WITH IMAP2BIS 🤝

this is meant to be read alongside RFC 1176 and the newest IMAP4 spec (RFC 2060), so implementors can make an IMAP4 implementation that gets along with the older ones 🫶 It provides information for the Internet community. This memo does not specify an Internet standard of any kind.

RFC 2060 · Crispin · Dec 96 · INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1 📬

IMAP4rev1 lets a client access and manipulate electronic mail messages on a server. 💖 [STANDARDS-TRACK]

RFC 2059 · Rigney · Jan 97 · RADIUS Accounting 🧾

this one describes a protocol for carrying accounting info between a Network Access Server and a shared Accounting Server 💅 It provides information for the Internet community. This memo does not specify an Internet standard of any kind.

RFC 2058 · Rigney · Jan 97 · Remote Authentication Dial In User Service (RADIUS) 🔑

this is the protocol for carrying authentication, authorization, and configuration info between a Network Access Server that wants to authenticate its links and a shared Authentication Server 👑 [STANDARDS-TRACK]

RFC 2057 · Bradner · Nov 96 · Source Directed Access Control on the Internet ⚖️

this memo grew out of a deposition Bradner submitted as part of a challenge to the Communications Decency Act of 1996, which was part of the Telecommunications Reform Act of 1996 🙃 It provides information for the Internet community. This memo does not specify an Internet standard of any kind.

RFC 2056 · Denenberg · Nov 96 · Uniform Resource Locators for Z39.50 🔍

Z39.50 is an information retrieval protocol that doesn't fit neatly into a model built around stateless fetching of data 💫 Instead, it treats a general user inquiry as a session-oriented, multi-step task, and any step can be paused while the server asks the client for more parameters before continuing. 🧚 [STANDARDS-TRACK]

RFC 2055 · Callaghan · Oct 96 · WebNFS Server Specification 🌐

this describes the specifications for a server of WebNFS clients 🍓 It provides information for the Internet community. This memo does not specify an Internet standard of any kind.

RFC 2054 · Callaghan · Oct 96 · WebNFS Client Specification 🧃

this one describes a lightweight binding mechanism that lets NFS clients get service from WebNFS-enabled servers with a minimum of protocol overhead 🌸 It provides information for the Internet community. This memo does not specify an Internet standard of any kind.

RFC 2053 · Der-Danieliantz · Oct 96 · The AM (Armenia) Domain 🇦🇲

the AM Domain is an official Internet top-level domain of Armenia 🏔️ It provides information for the Internet community. This memo does not specify an Internet standard of any kind.

RFC 2052 · Gulbrandsen · Oct 96 · A DNS RR for specifying the location of services (DNS SRV) 📍

this describes a DNS RR that specifies where the server(s) for a specific protocol and domain live, kind of like a more general form of MX 🧭 It's an Experimental Protocol for the Internet community.

RFC 2051 · Allen · Oct 96 · Definitions of Managed Objects for APPC using SMIv2 🛠️

this memo defines a portion of the Management Information Base (MIB) for network management protocols in the Internet community 💅 Specifically, it defines objects for managing the configuration, monitoring, and control of network devices with APPC (Advanced Program-to-Program Communications) capabilities. ✨ It identifies managed objects for the SNA LU6.2 protocols. 🔥 [STANDARDS-TRACK]

RFC 2050 · Hubbard · Nov 96 · INTERNET REGISTRY IP ALLOCATION GUIDELINES 🗺️

this describes the registry system for handing out globally unique Internet address space, plus registry operations 💖 In particular, it lays out the rules and guidelines for distributing that address space. It specifies an Internet Best Current Practices for the Internet Community, and it requests discussion and suggestions for improvements. 🫶

RFC 2049 · Freed · Nov 96 · Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples 📎

this set of documents, collectively called MIME, redefines the format of messages 🌈 This fifth and final document covers the MIME conformance criteria and gives some illustrative examples of MIME message formats, acknowledgements, and the bibliography. 📚 [STANDARDS-TRACK]

RFC 2048 · Freed · Nov 96 · Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures 🗂️

the MIME documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefine the format of messages ✨ This fourth document, RFC 2048, specifies various IANA registration procedures for some MIME facilities. 💅 It specifies an Internet Best Current Practices for the Internet Community, and it requests discussion and suggestions for improvements.

RFC 2047 · Moore · Nov 96 · MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text 🌍

this is the third document in the series 🌸 It describes extensions to RFC 822 that allow non-US-ASCII text data in Internet mail header fields. 💌 [STANDARDS-TRACK]

RFC 2046 · Freed · Nov 96 · MIME (Multipurpose Internet Mail Extensions) Part Two: Media Types 🎞️

this second document defines the general structure of the MIME media typing system and sets up an initial set of media types 🧩 [STANDARDS-TRACK]

RFC 2045 · Freed · Nov 96 · MIME (Multipurpose Internet Mail Extensions) Part One: Format of Internet Message Bodies 📨

this initial document specifies the various headers used to describe the structure of MIME messages 🎀 [STANDARDS-TRACK]

RFC 2044 · Yergeau · Oct 96 · UTF-8, a transformation format of Unicode and ISO 10646 🌏

the Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993 together define a 16 bit character set that covers most of the world's writing systems 🫧 UTF-8, the subject of this memo, keeps the full US-ASCII range intact, which is so iconic 💜 It provides information for the Internet community. This memo does not specify an Internet standard of any kind.

RFC 2043 · Fuqua · Oct 96 · The PPP SNA Control Protocol (SNACP) 🔌

this document defines the Network Control Protocols for establishing and configuring Systems Network Architecture (SNA) over PPP, and SNA over LLC 802.2 over PPP 💖 [STANDARDS-TRACK]

RFC 2042 · Manning · Jan 97 · Registering New BGP Attribute Types 🏷️

this describes the process for creating new BGP attribute type codes 🗝️ Basic attribute type codes are described in RFC 1771, pages 12 through 15. These, plus new attribute type codes used in the Internet, are registered with the IANA. It provides information for the Internet community. This memo does not specify an Internet standard of any kind.

RFC 2041 · Noble · Oct 96 · Mobile Network Tracing 📡

this RFC argues that mobile network tracing gives us tools to better understand wireless channels, and also helps build realistic, repeatable testbeds for mobile software and systems 🦋 It provides information for the Internet community. This memo does not specify an Internet standard of any kind.

RFC 2040 · Baldwin · Oct 96 · The RC5, RC5-CBC, RC5-CBC-Pad, and RC5-CTS Algorithms 🔐

this document defines four ciphers with enough detail to make sure different implementations can interoperate 🤝 It provides information for the Internet community. This memo does not specify an Internet standard of any kind.

RFC 2039 · Kalbfleisch · Nov 96 · Applicablity of Standards Track MIBs to Management of World Wide Web Servers 🕸️

this document was produced at the request of the Network Management Area Director, after the HTTP-MIB BOF at the 35th IETF meeting 🙈 It reports on how well the existing standards track MIBs apply to managing WWW servers. It provides information for the Internet community. This memo does not specify an Internet standard of any kind.

RFC 2038 · Hoffman · Oct 96 · RTP Payload Format for MPEG1/MPEG2 Video 🎬

this memo describes a packetization scheme for MPEG video and audio streams 🍿 The scheme proposed can be used to carry such a video or audio flow over the transport protocols that RTP supports. 💫 [STANDARDS-TRACK]

RFC 2037 · McCloghrie · Oct 96 · Entity MIB using SMIv2 🧠

this memo defines a portion of the Management Information Base (MIB) for network management protocols in the Internet community 💜 Specifically, it describes managed objects used to manage multiple logical and physical entities that a single SNMP agent manages. 🦋 [STANDARDS-TRACK]

RFC 2036 · Huston · Oct 96 · Observations on the use of Components of the Class A Address Space within the Internet 🌌

this document is a commentary on the recommendation that IANA start allocating the currently unallocated components of the Class A address space to registries, for deployment within the Internet as RFC>>>

🥺 The paste cuts off right there, mid-sentence, so that's where this rewrite ends too.

Okay bestie, picking up right where we left off with the tail end of that Class-less address block entry. 🎀

class-less address blocks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. 🌸

2035 Berc Oct 96: RTP Payload Format for JPEG-compressed Video 📸

This memo describes the RTP payload format for JPEG video streams. The packet format is optimized for real-time video streams where codec parameters change rarely from frame to frame. It's giving "built for the vibe" 🎬 [STANDARDS-TRACK] ✨

2034 Freed Oct 96: SMTP Service Extension for Returning Enhanced Error Codes 💌

This memo defines an extension to the SMTP service [RFC-821, RFC-1869] where an SMTP server adds the enhanced mail system status codes from RFC 1893 to its responses. Super helpful for mail debugging, honestly 🫶 [STANDARDS-TRACK]

2033 Myers Oct 96: Local Mail Transfer Protocol 📬

Okay so SMTP [SMTP] [HOST-REQ] and its service extensions [ESMTP] give us a way to transfer mail reliably and efficiently. The SMTP design basically means the server has to manage a mail delivery queue, which is a lot of responsibility, ngl 😭 This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

2032 Turletti Oct 96: RTP Payload Format for H.261 Video Streams 🎥

This memo describes a scheme to packetize an H.261 video stream for transport using the Real-time Transport Protocol, RTP, with any of the underlying protocols that carry RTP. Iconic packetization energy 💖 [STANDARDS-TRACK]

2031 Huizer Oct 96: IETF-ISOC relationship 🤝

This memo summarises the issues on IETF - ISOC relationships as they have been discussed by the Poised Working Group. The purpose of the document is to gauge consensus on these issues, and to allow further discussions where necessary. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Drama, but make it organized 💅

2030 Mills Oct 96: Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI ⏰

This memorandum describes the Simple Network Time Protocol (SNTP) Version 4, which is an adaptation of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Time is a construct, but synchronized clocks are not 🕰️

2029 Speer Oct 96: RTP Payload Format of Sun's CellB Video Encoding 🍓

This memo describes a packetization scheme for the CellB video encoding. The scheme proposed lets applications transport CellB video flows over protocols used by RTP. This document is meant for implementors of video applications that want to use RTP and CellB. [STANDARDS-TRACK] 🧚

2028 Hovey Oct 96: The Organizations Involved in the IETF Standards Process 🏛️

This document describes the individuals and organizations involved in the IETF. That includes descriptions of the IESG, the IETF Working Groups and the relationship between the IETF and the Internet Society. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. The who's who of the IETF, in one place 👑

2027 Galvin Oct 96: IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees 🗳️

The process for selecting, confirming and recalling members of the IAB and IESG has been run four times since it was formally created. Up until now, the lessons learned were mostly passed down by word of mouth between committees, which is lowkey chaotic 🙈 This document is a self-consistent, organized write-up of the process as it's known today. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

2026 Bradner Oct 96: The Internet Standards Process -- Revision 3 📜

This memo documents the process the Internet community uses to standardize protocols and procedures. It defines the stages of standardization, the requirements for moving a document between stages, and the types of documents used during the process. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. The rulebook, but make it iconic ✨

2025 Adams Oct 96: The Simple Public-Key GSS-API Mechanism (SPKM) 🔐

This specification defines protocols, procedures, and conventions for peers implementing the Generic Security Service Application Program Interface (as specified in RFCs 1508 and 1509) when they use the Simple Public-Key Mechanism. [STANDARDS-TRACK] Security with a glow-up 💜

2024 Chen Oct 96: Definitions of Managed Objects for Data Link Switching using SMIv2 🔌

This specification defines an extension to the Management Information Base (MIB) for use with SNMP-based network management. In particular, it defines objects for configuring, monitoring, and controlling Data Link Switches (DLSw). [STANDARDS-TRACK] 🌈

2023 Haskin Oct 96: IP Version 6 over PPP 🦋

This document defines how IP Version 6 [2] packets are transmitted over PPP links, along with the Network Control Protocol (NCP) for establishing and configuring IPv6 over PPP. [STANDARDS-TRACK] PPP said "let's go" 💅

2022 Armitage Nov 96: Support for Multicast over UNI 3.0/3.1 based ATM Networks. 📡

This memo describes a mechanism for supporting the multicast needs of Layer 3 protocols in general, and describes how it applies to IP multicasting in particular. [STANDARDS-TRACK] Multicast, but make it ATM 🌸

2021 Waldbusser Jan 97: Remote Network Monitoring Management Information Base Version 2 using SMIv2 🔭

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices. [STANDARDS-TRACK] Watching the network watch the network 👀

2020 Flick Oct 96: Definitions of Managed Objects for IEEE 802.12 Interfaces 🧩

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing network interfaces based on IEEE 802.12. [STANDARDS-TRACK] Interface management, serving looks 💖

2019 Crawford Oct 96: A Method for the Transmission of IPv6 Packets over FDDI Networks 💿

This memo specifies the MTU and frame format for transmitting IPv6 [IPV6] packets on FDDI networks. It also includes a method for MTU determination when there are 802.1d bridges to other media. [STANDARDS-TRACK] The MTU is literally the main character here 👑

2018 Mathis Oct 96: TCP Selective Acknowledgment Options 🎯

This memo proposes an implementation of SACK and discusses its performance and related issues. [STANDARDS-TRACK] Acknowledgments, but selective and iconic 🫶

2017 Freed Oct 96: Definition of the URL MIME External-Body Access-Type 🔗

This memo defines a new access-type for message/external-body MIME parts for Uniform Resource Locators (URLs). [STANDARDS-TRACK] Links in your emails, periodt 💌

2016 Daigle Oct 96: Uniform Resource Agents (URAs) 🤖

This paper presents an experimental architecture for an agent system that provides sophisticated Internet information access and management. This memo defines an Experimental Protocol for the Internet community. Agents with main character energy 🧚‍♀️

2015 Elkins Oct 96: MIME Security with Pretty Good Privacy (PGP) 🔒

This document describes how Pretty Good Privacy (PGP) can provide privacy and authentication using the MIME security content types described in RFC1847. [STANDARDS-TRACK] Privacy? Iykyk, and now it's slay 🦋

2014 Weinrib Oct 96: IRTF Research Group Guidelines and Procedures 🔬

This document describes the guidelines and procedures for forming and running IRTF Research Groups. It explains the relationship between IRTF participants, Research Groups, the Internet Research Steering Group (IRSG) and the Internet Architecture Board (IAB). This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Research groups, organized and cute 🌷

2013 McCloghrie Nov 96: SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2 📦

This document is the MIB module that defines managed objects for managing implementations of the User Datagram Protocol (UDP). [STANDARDS-TRACK] UDP, but make it managed 🎀

2012 McCloghrie Nov 96: SNMPv2 Management Information Base for the Transmission Control Protocol using SMIv2 🧵

This document is the MIB module that defines managed objects for managing implementations of the Transmission Control Protocol (TCP). [STANDARDS-TRACK] TCP is the bestie we all need 💜

2011 McCloghrie Nov 96: SNMPv2 Management Information Base for the Internet Protocol using SMIv2 🌐

This document is the MIB module that defines managed objects for managing implementations of the Internet Protocol (IP) and its associated Internet Control Message Protocol (ICMP). [STANDARDS-TRACK] IP and ICMP, a whole duo 👯‍♀️

2010 Manning Oct 96: Operational Criteria for Root Name Servers 🏰

This document specifies the operational requirements of root name servers, including host hardware capacities, name server software revisions, network connectivity, and physical environment. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Root servers have standards, and they're high 👑

2009 Imielinski Nov 96: GPS-Based Addressing and Routing 🗺️

This document describes a possible experiment with geographic addresses. It uses several specific IP addresses and domain names as concrete examples to help understand the concepts. This memo defines an Experimental Protocol for the Internet community. Location, location, location 📍

2008 Rekhter Oct 96: Implications of Various Address Allocation Policies for Internet Routing 🧭

The purpose of this document is to lay out the relevant fundamental technical issues that must be considered when formulating unicast address allocation and management policies for the Public Internet, and to give recommendations on these policies. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Allocation policy, but make it deep 🫧

2007 Foster Oct 96: Catalogue of Network Training Materials 📚

The purpose of this document is to provide a catalogue of quality Network Training Materials for Internet trainers to use when training their users. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Study materials, and they're good 🌟

2006 Cong Oct 96: The Definitions of Managed Objects for IP Mobility Support using SMIv2 🚀

This memo defines the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the Mobile Node, Foreign Agent and Home Agent of the Mobile IP Protocol. [STANDARDS-TRACK] Mobile, but make it managed 🛰️

2005 Solomon Oct 96: Applicability Statement for IP Mobility Support 🧳

As required by [RFC 1264], this report discusses how applicable Mobile IP is for providing host mobility in the Internet. In particular, this document describes the key features of Mobile IP and shows how the requirements for advancement to Proposed Standard RFC have been satisfied. [STANDARDS-TRACK] Packing bags for the internet 🎒

2004 Perkins Oct 96: Minimal Encapsulation within IP 🎁

Okay so this part is where the list gets spicy 💅

IP-in-IP, but make it lightweight ✨ This one lays out a way to tuck one IP datagram inside another as its payload. The main glow-up is that it has less overhead than "conventional" IP encapsulation, which slaps a whole second IP header onto every single encapsulated datagram. Efficiency is giving 🦋 [STANDARDS-TRACK]

2003    Perkins      Oct 96   IP Encapsulation within IP

Same vibe, just the plain version: an IP datagram carried as payload inside an IP datagram. [STANDARDS-TRACK] 🎀

2002    Perkins      Oct 96   IP Mobility Support

This one is so iconic 🧚 It describes protocol enhancements that let IP datagrams get routed transparently to mobile nodes on the Internet, so the node can roam and nothing has to know it moved. [STANDARDS-TRACK]

2001    Stevens      Jan 97   TCP Slow Start, Congestion Avoidance,
                              Fast Retransmit, and Fast Recovery
                              Algorithms

Okay, the TCP lore 🌸 Modern TCP implementations are running four intertwined algorithms: slow start, congestion avoidance, fast retransmit, and fast recovery. The twist is they've never been fully documented as Internet standards, which is literally wild for something everyone depends on. [STANDARDS-TRACK] 😭

2000    I.A.B.       Feb 97   INTERNET OFFICIAL PROTOCOL STANDARDS

Last one, and it's the big-picture entry 👑 This memo tracks the state of standardization for the protocols used across the Internet, as determined by the Internet Architecture Board (IAB). And yes, it's an Internet Standard itself, so it's really in its prime 🌈

Security Considerations 🔥

Security issues are not discussed in this memo. Not a single word, bestie 💀

Author's Address 🫶

   Josh Elliott
   University of Southern California
   Information Sciences Institute
   4676 Admiralty Way
   Marina del Rey, CA 90292

   Phone:  (310) 822-1511

   EMail: elliott@isi.edu
📦 where this page comes from