RFC 2999
Request for Comments Summary RFC Numbers 2900-2999
Request for Comments Summary 🎀
okay bestie, the title block tea ☕ this is RFC 2999, called Request for Comments Summary, from the Network Working Group 🌸 It's by S. Ginoza at ISI, it's in the Informational category, and it's dated August 2001. The header doesn't list any RFCs it obsoletes or updates, so it's just vibing solo 🦋 Its whole thing is covering RFC Numbers 2900-2999.
Status of This Memo 💅
so this is literally a slightly annotated list of the 100 RFCs from RFC 2900 through RFCs 2999 ✨ it's a status report on those RFCs. This memo gives info to the Internet community, and it does not specify an Internet standard of any kind. Distribution is unlimited, so share it with everyone 🌈
Copyright Notice 🔒
the legal bit is Copyright (C) The Internet Society (2001). All Rights Reserved. 💜
Note ✨
not every RFC is a Proposed Standard, Draft Standard, or Standard, but many are 👀 statuses can change during standards processing, so this list only says which ones are on the standards track. For the current state, check the latest edition of "Internet Official Protocol Standards" 🔥 Standards-track RFCs are marked [STANDARDS-TRACK] in this note, but the entries below actually spell it [STANDARDS TRACK] (with a space), so keep an eye out 🙈
The RFC Lineup 🧚
RFC 2999 🎀
2999 Ginoza Aug 2001 Request for Comments Summarythis memo is literally itself 🙈 it's the summary you're reading rn
RFC 2998 🦋
2998 Bernet Nov 2000 A Framework for Integrated
Services Operation over
Diffserv Networksthis one lays out a framework for how Integrated Services can be supported over Diffserv networks. It's informational, so it's giving context, not a spec 💖
RFC 2997 🌸
2997 Bernet Nov 2000 Specification of the Null
Service Typeokay this one is so good 😭 the Null Service lets apps identify themselves to network Quality of Service (QoS) policy agents using RSVP signaling, but they don't have to specify resource requirements. The policy agents respond by applying QoS policies that fit the app (as the network administrator decides) 🔥 It's especially useful on networks mixing differentiated service (diffserv) QoS with RSVP signaling, because the policy agents can point the signaled app's traffic at a particular diffserv class of service 💅 [STANDARDS TRACK]
RFC 2996 🧚
2996 Bernet Nov 2000 Format of the RSVP DCLASS
Objectthis one nails down the format of the DCLASS object and briefly talks about how it's used ✨ [STANDARDS TRACK]
RFC 2995 🌈
2995 Lu Nov 2000 Pre-SPIRITS Implementations of
PSTN-initiated Servicesngl this is a fun one 🫶 it describes four existing implementations of SPIRITS-like services, from Korea Telecom, Lucent Technologies, NEC, and Telia, all working with Nortel Networks. SPIRITS-like services start in the Public Switched Telephone Network (PSTN) and need the Internet and the PSTN to work together 📞 It's informational, so it's a real-world snapshot 💜
RFC 2994 💜
2994 Ohta Nov 2000 A Description of the MISTY1
Encryption Algorithmthe crypto queen is here 👑 MISTY1 is a secret-key cryptosystem, a block cipher with a 128-bit key, a 64-bit block, and a variable number of rounds. This doc walks through the algorithm, including its key scheduling part and its data randomizing part 🔐 It's informational.
RFC 2993 🍓
2993 Hain Nov 2000 Architectural Implications of
NATthis is the big-picture NAT talk 🍓 it covers the architectural implications of Network Address Translation (NAT) and gives guidelines for implementations. Informational, so it's sharing lessons, not laying down law 🫶
RFC 2992 ✨
2992 Hopps Nov 2000 Analysis of an Equal-Cost
Multi-Path Algorithmokay so equal-cost multi-path (ECMP) is a routing technique for sending packets along multiple paths of equal cost 🛣️ The forwarding engine tells paths apart by next-hop, and when a packet shows up, the router has to decide which next-hop (path) to use. This doc analyzes one method for making that call, including how well the algorithm performs and how much disruption happens when the set of next-hops changes 🔥 It's informational.
RFC 2991 🌟
2991 Thaler Nov 2000 Multipath Issues in Unicast
and Multicast Next-Hop
Selectionso with multipath routing, a forwarder can have several next-hops for any destination, which means it has to use some method to pick the right one for each packet 🧩 This memo sums up current practices, problems, and solutions. It's informational, so it's the full tea on the state of things ☕
RFC 2990 👑
2990 Huston Nov 2000 Next Steps for the IP QoS
Architecturethis one is giving "what's next" energy 🚀 it highlights the open architectural issues around deploying and using QoS mechanisms inside internet networks, and points out where more standards work could help. It's the outcome of a collaborative exercise by the Internet Architecture Board. Informational, and very iconic 💅
RFC 2989 🌸
2989 Aboba Nov 2000 Criteria for Evaluating AAA
Protocols for Network Accessthis is a summary of the Authentication, Authorization, Accounting (AAA) protocol requirements for network access 📋 It's informational, so it's a checklist for comparing protocols 🫶
RFC 2988 🎀
2988 Paxson Nov 2000 Computing TCP's Retransmission
Timerok this one is a must-read for TCP nerds 🤓 it defines the standard algorithm that Transmission Control Protocol (TCP) senders are required to use to compute and manage their retransmission timer ⏱️ [STANDARDS TRACK]
RFC 2987 🦋
2987 Hoffman Nov 2000 Registration of Charset and
Languages Media Features Tagsthis one registers two media feature tags, "charset" and "language" 🏷️ [STANDARDS TRACK]
RFC 2986 💖
2986 Nystrom Nov 2000 PKCS #10: Certification
Request Syntax Specification
Version 1.7this is a republication of PKCS #10 v1.7 from RSA Laboratories' Public-Key Cryptography Standards (PKCS) series 🔑 Change control stays inside the PKCS process. Everything in the body except the security considerations section is taken straight from PKCS #9 v2.0 or PKCS #10 v1.7. It's informational.
RFC 2985 💜
2985 Nystrom Nov 2000 PKCS #9: Selected Object
Classes and Attribute Types
Version 2.0another republication from the PKCS crew 🔐 this one brings over PKCS #9 v2.0 from RSA Laboratories' PKCS series. Change control is still with the PKCS process, and the body (minus the security considerations section) comes directly from that spec. Informational, so it's giving reference vibes 📚
RFC 2984 🌈
2984 Adams Oct 2000 Use of the CAST-128 Encryption
Algorithm in CMSthis one shows how to bring CAST-128 into the S/MIME Cryptographic Message Syntax (CMS) as an extra algorithm for symmetric encryption 🔒 [STANDARDS TRACK]
RFC 2983 🧚
2983 Black Oct 2000 Differentiated Services and
Tunnelsthis one looks at how differentiated services (diffserv) interacts with IP tunnels of different kinds 🚇 It's informational, so it's a "heads up, here's what happens" kinda doc 🫶
RFC 2982 🍓
2982 Kavasseri Oct 2000 Distributed Management
Expression MIBthis defines a piece of the Management Information Base (MIB) for network management protocols 🛠️ It's all about managed objects used for managing expressions of MIB objects. [STANDARDS TRACK]
RFC 2981 ⭐
2981 Kavasseri Oct 2000 Event MIBanother MIB slice for network management 📊 this one has managed objects you can use to manage and monitor MIB objects, and take action through events. [STANDARDS TRACK]
RFC 2980 🌸
2980 Barber Oct 2000 Common NNTP Extensionsthis one documents and discusses a bunch of popular extensions to the Network News Transfer Protocol (NNTP), as defined in RFC 977 📰 It's not meant to be a standard of any kind. The hope is that it works as a reference for future NNTP implementers 💖 It's informational.
RFC 2979 🔥
2979 Freed Oct 2000 Behavior of and Requirements
for Internet Firewallsthis defines behavioral characteristics of, and interoperability requirements for, Internet firewalls 🧱 It's informational, so it's a "how firewalls should act" reference 🫶
RFC 2978 🎀
2978 Freed Oct 2000 IANA Charset Registration
Proceduresso MIME and a bunch of other Internet protocols can use lots of different charsets, which makes labeling them super important 🏷️ This document specifies an Internet Best Current Practices for the Internet Community. It also requests discussion and suggestions for improvements, so jump in 💬
RFC 2977 🦋
2977 Glass Oct 2000 Mobile IP Authentication,
Authorization, and Accounting
Requirementsthis lists the requirements a AAA service would need to support in order to help provide Mobile IP services 📱 Informational, so it's a checklist for the vibes ✨
RFC 2976 💜
2976 Donovan Oct 2000 The SIP INFO Methodthis one extends the Session Initiation Protocol (SIP) by adding the INFO method 📞 INFO is meant for carrying session-related control information that gets generated during a session. [STANDARDS TRACK]
RFC 2975 🌈
2975 Aboba Oct 2000 Introduction to Accounting
Managementthis one describes and discusses the issues involved in designing modern accounting systems 💅 Accounting Management is all about collecting resource consumption data for capacity and trend analysis, cost allocation, auditing, and billing 🧾 Informational, so it's a friendly intro 🫶
RFC 2974 🍓
2974 Handley Oct 2000 Session Announcement Protocolthis describes version 2 of the multicast session directory announcement protocol, the Session Announcement Protocol (SAP) 📣 It also covers the security and scalability issues that implementors should take into account. This memo defines an Experimental Protocol for the Internet community, so it's a bit of an experiment 🧪
RFC 2973 🧚
2973 Balay Oct 2000 IS-IS Mesh Groupsokay this one is about a mechanism to cut down on redundant packet transmissions for the Intermediate System to Intermediate System (IS-IS) 🌐 the rest of this entry is coming up in part 2, so stay tuned bestie 💖✨
Okay so the first bit is the end of an entry about IS-IS, the routing protocol described in ISO 10589. It's giving standard "for the Internet community" info vibes 🦋
RFC 2972 · Context and Goals for Common Name Resolution 🌸
Popp, Oct 2000 💖
This doc sets the scene and goals for a Common Name Resolution Protocol. It's info for the Internet community ✨
RFC 2971 · IMAP4 ID extension 🎀
Showalter, Oct 2000 💅
This one's an ID extension that lets Internet Message Access Protocol - Version 4rev1 (IMAP4rev1) announce which program a client or server is running. The client and server swap identification info about their implementation, so bug reports and usage stats are way more complete 📊 [STANDARDS TRACK] 🔥
RFC 2970 · Architecture for Integrated Directory Services - Result from TISDAG 🧚
Daigle, Oct 2000 🫶
Drawing on what the TISDAG (Technical Infrastructure for Swedish Directory Access Gateways) project learned, this doc lays out how to link lots of widely scattered servers into one service. The big move? It doesn't force every server to use one protocol and one schema set. It's giving flexibility 👑 This memo provides information for the Internet community.
RFC 2969 · Wide Area Directory Deployment - Experiences from TISDAG 🍓
Eklof, Oct 2000 📚
This doc shares what happened when building the infrastructure for a national (multi-organizational) directory service, plus a pilot deployment running on off-the-shelf directory service products. Real-life lessons, no cap 🙈 This memo provides information for the Internet community.
RFC 2968 · Mesh of Multiple DAG servers - Results from TISDAG 🕸️
Daigle, Oct 2000 ✨
This one sets the basic principle for building a mesh: interoperating services swap index objects, depending on the mesh's architecture (hierarchical, or graph-like, ideally without loops!) 😭 The Common Indexing Protocol (CIP) is built to make not just query referral indexes, but also meshes of (loosely) affiliated referral indexes. The point of a mesh like this is distributed sharing of indexing and/or searching tasks across servers. TISDAG focused on one referral index so far, so the obvious next step is connecting it to a bigger group of interoperating services 💜 This memo provides information for the Internet community.
RFC 2967 · TISDAG - Technical Infrastructure for Swedish Directory Access Gateways 🇸🇪
Daigle, Oct 2000 🌈
The big goal here is building the technical infrastructure for a single-access-point service that searches whitepages info on Swedish Internet users. Main character project 💅 This memo provides information for the Internet community.
RFC 2966 · Domain-wide Prefix Distribution with Two-Level IS-IS 🦋
Li, Oct 2000 💖
This doc describes extensions to the Intermediate System to Intermediate System (IS-IS) protocol so it can do optimal routing inside a two-level domain. Routing glow-up 🔥 This memo provides information for the Internet community.
RFC 2965 · HTTP State Management Mechanism 🍪
Kristol, Oct 2000 💜
This spec explains how to create a stateful session with Hypertext Transfer Protocol (HTTP) requests and responses. [STANDARDS TRACK] ⭐
RFC 2964 · Use of HTTP State Management 🙈
Moore, Oct 2000 🌸
This memo calls out specific uses of the HTTP State Management protocol that are either (a) not recommended by the IETF, or (b) believed to be harmful and discouraged. It also gets into extra privacy considerations that the HTTP State Management spec doesn't cover. This doc is an Internet Best Current Practices document for the Internet Community, and it's asking for discussion and suggestions for improvements 🫶
⚠️ Heads up bestie: the IETF doesn't recommend some of these HTTP state uses, and others could be harmful, so be careful with cookies 🍪💀
RFC 2963 · A Rate Adaptive Shaper for Differentiated Services 🎀
Bonaventure, Oct 2000 ✨
This memo describes several Rate Adaptive Shapers (RAS) that work together with the single rate Three Color Markers (srTCM) and the two rate Three Color Marker (trTCM), which are described in RFC2697 and RFC2698 respectively. This memo provides information for the Internet community.
RFC 2962 · An SNMP Application Level Gateway for Payload Address Translation 🧚♀️
Raz, Oct 2000 🌈
This doc describes the ALG (Application Level Gateway) for SNMP (Simple Network Management Protocol). It statically maps IP (Internet Protocol) addresses in the payload of SNMP packets from one group to another. This memo provides information for the Internet community.
RFC 2961 · RSVP Refresh Overhead Reduction Extensions 🔥
Berger, Apr 2001 💅
This doc describes a bunch of mechanisms to cut down the processing overhead of refresh messages. It also gets rid of the state synchronization latency that happens when an RSVP (Resource ReserVation Protocol) message gets lost, and when you want it, lets you refresh state without sending whole refresh messages. [STANDARDS TRACK] 👑
RFC 2960 · Stream Control Transmission Protocol 🌊
Stewart, Oct 2000 💖
This document describes the Stream Control Transmission Protocol (SCTP). [STANDARDS TRACK] ✨
RFC 2959 · Real-Time Transport Protocol Management Information Base 📊
Baugher, Oct 2000 🦋
This memo defines a piece of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS TRACK] 🫶
RFC 2958 · The application/whoispp-response Content-type 💌
Daigle, Oct 2000 🌸
With RFC 2957, this doc helps MIME-enabled mail software, and other systems that use Internet media types, carry out Whois++ transactions. This memo provides information for the Internet community. 🍓
RFC 2957 · The application/whoispp-query Content-Type 💌
Daigle, Oct 2000 🌸
With RFC 2958, this doc helps MIME-enabled mail software, and other systems that use Internet media types, carry out Whois++ transactions. This memo provides information for the Internet community. 🍓
RFC 2956 · Overview of 1999 IAB Network Layer Workshop 🗺️
Kaat, Oct 2000 🧚
This doc gives an overview of a workshop the Internet Architecture Board (IAB) held on the Internet Network Layer architecture. It was hosted by SURFnet in Utrecht, the Netherlands, on 7-9 July 1999. The goal was to figure out the state of the network layer and how it affects continued growth and usage of the Internet 🌈 This memo provides information for the Internet community.
RFC 2955 · Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function 🔧
Rehbehn, Oct 2000 ✨
This memo defines a Management Information Base (MIB) to configure, monitor, and control a service interworking function (IWF) for Permanent Virtual Connections (PVC) between Frame Relay and Asynchronous Transfer Mode (ATM) technologies. [STANDARDS TRACK] 💜
RFC 2954 · Definitions of Managed Objects for Frame Relay Service 🔧
Rehbehn, Oct 2000 🫶
This memo extends the Management Information Base (MIB) for use with network management protocols in Transmission Control Protocol/Internet Protocol-based (TCP/IP) internets. Specifically, it defines objects for managing the frame relay service. [STANDARDS TRACK] 🌸
RFC 2953 · Telnet Encryption: DES 64 bit Output Feedback 🔐
Ts'o, Sep 2000 💅
This doc specifies how to use the data encryption standard (DES) algorithm in output feedback mode with the telnet encryption option. This memo provides information for the Internet community. ✨
RFC 2952 · Telnet Encryption: DES 64 bit Cipher Feedback 🔐
Ts'o, Sep 2000 💖
This doc specifies how to use the DES encryption algorithm in cipher feedback mode with the telnet encryption option. This memo provides information for the Internet community. 🦋
RFC 2951 · TELNET Authentication Using KEA and SKIPJACK 🔑
Housley, Sep 2000 🌈
This doc defines a way to authenticate TELNET using the Key Exchange Algorithm (KEA), and to encrypt the TELNET stream using SKIPJACK. This memo provides information for the Internet community. 👑
RFC 2950 · Telnet Encryption: CAST-128 64 bit Cipher Feedback 🔐
Altman, Sep 2000 🎀
This doc specifies how to use the CAST-128 encryption algorithm in cipher feedback mode with the telnet encryption option. Two key sizes are defined: 40 bit and 128 bit. [STANDARDS TRACK] 🍓
RFC 2949 · Telnet Encryption: CAST-128 64 bit Output Feedback 🔐
Altman, Sep 2000 🌸
This doc specifies how to use the CAST-128 encryption algorithm in output feedback mode with the telnet encryption option. Two key sizes are defined: 40 bit and 128 bit. [STANDARDS TRACK] 💜
RFC 2948 · Telnet Encryption: DES3 64 bit Output Feedback 🔐
Altman, Sep 2000 ✨
This doc specifies how to use the Triple-DES (data encryption standard) algorithm in output feedback mode with the telnet encryption option. [STANDARDS TRACK] 🫶
RFC 2947 · Telnet Encryption: DES3 64 bit Cipher Feedback 🔐
Altman, Sep 2000 💅
This doc specifies how to use the Triple-DES (data encryption standard) algorithm in cipher feedback mode with the telnet encryption option. [STANDARDS TRACK] 🦋
RFC 2946 · Telnet Data Encryption Option 🔐
Ts'o, Sep 2000 🌈
This doc describes the telnet encryption option as a generic way to provide data confidentiality services for the telnet data stream. [STANDARDS TRACK] 👑
RFC 2945 · The SRP Authentication and Key Exchange System 🔑
Wu, Sep 2000 💖
This doc describes a cryptographically strong network authentication mechanism called the Secure Remote Password (SRP) protocol. [STANDARDS TRACK] ✨
RFC 2944 · Telnet Authentication: SRP 🔑
Wu, Sep 2000 🌸
This doc specifies an authentication scheme for the Telnet protocol under the framework described in RFC 2941. It uses the Secure Remote Password Protocol (SRP) authentication mechanism. [STANDARDS TRACK] 🎀
RFC 2943 · TELNET Authentication Using DSA 🔑
Housley, Sep 2000 🧚
This doc defines a telnet authentication mechanism using the Digital Signature Algorithm (DSA). It relies on the Telnet
Authentication Option. [STANDARDS TRACK]
2942 Telnet Authentication: Kerberos Version 5 💖
Author: Ts'o | Date: Sep 2000
okay so this one is all about how Kerberos Version 5 gets used with the telnet protocol 🦋 It describes a telnet authentication suboption that's meant to be used with the telnet authentication option. main character energy, fr fr ✨ [STANDARDS TRACK]
2941 Telnet Authentication Option 🎀
Author: Ts'o | Date: Sep 2000
this one describes the authentication option for telnet as a generic method for negotiating an authentication type and mode 🫶 It covers whether encryption should be used and whether credentials should be forwarded. lowkey the whole thing is about making the negotiation flexible 💅 [STANDARDS TRACK]
2940 Definitions of Managed Objects for Common Open Policy Service (COPS) Protocol Clients 🌸
Author: Smith | Date: Oct 2000
this memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets 🧚 specifically, it defines objects for managing a client of the Common Open Policy Service (COPS) protocol. it's giving network admin realness 👑 [STANDARDS TRACK]
2939 Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types 🍓
Author: Droms | Date: Sep 2000
this document describes the procedure for defining new DHCP options and message types 💜 it specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. bestie, you can totally weigh in 🫶
2938 Identifying Composite Media Features ✨
Author: Klyne | Date: Sep 2000
this document describes an abbreviated format for a composite media feature set, based on a hash of the feature expression describing that composite. the way that this shrinks things down is so iconic 🦋 [STANDARDS TRACK]
2937 The Name Service Search Option for DHCP 🌈
Author: Smith | Date: Sep 2000
this document defines a new Dynamic Host Configuration Protocol (DHCP) option. it's passed from the DHCP Server to the DHCP Client to specify the order in which name services should be consulted when resolving hostnames and other information ✨ it's literally a priority list for name lookups, so cute 🎀 [STANDARDS TRACK]
2936 HTTP MIME Type Handler Detection 🌸
Author: Eastlake | Date: Sep 2000
okay the problem here is that entities composing web pages to provide services over the Hypertext Transfer Protocol (HTTP) frequently don't know what Multipurpose Internet Mail Extensions (MIME) types have handlers installed at a user's browser 😭 this document summarizes reasonable techniques to solve this for most of the browsers actually deployed on the Internet as of early 2000. this memo provides information for the Internet community 💅
2935 Internet Open Trading Protocol (IOTP) HTTP Supplement 🫶
Author: Eastlake | Date: Sep 2000
the goal of mapping to the transport layer is to make sure the underlying XML documents get carried successfully between the various parties 💖 this document describes that mapping for the Hyper Text Transport Protocol (HTTP), Versions 1.0 and 1.1. [STANDARDS TRACK]
2934 Protocol Independent Multicast MIB for IPv4 🦋
Author: McCloghrie | Date: Oct 2000
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 managed objects used for managing the Protocol Independent Multicast (PIM) protocol for IPv4. this memo defines an Experimental Protocol for the Internet community. experimental era, bestie 🧪
2933 Internet Group Management Protocol MIB 💜
Author: McCloghrie | Date: Oct 2000
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 objects used for managing the Internet Group Management Protocol (IGMP). [STANDARDS TRACK]
2932 IPv4 Multicast Routing MIB ⭐
Author: McCloghrie | Date: Oct 2000
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 managed objects used for managing IP Multicast Routing for IPv4, independent of the specific multicast routing protocol in use. [STANDARDS TRACK]
2931 DNS Request and Transaction Signatures ( SIG(0)s ) 🔥
Author: Eastlake | Date: Sep 2000
this document describes the minor but non-interoperable changes in Request and Transaction signature resource records ( SIG(0)s ) that implementation experience has deemed necessary 💀 the tea is that these changes weren't optional, they were needed. [STANDARDS TRACK]
2930 Secret Key Establishment for DNS (TKEY RR) 🔐
Author: Eastlake | Date: Sep 2000
this document describes a Transaction Key (TKEY) RR that can be used in a number of different modes to establish shared secret keys between a DNS resolver and server 🗝️ it's the secret handshake of DNS, and I'm obsessed 😭 [STANDARDS TRACK]
2929 Domain Name System (DNS) IANA Considerations 🌸
Author: Eastlake | Date: Sep 2000
this document discusses the Internet Assigned Number Authority (IANA) parameter assignment considerations given for the allocation of Domain Name System (DNS) classes, Resource Record (RR) types, operation codes, error codes, etc. it specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements 💅
2928 Initial IPv6 Sub-TLA ID Assignments 🧚
Author: Hinden | Date: Sep 2000
this document defines initial assignments of IPv6 Sub-Top-Level Aggregation Identifiers (Sub-TLA ID) to the Address Registries. this memo provides information for the Internet community ✨
2927 MIME Directory Profile for LDAP Schema 🎀
Author: Wahl | Date: Sep 2000
this document defines a multipurpose internet mail extensions (MIME) directory profile for holding a lightweight directory access protocol (LDAP) schema. this memo provides information for the Internet community 🫶
2926 Conversion of LDAP Schemas to and from SLP Templates 🦋
Author: Kempf | Date: Sep 2000
this document describes a procedure for mapping between Service Location Protocol (SLP) service advertisements and lightweight directory access protocol (LDAP) descriptions of services 🌈 this memo provides information for the Internet community.
2925 Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations 🍓
Author: White | Date: Sep 2000
this memo defines Management Information Bases (MIBs) for performing remote ping, traceroute and lookup operations at a remote host 💜 [STANDARDS TRACK]
2924 Accounting Attributes and Record Formats 💖
Author: Brownlee | Date: Sep 2000
this document summarises Internet Engineering Task Force (IETF) and International Telecommunication Union (ITU-T) documents related to Accounting 📚 this memo provides information for the Internet community.
2923 TCP Problems with Path MTU Discovery 😭
Author: Lahey | Date: Sep 2000
this memo catalogs several known Transmission Control Protocol (TCP) implementation problems dealing with Path Maximum Transmission Unit Discovery (PMTUD) 💀 the list includes the long-standing black hole problem, stretch acknowlegements (ACKs) due to confusion between Maximum Segment Size (MSS) and segment size, and MSS advertisement based on PMTU. this memo provides information for the Internet community ✨
2922 Physical Topology MIB 🌸
Author: Bierman | Date: Sep 2000
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 managed objects used for managing physical topology identification and discovery. this memo provides information for the Internet community 💅
2921 6BONE pTLA and pNLA Formats (pTLA) 🌈
Author: Fink | Date: Sep 2000
this memo defines how the 6bone uses the 3FFE::/16 IPv6 address prefix, allocated in RFC 2471, "IPv6 Testing Address Allocation", to create pseudo Top-Level Aggregation Identifiers (pTLA's) and pseudo Next-Level Aggregation Identifiers (pNLA's) 🦋 this memo provides information for the Internet community.
2920 SMTP Service Extension for Command Pipelining 🎀
Author: Freed | Date: Sep 2000
this memo defines an extension to the Simple Mail Transfer Protocol (SMTP) service whereby a server can indicate the extent of its ability to accept multiple commands in a single Transmission Control Protocol (TCP) send operation. [STANDARDS TRACK] ⭐
2919 List-Id: A Structured Field and Namespace for the Identification of Mailing Lists 💜
Author: Chandhok | Date: Mar 2001
software that handles electronic mailing list messages (servers and user agents) needs a way to reliably identify messages that belong to a particular mailing list 📬 with the advent of list management headers, it has become even more important to provide a unique identifier for a mailing list regardless of the particular host that serves as the list processor at any given time. [STANDARDS TRACK] 🫶
2918 Route Refresh Capability for BGP-4 🔥
Author: Chen | Date: Sep 2000
this document defines a new Border Gateway Protocol (BGP) capability termed 'Route Refresh Capability', which would allow the dynamic exchange of route refresh requests between BGP speakers and subsequent re-advertisement of the respective Adj-RIB-Out 🌐 [STANDARDS TRACK]
2917 A Core MPLS IP VPN Architecture 🌸
Author: Muthukrishnan | Date: Sep 2000
this memo presents an approach for building core Virtual Private Network (VPN) services in a service provider's MPLS backbone 🧚 this memo provides information for the Internet community 💅
2916 E.164 number and DNS 📞
Author: Faltstrom | Date: Sep 2000
this document discusses the use of the Domain Name System (DNS) for storage of E.164 numbers. [Standards Track] ✨
2915 The Naming Authority Pointer (NAPTR) DNS Resource Record 🦋
Author: Mealling | Date: Sep 2000
this document describes a Domain Name System (DNS) resource record which specifies a regular expression based rewrite rule that, when applied to an existing string, will produce a new domain label or Uniform Resource Identifier (URI) 🎀 [STANDARDS TRACK]
2914 Congestion Control Principles 🌈
Author: Floyd | Date: Sep 2000
the goal of this document is to explain the need for congestion control in the Internet, and to discuss what constitutes correct congestion control 🫶 it specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
2913 MIME Content Types in Media Feature Expressions 💜
Author: Klyne | Date: Sep 2000
this memo defines a media feature tag whose value is a Multipurpose Internet Mail Extensions (MIME) content type 🍓 [STANDARDS TRACK]
2912 Indicating Media Features for MIME Content 🧚
Author: Klyne | Date: Sep 2000
this memo defines a Multipurpose Internet Mail Extensions (MIME) 'Content-features:' header that can be used to annotate a MIME message part using this expression format, and indicates some ways it might be
heads up bestie 🫶 this chunk is actually the RFC index (the list of RFCs from 2000 to 2001) plus the RFC 2900 wrap-up, not the body of RFC 2999, so I rewrote exactly what you sent.
used. [STANDARDS TRACK] ✨
2911 Hastings Sep 2000 Internet Printing
Protocol/1.1: Model and
Semanticsokay, this one is part of a whole set of docs that together cover every aspect of the brand-new Internet Printing Protocol (IPP) 🖨️ [STANDARDS TRACK]
2910 Herriot Sep 2000 Internet Printing
Protocol/1.1: Encoding and
Transportsame squad as 2911 💅 another piece of that IPP set, covering everything about the brand-new protocol [STANDARDS TRACK]
2909 Radoslavov Sep 2000 The Multicast Address-Set
Claim (MASC) Protocolthis one describes the Multicast Address-Set Claim (MASC) protocol, which can be used for inter-domain multicast address set allocation 🦋 This memo defines an Experimental Protocol for the Internet community.
2908 Thaler Sep 2000 The Internet Multicast Address
Allocation Architectureit proposes a multicast address allocation architecture (MALLOC) for the Internet 🌸 This memo provides information for the Internet community.
2907 Kermode Sep 2000 MADCAP Multicast Scope Nesting
State Optionso this defines a new option for the Multicast Address Dynamic Client Allocation Protocol (MADCAP) to support nested scoping 🧚 [STANDARDS TRACK]
2906 Farrell Aug 2000 AAA Authorization Requirementsthis one spells out the requirements that Authentication Authorization Accounting (AAA) protocols must meet in order to support authorization services in the Internet 🔐 This memo provides information for the Internet community.
2905 Vollbrecht Aug 2000 AAA Authorization Application
Examplesexamples! it describes several applications that need authorization, which is so helpful 🍓 This memo provides information for the Internet community.
2904 Vollbrecht Aug 2000 AAA Authorization Frameworkthis is the base requirements memo for Authorization of Internet Resources and Services (AIRS) 👑 It presents an architectural framework for understanding the authorization of Internet resources and services, and it derives requirements for authorization protocols. This memo provides information for the Internet community.
2903 de Laat Aug 2000 Generic AAA Architecturethis one proposes an Authentication, Authorization, Accounting (AAA) architecture with a generic AAA server, plus an application interface to a set of Application Specific Modules that can do application specific AAA functions 🫧 This memo defines an Experimental Protocol for the Internet community.
2902 Deering Aug 2000 Overview of the 1998 IAB
Routing Workshopthis is an overview of a Routing workshop the Internet Architecture Board (IAB) held during March 25-27, 1998 🌊 This memo provides information for the Internet community.
2901 Wenzel Aug 2000 Guide to Administrative
Procedures of the Internet
Infrastructurethis one describes the administrative procedures for networks that want to connect to the global Internet 🌍 This memo provides information for the Internet community.
2900 Reynolds Aug 2001 Internet Official Protocol
Standardsokay the big one 🌈 this memo is a snapshot of the state of standardization of protocols used in the Internet as of July 17, 2001. It lists official protocol standards and Best Current Practice RFCs, but it is not a complete index to the RFC series. This memo is an Internet Standard.
Security Considerations ✨
serious moment 🥺 This memo does not affect the technical security of the Internet, but it may cite important security specifications.
Author's Address 🎀
Sandy Ginoza is the author, and her contact details are below 💌
Sandy Ginoza
University of Southern California
Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292
Phone: (310) 822-1511
EMail: ginoza@isi.eduFull Copyright Statement 💜
Copyright (C) The Internet Society (2001). All Rights Reserved.Okay so the vibe is: you can copy this document and pass it around, and you can make derivative works that comment on or explain it or help with implementing it, then publish and distribute them, in whole or in part, with no restrictions of any kind. The catch is that the copyright notice and this paragraph have to stay on all copies and derivative works. This document itself can't be modified in any way, like removing the copyright notice or the references to the Internet Society or other Internet organizations, except for developing Internet standards (then the Internet Standards process copyright procedures must be followed) or translating it into languages other than English. These limited permissions are perpetual and won't be revoked by the Internet Society or its successors or assigns.
This document and the information in it is provided "AS IS", 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 🫶
the RFC Editor function is currently funded by the Internet Society ✨
📦 where this page comes from
- ietf: rfc2999 2001-08
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms