RFC 2599
Request for Comments Summary RFC Numbers 2500-2599
RFC 2599: Request for Comments Summary ✨
Okay bestie, RFC 2599 is basically the table of contents for a whole batch of RFCs 💖 It's titled Request for Comments Summary and covers RFC Numbers 2500-2599. It was written by A. DeLaCruz at ISI, it's in the Informational category, and it's dated March 2000 📅 The header doesn't list anything it obsoletes or updates, so it's a pure status report, no drama 🌸
Status of This Memo 🌸
This RFC is a slightly annotated list of the 100 RFCs from RFC 2500 through RFC 2599, so it's a status report on all of them ✨ It provides information for the Internet community 🦋 It does not specify an Internet standard of any kind, so don't go looking for a spec in here 🙈 Distribution of this memo is unlimited, so share it with everyone 💅
Copyright Notice 🎀
Copyright (C) The Internet Society (2000). All Rights Reserved. 💜
Note 🦋
Okay so, many RFCs are Proposed Standards, Draft Standards, or Standards, but not all of them are 🌈 The status can change during standards processing, so this document only says whether they're on the standards track. For the current status, check the latest edition of "Internet Official Protocol Standards" 📚 In the list below, RFCs on the standards track are marked [STANDARDS-TRACK] 🏷️
The Listing 📋
Here's how the columns line up, iykyk 😭
RFC Author Date Title
--- ------ ---- -----2599 · Delacruz · Mar 2000 · Request for Comments Summary 🎀 This memo. Yes, this is the summary describing itself, very meta 🪞
2598 · Jacobson · Jun 1999 · An Expedited Forwarding PHB 🚀 The definition of PHBs (per-hop forwarding behaviors) is a critical part of the work of the Diffserv Working Group 👑 This doc describes a PHB called Expedited Forwarding. [STANDARDS-TRACK] 🔥
2597 · Heinanen · Jun 1999 · Assured Forwarding PHB Group 💖 This doc defines a general use Differentiated Services (DS) Per-Hop-Behavior (PHB) Group called Assured Forwarding (AF). [STANDARDS-TRACK] ✨
2596 · Wahl · May 1999 · Use of Language Codes in LDAP 🌸 This one describes how language codes get carried in LDAP and how LDAP servers are supposed to interpret them. [STANDARDS-TRACK] 🧚
2595 · Newman · Jun 1999 · Using TLS with IMAP, POP3 and ACAP 🔐 Sites are going to want simple password authentication alongside TLS encryption, so this spec defines the PLAIN SASL mechanism for protocols that don't have a simple password authentication command, like ACAP and SMTP. [STANDARDS-TRACK] 💅
2594 · Hazewinkel · May 1999 · Definitions of Managed Objects for WWW Services 🕸️ This memo defines a chunk of the Management Information Base (MIB) for network management protocols in the Internet Community. Specifically, it describes a set of objects for managing World Wide Web (WWW) services. [STANDARDS-TRACK] 🎀
2593 · Schoenwaelder · May 1999 · Script MIB Extensibility Protocol Version 1.0 🦋 The Script MIB extensibility protocol (SMX) separates language specific runtime systems from language independent Script MIB implementations, which is giving modular energy 🧩 This memo defines an Experimental Protocol for the Internet community. 🧪
2592 · Levi · May 1999 · Definitions of Managed Objects for the Delegation of Management Scripts 🌈 This is another MIB portion for network management protocols. It lets you delegate management scripts to distributed managers, which is so iconic ✨ [STANDARDS-TRACK]
2591 · Levi · May 1999 · Definitions of Managed Objects for Scheduling Management Operations ⏰ A MIB for scheduling management operations, for the Internet community. [STANDARDS-TRACK] 🗓️
2590 · Conta · May 1999 · Transmission of IPv6 Packets over Frame Relay Networks Specification 🌐 This memo describes mechanisms for sending IPv6 packets over Frame Relay networks. [STANDARDS-TRACK] 💜
2589 · Yaacovi · May 1999 · Lightweight Directory Access Protocol (v3): Extensions for Dynamic Directory Services 📇 This document sets out the requirements for dynamic directory services, and specifies the format of request and response extended operations so clients and servers can interoperate in a dynamic directories environment. [STANDARDS-TRACK] 🫶
2588 · Finlayson · May 1999 · IP Multicast and Firewalls 🔥 We talk through the drama of IP multicast traffic crossing a firewall, and describe ways a firewall can implement and control that crossing 🧱 We also explain why firewall mechanisms like SOCKS, which were built specifically for unicast traffic, are less appropriate for multicast 🙅♀️ This memo provides information for the Internet community.
2587 · Boeyen · Jun 1999 · Internet X.509 Public Key Infrastructure LDAPv2 Schema 🔑 This schema is a minimal one for supporting PKIX in an LDAPv2 environment, as defined in RFC 2559. Only PKIX-specific components are specified here. [STANDARDS-TRACK] 🎀
2586 · Salsman · May 1999 · The Audio/L16 MIME content type 🎧 This document defines the audio/L16 MIME type, a reasonably high quality audio format for Internet applications 🎶 This memo provides information for the Internet community.
2585 · Housley · May 1999 · Internet X.509 Public Key Infrastructure Operational Protocols: FTP and HTTP 🗝️ The protocol conventions in this document cover some of the operational requirements of the Internet Public Key Infrastructure (PKI) ✨ Specifically, they explain how to use the File Transfer Protocol (FTP) and the Hypertext Transfer Protocol (HTTP) to fetch certificates and certificate revocation lists (CRLs) from PKI repositories. [STANDARDS-TRACK] 🫶
2584 · Clouston · May 1999 · Definitions of Managed Objects for APPN/HPR in IP Networks 🛰️ Another MIB portion for the Internet community. It defines objects for monitoring and controlling HPR (High Performance Routing) network devices that can communicate in IP (Internet Protocol) networks. [STANDARDS-TRACK] 💅
2583 · Carlson · May 1999 · Guidelines for Next Hop Client (NHC) Developers 🧑💻 This document gives guidelines for developers of the Next Hop Resolution Protocol Clients (NHC). The goal is to define how the NHC code interacts with the TCP/IP protocol stack of the local host operating system 🧠 This memo provides information for the Internet community.
2582 · Floyd · Apr 1999 · The NewReno Modification to TCP's Fast Recovery Algorithm 🌊 This doc describes a specific algorithm for responding to partial acknowledgments, called NewReno 🦋 This memo defines an Experimental Protocol for the Internet community. 🧪
2581 · Allman · Apr 1999 · TCP Congestion Control 🚦 This one defines TCP's four intertwined congestion control algorithms: slow start, congestion avoidance, fast retransmit, and fast recovery 😭 It also specifies how TCP should begin transmitting after a relatively long idle period, and discusses various acknowledgment generation methods. [STANDARDS-TRACK] 🔥
2580 · McCloghrie · Apr 1999 · Conformance Statements for SMIv2 📏 Related objects get defined in MIB modules, and it can be useful to define the acceptable lower bounds of implementation, along with the level of implementation actually achieved. This document defines the notation used for those purposes. [STANDARDS-TRACK] 🎀
2579 · McCloghrie · Apr 1999 · Textual Conventions for SMIv2 📝 This document defines the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK] ✨
2578 · McCloghrie · Apr 1999 · Structure of Management Information Version 2 (SMIv2) 🏗️ This document defines the Structure of Management Information Version 2 (SMIv2), which is that adapted subset, and it assigns a set of associated administrative values to go with it. [STANDARDS-TRACK] 👑
2577 · Allman · May 1999 · FTP Security Considerations 🔐 This doc gives suggestions for system administrators and people implementing FTP servers, to decrease the security problems associated with FTP. Please read it, it's serious 🚨 This memo provides information for the Internet community.
2576 · Frye · March 2000 · Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework 🤝 This document describes how version 3 of the Internet-standard Network Management Framework (SNMPv3), version 2 (SNMPv2), and the original version 1 (SNMPv1) all coexist 🌈 [STANDARDS TRACK]
2575 · Wijnen · Apr 1999 · View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) 🚪 This document describes the View-based Access Control Model for use in the SNMP architecture (RFC2571). It defines the Elements of Procedure for controlling access to management information 🔒 It also includes a MIB for remotely managing the configuration parameters for VACM. [STANDARDS-TRACK] 💖
2574 · Blumenthal · Apr 1999 · User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) 🛡️ This document describes the User-based Security Model (USM) for SNMP version 3, for use in the SNMP architecture. It defines the Elements of Procedure 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] ✨
2573 · Levi · Apr 1999 · SNMP Applications 📡 This memo describes five types of SNMP applications that make use of an SNMP engine 🧩 It also defines MIB modules for specifying targets of management operations, for notification filtering, and for proxy forwarding. [STANDARDS-TRACK] 🎀
2572 · Case · May 1999 · Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) 📬 This document describes the Message Processing and Dispatching for SNMP messages within the SNMP architecture 🚚 It defines the procedures for dispatching potentially multiple versions of SNMP messages to the proper SNMP Message Processing Models, and for dispatching PDUs to SNMP applications. It also describes one Message Processing Model, the SNMPv3 Message Processing Model. 💜
Quick heads-up, bestie: the text you pasted is actually the RFC index listing for RFCs 2545 through 2571, not RFC 2599 itself. The SNMP summaries in your message aren't in it either, so I rewrote what's here. If you send the RFC 2599 text, I'll pick up from there. 💖
RFC 2571
2571 Harrington May 1999 An Architecture for Describing
SNMP Management FrameworksOkay so this one describes an architecture for describing SNMP Management Frameworks 🏗️✨ [STANDARDS-TRACK]
RFC 2570
2570 Case Apr 1999 Introduction to Version 3
of the Internet-standard
Network Management FrameworkThis is your overview of the third version of the Internet-standard Management Framework, which everyone calls the SNMP version 3 Framework (SNMPv3) 🧚. It's just info for the Internet community, no pressure lol 💅
RFC 2569
2569 Herriot Apr 1999 Mapping between LPD and IPP
ProtocolsThis is one of a bunch of docs that together cover every bit of the new Internet Printing Protocol (IPP) 🖨️. This one compares what the two protocols can do, and it also helps people build gateways between LPD and IPP 🌉. It defines an Experimental Protocol for the Internet community 🧪
RFC 2568
2568 Zilles Apr 1999 Rationale for the Structure of
the Model and Protocol for the
Internet Printing ProtocolThis doc is the high-level tour of IPP 🗺️. It gives you a roadmap for the whole IPP spec suite and explains why the IETF working group made its big calls. It defines an Experimental Protocol for the Internet community ✨
RFC 2567
2567 Wright Apr 1999 Design Goals for an Internet
Printing ProtocolThis one takes a big-picture look at distributed printing 🌍. It walks through real-life scenarios to show which features a printing protocol needs for the Internet, and it lays out requirements for three types of users: end users, operators, and administrators 👑. It defines an Experimental Protocol for the Internet community 🧪
RFC 2566
2566 deBry Apr 1999 Internet Printing
Protocol/1.0: Model and
SemanticsThis doc gives you a simplified model made of abstract objects, their attributes, and their operations 🧩. The best part is it doesn't care about encoding or transport, so it's independent of both. It also covers security, internationalization, and directory issues 🔐. It defines an Experimental Protocol for the Internet community 🧪
RFC 2565
2565 Herriot Apr 1999 Internet Printing
Protocol/1.0: Encoding and
TransportHere's the encoding rulebook 📦. It explains how to turn IPP operations and IPP attributes into a new Internet MIME media type called "application/ipp" 💌. It also sets the rules for sending a message body whose Content-Type is "application/ipp" over HTTP 🌸. It defines an Experimental protocol for the Internet community 🧪
RFC 2564
2564 Kalbfleisch May 1999 Application Management MIBThis memo defines a standards-track part of the Management Information Base (MIB) for network management protocols in the Internet community 📚. It's all about objects for managing applications 🎀 [STANDARDS-TRACK]
RFC 2563
2563 Troll May 1999 DHCP Option to Disable
Stateless Auto-Configuration in
IPv4 ClientsThis one is a DHCP mechanism that lets servers tell clients they have no IP address to offer, so the client shouldn't make up an IP address of its own 🙅♀️. [STANDARDS-TRACK]
RFC 2562
2562 White Apr 1999 Definitions of Protocol and
Managed Objects for TN3270E
Response Time Collection Using
SMIv2 (TN3270E-RT-MIB)This memo defines the protocol and the MIB for collecting response time data on TN3270 and TN3270E sessions, done by a TN3270E server ⏱️. [STANDARDS-TRACK]
RFC 2561
2561 White Apr 1999 Base Definitions of Managed
Objects for TN3270E Using SMIv2This memo defines a MIB for configuring and managing TN3270E servers 🖥️. The MIB gives generic support for both host and gateway TN3270E server implementations 💜 [STANDARDS-TRACK]
RFC 2560
2560 Myers Jun 1999 X.509 Internet Public Key
Infrastructure Online
Certificate Status
Protocol - OCSPThis doc specifies a protocol for checking the current status of a digital certificate, and it does that without needing CRLs 🔍 [STANDARDS-TRACK]
RFC 2559
2559 Boeyen Apr 1999 Internet X.509 Public Key
Infrastructure Operational
Protocols - LDAPv2Specifically, this one covers getting access to Public Key Infrastructure (PKI) repositories 🗝️. You can use that access to retrieve PKI information and to manage that same information 📂 [STANDARDS-TRACK]
RFC 2558
2558 Tesink Mar 1999 Definitions of Managed Objects
for the SONET/SDH Interface TypeThis memo defines a piece of the MIB for TCP/IP-based internets 🌐. It's specifically about objects for managing SONET/SDH interfaces 🔌. This doc is a companion to the documents that define Managed Objects for the DS1/E1/DS2/E2 and DS3/E3 Interface Types 💫 [STANDARDS-TRACK]
RFC 2557
2557 Palme Mar 1999 MIME Encapsulation of
Aggregate Documents, such
as HTML (MHTML)This doc does two things, a) and b) 🎀. First, it defines using a MIME multipart/related structure to bundle a text/html root resource together with the subsidiary resources it references. Second, it specifies a MIME content-header (Content-Location) so that URIs in a multipart/related text/html root body part can point to subsidiary resources in other body parts of that same multipart/related structure 🧩 [STANDARDS-TRACK]
RFC 2556
2556 Bradner Mar 1999 OSI connectionless transport
services on top of UDP
Applicability Statement for
Historic StatusOkay, so RFC 1240, "OSI connectionless transport services on top of UDP", was a Proposed Standard back in June 1991 🕰️. At this point there don't seem to be any implementations that follow RFC 1240 🙈. There's also growing concern about using UDP-based transport protocols in environments where congestion is possible 🚦. This memo provides information for the Internet community.
RFC 2555
2555 RFC Editor Apr 1999 30 Years of RFCsThis one is a little trip down memory lane 🥹. It starts with a short recollection from the RFC Editor at the time, Joyce K. Reynolds, and then hears from three pioneers: Steve Crocker, who wrote RFC 1; Vint Cerf, whose long-range vision still guides us; and Jake Feinler, who played a key role in the middle years of the RFC series 🌈. This memo provides information for the Internet community.
RFC 2554
2554 Myers Mar 1999 SMTP Service ExtensionThis doc defines an SMTP service extension [ESMTP] 📧. With it, an SMTP client can tell the server which authentication mechanism it wants, run an authentication protocol exchange, and optionally negotiate a security layer for later protocol interactions 🔒 [STANDARDS-TRACK]
RFC 2553
2553 Gilligan Mar 1999 Basic Socket Interface
Extensions for IPv6TCP/IP apps written with the sockets API have always been super portable, and we want that same portability for IPv6 apps 🌍. Changes to the sockets API are needed for IPv6 support, and this memo describes them 🛠️. They include a new socket address structure to carry IPv6 addresses, new address conversion functions, and some new socket options ✨. This memo provides information for the Internet community.
RFC 2552
2552 Blinov Apr 1999 Architecture for Information
Brokerage in the ACTS Project
GAIAThis memo introduces a generic architecture for information brokerage that doesn't depend on any particular domain or supplier 🦋. It was designed as part of the ACTS project GAIA (Generic Architecture for Information Availability) 💜. This memo provides information for the Internet community.
RFC 2551
2551 Bradner 1 Apr 1999 The Roman Standards Process --
Revision IIIThis memo documents the process the Roman community uses to standardize protocols and procedures 🏛️. It lays out the stages of standardization, what a document needs to move between stages, and the types of documents used along the way 📜. It also covers the intellectual property rights and copyright issues tied to the standards process ⚖️.
RFC 2550
2550 Glassman 1 Apr 1999 Y10K and BeyondThis spec offers a solution to the "Y10K" problem, which people also call the "YAK" problem (hex) and the "YXK" problem (Roman numerals) 😭💀. This memo provides information for the Internet community.
RFC 2549
2549 Waitzman 1 Apr 1999 IP over Avian Carriers with
Quality of ServiceThis memo amends RFC 1149, "A Standard for the Transmission of IP Datagrams on Avian Carriers", by adding Quality of Service information 🐦. It's an experimental, not recommended standard 🙈. This memo defines an Experimental Protocol for the Internet community.
RFC 2548
2548 Zorn Mar 1999 Microsoft Vendor-specific
RADIUS AttributesThis doc describes the set of Microsoft vendor-specific RADIUS attributes 🪟. This memo provides information for the Internet community.
RFC 2547
2547 Rosen Mar 1999 BGP/MPLS VPNsThis doc describes a method that lets a Service Provider with an IP backbone offer VPNs (Virtual Private Networks) to its customers 🔐🌐. This memo provides information for the Internet community.
RFC 2546
2546 Durand Mar 1999 6Bone Routing PracticeThis memo gives guidelines on how 6Bone sites might operate 🧭. The goal is to keep the 6Bone a quality experimentation environment and to avoid the pathological situations seen in the past 💅. It defines the 'best current practice' acceptable in the 6Bone for configuring both Interior Gateway Protocols and Exterior Gateway Protocols 🌸. This memo provides information for the Internet community.
RFC 2545
2545 Marques Mar 1999 Use of BGP-4 Multiprotocol
Extensions for IPv6
Inter-Domain RoutingBGP-4 Multiprotocol Extensions (BGP-MP) defines the format of two BGP attributes, MP_REACH_NLRI and MP_UNREACH_NLRI 🛣️. Those can be used to announce reachability information and to withdraw that announcement 📣. This doc explains how compliant systems should use those attributes to carry IPv6 routing information 💖.
2544 Benchmarking Methodology for Network Interconnect Devices (Bradner, Mar 1999) 🧪 okay so this one is a republication of RFC 1944, but it fixes the IP addresses that were picked as the defaults for networking test equipment. Super important detail, bestie. This memo provides information for the Internet community. 🎀
2543 SIP: Session Initiation Protocol (Handley, Mar 1999) 📞 The Session Initiation Protocol is an application-layer control (signaling) protocol that's literally the boss of creating, modifying, and terminating sessions with one or more participants. Iconic. [STANDARDS-TRACK] 👑
2542 Terminology and Goals for Internet Fax (Masinter, Mar 1999) 📠 This one defines a bunch of terms you need for talking about Internet Fax. It also lays out the goals of the Internet Fax working group and sets a baseline of desired functionality that Internet Fax protocols can be judged against. This memo provides information for the Internet community. 💅
2541 DNS Security Operational Consideration (Eastlake, Mar 1999) 🔐 This document talks through the operational side of keys and signatures used with the KEY and SIG DNS resource records. It's giving operations manual energy. This memo provides information for the Internet community. ✨
2540 Detached Domain Name System (DNS) Information (Eastlake, Mar 1999) 🗃️ A standard format is defined for representing detached DNS information. This is expected to be useful for storing info pulled from the Domain Name System (DNS), security info included, in archives or in places that aren't connected to the Internet. This memo defines an Experimental Protocol for the Internet community. 🧪
2539 Storage of Diffie-Hellman Keys in the Domain Name System (DNS) (Eastlake, Mar 1999) 🔑 This describes a standard way to store Diffie-Hellman keys in the DNS using DNS KEY resource records. [STANDARDS-TRACK] 🫶
2538 Storing Certificates in the Domain Name System (DNS) (Eastlake, Mar 1999) 📜 Public keys get published a lot, and their authenticity gets shown with certificates. So this defines a CERT resource record (RR), which means certificates and their related certificate revocation lists can live in the DNS. [STANDARDS-TRACK] 🌸
2537 RSA/MD5 KEYs and SIGs in the Domain Name System (DNS) (Eastlake, Mar 1999) 🦋 This is a standard way to store RSA keys and RSA/MD5 based signatures in the DNS, using DNS KEY and SIG resource records. [STANDARDS-TRACK] 💜
2536 DSA KEYs and SIGs in the Domain Name System (DNS) (Eastlake, Mar 1999) 🌈 This is a standard way to store US Government Digital Signature Algorithm keys and signatures in the DNS, using DNS KEY and SIG resource records. [STANDARDS-TRACK] ⭐
2535 Domain Name System Security Extensions (Eastlake, Mar 1999) 🛡️ This document takes in feedback on RFC 2065 from early implementers and potential users. [STANDARDS-TRACK] 🔥
2534 Media Features for Display, Print, and Fax (Masinter, Mar 1999) 🖨️ This spec defines some common media features for describing image resolution, size, color, and image representation methods. They're shared across web browsing, printing, and fax apps, so it's a whole vibe. [STANDARDS-TRACK] 🍓
2533 A Syntax for Describing Media Feature Sets (Klyne, Mar 1999) 🧩 This introduces a syntax for defining feature sets built from combinations and relations of individual media features. [STANDARDS-TRACK] ✨
2532 Extended Facsimile Using Internet Mail (Masinter, Mar 1999) 📬 This extends "Simple Mode of Facsimile Using Internet Mail" with more features, like sending enhanced document characteristics (higher resolution, color) and confirming delivery and processing. [STANDARDS-TRACK] 🎀
2531 Content Feature Schema for Internet Fax (Klyne, Mar 1999) 🗂️ This defines a content feature schema, which is a profile of the media feature registration mechanisms. It's used for capability identification between extended Internet fax systems. [STANDARDS-TRACK] 💖
2530 Indicating Supported Media Features Using Extensions to DSN and MDN (Wing, Mar 1999) 🔔 This memo describes a format for Message Disposition Notifications and Delivery Status Notifications that carry that kind of supported-features info. [STANDARDS-TRACK] 🫶
2529 Transmission of IPv6 over IPv4 Domains without Explicit Tunnels (Carpenter, Mar 1999) 🚀 Okay this one is a big deal. It specifies the frame format for sending IPv6 packets and how to form IPv6 link-local addresses over IPv4 domains. It also says what goes in the Source/Target Link-layer Address option used in Router Solicitation, Router Advertisement, Neighbor Solicitation, Neighbor Advertisement, and Redirect messages, when those get sent over an IPv4 multicast network. [STANDARDS-TRACK] 😭
2528 Internet X.509 Public Key Infrastructure (Housley, Mar 1999) 🔏 This spec gives guidance on using Internet Public Key Infrastructure certificates to convey Key Exchange Algorithm (KEA) keys. This memo provides information for the Internet community. 🌟
2527 Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework (Chokhani, Mar 1999) 📋 This is a framework that helps writers of certificate policies or certification practice statements for certification authorities and public key infrastructures. It gives a big checklist of topics that might (the writer decides) need covering in a certificate policy or certification practice statement. This memo provides information for the Internet community. 💅
2526 Reserved IPv6 Subnet Anycast Addresses (Johnson, Mar 1999) 📍 This defines a set of reserved anycast addresses within each subnet prefix, and lists the initial allocation of those reserved subnet anycast addresses. [STANDARDS-TRACK] 🦋
2525 Known TCP Implementation Problems (Paxson, Mar 1999) 🐛 This memo catalogs a bunch of known TCP implementation problems. Iykyk, and now you'll know them too. This memo provides information for the Internet community. 🙈
2524 Neda's Efficient Mail Submission and Delivery (EMSD) Protocol Specification Version 1.3 (Banan, Feb 1999) 📨 This spec focuses narrowly on submitting and delivering short mail messages, with a clear emphasis on efficiency. This memo provides information for the Internet community. 🍓
2523 Photuris: Extended Schemes and Attributes (Karn, Mar 1999) 🔑 Photuris is a session-key management protocol. Extensible Exchange-Schemes let future implementation changes happen without messing with the basic protocol. This document defines an Experimental Protocol for the Internet community. 🧪
2522 Photuris: Session-Key Management Protocol (Karn, Mar 1999) 🗝️ This document defines the basic protocol mechanisms. This document defines an Experimental Protocol for the Internet community. 🧚
2521 ICMP Security Failures Messages (Karn, Mar 1999) 🚨 This spec defines ICMP messages for indicating failures when using IP Security Protocols (AH and ESP). This document defines an Experimental Protocol for the Internet community. 💀
2520 NHRP with Mobile NHCs (Luciani, Feb 1999) 📡 The document describes an extension to NHRP that lets Mobile NHCs register with and attach to an NHS in their home LIS in an authenticated way. This memo defines an Experimental Protocol for the Internet community. 🔐
2519 A Framework for Inter-Domain Route Aggregation (Chen, Feb 1999) 🗺️ This presents a framework for inter-domain route aggregation, plus an example router configuration that "implements" the framework. This memo provides information for the Internet community. ✨
2518 HTTP Extensions for Distributed Authoring -- WEBDA (Goland, Feb 1999) 🌐 This spec defines a set of methods, headers, and content-types that go alongside HTTP/1.1. They handle resource property management, resource collection creation and management, namespace manipulation, and resource locking (collision avoidance). [STANDARDS-TRACK] 💜
2517 Building Directories from DNS: Experiences from WWWSeeker (Moats, Feb 1999) 📚 This memo shares lessons learned during InterNIC Directory and Database Services' development and operation of WWWSeeker, an app that finds a web site when you give it info about an organization's name and location. This memo provides information for the Internet community. 🫶
2516 A Method for Transmitting PPP Over Ethernet (PPPoE) (Mamakos, Feb 1999) 🔌 This describes how to build PPP sessions and encapsulate PPP packets over Ethernet. This memo provides information for the Internet community. 🌸
2515 Definitions of Managed Objects for ATM Management (Tesink, Feb 1999) 📊 This defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. It especially covers objects used for managing ATM-based interfaces, devices, networks, and services. [STANDARDS-TRACK] 👑
2514 Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM MEanagement (Noto, Feb 1999) 🏷️ This memo describes the Textual Conventions and OBJECT-IDENTITIES used for managing ATM-based interfaces, devices, networks, and services. [STANDARDS-TRACK] 🎀
2513 Managed Objects for Controlling the Collection and Storage of Accounting Information for Connection-Oriented Networks (McCloghrie, Feb 1999) 🧾 This memo defines a portion of the MIB for use with network management protocols in the Internet community. In particular, it describes managed objects used for controlling the collection and storage of accounting information for connection-oriented ✨
networks such as ATM. [STANDARDS-TRACK] ✨
2512 McCloghrie Feb 1999 Accounting Information for ATM
Networksokay bestie, this one is all about accounting for ATM 💅 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community 🧚 It lays out a set of ATM-specific accounting info that can be collected for connections on ATM networks 📊 [STANDARDS-TRACK] 🫶
2511 Myers Mar 1999 Internet X.509 Certificate
Request Message Formatthis one's giving certificate requests 🔐 This document describes the Certificate Request Message Format (CRMF) 💜 [STANDARDS-TRACK]
2510 Adams Mar 1999 Internet X.509 Public Key
Infrastructure Certificate
Management Protocolsnext up is the whole PKI certificate management protocols era 👑 This document describes the Internet X.509 Public Key Infrastructure (PKI) Certificate Management Protocols 🌸 [STANDARDS-TRACK]
2509 Engan Feb 1999 IP Header Compression over PPPokay so this one is about shrinking IP headers over PPP links 🦋 This document describes an option for negotiating the use of header compression on IP datagrams transmitted over the Point-to-Point Protocol. It defines extensions to the PPP Control Protocols for IPv4 and IPv6 ✨ [STANDARDS-TRACK]
2508 Casner Feb 1999 Compressing IP/UDP/RT Headers
for Low-Speed Serial Linksmain character energy for slow links 🐢 This document describes a method for compressing the headers of IP/UDP/RTP datagrams to reduce overhead on low-speed serial links 💖 [STANDARDS-TRACK]
2507 Degermark Feb 1999 IP Header Compressionngl this is the one that started the header compression obsession 🌈 This document describes how to compress multiple IP headers and TCP and UDP headers per hop over point to point links 🔥 [STANDARDS-TRACK]
2506 Holtman Mar 1999 Media Feature Tag Registration
Procedureokay, registration era 🎀 This document defines a registration procedure which uses the Internet Assigned Numbers Authority (IANA) as a central registry for the media feature vocabulary 🍓 This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements 🫶
2505 Lindberg Feb 1999 Anti-Spam Recommendations for
SMTP MTAsspam is literally not it 🙅♀️ This memo gives a number of implementation recommendations for SMTP, MTAs (Mail Transfer Agents, e.g. sendmail,) to make them more capable of reducing the impact of spam 💅 This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
2504 Guttman Feb 1999 Users' Security Handbookthis one is the bestie handbook for regular users 🔐 The Users' Security Handbook is the companion to the Site Security Handbook (SSH). It is intended to provide users with the information they need to help keep their networks and systems secure 🛡️ This memo provides information for the Internet community 💜
2503 Moulton Feb 1999 MIME Types for Use with the
ISO ILL ProtocolMIME types go brr 📎 This memorandum describes a set of MIME types for use with the ISO Interlibrary Loan Protocol (ISO 10160/10161) 📚 This memo provides information for the Internet community ✨
2502 Pullen Feb 1999 Limitations of Internet Protocol
Suite for Distributed Simulation
the Large Multicast Environmentthis one is so specific and I'm obsessed 🧚 This memo defines services that LSMA has found to be required, and aspects of the Internet protocols that LSMA has found to need further development in order to meet these requirements 🌸 This memo provides information for the Internet community.
2501 Corson Jan 1999 Mobile Ad hoc Networking (MANET):
Routing Protocol Performance
Issues and Evaluation
Considerationsmobile ad hoc networks are lowkey chaotic 🦋 This memo first describes the characteristics of Mobile Ad hoc Networks (MANETs), and their idiosyncrasies with respect to traditional, hardwired packet networks. It then discusses the effect these differences have on the design and evaluation of network control protocols with an emphasis on routing performance evaluation considerations 🌈 This memo provides information for the Internet community.
2500 IETF Jun 1999 Internet Official Protocol
Standardsand finally, the big status summary 👑 This memo summarizes the status of Internet protocols and specifications 💅 [STANDARDS-TRACK]
Security Considerations ✨
This memo does not affect the technical security of the Internet, but it does cite some security specifications 🔐
Author's Address 🎀
Alison De La Cruz
University of Southern California
Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292
Phone: (310) 822-1511
EMail: delacruz@isi.eduFull Copyright Statement 💖
Copyright (C) The Internet Society (2000). 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.
Acknowledgement 🫶
Funding for the RFC Editor function is currently provided by the Internet Society. 🌈
📦 where this page comes from
- ietf: rfc2599 2000-03
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms