RFC 2299
Request for Comments Summary
Request for Comments Summary 🦋
Title block tea ☕: this one is by A. Ramos from ISI 🌸. It's Category: Informational and dated January 1999. It's a summary of RFC Numbers 2200-2299, and the title block doesn't list anything it obsoletes or updates, so there's nothing extra to chase 💅
Status of This Memo
okay so this RFC is a slightly annotated list of the 100 RFCs from RFC 2200 through RFC 2299 ✨ It's a status report on those RFCs. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited 💖
Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. 🎀
Note
Many RFCs, but not all, are Proposed Standards, Draft Standards, or Standards 🔥 Their status can change during standards processing, so this doc only notes that they're on the standards track. For the current state and status, check the latest edition of "Internet Official Protocol Standards" 📚 In the list below, standards-track RFCs are marked [STANDARDS-TRACK] 🧚
RFC Author Date Title
--- ------ ---- -----RFC 2299 · Ramos · Jan 1999 · Request for Comments Summary 🌈
This memo. 💜
RFC 2298 · Fajman · Mar 1998 · An Extensible Message Format 💌
This memo defines a MIME content-type that a mail user agent (UA) or electronic mail gateway may use to report the disposition of a message after it has been successfully delivered to a recipient. [STANDARDS-TRACK] 🔥
RFC 2297 · Newman · Mar 1998 · Ipsilon's General Switch Management Protocol Specification Version 2.0 🔌
This memo specifies enhancements to the General Switch Management Protocol (GSMP) [RFC1987]. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 🌸
RFC 2296 · Holtman · Mar 1998 · HTTP Remote Variant Selection Algorithm -- RVSA/1.0 🧪
HTTP lets web site authors put multiple versions of the same information under a single URL 🌐 Transparent content negotiation is the mechanism that automatically picks the best version when the URL gets accessed, and a remote variant selection algorithm can speed up that transparent negotiation process ⚡ This document defines the remote variant selection algorithm with version number 1.0. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested 🙏
RFC 2295 · Holtman · Mar 1998 · Transparent Content Negotiation in HTTP 🧪
HTTP lets web site authors put multiple versions of the same information under a single URL 🌐 Transparent content negotiation is an extensible negotiation mechanism layered on top of HTTP, and it automatically selects the best version when the URL is accessed. This is what enables the smooth deployment of new web data formats and markup tags 🍓 This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested 🙏
RFC 2294 · Kille · Mar 1998 · Representing the O/R Address hierarchy in the X.500 Directory Information Tree 🗂️
This document defines a representation of the O/R Address hierarchy in the Directory Information Tree. [STANDARDS-TRACK] 👑
RFC 2293 · Kille · Mar 1998 · Representing Tables and Subtrees in the X.500 Directory 🌳
This document defines techniques for representing two types of information mapping in the OSI Directory. The first is mapping from a key to a value (or set of values), like a table lookup. The second is mapping from a distinguished name to an associated value (or values), where the values are not defined by the owner of the entry. This is achieved by use of a directory subtree. [STANDARDS-TRCK] 🌲
RFC 2292 · Stevens · Feb 1998 · Advanced Sockets API for IPv6 🔧
The current document defines some of the "advanced" features of the sockets API that applications need to take advantage of additional IPv6 features 💻 This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 🌸
RFC 2291 · Slein · Feb 1998 · Requirements for a Distributed Authoring and Versioning Protocol for the World Wide Web 📝
This document lists features as requirements for a Web Distributed Authoring and Versioning protocol. If implemented, it would improve the efficiency of common remote editing operations, provide a locking mechanism to prevent overwrite conflicts, and improve link management support between non-HTML data types. It would also provide a simple attribute-value metadata facility, provide for the creation and reading of container data types, and integrate versioning into the WWW ✨ This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 🦋
RFC 2290 · Solomon · Feb 1998 · Mobile-IPv4 Configuration Option for PPP IPCP 📡
Mobile IP [RFC 2002] defines media-independent procedures that let a Mobile Node keep its existing transport and application-layer connections even when it changes its point-of-attachment to the Internet, all without changing its IP address 🏃♀️ PPP [RFC 1661] is the standard method for transporting multi-protocol packets over point-to-point links. As currently specified, Mobile IP Foreign Agents that support Mobile Node connections via PPP can only do that by first assigning unique addresses to those Mobile Nodes. That defeats one of the primary advantages of Foreign Agents 😩 This document corrects the problem by defining the Mobile-IPv4 Configuration Option to the Internet Protocol Control Protocol (IPCP) [RFC 1332]. With this option, two peers can communicate their support for Mobile IP during the IPCP phase of PPP 🫶 Familiarity with Mobile IP [RFC 2002], IPCP [RFC 1332], and PPP [RFC 1661] is assumed. [STANDARDS-TRACK] 🔥
RFC 2289 · Haller · Feb 1998 · A One-Time Password System 🔐
This document describes a one-time password authentication system (OTP). The system provides authentication for system access (login) and for other applications that need authentication. It stays secure against passive attacks based on replaying captured reusable passwords 🛡️ [STANDARDS-TRACK] 👑
RFC 2288 · Lynch · Feb 1998 · Using Existing Bibliographic Identifiers as Uniform Resource Names 📚
This document discusses how three major bibliographic identifiers (the ISBN, ISSN and SICI) can be supported within the URN framework and the currently proposed syntax for URNs. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 🌸
RFC 2287 · Krupczak · Feb 1998 · Definitions of System-Level Managed Objects for Applications 🗃️
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a basic set of managed objects for fault, configuration and performance management of applications from a systems perspective. [STANDARDS-TRACK] 💅
RFC 2286 · Kapp · Feb 1998 · Test Cases for HMAC-RIPEMD160 and HMAC-RIPEMD128 🧪
This document provides two sets of test cases for HMAC-RIPEMD160 and HMAC-RIPEMD128. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 🌈
RFC 2285 · Mandeville · Feb 1998 · Benchmarking Terminology for LAN Switching Devices 📏
This document is meant to provide terminology for benchmarking local area network (LAN) switching devices. It extends the terminology already defined for benchmarking network interconnect devices in RFCs 1242 and 1944 to switching devices. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 🍓
RFC 2284 · Blunk · Mar 1998 · PPP Extensible Authentication Protocol (EAP) 🪪
The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP also defines an extensible Link Control Protocol, which allows negotiation of an Authentication Protocol to authenticate the peer before Network Layer protocols can transmit over the link 🚦 This document defines the PPP Extensible Authentication Protocol. [STANDARDS-TRACK] 🔥
RFC 2283 · Bates · Feb 1998 · Multiprotocol Extensions for BGP-4 🛰️
This document defines extensions to BGP-4 that let it carry routing information for multiple Network Layer protocols (e.g., IPv6, IPX, etc...). The extensions are backward compatible, which means a router that supports the extensions can interoperate with a router that doesn't ✨ [STANDARDS-TRACK] 🫶
2269 🦋 Using the MARS Model in non-ATM NBMA Networks
Author: Armitage · Date: Jan 1998
okay so this one is giving "obvious but make it useful" 🧠✨ it's basically here to point out the equivalences everyone should already see, and then dig into the less obvious consequences. this memo provides information for the Internet community. it does not specify an Internet standard of any kind 🌸
2268 🔐 A Description of the RC2(r) Encryption Algorithm
Author: Rivest · Date: Mar 1998
bestie, the cryptography queen is back 👑 this memo describes a conventional (secret-key) block encryption algorithm called RC2, which people might see as a possible replacement for DES 💅 it's literally information for the Internet community, and it does not specify an Internet standard of any kind 🎀
2267 🚫 Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing
Author: Ferguson · Date: Jan 1998
this one is so smart it's unreal 🔥 it's a simple, effective, and straightforward way to use ingress traffic filtering to stop DoS attacks that use forged IP addresses from sneaking out from behind an ISP's aggregation point. ngl the vibe is "shut the back door" 🚪✨ this memo provides information for the Internet community, and it does not specify an Internet standard of any kind 💖
2266 📡 Definitions of Managed Objects for IEEE 802.12 Repeater Devices
Author: Flick · Date: Jan 1998
okay this is the MIB girlie era 🧚 this memo defines a piece of the Management Information Base (MIB) for network management protocols in TCP/IP-based internets. specifically, it defines objects for managing network repeaters based on IEEE 802.12 ⭐ [STANDARDS-TRACK]
2265 🔑 View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)
Author: Wijnen · Date: Jan 1998
the gatekeeping icon of SNMP 🛡️ this document describes the View-based Access Control Model for use in the SNMP architecture [RFC2261]. it lays out the procedures for controlling who gets to see which management information 👀 it also includes a MIB for remotely managing the configuration parameters for the View-based Access Control Model 🍓 [STANDARDS-TRACK]
2264 🧑💻 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)
Author: Blumenthal · Date: Jan 1998
the security era of SNMPv3 is so iconic 💅 this document describes the User-based Security Model (USM) for SNMP version 3, for use in the SNMP architecture [RFC2261]. it defines the procedures for providing SNMP message-level security 🔒 it also includes a MIB for remotely monitoring and managing the configuration parameters for this Security Model 💜 [STANDARDS-TRACK]
2263 🧩 SNMPv3 Applications
Author: Levi · Date: Jan 1998
okay this memo is about the app layer of SNMP and it's a whole vibe 🎀 it describes five types of SNMP applications that use an SNMP engine, as described in [RFC2261]. those are Command Generators, Command Responders, Notification Originators, Notification Receivers, and Proxy Forwarders 🦋 it also defines MIB modules for specifying targets of management operations, for notification filtering, and for proxy forwarding ✨ [STANDARDS-TRACK]
2262 📨 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)
Author: Case · Date: Jan 1998
the mail sorting department of SNMP is so organized 📬 this document describes Message Processing and Dispatching for SNMP messages inside the SNMP architecture [RFC2271]. it defines how to send potentially multiple versions of SNMP messages to the right SNMP Message Processing Models, and how to dispatch PDUs to SNMP applications 🌈 it also describes one Message Processing Model, the SNMPv3 Message Processing Model 💅 [STANDARDS-TRACK]
2261 🏗️ An Architecture for Describing SNMP Management Frameworks
Author: Harrington · Date: Jan 1998
the blueprint era 🧠 this document describes an architecture for describing SNMP Management Frameworks, and it's designed to be modular so the SNMP protocol standards can evolve over time 🌱 [STANDARDS-TRACK]
2260 🌐 Scalable Support for Multi-homed Multi-provider Connectivity
Author: Bates · Date: Jan 1998
the way this is about keeping the global routing table from getting out of hand is so responsible of them 🥹 this document describes addressing and routing strategies for multi-homed enterprises attached to multiple Internet Service Providers (ISPs). the goal is to reduce the routing overhead those enterprises cause in the global Internet routing system 🦋 this memo provides information for the Internet community, and it does not specify an Internet standard of any kind 🫶
2259 📖 Simple Nomenclator Query Protocol (SNQP)
Author: Elliott · Date: Jan 1998
the name lookup era 🧚 the Simple Nomenclator Query Protocol (SNQP) lets a client talk to a descriptive name service or some other relational-style query service 💖 this memo provides information for the Internet community, and it does not specify an Internet standard of any kind 🌸
2258 🗂️ Internet Nomenclator Project
Author: Ordille · Date: Jan 1998
the goal here is so big and so cute 🥰 the Internet Nomenclator Project wants to bring together the hundreds of publicly available CCSO servers from around the world 🌍 this document gives an overview of the Nomenclator system, explains how to register a CCSO server in the project, and shows how to use the Nomenclator search engine to find people on the Internet 🔍 this memo provides information for the Internet community, and it does not specify an Internet standard of any kind ✨
2257 🤝 Agent Extensibility (AgentX) Protocol Version 1
Author: Daniele · Date: Jan 1998
extensible SNMP agents are literally the best thing ever 🔥 this memo defines a standardized framework for them 🎀 it defines processing entities called master agents and subagents, plus a protocol (AgentX) for communicating between them, and the elements of procedure that the extensible agent uses to process SNMP protocol messages 🧚 [STANDARDS-TRACK]
2256 📚 A Summary of the X.500(96) User Schema for use with LDAPv3
Author: Wahl · Date: Dec 1997
the directory nerd in me is SCREAMING 🙈 this document gives an overview of the attribute types and object classes that the ISO and ITU-T committees defined in the X.500 documents, especially the ones meant for directory clients 💜 [STANDARDS-TRACK]
2255 🔗 The LDAP URL Format
Author: Howes · Date: Dec 1997
last one in this batch and it's a clean finish 🍓 this document describes a format for an LDAP Uniform Resource Locator 🌈 bestie, that's the whole thing ✨
[STANDARDS-TRACK]
2254. The String Representation of LDAP Search Filters 💖
2254 Howes Dec 1997 The String Representation of
LDAP Search Filtersokay so this one gives LDAP search filters a human-readable string format, so you can actually read them without squinting 👀 [STANDARDS-TRACK] ✨
2253. Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names 🎀
2253 Wahl Dec 1997 Lightweight Directory Access
Protocol (v3): UTF-8 String
Representation of
Distinguished Namesthis spec gives names a string format that's super clean for the common distinguished names everyone uses, and it can still represent any distinguished name, which is so iconic 💅 [STANDARDS-TRACK]
2252. Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions 🦋
2252 Wahl Dec 1997 Lightweight Directory Access
Protocol (v3): Attribute
Syntax Definitionsbestie, this doc defines a set of syntaxes for LDAPv3, plus the rules for turning attribute values of those syntaxes into octet strings so they can travel over the LDAP protocol 🧚 [STANDARDS-TRACK]
2251. Lightweight Directory Access Protocol (v3) 🌸
2251 Wahl Dec 1997 Lightweight Directory Access
Protocol (v3)the protocol here is built to get you access to directories that follow the X.500 models, but without the heavy resource requirements of the X.500 Directory Access Protocol (DAP) 🍓 [STANDARDS-TRACK]
2250. RTP Payload Format for MPEG1/MPEG2 Video 🎬
2250 Hoffman Jan 1998 RTP Payload Format for
MPEG1/MPEG2 Videothis memo describes a packetization scheme for MPEG video and audio streams, and yes, it's giving video-streaming queen 👑 [STANDARDS-TRACK]
2249. Mail Monitoring MIB 📬
2249 Freed Jan 1998 Mail Monitoring MIBthis memo defines a chunk of the Management Information Base (MIB) for network management protocols in the Internet community. Specifically, it extends the basic Network Services Monitoring MIB [8] so you can monitor Message Transfer Agents (MTAs). It can also be used to monitor MTA components inside gateways 🔍 [STANDARDS-TRACK]
2248. Network Services Monitoring MIB 📊
2248 Freed Jan 1998 Network Services Monitoring MIBthis MIB can totally stand on its own for any application, and for most simple applications it'll be enough 💖 It's also designed as a building block you can pair with application-specific monitoring and management. [STANDARDS-TRACK]
2247. Using Domains in LDAP/X.500 Distinguished Names 🌈
2247 Kille Jan 1998 Using Domains in LDAP/X.500
Distinguished Namesthis doc defines an algorithm for turning a name registered with the Internet Domain Name Service [2] into an LDAP distinguished name. so cute, right? [STANDARDS-TRACK] 🫶
2246. The TLS Protocol Version 1.0 🔐
2246 Dierks Jan 1999 The TLS Protocol Version 1.0this one specifies Version 1.0 of the Transport Layer Security (TLS) protocol. TLS gives you communications privacy over the Internet, letting client/server apps talk in a way that's built to stop eavesdropping, tampering, and message forgery. literally the bodyguard of the internet 💅 [STANDARDS-TRACK]
2245. Anonymous SASL Mechanism 🙈
2245 Newman Nov 1997 Anonymous SASL Mechanismngl, plaintext login commands aren't allowed in new IETF protocols anymore, so we needed a fresh way to do anonymous login inside the SASL [SASL] framework ✨ [STANDARDS-TRACK]
2244. ACAP -- Application Configuration Access Protocol ⭐
2244 Newman Nov 1997 ACAP -- Application
Configuration Access ProtocolACAP is built to support remote storage and access of program options, configuration, and preference info. it's giving organised settings energy 🗂️ [STANDARDS-TRACK]
2243. OTP Extended Responses 🔑
2243 Metz Nov 1997 OTP Extended Responsesthis doc specifies a type of response to an OTP [RFC 1938] challenge that explicitly says how the response is encoded. it also specifies a response that lets an OTP generator ask a server to re-initialize a sequence and change parameters, like the secret pass phrase. main character energy 🎭 [STANDARDS-TRACK]
2242. NetWare/IP Domain Name and Information 🌐
2242 Droms Nov 1997 NetWare/IP Domain Name and
Informationthis doc defines options that carry the NetWare/IP domain name and NetWare/IP sub-options to DHCP clients 🧁 [STANDARDS-TRACK]
2241. DHCP Options for Novell Directory Services 💜
2241 Provan Nov 1997 DHCP Options for Novell
Directory Servicesthis doc defines three new DHCP options for delivering config info to clients of Novell Directory Services. (yes it says that twice, we're going to ignore the copy-paste situation and move on 🙃)
This document defines three new DHCP options for delivering configuration information to clients of the Novell Directory Services. [STANDARDS-TRACK] 🌸
2240. A Legal Basis for Domain Name Allocation ⚖️
2240 Vaughan Nov 1997 A Legal Basis for Domain Name
Allocationthe point of this memo is to get people talking about the real problems with the top level domain space running out, and the fights that break out when several organisations want the same name 😭 It's info for the Internet community, not an Internet standard of any kind.
2239. Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2 🔧
2239 de Graaf Nov 1997 Definitions of Managed Objects
for IEEE 802.3 Medium
Attachment Units (MAUs) using SMIv2this memo defines a portion of the MIB for network management protocols in the Internet community. It defines objects for managing 10 and 100 Mb/second Medium Attachment Units (MAUs), based on IEEE Std 802.3 Section 30, "10 & 100 Mb/s Management," October 26, 1995. [STANDARDS-TRACK] 🦋
2238. Definitions of Managed Objects for HPR using SMIv2 🛰️
2238 Clouston Nov 1997 Definitions of Managed Objects
for HPR using SMIv2this memo defines a portion of the MIB for network management protocols in the Internet community. It's all about objects for monitoring and controlling network devices with HPR (High Performance Routing) capabilities, and it identifies the managed objects for the HPR protocol. [STANDARDS-TRACK] 💫
2237. Japanese Character Encoding for Internet Messages 🇯🇵
2237 Tamaru Nov 1997 Japanese Character Encoding
for Internet Messagesthis memo defines an encoding scheme for Japanese characters and describes "ISO-2022-JP-1", which is used in electronic mail [RFC-822] and network news [RFC 1036]. It also lists the Japanese Character Set that can be used with this encoding scheme. it's info for the Internet community, and it does not specify an Internet standard of any kind. 🌺
2236. Internet Group Management Protocol, Version 2 👥
2236 Fenner Nov 1997 Internet Group Management
Protocol, Version 2this memo documents IGMPv2, which IP hosts use to report their multicast group memberships to routers. It updates STD 5, RFC 1112. [STANDARDS-TRACK] 💖
2235. Hobbes' Internet Timeline 🕰️
2235 Zakon Nov 1997 Hobbes' Internet Timelinethis document is a history of the Internet laid out as a timeline, hitting the key events and technologies that shaped the Internet as we know it today. a growth summary of the Internet and some related technologies is included too. This memo is info for the Internet community, and it does not specify an Internet standard of any kind. 📜
2234. Augmented BNF for Syntax Specifications: ABNF 🧩
2234 Crocker Nov 1997 Augmented BNF for Syntax
Specifications: ABNFback in the early Arpanet days, every spec had its own definition of ABNF, including the email specs RFC733 and then RFC822, which became the usual citations for it. this doc pulls that definition out on its own so you can reference it selectively. Predictably, it also adds some modifications and enhancements 🎀 [STANDARDS-TRACK]
2233. The Interfaces Group MIB using SMIv2 🔌
2233 McCloghrie Nov 1997 The Interfaces Group MIB using
SMIv2this memo defines a portion of the MIB for network management protocols in the Internet community. In particular, it describes the managed objects used for managing Network Interfaces. [STANDARDS-TRACK] 🫧
2232. Definitions of Managed Objects for DLUR using SMIv2 🧭
2232 Clouston Nov 1997 Definitions of Managed Objects
for DLUR using SMIv2this memo defines a portion of the MIB for network management protocols in the Internet community. It defines objects for monitoring and controlling network devices with DLUR (Dependent LU Requester) capabilities, and it identifies the managed objects for the DLUR protocol. [STANDARDS-TRACK] 🍭
2231. MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations 🌍
2231 Freed Nov 1997 MIME Parameter Value and
Encoded Word Extensions:
Character Sets, Languages, and
Continuationsthis memo extends the RFC 2045 media type and RFC 2183 disposition parameter value mechanisms. It also extends the encoded words from RFC 2047 so you can specify the language to be used for display, not just the character set. [STANDARDS-TRACK] 🌈
2230. Key Exchange Delegation Record for the DNS 🗝️
2230 Atkinson Nov 1997 Key Exchange Delegation Record
for the DNSthis note describes a mechanism where one node is authorised to act as key exchanger for a second node, and that delegation is made available through the Secure DNS. It's meant to be used only with the Secure DNS. It's info for the Internet community, and it does not specify an Internet standard of any kind. 💅
2229. A Dictionary Server Protocol 📖
2229 Faith Oct 1997 A Dictionary Server Protocolthe Dictionary Server Protocol (DICT) is a TCP transaction based query/response protocol. It lets a client pull dictionary definitions from a set of natural language dictionary databases. It's info for the Internet community, and it does not specify an Internet standard of any kind. 🧠
2228. FTP Security Extensions 🔒
2228 Horowitz Oct 1997 FTP Security Extensionsthis document defines extensions to the FTP specification, STD 9, RFC 959, "FILE TRANSFER PROTOCOL (FTP)" (October 1985). [STANDARDS-TRACK] 🛡️
2227. Simple Hit-Metering and Usage-Limiting for HTTP 📏
2227 Mogul Oct 1997 Simple Hit-Metering and
Usage-Limiting for HTTPthis document proposes a simple extension to HTTP that uses a new "Meter" header. [STANDARDS-TRACK] 🎈
2226. IP Broadcast over ATM Networks 📡
2226 Smith Oct 1997 IP Broadcast over ATM Networksthis memo describes how the IP multicast service being developed by the IP over ATM working group can be used to support IP broadcast transmission. [STANDARDS-TRACK] 🌟
2225. Classical IP and ARP over ATM 🔗
2225 Laubach Apr 1998 Classical IP and ARP over ATMthis memo defines an initial application of classical IP and ARP in an Asynchronous Transfer Mode (ATM) network environment configured as a Logical IP Subnetwork (LIS). [STANDARDS-TRACK] 🧚
2224. NFS URL Scheme 🗃️
2224 Callaghan Oct 1997 NFS URL Schemea new URL scheme, 'nfs', is defined. It's used to refer to files and directories on NFS servers using the general URL syntax defined in RFC 1738, "Uniform Resource Locators (URL)". It's info for the Internet community, and it does not specify an Internet standard of any kind. 🍓
2223. Instructions to RFC Authors ✍️
2223 Postel Oct 1997 Instructions to RFC Authorsokay so this RFC gives info about how to prepare RFCs, plus the policies for getting them published. It's info for the Internet community. This RFC
so yeah, this memo does not specify an Internet standard of any kind 💅 it's just here to give you the lowdown. 🎀
2222. Simple Authentication and Security Layer (SASL) 🔐
2222 Myers Oct 1997 Simple Authentication and
Security Layer (SASL)Okay bestie, SASL is basically a way to bolt authentication onto connection-based protocols. It's giving "add a lock to any door" energy 🔒 [STANDARDS-TRACK] ✨
2221. IMAP4 Login Referrals 🦋
2221 Gahrns Oct 1997 IMAP4 Login ReferralsSo when you've got loads of users and tons of IMAP4 [RFC-2060] servers, you sometimes have to move people from one server to another. Login referrals let clients quietly hop over to a new IMAP4 server when their home server changes, no drama 🫶 [STANDARDS-TRACK]
2220. The Application/MARC Content-type 📚
2220 Guenther Oct 1997 The Application/MARC Content-
typeThis one is a mechanism for representing objects that are files of Machine-Readable Cataloging records (MARC). MARC formats are the standards for representing and communicating bibliographic info, and a MARC record holds metadata for a resource that follows those formats 🧚 It's just here to inform everyone. It's not a standard, babe 🌸
2219. Use of DNS Aliases for Network Services 🌐
2219 Hamilton Oct 1997 Use of DNS Aliases for Network
ServicesEveryone's been using symbolic names (usually CNAMEs) in DNS ([RFC-1034, RFC-1035]) for services like anonymous FTP [RFC-959] servers, Gopher [RFC-1436] servers, and most notably World-Wide Web HTTP [RFC-1945] servers, and it's iconic 💅 It lets you move a service between machines without anyone noticing, and lets people or agents find out that an org runs, say, a web server. The catch is there was never an actual standards doc for these names, so this one gathers up all the unwritten "folklore" about naming conventions and suggests a way to handle new protocols. It's a Best Current Practice, and it's asking for your feedback on how to make it better 🍓
2218. A Common Schema for the Internet White Pages Service 📇
2218 Genovese Oct 1997 A Common Schema for the
Internet White Pages ServiceThis one nails down the minimum set of core attributes for a White Pages entry about an individual, and explains how brand-new objects with those attributes can be defined and published 📝 [STANDARDS-TRACK]
2217. Telnet Com Port Control Option 📞
2217 Clark Oct 1997 Telnet Com Port Control OptionThis memo proposes a protocol so that modems hooked up to a network can get used a lot more for outbound dialing 🙈 It defines an Experimental Protocol for the Internet community.
2216. Network Element Service Specification Template 🧩
2216 Shenker Sep 1997 Network Element Service
Specification TemplateThis doc sets up a framework for describing the services that network elements provide to applications, in an internetwork with multiple qualities of service. It starts with the context you need, like definitions and suggested data formats, then lays out a "template" that service spec documents should follow 📋 It's informational, not a standard of any kind 🫶
2215. General Characterization Parameters for Integrated Service Network Elements ⚙️
2215 Shenker Sep 1997 General Characterization
Parameters for Integrated
Service Network ElementsThis one defines a set of general control and characterization parameters for network elements that support the IETF integrated services QoS control framework. It's giving structure 💜 [STANDARDS-TRACK]
2214. Integrated Services Management Information Base Guaranteed Service Extensions using SMIv2 📊
2214 Baker Sep 1997 Integrated Services Management
Information Base Guaranteed
Service Extensions using SMIv2This memo defines a piece of the Management Information Base (MIB) for network management protocols in TCP/IP-based internets. Specifically, it defines objects for managing the interface attributes from the Guaranteed Service of the Integrated Services Model 📈 [STANDARDS-TRACK]
2213. Integrated Services Management Information Base using SMIv2 📊
2213 Baker Sep 1997 Integrated Services Management
Information Base using SMIv2Same vibe as 2214, but this time it's for the interface attributes in the Integrated Services Model in general, not just Guaranteed Service 💖 It's a MIB section for network management in TCP/IP-based internets. [STANDARDS-TRACK]
2212. Specification of Guaranteed Quality of Service 🏆
2212 Shenker Sep 1997 Specification of Guaranteed
Quality of ServiceThis memo describes the network element behavior you need to deliver a guaranteed service (guaranteed delay and bandwidth) on the Internet. The reliability is unmatched fr fr 👑 [STANDARDS-TRACK]
2211. Specification of the Controlled-Load Network Element Service 🎚️
2211 Wroclawski Sep 1997 Specification of the
Controlled-Load Network
Element ServiceThis one specifies the network element behavior required to deliver Controlled-Load service on the Internet ✨ [STANDARDS-TRACK]
2210. The Use of RSVP with IETF Integrated Services 🎀
2210 Wroclawski Sep 1997 The Use of RSVP with IETF
Integrated ServicesThis note walks through how to use the RSVP resource reservation protocol with the Controlled-Load and Guaranteed QoS control services 💅 [STANDARDS-TRACK]
2209. Resource ReSerVation Protocol (RSVP) Version 1 Message Processing Rules 🧠
2209 Braden Sep 1997 Resource ReSerVation Protocol
(RSVP) -- Version 1 Message
Processing RulesThis memo is an algorithmic breakdown of the rules an RSVP implementation uses to process messages. It's meant to clarify the version 1 RSVP protocol spec, so it's basically a study guide 📖 It's informational, not a standard of any kind.
2208. RSVP Version 1 Applicability Statement: Some Guidelines on Deployment 🚀
2208 Mankin Sep 1997 Resource ReSerVation Protocol
(RSVP) Version 1 Applicability
Statement Some Guidelines on
DeploymentThis document covers where RSVP fits alongside the Integrated Services protocols and other pieces of resource reservation, and it gives guidelines for deploying resource reservation at this time 🗺️ It's informational, and it doesn't specify an Internet standard of any kind.
2207. RSVP Extensions for IPSEC Data Flows 🔏
2207 Berger Sep 1997 RSVP Extensions for IPSEC Data
FlowsThis document adds extensions to Version 1 of RSVP. They let you support individual data flows using RFC 1826, IP Authentication Header (AH) or RFC 1827, IP Encapsulating Security Payload (ESP) 🛡️ [STANDARDS-TRACK]
2206. RSVP Management Information 🗂️
2206 Baker Sep 1997 RSVP Management Information
This memo defines a portion ofThis memo defines a chunk of the MIB for network management protocols in TCP/IP-based internets. It's all about managing RSVP inside the interface attributes of the Integrated Services Model 🧁 [STANDARDS-TRACK]
2205. Resource ReSerVation Protocol (RSVP) Version 1 Functional Specification 💫
2205 Braden Sep 1997 Resource ReSerVation Protocol
(RSVP)--Version 1 Functional
SpecificationThis memo describes version 1 of RSVP, a resource reservation setup protocol designed for an integrated services Internet. RSVP does receiver-initiated setup of resource reservations for multicast or unicast data flows, and it's known for good scaling and robustness 🔥 [STANDARDS-TRACK]
2204. ODETTE File Transfer Protocol 📦
2204 Nash Sep 1997 ODETTE File Transfer ProtocolThis memo describes a file transfer protocol that helps trading partners do electronic data interchange. It's informational, and it doesn't specify an Internet standard of any kind 💼
2203. RPCSEC_GSS Protocol Specification 🔑
2203 Eisler Sep 1997 RPCSEC_GSS Protocol SpecificationThis memo describes an ONC/RPC security flavor that lets RPC protocols access the Generic Security Services Application Programming Interface (called GSS-API from here on out) 🥰 [STANDARDS-TRACK]
2202. Test Cases for HMAC-MD5 and HMAC-SHA-1 🧪
2202 Cheng Sep 1997 Test Cases for HMAC-MD5 and
HMAC-SHA-1This document gives two sets of test cases, one for HMAC-MD5 and one for HMAC-SHA-1. Both are constructs of the HMAC [HMAC] message authentication function, using the MD5 [MD5] and SHA-1 [SHA] hash functions 🧪 It's informational and does not specify an Internet standard of any kind.
2201. Core Based Trees (CBT) Multicast Routing Architecture 🌳
2201 Ballardie Sep 1997 Core Based Trees (CBT)
Multicast Routing ArchitectureCBT builds a single delivery tree per group, and all of that group's senders and receivers share it 🌲 It defines an Experimental Protocol for the Internet community.
2200. Internet Official Protocol Standards 👑
2200 IAB Jun 1997 INTERNET OFFICIAL PROTOCOL
STANDARDSThis is the one that tells you where everything stands 🗺️ It starts with a discussion of the standardization process and the RFC document series, then explains the terms. Sections 6.2 - 6.10 contain the lists of protocols at each stage of standardization. The end has pointers to references and contacts for more info 📚 [STANDARDS-TRACK]
Security Considerations 🔒
Okay, the security section is short and sweet: there are no security issues in this Informational RFC 🫶
Author's Address 📮
Alegre Ramos
University of Southern California
Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292
Phone: (310) 822-1511
EMail: ramos@isi.eduFull Copyright Statement ©
Here's the legal stuff, kept word for word so it stays legit 💖
Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.📦 where this page comes from
- ietf: rfc2299 1999-01
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms